Summary: | nouveau: oops in nv50_vm_map_pgt | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | somethingsome2000 | ||||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | blocker | ||||||||||
Priority: | medium | CC: | somethingsome2000 | ||||||||
Version: | 7.4 (2008.09) | ||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
somethingsome2000
2011-03-15 17:02:15 UTC
Created attachment 44489 [details]
dmesg logfile from boot
Created attachment 44490 [details]
xorg log file
I saw it only ones. Just after kernel upgrade from 2.6.38-rc7 to 2.6.38-rc8. I couldn't reproduce it. kernel: 2.6.38 xorg-server: 1.9.4 Right now I use 2.6.38. Created attachment 44520 [details]
Dmesg log
Very odd. I noticed that my kernel was compiled without debugging, so I decided to recompile with debugging enabled to get useful output for you guys. The strange thing is that with debugging enabled, my kernel can now boot properly Is it still crashing on newer kernel? I think we fixed it in 2.6.38.5 / 2.6.39-rc5. (Logs are from 2.6.38 / 2.6.38-rc8 and in both oops triggered on address which had high word set to 0xffffffff. Considering that between 2.6.38-rc7 and 2.6.38.5 we had a memory corruption bug which could overwrite one word with 0xffffffff, it's quite possible it's the same bug...) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.