Messages in this thread | | | Date | Thu, 08 Aug 2002 12:15:35 -0400 | From | "Anthony Russo., a.k.a. Stupendous Man" <> | Subject | Re: 2.4.19 BUG in page_alloc.c:91 |
| |
Thank you very much. As I suspected, the tainted driver is the one I use for my NetGear ethernet card (not nvidia :) I have switched to using the standard netgear driver that comes with linux and won't taint the kernel. I am now rebooting and if the problem reoccurs I will follow up with an email.
Thank you all for the support.
-- tony
Willy Tarreau wrote:
>On Thu, Aug 08, 2002 at 11:45:15AM -0400, Anthony Russo., a.k.a. Stupendous Man wrote: > > > >>Is there a way to tell which module it is that is setting the taint flag? >>I can load each module one by one and check after each if the taint flag >>is set, but I just need to know how to tell it is set. >> >> > >Modinfo could help you by telling you the licence for each module. >In the worst case, manually unload them all, and reload them one at a time. >Modprobe will issue a warning when loading such a module. > >BTW, my apologies for doubting about a removed nvidia driver ;-) > >Regards, >Willy > > > >
-- "Surrender to the Void." <http://162.83.145.190:8080/%7Eapr/surrenderToTheVoid.mp3> -- John Lennon
- 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/
| |