linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: marcelo@conectiva.com.br, ia6432@inbox.ru, green@namesys.com,
	linux-kernel@vger.kernel.org, andrea@suse.de
Subject: Re: 2.4.22-pre3 and reiserfs boot problem
Date: 11 Jul 2003 09:48:02 -0400	[thread overview]
Message-ID: <1057931282.13318.39.camel@tiny.suse.com> (raw)
In-Reply-To: <20030711152738.5b26fb4c.skraw@ithnet.com>

On Fri, 2003-07-11 at 09:27, Stephan von Krawczynski wrote:
>  
> > My first guess is that blk_oversized_queue is false but there aren't any
> > requests left.  That will pretty much spin in __get_request_wait with
> > irqs off, which sounds similar to what he's hitting.
> 
> Why is it I am only seeing it on a big device of 320 GB? Even 60GB mount
> without problems...

Honestly not sure.  I could make a better guess if you got a stack trace
with nmi_watchdog on, so we could see which part of the reiserfs mount
process was causing problems.

The bug would be easier to hit with smaller blocksizes, I'm running
tests now with ext and 1k blocksizes.

-chris



  reply	other threads:[~2003-07-11 13:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E19ae9K-000Nas-00.ia6432-inbox-ru@f7.mail.ru>
2003-07-10 17:12 ` 2.4.22-pre3 and reiserfs boot problem Stephan von Krawczynski
2003-07-10 18:01   ` Marcelo Tosatti
2003-07-11 13:15     ` Chris Mason
2003-07-11 13:27       ` Stephan von Krawczynski
2003-07-11 13:48         ` Chris Mason [this message]
2003-07-11 13:38       ` Stephan von Krawczynski
2003-07-11 13:51         ` Chris Mason
2003-07-11 15:15         ` Marcelo Tosatti
2003-07-10 15:49 "Peter Lojkin" 
2003-07-10 16:06 ` Stephan von Krawczynski
2003-07-10 17:55   ` Marcelo Tosatti
2003-07-10 17:57     ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2003-07-10 14:20 Carl-Daniel Hailfinger
2003-07-10 14:38 ` Stephan von Krawczynski
2003-07-10 14:44   ` Carl-Daniel Hailfinger
2003-07-10 15:12     ` Stephan von Krawczynski
2003-07-10 15:30 ` Anders Karlsson
2003-07-10 15:39   ` Carl-Daniel Hailfinger
2003-07-10 19:06     ` Anders Karlsson
2003-07-06 16:34 Stephan von Krawczynski
2003-07-06 18:13 ` Chris Mason
2003-07-06 21:24   ` Stephan von Krawczynski
2003-07-07 10:06   ` Stephan von Krawczynski
2003-07-09 12:01   ` Stephan von Krawczynski
2003-07-09 13:36     ` Chris Mason
2003-07-09 13:48       ` Oleg Drokin
2003-07-09 13:58         ` Stephan von Krawczynski
2003-07-09 14:11           ` Oleg Drokin
2003-07-09 14:25             ` Stephan von Krawczynski
2003-07-09 17:18               ` Marcelo Tosatti
2003-07-10 11:21                 ` Stephan von Krawczynski
2003-07-10 11:54                   ` Marcelo Tosatti
2003-07-10 12:20                     ` Stephan von Krawczynski
2003-07-10 12:00                 ` Stephan von Krawczynski
     [not found]         ` <20030709154015.GJ150921@niksula.cs.hut.fi>
2003-07-09 16:36           ` Stephan von Krawczynski
2003-07-09 14:01     ` Vincent Touquet
2003-07-09 14:20       ` Stephan von Krawczynski

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=1057931282.13318.39.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=andrea@suse.de \
    --cc=green@namesys.com \
    --cc=ia6432@inbox.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=skraw@ithnet.com \
    /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;
as well as URLs for NNTP newsgroup(s).