In message <1040260444.1316.4.camel@ixodes.goop.org> you write:
> Hi,
>
> I just had an oops in the modules code:
>
> Dec 18 16:58:59 ixodes kernel: Unable to handle kernel paging request at virt
ual address f8980924
> Dec 18 16:58:59 ixodes kernel: printing eip:
> Dec 18 16:58:59 ixodes kernel: f896756d
> Dec 18 16:58:59 ixodes kernel: *pde = 01bfc067
> Dec 18 16:58:59 ixodes kernel: *pte = 00000000
> Dec 18 16:58:59 ixodes kernel: Oops: 0000
> Dec 18 16:58:59 ixodes kernel: CPU: 0
> Dec 18 16:58:59 ixodes kernel: EIP: 0060:[<f896756d>] Not tainted
> Dec 18 16:58:59 ixodes kernel: EFLAGS: 00010282
> Dec 18 16:58:59 ixodes kernel: EIP is at __exitfn+0xd/0x4c [parport_pc]
Actually, you had an oops in the parport_pc code, in
cleanup_module(). Now, *why* that oopsed, I don't know...
> Now, any process which touches /proc/modules hangs, I guess because a
> lock was being held.
Yes. Changing this would be particularly interesting, since you don't
want a simultaneous "modprobe" to fail.
Rusty.
-- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Dec 23 2002 - 22:00:22 EST