|Summary:||2.6.38 kernel fails to boot with nouveau driver active|
|Component:||Driver/nouveau||Assignee:||Nouveau Project <nouveau>|
|Status:||RESOLVED DUPLICATE||QA Contact:||Xorg Project Team <xorg-team>|
|i915 platform:||i915 features:|
Description ghutzl 2011-04-17 13:28:16 UTC
Created attachment 45742 [details] my kernel config for a 22.214.171.124 vanilla kernel Hello! My 2.6.38 kernel fails to boot when using the nouveau driver. See these pictures of the kernel output while booting: http://tinypic.com/r/xefq6e/7 http://tinypic.com/r/2w5kc8w/7 http://tinypic.com/r/30wmlmv/7 I made 3 pictures because I wanted to show the effect of the "shifted" text in the fullscreen picture where you can barely read the text. The other two pictures show the text. I am running gentoo linux and I used kernel 2.6.37 for quite a while with no problems but was not able to produce a working 2.6.38 kernel. I have tried the gentoo-sources-2.6.38-r1 and also a vanilla 126.96.36.199 kernel and the behaviour is the same for both. I have attached my kernel config.
Comment 1 ghutzl 2011-04-17 13:50:00 UTC
Looks like I found the culprit: In a desperate attempt I have deactivated the boot logo display in my kernel and now it boots with no problems. Please tell me if and how I can help debugging this. For the moment I can perfectly live without the boot logo but I would like to contribute something to nouveau development if I can.
Comment 2 Marcin Slusarz 2011-04-17 14:28:27 UTC
This is probably the same bug which was reported recently: https://lkml.org/lkml/2011/4/15/27 https://bugs.freedesktop.org/show_bug.cgi?id=36248
Comment 3 Marcin Slusarz 2011-04-22 07:37:10 UTC
Yes, it's the same bug and it's fixed by commit a18d89ca026140eb8ac4459bf70a01c571dd9a32 "drm/nouveau: fix notifier memory corruption bug" (after 2.6.39-rc4). It will soon go to 2.6.38-stable. If you are impatient, you can apply it manually from: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=a18d89ca026140eb8ac4459bf70a01c571dd9a32 *** This bug has been marked as a duplicate of bug 35374 ***