lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <661459dd-67d0-4e1c-bb28-9adf1417f660@panix.com>
Date: Fri, 14 Feb 2025 09:39:33 -0800
From: Kenneth Crudup <kenny@...ix.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>, Me <kenny@...ix.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>, ilpo.jarvinen@...ux.intel.com,
 Bjorn Helgaas <bhelgaas@...gle.com>, Jian-Hong Pan <jhp@...lessos.org>,
 linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
 Niklāvs Koļesņikovs <pinkflames.linux@...il.com>,
 Andreas Noever <andreas.noever@...il.com>,
 Michael Jamet <michael.jamet@...el.com>,
 Yehezkel Bernat <YehezkelShB@...il.com>, linux-usb@...r.kernel.org
Subject: Re: diagnosing resume failures after disconnected USB4 drives (Was:
 Re: PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac))


This is excellent news that you were able to reproduce it- I'd figured 
this regression would have been caught already (as I do remember this 
working before) and was worried it may have been specific to a 
particular piece of hardware (or software setup) on my system.

I'll see what I can dig up on my end, but as I'm not expert in these 
subsystems I may not be able to diagnose anything until your return.

I also saw some DRM/connected fixes posted to Linus' master so maybe one 
of them corrects this new display-crash issue (I'm not home on my big 
monitor to be able to test yet).

-Kenny

On 2/14/25 08:29, Mika Westerberg wrote:
> Hi,
> 
> On Thu, Feb 13, 2025 at 11:19:35AM -0800, Kenneth Crudup wrote:
>>
>> On 2/13/25 05:59, Mika Westerberg wrote:
>>
>>> Hi,
>>
>> As Murphy's would have it, now my crashes are display-driver related (this
>> is Xe, but I've also seen it with i915).
>>
>> Attached here just for the heck of it, but I'll be better testing the NVMe
>> enclosure-related failures this weekend. Stay tuned!
> 
> Okay, I checked quickly and no TB related crash there but I was actually
> able to reproduce hang when I unplug the device chain during suspend. I did
> not yet have time to look into it deeper. I'm sure this has been working
> fine in the past as we tested all kinds of topologies including similar to
> this.
> 
> I will be out next week for vacation but will continue after that if the
> problem is not alraedy solved ;-)
> 

-- 
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange 
County CA


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