Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Sep 2004 07:35:06 +0200
From:      =?ISO-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net>
To:        Doug White <dwhite@gumbysoft.com>
Cc:        stable@freebsd.org
Subject:   Re: Obscure errors in dmsg, system instability
Message-ID:  <5390CF52-0D22-11D9-862C-000D9335BCEC@anduin.net>
In-Reply-To: <20040922191436.A36124@carver.gumbysoft.com>
References:  <41519A92.3070503@anduin.net> <20040922191436.A36124@carver.gumbysoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 23. Sep 2004, at 04:15, Doug White wrote:

> Is something sharing an interrupt with that device?
>
> PCI bus errors are generally Bad News .. either some device or the 
> mobo is inroducing errors.

Well.. Yes, there is some interrupt sharing. Relevant parts of dmsg:

[ltning@carnen] ~$ dmesg | grep "irq 2"
IOAPIC #0 intpin 19 -> irq 2
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xd400-0xd41f irq 
2 at device 4.2 on pci0
ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> port 0xd000-0xd0ff mem 
0xe2000000-0xe2000fff irq 2 at device 6.0 on pci0
amr0: <LSILogic MegaRAID> mem 0xe3000000-0xe300ffff irq 2 at device 9.1 
on pci0

I don't like the fact that the LSI and the Adaptec are sharing IRQs, 
given that the LSI is the main system drive controller (which is why I 
don't use the Adaptec at all - and it cannot be disabled in BIOS I 
think!)...

I should perhaps try to reallocate some of the IRQs, but I don't really 
have a clue how to do that, since I have no VGA in that box.. Ohwell, I 
guess I just have to rip it open ;)

Any other clues?

Thanks,
/Eirik





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5390CF52-0D22-11D9-862C-000D9335BCEC>