On Mon, Oct 20, 2003 at 07:56:11AM +0900, NISHIO Yasuhiro wrote:
> 
> I tried with U66, and I got following message.
> 
>                 :
>         fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
>         Kernelized RAIDframe activated
>         pdcide0:0: bogus intr (reg 0x1131520)
>         pdcide0:0: bogus intr (reg 0x1131520)
>         pdcide0:0: bogus intr (reg 0x1131520)
>                 :
> 
> But I found workaround. That is ``do NOT attach "QUANTUM FIREBALL" to
> Ultra100 or Ultra66''.  I think my QUANTUM FIREBALL has
> hardware/firmware bug.

Possibly, it asserts its interrupt line while reset is active.
Now that the probe is done with interrupts enabled, this fails.

> 
> Here is the summary;
> --------------------
> 
> Kernel: NetBSD-current 2003-09-19 21:40:00 UTC or later
> 
>   - The "bogus intr" message appears only when the "QUANTUM
>     <FIREBALLlct15 30>"  attached to Ultra100. (reappearance 100%)
> 
>     There is no effect if
> 	- remove Other(cbb, fxp, wm) PCI Card,
>         - replace PCI card slot,
>         - use new UDMA100 IDE cable.
> 	- disable/enable on board IDE,
> 	- disable/enable VGA IRQ,
> 	- disable/enable on board USB,
> 	- etc.
> 
>   - pdcide driver work well with
> 	- SEAGATE <ST340810ACE> on U100 Primary master
> 	  Western Digital <WDC WD136AA> on U100 Secondary master	
> 	- WDC on Primary, ST on Secondary
> 
> 
>   - U66(PDC20262) & FIREBALL dose not work.
>         ``pdcide0:0: bogus intr (reg 0x1131520)''
> 
>         only ``pdcide0:0:...'' messages, ``pdcide0:0:..'' and
>         ``pdcide0:1:...'' when I used U100.
> 
>   ==> FIREBALL has hardware bug?

Maybe, but not handled the same way by different controllers.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--