kernel pre6-5, ray_cs in socket 0 oopses/hangs the machine the first
time it is ejected.
in socket 1, you can eject and insert and it's fine. the second eject
causes an oops:
(physical insert/eject/insert/eject, no cardctl)
Apr 24 20:13:55 nifty cardmgr[54]: starting, version is 3.1.11
Apr 24 20:13:55 nifty cardmgr[54]: watching 2 sockets
Apr 24 20:13:55 nifty kernel: cs: IO port probe 0x0c00-0x0cff: excluding
0xcf8-0xcff
Apr 24 20:13:55 nifty kernel: cs: IO port probe 0x0800-0x08ff: clean.
Apr 24 20:13:55 nifty kernel: cs: IO port probe 0x0100-0x04ff: excluding
0x398-0x39f 0x4d0-0x4d7
Apr 24 20:13:55 nifty cardmgr[54]: initializing socket 1
Apr 24 20:13:55 nifty cardmgr[54]: socket 1: RayLink PC Card WLAN
Adapter
Apr 24 20:13:55 nifty kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 24 20:13:55 nifty kernel: cs: memory probe 0xa0000000-0xa0ffffff:
clean.
Apr 24 20:13:55 nifty kernel: ray_cs Detected: WebGear PC Card WLAN
Adapter Version 4.88 Jan 1999
Apr 24 20:13:55 nifty cardmgr[54]: executing: './network start eth0'
Apr 24 20:13:55 nifty kernel: eth0: RayLink, irq 3, hw_addr
00:00:8F:48:C8:91
Apr 24 20:14:22 nifty cardmgr[54]: shutting down socket 1
Apr 24 20:14:22 nifty cardmgr[54]: executing: './network stop eth0'
Apr 24 20:14:34 nifty cardmgr[54]: initializing socket 1
Apr 24 20:14:34 nifty cardmgr[54]: socket 1: RayLink PC Card WLAN
Adapter
Apr 24 20:14:34 nifty cardmgr[54]: executing: './network start eth0'
Apr 24 20:14:34 nifty kernel: ray_cs Detected: WebGear PC Card WLAN
Adapter Version 4.88 Jan 1999
Apr 24 20:14:34 nifty kernel: eth0: RayLink, irq 3, hw_addr
00:00:8F:48:C8:91
Unable to handle kernel NULL pointer dereference at virtual address
00000000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c01fe016>]
EFLAGS: 00010286
eax: 0000003a ebx: c02cae80 ecx: 0000009e edx: 00000000
esi: c0568e00 edi: 00000007 ebp: c03767a0 esp: c02d1ebc
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c02d1000)
Stack: c02951a0 c02045e1 c02cae80 c0568e00 c0568e00 c02045e1 00000f50
00000007
c02cae80 c0204a8e 00000011 c0568e00 ffffffff c0201750 c02cae80
00000006
c0568e00 c0568e00 c0b85c00 c0568e00 c03767a0 c01a5be4 c0568e00
cbf1bd80
Call Trace: [<c02951a0>] [<c02045e1>] [<c02045e1>] [<c0204a8e>]
[<c0201750>] [<c01a5be4>] [<c01df7b3>]
[<c01df77c>] [<c011f5b9>] [<c011c827>] [<c011c784>] [<c011c682>]
[<c010bda8>] [<c0110680>] [<cc8
[<c0108a60>] [<c010adb8>] [<c0110680>] [<cc802030>] [<c0108a60>]
[<c01108a2>] [<c0110680>] [<c01
[<c0108ac6>] [<c0105000>] [<c010018d>]
Code: c7 05 00 00 00 00 00 00 00 00 83 c4 08 83 e7 fe be 60 49 37
Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
In interrupt handler - not syncing
the oops debug has already been reported, it's the one David Hinds
replied to saying it's fixed in his pkg but Corey hasn't updated the
kernel files yet.
-d
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:09 EST