Message-ID: <20051020163425.z7wygjyir8lcw0gk@horde.fusednetworks.co.uk>
Date: Thu, 20 Oct 2005 16:34:25 +0100
From: Chris Boot <bootc@bootc.net>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiser4 lockups (no oops)
References: <43567D80.3050304@bootc.net> <20051020131815.GI2811@suse.de>
In-Reply-To: <20051020131815.GI2811@suse.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1038
Lines: 28

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 see there's now a reiser4-fix-livelock-2.patch, anybody know the 
differences?

Chris

-- 
Chris Boot
bootc@bootc.net
http://www.bootc.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/