Re: Computer fails to resume from suspend unless I rmmod jme before initiating the suspend
From: Diego Viola <hidden>
Date: 2016-02-12 08:17:25
Also in:
lkml
On Wed, Feb 10, 2016 at 7:36 PM, Diego Viola [off-list ref] wrote:
On Wed, Feb 10, 2016 at 2:19 AM, Diego Viola [off-list ref] wrote:quoted
Hi Guo, I have an x86 computer with this network card: 02:00.0 Ethernet controller: JMicron Technology Corp. JMC260 PCI Express Fast Ethernet Controller (rev 03) Every time I initiate a suspend (systemctl suspend) the machine hangs at resume unless I unload the jme driver. Here is a Call Trace I was able to get after it hanged: <IRQ> tasklet_action+0xb0/0xd0 __do_softirq+0xcf/0x290 irq_exit+0xa3/0xb0 do_IRQ+0x54/0xd0 common_interrupt+0x82/0x82 <EOI> jme_start_irq+0x84/0xa0 [jme] jme_resume+0x12f/0x210 [jme] pci_pm_resume+0x64/0xa0 ? pci_pm_thaw+0x90/0x90 dpm_run_callback+0x4e/0x130 device_resume+0xd3/0x1f0 async_resume+0x1d/0x50 async_run_entry_fn+0x48/0x150 process_one_work+0x14b/0x440 worker_thread+0x48/0x4a0 ? process_one_work+0x440/0x440 kthread+0xd8/0xf0 ? kthread_worker_fn+0x170/0x170 ret_from_fork+0x3f/0x70 ? kthread_worker_fn+0x170/0x170 Please note that I had to type the calltrace above as I don't have a serial cable and netconsole didn't work for me for some reason, so there could be typos I didn't notice. I run Arch Linux (x86-64), my uname is: $ uname -a Linux myhost 4.4.1-2-ARCH #1 SMP PREEMPT Wed Feb 3 13:12:33 UTC 2016 x86_64 GNU/Linux Please let me know if you have any questions or need any other information. Thanks, DiegoI found something interesting, I can suspend/resume just fine when the module is loaded and when I do this: $ ip link set ens34 down When I bring the device up again the hang still occurs. Diego
I have tried to reproduce this problem with the latest git (torvalds/linux.git) and also went back to Linux 3.11 and I still got the hang with both, my plan was to run git bisect, but the problem still occurs. I opened this bug in bugzilla if it's preferred to deal with the problem there: https://bugzilla.kernel.org/show_bug.cgi?id=112351 Thanks, Diego