All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Soeren Sonnenburg <reiserfs@nn7.de>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: reiserfs b0rken on 2.4.22-pre4-ben0 on powerpc ?
Date: 12 Jul 2003 15:34:08 -0400	[thread overview]
Message-ID: <1058038447.13317.102.camel@tiny.suse.com> (raw)
In-Reply-To: <1058010165.17888.8.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 485 bytes --]

On Sat, 2003-07-12 at 07:42, Soeren Sonnenburg wrote:
> Hi.
> 
> I tried to mount a reiserfs partition (which is connected via firewire
> or usb mass storage) and while it mounts ok with 2.4.21-ben2 it hangs
> while mounting on 2.4.22-pre4-ben0.
> 
> I guess something is broken there... I can get into the kernel debugger
> xmon and supply you with a backtrace shot taken with some digital
> camera... if that helps.

Please try this (which is in -pre5 and not related to reiserfs)



[-- Attachment #2: io-stalls-11-inc.diff --]
[-- Type: text/plain, Size: 455 bytes --]

===== drivers/block/ll_rw_blk.c 1.46 vs edited =====
--- 1.46/drivers/block/ll_rw_blk.c	Fri Jul  4 13:35:08 2003
+++ edited/drivers/block/ll_rw_blk.c	Fri Jul 11 08:30:54 2003
@@ -618,7 +618,7 @@
 	do {
 		set_current_state(TASK_UNINTERRUPTIBLE);
 		spin_lock_irq(&io_request_lock);
-		if (blk_oversized_queue(q)) {
+		if (blk_oversized_queue(q) || q->rq.count == 0) {
 			__generic_unplug_device(q);
 			spin_unlock_irq(&io_request_lock);
 			schedule();

  parent reply	other threads:[~2003-07-12 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 11:42 reiserfs b0rken on 2.4.22-pre4-ben0 on powerpc ? Soeren Sonnenburg
2003-07-12 12:52 ` Dieter Nützel
2003-07-12 14:43   ` Soeren Sonnenburg
2003-07-12 19:34 ` Chris Mason [this message]
2003-07-13 12:43   ` Soeren Sonnenburg

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=1058038447.13317.102.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=reiserfs-list@namesys.com \
    --cc=reiserfs@nn7.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.