This has occurred again and although it is not on the most recent kernel
it had a slightly different call stack so I thought I would post the log
just in case they help. This is on 3.0.0-13-generic.
The interesting bit is that every stack has a call to schedule near the
top. This hints to me that
This bug has happened again. This is only the second time, and I'm
really not sure how to replicate it. However there does appear to be a
deadlock (or a crash with a lock held) happening.
This trace has a couple of threads that are a little past
queue_log_writer:
One has a frame like
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
** Attachment added: Kernel log of that session.
https://bugs.launchpad.net/bugs/863736/+attachment/2489780/+files/kernel.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863736
Title:
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863736
Title:
Processes blocked indefinitely in kernel: queue_log_writer+0x8c/0xd0
