From: Christian Kujau <lists@nerdbynature.de>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Hard lockup with kernel 2.6.25 and 2.6.25.1
Date: Sun, 4 May 2008 01:05:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.10.0805040104100.5391@sheep.housecafe.de> (raw)
In-Reply-To: <20080504005209.13af2b2c@highlander.home.lan>
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.
next prev parent reply other threads:[~2008-05-03 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 22:52 Malte Schröder
2008-05-03 23:05 ` Christian Kujau [this message]
2008-05-04 9:54 ` Malte Schröder
2008-05-03 23:18 ` Greg KH
2008-05-04 9:51 ` Malte Schröder
2008-05-04 11:49 ` Malte Schröder
2008-05-04 19:56 ` Jan Engelhardt
2008-05-04 20:22 ` Malte Schröder
2008-05-12 13:28 ` Malte Schröder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.0805040104100.5391@sheep.housecafe.de \
--to=lists@nerdbynature.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maltesch@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®