On 03/12/2015 17:19, Jonathan Billings wrote: > On Thu, Dec 03, 2015 at 04:46:10PM +0000, Duncan Brown wrote: >> Here is a couple of pictures, >> >> http://i.imgur.com/Vqvqn1H.jpg >> http://i.imgur.com/WQaz1j9.png >> >> Any use? > So, both of those are just the end of the kernel call trace, > unfortunately, it doesn't show what function actually caused the > panic. That'd be above that text, something you could get from an > attached console. > > The first one looks like its in the middle of allocating an inode for > a file, the second in looking up some dentry during init (just > guessing though), although both seem to be in an allocation event at > the end of an interrupt (EOI), but that's probably just coincidence. I had a feeling that would be the case It's installed on an SSD so it goes past instantly I've taken a video and can just about make out "Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu"
