April 2001 - Packet Writing - openSUSE Mailing Lists

0.0.2j/2.4.4 report
by Morten Bo Johansen 04 May '01

04 May '01

With ide-scsi I had the exact same problem as with 2.4.4pre6 and 0.0.2i as reported in <20010423224639.A593(a)olafrye.dyndns.org> , i.e. a complete lockup of my system so a hard reset was neccesary and alas I am still not able to make serial logging work so I cannot provide a bug report, sorry. I then tried to disable ide-scsi and this time at least the lockup is avoided but I get these errors instead: Formatting track Writing UDF structures to disc 7200 (CEST)/-120 hdd: irq timeout: status=0xd0 { Busy } hdd: Atapi reset complete wait_cmd: Input/output error Command failed: 2a 00 00 00 00 00 00 00 20 00 00 00 - sense 08.00.00 Error writing packet 0 (ffffffff) Regards, Morten -- "Life is all memory, except for the one present moment that goes by you so quick you hardly catch it going." (Tennessee Williams)

2 6

hang with 0.0.2j & 2.4.4 using cdrwtool
by rsmith＠xs4all.nl 02 May '01

02 May '01

After installing 2.4.4 with the 0.02j patch, I ran into the following difficulties: ---------------------- cdrwtool output ---------------------------------- slacker:/home/rsmith/tmp/src/udf-cvs/udf/tools# ./cdrwtool -d /dev/sr0 -q using device /dev/sr0 768KB internal buffer setting write speed to 12x Settings for /dev/sr0: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/sr0. The disc is going to be blanked and formatted with one big track. All data on the device will be lost!! Press CTRL-C to cancel now. Initiating quick disc blank Disc capacity is 275008 blocks (550016KB/537MB) Formatting track ---------------------- cdrwtool output ---------------------------------- There was one more line of output, something like: ---------------------- cdrwtool output ---------------------------------- 7200 (EST) ---------------------- cdrwtool output ---------------------------------- But it scrolled off the screen before I could write it down, and I can't remember the precise message. At this point a lot of error messages appeared in the log file: --------------------- /var/log/syslog ----------------------------------- Apr 29 13:22:59 slacker kernel: hdc: empty DMA table? Apr 29 13:23:04 slacker kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 1, lun 0 0x2a 00 00 00 00 00 00 00 20 00 Apr 29 13:23:09 slacker kernel: hdc: irq timeout: status=0xd0 { Busy } Apr 29 13:23:09 slacker kernel: hdc: DMA disabled Apr 29 13:23:09 slacker kernel: hdc: ATAPI reset complete Apr 29 13:23:09 slacker kernel: hdc: irq timeout: status=0xd0 { Busy } Apr 29 13:23:09 slacker kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 1, lun 0 0x2a 00 00 00 00 00 00 00 20 00 Apr 29 13:23:09 slacker kernel: SCSI host 0 abort (pid 0) timed out - resetting Apr 29 13:23:09 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:10 slacker kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 1, lun 0 0x2a 00 00 00 00 00 00 00 20 00 Apr 29 13:23:10 slacker kernel: SCSI host 0 abort (pid 0) timed out - resetting Apr 29 13:23:10 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:10 slacker kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 1, lun 0 0x2a 00 00 00 00 00 00 00 20 00 Apr 29 13:23:10 slacker kernel: SCSI host 0 abort (pid 0) timed out - resetting Apr 29 13:23:10 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:12 slacker kernel: hdc: ATAPI reset complete Apr 29 13:23:12 slacker kernel: hdc: irq timeout: status=0xd0 { Busy } Apr 29 13:23:12 slacker kernel: hdc: status timeout: status=0xd0 { Busy } Apr 29 13:23:12 slacker kernel: hdc: drive not ready for command Apr 29 13:23:15 slacker kernel: hdc: ATAPI reset complete Apr 29 13:23:17 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:17 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:18 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:18 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:20 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:20 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:22 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:22 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:23 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:23 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:24 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:24 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:25 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:25 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:26 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:26 slacker kernel: SCSI bus is being reset for host 0 channel 0. Apr 29 13:23:27 slacker kernel: scsi0 : channel 0 target 1 lun 0 request sense f ailed, performing reset. Apr 29 13:23:27 slacker kernel: SCSI bus is being reset for host 0 channel 0. --------------------- /var/log/syslog ----------------------------------- At this point, the box seemed to have hung completely; all disk activity ceased, it didn't respond to keyboard input anymore, and I did a hard reset. I've tried several times, but always with the same result. It always hangs at the end of the disk blanking c.q. beginning of the writing of the filesystem. My writer is a Philips CDD 3610, and I'm using scsi emulation. The CDRW disc I was using had been used before, but I used cdrecord to do a complete blank beforehand. I might add that pktsetup worked without errors, but mounting the disk failed of course, because it couldn't find a valid superblock. Some drive info: -------------------------- /proc data ------------------------------------ slacker:/home/rsmith# cat /proc/ide/hdc/model PHILIPS CDD3610 CD-R/RW slacker:/home/rsmith# cat /proc/ide/hdc/settings name value min max mode ---- ----- --- --- ---- bios_cyl 0 0 1023 rw bios_head 0 0 255 rw bios_sect 0 0 63 rw current_speed 33 0 69 rw ide_scsi 0 0 1 rw init_speed 33 0 69 rw io_32bit 0 0 3 rw keepsettings 0 0 1 rw log 0 0 1 rw nice1 1 0 1 rw number 2 0 3 rw pio_mode write-only 0 255 w slow 0 0 1 rw transform 1 0 3 rw unmaskirq 0 0 1 rw using_dma 1 0 1 rw slacker:/home/rsmith# cat /proc/ide/hdc/identify 8580 0000 0000 0000 0000 0000 0000 0000 0000 0000 3456 4f32 3239 3834 3831 3734 3332 3330 3032 3130 0000 1e78 0000 563a 3030 332e 3031 5048 494c 4950 5320 4344 4433 3631 3020 4344 2d52 2f52 5720 2020 2020 2020 2020 2020 2020 2020 2020 0000 0000 0b00 0000 0200 0200 0002 0000 0000 0000 0000 0000 0000 0000 0000 0007 0203 0001 007f 007f 00d0 007f 0000 0000 0000 <the rest of the data contained only 0s> slacker:/home/rsmith# cat /proc/ide/hdc/driver ide-scsi version 0.9 slacker:/home/rsmith# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: IOMEGA Model: ZIP 100 Rev: 23.D Type: Direct-Access ANSI SCSI revision: ffffffff Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: PHILIPS Model: CDD3610 CD-R/RW Rev: 3.01 Type: CD-ROM ANSI SCSI revision: 02 -------------------------- /proc data ------------------------------------ I hope this gives enough info. Roland -- Roland Smith "Traveler, there is no path. r s m i t h @ x s 4 a l l . n l You make the path as you walk." http://www.xs4all.nl/~rsmith/

