From: Jens Axboe <axboe@suse.de>
To: A Guy Called Tyketto <tyketto@wizard.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'eject' process stuck in "D" state
Date: Thu, 20 Dec 2001 13:28:05 +0100 [thread overview]
Message-ID: <20011220132805.D710@suse.de> (raw)
In-Reply-To: <20011220111249.GA15692@wizard.com> <20011220122325.A710@suse.de> <20011220113654.GA1271@wizard.com> <20011220123904.B710@suse.de> <20011220120750.GA1429@wizard.com> <20011220131116.C710@suse.de> <20011220122414.GA507@wizard.com>
In-Reply-To: <20011220122414.GA507@wizard.com>
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
On Thu, Dec 20 2001, A Guy Called Tyketto wrote:
> Just getting to that. as I brought down the box, I got some errors on
> /dev/tty1, which are the same from dmesg. 'ere ya go.
Ah, please try this patch.
--
Jens Axboe
[-- Attachment #2: ide-cd-block-pc-1 --]
[-- Type: text/plain, Size: 570 bytes --]
diff -ur -X exclude /opt/kernel/linux-2.5.1/drivers/ide/ide-cd.c linux/drivers/ide/ide-cd.c
--- /opt/kernel/linux-2.5.1/drivers/ide/ide-cd.c Sat Dec 8 23:02:47 2001
+++ linux/drivers/ide/ide-cd.c Thu Dec 20 07:25:26 2001
@@ -594,7 +594,7 @@
cdrom_end_request (1, drive);
*startstop = ide_error (drive, "request sense failure", stat);
return 1;
- } else if (rq->flags & REQ_PC) {
+ } else if (rq->flags & (REQ_PC | REQ_BLOCK_PC)) {
/* All other functions, except for READ. */
struct completion *wait = NULL;
pc = (struct packet_command *) rq->special;
next prev parent reply other threads:[~2001-12-20 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 11:12 'eject' process stuck in "D" state A Guy Called Tyketto
2001-12-20 11:23 ` Jens Axboe
2001-12-20 11:36 ` A Guy Called Tyketto
2001-12-20 11:39 ` Jens Axboe
2001-12-20 12:07 ` A Guy Called Tyketto
2001-12-20 12:11 ` Jens Axboe
2001-12-20 12:24 ` A Guy Called Tyketto
2001-12-20 12:28 ` Jens Axboe [this message]
2001-12-21 1:54 ` A Guy Called Tyketto
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=20011220132805.D710@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tyketto@wizard.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