14 comments

[ 3.1 ms ] story [ 34.1 ms ] thread
ctrl+f "ground": no results.

I'd bet it's a grounding issue.

Probably not grounding, but quite probably some kind of voltage dip.
"Try another refrigerator" pretty much sums up internet help.
Just wait until you find out that it sums up everything from auto repair to diagnostic medicine...
I have a similar issue.

Sometimes, but not every time, when I turn on a particular halogen lamp using the same outlet as a particular computer, it triggers USB detection and I get kernel messages on /dev/console as if I was plugging in a USB device.

This is a BSD kernel.

Now, if you had some kind of home automation switching the lights you could implement a really slow communication protocol as a USB device driver.
This was happening to me, there was some problem with the electricity in my apartment. I can't recall what the electrician said, there were some switches that only 1/4 were working, and if 2/4 had been it would have fried everything. They fixed it in about an hour.
Known bug #1568604: "Mouse cursor lost when unlocking with Intel graphics"[1]. There are many suspend/resume/power management events which can cause the cursor to disappear. The refrigerator cycling is probably causing a brief power dip or surge which the computer interprets as a power cycling event. There's a fix, and it's gradually going into the various Linux distros.

When this happens, try CTRL-ALT-F1 followed by CTRL-ALT-F7. That switches the display to text mode and back. If that restores the cursor, this is the problem.

[1] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video...

Arch has been distributing git builds of xf86-video-intel for a while, since there haven't been any releases in almost 2 years. The bug was fixed over a month ago and the latest Arch build is only a few days old. Its even noted as being fixed on Arch in the bug comments [0].

So, probably not that.

[0] https://bugs.freedesktop.org/show_bug.cgi?id=94677

If you can get the cursor to disappear with the display still running, the bug is related to this bug. Maybe the fix isn't complete enough.
What an amazing answer. Systems are weird.
I think thinkpads of that generation had RF shielding issues.

I had a W520 that would crash whenever it was moved across a table or removed from a backpack. Turns out the shielding on the RAM door was faulty and the static charge generated by friction on the bottom of the case was enough to corrupt the ram contents and crash the laptop. Talk about a bizarre failure.