Michael Marley, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report. apport-collect -p linux <replace-with-bug-number> 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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it. Please let us know your results. Thanks in advance. ** Tags added: needs-upstream-testing ** Description changed: I recently updated to the latest (2.6.35-8-generic) kernel on a Maverick system, but rebooting after the update caused Xorg not to start. I see the following messages in dmesg: [ 33.716949] Xorg:1316 conflicting memory types e0000000-e0546000 write-combining<->uncached-minus [ 33.716954] reserve_memtype failed 0xe0000000-0xe0546000, track write-combining, req write-combining [ 49.853274] Xorg:1492 conflicting memory types e0000000-e0546000 write-combining<->uncached-minus [ 49.853279] reserve_memtype failed 0xe0000000-0xe0546000, track write-combining, req write-combining I also see an error in Xorg.0.log: [ 49.853] (EE) NVIDIA(0): Failed to allocate primary buffer: out of memory. I tried reverting to the previous kernel, but this doesn't fix the problem. That makes me think maybe some other update caused the problem, but I can't find anything that looks suspicious in dpkg.log. + + WORKAROUND: Adding "nopat" to the kernel command line causes this + problem to go away. ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605837 Title: After recent updates, X will no longer start with the Nvidia driver on maverick (related to "pat"/"nopat" kernel option) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/605837/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
