Hi Erik,
On Tue, Jan 02, 2018 at 11:09:03AM -0800, E Barker wrote:
> Hello,
>
> Just wondering when we can expect an update to the linux and initrd
> images within the netboot debian-installer tree?
See https://lists.debian.org/debian-stable-announce/2017/12/msg2.html
The netboot images wil
Hello,
Just wondering when we can expect an update to the linux and initrd
images within the netboot debian-installer tree?
I had to apply the numa=off workaround for PXE installs but the
date/time stamp for the files still show 12/5/17, 7:51:00 AM:
ftp://ftp.ca.debian.org/debian/dists/jessie/ma
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
Report
On Mon, 2017-12-18 at 18:40 +, Thomas Patrick Downes wrote:
> Is there going to be any kind of post-mortem analysis of how this
> happened?
I think it would be good to do this, but it doesn't seem to be
something that Debian does as a matter of course, and I'm unlikely to
be the right person t
On Tue, 2017-12-19 at 12:09 -0600, Phil Kauffman wrote:
> Can we also make sure that this bug gets fixed in the netboot kernel?
>
> http://ftp.us.debian.org/debian/dists/jessie/main/installer-amd64/cur
> rent/images/netboot/debian-installer/amd64/linux
The netboot kernel won't be updated until th
Can we also make sure that this bug gets fixed in the netboot kernel?
http://ftp.us.debian.org/debian/dists/jessie/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
Cheers,
Phil
Is there going to be any kind of post-mortem analysis of how this happened? The
changelogs indicate that this entered oldstable-proposed-updates around 4
December. I’m not quite sure when it entered oldstable-updates or if it ever
formally entered oldstable-updates prior to being incorporated in
Thank you. The update has just been applied and my systems are now up
and running again with no UUID error.
Hi,
we also had this bug and the downgrade saved our lifes.!
We also can see that the new package ist available - but is it fixed there?
best regards
Andreas
Hi all,
I saw that the package 3.16.51-3 is now available in jessie-update.
Is there any chance to have this package available in jessie
repository before the next point release ?
Thomas
On Mon, 11 Dec 2017 15:07:39 +0900 Stephane Lapie
wrote:
Hi,
I also got some hardware refusing to boot with this bug :
HP ProLiant DL360 Gen9
The crash is instant, right after GRUB loads the kernel and initramfs.
Partial backtrace (re-typed from a KVM screen capture) :
[0.649289] Call Tra
Dear Ben,
Thank you, the fix works for me, both Sun Fires (X2200M2 and X4200M2) boot with
3.16.51-3~a.test (2017-12-11).
Best wishes:
Elemér
Hi is there a way to do a netinst to a specific source-version such
as 3.16.48-1.
Thanks in advance.
]---
[0.920012] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[0.920012]
[0.924000] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[0.924000]
As per the comment #170
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88393
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
Just installed the kernel provided by Ben Hutchings.
The server now boots normally and appear to function OK.
Thanks,
--
Oron Peled
Package: src:linux
Version: 3.16.51-2
Followup-For: Bug #883938
Dear Maintainer,
I did bisection of upstream kernel between 3.16.48 and 3.16.51
The problematic commit was: cbff7ea5d47aa15e1b6d8063bd147cc0a289e452
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h
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
Hi,
* Ben Hutchings [171214 11:37]:
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix it. An updated package is
> available at:
>
> https://people.debian.
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 Tue, 12 Dec 2017 01:57:48 + Ben Hutchings wrote:
> [This message is bcc'd to all bug reporters.]
>
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix it
On 12/12/17 02:57, Ben Hutchings wrote:
> https://people.debian.org/~benh/packages/jessie-pu/linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64.deb
>
> Please report back (to the bug address) whether this fixes the
> regression for you.
>
Fixes the problem on our servers. Thanks!
Mike.
On Sun, 10 Dec 2017 18:10:27 + "Grischa Zengel" wrote:
> I had the same problem with my VMs under Proxmox/KVM.
>
> After changing CPU structure from "2 socket 1 CPU" to "1 socket 2 CPU"
the problem was gone.
> Only enabling/disabling NUMA didn't work.
>
> So I think it's a problem with aktivati
On Tue, 12 Dec 2017 01:57:48 + Ben Hutchings wrote:
> [This message is bcc'd to all bug reporters.]
>
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix
Hi Ben,
Ben Hutchings wrote:
An updated package is available at:
https://people.debian.org/~benh/packages/jessie-pu/linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64.deb
I can also confirm that this build works fine on my problematic
machines.
Thanks for the fix!
Karsten
signature.asc
D
3.16.51-3~a.test also works on my previously problematic box.
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
On Tue, 12 Dec 2017 01:57:48 + Ben Hutchings wrote:
> [This message is bcc'd to all bug reporters.]
>
> Apologies for this regression. Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix i
[This message is bcc'd to all bug reporters.]
Apologies for this regression. Salvatore Bonaccorso has tracked down
which change in 3.16-stable triggers the crash, and I identified some
related upstream changes which appear to fix it. An updated package is
available at:
https://people.debian.org
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
Same here with DELL R7910 and dual Xeon E5-2660v3. Downgrading the kernel
did help.
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
Control: summary -1 Seems two affect machines with more than one socket.
Workaround: set maxcpus=1 on the kernel command line
Hi,
this seems to affect two-socket boxes.
Workaround is to set maxcpus=1 on the kernel command line.
Bernhard
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
One more bit of info if it helps.
I noticed that I had some ProLiant DL360 Gen9 servers that booted fine with
that version.
The main difference between the ones that failed booting had more CPU cores
detected than the ones that succeeded.
For reference, the successful one had 20, the failed one ha
Have the same issue (kernel panic) after kernel upgade this night. I had to
restore the old kernel+initrd+modules from backup (Linux xxx 3.16.0-4-amd64 #1
SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux).
Server: HP ProLiant DL380 G6
# lspci
00:00.0 Host bridge: Intel Corporation 5520
Hi,
I also got some hardware refusing to boot with this bug :
HP ProLiant DL360 Gen9
The crash is instant, right after GRUB loads the kernel and initramfs.
Partial backtrace (re-typed from a KVM screen capture) :
[0.649289] Call Trace:
[0.649362] [] ? sched_init_smp+0x398/0x452
[0.6
Hi,
The non-booting machines have multiple CPUs:
* X4200M2: 2 AMD 2220, no Xen, LVM
* X2200M2: 2 AMD 2347HE
The booting machine has multiple CPUs as well, but Xen is configured to give
only 1 vCPU to Doms.
* X4200M2: 2 AMD 2220, Xen
The freezing machine might have a HW problem or might be hi
Hi,
Update: probably reproduced the bug in Xen on a Sun Fire X4200 M2 ;(
After 4.5 hours, it froze so hard that I could not power it off via the iLOM,
even Num Lock wouldn't work. After
rebooting, lock-ups occurred in about 5-30 minutes. There is nothing in the
syslog.
After downgrading the D
I had the same problem with my VMs under Proxmox/KVM.
After changing CPU structure from "2 socket 1 CPU" to "1 socket 2 CPU" the
problem was gone.
Only enabling/disabling NUMA didn't work.
So I think it's a problem with aktivating second prozessor.
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
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
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
62 matches
Mail list logo
