archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <>
To: Stanislaw Gruszka <>,
	Helmut Schaa <>
Cc: "" <>,
	LKML <>,
	Linux kernel regressions list <>,
	Thomas Mann <>
Subject: [Regression] rt2800usb - Wifi performance issues and connection drops
Date: Sat, 4 Mar 2023 17:24:07 +0100	[thread overview]
Message-ID: <> (raw)

Hi, this is your Linux kernel regression tracker.

I noticed a regression report in As many (most?)
kernel developer don't keep an eye on it, I decided to forward it by
mail. Quoting from :

>  Thomas Mann 2023-03-03 15:12:03 UTC
> After the update of linux to 6.2.x, i get connection drops and bandwidth problems.
> 6.2.1 was completely unusable and 6.2.2 still has bandwidth problems but works a bit better
> The device in use is:
> 13d3:3273 IMC Networks 802.11 n/g/b Wireless LAN USB Mini-Card
> Downgrading the kernel to 6.1.[14,15] fixes the problem and the wifi gets stable again and the available bandwidth increases.
> demsg shows no errors
> [tag] [reply] [−]
> Private
> Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2023-03-04 05:45:33 UTC
> Please attach dmesg [without it most people won't even know which driver is in use for your card]
> [tag] [reply] [−]
> Private
> Comment 2 Thomas Mann 2023-03-04 12:36:45 UTC
> drive in use is rt2800usb
> [tag] [reply] [−]
> Private
> Comment 3 Thomas Mann 2023-03-04 12:38:01 UTC
> Created attachment 303840 [details]
> dmesg output

See the ticket for more details.

[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v6.1..v6.2
#regzbot title: net: wireless: rt2800usb: wifi performance issues and
connection drops
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
If I did something stupid, please tell me, as explained on that page.

             reply	other threads:[~2023-03-04 16:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 16:24 Linux regression tracking (Thorsten Leemhuis) [this message]
2023-03-05 17:25 ` [Regression] rt2800usb - Wifi performance issues and connection drops Thorsten Leemhuis
2023-03-05 22:05   ` Alexander Wetzel
2023-03-07 20:54     ` Alexander Wetzel
2023-03-07 22:31       ` Thomas Mann
2023-03-08  7:13         ` Alexander Wetzel
2023-03-08 10:26           ` Thomas Mann
2023-03-08 12:10             ` Alexander Wetzel
2023-03-08 12:29             ` Thomas Mann
2023-03-08  7:52       ` Felix Fietkau
2023-03-08 11:41         ` Alexander Wetzel
2023-03-08 11:57           ` Felix Fietkau
2023-03-08 12:21             ` Linux regression tracking (Thorsten Leemhuis)
2023-03-08 16:50               ` Alexander Wetzel
2023-03-09  7:59                 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-09 22:13             ` Alexander Wetzel
2023-03-11 21:26               ` Alexander Wetzel
2023-03-12  8:58                 ` Felix Fietkau
2023-03-09 17:00       ` Alexander Wetzel
2023-03-09 17:29         ` Thomas Mann

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).