Arch Linux

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

[SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

In Linux Kernel 3.12.0, Whenever I resume my System76 Gazelle Pro 8 laptop from suspend, everything works normal for ~1 second. Then, XFCE freezes up (every time). Keyboard and mouse are unresponsive. Even the Magic SysRq button doesn't work if I enable it beforehand. The only thing I can do is hold the power button.

So, I booted kernel 3.12 again, logged in, and this time ran systemctl suspend. The laptop suspended correctly. But when I woke it up, I was greeted with a kernel dump ending with "Fixing recursive fault but reboot is needed!" The keyboard was unresponsive.

I tried the adding the boot parameter "i915.i915_enable_rc6=0" as suggested in <https://bbs.archlinux.org/viewtopic.php?id=157859>. (My current configuration has "acpi_os_name=Linux acpi_osi=". I admit I haven't tried every combination of parameters.) What does "i915.i915_enable_rc6=0" do?

It looks like this person has a similar problem (except he's running the unstable (14.04) version of Ubuntu):

<https://bugs.launchpad.net/ubuntu/+sour … ug/1247654>

I set up syslog-ng, but no logs are written after the system freezes (and the errors are displayed). The logs only show information up until Linux suspends. Nothing after resuming is logged.

To make this clear, I only have this problem in kernel 3.12. Earlier versions work fine.

Does anyone have any ideas?

Output of inxi -M

Machine:   Mobo: System76 model: Gazelle Professional version: gazp8
           Bios: American Megatrends version: 4.6.5 date: 09/27/2012

From the end of /var/log/kernel.log

Nov 18 13:49:11 wopr kernel: [    4.411440] Bluetooth: HCI device and connection manager initialized
Nov 18 13:49:11 wopr kernel: [    4.411447] Bluetooth: HCI socket layer initialized
Nov 18 13:49:11 wopr kernel: [    4.411449] Bluetooth: L2CAP socket layer initialized
Nov 18 13:49:11 wopr kernel: [    4.411454] Bluetooth: SCO socket layer initialized
Nov 18 13:49:11 wopr kernel: [    4.413164] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Nov 18 13:49:11 wopr kernel: [    4.413166] Bluetooth: BNEP filters: protocol multicast
Nov 18 13:49:11 wopr kernel: [    4.413170] Bluetooth: BNEP socket layer initialized
Nov 18 13:49:11 wopr kernel: [    4.455954] acpi device:4d: registered as cooling_device9
Nov 18 13:49:11 wopr kernel: [    4.455981] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Nov 18 13:49:11 wopr kernel: [    4.456009] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input16
Nov 18 13:49:11 wopr kernel: [    4.456156] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Nov 18 13:49:12 wopr kernel: [    4.697302] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio2/input/input15
Nov 18 13:49:12 wopr kernel: [    5.338702] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
Nov 18 13:49:14 wopr kernel: [    7.467785] r8169 0000:03:00.2 enp3s0f2: link up
Nov 18 13:49:14 wopr kernel: [    7.467798] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0f2: link becomes ready
Nov 18 13:49:42 wopr kernel: [   35.360209] fuse init (API version 7.22)

From /var/log/messages.log

Nov 18 13:49:42 wopr dbus[291]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Nov 18 13:49:42 wopr dbus[291]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Nov 18 13:49:42 wopr dbus-daemon[291]: dbus[291]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
Nov 18 13:49:57 wopr dbus-daemon[291]: dbus[291]: [system] Rejected send message, 6 matched rules; type="method_call", sender=":1.26" (uid=2290 pid=489 comm="xfce4-power-manager --restart --sm-client-id 2e18d") interface="org.freedesktop.NetworkManager" member="Sleep" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=285 comm="/usr/bin/NetworkManager --no-daemon ")
Nov 18 13:50:00 wopr NetworkManager[285]: <info> sleep requested (sleeping: no  enabled: yes)
Nov 18 13:50:00 wopr NetworkManager[285]: <info> sleeping or disabling...
Nov 18 13:50:00 wopr NetworkManager[285]: <info> (wlp2s0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Nov 18 13:50:00 wopr NetworkManager[285]: <info> NetworkManager state is now ASLEEP
Nov 18 13:50:00 wopr NetworkManager[285]: <info> (enp3s0f2): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Nov 18 13:50:00 wopr NetworkManager[285]: <info> (enp3s0f2): deactivating device (reason 'sleeping') [37]
Nov 18 13:50:00 wopr dhcpcd[323]: received SIGTERM from PID 285, stopping
Nov 18 13:50:00 wopr dhcpcd[323]: enp3s0f2: removing interface
Nov 18 13:50:00 wopr dhcpcd[323]: exited
Nov 18 13:50:00 wopr dbus-daemon[291]: dbus[291]: [system] Rejected send message, 6 matched rules; type="method_call", sender=":1.26" (uid=2290 pid=489 comm="xfce4-power-manager --restart --sm-client-id 2e18d") interface="org.freedesktop.NetworkManager" member="Sleep" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=285 comm="/usr/bin/NetworkManager --no-daemon ")
Nov 18 13:50:00 wopr NetworkManager[285]: <info> (enp3s0f2): canceled DHCP transaction, DHCP client pid 323
Nov 18 13:50:00 wopr avahi-daemon[290]: Withdrawing address record for 192.168.1.111 on enp3s0f2.
Nov 18 13:50:00 wopr NetworkManager[285]: <info> Removing DNS information from /usr/bin/resolvconf
Nov 18 13:50:00 wopr avahi-daemon[290]: Leaving mDNS multicast group on interface enp3s0f2.IPv4 with address 192.168.1.111.
Nov 18 13:50:00 wopr avahi-daemon[290]: Interface enp3s0f2.IPv4 no longer relevant for mDNS.
Nov 18 13:50:00 wopr NetworkManager[285]: <info> (enp3s0f2): cleaning up...
Nov 18 13:50:00 wopr NetworkManager[285]: <info> (enp3s0f2): taking down device.
Nov 18 13:50:00 wopr avahi-daemon[290]: Withdrawing address record for fe80::290:f5ff:fee2:2cef on enp3s0f2.
Nov 18 13:50:00 wopr dbus-daemon[291]: dbus[291]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 18 13:50:00 wopr dbus[291]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 18 13:50:00 wopr dbus[291]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.
Nov 18 13:50:00 wopr dbus-daemon[291]: dbus[291]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.
Nov 18 13:50:00 wopr NetworkManager[285]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.
Nov 18 13:50:00 wopr systemd[1]: Starting Sleep.
Nov 18 13:50:00 wopr systemd[1]: Reached target Sleep.
Nov 18 13:50:00 wopr systemd[1]: Starting Suspend...
Nov 18 13:50:00 wopr systemd-sleep[690]: Suspending system...

Workarounds:

• Downgrade to kernel 3.11

• Install linux-lts and use it

Last edited by KlipperKyle (2014-03-08 00:09:22)

harshad1

Member

Registered: 2013-09-02

Posts: 20

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

I can confirm I have this exact bug. It is 100% reproducible with 3.12.

My laptop is a Sager np2252 (essentially an OEM system76 pangolin performance)

I have reverted to 3.11.6 for now and things are nice and stable.

r08

Member

Registered: 2013-11-21

Posts: 9

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

@KlipperKyle
Always wait until the latest kernel patch set has reached to atleast X.XX.6 before you jump the gun to X.XX.0
You avoid bugs like this.

Last edited by r08 (2016-02-21 04:24:20)

siliconmeadow

Member

From: Wolverhampton

Registered: 2011-10-17

Posts: 7

Website

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

Similar thing here - the system freezes after resuming from suspend and the system only responds when forcefully powering it off. I've waded through journalctl and came to the conclusion (eventually) that something funny was happening at the processor level when trying to resume. Yes, "something funny happening at the processor level" is a bona fide technical conclusion, and I'm sticking by it

Downgrading from linux-3.12.1-1-x86_64 to linux-3.12-1-x86_64 didn't sort it, but then downgrading to linux-3.11.6-1-x86_64 did.

Machine:   Mobo: System76 model: Gazelle Professional version: gazp7
           Bios: American Megatrends version: 4.6.5 date: 05/16/2012

harshad1

Member

Registered: 2013-09-02

Posts: 20

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

Perhaps this is specific to sager/clevo/system76 machines?

Since I don't actually have a 'system76' machine, perhaps one you you could send an email to their support people?

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

Since I don't actually have a 'system76' machine, perhaps one you you could send an email to their support people?

Now that final exams are over, I finally got around to hailing System76 support. (They use the Ubuntu Forums.)

<http://ubuntuforums.org/showthread.php?t=2195562>

siliconmeadow

Member

From: Wolverhampton

Registered: 2011-10-17

Posts: 7

Website

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

The latest kernel allows me to suspend and re-awake my System76 gazp7. Yay!

3.12.8-1-ARCH #1 SMP PREEMPT Thu Jan 16 09:16:34 CET 2014 x86_64 GNU/Linux

Last edited by siliconmeadow (2014-01-26 16:09:11)

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

The latest kernel allows me to suspect and re-awake my System76 gazp7. Yay!

3.12.8-1-ARCH #1 SMP PREEMPT Thu Jan 16 09:16:34 CET 2014 x86_64 GNU/Linux

Same here on my gazp8. Thank you, sir, for the good news.

I'll give kernel 3.12.8 a field test for a few days and then forward this to System76.

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

Same here on my gazp8. Thank you, sir, for the good news.

I spoke too soon. When I resume, my Ethernet device mysteriously disappears after several seconds. It will not show in ifconfig, and "ifconfig <device name> up" complains about a nonexistent device. This only happens on kernel 3.12.

@siliconmeadow, will you please confirm whether you experience the same issue?

After poking through "journalctl -b", I found enp3s0f2 started normally (20:53:11), but a few seconds later (20:53:17) the carrier was mysteriously turned off. Then, ntpd deleted the ethernet interface. See <http://sprunge.us/QdeU>.

And when using ifconfig to try to bring the Ethernet device back up: (Note: Wifi works. It's only Ethernet that dies.)

kyle@wopr ~ $ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 208  bytes 15856 (15.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 208  bytes 15856 (15.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.110  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::6236:ddff:fec1:cd98  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 219  bytes 36427 (35.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 199  bytes 132154 (129.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

kyle@wopr ~ $ sudo ifconfig enp3s0f2 up
[sudo] password for kyle: 
enp3s0f2: ERROR while getting interface flags: No such device
kyle@wopr ~ :( $ 

Note: MAC addresses are masked.

siliconmeadow

Member

From: Wolverhampton

Registered: 2011-10-17

Posts: 7

Website

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

I spoke too soon. When I resume, my Ethernet device mysteriously disappears after several seconds. It will not show in ifconfig, and "ifconfig <device name> up" complains about a nonexistent device. This only happens on kernel 3.12.

@siliconmeadow, will you please confirm whether you experience the same issue?

Doh! Same here! Fortunately I don't have a great need for Ethernet at the moment. It never occurred to me that some day I would utter that last sentence.

siliconmeadow

Member

From: Wolverhampton

Registered: 2011-10-17

Posts: 7

Website

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

I spoke too soon. When I resume, my Ethernet device mysteriously disappears after several seconds. It will not show in ifconfig, and "ifconfig <device name> up" complains about a nonexistent device. This only happens on kernel 3.12.

@siliconmeadow, will you please confirm whether you experience the same issue?

Hi,

I just updated to:

Linux damnyank 3.12.9-1-ARCH #1 SMP PREEMPT Sun Jan 26 09:01:37 CET 2014 x86_64 GNU/Linux

and have closed the lid once, re-opened it, and the ifconfig says the I still have eth0. Hopefully you'll find the same?

Cheers,

Richard

siliconmeadow

Member

From: Wolverhampton

Registered: 2011-10-17

Posts: 7

Website

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

Hi,

I just updated to:

Linux damnyank 3.12.9-1-ARCH #1 SMP PREEMPT Sun Jan 26 09:01:37 CET 2014 x86_64 GNU/Linux

and have closed the lid once, re-opened it, and the ifconfig says the I still have eth0. Hopefully you'll find the same?

Cheers,

Richard

Now I spoke to soon! eth0 device is missing after being suspended now.

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

Now I spoke to soon! eth0 device is missing after being suspended now.

I'm still having the same issue with kernel 3.12.9. I'm beginning to think this is an ntpd issue because ntpd is the one deleting the Ethernet interface.

I disabled ntpd before suspending. When resuming, the Ethernet device *was not deleted*.

Here are "journalctl -b" outputs from two test runs: (grep for enp3s0f2 near the end)

1. With ntpd running - <http://sprunge.us/WWMV> - I booted up with Wifi disabled (but Ethernet enabled and plugged in). I logged in and then put the laptop in suspend. I resumed the laptop. enp3s0f2 disappeared (The log says ntpd deleted it.). Then, I turned on Wifi, enabled sshd, and pulled the log.

2. Stopping ntpd before suspend - <http://sprunge.us/dAaW> - I booted up with Wifi disabled (but Ethernet and *ntpd enabled*). I logged in, ran "sudo stop ntpd" (to kill ntpd), and put the laptop in suspend. I resumed the laptop. enp3s0f2 was still present. I enabled sshd, and pulled the log (over Ethernet).

I'll have to investigate ntpd configuration later.

sej7278

Member

Registered: 2014-01-27

Posts: 4

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

just registered to say i've got the same issue on debian jessie/sid on 3.12.6-2 and 3.12.8-1, its nothing to do with ntp as i'm not using it.

on 3.12.6 eth0 wasn't detected at all if a cable wasn't plugged in on boot. on a related note the sdcard reader would hard crash the kernel so had to be blacklisted "blacklist rtsx_pci"

on 3.12.8 eth0 is detected fine on boot regardless of cable state, but it is lost on resume from suspend. sdcard reader no longer crashes, but doesn't work either.

nothing in logs, rtl8111 device is totally gone - doesn't show in lshw, lspci, dmesg etc. rmmod r8169 && modprobe -v r8169 makes no difference.

i don't get keyboard freezes or anything like that.

my device is a zoostorm/clevo laptop: http://www.ebuyer.com/468931-zoostorm-p … -7873-9043

Last edited by sej7278 (2014-01-27 11:59:36)

sej7278

Member

Registered: 2014-01-27

Posts: 4

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

ethernet is still disappearing on resume from suspend with 3.13.4-1

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

ethernet is still disappearing on resume from suspend with 3.13.4-1

Wow! I haven't had time to test, but I will have to examine this problem further.

In the thread in the Ubuntu forums, someone suggested creating a new thread for the disappearing Ethernet issue. I think creating a new thread here in the Arch BBS is also a good idea because (a) the problem we are having is no longer the original recursive fault and (b) Kernel 3.13 is out.

Unless someone is strongly opposed to forking this thread, within the next several days (once I get the chance to test kernel 3.13 on my gazp8) I will create a new thread and link back here.

sej7278

Member

Registered: 2014-01-27

Posts: 4

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

have you got a link to the ubuntu forum thread(s) related to this?

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

have you got a link to the ubuntu forum thread(s) related to this?

See #6: <http://ubuntuforums.org/showthread.php?t=2195562>

I'm probably going to split that one too when I get the chance. (I'll keep you updated.)

siliconmeadow

Member

From: Wolverhampton

Registered: 2011-10-17

Posts: 7

Website

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

I just updated and eth0 seems to be remaining pretty solid, after an hour or so of uptime and the closing of the lid a couple of times.

Linux damnyank 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux

Hope the other folks in this thread find the same.

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

For whatever reason, Ethernet seems to work for me after suspend (enp* is not being removed). (Kernel 3.13.5)

kyle@wopr ~ $ inxi -M
Machine:   Mobo: System76 model: Gazelle Professional version: gazp8
           Bios: American Megatrends version: 4.6.5 date: 09/27/2012
kyle@wopr ~ $ uname -a
Linux wopr 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux
kyle@wopr ~ $ 

@sej7278, will you please post some diagnostics so we can try to debug your issue? Suggestions:

• journalctl -b

• lspci (Are there any changes in the output of lspci before vs. after suspending?)

• Anything unusual you would like to include

sej7278

Member

Registered: 2014-01-27

Posts: 4

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

seems to be fixed in 3.13.5-1, ethernet is still there after suspend

KlipperKyle

Member

Registered: 2013-05-25

Posts: 29

Re: [SOLVED] Kernel 3.12.0: "Recursive fault" upon resuming from suspend

seems to be fixed in 3.13.5-1, ethernet is still there after suspend

Cool! I'll mark this thread as solved.

Thanks everyone for the help and hand-holding!