5.2-CURRENT - ata1-slave : TIMEOUT - SETFEATURES - another evil continues...

[Jeff Gardner]

I also had this problem with my 48X Lite-On.  Same model as mentioned
below.  However, my drive died.  So, I replaced it with the 52x model
52327S.

acd0: CDRW <LITE-ON LTR-52327S> at ata1-master UDMA33

I recently installed 5.2-RELEASE and then upgraded to -CURRENT as of a
few hours ago.  I can read CD's just fine.  However, trying to burn with
burncd gives the following:

genesis# burncd -f /dev/acd0 data 5.2-RELEASE-i386-miniinst.iso fixate
burncd: ioctl(CDIOCSTART): Device busy

I know this burner works (just not in 5.2-CURRENT right now) since I
used it to burn the above iso via another OS.

However, I do not get the warning mentioned below any longer.

Jeff

Colin Harford wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Matt,
> 
> I have the same problem, that the ATA probes keep dying with my burner...
> 
> I emailed Søren some dmesg related stuff today on it...
> 
> Cheers,
> 
> CH
> 
> 
> 
> On 31-Jan-04, at 5:59 PM, Matt Dawson wrote:
> 
>> OK, who said it was a Lite-On problem? Go to the head of the class. I 
>> just
>> removed all my ATA devices, installed my (crappy) Sil0680 software 
>> RAID card
>> temporarily and gave each device its own IDE channel. Whatever channel 
>> I put
>> the Lite-On LTR-48246S onto showed the following in dmesg:
>>
>> ata1-slave: WARNING - SETFEATURES recovered from missing interrupt
>>
>> with my kernel that works, p0. This is taken, of course, from the 
>> dmesg after
>> I put everything back the way it was. The original message was 
>> ata0-master. I
>> haven't tried compiling the latest source on this machine yet, since I 
>> figure
>> I have to get rid of this problem before I stand a fighting chance of 
>> getting
>> the new ata drivers working on here.
>>
>> So it seems the LTR-48246S is the problem device. Bummer. It works 
>> nicely with
>> K3b and xcdroast, too. I shall upgrade to the latest firmware if I can 
>> find a
>> binary file of SS0E (why do these people assume we all have Windoze 
>> boxes to
>> upgrade firmware?) and see what happens.
>>
>> UPDATE: Nothing happened with firmware update to SS0E. Still got the same
>> message.
>>
>> Any ideas? Is there some way this can be worked around? Any logs, etc.
>> required?
>>
>> -- 
>> Matt Dawson.
>>
>> _______________________________________________
>> freebsd-current at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscribe at freebsd.org"
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
> 
> iD8DBQFAHIaC70HXebAAFAERAjf/AJ9V48OVoVH4vdRrrBKbSqdx8zN61ACg9YtL
> /EwHwSnFLrmROnxhDjZnEo4=
> =6E1k
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org
> "