From: Chris Boot <bootc@bootc.net>
To: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Reiser4 lockups (no oops)
Date: Thu, 20 Oct 2005 17:27:23 +0100 [thread overview]
Message-ID: <4357C56B.30600@bootc.net> (raw)
In-Reply-To: <20051020162112.GT2811@suse.de>
Jens Axboe wrote:
>On Thu, Oct 20 2005, Chris Boot wrote:
>
>
>>Quoting Jens Axboe <axboe@suse.de>:
>>
>>
>>
>>>On Wed, Oct 19 2005, Chris Boot wrote:
>>>
>>>
>>>>I don't get any OOPSes or BUGs or anything, not on my screen nor on my
>>>>serial console (although I'm not sure I have this working right--I only
>>>>seem to get kernel boot messages). Machine replies to pings but I can't
>>>>
>>>>
>>>Easy fix for that is probably to kill klogd on the machine. Test with eg
>>>loading/unloading of loop, that prints a message when it loads.
>>>
>>>
>>I'd love to, but the machine is locked solid and won't turn on the
>>display or switch TTYs or anything. Anyway, I've applied
>>reiser4-fix-livelock.patch from ftp.namesys.org and so far so good
>>(over night).
>>
>>
>
>I mean _before_ the crash, to make sure the messages get out :-)
>
>
Oh! Hehe, now I get you. However, I'm using metalog for logging, and
modprobe loop doesn't give any output. What's interesting is that serial
console logging dies long before metalog is started, just after my swap
is added in fact. I'm using Gentoo.
Any ideas?
Cheers,
Chris
--
Chris Boot
bootc@bootc.net
http://www.bootc.net/
next prev parent reply other threads:[~2005-10-20 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 17:08 Reiser4 lockups (no oops) Chris Boot
2005-10-20 13:18 ` Jens Axboe
2005-10-20 15:34 ` Chris Boot
2005-10-20 16:21 ` Jens Axboe
2005-10-20 16:27 ` Chris Boot [this message]
2005-10-20 17:52 ` Nikita Danilov
2005-10-20 18:44 ` Chris Boot
2005-10-20 21:02 ` Nikita Danilov
2005-10-20 22:05 ` Chris Boot
2005-10-20 18:37 ` Mattia Dongili
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=4357C56B.30600@bootc.net \
--to=bootc@bootc.net \
--cc=axboe@suse.de \
--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