Bug#883294: Problem appears to be solved on 4.16.0-2-amd64

First apologies again for delayed answers. I am running testing which is up to date. On kernel 4.16.0-2-amd64, with command line /boot/vmlinuz-4.16.0-2-amd64 root=UUID=43ae47ae-86fc-43a6-9661-dcf030179dc0 ro tsc=unstable init=/lib/sysvinit/init the problem seems to be resolved. I would close

Bug#883294: Bug 197769 - kernel panic IO-APIC + timer (AMD CPU) from 4.13 onwards

Have you noticed https://bugzilla.kernel.org/show_bug.cgi?id=197769 *Bug 197769* - kernel panic IO-APIC + timer (AMD CPU) from 4.13 onwards seems very similiar to this debian-bug. In this context: > > > - Instead of not using IO-APIC

Bug#883294:

On Thu, Apr 26, 2018 at 08:54:26AM +0200, Romain Perier wrote: > Hello, > > Could you : > > - Retry with linux-image 4.15, that is the current kernel in buster/sid > - Instead of not using IO-APIC completly, could you try to boot with > kernel parameter "no_timer_check" ? I reaaly do apologise

Bug#883294: linux-image-4.13.0-1-amd64: Kernel panic prevents boot: regression (apic)

On Sun, Jul 01, 2018 at 02:57:02AM +0100, Ben Hutchings wrote: > I'm sending these questions to you since Romain mistakenly sent them > only to the bug: > > On Thu, 26 Apr 2018 08:54:26 +0200 Romain Perier > wrote: > > Hello, > > > > Could you : > > > > - Retry with linux-image 4.15, that is

Bug#883294: linux-image-4.13.0-1-amd64: Kernel panic prevents boot: regression (apic)

I'm sending these questions to you since Romain mistakenly sent them only to the bug: On Thu, 26 Apr 2018 08:54:26 +0200 Romain Perier wrote: > Hello, > > Could you : > > - Retry with linux-image 4.15, that is the current kernel in buster/sid (but now 4.16 is current) > - Instead of not

Bug#883294:

Hello, Could you : - Retry with linux-image 4.15, that is the current kernel in buster/sid - Instead of not using IO-APIC completly, could you try to boot with kernel parameter "no_timer_check" ? Does it help ? Thanks, Romain