linux-kernel - Re: Kernel Oops with 2.6.21.1 on an AMD K7 machine

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 May 2007 15:54:26 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Uwe Bugla" <uwe.bugla@....de>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: Kernel Oops with 2.6.21.1 on an AMD K7 machine

On Tue, 22 May 2007 00:28:57 +0200
"Uwe Bugla" <uwe.bugla@....de> wrote:

> kernel 2.6.21.1 makes my machine Oops about 20 seconds after KDE 3,5 is brought up showing its graphical login (kdm):

We're completely blind unless we can see that oops info.  If it reached
/var/log/messages then please send it.

If it didn't please set up netconsole (Documentation/networking/netconsole.txt)

If for some reason that isn't possible then you couldry switching to
the vga concole (alt-ctl-F1) before the ooops and see if the output
is visible on the VGA screen.  If it is there, a digital photo will suit
(you can email it to me and I can stick it on a server somewhere if
you like).  The last option is to write the oops info down with a
pencil and type it in again, but that's painful (all the hex addresses
in the stack backtrace can be omitted)

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/