linux-kernel - Re: Hard lockup with kernel 2.6.25 and 2.6.25.1

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]

Message-ID: <alpine.DEB.1.10.0805040104100.5391@sheep.housecafe.de>
Date:	Sun, 4 May 2008 01:05:51 +0200 (CEST)
From:	Christian Kujau <lists@...dbynature.de>
To:	Malte Schröder <maltesch@....de>
cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Hard lockup with kernel 2.6.25 and 2.6.25.1

On Sun, 4 May 2008, Malte Schröder wrote:
> This incident happened only a few hours after booting the new kernel,
> SysRq-keys didn't work. 2.6.24.5 has been running fine.

What's with the I/O errors - did they show up in 2.6.24.5? If not, what 
has changed in your .config with .25.1?

C.
-- 
BOFH excuse #202:

kernel panic: write-only-memory (/dev/wom0) capacity exceeded.
--
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/