Hi, On Tue, May 26, 2026 at 07:24:13PM +0200, Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > > On Mon, May 11, 2026 at 01:56:51PM +0200, Salvatore Bonaccorso wrote: > > Forwarding to the BTS: > > > > ----- Forwarded message from "Sicking, F.J. (Floris Jan)" > > <[email protected]> ----- > > > > From: "Sicking, F.J. (Floris Jan)" <[email protected]> > > Date: Sun, 10 May 2026 22:33:04 +0000 > > To: Salvatore Bonaccorso <[email protected]> > > Subject: Re: Bug#1135817: linux-image-6.1.0-45-amd64: multiple failures in > > power management > > Delivered-To: [email protected] > > Message-ID: > > <am5pr09mb80163c19e7b27971878f973987...@am5pr09mb8016.eurprd09.prod.outlook.com> > > > > Hi Salvatore, > > > > See the attached file. > > For one of the kernels I did an extra "make": > > $ make my_defconfig > > $ make -j $(nproc) # gave a kernel > > $ make -j $(nproc) bindeb-pkg > > > > Please let me know if this can be an issue or if there are any other > > issues with the log. > > Hmm, that is very odd since the 'bad commit' points to a driver we do > not even enable, so something went wrong in the bisect. Can you please > redo? You need to pay attention to wait "long enough" for the > suspected 'good cases". The reason is, you will know if things fail, > but if things do not fail it might be possible to not have waited long > enough. So when you have the issue not triggering, let's try to give > it more time before determining if it is "good". > > Can you retry with that?
One followup to that: since we have not seen any messages yet from the problem, might you please as well attach a netconsole so when then problem is hit we might get useful log information? On how to do that: https://docs.kernel.org/networking/netconsole.html#netconsole Can you additionally please provide the list of loaded module on the system? Regards, Salvatore
