From: Kalle Valo <kvalo@kernel.org>
To: Fourhundred Thecat <400thecat@ik.me>
Cc: ath11k@lists.infradead.org
Subject: Re: bizarre network problem on kernel 6.6.4
Date: Tue, 05 Dec 2023 19:04:46 +0200 [thread overview]
Message-ID: <87a5qopolt.fsf@kernel.org> (raw)
In-Reply-To: <3730972c-15fd-04ea-8335-16518bea56e3@ik.me> (Fourhundred Thecat's message of "Tue, 5 Dec 2023 17:43:21 +0100")
Fourhundred Thecat <400thecat@ik.me> writes:
> On 05/12/2023 13.11, Kalle Valo wrote:
>> Fourhundred Thecat <400thecat@ik.me> writes:
>>
>>> I have the most bizarre network problem on my laptop that I have ever
>>> seen, and I don't even know where to start:
>>>
>>> This is lenovo T14s Gen 4, using qualcomm driver ath11k_pci
>>>
>>> Previously I was using kernel 6.6.1 and wireless network was working fine.
>>>
>>> Now I compiled kernel 6.6.4 with identical config, and when I boot it,
>>> wireless network does not work:
>>
>> Did you verify that booting back to 6.6.1 fixes the problem? That would
>> rule out that this isn't due to some external reasons (user space or
>> network)
>>
>> If you can verify that 6.6.1 always works and 6.6.4 always fails I would
>> just try to git bisect the issue. It shouldn't take too long.
>
> yes. I verified multiple times that 6.6.1 works, and 6.6.4 has this problem.
>
> I am not really familiar with git bisect, and I am also not a kernel
> developer.
git bisect is a very useful tool, I recommend learning it as it makes so
much easier to find the culprit for regressions. You don't have to be a
kernel developer, it's enough that you know how to compile and install a
kernel.
Here's one doc I found with google, hopefully it helps:
https://wiki.gentoo.org/wiki/Kernel_git-bisect
Here's one from kernel documentation:
https://docs.kernel.org/admin-guide/bug-bisect.html
> 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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-05 17:04 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 [this message]
2023-12-06 19:15 ` Jeff Johnson
2023-12-09 5:30 ` Fourhundred Thecat
2023-12-11 13:27 ` Kalle Valo
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=87a5qopolt.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=400thecat@ik.me \
--cc=ath11k@lists.infradead.org \
/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