From: piotr@larroy.com (Pedro Larroy)
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [BUG] 2.6.9-rc2 scsi and elevator oops when I/O error
Date: Mon, 11 Oct 2004 17:24:14 +0200 [thread overview]
Message-ID: <20041011152414.GA5118@larroy.com> (raw)
In-Reply-To: <20041011050320.GA28703@larroy.com>
Another side problem I have observed about this:
Processes that call sync() get stuck into D state, for example shutdown.
--
Pedro Larroy Tovar | Linux & Network consultant | pedro%larroy.com
Las patentes de programación son nocivas para la innovación
http://proinnova.hispalinux.es/
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: piotr@larroy.com (Pedro Larroy)
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [BUG] 2.6.9-rc2 scsi and elevator oops when I/O error
Date: Mon, 11 Oct 2004 17:24:14 +0200 [thread overview]
Message-ID: <20041011152414.GA5118@larroy.com> (raw)
In-Reply-To: <20041011050320.GA28703@larroy.com>
Another side problem I have observed about this:
Processes that call sync() get stuck into D state, for example shutdown.
--
Pedro Larroy Tovar | Linux & Network consultant | pedro%larroy.com
Las patentes de programación son nocivas para la innovación
http://proinnova.hispalinux.es/
next prev parent reply other threads:[~2004-10-11 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 5:03 [BUG] 2.6.9-rc2 scsi and elevator oops when I/O error Pedro Larroy
2004-10-11 8:10 ` Nick Piggin
2004-10-11 9:50 ` Jens Axboe
2004-10-11 14:03 ` James Bottomley
2004-10-11 19:07 ` [linux-usb-devel] " Alan Stern
2004-10-11 19:07 ` Alan Stern
2004-10-11 15:12 ` Pedro Larroy
2004-10-11 15:24 ` Pedro Larroy [this message]
2004-10-11 15:24 ` Pedro Larroy
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=20041011152414.GA5118@larroy.com \
--to=piotr@larroy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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.