Message-ID: <3F0D761E.2050702@gmx.net>
Date: Thu, 10 Jul 2003 16:20:14 +0200
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Stephan von Krawczynski <skraw@ithnet.com>
CC: Marcelo Tosatti <marcelo@conectiva.com.br>,
       Oleg Drokin <green@namesys.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.22-pre3 and reiserfs boot problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1078
Lines: 31

Having read the whole thread, I came up with a few ideas.

The following patches in -pre3 could perhaps have to do something with
your problems:
  o (resend) collected semaphore fixes and semtimedop
  o Fix potential IO hangs and increase interactiveness during heavy IO
  o fix false sharing of mm info
  o fix up semops and return, allow timedop
  o mremap VM_LOCKED move_vma
  o remove io_apic_modify - this doesnt work on some APICs
  o small setup-pci cleanups

Since your hangs are not even traceable with SysRq, please try to boot
with nmi_watchdog=1 and if that doesn't work (dmesg will complain)
nmi_watchdog=2. About 15 seconds after the hang your box should print a
backtrace.

As a last resort you could mount the fs from UML.

I suggest you try the nmi_watchdog thing first.


Carl-Daniel
-- 
http://www.hailfinger.org/

-
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/