Bug#883425: linux-image-4.14.0-1-amd64: stale Android device entries in Thunar after USB disconnection

Two probably related bug reports: #882353 - nautilus: Phone does not disappear after disconnecting #884067 - Info received (GIO lists removable storage devices even after they have been unplugged when using Linux kernel v4.14) I filed the last one because I didn't notice the one for Nautilus,

Bug#733521: marked as done (linux-image-3.12-1-amd64: System76 Gazelle Pro crashes on hibernate)

Your message dated Thu, 14 Dec 2017 22:10:32 -0800 with message-id <87374cjzc7@hope.eyrie.org> and subject line Re: Bug#733521: linux-image-3.12-1-amd64: System76 Gazelle Pro crashes on hibernate has caused the Debian Bug report #733521, regarding linux-image-3.12-1-amd64: System76 Gazelle

Bug#884426: Wifi speeds of Debian 9 (Stretch) are 2-3 times slower than Debian 8 (Jessie)

Package: firmware-iwlwifi Version: 20161130-3 REPORT: Debian 8 (Jessie) 1) The Jessie wifi package is 'firmware-iwlwifi' version 0.43 2) Linux kernel = 3.16.0.4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux 3) C library version = 2.19-18+deb8u10 When using Debian 8 (Jessie)

Bug#855632: Bug#883217: linux: open on NFSv4 exported file on nfs server: "Resource temporarily unavailable" under reproducible conditions when client has granted read delegation on file

On 12/14/2017 12:51 PM, Salvatore Bonaccorso wrote: > Hi Stephen, > > On Mon, Dec 04, 2017 at 09:24:55PM +0100, Salvatore Bonaccorso wrote: >> Hi >> >> On Thu, Nov 30, 2017 at 03:35:40PM -0700, Stephen Dowdy wrote: >>> On 11/30/2017 01:39 PM, Salvatore Bonaccorso wrote: Is this worth

Bug#883938: netinst to a specific source-version?

Hi is there a way to do a netinst to a specific source-version such as 3.16.48-1. Thanks in advance.

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

Package: src:linux Version: 4.9.65-3 Followup-For: Bug #884116 -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: product_name: product_version: chassis_vendor: chassis_version: bios_vendor:

Bug#878221: linux-image-4.9.0-4-amd64: Screen flickers randomly with Radeon R9 270X since upgrade from 4.9.0-3 to 4.9.0-4

HP E242 1920x1200 -> DisplayPort -> HP HP Elitebook 2540p Same Problem/Same Fix: Downgrade to Linux laptom 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5

Bug#884387: Chipset affected by the bug

I forgot to tell which chipset was affected by this bug. According to lspci 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)

Bug#855632: Bug#883217: linux: open on NFSv4 exported file on nfs server: "Resource temporarily unavailable" under reproducible conditions when client has granted read delegation on file

Hi Stephen, On Mon, Dec 04, 2017 at 09:24:55PM +0100, Salvatore Bonaccorso wrote: > Hi > > On Thu, Nov 30, 2017 at 03:35:40PM -0700, Stephen Dowdy wrote: > > On 11/30/2017 01:39 PM, Salvatore Bonaccorso wrote: > > > Is this worth trying to be fixed for the jessie kernel? > > > > Salvatore, > >

Processed: tagging 884371

Processing commands for cont...@bugs.debian.org: > tags 884371 + moreinfo Bug #884371 [src:linux] Hangs on boot without messages Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 884371:

Bug#884371: Hangs on boot without messages

Hi Sven! On Thu, Dec 14, 2017 at 06:20:14PM +0100, Sven Bartscher wrote: > Hi Salvatore, > > Am 14.12.2017 um 17:33 schrieb Salvatore Bonaccorso: > > Just to confirm, the output is not logged to any console you are > > capturing? > > That's a good question. There might actually be another

Bug#884387: linux-image-4.14.0-1-amd64: Soundcard module don't load correctly on linux-image-4.14.0-1-amd64

