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

2017-12-10 Thread Debian Bug Tracking System
Processing control commands: > severity -1 critical Bug #884069 [linux-image-3.16.0-4-amd64] Kernel crash on boot on IBM BladeCenter HS22 Severity set to 'critical' from 'normal' -- 884069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884069 Debian Bug Tracking System Contact

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

2017-12-10 Thread Bernhard Schmidt
Control: severity -1 critical On Mon, Dec 11, 2017 at 09:14:27AM +0200, Rolandas Naujikas wrote: Hi, > Package: linux-image-3.16.0-4-amd64 > Version: 3.16.51-2 > > Loading Linux 3.16.0-4-amd64 ... > Loading initial ramdisk ... > [0.604128] general protection fault: [#1] SMP > [

Bug#884069: the same problem on different hardware

2017-12-10 Thread Rolandas Naujikas
Loading Linux 3.16.0-4-amd64 ... Loading initial ramdisk ... [0.349165] general protection fault: [#1] SMP [0.352000] Modules linked in: [0.352000] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW 3.16.0-4-amd64 #1 Debian 3.16.51-2 [0.352000] Hardware name: Sun Microsystems

Bug#884069: system cannot boot after upgrade to Debian 8.10

2017-12-10 Thread Rolandas Naujikas
Severity: critical

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

2017-12-10 Thread Rolandas Naujikas
Package: linux-image-3.16.0-4-amd64 Version: 3.16.51-2 Loading Linux 3.16.0-4-amd64 ... Loading initial ramdisk ... [0.604128] general protection fault: [#1] SMP [0.609303] Modules linked in: [0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW 3.16.0-4-amd64 #1 Debian

Bug#883938: HP ProLiant DL360 Gen9

2017-12-10 Thread Stephane Lapie
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

Bug#883938: same issue

2017-12-10 Thread Tomáš Thiemel
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

Bug#883938: HP ProLiant DL360 Gen9

2017-12-10 Thread Stephane Lapie
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 [

Bug#883980: Fifth Manifestation

2017-12-10 Thread Gerard M. Vignes
I was using the latest, built-in version of Firefox ESR 52.5.2 (64-bit), and I noticed that I got the same, consistent problem as with Chromium. When I move the mouse cursor between surrounding page and embedded video (either direction), the screen goes black for 1 second. This behavior is

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

2017-12-10 Thread Vagrant Cascadian
Package: src:linux Version: 4.9.65-3 Severity: normal Since upgrading to 4.9.65-3, my screen occasionally starts rapidly scrolling sideways, flashing on and off repeatedly... looks almost like the refresh rate or sync was off, and it's displaying the leftmost part of the screen on the rightmost

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

2017-12-10 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 linux Bug #709879 [espeak] espeak: Alsa lib underflow and clicking sounds. Bug reassigned from package 'espeak' to 'linux'. No longer marked as found in versions espeak/1.46.02-2. Ignoring request to alter fixed versions of bug #709879 to the same values

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

2017-12-10 Thread Samuel Thibault
Control: reassign -1 linux Hello, Really sorry this apparently went unnoticed for so long. anton, on dim. 26 mai 2013 19:19:32 +1000, wrote: > Espeak does not start normally and throws out the error message: > ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred > Hundreds of times. It does

Bug#883938: Sun Fire X4200 M2 Xen

2017-12-10 Thread Dr. Nagy Elemér Kár oly
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

Bug#883938: Sun Fire X4200 M2 Xen

2017-12-10 Thread Dr. Nagy Elemér Kár oly
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

Bug#883938: Same problem with KVM

2017-12-10 Thread Grischa Zengel
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.

Bug#883980: Steps to Duplicate Problem

2017-12-10 Thread Gerard M. Vignes
After a clean reboot, I began experimenting to find repeatable steps to duplicate the problem. I have the following programs running across 9 workspaces (which are always running on my machine): Chromium & gPHPEdit, Web (Ephiphany) & Geany, and Terminator (running a split screen). The problem

Bug#883976: marked as done (nfs-common: Shell script executed by systemd to mount net /home * /var fails)

2017-12-10 Thread Debian Bug Tracking System
Your message dated Sun, 10 Dec 2017 15:21:14 + with message-id <1512919274.2723.4.ca...@decadent.org.uk> and subject line Re: Bug#883976: nfs-common: Shell script executed by systemd to mount net /home * /var fails has caused the Debian Bug report #883976, regarding nfs-common: Shell script

Bug#883938: Sun Fire X4200 M2 too

2017-12-10 Thread Dr. Nagy Elemér Kár oly
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

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

2017-12-10 Thread Dominic Benson
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

Bug#884009: firmware: failed to load pci errors in syslog

2017-12-10 Thread Frederique
Package: firmware-atheros Version: 20170823-1 Severity: normal Dear Maintainer, * What led up to the situation? Error showing up during boot. * What exactly did you do (or not do) that was effective (or ineffective)? Start my computer. * What was the outcome of

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

2017-12-10 Thread Marek Skrobacki
​FWIW, I run into exact same kernel panic on R810. Downgrading to 3.16.43-2+deb8u5 "resolved" the problem. -- Marek

Bug#883935: linux-image-4.9.0-4-amd64: i915 GPU hang after every suspend or hibernate (Hang on render ring)

2017-12-10 Thread Christoph Wiedemann
Package: src:linux Version: 4.9.65-3 Followup-For: Bug #883935 Dear Maintainer, I have the same issue, and I find it very annoying. As a workaround I use kernel linux-image-4.12.0-1-amd64, which mostly manages to wake correctly from hibernation. But honestly, I'm a bit overstrained in using a

Bug#884001: linux-image-4.9.0-4-amd64: Severe graphics corruption on intel graphics after kernel upgrade

2017-12-10 Thread Andreas Berger
Package: src:linux Version: 4.9.65-3 Severity: important Hello, After upgrading the kernel from 4.9.51-1 to 4.9.65-3 i got severe graphics corruption (Screen content shifts sideways, flickers, screen goes black). This gets progressively worse so the system is unusable about 15 minutes after