Bug#897930: linux-image-4.9.0-6-686-pae: Random hard lockups (no panic message) on Via C7 system

Package: src:linux Version: 4.9.88-1 Severity: normal Dear Maintainer, For several weeks I have been experiencing hard lockups of my system (running a Via C7 CPU). When the system locks up, there is no panic message on the console, numlock/caps lock are inoperative, and a hard reset is the

Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging 897204

Hi, 2018-05-04 9:04 GMT+02:00 Salvatore Bonaccorso : > Hi Romain, > > On Fri, May 04, 2018 at 08:44:32AM +0200, Romain Perier wrote: >> Hello, >> >> Whoops, I did something wrong apparently, sorry. >> So I only fixed the issue in sid (4.16), I have to wait that the >> package

Bug#897917: Stretch kernel 4.9.88-1 breaks startup of RPC, KDC services

Package: linux-image-4.9.0-6-amd64 Version: 4.9.88-1 Issue: == Kernel "linux-image-4.9.0-6-amd64," version 4.9.88-1, breaks systemd startup of RPC, Kerberos KDC services.  Description: After upgrading to the latest Stretch kernel (4.9.88-1), RPC and KDC services time out

Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

Control: tag -1 moreinfo On Fri, 2018-05-04 at 15:35 +0300, Eugene Budanov wrote: > Package: linux-image-4.9.0-6-amd64 > Version: 4.9.82-1+deb9u3 > > Hi! > > Here's a short problem description. > > We have some Supermicro servers with the same configuration for all > machines (hardware,

Processed: Re: Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

Processing control commands: > tag -1 moreinfo Bug #897893 [src:linux] Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver Added tag(s) moreinfo. -- 897893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897893 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: forcibly merging 897427 897685

Processing commands for cont...@bugs.debian.org: > forcemerge 897427 897685 Bug #897427 [src:linux] linux-image-3.16.0-6-amd64 breaks KVM guests in libvirt Bug #897685 [src:linux] linux-image-3.16.0-6-amd64: Unable to start multiple KVM instances with libvirt Added indication that 897685 affects

Processed: reassign 897893 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 897893 src:linux 4.9.82-1+deb9u3 Bug #897893 [linux-image-4.9.0-6-amd64] Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver Bug reassigned from package 'linux-image-4.9.0-6-amd64' to 'src:linux'. No longer marked as

Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

Package: linux-image-4.9.0-6-amd64 Version: 4.9.82-1+deb9u3 Hi! Here's a short problem description. We have some Supermicro servers with the same configuration for all machines (hardware, kernels, packages, etc). A month ago, or maybe a bit later, all of these machines began crashing into

Bug#897802: linux: ftbfs with GCC-8

Package: src:linux Version: 4.15.17-1 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or

Bug#897685: linux-image-3.16.0-6-amd64: Unable to start multiple KVM instances with libvirt

Package: src:linux Version: 3.16.56-1 Severity: important Dear Maintainer, The kernel package linux-image-3.16.0-6-amd64 introduced a regression apparently preventing multiple KVM libvirt instances from running concurrently. Here is the error message when attempting to start a second instance :

Processed: affects 897427

Processing commands for cont...@bugs.debian.org: > affects 897427 libvirt-daemon-system Bug #897427 [src:linux] linux-image-3.16.0-6-amd64 breaks KVM guests in libvirt Added indication that 897427 affects libvirt-daemon-system > thanks Stopping processing here. Please contact me if you need

Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging 897204

Hi Romain, On Fri, May 04, 2018 at 08:44:32AM +0200, Romain Perier wrote: > Hello, > > Whoops, I did something wrong apparently, sorry. > So I only fixed the issue in sid (4.16), I have to wait that the > package is in buster before closing this bug, I guess, right ? My point was to reopen the

Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging 897204

Hello, Whoops, I did something wrong apparently, sorry. So I only fixed the issue in sid (4.16), I have to wait that the package is in buster before closing this bug, I guess, right ? Romain 2018-05-03 22:18 GMT+02:00 Debian Bug Tracking System : > Processing commands for