On Thu, 14 May 2009, Matt Kowalczyk wrote: > Hello, > > I posted the below message to the apcupsd developers and they responded that > this is a kernel problem. Specifically, the response was: > > Matt Kowalczyk wrote: > > The below taken from dmesg occurs very often. I'm not sure what > > exactly causes it to occur by apcupsd defuncts very quickly and I'm > > left with an unprotected system, > > This is a kernel panic. It is caused by a kernel bug or bad hardware, bad > RAM, bad power supply, etc. > > --Adam > > Below is my initial message, perhaps, this is the right group to report this > issue. > > The below taken from dmesg occurs very often. I'm not sure what exactly causes > it to occur by apcupsd defuncts very quickly and I'm left with an unprotected > system, >From the logs you have provided this seems to happen with 2.6.24 kernel, right? Are you able to reproduce the problem with newer kernels? There were quite a lot of fixes since 2.6.24. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
