THat said .. if the signature or board name check fails this should not cause any kernel panics requiring a reboot.
On Thursday, 31 August 2017 23:00:08 UTC+2, Michael Brown wrote: > > Not that I know of the pattern has been if the signature check failed the > kernel would panic and talk a lot about about: > > unable to handle kernel null pointer dereference > > A google search revealed the it could be unloading some sort of variable > that had not been initialized. > > I have mostly ignored this issue until I had something more robust and the > phenomena may have been due to the fpga not having enough time to > configure finish and startup before probing started (as the new designs > are somewhat larger, or may take longer time to initialize) > > On Thursday, 31 August 2017 14:37:39 UTC+2, Charles Steinkuehler wrote: >> >> On 8/30/2017 5:14 PM, Michael Brown wrote: >> > Under all circumstances the driver will fail and unload the hal is any >> of >> > the signatures are missing or incorrect >> > and will sometimes cause a kernel panic, this would IMHO be better to >> use >> > time on solving. >> >> Yeah, this is bad and should be fixed. Is there an issue for this in >> the tracker? >> >> -- >> Charles Steinkuehler >> [email protected] >> > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
