Okay TCO_RLD probably doesn't matter, it's TCO1_CNT_NO_REBOOT and TCO_TMR_HLT_MASK of TCO1_CNT that are not set in ebg but set in Linux driver.
On Tuesday, November 28, 2023 at 10:15:15 AM UTC+1 Root Mailer wrote: > Finally I have the same dump for the Linux driver: > > TCO_RLD: 0x4 > > TCOv1_TMR: 0x0 > TCO_DAT_IN: 0x0 > TCO_DAT_OUT: 0x0 > TCO1_STS: 0x0 > TCO2_STS: 0x0 > TCO1_CNT: 0x1801 > TCO2_CNT: 0x8 > TCOv2_TMR: 0x32 > > So apparently there is something wrong in TCO_RLD and/or TCO1_CNT. > > On Wednesday, November 22, 2023 at 2:53:12 PM UTC+1 Jan Kiszka wrote: > >> On 22.11.23 11:09, Root Mailer wrote: >> > As a first step I dumped the registers at the end of the init() >> function >> > here: >> > >> > >> https://github.com/siemens/efibootguard/blob/master/drivers/watchdog/itco.c#L341 >> >> > >> > Result: >> > >> > TCO_RLD: 0x64 >> > TCOv1_TMR: 0x0 >> > TCO_DAT_IN: 0x0 >> > TCO_DAT_OUT: 0x0 >> > TCO1_STS: 0x0 >> > TCO2_STS: 0x0 >> > TCO1_CNT: 0x1000 >> > TCO2_CNT: 0x8 >> > TCOv2_TMR: 0x64 >> > >> > As I did not find the register documentation from Intel yet, I can only >> > compare that to the one of the kernel watchdog. Maybe you already have >> a >> > hint. >> >> Not yet without digging into all the details. But do you happen to have >> the same dump for the Linux driver? >> >> Jan >> >> -- >> Siemens AG, Technology >> Linux Expert Center >> >> -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to efibootguard-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/9162e36f-2969-4a72-9d76-54f219cc9f32n%40googlegroups.com.
