From: "evilninja@gmx.net" <evilninja@gmx.net>
To: "Konstantin Münning" <konstantin@muenning.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser3 bug in 2.6.11.11
Date: Thu, 17 Nov 2005 00:36:59 +0100 [thread overview]
Message-ID: <437BC29B.3060704@gmx.net> (raw)
In-Reply-To: <43791A03.9030305@muenning.com>
Konstantin Münning schrieb:
> init started and first system startup messages appeared. But then a
> bunch of oopses appeared fast so I was not able to find which part of
> the kernel was causing the first error and then the keyboard stops
> responding so I couldn't scrollback. At that point only powering down
> was possible. I can't tell if it happens while fs was RO or when/after
> it was remounted RW. And as there was no network or disk access at that
> point recovering some information was not possible.
can you reproduce the oopses and redirect the errors/oops message to a
serial console or netconsole? does the error go away with a current
kernel? perhaps some reiserfs guru can decode them....
--
BOFH excuse #293:
You must've hit the wrong any key.
next prev parent reply other threads:[~2005-11-16 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 23:13 Reiser3 bug in 2.6.11.11 Konstantin Münning
2005-11-16 23:36 ` evilninja [this message]
2005-11-17 10:19 ` Konstantin Münning
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=437BC29B.3060704@gmx.net \
--to=evilninja@gmx.net \
--cc=konstantin@muenning.com \
--cc=reiserfs-list@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.