Bug#884094: register_key_type symbol missing, ABI counter not incremented

* Ben Hutchings [2017-12-11 15:59:38 +]: > I don't think there's any good way to deal with this > now, other than to force a rebuild of the module. Was afraid of that. It's what I did, of course, but it complicates the rollout. (I ran "dkms remove openafs/1.6.20 -k $(uname -r); dkms install

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#884069: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

Tested on most important system (IBM BladeCenter HS22). It boots OK, but infiniband don't work (interface is up, but rdma - no): [ 147.690952] ko2iblnd: disagrees about version of symbol rdma_resolve_addr [ 147.690956] ko2iblnd: Unknown symbol rdma_resolve_addr (err -22) [ 147.691009]

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

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

Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

[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:

Re: State of SecureBoot for Debian GNU/Linux?

On Mon, 2017-12-11 at 17:55 +0100, Philipp Hahn wrote: > Hello fellow DDs, > > I'm employed by Univention and we ship our Debian based distribution > "Univention Corporate Server" with UEFI support. Currently we're > building our own Linux kernel and have our own signed version of shim > and

Bug#884116: linux-image-4.9.0-4-amd64: screen atrifacts then crash

Source: linux Version: 4.9.0-4 Followup-For: Bug #884116 I've got the same error after upgrading from 4.9.0-3 to the newer kernel. I could provide information if required -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500,

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 884140 src:linux Bug #884140 [linux-image] Kernel 3.16.51-2 general protection fault in sched_init_smp() Warning: Unknown package 'linux-image' Bug reassigned from package 'linux-image' to 'src:linux'. No longer marked as found in

Bug#884001:

Hello, I think I have the same problem after installing the new 4.9.65-3 kernel. Sometimes I can't even log in because the screen freezes right after login. The bug doesn't seem to appear in console only sessions. The error doesn't occur while running with the previous kernel. It's a Lenovo

Bug#884061: linux-image-4.9.0-4-amd64: screen scrolls wildly

On 2017-12-10, Vagrant Cascadian wrote: > Since upgrading to 4.9.65-3, my screen occasionally starts rapidly > scrolling sideways, flashing on and off repeatedly... ... > When this starts to happen, usually there is a log in the dmesg output > like this: > > [drm:gen8_irq_handler [i915]] *ERROR*

Processed (with 1 error): Re: Bug#884140: Kernel 3.16.51-2 general protection fault in sched_init_smp()

Processing control commands: > forcemerge 883938 -1 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 Bug #884069 [src:linux] Kernel crash on boot on IBM BladeCenter HS22 Unable to merge bugs because: package of #884140 is

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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.

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Processed: summary 883938 Seems to affect machines with 2+-sockets/NUMA. Workaround: set numa=off on the kernel command and downgrade to 3.16.48-1 or earlier

Processing commands for cont...@bugs.debian.org: > summary 883938 Seems to affect machines with 2+-sockets/NUMA. Workaround: set > numa=off 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

Processed: summary 883938 Seems

Processing commands for cont...@bugs.debian.org: > summary 883938 Seems 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:

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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.

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#884094: User message

I have experienced this same problem suddenly on doing a safe-upgrade. Thank you for identifying the cause and reporting the problem. For the benefit of those users who will also encounter the problem and search for the cause, the user experience symptom is that on aklog, the following message is

State of SecureBoot for Debian GNU/Linux?

Hello fellow DDs, I'm employed by Univention and we ship our Debian based distribution "Univention Corporate Server" with UEFI support. Currently we're building our own Linux kernel and have our own signed version of shim and grub. For our next release, which will be based von Debian-Stretch,

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#884094: register_key_type symbol missing, ABI counter not incremented

On Mon, 2017-12-11 at 11:48 +0100, Sergio Gelato wrote: > Package: linux-image-4.9.0-4-amd64 > Version: 4.9.65-3 > Severity: important > Affects: openafs-modules-dkms > > debian/patches/debian/keys-limit-abi-change-in-4.9.59.patch renames > register_key_type to register_key_type_2 without bumping

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#883938:

Same here with DELL R7910 and dual Xeon E5-2660v3. Downgrading the kernel did help.

Bug#884116: Further information

After some more searching I found that the screen artifacts start after this message (from dmesg): [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Bug#884116: linux-image-4.9.0-4-amd64: screen atrifacts then crash

Package: src:linux Version: 4.9.65-3 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? I did an upgrade today and linux image was upgraded from 4.9.51-1 to 4.9.65-3. * What was the outcome of this action? Various screen artifacts appear

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Bug#884069: Same problem on Supermicro H8DGi-F

Same here with Supermicro H8DGi-F (with only one cpu installed)

Processed: tagging 883735, tagging 883735

Processing commands for cont...@bugs.debian.org: > tags 883735 - moreinfo Bug #883735 [initramfs-tools] initramfs-tools: automatic resume doesn't work for lvm swap partitions Removed tag(s) moreinfo. > tags 883735 + pending Bug #883735 [initramfs-tools] initramfs-tools: automatic resume doesn't

Bug#883735: Re: Bug#883735: initramfs-tools: automatic resume doesn't work for lvm swap partitions

Hi, On 07/12/17 01:30, Ben Hutchings wrote: > Control: reopen -1 > Control: tag -1 patch moreinfo > > On Thu, 2017-12-07 at 00:22 +, James Cowgill wrote: >> Hi, >> >> On 07/12/17 00:06, Ben Hutchings wrote: >>> On Wed, 2017-12-06 at 23:48 +, James Cowgill wrote: Package:

Bug#884094: register_key_type symbol missing, ABI counter not incremented

Package: linux-image-4.9.0-4-amd64 Version: 4.9.65-3 Severity: important Affects: openafs-modules-dkms debian/patches/debian/keys-limit-abi-change-in-4.9.59.patch renames register_key_type to register_key_type_2 without bumping the ABI counter, breaking OpenAFS kernel modules (package

Bug#709879: marked as done (espeak: Alsa lib underflow and clicking sounds.)

Your message dated Mon, 11 Dec 2017 21:42:00 +1100 with message-id and subject line Re: Bug#709879: espeak: Alsa lib underflow and clicking sounds. has caused the Debian Bug report #709879, regarding espeak: Alsa lib underflow

Bug#709879: espeak: Alsa lib underflow and clicking sounds.

Hi Samuel, No the bug must have been fixed at some point. I forgot I even submitted this. Still use espeak extensively, thanks for contributing to a wonderful program. Regards, Anton On Mon, Dec 11, 2017 at 8:14 AM, Samuel Thibault wrote: > Control: reassign -1 linux >

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

Processing commands for cont...@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

Processed: affects 883938

Processing commands for cont...@bugs.debian.org: > affects 883938 release.debian.org 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 Bug #884069 [src:linux] Kernel crash on boot on IBM BladeCenter HS22 Added indication that

Processed: summary 883938 Seems

Processing commands for cont...@bugs.debian.org: > summary 883938 Seems 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:

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

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

Processed: reassign 884069 to src:linux, forcibly merging 883938 884069

Processing commands for cont...@bugs.debian.org: > reassign 884069 src:linux Bug #884069 [linux-image-3.16.0-4-amd64] Kernel crash on boot on IBM BladeCenter HS22 Bug reassigned from package 'linux-image-3.16.0-4-amd64' to 'src:linux'. No longer marked as found in versions linux/3.16.51-2.

Bug#884069: workaround is to use nosmp

You can use nosmp parameter to start server temporary for downgrade.

Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

On Mon, 11 Dec 2017 08:37:30 +0100 Bernhard Schmidt wrote: > Control: severity -1 critical > Same issue for us with Dell PowerEdge R630. Regards, Thomas

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 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

Processed (with 1 error): forcibly merging 883938 884069

Processing commands for cont...@bugs.debian.org: > forcemerge 883938 884069 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 Unable to merge bugs because: package of #884069 is 'linux-image-3.16.0-4-amd64' not 'src:linux'

Processed: Re: Bug#883938: Workaround available

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

Bug#883938: Workaround available

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