Re: 2.1.82 & reproducible strange name module loading requests

Shaw Carruthers (shaw@shawc.demon.co.uk)
Wed, 28 Jan 1998 12:58:22 +0000 (GMT)

I did some debugging on this problem by hacking request_module to trigger
an oops when the problem occurred and got:

Jan 27 18:57:30 shawc kernel: Oops: 0002
Jan 27 18:57:30 shawc kernel: CPU: 0
Jan 27 18:57:30 shawc kernel: EIP: 0010:[<c14adf62>]
Jan 27 18:57:30 shawc kernel: EFLAGS: 00010203
Jan 27 18:57:30 shawc kernel: eax: 00000001 ebx: c014b102 ecx: c1a88fe0 edx: 00000000
Jan 27 18:57:30 shawc kernel: esi: bffff118 edi: c14adf3c ebp: 00005401 esp: c14adf20
Jan 27 18:57:30 shawc kernel: ds: 0018 es: 0018 ss: 0018
Jan 27 18:57:30 shawc kernel: Process rsmtp (pid: 215, process nr: 29, stackpage=c14ad000)
Jan 27 18:57:30 shawc kernel: Stack: 00000018 c014c21b c14adf3c bffff0f8 00005401 bffff0f8 00005401 bffffb24
Jan 27 18:57:30 shawc kernel: bffff2b8 bffff114 00000000 0808f289 4009ef40 00000062 40074cc0 c016649e
Jan 27 18:57:30 shawc kernel: 00005401 bffff0f8 00005401 00005401 bffff0f8 c14e0700 00000000 c15168e0
Jan 27 18:57:30 shawc kernel: Call Trace: [<c014c21b>] [<c016649e>] [<c0144619>] [<c012b4fe>] [<c010995a>]
Jan 27 18:57:30 shawc kernel: Code: 00 00 f8 f0 ff bf 01 54 00 00 01 54 00 00 f8 f0 ff bf 00 07

Using `/usr/src/linux/System.map' to map addresses to symbols.

>>EIP: c14adf62 cannot be resolved
Trace: c014c21b <dev_ioctl+11f/3ac>
Trace: c016649e <inet_ioctl+3f2/434>
Trace: c0144619 <sock_ioctl+21/28>
Trace: c012b4fe <sys_ioctl+112/128>
Trace: c010995a <system_call+3a/40>
Code:
Code: 00 00 addb %al,(%eax)
Code: f8 clc
Code: f0 ff lock (bad)
Code: bf 01 54 00 00 movl $0x5401,%edi
Code: 01 54 00 00 addl %edx,0x0(%eax,%eax,1)
Code: f8 clc
Code: f0 ff lock (bad)
Code: bf 00 07 00 90 movl $0x90000700,%edi
Code: 90 nop
Code: 90 nop

But I am none the wiser has to how control got there or what corrupted the
address.

--
Shaw Carruthers - shaw@shawc.demon.co.uk
London SW14 7JW UK
This is not a sig( with homage to Magritte).