Hi Salvatore.
Thank you for the reply. Before I got to the bisect, the 7.2.12-1 got
out and this version is working again fine regarding the hostapd. 

On Wed, 2026-10-21 at 09:07 +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> Hi Michal,
> 
> On Wed, Oct 21, 2026 at 12:11:43AM +0200, Michal Kaspar wrote:
> > Package: src:linux
> > Version: 7.2.11-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > Afeter kernel upgrade to 7.2.11+deb14-amd64 the hostapd stopped
> > working. When debuging the problem, I fuound the reason is the
> > Mediatek Wireless device failing to set in the AP mode. THe debug
> > information from hostapd below.
> > After reboot to 7.2.9+deb14-amd64 kernel, the problem went off
> > immediately so the changes between these 2 versions must have lead
> > to the problem.
> 
> Sorry for that. Could you please bisect the changes between 7.2.9 and
> 7.2.11 upstream with the following procedure please, so we can
> identify the problemtic change?
> 
>     git clone --single-branch -b linux-7.2.y
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>     cd linux-stable
>     git checkout v7.2.9
>     cp /boot/config-$(uname -r) .config
>     yes '' | make localmodconfig
>     make savedefconfig
>     mv defconfig arch/x86/configs/my_defconfig
> 
>     # test 7.2.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.2.11 to ensure this is "bad"
>     git checkout v7.2.11
>     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.2.9
>     git bisect bad v7.2.11
> 
> 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, try to 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

-- 
Michal Kašpar

Reply via email to