On Wednesday 09 August 2006 06:15, Dominic Marks wrote:> Hello,
>
> I seem to have a device conflict on my desktop. When attempting to fsck
> a gstripe
> volume attached via the twe card the system becomes 'choppy' and
from
> looking
> at systat (when it isn't frozen) the system is receiving about 300k
> interrupts per
> second from the pcm device. If I leave the system in this state for a
> few minutes it
> will do an instant-reset, presumably because it can't cope.
>
> Verbose dmesg: http://goodforbusiness.co.uk/~dom/dmesg.boot
>
> Specific parts:
>
> twe0: <3ware Storage Controller. Driver version 1.50.01.002> port
> 0xdcb0-0xdcbf mem 0xdf000000-0xdf7fffff irq 49 at device 13.0 on pci3
> twe0: Reserved 0x10 bytes for rid 0x10 type 4 at 0xdcb0
> ioapic2: routing intpin 1 (PCI IRQ 49) to vector 49
> twe0: [GIANT-LOCKED]
> twe0: AEN: <soft reset>
> twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048
> twe0: Monitor ME7X 1.01.00.040, PCB Rev5 , Achip 3.20 , Pchip 1.30-66
> twe0: port 0: WDC WD3200KS-00PFB0 305245MB
> twe0: port 1: WDC WD3200KS-00PFB0 305245MB
>
> pcm0: <CMedia CMI8738> port 0xcc00-0xccff irq 17 at device 13.0 on
pci7
> pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xcc00
> ioapic0: routing intpin 17 (PCI IRQ 17) to vector 55
> pcm0: [MPSAFE]
> pcm0: sndbuf_setmap 3e8ee000, 4000; 0xe5408000 -> 3e8ee000
> pcm0: sndbuf_setmap 3e8ea000, 4000; 0xe540c000 -> 3e8ea000
>
> I believe I can use device.hints(5) to work around this, but I am unsure
> variable I can
> set in order to resolve this. Does the device 13.0 from dmesg refer to
> the 'drq' ?
Does this system have an Intel PCI-X host bridge in it? If so, it's
probably due to brain damage in that chip. You might be able to work
around it by making twe0 use the same IRQ as pcm0 by adding the
following hint:
hint.pci3.13.INTA.irq=17
That should make twe0 use IRQ 17.
--
John Baldwin