Return-path: Received: from mail-lb0-f179.google.com ([209.85.217.179]:46452 "EHLO mail-lb0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753527AbaCJNw0 (ORCPT ); Mon, 10 Mar 2014 09:52:26 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 10 Mar 2014 15:52:25 +0200 Message-ID: (sfid-20140310_145233_263400_D8C5CFB3) Subject: Re: wifi driver or USB might leads suspend/resume failure on thinkpad X1 carbon From: Emmanuel Grumbach To: Shuduo Sang Cc: linux-usb , linux-wireless , Tedd Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Mar 10, 2014 at 3:20 PM, Shuduo Sang wrote: > On Mon, Mar 10, 2014 at 6:50 PM, Emmanuel Grumbach wrote: >>>>>> Hi, >>>>>> >>>>>> On Mon, Mar 10, 2014 at 7:05 AM, Shuduo Sang wrote: >>>>>>> Hi, >>>>>>> >>>>>>> Sorry for cross posting. I'm suffering an issue my Thinkpad X1 Carbon >>>>>>> can't resume after suspend recently. I tried many ways including >>>>>>> latest vanilla kernel, latest stable 3.13 and 3.11 kernel but it still >>>>>>> happens. I found it will not happen when I turn off WIFI device or USB >>>>>>> 3.0 in BIOS. So I suspect something need fix in either wifi driver or >>>>>>> USB side. Since Windows 7 works good so I suppose no hardware issue. >>>>>>> Anyone has some ideas to fix it or debug it? >>>>>>> >>>>>>> Thanks, >>>>>>> Shuduo >>>>>>> >>>>>> >>>>>> If you disable WiFi only (without touching USB 3.0 in BIOS), it works? >>>>>> How do you disable WiFi? Rfkill or removing iwlwifi? >>>>>> >>>>> >>>>> I have disabled WIFI device in BIOS, then its suspend/resume works. >>>>> >>>> >>>> Do you have any logs to share? >>>> I supposed you tested 3.13.6 right? >>> >>> Attach dmesg output. If any other log you need, I can capture too. >>> Actually I tried 3.14-rc6, 3.13.6 and 3.11.10. >> >> This looks healthy. >> >> Suspending console(s) (use no_console_suspend to debug) >> >> can you use no_console_suspend? > > Yes, this log is already output from the kernel I compile with > no_console_suspend. Hmm... weird... Don't know how we can debug this further then...