Bug#1016827: fixed 5.10.0-23-amd64 Bullseye
Hello! I just noticed this bug can't be reproduced anymore since linux 5.10.0-23-amd64 (5.10.179-1). Hopefully this will help to track what was the exact issue and how did it got fixed. Thanks!.
Bug#978043: Bug#1016827: Fixed
Please delete this email and the one I'm quoting; sent to Bug#978043, it was by accident. > Hi > > Well, at least for linux 5.10.162-1 the bug is still present, kernel > panic at the very end of reboot/power off process, can be sorted out > with the 'ccp.dmaengine=0' parameter. > > That's all I can share, the archlinux bug report I quoted didn't had > any activity since feb 2022, and the lkml I also quoted had the same > luck. All I know is that using linux from backports works correctly > with debian's default parameters. > > > (Oops, once again, sending the email to the wrong receipt) > > > > Source-Version: 6.1.15-1 > > > > Hi > > > > On Mon, Apr 10, 2023 at 09:01:13AM -0300, ng wrote: > >> Morning. > >> > >> I just booted into linux 6.1.15-1~bpo11+1 and it was already fixed, > >> no need > >> to use use 'ccp.dmaengine=0' anymore. Great! > >> > >> Bug resolved. > > Thanks, marking it as fixed accordingly, though would be nice to > > better understand the issue and to verify if it get fixed as well in > > the 5.10.y stable series. > > > > Regards, > > Salvatore > >
Bug#1016827: Fixed
Hi Well, at least for linux 5.10.162-1 the bug is still present, kernel panic at the very end of reboot/power off process, can be sorted out with the 'ccp.dmaengine=0' parameter. That's all I can share, the archlinux bug report I quoted didn't had any activity since feb 2022, and the lkml I also quoted had the same luck. All I know is that using linux from backports works correctly with debian's default parameters. (Oops, once again, sending the email to the wrong receipt) Source-Version: 6.1.15-1 Hi On Mon, Apr 10, 2023 at 09:01:13AM -0300, ng wrote: Morning. I just booted into linux 6.1.15-1~bpo11+1 and it was already fixed, no need to use use 'ccp.dmaengine=0' anymore. Great! Bug resolved. Thanks, marking it as fixed accordingly, though would be nice to better understand the issue and to verify if it get fixed as well in the 5.10.y stable series. Regards, Salvatore
Bug#978043: Bug#1016827: Fixed
Hi Well, at least for linux 5.10.162-1 the bug is still present, kernel panic at the very end of reboot/power off process, can be sorted out with the 'ccp.dmaengine=0' parameter. That's all I can share, the archlinux bug report I quoted didn't had any activity since feb 2022, and the lkml I also quoted had the same luck. All I know is that using linux from backports works correctly with debian's default parameters. (Oops, once again, sending the email to the wrong receipt) Source-Version: 6.1.15-1 Hi On Mon, Apr 10, 2023 at 09:01:13AM -0300, ng wrote: Morning. I just booted into linux 6.1.15-1~bpo11+1 and it was already fixed, no need to use use 'ccp.dmaengine=0' anymore. Great! Bug resolved. Thanks, marking it as fixed accordingly, though would be nice to better understand the issue and to verify if it get fixed as well in the 5.10.y stable series. Regards, Salvatore
Bug#1016827: Fixed
Morning. I just booted into linux 6.1.15-1~bpo11+1 and it was already fixed, no need to use use 'ccp.dmaengine=0' anymore. Great! Bug resolved. Have a nice day.