4 4

lockups
by darrell pfeifer 30 Apr '01

30 Apr '01

Hello, I'm running the 2j release on 2.4.4 (release version), using an HP drive, ide-cd. FYI, I also get lockups. The mouse stops moving under X and I can't switch to another console. The good news is that waiting a bit will eventually unlock. The last lockup went for about 50 seconds, just before the data finished writing (don't know if that was a coincidence). I'll try the incremental patch I just saw come flying in. (By the way, the CD/Packet code is some of the nicest and best documented kernel code I've seen) darrell

2 1

cdrwtool fails again with 0.02j and kernel 2.4.4
by rsmith＠xs4all.nl 30 Apr '01

30 Apr '01

After the last failure with ide-scsi emulation enabled, I tried again with the ide-cd driver: ------------------------------ cdrwtool -------------------------------- slacker:/home/rsmith/tmp/src/udf-cvs/udf/tools# ./cdrwtool -d /dev/hdc -q using device /dev/hdc 768KB internal buffer setting write speed to 12x Settings for /dev/hdc: Fixed packets, size 32 Mode-2 disc I'm going to do a quick setup of /dev/hdc. The disc is going to be blanked and f ormatted with one big track. All data on the device will be lost!! Press CTRL-C to cancel now. Initiating quick disc blank Disc capacity is 275008 blocks (550016KB/537MB) Formatting track Writing UDF structures to disc 7200 (CEST)/-120 wait_cmd: Input/output error Command failed: 2a 00 00 00 00 00 00 00 20 00 00 00 - sense 09.00.00 Error writing packet 0 (ffffffff) ------------------------------ cdrwtool -------------------------------- Nevertheless I inserted the pktcdvd module, and tried to mount the disk, just to see what happened. The accompanying errors from syslog are: --------------------------- /var/log/syslog ---------------------------- Apr 30 13:22:19 slacker kernel: hdc: irq timeout: status=0xd0 { Busy } Apr 30 13:22:19 slacker kernel: hdc: DMA disabled Apr 30 13:22:21 slacker kernel: hdc: ATAPI reset complete Apr 30 13:26:45 slacker kernel: hdc: irq timeout: status=0xd0 { Busy } Apr 30 13:26:47 slacker kernel: hdc: ATAPI reset complete Apr 30 13:29:58 slacker kernel: pktcdvd: inserted media is CD-RW Apr 30 13:29:58 slacker kernel: pktcdvd: Fixed packets, 32 blocks, Mode-2 disc Apr 30 13:29:58 slacker kernel: hdc: packet command error: status=0x51 { DriveRe ady SeekComplete Error } Apr 30 13:29:58 slacker kernel: hdc: packet command error: error=0x50 Apr 30 13:29:58 slacker kernel: ATAPI device hdc: Apr 30 13:29:58 slacker kernel: Error: Illegal request -- (Sense key=0x05) Apr 30 13:29:58 slacker kernel: Invalid field in command packet -- (asc=0x24, ascq=0x00) Apr 30 13:29:58 slacker kernel: The failed "Mode Sense 10" packet command was: Apr 30 13:29:58 slacker kernel: "5a 00 08 00 00 00 00 00 0c 00 00 00 " Apr 30 13:29:58 slacker kernel: pktcdvd: 550016kB available on disc Apr 30 13:30:07 slacker kernel: UDF-fs: No partition found (1) --------------------------- /var/log/syslog ---------------------------- Hope this helps. Roland -- Roland Smith "Traveler, there is no path. r s m i t h @ x s 4 a l l . n l You make the path as you walk." http://www.xs4all.nl/~rsmith/

1 0

packet-0.0.2j incremental fix
by Jens Axboe 30 Apr '01

30 Apr '01

Hi, There's a buffer count problem (reported by Stephen) in packet-0.0.2j, the attach patch should fix that. -- Jens Axboe

1 0

packet-0.0.2j
by Jens Axboe 30 Apr '01

30 Apr '01

Hi, Small stupid errors and a 2.4.4 kernel made me think that doing a completely fresh release was a good idea. Changes since packet-0.0.2i: - (0.0.2i-b) Fix compile error, pkt_put_buffer from pkt_end_io_read - Fix linking when ide-cd/sr modular and pktcdvd builtin - Remove SCSI_DEBUG_QUEUES, leave sanity segment check to final request state instead (makes more sense anyway now) - Add/correct config help entries - Merge 2.4.4 final - Remove throttling (see msg in packet-writing archive) - Remove request_cachep export again (used for throttling only) - Correctly kill request on I/O on media - Don't clear BH_Uptodate on failed buffer write (this is only valid for reads, see comment in source) Get it from *.kernel.org/pub/linux/kernel/people/axboe/packet or the sourceforge page. -- Jens Axboe

3 4

Best Sites #6A9B
by Martin Moere 29 Apr '01

29 Apr '01

***** This is an HTML Message ! *****

1 0

Device not ready errors
by Stephen Mollett 28 Apr '01

28 Apr '01

I am using 0.0.2i-pre3 with a Yamaha CRW4416S (SCSI3-MMC drive on an Adaptec AIC7880UW). When writing many files to a disc (eg. the kernel source), the driver seems to work OK to begin with: Detected scsi CD-ROM sr1 at scsi0, channel 0, id 2, lun 0 ... sr1: scsi3-mmc drive: 6x/6x writer cd/rw xa/form2 cdda tray ... pktcdvd: kernel thread pktcdvd0 started pktcdvd: writer sr1 sucessfully registered pktcdvd: speed (R/W) 3/2 pktcdvd: inserted media is CD-RW pktcdvd: Fixed packets, 32 blocks / packet, Mode-2 disc pktcdvd: enabled write caching on pktcdvd0 pktcdvd: speed (R/W) 3/2 pktcdvd: 540032kB available on disc [Lots of data written to disc, no errors in log] then suddenly floods the log with thousands of errors similar to: Device 0b:01 not ready: cmd=0, sector=95224, nr_sectors=8 or Device 0b:01 not ready: cmd=0, sector=628924, nr_sectors=68 Hope I've given sufficient information. Stephen Mollett

2 4

throttling and bad blocks
by Jens Axboe 28 Apr '01

28 Apr '01

Hi, I thought a bit more about the speed throttling I put in the latest release, and basically came to the conclusion that it shouldn't really be there. The low level drivers do their own retries of requests, and should do their own throttling too. Basically, when pktcdvd gets an I/O error from the lower layers the low level driver ought to have exhausted all possibilities wrt recovery. There's no point in doing retries etc at multiple levels, in fact it's pretty stupid. So I'm taking this code out again. But then, what should pktcdvd do on an I/O error? It should remap the packet location and resubmit the write. Ben, should we finally get this done? It's the last step in solid cd-rw writing, and absolutely critical if it's to be trusted. The problem with cd-rw is that UDF basically has to handle bad blocks and remapping. This is just one of the things that make it horrible to support, and why the format sucks. This sort of thing should be handled in hardware, like it is for any sane media. UDF will do its own read remapping for already remapped blocks I pressume (Ben?), if not pktcdvd can easily do it too (as long as I can get at the remap table). For writes, UDF needs to assign me a new start location for the packet. (UDF should to this too, but that would be much harder to support so I think for now we should let pktcvd do it). Comments? -- Jens Axboe

1 0

errors with 0.0.2i-b
by Graham Vincent 28 Apr '01

28 Apr '01

Hello. Here is the end of an attempt to build a new 2.4.3 kernel with the 0.0.2i-b packet writing patch applied. I updated the UDF version in the kernel to 0.9.3 before patching. Intel architecture. .... -o vmlinux drivers/block/block.o: In function `pkt_elevator_merge_req': drivers/block/block.o(.text+0x8a90): multiple definition of `pkt_elevator_merge_req' fs/fs.o(.text+0x2420): first defined here drivers/block/block.o: In function `pkt_elevator_cleanup': drivers/block/block.o(.text+0x8a94): multiple definition of `pkt_elevator_cleanup' fs/fs.o(.text+0x2424): first defined here fs/fs.o: In function `udf_set_blocksize': fs/fs.o(.text+0x587ec): undefined reference to `get_hardblocksize' make: *** [vmlinux] Error 1 .... Regards, Graham

2 1