On Wed, Mar 15, 2000 at 10:58:07AM +0000, Tim Waugh wrote:
> On Wed, 15 Mar 2000, Ian Peters wrote:
>
> > Unfortunately I'm leaving town in 4 hours, so I hope someone else is
> > also seeing this behaviour (or the cause is immediately apparent to
> > people in the know).
>
> I can't get this to happen here, I'm afraid.
Tim,
On my way out the door, thought I'd give it one last try.
Unfortunately, this is still reproducable for me.
This time, I got an oops to work with. All modules loaded fine, right
after boot I typed rmmod -a; rmmod -a, and I got the oops.
Afterwards, parport_pc is listed as (uninitialized), and parport is
still loaded as depending on parport_pc.
Quick hardware summary: Dual PII, Tyan Thunder motherboard, SCSI root,
SCSI and IDE devices. Parallel port is used to connect a Lexmark
Optra E printer.
ksymoops 2.3.3 on i686 2.3.99-pre1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.3.99-pre1/ (default)
-m /boot/System.map-2.3.99-pre1 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Warning (compare_ksyms_lsmod): module parport_pc is in lsmod but not in ksyms, probably no symbols exported
Unable to handle kernel NULL pointer dereference at virtual address 00000004
c01b6b27
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c01b6b27>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 00000000 ebx: c74a5c00 ecx: c129ffc0 edx: 00000000
esi: c8835ca0 edi: c8833000 ebp: 00000000 esp: c5a8df70
ds: 0018 es: 0018 ss: 0018
Process rmmod (pid: 230, stackpage=c5a8d000)
Stack: c74a5c00 c882d000 c8834b85 c8835ca0 c8833000 c882d000 c8833000 00000000
c0121af3 c8833000 c882d000 00000000 00000000 c0120eb1 c8833000 00000001
c5a8c000 00000061 00000005 bfffea0c c010bd30 00000000 00006161 08054006
Call Trace: [<c882d000>] [<c8834b85>] [<c8835ca0>] [<c8833000>] [<c882d000>] [<c8833000>] [<c0121af3>]
[<c8833000>] [<c882d000>] [<c0120eb1>] [<c8833000>] [<c010bd30>]
Code: 89 50 04 89 02 8b 1d a8 17 25 c0 81 fb a8 17 25 c0 74 29 8d
>>EIP; c01b6b27 <pci_unregister_driver+b/4c> <=====
Trace; c882d000 <[eepro100].data.end+75e1/7631>
Trace; c8834b85 <__kstrtab_parport_parse_dmas+3772/????>
Trace; c8835ca0 <__kstrtab_parport_parse_dmas+488d/????>
Trace; c8833000 <__kstrtab_parport_parse_dmas+1bed/????>
Trace; c882d000 <[eepro100].data.end+75e1/7631>
Trace; c8833000 <__kstrtab_parport_parse_dmas+1bed/????>
Trace; c0121af3 <free_module+17/98>
Trace; c8833000 <__kstrtab_parport_parse_dmas+1bed/????>
Trace; c882d000 <[eepro100].data.end+75e1/7631>
Trace; c0120eb1 <sys_delete_module+471/584>
Trace; c8833000 <__kstrtab_parport_parse_dmas+1bed/????>
Trace; c010bd30 <system_call+34/38>
Code; c01b6b27 <pci_unregister_driver+b/4c>
00000000 <_EIP>:
Code; c01b6b27 <pci_unregister_driver+b/4c> <=====
0: 89 50 04 mov %edx,0x4(%eax) <=====
Code; c01b6b2a <pci_unregister_driver+e/4c>
3: 89 02 mov %eax,(%edx)
Code; c01b6b2c <pci_unregister_driver+10/4c>
5: 8b 1d a8 17 25 c0 mov 0xc02517a8,%ebx
Code; c01b6b32 <pci_unregister_driver+16/4c>
b: 81 fb a8 17 25 c0 cmp $0xc02517a8,%ebx
Code; c01b6b38 <pci_unregister_driver+1c/4c>
11: 74 29 je 3c <_EIP+0x3c> c01b6b63 <pci_unregister_driver+47/4c>
Code; c01b6b3a <pci_unregister_driver+1e/4c>
13: 8d 00 lea (%eax),%eax
2 warnings issued. Results may not be reliable.
Sorry I can't stick around to do a better job tracking this one down,
I'm on my way out the door. You should have the .config from the last
mail I sent.
-- Ian Peters | GnuPG Key ID 5C23D20C | Those who know what's best itp@gnu.org | E584 2558 FAC3 BEAB EFAC | for us must rise and save itp@cmu.edu | FC74 CFED 7E24 5C23 D20C | us from ourselves...- 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 : Thu Mar 23 2000 - 21:00:18 EST