Definitely not memory, I think. I ran memtest from the old Arch iso for over 8 hours. It completed 3 passes and found zero errors.
I had problems getting a boot menu with the USB stick in place and ended up having to change the default boot order. That also seems weird - I've never had such an issue in the past on this machine.
This was entirely reproduceable last night. Took it to Lenovo today and it obviously performed perfectly.
They don't think it is the HDD but offered me a disk testing utility for Windows. Need to find out what to use in the Linux world.
They said all they could do was restore it to factory settings and see if that solved the issue. But since I couldn't even reproduce it with Linux, there didn't seem much point.
I was told by the person talking to me that he "wouldn't trust Linux's restart function" although he didn't say why. He seems to think it might be caused by a particular document, application or kind of update and told me to document it and look for a pattern.
I pointed out that I've seen the issue on reboot from BIOS which surely can't implicate Linux but that didn't seem to have any effect.
They didn't actually open it up to look at anything even though they said it could be a lose connection somewhere.
I'm being unfair, I think. It's intermittent. I couldn't reproduce it. What could I reasonably expect them to do? Just so frustrating...
And I'm not even sure it isn't "Linux" in the sense that I'm not sure it isn't software versus hardware. (I doubt very much that "Linux" is more likely to have such issues than Windows but all OSs have issues some of the time on some machines with some configs...) I just can't think what it could be software wise.
Maybe I should try the reboot force although there isn't much point right now as it is behaving perfectly anyway. Will need to wait until the issue next occurs...
Last edited by cfr (2012-08-29 20:38:33)
I just got my x121e back from the repair center and they changed the motherboard. I clearly told the customer service that it's not a software issue since it shutdown while installing a fresh OS, I also told them that I tried several harddrives which excludes the possibility of a harddrive problem. Apperently they could reproduce the error at the repair center and for the moment I have no issues, the machine runs flawlessly. Bottom line here is that that my machine shut down randomly and apperently there was some hardware issue on the motherboard, I suppose related to power supply for the harddrive...
That sounds like a different issue though I'm glad you got it fixed. Mine doesn't shut down randomly - more an issue on reboot.
Right now, I can't reboot from Arch - it just powers off. But I think that is Arch not hardware as I can reboot fine from finnix.
Have you tried if it happens without acpid?
Maybe that clashes with thinkpad_acpi.
I have also had an unclean-reboot which I have to sort out, if it recurrs. It booted fine again after pulling a USB dongle which was plugged in on reboot. Have you had any USB ports used usually when it happened?
I've usually got a mouse connected but not usually anything else.
I don't honestly think acpid is likely to be conflicting with thinkpad_acpi. Isn't acpid just the interface to the stuff underneath, including what's provided by the kernel module?
And I don't think acpid should be involved at all since systemd is supposed to be managing the reboot etc.
Or do you have some reason to suspect acpid? Just I'm reluctant to try pulling that out without good reason since I just got sleep etc. all working well again following the switch to systemd.
Last edited by cfr (2012-09-20 00:37:06)
Or do you have some reason to suspect acpid?
acpid listens/intercepts power-related events and reboot falls in there. The reason I suggested testing to remove/stop acpid is that here things like lid-close/etc work out-of-the-box with just thinkpad_acpi autoloaded on the same TP model.
Unfortunately laptop mode tools does not. I tested this and if I disable acpid then I end up without any automated control of stuff triggered by switches from and to battery/AC.
I think I'll just have to wait for them to iron out the issues with systemd etc. (I don't think that caused by boot stuttering but I do think it is probably responsible for my current inability to reboot.)
I could, I think, tell KDE to trigger the laptop-mode stuff but I'd rather not because that will only work in KDE and KDE isn't as reliable as acpid anyway. (Assuming KDE doesn't rely on acpid anyway - probably not, I guess.)
I'd like to be able to reboot, of course, but power management is a bigger deal.
Last edited by cfr (2012-09-20 22:21:13)