>Well, you effectively set it to 0 on all those devices that are not >supported yet. If someone uses such device in production AND something >goes wrong during an update, this would create a frozen device. In the >worst case, someone would even have to travel to it and perform a >power-cycle on-site. How will you address such a case in your user stories?
Yes you are right the hardcoded way is so risky I want to make it clear, We can set a variable that is watchdog_may_fail = 1 at the runtime. Then efibootguard will turn the error_exit to WARNING when this variable is set. Wouldn't we be able to overcome this situation in this way? Erdem Kahraman <[email protected]>, 11 May 2023 Per, 12:21 tarihinde şunu yazdı: > >Well, you effectively set it to 0 on all those devices that are not > >supported yet. If someone uses such device in production AND something > >goes wrong during an update, this would create a frozen device. In the > >worst case, someone would even have to travel to it and perform a > >power-cycle on-site. How will you address such a case in your user > stories? > > Yes you are right the hardcoded way is so risky > > I want to make it clear, > We can set a variable that is watchdog_may_fail = 1 at the runtime. > Then efibootguard will turn the error_exit to WARNING when this variable > is set. > Wouldn't we be able to overcome this situation in this way? > > Jan Kiszka <[email protected]>, 3 May 2023 Çar, 19:08 tarihinde şunu > yazdı: > >> On 03.05.23 17:55, Erdem Kahraman wrote: >> > Great you are right but I am going to send the image to different >> devices. >> > I dont know is it supporting or not. >> > I just want to if it is supporting; yes please enable the watchdog, if >> > it is not please go on. >> >> That case was not in scope for EBG so far. >> >> > >> > In your case there is only one device to use, but it is a generic image >> > for several different devices. >> > I can not be in interactive with device when the image sent to customer. >> > >> > So I can not set the wdog timer as 0 >> >> Well, you effectively set it to 0 on all those devices that are not >> supported yet. If someone uses such device in production AND something >> goes wrong during an update, this would create a frozen device. In the >> worst case, someone would even have to travel to it and perform a >> power-cycle on-site. How will you address such a case in your user >> stories? >> >> Jan >> >> > >> > Thanks >> > 3 Mayıs 2023 Çarşamba tarihinde saat 18:50:02 UTC+3 itibarıyla Jan >> > Kiszka şunları yazdı: >> > >> > On 03.05.23 17:46, Erdem Kahraman wrote: >> > > I want to enable watchdog and I want success watchdog experience >> for >> > > several devices, And I want; if there is unsupported watchdog I >> > want to >> > > say to ebg "never mind please go on" >> > > >> > > But if there is any error like "Cannot probe watchdog >> > (Unsupported)", I >> > > dont want to exit the boot. >> > > >> > > Actually mentioning at code >> > > <https://github.com/siemens/efibootguard/blob/master/main.c#L177 >> > <https://github.com/siemens/efibootguard/blob/master/main.c#L177>>; >> I >> > > dont want to use as "error_exit" maybe it should be "WARNING" ? >> > > >> > > I can pass this error by patching it but is there any other way? >> > >> > If you install EBG on a device that EBG does not support or where >> the >> > firmware already enables the watchdog, just set the timeout to 0, >> and >> > EBG will skip watchdog handling. >> > >> > Jan >> > >> > > >> > > 3 Mayıs 2023 Çarşamba tarihinde saat 18:32:13 UTC+3 itibarıyla Jan >> > > Kiszka şunları yazdı: >> > > >> > > On 03.05.23 17:08, Erdem Kahraman wrote: >> > > > Hello community, >> > > > >> > > > I want to use the efibootguard's watchdog by using a generic >> > device. >> > > > >> > > > There is too different hardwares and I want to activate the >> > > watchdog of >> > > > ebg if it is supporting. >> > > > >> > > > But when I test it, if the watchdog device not existing or not >> > > > supporting by ebg, the boot sequence gives error and exitting. >> > > > >> > > > Is there any way to pass error if there is no watchdog or not >> > > supported >> > > > watchdog? >> > > >> > > I'm not yet sure what exactly your are looking for, some >> > recommendation >> > > on how to debug a not-yet-working own driver in EBG? Or a better >> > > understanding how EBG is matching a driver with the found >> hardware? >> > > >> > > Jan >> > > >> > > -- >> > > Siemens AG, Technology >> > > Competence Center Embedded Linux >> > > >> > > -- >> > > 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 [email protected] >> > > <mailto:[email protected]>. >> > > To view this discussion on the web visit >> > > >> > >> https://groups.google.com/d/msgid/efibootguard-dev/15d7dcfc-906d-4b16-9930-e60a73efaff4n%40googlegroups.com >> < >> https://groups.google.com/d/msgid/efibootguard-dev/15d7dcfc-906d-4b16-9930-e60a73efaff4n%40googlegroups.com> >> < >> https://groups.google.com/d/msgid/efibootguard-dev/15d7dcfc-906d-4b16-9930-e60a73efaff4n%40googlegroups.com?utm_medium=email&utm_source=footer >> < >> https://groups.google.com/d/msgid/efibootguard-dev/15d7dcfc-906d-4b16-9930-e60a73efaff4n%40googlegroups.com?utm_medium=email&utm_source=footer >> >>. >> > >> > -- >> > Siemens AG, Technology >> > Competence Center Embedded Linux >> > >> > -- >> > 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 [email protected] >> > <mailto:[email protected]>. >> > To view this discussion on the web visit >> > >> https://groups.google.com/d/msgid/efibootguard-dev/592af421-2e69-4e9c-b1ca-585b9aa2cb9fn%40googlegroups.com >> < >> https://groups.google.com/d/msgid/efibootguard-dev/592af421-2e69-4e9c-b1ca-585b9aa2cb9fn%40googlegroups.com?utm_medium=email&utm_source=footer >> >. >> >> -- >> Siemens AG, Technology >> Competence Center Embedded Linux >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/CALk5RRsjsH-nYvvASOz%3DiobVr%3DmhCLOjzrdNa4O0j%2BqjMxN5qw%40mail.gmail.com.
