Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 200955

Summary: frequent crashes with actual ~amd64 hardened system
Product: Gentoo Linux Reporter: Thomas Sachau <tommy>
Component: HardenedAssignee: The Gentoo Linux Hardened Team <hardened>
Status: RESOLVED WONTFIX    
Severity: major CC: gengor, kfm
Priority: High    
Version: 2007.0   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: .config

Description Thomas Sachau gentoo-dev 2007-12-01 21:07:50 UTC
As told in answer #32 in bug 197521, i open a new bug for my problem. I copy my description from the other bugreport:

My problem is, i cannot give much information and i am also not able to
reproduce the crashes. But for me hardened-sources-.26.23 and
hardened-sources-2.6.23-r1 do somehow crash. After that, i cant do any keyboard
input, but still use my mouse and do some things on the desktop. But if i try
to kill my desktop, the screens goes black and i cant do something any more. I
can login over ssh and do some things, but e.g. one time i tried to compile
something and got an <defunct> emerge process. This happens with running
X+e17(cvs) and also without running X.
I do not get any kernel oops or any other message about the crash, only the
cursor does not blink any more (if i am on the konsole while the crash
happens).

This is on a hardened/amd64/multilib profile with ~amd64 keyword.

additional: tested hardened-sources-2.6.23-r2 today and had a crash again, this time nothing did react, no keyboard response, no network activity (ssh or similar not working any more).

Also had a crash with hardened-sources-2.6.22-r7, but in this case i was able to ssh in and it did run for a couple of day so its at least the more stable version for me.
Comment 1 Christian Heim (RETIRED) gentoo-dev 2007-12-27 15:24:47 UTC
You tried running memtest86 on your memory ? Seems more like a defective memory to me.
Comment 2 Christian Heim (RETIRED) gentoo-dev 2007-12-27 15:25:16 UTC
Oh, I'd also like to see the .config of your hardened-sources.
Comment 3 Thomas Sachau gentoo-dev 2007-12-27 21:13:01 UTC
Created attachment 139464 [details]
.config

did not try memtest so far, but will do it to exclude memory as a source
Comment 4 Thomas Sachau gentoo-dev 2007-12-28 20:50:19 UTC
2 hours memtest (4 complete test) and no error
Comment 5 Thomas Sachau gentoo-dev 2008-01-07 03:50:05 UTC
did some more tests:

compiled hardened-sources-2.6.23-r5 with gcc-3.4.6-vanilla => crash
compiled gentoo-sources-2.6.23-r5 with gcc-3.4.6 => crash

one interesting detail:
if this crash happens and network still exists, i can log into the machine using ssh. But once i try to emerge something, it stops at "preparing to unpack" and i get a defunct ebuild.sh.
Comment 6 Thomas Sachau gentoo-dev 2008-02-02 13:19:48 UTC
Seems like the crash i had without X could have some other reason, as i cannot reproduce it and all crashes since then happend with X running.

This where so far up to xorg-server-1.4.0.90-r2
and also the stable version up to xorg-server-1.3.0.0-r4
Comment 7 Thomas Sachau gentoo-dev 2008-02-06 16:27:29 UTC
Ok, new crash, some new details:

-I did not have X running, so perhaps X could change the time until it happens, but not the bug itself. A "emerge -uDN world" was running before and finished before the cursor freezed and no more input was possible.
-I have a <defunct> java process (running freenet from freenetproject.org on 64bit-java).
-I can still ssh in and watch top or browse directorys.

And another strange point: Also no other keyboard input works, strg-alt-entf did sent a "reboot"-command to the os, also it only starts to shut down and nothing more happens (and no interactions are any more possible).
Comment 8 Thomas Sachau gentoo-dev 2008-03-10 02:10:23 UTC
Seems like the problem is solved with kernel-2.6.24.
Running latest gentoo-sources for over 2 weeks now without this crashes.

Imho the problem was the old bcm43xx driver or related to it.

As there is no more upstream development for this driver, i will mark this one as wontfix.