This is a multi-part message in MIME format.
--------------060107010901080001040406
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

see attached message.

nishio@hh.iij4u.or.jp says he has a QUANTUM fireball, too... and his 
workaround was:

``do NOT attach "QUANTUM FIREBALL" to
Ultra100 or Ultra66''


Unfortunately, this workaround is no good for me.  I need the QUANTUM fireball drives attached to each of my controllers.

Nevertheless, I thought this information may help diagnose the problem.

~Mike.


--------------060107010901080001040406
Content-Type: message/rfc822;
 name="Re: i386 - Cannot boot from wd(Promise Ultra100) with infinite ``bogus inter''msg"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Re: i386 - Cannot boot from wd(Promise Ultra100) with infinite ``bogus inter''msg"

	by lsh131.siteprotect.com (8.11.6/8.11.6) with SMTP id h9MIv9d27402
	for <m.hertrick@neovera.com>; Wed, 22 Oct 2003 13:57:09 -0500
  by mail.netbsd.org with SMTP; 22 Oct 2003 18:56:34 -0000
	by chassiron.antioche.eu.org (8.11.6p3/8.11.6) with ESMTP id h9MIuVe17457;
	Wed, 22 Oct 2003 20:56:31 +0200 (MEST)
	by rochebonne.antioche.eu.org (8.12.9p1/8.12.8/Submit) id h9MIuVdZ001512;
	Wed, 22 Oct 2003 20:56:31 +0200 (MEST)
Date: Wed, 22 Oct 2003 20:56:31 +0200
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: NISHIO Yasuhiro <nishio@hh.iij4u.or.jp>
Cc: current-users@NetBSD.org
Subject: Re: i386 - Cannot boot from wd(Promise Ultra100) with infinite ``bogus inter'' msg
Message-ID: <20031022185631.GA857@antioche.eu.org>
References: <20031016211744.GA327@antioche.eu.org> <20031017.122734.730563953.nishio@cerberus.yhn.jp> <20031019143258.GA5981@antioche.eu.org> <20031020.075611.730552568.nishio@cerberus.yhn.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031020.075611.730552568.nishio@cerberus.yhn.jp>
User-Agent: Mutt/1.4i
Sender: current-users-owner@NetBSD.org

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
--



--------------060107010901080001040406--