From: Jens Axboe <axboe@suse.de>
To: Fabio Coatti <cova@ferrara.linux.it>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok
Date: Mon, 31 Jan 2005 09:00:22 +0100 [thread overview]
Message-ID: <20050131080021.GA9446@suse.de> (raw)
In-Reply-To: <200501310034.32005.cova@ferrara.linux.it>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
On Mon, Jan 31 2005, Fabio Coatti wrote:
> I'm seeing a problem with latest mm releases; with 2.6.11-rc1,2-mmX every time
> I fire up k3b, it get stuck here: (last line, previous lines just for
> documentation :) )
>
> open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 11
> ioctl(11, CDROM_SEND_PACKET, 0xbfffc4e0) = 0
> close(11) = 0
> open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 11
> ioctl(11, CDROM_SEND_PACKET, 0xbfffc590) = -1 EIO (Input/output error)
> close(11) = 0
> open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 11
> ioctl(11, CDROM_SEND_PACKET, 0xbfffc4e0) = 0
> ioctl(11, CDROM_SEND_PACKET, 0xbfffc4e0) = 0
> close(11) = 0
> open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 11
> ioctl(11, CDROM_GET_CAPABILITY or SNDRV_SEQ_IOCTL_UNSUBSCRIBE_PORT,
> 0x7fffffff) = 3735535
> close(11) = 0
> lstat64("/dev", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=30220, ...}) = 0
> lstat64("/dev/sr1", {st_mode=S_IFBLK|0600, st_rdev=makedev(11, 1), ...}) = 0
> open("/dev/sr1", O_RDONLY|O_NONBLOCK) = 11
> fstat64(11, {st_mode=S_IFBLK|0600, st_rdev=makedev(11, 1), ...}) = 0
> ioctl(11, CDROM_SEND_PACKET, 0xbfffd740) = 0
> close(11) = 0
> open("/dev/sr1", O_RDONLY|O_NONBLOCK) = 11
> fstat64(11, {st_mode=S_IFBLK|0600, st_rdev=makedev(11, 1), ...}) = 0
> ioctl(11, CDROMAUDIOBUFSIZ or SCSI_IOCTL_GET_IDLUN, 0xbfffd7e8) = 0
> ioctl(11, SCSI_IOCTL_GET_BUS_NUMBER, 0xbfffd8a4) = 0
> close(11) = 0
> open("/dev/sr1", O_RDONLY|O_NONBLOCK) = 11
> ioctl(11, CDROM_SEND_PACKET, 0xbfffd7d0) = 0
> ioctl(11, CDROM_SEND_PACKET
>
> At this point k3b is stuck in D stat, needs reboot.
The most likely suspect is the REQ_BLOCK_PC scsi changes. Can you try
2.6.11-rc2-mm1 with bk-scsi backed out? (attached)
--
Jens Axboe
[-- Attachment #2: bk-scsi-rc-fixes.patch.bz2 --]
[-- Type: application/x-bunzip2, Size: 30881 bytes --]
next prev parent reply other threads:[~2005-01-31 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 23:34 2.6.11-rc[1,2]-mmX scsi cdrom problem, 2.6.10-mm2 ok Fabio Coatti
2005-01-31 8:00 ` Jens Axboe [this message]
2005-01-31 10:08 ` Fabio Coatti
2005-01-31 11:05 ` Jens Axboe
2005-01-31 11:49 ` Douglas Gilbert
2005-01-31 11:49 ` Jens Axboe
2005-01-31 13:09 ` Douglas Gilbert
2005-01-31 13:53 ` Jens Axboe
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=20050131080021.GA9446@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=cova@ferrara.linux.it \
--cc=linux-kernel@vger.kernel.org \
/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