Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 03 Dec 2017 20:11:07 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 224059] LOR or deadlock in em0 when resuming from suspend
Message-ID:  <bug-224059-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224059

            Bug ID: 224059
           Summary: LOR or deadlock in em0 when resuming from suspend
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: zeising@FreeBSD.org

Created attachment 188497
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188497&action=
=3Dedit
Output from pciconf -lvbc

I get a lock or LOR or similar when resuming from suspend with the network
cable plugged in. This is on a Lenovo Thinkpad X270.
The machine resumes fine, but after a little while (minutes, if not less) t=
he
machine freezes.  I can feel it get warm and the fans spin, as if the CPU is
working 100%.  It feels like the lockup happens once there's traffic on the=
 NIC
after the resume.  Suspend/resume when not using the NIC works fine (such as
when using WiFi).
There is nothing on the screen when this happens, the screen just freezes in
the way it was, with no reaction on keyboard input and nothing on the conso=
le.=20
When I reboot, however, there is the following in /var/log/messages, which =
is
what led me to em0.

kernel: reversal:
kernel: em0:tx(0):callo (em0:tx(0):callo) @ /usr/src/sys/kern/kern_mutex.c:=
182
kernel: /usr/src/sys/net/iflib.c:2143
kernel: backtrace:
kernel: #0 0xffffffff805a3e93 at witness_debugger+0x73
kernel: #1 0xffffffff805a3d12 at witness_checkorder+0xe02
kernel: #2 0xffffffff8051fd6c at __mtx_lock_flags+0x9c
kernel: #3 0xffffffff80653789 at iflib_timer+0x149
kernel: #4 0xffffffff8055856c at softclock_call_cc+0x14c
kernel: #5 0xffffffff8055892c at softclock+0x7c
kernel: #6 0xffffffff805046a9 at intr_event_execute_handlers+0x99
kernel: #7 0xffffffff80504d96 at ithread_loop+0xb6
kernel: #8 0xffffffff80501ae4 at fork_exit+0x84
kernel: #9 0xffffffff8087718e at fork_trampoline+0xe

System is:
FreeBSD garnet.daemonic.se 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r325963M: S=
at
Nov 18 14:01:30 CET 2017=20=20=20=20
root@garnet.daemonic.se:/usr/obj/usr/src/amd64.amd64/sys/GARNET  amd64

Attached is also output from pciconf -lvbc

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224059-8>