From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: enc0der <enc0der@gmail.com>, Stanislaw Gruszka <stf_xl@wp.pl>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: rt8000usb driver issue (maybe interaction with other drivers)
Date: Wed, 4 Oct 2023 06:44:52 +0200 [thread overview]
Message-ID: <ac755d6d-7b3e-45b7-bd1f-e2c79de9d8eb@leemhuis.info> (raw)
In-Reply-To: <CAEXpi5StYwujiTaH2_5PE9Hg_cgzAEtBuFxfgVxEJvbqRNv_4A@mail.gmail.com>
On 04.10.23 03:34, enc0der wrote:
>
> [ 1542.248686] CPU: 3 PID: 29 Comm: ksoftirqd/3 Tainted: G W
> OE 5.10.120-tegra #1
FWIW, 5.10.120 is ancient from the upstream perspective. And I assume
that "-tegra" indicates that this is a vendor kernel that most likely is
heavily patched -- and those changes might be the reason for the
problem. Therefore you should report this to your vendor. See "Make sure
you're using the upstream Linux kernel" in
https://docs.kernel.org/admin-guide/reporting-issues.html for details.
If you want help from the upstream Linux kernel developers, please
reproduce the problem with latest mainline.
Ciao, Thorsten
next prev parent reply other threads:[~2023-10-04 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEXpi5Rd6Y4umKOWRsCjX0kit=W5ZrVhn=MuRkyvJPwmjjDVnA@mail.gmail.com>
2023-10-01 5:12 ` Bagas Sanjaya
2023-10-01 5:33 ` enc0der
2023-10-01 5:53 ` Bagas Sanjaya
2023-10-03 5:47 ` Kalle Valo
2023-10-02 18:50 ` Stanislaw Gruszka
2023-10-03 0:01 ` Bagas Sanjaya
2023-10-04 1:34 ` enc0der
2023-10-04 4:44 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-10-04 18:28 ` Stanislaw Gruszka
2023-10-05 18:08 ` enc0der
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=ac755d6d-7b3e-45b7-bd1f-e2c79de9d8eb@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=enc0der@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stf_xl@wp.pl \
/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®