General protection fault after resuming from hibernate

habitue · 2015-01-26 18:01:59

I've been dealing with this for months, and recently came to the conclusion it was power state related in some way.

Sometimes, when plugging my power cord in, (not when removing it), my laptop sometimes puts my harddrive into read-only mode, making the computer pretty useless for a while. You may not notice immediately since anything in ram still works until it tries to access the disk.

I know it's unlikely someone knows what's going on right off the bat, but I really need help figuring out how to diagnose it. No logs get written because the harddrive can't be written to when it happens. And I can't do anything in a shell because it tries to access the disk in the course of normal operations.

Ideas welcome! I have a lenovo X1 carbon (gen 2) if that's any use. I've updated my bios to 1.15 to avoid the hang issue it has.

[edit:below I determined the problem was caused by a general protection fault upon resuming from hibernate. the title was changed to reflect that]

Last edited by habitue (2015-01-26 19:11:13)

jasonwryan · 2015-01-26 18:06:10

What power saving utilities/settings are you using?

habitue · 2015-01-26 18:24:56

I have laptopmode tools. So, after I typed out my question, the obvious popped into my head "if the disk is unwriteable, and you can reproduce the issue by plugging in, why not tail journalctl first, and then trigger it".

So I did, and I took pictures of the error messages with my phone.

Seems that laptopmode tools is remounting the harddrive (to answer your question). and the disk has bad inodes, so to protect it the OS is mounting it read-only. So I forced fsck on reboot, and now Ican't get the issue to occur again.

The problem is, how did the drive get these bad inodes to begin with? I remember figuring this out 6 months or so ago, and doing fsck, and the problems stopped for a while. But I don't know what caused the issue. Maybe resuming from hibernate? not sure. For now I am going to turn off laptopmode remounting. I have an SSD so it's less important.

habitue · 2015-01-26 18:31:38

Ok, so following on my hunch that it was hibernate related, I tried resuming from hibernate. Upon resume, I got a black screen, and when I rebooted the kernel param for fsck forced it to clean the journal and clear unused inodes. So, it seems the real issue is that my hibernate setup is causing problems and is leaving the disk in a bad state, and I didn't have my boot process causing an fsck to clean up the bad state. It only noticed this when laptopmode tools forced a remount.

Now I need to debug hibernate. Any ideas? I get a black screen, so I can't even really use the "take a picture with your phone" strategy.

habitue · 2015-01-26 18:46:52

Caught a general protection fault:

https://www.dropbox.com/s/y6xuraplldple … t.jpg?dl=0

Last edited by habitue (2015-01-26 18:47:09)

alphaniner · 2015-01-26 18:52:40

Since the thread has changed focus, you should either change the title or mark this thread as solved and start a new one. IMO new the latter would be best, but maybe wait for jwr to chime in.

habitue · 2015-01-26 19:09:53

I'll switch the title, since it's changed focus to the actual underlying problem

Arch Linux

#1 2015-01-26 18:01:59

General protection fault after resuming from hibernate

#2 2015-01-26 18:06:10

Re: General protection fault after resuming from hibernate

#3 2015-01-26 18:24:56

Re: General protection fault after resuming from hibernate

#4 2015-01-26 18:31:38

Re: General protection fault after resuming from hibernate

#5 2015-01-26 18:46:52

Re: General protection fault after resuming from hibernate

#6 2015-01-26 18:52:40

Re: General protection fault after resuming from hibernate

#7 2015-01-26 19:09:53

Re: General protection fault after resuming from hibernate

Board footer