Bug 360243 – kernel builds ok but unusable due to system lockup

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Geoff Madden 2011-03-24 09:17:38 UTC]

I have tried several configurations,all pretty similar, the last one i tried was for 2.6.37-r5
which was successful,but not with 2.6.38/2.6.37-2,7. I have not had hassles
previously with this config. But it started with 2.6.37,the kernel builds & installs
ok but reboot just gives me a hung computer with the keyboard lock led alight
& no responsiveness.

Reproducible: Always

Steps to Reproduce:
1.configure kernel with genkernel,build kernel with genkernel
2.restart computer
3.lockup
Actual Results:  
computer restarts runs through startup procedure,select kernel screen,screen goes blank
system locked up

Expected Results:  
should have booted into kernel and run the system

I think that it's not reading the initramfs for some reason

But in any case I recompiled & installed manually, with the same final result

[Comment 1 Geoff Madden 2011-03-24 09:20:43 UTC]

Created attachment 267053 [details]
emerge info for x86

[Comment 2 Geoff Madden 2011-03-24 09:33:55 UTC]

Created attachment 267055 [details]
configuration used to compilr kernel

[Comment 3 Geoff Madden 2011-03-27 08:31:25 UTC]

I have borrowed my .config from my x86_64 athlon and modified to suit the x86,
this compile was totally successful.I am using it now,What baffles me is itis almost identical to the configs I have used previously. Can some one point me to a use of a unix tool to compare the both configs ,in a (dumb)user readable manner it will be appreciated,as I would like to not make this mistake in the future.
Geoff

[Comment 4 Geoff Madden 2011-03-27 08:32:57 UTC]

Created attachment 267361 [details]
working config for 2.6.38

[Comment 5 EoD 2011-04-22 02:56:16 UTC]

A difference in your new config is the lack of "CONFIG_DRM_NOUVEAU_DEBUG=y".

Your report sounds very much like this one: https://bugs.freedesktop.org/show_bug.cgi?id=35374

[Comment 6 Geoff Madden 2011-04-23 03:28:33 UTC]

(In reply to comment #5)
> A difference in your new config is the lack of "CONFIG_DRM_NOUVEAU_DEBUG=y".
> 
> Your report sounds very much like this one:
> https://bugs.freedesktop.org/show_bug.cgi?id=35374

Yep that looks about right,thank the good programmer up above for the corrections in later kernels. I will try to commit to Memory the debug feature for the x86. But it's complicated this end as I have different gui cards for the each machine ATI for x86_64 and NV5M64 for the x86 both have AMD processors,but of different ages. I probably should just resort to one machine make life simpler HI.
Geoff