2.6.x kernels & PCI-to-PCMCIA bridges [again]
Dominik Brodowski
linux at dominikbrodowski.de
Wed May 5 17:54:27 BST 2004
That's a real strange panic() -- and even more strange, I do see the exact
same panic() [call trace starting at common_interrupt(), Process pci.agent()
for me] on some occasions when I use the new Intel driver for the ipw2100
WLAN Mini-PCI card -- which also uses parts of "hostap". Also, nothing in
the call trace does seem to be pcmcia-related... Does anybody have any
ideas on what the cause of these panics might be?
Dominik
On Wed, May 05, 2004 at 11:44:28AM +0300, jar wrote:
> Unable to handle kernel paging request at virtual address 6b6b6b6b
> printing eip:
> 6b6b6b6b
> *pde = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<6b6b6b6b>] Not tainted
> EFLAGS: 00010202 (2.6.5-1.339)
> EIP is at 0x6b6b6b6b
> eax: 6b6b6b6b ebx: 6b6b6b6b ecx: c331bee0 edx: c03b6fd0
> esi: 6b6b6b6b edi: c03374a0 ebp: c03b6fd0 esp: c03b6fc8
> ds: 007b es: 007b ss: 0068
> Process hotplug (pid: 2158, threadinfo=c03b6000 task=c36180b0)
> Stack: c012720e c03b6fd0 c03b6fd0 c03b6fd0 c03b6fd8 00000011 c03db3a8
> 0000000a
> 00000000 c0122f5d c0a7ef10 00000046 c03b7000 c0108c41
> Call Trace:
> [<c012720e>] run_timer_softirq+0x217/0x32b
> [<c0122f5d>] __do_softirq+0x35/0x73
> [<c0108c41>] do_softirq+0x46/0x4d
> =======================
> [<c010803d>] do_IRQ+0x2f5/0x301
> [<c02e8f28>] common_interrupt+0x18/0x20
> [<c0143d02>] check_poison_obj+0xa3/0x15b
> [<c016d8fd>] getname+0x19/0xb2
> [<c0145786>] kmem_cache_alloc+0x77/0x142
> [<c016d8fd>] getname+0x19/0xb2
> [<c015e11d>] sys_open+0xc/0x7d
> [<c02e8d37>] syscall_call+0x7/0xb
>
> Code: Bad EIP value.
> <0>Kernel panic: Fatal exception in interrupt
> In interrupt handler - not syncing
More information about the linux-pcmcia
mailing list