freebsd stable - Jun 2003 - Iomega Zip 100 Problems with "New" ATA

I believe that I'm having some problems with a Zip 100 drive and the
"new" (not really so new anymore) ATA driver. I added a Zip and a new
CD-R device to a system over the weekend. The BIOS identifies all of
the new devices just fine, but when I boot FreeBSD (the only OS on the
system), I get to the ATA probes and things lockup (these are from
notes, not exact),

  ad2: READ command timeout tag=0 serv=0 - resetting
  ata1: reseting devices... done
  ad2: <IOMEGA  ZIP100> (blah, blah) PIO0

And it just hangs there forever, no Ctl-Alt-Del, no nuthin', hit the
reset button on the case.

The Zip is the slave on the secondary controller. I've had the problem
with 4.8-RELEASE and a very recent 4.8-STABLE. I've tested with
GENERIC just to make sure it wasn't my kernel config.

I believe this is a problem with the ATA driver and the Zip:

 1) If I pull the power on the Zip (still in the case, still on the
    ribbon), everything boots up fine.

 2) If I boot up a 4.5-STABLE-p1 kernel on the HDD, all devices are
    detected, and we come up in multi-user mode. (Albeit with
    unrelated errors due to a 4.5 kernel and 4.8 userland.)

 3) If I boot off of a 4.5-RELEASE CDROM and put on the 4.5 live FS,
    all devices are detected. This shows the new CD-R probably is not
    the flaky one.

I knew there have been some problems with the new (post 4.5) ATA
code. I've reviewed what I could find in the -stable archives and
didn't find anything specific to Zip drives. Has anyone else seen
problems with Zip drives? Any ways to work around this? Perhaps some
boot vars?

Thus spake Crist J. Clark (cjclark@alum.mit.edu) [2003-06-23 18:50] :

	-(Snip)-
> I knew there have been some problems with the new (post 4.5) ATA
> code. I've reviewed what I could find in the -stable archives and
> didn't find anything specific to Zip drives. Has anyone else seen
> problems with Zip drives? Any ways to work around this? Perhaps some
> boot vars?
	Well, this isn't going to be super helpful to you, but I did
want to offer you some consolation. I had a paraport zip on a
4.7-RELEASE system. This one of course, uses a different driver chain 
than the IDE one would (At least I think ... I'll not claim that I 
know much about kernel guts) but I did see similar behavior. 

	On the one I had the machine would boot up and everything would
probe correctly (including the zip drive), but as soon as I tried to
access the drive from userland, either with a mount, or a `camcontrol
reset` or anything like that -- hard lock.

	I tried different media, different cables, and even a different
drive, all to no avail. I don't think it was a parallel port issue as I
have other devices on the paraport now (I didn't then) that work fine. I
eventually gave up and bought another CD burner...

	Sorry I couldn't be more helpful. Maybe it's not the IDE driver,
but the core ZIP drive code? 

	



-- 
-----------------------------------
 Samuel Kesterson                 
 skesterson@09217travelnow.com        
 (Remove the numbers to reply)

 Views expressed are mine and not 
     my employers, blah blah blah.
-----------------------------------