Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
i think this might be one of those "rare" linux viruses.
all of the things you mention are very common to windows viruses, so...
I would strongly doubt that. If it were true then Lockywolf could sell his machine to a museum for zillions of euros. There have been "proof of concept" type linux viruses that could possibly be written and could possibly cause problems if around 37 preconditions were met. I have never heard of a linux user ever having contracted a viral infection "in the wild".
Let me repeat, it is theoretically possible to create and spread viruses that could effect linux. I have just never heard of a case where it really happened.
I await enlightenment if I am mistaken.
cheers,
jdk
I would say that you definitely have a hardware failure waiting to happen. Probably it's causing the system to be flooded with interrupts.
While you still have time, get everything off that system onto a backup, and plan to replace the system a.s.a.p. "It's gonna blow, and it's gonna blow soon. Don't be riding it, or standing underneath it, when it hits the ground."
I would say that you definitely have a hardware failure waiting to happen. Probably it's causing the system to be flooded with interrupts.
While you still have time, get everything off that system onto a backup, and plan to replace the system a.s.a.p. "It's gonna blow, and it's gonna blow soon. Don't be riding it, or standing underneath it, when it hits the ground."
Maybe that's the cause.
If the distro has an easy way to disable acpi you might be able to work around the problem that way. If not, maybe you can disable it at BIOS level (not sure if linux will care about that, though).
Maybe it's just a bad plug or something that can't maintain a constant flow of current which is causing an interrupt flood to the acpi subsystem or something.
You can as well try to pass the acpi=off option to the boot line, of even to disable it at kernel level.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.