On Mon, 11 Dec 2017 19:07:05 +0100 Karsten Heiken <
hei...@luis.uni-hannover.de> wrote:
> Bernhard Schmidt wrote:
> >Can you check whether numa=off on the kernel command line fixes this as
well?
>
> Indeed it does. Appending numa=off to the kernel command line fixes
> the bug in my KVM virtual mach
The Xen Project CI has six machines which were affected by this
regression. (Kernel messages are near-identical to those reported
by others in this bug.) As suggested I downloaded this kernel;
https://people.debian.org/~benh/packages/jessie-pu/linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64
Also unable to boot since update to 3.16.51 on Intel 2nd Gen i7-2600 @
3.4GHz on Asus P8 H67-M (1 CPU, 8 core)
***UUID*** not found
Booted from another drive, downloaded linux-image-3.16.0-4-amd64 with
3.16.43-2+deb8u2 and extracted files over boot/lib/usr on main drive.
Now booting with no ap
The same issue here with CPU Intel(R) Xeon(R) CPU E5-2603 0 @ 1.80GHz(8
Core).
Back to 3.16.43-2+deb8u5 works for me.
This was a production system.
--
Mit freundlichen Grüßen / Best regards
Olaf Neupert
PARADIGMA Software GmbH
Paul-Lincke-Ufer 8e, 10999 Berlin | Feringastr. 6, 85774 Unterföhr
Package: src:linux
Followup-For: Bug #883938
Dear Maintainer,
I have run into this same problem on HP ProLiant DL380 G6 (fortunately this is
only a backup server)
I confirm that numa=off workaround works for me. That allowed me to install
linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64.deb
Hello Ben,
Thank you for the fix. We have same issue as other people in this conversation.
When do you think that the fix will be rollout as stable?
Sebastian Gerke
--
Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)
Institut für Antriebstechnik | Linder Höhe | 5114
On Mon, Dec 11, 2017 at 11:10:42PM +0100, Salvatore Bonaccorso wrote:
> Hi Ben,
>
> On Mon, Dec 11, 2017 at 09:47:49PM +, Ben Hutchings wrote:
> > On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote:
> > > There were several commits interspersed with sched/topology fixes
> > > upstream that
The provided work-around (setting numa=off) worked here.
Do you need further information about the system in use?
BTW: Thank you for the NUMA advice, it was about 21.00 CET when
I started a search engine and found the bug entry and the suggested
work-around, so, your advice came just in time.
Hi Ben,
On Mon, Dec 11, 2017 at 09:47:49PM +, Ben Hutchings wrote:
> On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote:
> > There were several commits interspersed with sched/topology fixes
> > upstream that I thought were cleanup and therefore didn't backport to
> > the 3.16 stable branc
On Mon, 2017-12-11 at 21:29 +, Ben Hutchings wrote:
> There were several commits interspersed with sched/topology fixes
> upstream that I thought were cleanup and therefore didn't backport to
> the 3.16 stable branch. Now I suspect that at least some of them are
> needed.
>
> I'm attaching ba
There were several commits interspersed with sched/topology fixes
upstream that I thought were cleanup and therefore didn't backport to
the 3.16 stable branch. Now I suspect that at least some of them are
needed.
I'm attaching backports of 3 of the commits that I left out. Can you
test whether t
Hi
here the bisect log (unless overseen something with the last good commit):
git bisect start
# good: [3717265153a66c2ecbd745ea8eef213289b4a55e] Linux 3.16.48
git bisect good 3717265153a66c2ecbd745ea8eef213289b4a55e
# bad: [c45c05f42d5d3baf5d18e648c064788381fcfa1c] Linux 3.16.51
git bisect bad c
Bernhard Schmidt wrote:
Can you check whether numa=off on the kernel command line fixes this as well?
Indeed it does. Appending numa=off to the kernel command line fixes
the bug in my KVM virtual machines as well as my physical servers (at
least the ones I've tested so far).
So this might be a
Hi Karsten,
Thanks for the test. Can you check whether numa=off on the kernel command line
fixes this as well?
Bernhard
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
I can reproduce the bug on multiple (physical) servers running in our
data center.
When booting my virtual servers with the new kernel, the issue did not
arise...
...until I enabled NUMA.
Booting a virtual machine with 2 sockets and 16 cores each works fine
when NUMA is disabled in KVM.
With N
Just as a note:
Upgrading to jessie-backports version 4.9.51-1~bpo8+1 is also an option,
which works.
Christoph
<>
signature.asc
Description: OpenPGP digital signature
Hi
The issue is as well happening with 3.16.51 vanilla (and config
generated with localmodconfig, make deb-pkg built).
Trying to bisect now.
Regards,
Salvatore
Same here, whole cluster of machines down here with this kernel. Same
panic message, so I won't repeat it here. These are Supermicro boxes
with Xeon CPUs:
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
O
On Mon, Dec 11, 2017 at 09:23:45AM +0100, Salvatore Bonaccorso wrote:
> The issue seems not present when rolling back to 3.16.48-1 (this is
> one kernel version which was only present in jessie-proposed-update).
>
> Can someone confirm? If yes it has to be a change between 3.16.48-1
> and 3.16.51
The issue seems not present when rolling back to 3.16.48-1 (this is
one kernel version which was only present in jessie-proposed-update).
Can someone confirm? If yes it has to be a change between 3.16.48-1
and 3.16.51-2.
Regards,
Salvatore
I encountered this on an old Intel SR1600 box with Westmere Xeons.
I have an Ivy Bridge E5-1620v2 physical box that has booted successfully
with this kernel, and I haven't seen any problem among the dozen or so
VMs that have so far rebooted onto it (VMware ESXi 6.0/6.5, on dual E5
Xeon Sandy Bridg
FWIW, I run into exact same kernel panic on R810. Downgrading
to 3.16.43-2+deb8u5 "resolved" the problem.
-- Marek
Hi
> I only have a terrible java KVM app available for seeing the console, and from
> what I can see, it logs with timestamps [0.811] through [0.841] (typing in
> from an image - excuse any typos, and leaving out long hexadecimal numbers
> that might not be interesting)
here is one captured from
On Sat, Dec 09, 2017 at 18:46:08 +0100, Rene Engelhard wrote:
> On Sat, Dec 09, 2017 at 06:23:04PM +0100, debbug wrote:
> > Package: src:linux
> > Version: 3.16.43-2+deb8u5
> > Severity: grave
> > Justification: renders package unusable
> >
> > (Note: This bug affects version 3.16.51-2, not 3.16.4
notfound 883938 3.16.43-2+deb8u5
found 883938 3.16.51-2
thanks
Hi,
On Sat, Dec 09, 2017 at 06:23:04PM +0100, debbug wrote:
> Package: src:linux
> Version: 3.16.43-2+deb8u5
> Severity: grave
> Justification: renders package unusable
>
> (Note: This bug affects version 3.16.51-2, not 3.16.43-2+deb
Processing commands for cont...@bugs.debian.org:
> notfound 883938 3.16.43-2+deb8u5
Bug #883938 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on boot after
upgrading to debian 8.10 kernel 3.16.51
No longer marked as found in versions linux/3.16.43-2+deb8u5.
> found 883938 3.16.51-2
Bug #88
Package: src:linux
Version: 3.16.43-2+deb8u5
Severity: grave
Justification: renders package unusable
(Note: This bug affects version 3.16.51-2, not 3.16.43-2+deb8u5,
but that's the version that "reportbug" filled in after downgrading
to get this system back up running)
After upgrading from Debian
27 matches
Mail list logo
