| Date | Thu, 21 Oct 2004 14:25:11 -0500 | From | "K.R. Foley" <> | Subject | Re: [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U9 |
| |
Thomas Gleixner wrote: > On Thu, 2004-10-21 at 20:57, K.R. Foley wrote: > >>>I guess, you don't have a tulip network card in your box, as the module >>>is removed. >>> >>>The question is, if it got registered correctly before the removal. >> >>Actually I do have the tulip card in the box and I am pulling this stuff >>from the logs over that connection now. Here are the next lines from the >>log that might help. > > > Not really. We must figure out, why sys_delete_module is called.
Understand. I did not mean the log would help figure it out, but that it would explain that the card really is present. :)
My guess is that it is prematurely unloading the driver before it's fully registered, like you said. The question is why? Also I am not in front of the system right now so I can't unload the module to see if it generates the error again, but I will try it when I get home.
> > [<e09a7767>] tulip_cleanup+0x17/0x1b [tulip] (16) > [<c0139801>] sys_delete_module+0x121/0x150 (12) <<-------- > [<c01531a1>] sys_munmap+0x51/0x60 (64) > [<c0116a20>] do_page_fault+0x0/0x660 (16) > [<c0106719>] sysenter_past_esp+0x52/0x71 (16) > > >>Oct 21 12:33:22 porky kernel: tulip 0000:04:0a.0: Device was removed >>without pro >>perly calling pci_disable_device(). This may need fixing. > > > This one is a result of the BUG() > > tglx > > >
- 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/
|