Control: tags -1 + moreinfo upstream
Hi
On Sun, Jun 21, 2026 at 08:59:00AM +0900, Atsuhito Kohda wrote:
> Package: src:linux
> Version: 7.0.12-2
> Severity: normal
>
> Dear Maintainer,
>
> * What led up to the situation?
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> * What was the outcome of this action?
> * What outcome did you expect instead?
>
> Since upgrading from **linux-image-7.0.9+deb14-amd64** to **7.0.10**, I have
> been unable to connect to the Internet through a Corega Wi-Fi router.
>
> I expected the problem might be fixed in **7.0.12**, but the issue still
> persists. If I downgrade back to **7.0.9**, the connection works normally
> again.
>
> The Corega router is located in my office at work, so I do not use it all the
> time. However, this problem is causing inconvenience when I need to connect
> through that router.
Since you experience the bug between 7.0.9 and 7.0.10:
Can you please do three things:
1. 7.0.13-1 is out and uploaded to unstable, does this still expose
the problem?
2. 7.1.1-1~exp1 as well contain the bug?
3. most ideal knowing as well what introduces the bug, could you
bisect the changes between 7.0.9 and 7.0.10 upstream to identify
the breaking commit? Following is a short set of instructions on
how to do it.
git clone --single-branch -b linux-7.0.y
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
cd linux-stable
git checkout v7.0.9
cp /boot/config-$(uname -r) .config
yes '' | make localmodconfig
make savedefconfig
mv defconfig arch/x86/configs/my_defconfig
# test 7.0.9 to ensure this is "good"
make my_defconfig
make -j $(nproc) bindeb-pkg
... install the resulting .deb package and confirm problem does not exist
# test 7.0.10 to ensure this is "bad"
git checkout v7.0.10
make my_defconfig
make -j $(nproc) bindeb-pkg
... install the resulting .deb package and confirm problem exists
With that confirmed, the bisection can start:
git bisect start
git bisect good v7.0.9
git bisect bad v7.0.10
In each bisection step git checks out a state between the oldest
known-bad and the newest known-good commit. In each step test using:
make my_defconfig
make -j $(nproc) bindeb-pkg
... install, verify if problem exists
and if the problem is hit run:
git bisect bad
and if the problem doesn't trigger run:
git bisect good
. Please pay attention to always select the just built kernel for
booting, it won't always be the default kernel picked up by grub.
Iterate until git announces to have identified the first bad commit.
Then provide the output of
git bisect log
In the course of the bisection you might have to uninstall previous
kernels again to not exhaust the disk space in /boot. Also in the end
uninstall all self-built kernels again.
Regards,
Salvatore
