regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: iwlwifi: loosing connection to AP (regression from 5.4.143) (fwd from b.k.o bug 215401) #forregzbot
Date: Thu, 3 Feb 2022 13:22:07 +0100	[thread overview]
Message-ID: <8be5847a-f123-e488-80cd-5fb02431bece@leemhuis.info> (raw)
In-Reply-To: <b4470632-9209-ce77-937f-656566d333b3@leemhuis.info>

#regzbot invalid: reporter said "it must have been a temporary wifi issue"

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 24.12.21 09:24, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
> 
> Forwarding a regression reported in bugzilla.kernel.org, to ensure
> all the interested parties are aware of it, as quite a few (many?)
> subsystems don't react at all to reports in that bug tracker.
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=215401
> 
>> Martin Mokrejs 2021-12-23 20:25:45 UTC
>>
>> Created attachment 300133 [details] dmesg-5.4.167.txt
>>
>> Hi, I jumped from 5.4.143 to 5.4.167 but the connection to wifi was
>> so unstable I had to reboot to use the old kernel. I never used git
>> bisect and am not sure I have that much time to play with that.
>> However, let me say that I lost about 5x connection to AP. Sooner or
>> later after each situation I disconnected from the AP using nm-applet
>> and re-connected. That has helped for a short while, liek a few
>> minutes, then I again lost network connection. Maybe you can find the
>> event in the dmesg output.
>>
>> Once, for some reason, there is also a stacktrace from the kernel.
>> Why just onceinstead of about 5 times I have no idea.
>>
>> I could provide the same kernel messages supplemented with daemon
>> messages from syslog.
>>
>> Hope this helps to some extent,
> 
> Feel free to either continue discussing this here or in the ticket, I
> don't care.
> 
> To be sure this issue doesn't fall through the cracks unnoticed, I'm
> also adding it to regzbot, my Linux kernel regression tracking bot:
> 
> #regzbot introduced v5.4.143 to v5.4.167
> #regzbot title: net: iwlwifi: frequently loosing connection to AP
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215401
> 
> Reminder: when fixing the issue, please link to this mail and the bug
> entry with a link tag.
> 
> Ciao, Thorsten (wearing his 'Linux kernel regression tracker' hat).
> 
> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
> on my table. I can only look briefly into most of them. Unfortunately
> therefore I sometimes will get things wrong or miss something important.
> I hope that's not the case here; if you think it is, don't hesitate to
> tell me about it in a public reply. That's in everyone's interest, as
> what I wrote above might be misleading to everyone reading this; any
> suggestion I gave thus might sent someone reading this down the wrong
> rabbit hole, which none of us wants.
> 
> BTW, I have no personal interest in this issue, which is tracked using
> regzbot, my Linux kernel regression tracking bot
> (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
> this mail to get things rolling again and hence don't need to be CC on
> all further activities wrt to this regression.
> 
> ---
> Additional information about regzbot:
> 
> If you want to know more about regzbot, check out its web-interface, the
> getting start guide, and/or the references documentation:
> 
> https://linux-regtracking.leemhuis.info/regzbot/
> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
> 
> The last two documents will explain how you can interact with regzbot
> yourself if your want to.
> 
> Hint for reporters: when reporting a regression it's in your interest to
> tell #regzbot about it in the report, as that will ensure the regression
> gets on the radar of regzbot and the regression tracker. That's in your
> interest, as they will make sure the report won't fall through the
> cracks unnoticed.
> 
> Hint for developers: you normally don't need to care about regzbot once
> it's involved. Fix the issue as you normally would, just remember to
> include a 'Link:' tag to the report in the commit message, as explained
> in Documentation/process/submitting-patches.rst
> That aspect was recently was made more explicit in commit 1f57bd42b77c:
> https://git.kernel.org/linus/1f57bd42b77c

      reply	other threads:[~2022-02-03 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  8:24 iwlwifi: loosing connection to AP (regression from 5.4.143) (fwd from b.k.o bug 215401) Thorsten Leemhuis
2022-02-03 12:22 ` Thorsten Leemhuis [this message]

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=8be5847a-f123-e488-80cd-5fb02431bece@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=regressions@lists.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;
as well as URLs for NNTP newsgroup(s).