This did not happen with kernel 2.6.38-rc8 but started with the 2.6.38 release
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.
Right now I use 2.6.38.
Created attachment 44520 [details]
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 22.214.171.124 / 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 126.96.36.199 we had a memory corruption bug which could overwrite one word with 0xffffffff, it's quite possible it's the same bug...)