From: Mattia Dongili <malattia@linux.it>
To: Chris Boot <bootc@bootc.net>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Reiser4 lockups (no oops)
Date: Thu, 20 Oct 2005 20:37:24 +0200 [thread overview]
Message-ID: <20051020183724.GA3999@inferi.kami.home> (raw)
In-Reply-To: <20051020163425.z7wygjyir8lcw0gk@horde.fusednetworks.co.uk>
On Thu, Oct 20, 2005 at 04:34:25PM +0100, 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).
aah! nice, those also fix the apt-get freeze I've been having from some
mm kernels ago.
I also managed to get the trace of apt-get freezing by means of Sysrq+P
but I stupidly forgot the fs was readonly so I didn't dump dmesg :P
I can easily reproduce it if anyone is interested.
> I see there's now a reiser4-fix-livelock-2.patch, anybody know the
> differences?
don't know, I'd try the -2 patches also, they seem a different version
of the same fix/cleanup.
--
mattia
:wq!
prev parent reply other threads:[~2005-10-20 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 17:08 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
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 [this message]
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=20051020183724.GA3999@inferi.kami.home \
--to=malattia@linux.it \
--cc=axboe@suse.de \
--cc=bootc@bootc.net \
--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
all inboxes | Powered by JetHome®