From: Chris Mason <mason@suse.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: Adam Nielsen <a.nielsen@optushome.com.au>, reiserfs-list@namesys.com
Subject: Re: BUG: Replaying ReiserFS log causes hard lockup
Date: Thu, 25 Mar 2004 07:54:22 -0500 [thread overview]
Message-ID: <1080219262.14742.146.camel@watt.suse.com> (raw)
In-Reply-To: <1080213348.1976.277.camel@tribesman.namesys.com>
On Thu, 2004-03-25 at 06:15, Vladimir Saveliev wrote:
> Hello
>
> On Thu, 2004-03-25 at 13:48, Adam Nielsen wrote:
> > Hi,
> >
> > My apologies if this is the wrong place to send a report like this, but
> > I couldn't find anywhere more suitable!
> >
> > I have just come across a rather annoying bug, which seems to be most
> > likely located in ReiserFS as my computer now locks up while
> > booting a stock 2.6.3 kernel almost immediately after displaying this:
> >
> > found reiserfs format "3.6" with standard journal
> > Reiserfs journal params: device sda1, size 8192, journal first block 18,
> > max trans len 1024, max batch 900, max commit age 30, max trans age 30
> > reiserfs: checking transaction log (sda1) for (sda1)
> >
Please compile the kernel with sysrq support, and try to do a sysrq-p
when things are locked. If there kernel is completely frozen, you can
turn on the nmi watchdog, which should trigger an oops to tell us where
things are broken. You can get more details about both of these from
the Documentation directory in the kernel source
Documentation/nmi_watchdog.txt
Documentation/sysrq.txt
-chris
next prev parent reply other threads:[~2004-03-25 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 10:48 BUG: Replaying ReiserFS log causes hard lockup Adam Nielsen
2004-03-25 11:15 ` Vladimir Saveliev
2004-03-25 12:14 ` Adam Nielsen
2004-03-25 12:55 ` Vladimir Saveliev
2004-03-25 12:54 ` Chris Mason [this message]
2004-03-26 12:01 ` Adam Nielsen
2004-03-26 12:34 ` Adam Nielsen
2004-03-26 15:46 ` Jeff Mahoney
2004-03-26 23:06 ` Adam Nielsen
2004-03-25 18:51 ` Matthias Andree
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=1080219262.14742.146.camel@watt.suse.com \
--to=mason@suse.com \
--cc=a.nielsen@optushome.com.au \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.