intrepid - 2.6.27-7generic - X does not start - mtrr base (0xcd000000) is not aligned on a size (0xe00000) boundary

[HugoHirsch]

Fujitsu Amilo XI2428 with current up2date intrepid 8.10 -
2.6.27-7 kernel installed.

X does not start and last message in log is

[ 760.132151] mtrr: base(0xcd000000) is not aligned on a size(0xe00000) boundary
[ 907.201639] mtrr: no MTRR for cd000000,e00000 found
[ 986.016077] mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary

System runs with kdm.

[HugoHirsch (ubuntubugs-aiki-it)]

Situation did not change until kdm was default display manager - after having switched back to gdm I'm able to login again.

dmesg does not contain above error message with "mtrr ... ".

[HugoHirsch (ubuntubugs-aiki-it)]

Kernel is:
$ uname -a
Linux shoshin 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686 GNU/Linux

[HugoHirsch (ubuntubugs-aiki-it)]

Same situation again -
if I switch to kdm as displaymanager via dpkg-reconfigure X does not come up and needs to be restarted after setting gdm as default display manager.

Last log message is:
[ 63.741143] NVRM : nv_acpi_nvif_method : NVIF data invalid. function d subFunction 0
[ 96.795864] mtrr: base(0xcd000000) is not aligned on a size(0xe00000) boundary
[ 143.985535] mtrr: no MTRR for cd000000,e00000 found
[ 226.214057] NVRM : nv_acpi_nvif_method : NVIF data invalid. function d subFunction 0

01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GS (rev a1)

~$ uname -a
Linux shoshin 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux

[Id2ndR (id2ndr)]

I saw an error that's rather the same that "mtrr: base(0xcd000000) is not aligned on a size(0xe00000) boundary" yesterday on a computer using an nvidia 8400GS on Intrepid and GDM wasn't able to start. Btw I didn't saw acpi related errors.
I just cleaned up the computer by purging obsoletes packages and removing all packages related to nvidia. Then I installed manually latest driver (177) from packages, and created a new xorg config with nvidia-xconfig. Then after having restarted it worked like a charm.

[HugoHirsch (ubuntubugs-aiki-it)]

Thanks for your comment - my problem is that KDM won't start but GDM does perfectly.

[HugoHirsch (ubuntubugs-aiki-it)]

Performed a fresh installation of ubuntu 8.10 on the same machine -
worked perfectly until I upgraded to nvidia-177.80 and kubuntu-desktop / kde-i18n.

Having installed kdm and ubuntu I wasn't able to reboot into graphical mode.

Solution was to switch back to gdm as default display manager - brings back X after reboot. Last log message was:
[ 96.995383] mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary

[HugoHirsch (ubuntubugs-aiki-it)]

These logs were created after reboot into not working graphical mode with nvidia 177.80 on a freshly installed ubuntu 8.10
-kdm.log
-messages*
-Xorg.0.*
-Xorg.failsafe.*
all zipped.

Last log message was:
mtrr: base(0xcd000000) is not aligned on a size (oxe00000) boundary

[HugoHirsch (ubuntubugs-aiki-it)]

:uname -a
Linux boxname 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

[Leann Ogasawara (leannogasawara)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.

[kernel-janitor (kernel-janitor)]

Hi HugoHirsch,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 288414

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[HugoHirsch (ubuntubugs-aiki-it)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:de:en_GB:en
Uname: Linux 2.6.28-15-generic i686
UserGroups:

[HugoHirsch (ubuntubugs-aiki-it)]

Same behaviour - after dpkg-reconfigure gdm and a reboot X crashes.

Last log message was:
[ 85.744829] NVRM : nv_acpi_nvif_method : NVIF data invalid. function d subFunction 0

[Leann Ogasawara (leannogasawara)]

Hi HugoHirsch,

Can you actually test and confirm against the newer Karmic 9.10 Alpha - http://cdimage.ubuntu.com/releases/karmic . It contains a newer 2.6.31 base kernel. Thanks.

[HugoHirsch (ubuntubugs-aiki-it)]

Hi Leann,
unfortunately I cannot check the change of gdm/kdm. Ubuntu-alpha5 and kubuntu-alpha5 work, but the problem occurred when changing the display manager on a running instance.

Sorry

[HugoHirsch (ubuntubugs-aiki-it)]

Seems to be fixed now - I'm able to change from gdm to kdm without any hickups. If kdm is selected I have a working X but cannot change to console (the console's picture is all white with colourful stripes flowing in the picture from the top).

[penalvch (penalvch)]

HugoHirsch, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288414/comments/17 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.