Subject: Re: hptide0:0: bogus intr
To: None <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 09/14/2005 02:22:43
In article <008101c5b8c7$520af660$0a2e567e@monster4c>,
Robert Ken Francis <firstname.lastname@example.org> wrote:
>Yes, I guess my dmesg can be confusing. Thank you for responding.
>To clarify, on the card I have an hptide0:1:0, an hptide0:1:1, an
>hptide0:0:0, and I should have had an hptide0:0:1 but instead I
>got this "hptide0:0: bogus intr" message. So my wd2 and wd3 should have
>been wd3 and wd4, respectively. I can't use the drive as I
>get no wd device.
>On the motherboard I have a siside0:0:0 and a siside0:0:1 (a large hard
>drive and a DVD reader). The siside0:1:0 and siside0:1:1 I
>disabled in the BIOS and that connection doesn't work.
>The Adaptec ATA RAID 1200A card BIOS detects everything properly, so it
>would appear that I have the jumpers set up properly. DOS
>can detect everything.
>With this in mind:
>I just got NetBSD 3.99.8 and it still has the same problem 2.0.2 has,
>which is that I always get a "hptide0:0: bogus intr" message
>in my dmesg (see below). I am running an Adaptec ATA RAID 1200A card.
>The hard drive is an old Conner CP3041 and is a slave drive
>on the first Adaptec IDE ribbon.
>Can I fix this problem by modifying a setting and/or rebuilding the
>kernel? Or is this a bug that I should report?
Have you tried enabling one or more of:
#options PCI_ADDR_FIXUP # fixup PCI I/O addresses
#options PCI_BUS_FIXUP # fixup PCI bus numbering
#options PCI_INTR_FIXUP # fixup PCI interrupt routing