Subject: Re: port-i386/33492: wi(4) crash
To: None <port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Abrasive <abrasive@axdf.net>
List: netbsd-bugs
Date: 05/17/2006 02:00:06
The following reply was made to PR port-i386/33492; it has been noted by GNATS.

From: Abrasive <abrasive@axdf.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-i386/33492: wi(4) crash
Date: Wed, 17 May 2006 11:57:28 +1000

 On Tue, May 16, 2006 at 05:05:14PM +0000, Matthias Drochner wrote:
 >  abrasive@axdf.net said:
 >  > 	This was traced, with breadcrumbs, to this line in wi_reset (dev/ic/
 >  > wi.c):
 >  > 	CSR_WRITE_2(sc, WI_EVENT_ACK, ~0); 
 >  
 >  For me this looks like an address conflict, the address
 >  > pcic0: port 0x300-0x30f
 >  might be in use by something else.
 >  To get some information, the pnpbios might be of some use.
 
 pnpbios? Not on this laptop! (No isapnp, no PCI at all, a bare DOS BIOS... it's only about ten years old.)
 
 So, there's also nowhere else to configure the PCMCIA interface to - here, from the kernel config:
 pcic0	at isa? port 0x3e0 iomem 0xd0000 iosiz 0x4000
 pcic1	at isa? port 0x3e2 iomem 0xd4000 iosiz 0x4000
 
 Being an ISA-based system this is the only place I'd expect to find these (that's from the GENERIC_TINY config also).
 And, pcic0 actually attaches, and works perfectly with other cards. So, that address space does seem to be pretty clear.
 
 James