bad news: module re-compile is not the issue. The problem came back. And this time I know why. This problem happens when I stop sensors, rmmod the module, suspend2 to disk, resume from the swap image and modprobe the module. After sometime, these messages start appearing in the log. Is there anything that you want me to enable for debugging purposes, so that we can capture more information when it happens next time? I can almost always reproduce it with suspend resume cycle. On 7/9/06, Hans de Goede <j.w.r.degoede at hhs.nl> wrote: > > > > Sunil Kumar wrote: > > Why I expect re-compile to work is that I might have done some kernel > > rebuild with a newer option (I don't remember if I disabled HIGHPTE > > before or after I built abituguru last time) and it is possible that the > > module still loads fine but can't really get initialized the first time. > > > > Ah I see. > > > What is the unit for those timeouts you mentioned? In case I need to go > > there. > > > Number of attempted ISA reads while waiting for a certain response > before giving up. > > > This is the advantage of having it in the kernel tree itself. When is it > > expected to be in kernel mainline? 2.6.17 series? (I can't run mm for > now.) > > > > Its in 2.2.18rc1 > > Regards, > > Hans > > > p.s > > Everyone I'm going on a short vacation till friday so don't expect any > response /replies from me till saturday. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060710/6326e2f4/attachment.html
