Messages in this thread | | | From | Rusty Russell <> | Subject | Re: modules oops in 2.5.52 | Date | Thu, 19 Dec 2002 16:55:38 +1100 |
| |
In message <1040271549.1317.12.camel@ixodes.goop.org> you write: > On Wed, 2002-12-18 at 18:11, Rusty Russell wrote: > > 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... > > It looks like it might end up calling request_module() from within > cleanup_module(). Is that going to be a problem?
Yes, it would be a problem. But I don't think that's the problem here, and I don't think it can actually happen (it's a pretty insane idea).
BTW, I can't reproduce your problem, maybe because I can't unload parport_pc here:
Module parport cannot be unloaded due to unsafe usage in drivers/parport/init.c:234 Module parport_pc cannot be unloaded due to unsafe usage in drivers/parport/parport_pc.c:1239
A little confused, 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/
| |