http://bugzilla.suse.com/show_bug.cgi?id=1087873 Bug ID: 1087873 Summary: system stalls or thrashes while quitting firefox and eventually even disconnects WiFi Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: okurz@suse.com QA Contact: qa-bugs@suse.de CC: enadolski@suse.com Depends on: 1017461 Found By: --- Blocker: --- Created attachment 765756 --> http://bugzilla.suse.com/attachment.cgi?id=765756&action=edit system journal showing how the network connection dies while the system stalls, the blocked tasks and the ressurection of network ## Observation On a system with openSUSE Leap 42.3 with linux 4.14.0-1.gc6cd519-default I terminated firefox which was long running and hogging one CPU for yet unknown reason. After asking firefox to terminate I could see the HDD activity LED to light up and stay lit for some time. During this time my desktop clock did not progress and also the system did not react to input except for changing to a tty and calling magic-sysrq sequences. With this I managed to call sysrq-w and sysrq-q to show blocked tasks and current times. In the end after about 2-3 minutes the situation resolved itself and firefox was reported as "Process 24511 (firefox) of user 1000 dumped core." coredumpctl reports a bit of information but unfortunately the coredump itself can not be read: ``` $ sudo coredumpctl gdb 24511 PID: 24511 (firefox) UID: 1000 (okurz) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Tue 2018-04-03 12:18:40 CEST (17min ago) Command Line: /usr/lib64/firefox/firefox Executable: /usr/lib64/firefox/firefox Control Group: / Slice: -.slice Boot ID: a91c1ffc51914ccdaf76eb665dd80e25 Machine ID: 339191be94277a023643ad6956e599fe Hostname: linux-28d6.suse Message: Process 24511 (firefox) of user 1000 dumped core. Cannot retrieve coredump from journal nor disk. Failed to retrieve core: No such file or directory ``` The system journal reports about the running tasks and there is at least one mention of btrfs so I assume it has something to do with either btrfs or the crypt filesystem. Please check the attached logs for details. ## Reproducible Very hard but I have seen similar behavior in cases of processes terminate with SIGSEGV or when a memory leak appears and a process is eventually killed by the OOM killer. I now that I am not running a supported kernel anymore but I have seen similar behavior on the stock openSUSE Leap 42.3 kernel 4.4. ## Expected result System should stay responsive. -- You are receiving this mail because: You are on the CC list for the bug.