I don't fully understand... sorry if I'm slow. is the problem doing mallocs from an interrupt context or non-atomic mallocs? what's non-atomic about the malloc? how did we get in an interrupt context? Martin Bene wrote: > Another update fort his issue [kernel panic triggered by bmcsensors}: > > The source of the problem are the non-atomic kernel mallocs for device > registration called from an interrupt context - this doesn't seem to be > supported and as observed can crash the kernel. > > A possible solution is to create a kernel thread on initialisation, > leave that thread hanging round while the device scan runs, and finaly > signal the init thread when device scan is complete to finish > initialisation be registing the sensors found during scan. > > A patch implementing such a scheme was created by Yvon JEGOU, I'll post > it here again. > > Thanks, Martin > >
