mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Pitt <martin@piware.de>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org, vitaly@namesys.com
Subject: Re: PROBLEM: 2.6.0-test1/2 reiserfsck journal replaying hangs
Date: Mon, 4 Aug 2003 15:22:11 +0200	[thread overview]
Message-ID: <20030804132207.GA29529@donald.balu5> (raw)
In-Reply-To: <20030804101628.GD3911@namesys.com>

Hi!

Am 2003-08-04 14:16 +0400 schrieb Oleg Drokin:
> Hello!
> 
> On Mon, Aug 04, 2003 at 12:13:12PM +0200, Martin Pitt wrote:
> 
> > > What was screen looking like at the hang time (can you capture it somehow?),
> > That's very difficult, no consoles are active at that time. There are
> > no error messages and no messages that don't appear with 2.4.x, apart
> > from the warnings about missing module stuff. I can photograph it if
> > you want.
> 
> Yeah, sure.

I did that. I will send you the screenshot per private mail for not
cluttering up the mailing list.

> > > can you press sysrq-T at the time of a hang and then send us the traces?
> > That's even more difficult, it produces several screenfulls of text
> > scrolling away very fast. I'd need a serial console for this purpose
> > but it will last a while to set this up since I don't have the
> > necessary hardware here. I could do it tomorrow.
> 
> Well, as I understand, you first press sysrq-T, then ^C, then thing boots and you can
> colled sysrq-t output from dmesg or boot logs.

It does not work that way. Both with 2.4.x and 2.6.0-test2, after
pressing sysrq-something you can only choose actions from the menu (i.
e. eventually reboot). Every key press is interpreted as magic key
menu selection, I do not even have to hold down alt+sysrq to choose
's'ync, 'b'oot and so on. There is no such thing as "e'x'it from this
menu". This may be regarded as another bug.

Syslog is not started at the point of root fs check, thus the dump is
not saved. I cannot call dmesg since after sysrq+t I'm stuck in the
emergency menu. So I booted normally (^C, ^D) and then did a sysrq+t,
rebooting and saving the previous syslog (boot messages and trace) in
kernmsg.txt. I do not think that it will be helpful since fsck has
finished at that time, but I attach it nevertheless.

Any other chance? I can also try other combinations (modular kernel,
no devfs, etc. but actually I like it the way it is).

Thanks!

Martin
-- 
Martin Pitt
home:  www.piware.de
eMail: martin@piware.de

Es gibt zwei Regeln für Erfolg im Leben:
1. Erzähle den Leuten nie alles, was Du weißt.

  reply	other threads:[~2003-08-04 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03 10:23 Martin Pitt
2003-08-04  7:54 ` Oleg Drokin
2003-08-04  8:43   ` Martin Pitt
2003-08-04  9:10     ` Vitaly Fertman
2003-08-04  9:17     ` Oleg Drokin
2003-08-04 10:13       ` Martin Pitt
2003-08-04 10:16         ` Oleg Drokin
2003-08-04 13:22           ` Martin Pitt [this message]
2003-08-04 13:48             ` Oleg Drokin

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=20030804132207.GA29529@donald.balu5 \
    --to=martin@piware.de \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vitaly@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 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®