Date: 7 Feb 2001 00:49:59 -0000 From: Jeff <jeff@drunkenchipmunk.com> To: ken@kdm.org Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI errors with adv0 adapter and SAF CD-R8020 Message-ID: <20010207004959.69117.qmail@adsl-63-193-27-229.dsl.snfc21.pacbell.net> In-Reply-To: <20010206163051.A96033@panzer.kdm.org> (ken@kdm.org) References: <20010206185148.67754.qmail@adsl-63-193-27-229.dsl.snfc21.pacbell.net> <20010206163051.A96033@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ken, Thanks for the reply! To answer your questions: Yes, the same media seems to work under NT but not FreeBSD: the discs are blue TDK 650MB cd-rs. There is nothing else on the controller except for the cd writer device. Incidentally, Mike Squires replied to my message with the observation that the EEPROM checksum failed in the adv0 init part of the dmesg output. I hadn't paid too much attention to it before, but perhaps this is simply a case of controller failure...? I suppose burning a CD under Windows NT would provide more insight in that direction, but my NT installation got wrecked beyond repair over the weekend after installing some silly application (now it won't boot beyond the initial blue screen anymore). The last time I burned a CD under NT was last week, so the assumption that the device/adapter would still work under NT can't really be verified. FYI, the motherboard is an Asus P2B, with Award BIOS rev 1006. I will go ahead and file the PR with the additional information you specified. Thanks again, Jeff > > I'm hoping someone can help shed some light on this problem. > > > > I am running FreeBSD 4.2-RELEASE and trying to use cdrecord 1.9 (from > > a freshly cvsup'd ports collection). The problems occur below with the > > stock generic kernel, and also with custom kernel with "options > > _KPOSIX_VERSION=199309L" line added in for priority scheduling (some > > discussions suggest this is helpful for cdrecord to work properly) > > > > The CD burner is a Smart And Friendly 8020 8x's writer. Relevant > > output from dmesg: > > ---------- > > adv0: <AdvanSys ASC3030/50 SCSI controller> port 0xa800-0xa8ff mem 0xe1000000-0x10000ff irq 10 at device 10.0 on pci0 > > adv0: Warning EEPROM Checksum mismatch. Using default device parameters > > adv0: AdvanySys SCSI Host Adapter, SCSI ID 7, queue depth 16 > > ... > > cd0 at adv0 bus 0 target 6 lun 0 > > cd0: <SAF CD-R8020 1.24> Removable CD-ROM SCSI-2 device > > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > > ---------- > > > > I have a 429142016 byte (~429M) .iso file (created with mkisofs) I'm > > trying to burn, so I run the following as root: > > > > cdrecord device=0,6,0 speed=4 mybackup.iso > > > > I have also tried with speed values of 1 and 8, with the same results. > > cdrecord starts up, the 'write' light on the cd burner comes on, the > > 'read' light flashes; a minute or two thereafter, I get the following > > output: > > > > (pass0:adv0:0:6:0): Timed out > > (pass0:adv0:0:6:0): Attempting abort > > (pass0:adv0:0:6:0): Timed out > > (pass0:adv0:0:6:0): Resetting bus > > adv0: No longer in timeout > > cdrecord: Input/output error. write_g1: scsi sendcmd: cmd timeout after 42.200 (40) s > > CDB: 2A 00 00 00 5E 36 00 00 1F 00 > > write track data: error after 49393664 bytes > > Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 > > cdrecord: Input/output error. flush cache: scsi sendcmd: retryable error > > Those messages mean that the CD-R took longer than the timeout period (40 > seconds) to return a write command. > > [ ... ] > > > In the error output above, it seems to have written about 49M before > > dying. Sometimes it gets to about 100M, it seems to vary a great deal. > > > > Has anyone seen errors like this? I'm assuming the > > "(pass0:adv0:0:6:0): Timed out" messages are kernel-level output: does > > this suggest SCSI driver or subsystem issues? The device works > > properly under Windows NT. If these are timeouts, are there values I > > can tune somewhere to fix/prevent them? I have a small stack of failed > > cd-r's lying uselessly in the trash, it's been frustrating. > > Are you using the same media under NT that you're using under FreeBSD? > > Do you have any other devices on that controller, and do they function > properly? > > I talked to Justin Gibbs (author of the driver) about this, and he says > that it's possible that the NT driver for that board is using different > firmware than the FreeBSD driver, which could explain a difference in > behavior. > > Anyway, he's planning on working on the Advansys driver soon, so he'd like > you to file a PR describing your problem as you have in this message, > except perhaps you may want to include full dmesg information, and also > indicate what brand/model motherboard you're using. > > Also, you'll want to answer the two questions above in the PR and perhaps > here on the -scsi list as well. > > It isn't entirely clear what the problem is, perhaps when Justin looks at > the driver he may be able to reproduce your problem. > > Ken > -- > Kenneth Merry > ken@kdm.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010207004959.69117.qmail>