mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: russ.weight@linux.dev, gregkh@linuxfoundation.org,
	rafael@kernel.org, linux-kernel@vger.kernel.org,
	masahiroy@kernel.org
Subject: Re: [PATCH] firmware_loader: Use init_utsname()->release
Date: Mon, 26 Feb 2024 17:13:44 +0000	[thread overview]
Message-ID: <cb0c185c-54f8-4b43-856f-685cc5ed3fc4@oracle.com> (raw)
In-Reply-To: <ZdzGF9bxLn3Slbgi@bombadil.infradead.org>

On 26/02/2024 17:10, Luis Chamberlain wrote:
>>> I am running this now, but it does not seem stable on a v6.8-rc5 baseline. I
>>> am seeing hangs. Are there any known issues?
>> I tested next-20240108 and so no issues.
>>
>> Lemme upgrade.
>>
>> Note you also need /lib/udev/rules.d/50-firmware.rules removed if
>> you have it.

I have this:
ubuntu@jgarry-ubuntu-bm5-instance-20230215-1843:~/mnt/linux2$ more 
/lib/udev/rules.d/50-firmware.rules
# stub for immediately telling the kernel that userspace firmware loading
# failed; necessary to avoid long timeouts with 
CONFIG_FW_LOADER_USER_HELPER=y
SUBSYSTEM=="firmware", ACTION=="add", ATTR{loading}="-1"

So I can remove it.

> I don't see any hung tasks on next-20240226. Perhaps its with your
> config that it is triggered.
OK, I'll check again when I get a chance, but I am not so keen on 
checking linux-next in general.

Cheers,
John

  reply	other threads:[~2024-02-26 17:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 14:58 John Garry
2024-02-22 15:53 ` Luis Chamberlain
2024-02-23 14:29   ` John Garry
2024-02-23 15:34     ` John Garry
2024-02-26 16:34     ` Luis Chamberlain
2024-02-26 17:10       ` Luis Chamberlain
2024-02-26 17:13         ` John Garry [this message]
2024-02-27 12:59           ` Luis Chamberlain
2024-02-27 13:02             ` John Garry
2024-02-27 13:50               ` Luis Chamberlain
2024-02-27 13:53                 ` Luis Chamberlain
2024-02-28 12:31                 ` John Garry
2024-02-28 15:18                   ` Luis Chamberlain
2024-02-28 16:12                     ` John Garry

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=cb0c185c-54f8-4b43-856f-685cc5ed3fc4@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=rafael@kernel.org \
    --cc=russ.weight@linux.dev \
    /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®