From: "Gustavo Guillermo Pérez" <gustavo@compunauta.com>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: SCSI trow USB-STORAGE or SBP2 Debug for buggy device Kernels 2.6.X
Date: Tue, 8 Aug 2006 23:03:35 -0500 [thread overview]
Message-ID: <200608082303.35668.gustavo@compunauta.com> (raw)
In-Reply-To: <20060730160808.d67f71bb.akpm@osdl.org>
El Domingo, 30 de Julio de 2006 18:08, escribió:
> If this is still happening in 2.6.18-rc3 could you please raise a report at
> bugzilla.kernel.org?
It does not happen, Thanks.
Sorry for the late testing.
> Thanks.
>
>
> On Mon, 24 Apr 2006 10:29:14 -0500
>
> Gustavo Guillermo Pérez <gustavo@compunauta.com> wrote:
> > Hello, list, I've tried to figure out why my external DVDRW Device has a
> > problem using UDF, SCSI subsystem reports "Device not ready" when burning
> > with growisofs, the media is being written perfect, no defective media or
> > sector errors ater burning. I've tried diferent DVDRW and I discover that
> > only pioneer has this issue DVR106D /107D/108D/109D/110D (I have a lot of
> > them) but only trow usb-storage or sbp2 device converters I have this
> > error, and with this error UDF system show bad sectors, there is not bad
> > sectors, and it happens only when writing big files about more than 1 or
> > 2MB, not 100Kbyte files or many small files, Then is cause I guess the
> > drive need some time to get ready again and I guess scsi system can
> > resend the
> > command?!?!?!?.
> >
> > Then going more far away, I see there is a black list on SCSI system,
> > scsi_devinfo.c that has a list of vendor and product identifications.
> > I've tried to add this line:
> > {"PIONEER", "DVD-RW DVR-106D", NULL, BLIST_RETRY_HWERROR},
> >
> > With no effects, Cause this error looks like not hardware error, is just
> > not ready.
> >
> > Then I have an Idea, what happen if on scsi_lib.c where resides the
> > faulty code:
> > if (!(req->flags & REQ_QUIET))
> > dev_printk(KERN_INFO,
> > &cmd->device->sdev_gendev,
> > "Device not ready.\n");
> > scsi_end_request(cmd, 0, this_count, 1);
> > return;
> > I change scsi_end_request(cmd, 0, this_count, 1);
> > by a comparison about vendor ID and Model
> > and then if is a buggy one executes scsi_requeue_command(q, cmd); instead
> > of scsi_end_request(cmd, 0, this_count, 1);
> >
> > Can I use this vars to deal only the same situation and not sata, nor
> > usb-card reader, etc. etc.?!?!?!??!?!?!?!?
> > &cmd->device->vendor
> > &cmd->device->model
> > &cmd->pid
> > &cmd->sc_magic
> >
> > How can I print it with prontk, I should use ?!?!?!
> > printk("Vendor: %s Model: %s Pid: %s Magic %s DevNotReady_Error\n",
> > &cmd->device->vendor,
> > &cmd->device->model,
> > &cmd->pid,
> > &cmd->sc_magic);
> >
> > This device seems to require more patient to get ready...
> >
> > this is my log USB-STORAGE generic adapter
> >
> > Apr 3 18:13:30 g kernel: usb 4-1: new full speed USB device using
> > ehci_hcd and address 2
> > Apr 3 18:13:30 g kernel: scsi2 : SCSI emulation for USB Mass Storage
> > devices Apr 3 18:13:35 g kernel: Vendor: PIONEER Model: DVD-RW
> > DVR-106D Rev: 1.08
> > Apr 3 18:13:35 g kernel: Type: CD-ROM
> > ANSI SCSI revision: 00
> > Apr 3 18:13:35 g kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw
> > xa/form2 cdda tray
> > Apr 3 18:13:35 g scsi.agent[14695]: cdrom
> > at
> > /devices/pci0000:00/0000:00:10.3/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0
> >:0 Apr 3 18:13:53 g kernel: cdrom: This disc doesn't have any tracks I
> > recognize!
> > Apr 3 18:14:42 g kernel: sr 2:0:0:0: Device not ready.
> > Apr 3 18:15:13 g last message repeated 21 times
> > Apr 3 18:16:14 g last message repeated 31 times
> > Apr 3 18:17:16 g last message repeated 31 times
> > Apr 3 18:18:17 g last message repeated 31 times
> > Apr 3 18:19:19 g last message repeated 31 times
> > Apr 3 18:20:20 g last message repeated 30 times
> > Apr 3 18:21:21 g last message repeated 28 times
> > Apr 3 18:22:22 g last message repeated 30 times
> > Apr 3 18:23:24 g last message repeated 31 times
> >
> > diferent USB-STORAGE+ieee1394:
> > Apr 7 23:28:54 g kernel: sbp2: $Rev: 1306 $ Ben Collins
> > <bcollins@debian.org> Apr 7 23:28:54 g kernel: scsi2 : SCSI emulation
> > for IEEE-1394 SBP-2 Devices Apr 7 23:28:55 g kernel: ieee1394: sbp2:
> > Logged into SBP-2 device Apr 7 23:28:55 g kernel: Vendor: PIONEER
> > Model: DVD-RW DVR-110D Rev: 1.37
> > Apr 7 23:28:55 g kernel: Type: CD-ROM
> > ANSI SCSI revision: 00
> > Apr 7 23:28:55 g kernel: sr1: scsi3-mmc drive: 1x/351x xa/form2 tray
> > Apr 7 23:28:55 g scsi.agent[9237]: cdrom
> > at
> > /devices/pci0000:00/0000:00:14.0/fw-host0/0050c50250004101/0050c502500041
> >01-0/h Apr 7 23:28:56 g fstab-sync[9271]: added mount point /media/cdrom
> > for /dev/sr1
> > Apr 7 23:28:56 g kernel: cdrom: This disc doesn't have any tracks I
> > recognize!
> > Apr 7 23:32:11 g kernel: sr 2:0:0:0: Device not ready.
> > Apr 7 23:32:42 g last message repeated 290 times
> > Apr 7 23:33:45 g last message repeated 182 times
> > Apr 7 23:34:46 g last message repeated 92 times
> > Apr 7 23:35:47 g last message repeated 87 times
> > Apr 7 23:36:48 g last message repeated 103 times
> > Apr 7 23:37:50 g last message repeated 128 times
> > Apr 7 23:38:51 g last message repeated 140 times
> > Apr 7 23:39:52 g last message repeated 157 times
> > Apr 7 23:40:06 g last message repeated 65 times
> >
> > SBP2 with another DVDR107
> > Oct 11 10:53:52 g kernel: sbp2: $Rev: 1219 $ Ben Collins
> > <bcollins@debian.org> Oct 11 10:53:52 g kernel: scsi0 : SCSI emulation
> > for IEEE-1394 SBP-2 Devices Oct 11 10:53:52 g net.agent[8231]: add event
> > not handled
> > Oct 11 10:53:53 g kernel: ieee1394: sbp2: Logged into SBP-2 device
> > Oct 11 10:53:53 g kernel: Vendor: PIONEER Model: DVD-RW DVR-107D
> > Rev: 1.21
> > Oct 11 10:53:53 g kernel: Type: CD-ROM
> > ANSI SCSI revision: 02
> > Oct 11 10:53:53 g kernel: sr0: scsi3-mmc drive: 62x/62x writer cd/rw
> > xa/form2 cdda tray
> > Oct 11 10:53:53 g scsi.agent[8285]: cdrom
> > at
> > /devices/pci0000:00/0000:00:14.0/fw-host0/0050c50250004101/0050c502500041
> >01-0/h Oct 11 10:56:21 g kernel: XFS mounting filesystem hda6
> > Oct 11 11:00:09 g kernel: Device sr0 not ready.
> > Oct 11 11:00:40 g last message repeated 145 times
> > Oct 11 11:01:41 g last message repeated 178 times
> > Oct 11 11:02:40 g last message repeated 174 times
> >
> >
> > any thougts?
> >
> > --
> > Gustavo Guillermo Pérez
> > Compunauta uLinux
> > www.compunauta.com
--
Gustavo Guillermo Pérez
Compunauta uLinux
www.compunauta.com
prev parent reply other threads:[~2006-08-09 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 15:29 SCSI trow USB-STORAGE or SBP2 Debug for buggy device Kernels 2.6.X Gustavo Guillermo Pérez
2006-04-24 18:38 ` James Bottomley
2006-04-24 21:30 ` Gustavo Guillermo Pérez
2006-04-24 22:02 ` James Bottomley
2006-04-24 22:12 ` Gustavo Guillermo Pérez
2006-04-25 6:09 ` Stefan Richter
2006-04-25 21:41 ` Gustavo Guillermo Pérez
2006-04-25 21:48 ` James Bottomley
2006-04-27 17:40 ` Gustavo Guillermo Pérez
2006-04-28 1:38 ` Gustavo Guillermo Pérez
[not found] ` <20060730160808.d67f71bb.akpm@osdl.org>
2006-08-09 4:03 ` Gustavo Guillermo Pérez [this message]
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=200608082303.35668.gustavo@compunauta.com \
--to=gustavo@compunauta.com \
--cc=akpm@osdl.org \
--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 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.