Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752526AbdCAQva (ORCPT ); Wed, 1 Mar 2017 11:51:30 -0500 Received: from mail-ua0-f182.google.com ([209.85.217.182]:34854 "EHLO mail-ua0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750813AbdCAQv3 (ORCPT ); Wed, 1 Mar 2017 11:51:29 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Diego Viola Date: Wed, 1 Mar 2017 12:47:35 -0300 Message-ID: Subject: Re: Dell Inspiron 5558/0VNM2T and suspend/resume problem with r8169 To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1228 Lines: 38 On Wed, Mar 1, 2017 at 12:44 PM, Diego Viola wrote: > My machine (a Dell Inspiron 5558 laptop) fails to resume from suspend > unless I rmmod r8169 first. > > Another workaround is to do this before suspend: > > echo 0 > /sys/power/pm_async > > I've been reproducing the freeze like this: > > $ i3lock && systemctl suspend > > I would have to repeat this at least 5 times for the freeze to occur, > but it seems to be easily reproducible. > > If I don't invoke i3lock, I cannot get the freeze to happen, but it > seems to happen with other lockers also. > > I have tried Alt+SysRq+r and tried to switch to another TTY but the > machine is always unresponsive, which indicates that it's a kernel > panic. > > I have had a similar issue to this about a year ago with the jme > driver and this was the fix: > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/jme.c?id=ee50c130c82175eaa0820c96b6d3763928af2241 > > I haven't tried getting a kernel trace yet, but all seems to indicate > the problem is caused by r8169, at least til now. > > Any ideas, please? > > Thanks, > Diego Sorry, I forgot to mention, I'm on Arch Linux (x86_64), kernel 4.9.11-1-ARCH. Diego