From: Genes Lists <lists@sapience.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, johanneswueller@gmail.com
Subject: Re: 6.9.3 Hung tasks
Date: Thu, 30 May 2024 09:36:45 -0400 [thread overview]
Message-ID: <15a0bbd24cd01bd0b60b7047958a2e3ab556ea6f.camel@sapience.com> (raw)
In-Reply-To: <9d189ec329cfe68ed68699f314e191a10d4b5eda.camel@sapience.com>
[-- Attachment #1.1: Type: text/plain, Size: 213 bytes --]
On Thu, 2024-05-30 at 08:53 -0400, Genes Lists wrote:
>
>
This report for 6.9.1 could well be the same issue:
https://lore.kernel.org/lkml/e441605c-eaf2-4c2d-872b-d8e541f4cf60@gmail.com/
--
Gene
[-- Attachment #1.2: Type: text/html, Size: 891 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-30 13:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 12:53 Genes Lists
2024-05-30 13:36 ` Genes Lists [this message]
2024-05-30 14:04 ` Russell King (Oracle)
2024-05-30 16:23 ` Genes Lists
2024-05-31 8:39 ` Hung tasks due to a AB-BA deadlock between the leds_list_lock rwsem and the rtnl mutex (was: 6.9.3 Hung tasks) Linux regression tracking (Thorsten Leemhuis)
2024-05-31 9:50 ` Hung tasks due to a AB-BA deadlock between the leds_list_lock rwsem and the rtnl mutex Hans de Goede
2024-05-31 10:22 ` Hans de Goede
2024-06-01 20:05 ` Hans de Goede
2024-05-31 11:55 ` Genes Lists
2024-05-31 12:54 ` Andrew Lunn
2024-05-31 13:11 ` Hans de Goede
2024-05-31 13:29 ` Andrew Lunn
2024-05-31 13:36 ` Hans de Goede
2024-06-06 12:01 ` Hans de Goede
2024-06-06 13:12 ` Andrew Lunn
2024-06-06 13:39 ` Jakub Kicinski
2024-06-06 14:25 ` Genes Lists
2024-06-07 10:22 ` Hans de Goede
2024-06-07 11:27 ` Genes Lists
2024-06-07 10:19 ` Hans de Goede
2024-06-24 19:57 ` Heiner Kallweit
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=15a0bbd24cd01bd0b60b7047958a2e3ab556ea6f.camel@sapience.com \
--to=lists@sapience.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=johanneswueller@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®