Hello Andreas,
act as AP just fine otherwise?

Can you please test a newer kernel from forky (or trixie backports) and
report back about the behaviour there?
Depending on the issue being reproducible with this newer kernel we have
to report upstream or determine the fixing commit and ask for
backporting to stable.

Best regards
Uwe

Hello Uwe,

sorry about my late response. I thought I will get an email if someone
ask for info but I got none...

I have built an IR connection to my server to switch AP mode on and
off. If the AP is running all seems to work fine (I don't have have
tested this strong). If the AP is shut down the kernel warning
appears always with the trixie 6.12.xy kernel versions.

I also have tested kernel 6.1.0-43 and 7.0.10+deb13-amd64 - no problem
with those!

Best regards
Andreas

Control: fixed -1 7.0.10
Hello Andreas,
gmx considered my mail to be spam :-\ I hope it works better this time.

The obvious options now are:

 - lazy: You continue to use 7.0.y and newer from backports
 - You bisect the issue, identifying the commit that fixes the behaviour
   between 6.12.y and 7.0.y.

If you want to do the latter, please start with bisecting between
packaged versions from https://snapshot.debian.org/package/linux/. The
idea is to find the oldest kernel that doesn't show this behaviour and
the suggested procedure is to start testing e.g. a 6.16 kernel (i.e. one
~ in the middle between 6.12 and 7.0) and depending on this one showing
the issue or not continue between 6.16 and 7.0 or between 6.12 and 6.16.
Then iterate that until you find that oldest kernel image without that
problem.

If anything is unclear, don't hesitate to ask.

If you want to go the lazy path, that's ok, too. But please say so, that
we can close this bug.

Best regards
Uwe