Bug 20931 – System hard locks when entering X with gentoo-sources-2.4.20-r5

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Chris Gianelloni (RETIRED) 2003-05-13 09:54:32 UTC]

The system does not respond at all.  I cannot ping/ssh from another machine. 
This only occurs with the gentoo-sources-2.4.20-r5 kernel.  This occurs with the
Nvidia drivers, or using the stock XFree driver.  It occurs using the NVidia AGP
driver, or the kernel AGP.  There is of course nothing in the system logs to
indicate a problem.  I am attaching my XF86Config and .config for the kernel.  I
have no problems at all running under 2.4.20-r2.

[Comment 1 Chris Gianelloni (RETIRED) 2003-05-13 09:55:46 UTC]

Created attachment 11896 [details]
XFree configuration

[Comment 2 Chris Gianelloni (RETIRED) 2003-05-13 09:56:59 UTC]

Created attachment 11897 [details]
Kernel configuration

[Comment 3 Chris Gianelloni (RETIRED) 2003-05-13 09:59:31 UTC]

I failed to mention that I am running the Nvidia driver version 4349.

[Comment 4 Fred Van Andel (RETIRED) 2003-05-13 16:27:03 UTC]

Some grsecurity options cause problems with X, but I forget which ones off hand.

Start by trying a kernel with grsecurity disabled and see if it works.

[Comment 5 Chris Gianelloni (RETIRED) 2003-05-13 17:02:16 UTC]

Turning off grsecurity has no effect.  I have already tested this, not to mention my grsecurity configuration works perfectly under 2.4.20-r2 with the same configuration.  The two options you are thinking of are CONFIG_GRKERNSEC_PAX_NOEXEC and CONFIG_GRKERNSEC_IO, neither of which I have enabled.

I compiled this kernel using my working .config from 2.4.20-r2 and make oldconfig.  I enabled no new options other than ipsec.

[Comment 6 Chris Gianelloni (RETIRED) 2003-05-14 14:39:45 UTC]

OK.  The problem is actually with XFree86 4.3 and the CursorShadow option of the NVidia driver.  Apparently, the option no longer should be used under version 4.3, I would guess due to the new X cursor support.

Please close this bug.

[Comment 7 Chris Gianelloni (RETIRED) 2003-05-14 15:23:22 UTC]

OK.  Keep this open.  It appears I was wrong about the cause.  This seems to happen only during load, which is why I did not notice it before.

Also, I should mention that I am using the usagi and aavm USE flags.  Could this be a bug in one of the patches not being aavm compatable?  I know the ck-sources use aavm as their default.

[Comment 8 Chris Gianelloni (RETIRED) 2003-05-15 09:48:21 UTC]

Well, I tried recompiling without aavm and using the default rmap.  I still get hard lockups under X when I put any load on the system.

[Comment 9 Brian Jackson (RETIRED) 2003-09-24 00:54:44 UTC]

does this still happen? does this happen if you don't use nvidia drivers? what about different kernels?

[Comment 10 Chris Gianelloni (RETIRED) 2003-09-24 07:31:19 UTC]

Yes, it still happened with -r5.  It no longer happens with -r6 or -r7, so I would say we'll just leave this resolved.