Processed: summary 883938 Seems to affect machines with more than one socket. Workaround: set maxcpus=1 on the kernel command and downgrade to 3.16.48-1 or earlier

From	"Debian Bug Tracking System" <owner@bugs.debian.org>
Newsgroups	linux.debian.kernel
Subject	Processed: summary 883938 Seems to affect machines with more than one socket. Workaround: set maxcpus=1 on the kernel command and downgrade to 3.16.48-1 or earlier
Date	2017-12-11 10:20 +0100
Message-ID	<uVspH-3iJ-1@gated-at.bofh.it> (permalink)
References	<uVspH-3iJ-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Processing commands for control@bugs.debian.org:

> summary 883938 Seems to affect machines with more than one socket. Workaround: set maxcpus=1 on the kernel command and downgrade to 3.16.48-1 or earlier
Summary replaced with message bug 883938 message 
Summary replaced with message bug 883938 message 
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
883938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883938
884069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884069
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread

Thread

Processed: summary 883938 Seems to affect machines with more than  one socket. Workaround: set maxcpus=1 on the kernel command and downgrade  to 3.16.48-1 or earlier "Debian Bug Tracking System" <owner@bugs.debian.org> - 2017-12-11 10:20 +0100

csiph-web