linux crashes due to conflict between scsi adapter and wifi network card

From: Tom Van Overbeke (tom.van.overbeke_at_pandora.remove-me.be)
Date: 02/27/04


Date: Fri, 27 Feb 2004 18:30:35 GMT

Hi, i have a serious problem with 2 pci devices that seem to conflict with
eachother:
 
a wifi pci card from level one (model WNC-0200) (with the infamous ACX100
chipset)
 
the other card is a pci scsi adapter Adaptec AHA-2940UW.

the wifi card itself is not the problem, but as soon as i try to access
the tape drive (DLT-2000) that is attached to the scsi adapter, linux
crashes after a few minutes. (a scsi harddisk i attached to this adapter
had the same erratic behaviour)

I installed windows on another partition on this pc, and the tape drive is
also having problems after a few minutes, but at least windows doesn't
crash.

each of the devices when installed separately on the pc work ok. I even
had the pc returned to the shop, but they returned it with a 'these 2
devices are simply not compatible' statement. I did a lot of research on
the internet, and found a lot of references to changing things in the bios
(my pc has a Asus P4B266 motherboard and an award bios). the firmware of
the motherboard has been flashed to the most recent version.

Things i tried: set pnp os in bios to yes / no, try to allocate a specific
irq per bus, so that they wouldn't conflict, i've put the devices in other
pci slots, tried to give options to the linux kernel when booting (style
acpioff and so on). It just didn't make any difference at all.

So i'm turning to you, gurus, as a last resort to help me.

Here's some info on my setup:

kernel: gentoo 2.4.22-gentoo-r7 (but a 2.6 kernel didn't work either)

02:0b.0 Network controller: Texas Instruments ACX 100 22Mbps Wireless
Interface
        Subsystem: Global Sun Technology Inc: Unknown device 8501 Control:
        I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
        Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr-
        DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt:
        pin A routed to IRQ 9
        Region 0: I/O ports at b800 [size=32] Region 1: Memory at f1000000
        (32-bit, non-prefetchable) [size=4K] Region 2: Memory at f0800000
        (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power
        Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
                PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable-
                DSel=0 DScale=0 PME-
 
02:0d.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
        ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+
        ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 2000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at b400 [disabled] [size=256] Region 1: Memory
        at f0000000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at
        <unassigned> [disabled] [size=64K]

tvo scripts # cat /proc/interrupts
           CPU0
  0: 1588570 XT-PIC timer
  1: 9187 XT-PIC keyboard
  2: 0 XT-PIC cascade
  5: 79233 XT-PIC usb-ohci, aic7xxx, cmpci, eth0
  8: 2 XT-PIC rtc
  9: 55 XT-PIC ehci_hcd, usb-uhci, wlan0
 10: 0 XT-PIC usb-uhci
 11: 1037981 XT-PIC usb-ohci, eth1, nvidia
 12: 279437 XT-PIC PS/2 Mouse
 14: 26278 XT-PIC ide0
 15: 2 XT-PIC ide1
NMI: 0
LOC: 1588642
ERR: 0
MIS: 0

(wlan0 is the wifi network device)

Does anyone see what could cause the conflict ? the irq's are not the
same, so that shouldn't be it ? or what else could it be ?

if the conflict can't be resolved, could i somehow disable the wifi card
via some pci tool like setpci ? (so that linux doesn't see it at all).
when i want to backup, i could disable the wifi card, and re-enable it
afterwards. i could live with this (if it's technically possible).

Thanks in advance for your help,

Tom.



Relevant Pages

  • RE: Device Manager Code 12
    ... Well, we know one device that started the resource conflict, the PCI bus ... 1394a PCI host controller card you installed, just might be easier to move it ... hardware resources, later down the road for you maybe it will come in handy.. ...
    (microsoft.public.windowsxp.hardware)
  • Re: P5/Celeron comments?
    ... type of video capture card require. ... That restriction is caused by the mix of PCI Express and PCI ... which means a PCI bus card may get the "short straw". ... and you only get time slices from each camera. ...
    (alt.comp.periphs.mainboard.asus)
  • CRASH: SATA + 8139 + Via Rhine = STOP
    ... On the other side I have an 8139 based card. ... a Silicon Image Serial-ATA card on the PCI bus. ... raid5 personality registered as nr 4 ... md: Autodetecting RAID arrays. ...
    (Linux-Kernel)
  • [RFC / git patch] Move pci_find_* under CONFIG_PCI_LEGACY
    ... converting ancient drivers to PCI hotplug API, ... config HISAX_TELESPCI ... bool "NETspider U card" ... +#ifdef CONFIG_PCI_LEGACY ...
    (Linux-Kernel)
  • Re: Help: searching a video server that meets my requirements
    ... For basic composite capture, ... be BT878 chips. ... is a PCI to PCI bridge chip, so there aren't four loads and ... The above card will saturate a PCI bus, ...
    (rec.video.desktop)