On Wed, Sep 13, 2017 at 05:03:32PM +0300, Mathias Nyman wrote:
> On 07.09.2017 18:16, Greg KH wrote:
> > On Thu, Sep 07, 2017 at 09:12:53AM -0600, Jose Marino wrote:
> > > I have tested Mathias' patch on top of v4.13 and it fixes the problem. I
> > > was
> > > able to suspend/resume a few times wi
On 07.09.2017 18:16, Greg KH wrote:
On Thu, Sep 07, 2017 at 09:12:53AM -0600, Jose Marino wrote:
I have tested Mathias' patch on top of v4.13 and it fixes the problem. I was
able to suspend/resume a few times with no kernel panics.
Yeah! Thanks for testing. Mathias, care to send me a "real"
On Thu, Sep 07, 2017 at 09:12:53AM -0600, Jose Marino wrote:
> I have tested Mathias' patch on top of v4.13 and it fixes the problem. I was
> able to suspend/resume a few times with no kernel panics.
Yeah! Thanks for testing. Mathias, care to send me a "real" patch for
this so I can get it to Li
I have tested Mathias' patch on top of v4.13 and it fixes the problem. I
was able to suspend/resume a few times with no kernel panics.
Jose
On 09/07/2017 08:09 AM, Mathias Nyman wrote:
On 07.09.2017 14:59, Mathias Nyman wrote:
On 07.09.2017 12:23, Greg KH wrote:
On Wed, Sep 06, 2017 at 10:04
On 07.09.2017 14:59, Mathias Nyman wrote:
On 07.09.2017 12:23, Greg KH wrote:
On Wed, Sep 06, 2017 at 10:04:08AM -0600, Jose Marino wrote:
The bug is still present in kernel 4.13. The panic logs look pretty much the
same as with 4.12.4. I have attached the pstore and journald messages to the
bu
On 07.09.2017 12:23, Greg KH wrote:
On Wed, Sep 06, 2017 at 10:04:08AM -0600, Jose Marino wrote:
The bug is still present in kernel 4.13. The panic logs look pretty much the
same as with 4.12.4. I have attached the pstore and journald messages to the
bugzilla bug report just in case.
I reverted
On Wed, Sep 06, 2017 at 10:04:08AM -0600, Jose Marino wrote:
> The bug is still present in kernel 4.13. The panic logs look pretty much the
> same as with 4.12.4. I have attached the pstore and journald messages to the
> bugzilla bug report just in case.
>
> I reverted commit 5cc9b698a494827 on to
The bug is still present in kernel 4.13. The panic logs look pretty much
the same as with 4.12.4. I have attached the pstore and journald
messages to the bugzilla bug report just in case.
I reverted commit 5cc9b698a494827 on top of v4.13 and I can confirm that
it fixes the problem.
Jose
On
I have not tested 4.13 yet. I'll try to do that today and report back.
Jose
On 09/06/2017 01:16 AM, Greg KH wrote:
On Tue, Sep 05, 2017 at 03:11:40PM -0600, Jose Marino wrote:
Hi,
I found a way to reliably trigger this bug:
- Boot laptop
- Plug in dock (with external display connected to dock)
On Tue, Sep 05, 2017 at 03:11:40PM -0600, Jose Marino wrote:
> Hi,
> I found a way to reliably trigger this bug:
> - Boot laptop
> - Plug in dock (with external display connected to dock)
> - Send output to external display
> - Suspend
>
> I did a bisect between 4.12.3 and 4.12.4 and here is the r
Hi,
I found a way to reliably trigger this bug:
- Boot laptop
- Plug in dock (with external display connected to dock)
- Send output to external display
- Suspend
I did a bisect between 4.12.3 and 4.12.4 and here is the result:
5cc9b698a494827b15f74ef70a31d7911d00e52a is the first bad commit
comm
I'm running archlinux on a Dell XPS15 9550 and I connect it to a TB16
thunderbolt dock. Connected to the dock I have a 4k external display and
a USB logitech transmitter for my wireless keyboard and mouse.
The TB16 dock is a finicky beast and doesn't currently work 100% with
linux. However, if
12 matches
Mail list logo