Package: src:linux Version: 4.14.2-1 Severity: normal Dear Maintainer, * What led up to the situation? Sound used to work so I guess what led up to the problem was upgrading the (switching to) new kernel Here is dmesg output : https://hastebin.com/oyepogolux.vbs interesting lines are 712

linux_3.16.51-3_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Dec 2017 20:11:46 + Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all linux-headers-3.16.0-4-all-alpha

Bug#884140: marked as done (Kernel 3.16.51-2 general protection fault in sched_init_smp())

Your message dated Thu, 14 Dec 2017 17:32:32 + with message-id and subject line Bug#883938: fixed in linux 3.16.51-3 has caused the Debian Bug report #883938, regarding Kernel 3.16.51-2 general protection fault in sched_init_smp() to be marked as done.

Bug#884069: marked as done (Kernel crash on boot on IBM BladeCenter HS22)

Your message dated Thu, 14 Dec 2017 17:32:32 + with message-id and subject line Bug#883938: fixed in linux 3.16.51-3 has caused the Debian Bug report #883938, regarding Kernel crash on boot on IBM BladeCenter HS22 to be marked as done. This means that you

Bug#884371: Hangs on boot without messages

Hi Salvatore, Am 14.12.2017 um 17:33 schrieb Salvatore Bonaccorso: > Just to confirm, the output is not logged to any console you are > capturing? That's a good question. There might actually be another console where the output is going. I will definitely check this the next time it's possible.

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

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;

Bug#884183: linux-image-3.16.0-4-amd64: Kernel panic at boot

On 12/13/17, Benjamin Moody wrote: > Same problem here. 3.16.43-2+deb8u5 works, 3.16.51-2 is broken. > > Supermicro H8QM3 > > Quad-Core AMD Opteron(tm) Processor 8347 HE (fam: 10, model: 02, > stepping: 03) > > Two 3ware 9650SE RAID cards Sorry I didn't think to look

Bug#884371: Hangs on boot without messages

Hi Sven, On Thu, Dec 14, 2017 at 04:50:02PM +0100, Sven Bartscher wrote: > Package: src:linux > Version: 3.16.51-2 > Severity: important > > Due to the nature of this bug, this report was generated with reportbug > running > on 3.16.43-2+deb8u5, so the information gathered by reportbug may only

Bug#872560: iproute2 vrf

iproute2 versions since v4.10.0 (which are not yet in Debian) have the 'ip vrf exec' subcommand, which needs CONFIG_CGROUP_BPF as well.

Bug#884371: Hangs on boot without messages

Package: src:linux Version: 3.16.51-2 Severity: important Due to the nature of this bug, this report was generated with reportbug running on 3.16.43-2+deb8u5, so the information gathered by reportbug may only be partially useful. After upgrading the kernel to 3.16.51-2 it doesn't boot anymore.

Bug#883938: Info received (linux-image-3.16.0-4-amd64: Bisected upstream kernel and found guily commit)

Just installed the kernel provided by Ben Hutchings. The server now boots normally and appear to function OK. Thanks, -- Oron Peled

Bug#864777: initramfs-tools: Please support a tmpfs boot mode

Hi Peter, Am Donnerstag, den 29.06.2017, 15:55 -0400 schrieb Peter Colberg: > Hi Benjamin, > > On Wed, Jun 14, 2017 at 05:47:54PM +0200, Benjamin Drung wrote: > > Package: initramfs-tools > > Version: 0.130 > > Severity: normal > > Tags: patch > > > > Hi, > > > > The tmpfs boot mode allows one

Bug#883938: linux-image-3.16.0-4-amd64: Bisected upstream kernel and found guily commit

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

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

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

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

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

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

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

Processed: reassign 881352 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 881352 src:linux 4.13.4-2 Bug #881352 [linux-image-4.13.0-1-686-pae] udisks2: Breaks installation with kernel panic Bug reassigned from package 'linux-image-4.13.0-1-686-pae' to 'src:linux'. Ignoring request to alter found versions of

Processed: tagging 883938

Processing commands for cont...@bugs.debian.org: > tags 883938 + pending 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 Bug #884140 [src:linux] Kernel