[SOLVED] My Linux Server is turning insane, module loaded for hardware that is not present
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My Linux Server is turning insane, module loaded for hardware that is not present
I have the oddest thing I have ever seen.
I used to have a Intel gigabit NIC in this server and saw that it was trying to load the module over and over and over and over.
Then I removed the NIC, thinking that it is damaged.
And now? The server is still stuck loading the driver and unloading it every few seconds. It this system possessed or just straight crazy?
the frequency can be explained if something wanted to restart [repeatedly] it in case of a problem. But we need to know why is it died? Is this the correct driver at all?
the frequency can be explained if something wanted to restart [repeatedly] it in case of a problem. But we need to know why is it died? Is this the correct driver at all?
The crazy thing is: there is no Intel NIC in this machine, none.
The crazy thing is: there is no Intel NIC in this machine, none.
You told it already. You can remove (rename) that driver. And again, without details hard to say anything. There should be something related in /var/log (or somewhere). http://www.catb.org/~esr/faqs/smart-...html#beprecise
This is a real Irish solution: Have you tried putting the NIC back, and just let it load? BTW, in modprobe.d, you can also link the module to /bin/true, which reports success
Well, there is a good point, I was looking at the kernel logs via dmesg and saw that it was loading and unloading. I actually solved the puzzle, this is piece of software that I wrote many years ago that assumed a trusty e1000e to be present and it was purposefully loading the module over and over when it did not work.
Yes, the logs really do hold the solution pretty much 100% of all time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.