Ingo Molnar wrote: >A BUG_ON() has a (much) lower likelyhood of being reported back - for >most users it is a "X just hung hard, there was nothing in the syslog, i >had to switch back to the older kernel" experience, and they do not have >a serial console to hook up (newer hardware often doesnt even have a >serial port). With the WARN_ON()s we have a _chance_ that despite the >seriousness of the bug, the message makes it to the syslog, until the >system comes to a screeching halt due to side-effects of the bug. > >in that sense i am part of the problem: i was adding WARN_ON()s that >werent true 'warnings' but 'bugs'. So i'd very much like to fix that >problem, but i'd also like to solve the (very serious and existing) >problem of BUG_ON()s making it less likely to get bugs reported back. > > > There is a fundamental problem in getting a decent log to debug a crashed kernel. Maybe we should take a hint from Solaris. If the kernel crashes Solaris dumps core to swap and sets a flag. At the next boot this image is copied to /var/adm/crashdump where it is preserved for future debugging. Obviously swap needs to be larger than core, but this is usually the case.
On Sun machines this is fairly easy because the dump can be performed by the OBP, on other architectures it may be more difficult to still have enough working kernel to achieve the dump after a kernel panic. Just a thought ....... ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
