From: Theodore Tso <tytso@mit.edu>
To: Andreas Friedrich Berendsen <afberendsen@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: possible ext4 race situation freezing linux
Date: Tue, 24 Feb 2009 12:30:31 -0500 [thread overview]
Message-ID: <20090224173031.GE5482@mit.edu> (raw)
In-Reply-To: <1235495013.11758.37.camel@localhost.localdomain>
On Wed, Feb 25, 2009 at 06:03:33AM +1300, Andreas Friedrich Berendsen wrote:
> Tso & Eric,
>
> I'll try again to reproduce the error, but when the system freezes, I
> have the X interface running. And, indeed, I'm not familiar with the
> behaviour of sysreq. Which sysrq should I use when the problem happens?
> Will the system change to the text interface? If there are no disk
> activity (all leds are off), where the information will be recorded?
Well, given that you can reproduce it fairly reliably, can't you just
switch to a text console using before triggering your reproduction
case? You can use different VT consules, switching between them using
Alt-F2, Alt-F3, Alt-F2, Alt-F4, etc., instead of using different
terminal windows.
Depending on how badly system is wedged, it may not be possible to
record the information to disk. Usually what folks will do is use a
digital camera and record snapshots from the text console, or, if they
have a serial console set up, they can record output on another
machine. A serial console has the advantage that you can reliably
capture the entire sysrq output (you send a serial break character
instead of using the sysrq key) and it also works even if you have X
running. As such, it's the preferred method, but it's a bit of a pain
for most people to set up, and some modern laptops no longer have 8250
serial ports any more, so we make do with what we have.
Regards,
- Ted
next prev parent reply other threads:[~2009-02-24 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 12:22 possible ext4 race situation freezing linux Andreas Friedrich Berendsen
2009-02-24 14:17 ` Theodore Tso
2009-02-24 15:38 ` Eric Sandeen
2009-02-24 17:03 ` Andreas Friedrich Berendsen
2009-02-24 17:30 ` Theodore Tso [this message]
2009-03-04 6:42 ` Andreas Friedrich Berendsen
2009-03-04 6:56 ` Eric Sandeen
2009-03-04 8:03 ` Andreas Friedrich Berendsen
2009-03-06 19:21 ` Andreas Friedrich Berendsen
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=20090224173031.GE5482@mit.edu \
--to=tytso@mit.edu \
--cc=afberendsen@gmail.com \
--cc=linux-ext4@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).