FS#49451 - [linux] 4.6.x status of AC-plug changes -> systemd/complete system hangs and printk messages dropped

Attached to Project: Arch Linux
Opened by Felix Hipp (flix) - Monday, 23 May 2016, 17:07 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 03 October 2017, 15:09 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
device: toshiba l775d
when AC is plugged in or plugged out, then the system hangs, terminal dropps printk messages by watchdog saying, that cpu#3 stuck for 23s [systemd-journal]
then systemd takes in "top" 100% cpu
i have to crash the computer and boot again.
the problem came, when i updated/made 'pacman -Syu' a week ago. Before that i had never problems with that.
hope that will help others and me :-)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 03 October 2017, 15:09 GMT
Reason for closing:  Fixed
Comment by Felix Hipp (flix) - Monday, 23 May 2016, 17:09 GMT
plugged in/plugged out means, when the status of the plug changes. if plugged in on boot and i unplug it, it freezes, and the other way around same thing....
Comment by Dave Reisner (falconindy) - Monday, 23 May 2016, 17:23 GMT
No package versions, no precise logs... What is systemd doing while it's consuming 100% CPU? A backtrace or even an strace would be useful...
Comment by Felix Hipp (flix) - Monday, 23 May 2016, 17:29 GMT
sry i'm not that familiar with that. i have a 64bit system and the newest update. where can i find the logs? every time when the system hangs, i cant do anything and after the reboot i cant find any logs.... any idea where i can find them?
Comment by Felix Hipp (flix) - Monday, 23 May 2016, 17:53 GMT
here is the strace log file...after a quarter of the file i unplugged the device to see what happened
   strace (300.6 KiB)
Comment by Felix Hipp (flix) - Monday, 23 May 2016, 18:03 GMT
ok found out that the error message from strace is the same as the one coming when systemd-journald restarts. found a lot of this with google but no solution.
originally it's like: "epipe: broken pipe"
i really hope that anyone has an idea! im a little bit desperately...
Comment by Dave Reisner (falconindy) - Monday, 23 May 2016, 18:16 GMT
If you repeat the strace with something like -s 200, you'll be able to see the whole ACPI message that the kernel is barfing at you.

Seems like a hardware/kernel problem...
Comment by Felix Hipp (flix) - Monday, 23 May 2016, 18:20 GMT
here's the new file
   strace (29.9 KiB)
Comment by Dave Reisner (falconindy) - Monday, 23 May 2016, 18:32 GMT
ACPI Error: No handler or method for GPE 0A, disabling event (20160108/evgpe-790)

I don't know what that means, but it seems like it might be https://bugzilla.kernel.org/show_bug.cgi?id=114201

There's a patch, but it's not clear it's been merged into linux-next yet.
Comment by Felix Hipp (flix) - Monday, 23 May 2016, 18:50 GMT
thank you very much! i found this http://www.spinics.net/lists/linux-watchdog/msg09165.html but i'm not sure how to apply the patch. i found an entry in the wiki but to be honest i don't understand it. what do they mean saying " Add an entry to the source array of the PKGBUILD for the patch file,"? (https://wiki.archlinux.org/index.php/Patching_in_ABS)
Comment by mattia (nTia89) - Monday, 02 October 2017, 20:28 GMT
is this issue still valid or latest kernel already contain the patch?
Comment by Eli Schwartz (eschwartz) - Monday, 02 October 2017, 22:46 GMT
tpowa, according to the linked upstream bug, this was fixed in 4.5 https://patchwork.kernel.org/patch/9142277/ but afterwards you modified the Summary to reference 4.6.x ???

Is this not the same issue?
Comment by Felix Hipp (flix) - Tuesday, 03 October 2017, 14:59 GMT
sry, no issues anymore...
requesting closure

Loading...