Subject: kern/10183: cardbus related panic
To: None <>
From: Hubert Feyrer <>
List: netbsd-bugs
Date: 05/23/2000 09:27:12
>Number:         10183
>Category:       kern
>Synopsis:       cardbus related panic
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 23 09:28:00 PDT 2000
>Originator:     Hubert Feyrer
>Release:        20000523
Hubert Feyrer <>
Toshiba Satellite 2140 XCDS (i386), today's sources.

	When booting a GENERIC kernel that has cbb*, cardslot*, cardbus*
	and pcmcia* at cardslot enabled, the following panic occurs (ten
	finger dump):

[cb0 found on Toshiba America Info Systems ToPIC97 CardBus-PCI Bridge chip
 Sorry for not more information, this was scrolling away too fast]
cbb0: NOT USED because of unconfigured interrupt
cbb1: NOT USED because of unconfigured interrupt
pcic0: controller 0 (Intel 82365SL Revision 1) has sockets A and B
pcic1: controller 1 (Intel 82365SL Revision 1) has no sockets
pcmcia0 at pcic0 controller 0 socket 0
pcmcia1 at pcic0 controller 0 socket 1
isapnp0: no ISA Plig 'n Play devices found
biomask ef7d netmask ef7d ttymask ffff
pcic0: controller 0 detecting irqs with mask 0xdeb8:..3uvm_fault(0xc04cd90a, 0x0, 0, 1) -> 1
kernel: page fault trap, code=0
Stopped in swapper at   isa_intr_disestablish+0x9:     movl   0x14(%ecx),%edx

	Stack trace:

db> t
isa_intr_disestablish(c04eb080,...) at isa_intr_disestablish+0x9
gcc2_compiled.(c06dd09c) at gcc2_compiled.+0x93
Xintr4() at Xintr4+0x70
--- interrupt ---
isa_intr_establish() at isa_intr_establish+0x114
pcic_isa_prove_interrupts() ... +167

	The machine's BIOS allows setting the bridge to auto-detect, 
	PCIC-Compatible and CardBus/16-bit. The panic happens with the
	first two, and only with "cardbus" I get to boot. But no
	cardbus/pcmcia slot is found either.

	Boot a -current kernel with cardbus enabled on a Toshiba
	Satellite 2140 XCDS that has the bridge's mode set to
	pcmcia or auto-detect.

	No idea.
	Maybe some dereferenced NULL-pointers / NULL pointers being passed
	to funktions that don't expect/properly handle them?