From: Kalle Valo <kvalo@kernel.org>
To: Fourhundred Thecat <400thecat@ik.me>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>, ath11k@lists.infradead.org
Subject: Re: bizarre network problem on kernel 6.6.4
Date: Mon, 11 Dec 2023 15:27:58 +0200 [thread overview]
Message-ID: <875y14q36p.fsf@kernel.org> (raw)
In-Reply-To: <446c5c32-01f0-fe0d-0596-254d73f86e6b@ik.me> (Fourhundred Thecat's message of "Sat, 9 Dec 2023 06:30:46 +0100")
Fourhundred Thecat <400thecat@ik.me> writes:
>>>> But I tried checking out linux kernel git repository, switched to tag
>>>> 6.6. and looked inside drivers/net/wireless/ath/ath11k trying to spot
>>>> any change. But git log shows last change on 2023-08-30, whereas kernel
>>>> 6.6.4 was released few days ago
>>>
>>> I assume you were looking at Torvalds' tree only. The release 6.6.4
>>> means that you are using a stable release which are in linux-stable
>>> tree, the gentoo doc above should help more.
>>
>> FWIW it seems that the only changes to ath11k have been trivial:
>>
>> % git log --oneline v6.6.1..v6.6.4 -- drivers/net/wireless/ath/ath11k/
>> e83246ecd3b1 wifi: ath11k: fix gtk offload status event locking
>> 69cede2a5a5f wifi: ath11k: fix htt pktlog locking
>> 21ebb0aba580 wifi: ath11k: fix dfs radar event locking
>> c5b914528e55 wifi: ath11k: fix temperature event locking
>> 2d88afdac295 wifi: ath11k: fix Tx power value during active CAC
>> d412d0ef300f wifi: ath11k: fix boot failure with one MSI vector
>> % git remote -v
>> origin git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
>> (fetch)
>> origin git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
>> (push)
>>
>> Suggest you follow the instructions at the following link and create a
>> kernel bug report:
>> https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
>>
>> Meanwhile I'll build and load 6.6.4 on my laptop.
>
> I have just tried new kernel 6.6.5 and everything works fine !!!
>
> so whatever was the cause, seems to have been fixed between 6.6.4 and 6.6.5
>
> any idea what was the issue?
Heh, for once something which is easy to answer :) The only change in
6.6.5 was this commit:
Revert "wifi: cfg80211: fix CQM for non-range use"
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.6.y&id=9099d0682462e8664c8cbbe8989de65e50f62b17
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-12-11 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 3:13 bizarre network problem on kernel 6.6.4 Fourhundred Thecat
2023-12-05 12:11 ` Kalle Valo
2023-12-05 16:43 ` Fourhundred Thecat
2023-12-05 17:04 ` Kalle Valo
2023-12-06 19:15 ` Jeff Johnson
2023-12-09 5:30 ` Fourhundred Thecat
2023-12-11 13:27 ` Kalle Valo [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=875y14q36p.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=400thecat@ik.me \
--cc=ath11k@lists.infradead.org \
--cc=quic_jjohnson@quicinc.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).