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

2017-02-19 Thread Thomas Vaughan
hings 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

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

2017-02-16 Thread Thomas Vaughan
I suppose that the vbox* modules built by way of dkms count as out-of-tree. On Thu, Feb 16, 2017 at 8:17 PM, Thomas Vaughan wrote: > I have attached the output both for linux-3.16 (which seems to have no > problem) and for linux-4.9. > > On Thu, Feb 16, 2017 at 8:01 PM, Ben Hutchi

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

2017-02-16 Thread Thomas Vaughan
I have attached the output both for linux-3.16 (which seems to have no problem) and for linux-4.9. On Thu, Feb 16, 2017 at 8:01 PM, Ben Hutchings wrote: > On Fri, 2017-02-17 at 02:26 +0000, Thomas Vaughan wrote: > > No, I'm using only the free-software drivers. > > > >

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

2017-02-16 Thread Thomas Vaughan
ere was no problem with Linux-4.8; bummer when Linux-4.8 disappeared from the Debian repositories. What counts as out-of-tree? On Thu, Feb 16, 2017 at 20:08 Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Sun, 29 Jan 2017 11:37:16 -0700 Thomas Vaughan > wrote: > > Package:

Bug#853100: Classification of Bug

2017-02-09 Thread Thomas Vaughan
When I submitted this bug report, I classified it as "normal". But I suspect that it is graver than that. My system is currently unusable with the kernel in testing and the kernel in unstable. Only by pulling the ancient kernel from stable can I use my system at all. -- Thomas E. Vaughan

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

2017-01-29 Thread Thomas Vaughan
Package: src:linux Version: 4.9.2-2 Severity: normal Dear Maintainer, Ever since linux-image-4.9.0-amd64 showed up in unstable, I've been unable to use it on my laptop, a Dell Latitude E6530. After boot, the display manager never shows the X login screen. Eventually, I see messages like the fol

Bug#615598: I've seen something like this, too.

2011-03-01 Thread Thomas Vaughan
I've seen a similar problem, with the EDID complaint every so often, on a machine with Intel graphics, with each of 2.6.37-1 and 2.6.37-2. This machine's graphics continue to work. -- Thomas E. Vaughan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsub

Bug#567832: linux-image-2.6.32-trunk-686: "soft lockup - CPU#0 stuck" inside Virtualbox

2010-08-07 Thread Thomas Vaughan
p with no problems. > > Jeff > > -Original Message- > From: Thomas Vaughan [mailto:tevaug...@gmail.com] > Sent: Sunday, August 01, 2010 8:45 PM > To: Fleck, Jeff > Subject: Fwd: linux-image-2.6.32-trunk-686: "soft lockup - CPU#0 stuck" > inside Virtualbox >