| View previous topic :: View next topic |
| Author |
Message |
fimblo
Guru
Joined: 19 Feb 2003
Posts: 306
Location: European Union, Stockholm
|
 Posted: Mon Sep 15, 2003 7:31 pm Post subject: mtrr problem? |
 |
|
hiya all,
I've got an Intel Celeron (Northwood) 2.00GHz, so I turned on mtrr in the kernel. Now Im seeing some strange stuff in dmesg:
| Code: | PCI: Found IRQ 11 for device 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
memory : c79e2200
memory : c79e2500
memory : c23de800
mtrr: base(0xe8020000) is not aligned on a size(0x400000) boundary
memory : c79e2780
memory : c79e2680
memory : c79e2c00
memory : c79e2280
memory : c79e2f80
PCI: Found IRQ 11 for device 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
|
And I have no idea what this is... is this a problem, or is it just telling me like, that there was a problem and that its solved now? Confused... 
/fimblo
_________________
http://blahonga.yanson.org - little geekblog
http://blahona.yanson.org/howtos/livecd - yet another livecd howto |
|
| Back to top |
|
 |
meowsqueak
Veteran
Joined: 26 Aug 2003
Posts: 1549
Location: New Zealand
|
| Posted: Tue Sep 16, 2003 3:39 am Post subject: |
|
|
| It doesn't look like an error to me - more like an 'informational message'. Since this stuff is all handled internally by the kernel, I personally wouldn't worry about it. Nothing has actually broken I take it? |
|
| Back to top |
|
|
fimblo
Guru
Joined: 19 Feb 2003
Posts: 306
Location: European Union, Stockholm
|
| Posted: Tue Sep 16, 2003 6:35 am Post subject: |
|
|
nope nothings broken, but its filling the dmesg, and I dont like that, since its... telling me something.
| Code: | ...
...
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1.
memory : cd13a900
memory : cd13a880
memory : cd13a800
[drm] AGP 0.99 aperture @ 0xe8000000 128MB
[drm] Initialized i830 1.3.2 20021108 on minor 0
mtrr: base(0xe8020000) is not aligned on a size(0x280000) boundary
memory : cd13a700
memory : cd13a680
memory : cd13a600
memory : cd13a580
memory : cd13a500
PCI: Found IRQ 11 for device 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
memory : cd13a900
memory : cd13a880
memory : cd13a800
mtrr: base(0xe8020000) is not aligned on a size(0x280000) boundary
memory : cd13a680
memory : cd13a600
memory : cd13a580
memory : cd13a500
memory : cd13a780
PCI: Found IRQ 11 for device 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
memory : cd13aa80
memory : cd13a880
memory : cd13a800
mtrr: base(0xe8020000) is not aligned on a size(0x280000) boundary
memory : cd13a600
memory : cd13a580
memory : cd13a500
memory : cd13a780
memory : cd13a480
PCI: Found IRQ 11 for device 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
memory : c3f02e80
memory : cd13a280
memory : cd13a380
mtrr: base(0xe8020000) is not aligned on a size(0x280000) boundary
memory : c3f02780
memory : c05e4980
memory : c3f02480
memory : c3f02f80
memory : cd13a900
PCI: Found IRQ 11 for device 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
sr0: mmc-3 profile: 0h
memory : c05e4400
memory : c310a400
memory : cb978400
mtrr: base(0xe8020000) is not aligned on a size(0x280000) boundary
memory : cdce0100
memory : c310ae80
memory : c05e4a80
memory : cd13a680
memory : c05e4b00
PCI: Found IRQ 11 for device 00:02.0
PCI: Sharing IRQ 11 with 00:1d.0
fimblo@tempname fimblo $ |
know what I mean? this just doesnt feel normal.
_________________
http://blahonga.yanson.org - little geekblog
http://blahona.yanson.org/howtos/livecd - yet another livecd howto |
|
| Back to top |
|
|
meowsqueak
Veteran
Joined: 26 Aug 2003
Posts: 1549
Location: New Zealand
|
| Posted: Tue Sep 16, 2003 9:03 pm Post subject: |
|
|
Hmmm, do you have any sort of extra debugging enabled somewhere in your kernel? I can't see any 'error' or 'warning' messages, but you are right - there's a lot of seemingly unhelpful guff there.
(being 'not aligned' might be a bonus or a problem - who knows?) |
|
| Back to top |
|
|
|
Kernel & Hardware
