From: Christoph Hellwig <hch@infradead.org>
To: Marek Habersack <grendel@caudium.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS problems (hard lockup and oops on startup) with 2.5.5{6,7}
Date: Wed, 15 Jan 2003 20:21:34 +0000 [thread overview]
Message-ID: <20030115202134.A25143@infradead.org> (raw)
In-Reply-To: <20030114175528.GA1213@thanes.org>; from grendel@caudium.net on Tue, Jan 14, 2003 at 06:55:28PM +0100
On Tue, Jan 14, 2003 at 06:55:28PM +0100, Marek Habersack wrote:
> Hello,
>
> The kernel 2.5.56 seems to have changed something that affected the XFS
> code as I'm getting hit by one (and possibly two) bugs related to it now.
> What happens is that the machine suddenly freezes (running Debian/Sid -
> XFree 4.2.1, glibc 2.3.1, gnome2 - nothing out of ordinary) so that SysRq
> keys don't have any effect (but Numlock still toggles the led on the
> keyboard), machine is inaccessible from the net and the only cure is hard
> reboot. Nothing gets logged on the freeze and on reboot when XFS attempts to
> check the first filesystem the kernel oopses with Oops code 0002, in the
> interrupt handler. Nothing gets logged, of course, so I can't provide the
> full backtrace right now - I'll try to get it logged through the serial console
> if it happens again with 2.5.58. I have copied some values by hand from the
> screen (until I lost patience... :)):
>
> Unable to handle kernel paging request at virtual address 000500074
> printing EIP
Hmm, that's really no much info. And there weren't any XFS changes from
2.5.52 to 2.5.58..
next prev parent reply other threads:[~2003-01-15 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 17:55 XFS problems (hard lockup and oops on startup) with 2.5.5{6,7} Marek Habersack
2003-01-15 20:21 ` Christoph Hellwig [this message]
2003-01-15 21:59 ` Marek Habersack
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=20030115202134.A25143@infradead.org \
--to=hch@infradead.org \
--cc=grendel@caudium.net \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).