Bug#853100: linux-image-4.9.0-1-amd64: Blocked tasks and no X on Latitude E6530

[Thomas Vaughan <tevaughan@gmail.com>]

The problem seems to have disappeared in the kernel that came out today. I attach another /var/log/messages, this one from boot until about five minutes after boot, for linux-image-4.9.0-2-amd64 (4.9.10-1).

It looks to my naive eye as though there is some problem related to nouveau with linux-image-4.9.0-1-amd64 (4.9.6-3), but the problem seems to be resolved with linux-image-4.9.0-2-amd64 (4.9.10-1).

On Sun, Feb 19, 2017 at 4:47 PM, Thomas Vaughan <tevaughan@gmail.com> wrote:

Attached is a copy of /var/log/messages from boot up until just after the time of the first occurrence of the report of a blockage more than 120 seconds.

I notice that there is a new kernel package in unstable today. I'll check that out, too.

On Sat, Feb 18, 2017 at 1:38 PM, Ben Hutchings <ben@decadent.org.uk> wrote:

On Thu, 2017-02-16 at 20:17 -0700, Thomas Vaughan wrote:
> I have attached the output both for linux-3.16 (which seems to have no
> problem) and for linux-4.9.

OK, so you have the VirtalBox and Broadcom wl modules loaded.  I doubt
that they are involved in this bug.

Can you look through /var/log/messages and extract the messages around
the same time as "INFO: task worker/1:1:68 blocked for more than 120
seconds"?

Ben.

--
Ben Hutchings
Knowledge is power.  France is bacon.

--

Thomas E. Vaughan

--

Thomas E. Vaughan

Attachment: messages-2017-Feb-19-2
Description: Binary data