Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   bugzilla-daemon@kernel.org
To:     linux-bluetooth@vger.kernel.org
Subject: [Bug 216936] First attempt to upload firmware for Intel Bluetooth
 fails (a timing issue?)
Date:   Tue, 17 Jan 2023 05:58:57 +0000
Message-ID: <bug-216936-62941-khsJBeTCTW@https.bugzilla.kernel.org/>
In-Reply-To: <bug-216936-62941@https.bugzilla.kernel.org/>
References: <bug-216936-62941@https.bugzilla.kernel.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
MIME-Version: 1.0
Precedence: bulk

https://bugzilla.kernel.org/show_bug.cgi?id=3D216936

Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mario.limonciello@amd.com

--- Comment #4 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> Kernel 6.1.4 and previous kernels didn't have the issue.
> I had these errors with 6.1.4 as well.

Which one is it?

If you can find a definitive kernel it really was working 100% of the time a
bisect would be ideal.  But given the ambiguous result you indicated with
6.1.4, I suspect it's not really ever been 100% correct.

Perhaps turning on dynamic debugging for net/bluetooth would be helpful to
identify what about the sequence of init causes -ENODEV.  Naively it looks =
to
me that the main reason this can get returned is if a command is issued whi=
le
the device is actively being unregistered.

So perhaps your userspace is racing?

--=20
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.=