Bug#1069773: linux-image-6.1.0-20-amd64: Bluetooth fails to resume after suspend with linux-image-6.1.0-20

2024-04-24 Thread Robert Lange
Package: src:linux Version: 6.1.85-1 Severity: important Dear Maintainer, After upgrading to linux-image-6.1.0-20-amd64 and rebooting my laptop, my Bluetooth mouse failed to work after resuming from suspend (via closing and reopening my laptop). Manually stopping and starting Bluetooth via the

Bug#852612: bug severity upgrade?

2017-02-01 Thread Robert Lange
Is it possible to get an upgrade in severity to grave for this bug (or the linked bug #851928)? The fix for this bug is blocked from entering testing by another bug that is marked grave: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853170 Both of (#852612 / #851928) and #853170 cause

Bug#852612: Acknowledgement (linux-image-4.9.0-1-amd64: kernel 4.9.2-2 panics on boot)

2017-01-25 Thread Robert Lange
> I think this should be the same as #851928 addressed by > > - http://git.kernel.org/linus/20b1e22d01a4b0b11d3a1066e9feb04be38607ec > - http://git.kernel.org/linus/0100a3e67a9cef64d72cd3a1da86f3ddbee50363 > > and already pending for the next upload of src:linux to unstable > (4.9.6-1). >

Bug#852612: Acknowledgement (linux-image-4.9.0-1-amd64: kernel 4.9.2-2 panics on boot)

2017-01-25 Thread Robert Lange
This bug is almost certainly related to this patch, which I believe is not in the currently packaged kernel: https://git.kernel.org/cgit/linux/kernel/git/efi/efi.git/commit/?h=next=b2a91a35445229 The machine referenced in that patch is the Lenovo ThinkPad w541, which is a minor hardware

Bug#852612: linux-image-4.9.0-1-amd64: kernel 4.9.2-2 panics on boot

2017-01-25 Thread Robert Lange
Package: src:linux Version: 4.9.2-2 Severity: important Dear Maintainer, I upgraded to kernel 4.9 which just migrated into testing. Upon reboot the system failed to get past "loading initial ramdisk". I added "debug ignore_loglevel earlyprintk=efi,keep" to the kernel command line and was able to

Bug#789952: update to linux-image-amd64 4.0+65 (running kernel 4.0.8-1)

2015-07-15 Thread Robert Lange
Now that a 4.0.x kernel is in testing, I tried this again. $ uname -a Linux iset 4.0.0-2-amd64 #1 SMP Debian 4.0.8-1 (2015-07-11) x86_64 GNU/Linux The bitrate is still incorrect. It appears to be constant at whatever the first sampled value was since the system last booted. The link quality and

Bug#789952: linux-image-4.0.0-2-amd64: kernel 4.0.0-2 with iwlwifi 7260 reports incorrect wifi bit rate

2015-06-25 Thread Robert Lange
Package: src:linux Version: 4.0.5-1 Severity: normal When using the kernel provided by linux-image-4.0.0-2-amd64, the WiFi bit rate is misreported. The exact (incorrect) bit rate changes on each boot (possibly on the first WiFi connection), but is constant until the computer is rebooted,