Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash)

Hello, Please close this case, false alarm, the debian/kernel is OK, appears to be an HW issue that needs a workaround. I've sent a note to linux-kernel@ Jan 5 06:18:52 atom kernel: [295306.524933] pcieport :00:06.0: AER: Corrected error received: :00:06.0 Jan 5 06:18:52 atom kernel: [2

Bug#1060066: linux-image-6.1.0-17-amd64: kernel crash

Package: linux-image-6.1.0-17-amd64 Distribution: Debian Stable Kernel: 6.1.0-17-amd64 I have reverted back to 6.1.0-16-amd64. Currently, I am not using a remote syslog server so the crash dump is in a picture: https://imgur.com/a/0ClFFOw Regards, Justin

Bug#557262: closed by maximilian attems (Re: Bug#557262: Processed: Re: Bug#557262: 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available) - root ca

On Tue, 2 Feb 2010, maximilian attems wrote: On Tue, Feb 02, 2010 at 12:27:43PM -0500, Justin Piszcz wrote: FYI Just to confirm it was not a hardware issue, the host has not crashed since I have stopped running asterisk, definitely a kernel issue. Justin. well if you can reproduce it

Bug#557262: closed by maximilian attems (Re: Bug#557262: Processed: Re: Bug#557262: 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available) - root c

Just to confirm it was not a hardware issue, the host has not crashed since I have stopped running asterisk, definitely a kernel issue. Justin. On Tue, 2 Feb 2010, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the linux-2