public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Boot <bootc@bootc.net>
To: linux-kernel@vger.kernel.org
Subject: Reiser4 lockups (no oops)
Date: Wed, 19 Oct 2005 18:08:16 +0100	[thread overview]
Message-ID: <43567D80.3050304@bootc.net> (raw)

Hi all,

I've been using Reiser4 on a couple of filesystems to give it a shot, 
and although it has been working fine for a while I've noticed that 
newer versions of the patch cause lockups on my machine. It all started 
when I upgraded to the reiser4-for-2.6.13-1.patch.gz from 
reiser4-for-2.6.12-3.patch.gz, which works fine. I've also tested a 
vanilla 2.6.14-rc4-mm1 which has the same symptoms.

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 
SSH, and the watchdog doesn't kick in (hangcheck or w83627hf_wdt) so I 
only notice it's crashed when I wake up in the morning. The crashes seem 
most lilkely to occur in periods of heavy I/O -- large Samba file 
transfers or updatdb do the trick.

Anything I can do to try and track down the issue?

Thanks,
Chris

-- 
Chris Boot
bootc@bootc.net
http://www.bootc.net/


             reply	other threads:[~2005-10-19 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 17:08 Chris Boot [this message]
2005-10-20 13:18 ` Reiser4 lockups (no oops) 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

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=43567D80.3050304@bootc.net \
    --to=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