ooops on modules

Marty Leisner (leisner@sdsp.mc.xerox.com)
Thu, 24 Oct 1996 13:34:23 PDT


I just got a 2.0.23 patch to smbfs...

But its producing an oops...

How do I debug a module producing an oops? Where does it get the
module symbols from?

I got a newer klogd (1.3) and I'm seeing:
divide error: 0000
CPU: 0
EIP: 0010:[<0181a1e5>]
EFLAGS: 00010202
eax: 00000001 ebx: 00626aa8 ecx: 0063f000 edx: 00000000
esi: 00000000 edi: 00000000 ebp: 00000003 esp: 00659df4
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process touch (pid: 225, process nr: 25, stackpage=00659000)
Stack: 00626aa8 00659f74 00659f74 00000003 00000000 00000246 00000000 00000ff0
001d3920 00602018 00013e20 007d0064 00013e2c 0011d13f 00000005 00000000
00602034 0016c64a 00602070 00000006 000186a3 00000002 00000064 00000064
Call Trace: [<0011d13f>] [<0016c64a>] [<0016b182>] [<0016b245>] [<0016e018>] [<0016e506>] [<0016e438>]
[<0011b08d>] [<0011b89d>] [<0012a37a>] [<0012a580>] [<0012a660>] [<001288d5>] [<0010a895>]
Code: f7 3d 54 b4 81 01 39 fa 75 b9 31 c9 85 c9 75 51

(once I know where its happening, it should be easy to fix).

marty leisner@sdsp.mc.xerox.com
Don't confuse education with schooling.
Milton Friedman to Yogi Berra