[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aJQDV5eQTVzVNg9y@linux.gnuweeb.org>
Date: Thu, 7 Aug 2025 08:37:27 +0700
From: Ammar Faizi <ammarfaizi2@...weeb.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Simon Horman <horms@...nel.org>, Oliver Neukum <oneukum@...e.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Netdev Mailing List <netdev@...r.kernel.org>,
Linux USB Mailing List <linux-usb@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Armando Budianto <sprite@...weeb.org>, gwml@...r.gnuweeb.org,
stable@...r.kernel.org, John Ernberg <john.ernberg@...ia.se>
Subject: Re: [PATCH net v2] net: usbnet: Fix the wrong netif_carrier_on()
call placement
On Wed, Aug 06, 2025 at 04:54:36AM +0300, Linus Torvalds wrote:
> Anyway, I've applied Ammar's v3 that ended up the same patch that I also tested,
Yesterday, I synced with your tree, but couldn't boot. Crashed with
this call trace:
https://gist.githubusercontent.com/ammarfaizi2/3ba41f13517be4bae70cde869347d259/raw/0ac09b3e1d90d51c3fed14ca9f837f45d7730f0a/crash.jpg
This morning, I synced with your tree again, still the same result.
I'll try to bisect it and report to approriate subsystem once I get the
first bad commit. I suspect it's related to pci or nvme (based on that
call trace).
--
Ammar Faizi
Powered by blists - more mailing lists