Processed: Re: Bug#883938: Workaround available

To: Bernhard Schmidt <berni@birkenwald.de>
Cc: debian-kernel@lists.debian.org
Subject: Processed: Re: Bug#883938: Workaround available
From: "Debian Bug Tracking System" <owner@bugs.debian.org>
Date: Mon, 11 Dec 2017 08:06:04 +0000
Message-id: <[🔎] handler.s.B883938.151297938815838.transcript@bugs.debian.org>
References: <[🔎] 20171211080303.3knykh4q3ir2op52@fliwatuet.svr02.mucip.net> <[🔎] 20171209172304.GA2110@noloop.net>

Processing control commands:

> summary -1 Seems two affect machines with more than one socket. Workaround: set maxcpus=1 on the kernel command line
Summary recorded from message bug 883938 message 

-- 
883938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883938
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Reply to:

References:
- Bug#883938: Workaround available
  - From: Bernhard Schmidt <berni@birkenwald.de>
- 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: Workaround available
Next by Date: Processed (with 1 error): forcibly merging 883938 884069
Previous by thread: Bug#883938: Workaround available
Next 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
Index(es):
- Date
- Thread