Bug#916898: linux-image-4.18.0-3-amd64: kernel oops and gdm fails to start

To: Ben Hutchings <ben@decadent.org.uk>
Cc: 916898@bugs.debian.org
Subject: Bug#916898: linux-image-4.18.0-3-amd64: kernel oops and gdm fails to start
From: "Wendy J. Elmer" <webe3vt@aim.com>
Date: Sat, 09 Feb 2019 21:32:21 -0600
Message-id: <[🔎] a1733195a70c0ede7a1af439c9cffc6d7ed6c203.camel@aim.com>
Reply-to: "Wendy J. Elmer" <webe3vt@aim.com>, 916898@bugs.debian.org
In-reply-to: <[🔎] 4daa9afc74d8a84db97ad686ba74f6ce0d62fdf0.camel@decadent.org.uk>
References: <154527331473.6380.2008831977683290486.reportbug@MODebian.gateway.pace.com> <[🔎] 4daa9afc74d8a84db97ad686ba74f6ce0d62fdf0.camel@decadent.org.uk> <154527331473.6380.2008831977683290486.reportbug@MODebian.gateway.pace.com>

yes, 4.19 solved the problem.

Thanks,

On Sun, 2019-02-10 at 01:34 +0000, Ben Hutchings wrote:

Control: forcemerge 914495 -1

On Wed, 19 Dec 2018 20:35:14 -0600 "Brent S. Elmer" <

webe3vt@aim.com

> wrote:

Package: src:linux

Version: 4.18.20-2

Severity: critical

Justification: breaks the whole system

I upgraded to linux-image-4.18.0-3-amd64 and gdm fails to start.  I can get

into the system remotely and get to the journal.  There is a kernel oops in the

journal.

[...]

This looks like a bug that was fixed in 4.19.  Let us know if you're

still seeing the problem.

Ben.

Reply to:

References:
- Bug#916898: linux-image-4.18.0-3-amd64: kernel oops and gdm fails to start
  - From: Ben Hutchings <ben@decadent.org.uk>