From: Diego Viola <diego.viola@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled
Date: Wed, 8 Mar 2017 17:40:58 -0300 [thread overview]
Message-ID: <CA+ToGPEyArbKR3QZ8Sz6nQtS8c+aj2K9r9U8cv=hpg==3NGgSQ@mail.gmail.com> (raw)
In-Reply-To: <20170308201558.GA16596@kroah.com>
Hi Greg,
On Wed, Mar 8, 2017 at 5:15 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Wed, Mar 08, 2017 at 03:49:19PM -0300, Diego Viola wrote:
>> It hangs on resume from suspend if I have USB 3.0 enabled on the BIOS,
>> it works fine with ehci_hcd or USB 2.0.
>>
>> The way I reproduce the problem is with this command:
>>
>> $ i3lock && systemctl suspend
>>
>> This is what I see on the screen when it hangs:
>>
>> https://dl.dropboxusercontent.com/u/6005119/dell/IMG_20170308_095000.jpg
>> https://dl.dropboxusercontent.com/u/6005119/dell/IMG_20170307_133928.jpg
>>
>> Some logs:
>>
>> https://dl.dropboxusercontent.com/u/6005119/dell/dmesg1.txt
>> https://dl.dropboxusercontent.com/u/6005119/dell/dmesg2.txt
>>
>> I'm on Arch Linux x86_64, kernel 4.9.11-1-ARCH.
>>
>> I also tried Linux 4.10.1 and I could reproduce this problem there as well.
>>
>> Please let me know if I could provide more info.
>
> Has any previous kernel ever worked properly before? If so, any chance
> you can use 'git bisect' to find the offending commit?
I'm not sure, this is my work machine and I've only started using it
recently (since about a month ago or so).
I will try older kernels and see if I get any different results, I
will report back in any case.
>
> And are you sure you have updated your bios to the latest version?
Yes.
>
> thanks,
>
> greg k-h
Thanks,
Diego
next prev parent reply other threads:[~2017-03-08 20:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 18:49 Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled Diego Viola
2017-03-08 19:59 ` Diego Viola
2017-03-08 20:15 ` Greg KH
2017-03-08 20:40 ` Diego Viola [this message]
2017-03-09 14:11 ` Diego Viola
2017-03-09 17:15 ` Diego Viola
2017-03-14 17:20 ` Diego Viola
2017-03-14 19:15 ` Diego Viola
2017-03-15 14:00 ` Diego Viola
2017-03-16 14:03 ` Ulf Hansson
2017-03-16 15:07 ` Alan Stern
2017-03-16 15:45 ` Diego Viola
2017-03-16 15:51 ` Diego Viola
2017-03-16 16:02 ` Diego Viola
2017-03-16 16:19 ` Diego Viola
2017-03-16 17:14 ` Diego Viola
2017-03-16 18:47 ` Diego Viola
2017-03-17 15:55 ` Diego Viola
2017-03-17 16:24 ` Alan Stern
2017-03-17 16:57 ` Diego Viola
2017-03-17 20:18 ` Diego Viola
2017-03-19 21:29 ` Diego Viola
2017-03-20 14:21 ` Mathias Nyman
2017-03-20 15:39 ` Diego Viola
2017-03-20 16:32 ` Mathias Nyman
2017-03-20 18:27 ` Diego Viola
2017-03-20 23:15 ` Diego Viola
2017-03-21 13:04 ` Diego Viola
2017-03-21 15:29 ` Diego Viola
2017-03-21 22:52 ` Diego Viola
2017-03-22 17:51 ` Mathias Nyman
2017-03-23 17:02 ` Mathias Nyman
2017-03-23 17:12 ` Diego Viola
2017-03-24 13:12 ` [RFT PATCH] xhci: Manually give back cancelled URBs if queuing for cancel fails Mathias Nyman
2017-03-24 16:25 ` Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled Diego Viola
2017-03-27 7:04 ` Mathias Nyman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+ToGPEyArbKR3QZ8Sz6nQtS8c+aj2K9r9U8cv=hpg==3NGgSQ@mail.gmail.com' \
--to=diego.viola@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).