On Sun, 2011-11-27 at 13:29 +0100, axst@users.sourceforge.net wrote: > Hi, > > I hope this line from the log answers your question: > > upgrade linux-image-2.6.32-5-686 2.6.32-38 2.6.32-39 Right. > On Fri, 25 Nov 2011, Ben Hutchings wrote: > > > What was the previous version? > > > All changes are logged to /var/log/dpkg.log, but not the source > > locations. > > Is there a place where I could find out about them so I can eliminate problematic packages > before the upgrade to the next release? If it's the kernel, there's not a whole lot you can do either. (We would like to move to a model where it's easy to keep a known-good version as a fallback, but we're not ready to do that yet.) Version 2.6.32-39 doesn't appear to have any fixes for bugs like the one you described, so this probably is still to be fixed. You said that the system was not completely hung after the 'oops' message, which means the message was probably included in the system log (/var/log/messages or one of the numbered older files). Please can you look for it there and provide the full message (there are start and end markers) plus any other kernel messages from the few minutes before. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity.
Attachment:
signature.asc
Description: This is a digitally signed message part