Bug#883938: Sun Fire X4200 M2 too

To: 883938@bugs.debian.org
Subject: Bug#883938: Sun Fire X4200 M2 too
From: "Dr. Nagy Elemér Kár oly" <eknagy@omikk.bme.hu>
Date: Sun, 10 Dec 2017 15:26:33 +0100
Message-id: <[🔎] 20171210142103.M39894@omikk.bme.hu>
Reply-to: "Dr. Nagy Elemér Kár oly" <eknagy@omikk.bme.hu>, 883938@bugs.debian.org
References: <[🔎] 20171209172304.GA2110@noloop.net>

Hi,

Reproduced it on a Sun Fire X4200 M2 too, screenshot attached.

Could we increase the severity to critical like Debian bug #883294? It downed a production server ;(

Downgrading to "3.16.43-2+deb8u5 (2017-09-19)" fixed it.

Elmar

Attachment: sun_x4200m2_too.png
Description: PNG image

Reply to:

References:
- Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
  - From: debbug <debbug.linuximage.debian810@sub.noloop.net>

Prev by Date: Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
Next by Date: Bug#883976: marked as done (nfs-common: Shell script executed by systemd to mount net /home * /var fails)
Previous by thread: Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
Next by thread: Bug#883938: Same problem with KVM
Index(es):
- Date
- Thread