Bug#1014649: linux-image-5.18.0-2-amd64: System fails to sspend when bluetooth headset is connected

Package: src:linux Version: 5.18.5-1 Severity: normal Dear Maintainer, starting a month or so ago, I can no longer suspend my system when a bluetooth headset is connected. When I select "Sleep" in KDE, the screen goes black, but the laptop keeps running. I have to press the power button for aroun

Bug#1014651: firmware-misc-nonfree: Missing latest i915/skl_guc firmware

Package: firmware-misc-nonfree Version: 20210818-1 Severity: normal Dear Maintainer, on boot, my system says it needs this firmware: Jul 09 09:59:17 r-thinktop kernel: i915 :00:02.0: firmware: failed to load i915/skl_guc_69.0.3.bin (-2) Jul 09 09:59:17 r-thinktop kernel: firmware_class: See

Bug#782442: USB3 external HDD not recognized [regression]

Hi again, > Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control" > fixes the problem: When I subsequently plug in the disk, it is > recognized correctly. I confirmed this with an older kernel (the 3.16 > Debian kernel, to be more precise). That's good to know, now I don't > nee

Bug#782442: USB3 external HDD not recognized [regression]

Hi, >>> Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control" >>> fixes the problem: When I subsequently plug in the disk, it is >>> recognized correctly. I confirmed this with an older kernel (the 3.16 >>> Debian kernel, to be more precise). That's good to know, now I don't >>>

Bug#782442: USB3 external HDD not recognized [regression]

Hi, >>> I got some untested and not yet reviewed usb3 resume race fixes from Zhuang >>> Jin Can >>> If you can try them out and see if they help it would be great. >>> They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree: >>> (5 extra patches on top of current usb-linus) >>>

Bug#781953: linux-image-3.16.0-4-amd64: Verbose messages at boot time

Package: src:linux Version: 3.16.7-ckt7-1 Severity: normal Dear Maintainer, when using th grub graphical mode and a graphical plymouth theme, a pretty seamless boot experience becomes possible with current Debian. There is however one piece of text output remaining (or actually, it came up somew

Bug#781953: closed by Ben Hutchings (Bug#781953: fixed in linux 3.16.7-ckt9-1)

> #781953: linux-image-3.16.0-4-amd64: Verbose messages at boot time > > It has been closed by Ben Hutchings . Wow, that was fast - thanks a lot :) Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas..

Bug#782442: linux-image-3.16.0-4-amd64: USB3 regression: External hard disk does not work anymore

Package: src:linux Version: 3.16.7-ckt9-1 Severity: normal Dear Maintainer, one of my external hard disks does not work anymore with current kernels, when I plug it into my USB3 port. Steps to reproduce: * Boot the system without the disk being connected * Plug the disk into my Laptop's USB3 por

Bug#782442: USB3 regression: External hard disk does not work anymore

Hi again, I now tested various upstream kernels and was able to reproduce the issue with upstream v3.16, but *not* with upstream v3.15 or v3.14. I will try some more times and then report this upstream. It seems to me that the issue is introduced by a patch that Debian already shipped with v3.14,

Bug#782442: USB3 regression: External hard disk does not work anymore: upstream bug report

Hi, I reported this upstream at . Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/552ab62c.60

Bug#782442: USB3 external HDD not recognized [regression]

Hi all, One of my external hard disks does not work anymore with current kernels, when I plug it into my USB3 port. Steps to reproduce: * Boot the system without the disk being connected * Plug the disk into my Laptop's USB3 port * Watch dmesg and my DE's removable media notification Behavior wi

Bug#782442: USB3 external HDD not recognized [regression]

Hi, > The USB-3 driver is made up of these files: drivers/usb/host/xhci* I did a bisect on these files only, and here's the result: > d6236f6d1d885aa19d1cd7317346fe795227a3cc is the first bad commit > commit d6236f6d1d885aa19d1cd7317346fe795227a3cc > Author: Wang, Yu > Date: Tue Jun 24 17:14

Bug#782442: USB3 external HDD not recognized [regression]

Hi again, >> d6236f6d1d885aa19d1cd7317346fe795227a3cc is the first bad commit >> commit d6236f6d1d885aa19d1cd7317346fe795227a3cc >> Author: Wang, Yu >> Date: Tue Jun 24 17:14:44 2014 +0300 >> >> xhci: Fix runtime suspended xhci from blocking system suspend. > > I confirmed that reverting t

Bug#782442: USB3 external HDD not recognized [regression]

Hi, > Ok, xhci is reset in resume in your case (indicated by the "root hub lost > power or was reset" messages) > That patch adds an additional check that ensures there was some event before > resuming the roothub. > > Could you try out the following and see if it helps? If the event is > lost

Bug#782442: USB3 external HDD not recognized [regression]

Hi, > Attached a testpatch based on 4.1-rc2 Thanks. Unfortunately, this patch did not help: I saw no change in behavior compared to vanilla 4.1-rc2. I should probably mention that there is a slight difference in the log output of the 3.16 and 4.1 kernels: The "xhci_hcd :04:00.0: irq 42 for M

Bug#785526: firmware-linux-nonfree: initramfs trigger only rebuilds initdisk of latest kernel

Package: firmware-linux-nonfree Version: 0.44 Severity: normal Dear Maintainer, when the package firmware-linux-nonfree is installed, it triggers the hook of the initramdisk package. I conclude that some firmware may be needed by the initramfs (which makes sense to me), and hence it is importan

Bug#785526: firmware-linux-nonfree: initramfs trigger only rebuilds initdisk of latest kernel

Hi, >> when the package firmware-linux-nonfree is installed, it triggers the hook >> of the initramdisk >> package. I conclude that some firmware may be needed by the initramfs (which >> makes sense to me), >> and hence it is important to keep the initramfs up-to-date as firmware is >> updated.

Bug#763172: iwlwifi: Microcode SW error

Hi, I reported this bug upstream as Kind regards Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/543d0600.

Bug#763172: iwlwifi: Microcode SW error

Hi, > I'm having exactly the same problem on my Dell Latitude E7240 at every > boot. I can only use the card after rmmod iwlmvm iwlwifi && modprobe > iwlwifi . Could you submit a full dmesg? In particular, could you check whether the WiFi kill flag was set when the problem occured? As we found ou

Bug#762285: [Regression] Brightness control does not work anymore

Hi, there's a patch in the upstream bug report at . It would be great if that patch (or whatever ends up being submitted/accepted upstream) could land in Jessie, as this will fix backlight control for at least some Laptops with multiple GPUs - a f

Bug#763172: iwlwifi: Microcode SW error

Hi, there's now a patch in the upstream bug report (and soon to be submitted upstream) that seems to fix the issue on my machine. It turns out that this is probably not a regression in the kernel, but introduced by the fact that systemd restores

Bug#763172: iwlwifi: Microcode SW error

Hi again, this patch has made it into an upstream stable release, and it seems that it entered Debian as well. I cannot reproduce the issue anymore. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas..

Bug#762285: [Regression] Brightness control does not work anymore

Hi, this issue is still present in current kernels. There's a working patch upstream that landed in 3.19 (as dce4ec2e). Not being able to control the backlight is a pretty disturbing regression, so I would appreciate if you could consider this patch. Kind regards, Ralf -- To UNSUBSCRIBE, email

Bug#761428: linux-image-3.16-1-amd64: [regression] SD card reader in Asus X53SM does not work anymore

Package: src:linux Version: 3.16.2-3 Severity: normal Dear Maintainer, with the current unstable kernel (3.16), the SD card reader in my Asus X53SM does not work anymore. When I plugin in a card, nothing happens in dmesg or anywhere else (as far as I can tell). The same card reader works fine w

Bug#761428: linux-image-3.16-1-amd64: [regression] SD card reader in Asus X53SM does not work anymore

Hi, >> It seems to be enabled through CONFIG_MFD_RTSX_USB, which I don't see >> anywhere in the Debian packaging (svn sid branch). > [...] > > It is enabled. But the new driver's author forgot to include the device > ID list in the module metadata. So the driver should work if loaded by > runni

Bug#761428: linux-image-3.16-1-amd64: [regression] SD card reader in Asus X53SM does not work anymore

Hi, I verified the solution with a vanilla kernel, and reported it upstream as . Kind regards Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#761825: linux-image-3.16-1-amd64: Now Bluetooth errors on system boot

Package: src:linux Version: 3.16.2-3 Severity: normal Dear Maintainer, since I upgraded to the linux 3.16 packages, I am getting the following bluetooth error on every system boot: kernel: Bluetooth: hci0 sending initial HCI reset command failed (-19) I saw so such error with the 3.14 kernel

Bug#762285: linux-image-3.16-2-amd64: [Regression] Brightness control does not work anymore

Package: src:linux Version: 3.16.3-1 Severity: normal Dear Maintainer, the brightness control of my Laptop does not work anymore. It used to work with the 3.14 kernel. Previous behavior (3.14): * When I drag the brightness slider in KDE, the OSD appears and the brightness changes. * After some

Bug#762285: linux-image-3.16-2-amd64: [Regression] Brightness control does not work anymore

Hi, I reported this upstream at . Kind regards Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542184bf.804

Bug#763172: iwlwifi: Microcode SW error

Package: src:linux Version: 3.16.3-2 Severity: normal Dear Maintainer, the wireless driver occasionally complains about microcode errors. This happens around twice a week. It didn't happen at all with the 3.14 kernel. My laptop runs an Intel Wireless 7260 card. Here's the "iwlwifi" part of the l

Bug#811276: linux-image-4.3.0-1-amd64: [regression] Error when ethernet is unplugged: r8169 0000:05:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).

Package: src:linux Version: 4.3.3-5 Severity: normal Dear Maintainer, Since I rebooted my machine on Jan 12th, I am seeing the following error over and over in my kernel log: r8169 :05:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10). The error appears roughly every 10sec, whene

Bug#942700: linux-image-5.2.0-3-amd64: Regularly, 1 CPU core is entirely hogged by kworker/0:1+kacpid

Package: src:linux Version: 5.2.17-1 Severity: important Dear Maintainer, Since the most recent kernel update, I regularly have 100% load on one CPU core, According to top, the load is caused by "kworker/0:1+kacpid". I have never seen this effect before so this is a recent regression. This happ

Bug#953291: linux-image-amd64: udp SO_REUSEPORT broken (fix in 4.19.75)

Package: linux-image-amd64 Version: 4.19+105+deb10u1~bpo9+1 Severity: normal Tags: upstream Dear Maintainer, Since kernel 4.5, SO_REUSEPORT was somewhat broken for UDP when [1] landed. The fix for this was backported to the 4.19 series in 4.19.75 [2]. However, both kernels available on Debian ol

Bug#619711: console-setup: breaks copying keymap to initramfs

Hi, is there any progress on this one? This recently bit me quite hard when I installed a system with full-disk encryption, using a password which required the correct keyboard layout to be entered. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a su

Bug#568008: Error message problem persists

found 568008 linux-2.6/3.1.8-2 thanks The error messages are still shown with the 3.1 kernel. > But for some reason there is not a single alias for the modules that > implement SHA-1: > > $ grep '^alias sha1 ' /lib/modules/3.0.0-1-amd64/modules.alias > alias sha1 sha1_generic > > $ grep '^alias

Bug#568008: FATAL: Error inserting padlock_sha: No such device

Hi everyone, are there any updates on this? With current Debian testing (Kernel 2.6.39), I am still getting this error on boot: FATAL: Error inserting padlock_sha (/lib/modules/2.6.39-2- amd64/kernel/drivers/crypto/padlock-sha.ko): No such device I understand it is harmless, but it should still b

Bug#485070: cryptsetup: "FATAL" padlock_{aes,sha} error during boot

Hi, as per request of Jonathan at http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=485070, I am reporting the mentioned bug to this list as well: With current Debian testing (Kernel 2.6.39), I am getting this error on each boot: FATAL: Error inserting padlock_sha (/lib/modules/2.6.39-2- amd64/

Bug#568008: cryptsetup: strange padlock_aes error during boot

Hi, > So this is a different bug. > > I've unmerged and reopened #568008 which refers to padlock_sha. Thanks! I already wondered why some bugs referred to aes and some for sha, but assumed they were the same as they were merged. So the sha problem remains. Does "this is safe to ignore" apply to

Bug#638863: linux-image-3.0.0-1-amd64: Errors/warnings show during startup

Package: linux-2.6 Version: 3.0.0-1 Severity: minor Each time I start up my laptop, the following errors (warnings?) appear: [5.083819] shpchp :00:01.0: Cannot reserve MMIO region [5.447322] SP5100 TCO timer: mmio address 0xfec000f0 already in use The system is working fine as far as

Bug#638863: linux-image-3.0.0-1-amd64: Errors/warnings show during startup

Hi, > Let's deal with the first one. It seems like a real problem because > it distracts people debugging other problems. The second should be > filed as a separate bug if you are interested in working on it. > [snip] > > The test has been that way ever since v2.6.15-rc1~731^2~22^2~13 > (shpch

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

Hi list, each time I start up my laptop (Debian testing, Linux 3.0 as provided in the repositories), the following error (warning?) appears: [5.083819] shpchp :00:01.0: Cannot reserve MMIO region The system is working fine as far as I can tell. I observed that message for quite a while

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

Hi Bjorn, > Ralf, can you attach your /proc/iomem contents, too? I looked at the > "SP5100 TCO timer: mmio address 0xfec000f0 already in use" message, > but I don't see why that address is in use. Sure, you can find it attached. I am getting some more kernel error messages during boot (that I pl

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

Hi, > Here's a test patch for the TCO timer issue. That SP5100 watchdog > driver is a mess -- it gropes around at hard-coded places in I/O port > space -- so while I think this patch will fix the message, the > watchdog itself still may not work. If you can verify that the > watchdog works, that

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

Hi Bjorn, > Here's a test patch for the TCO timer issue. That SP5100 watchdog > driver is a mess -- it gropes around at hard-coded places in I/O port > space -- so while I think this patch will fix the message, the > watchdog itself still may not work. If you can verify that the > watchdog works

Bug#638863: "shpchp: Cannot reserve MMIO region" error during boot (linux 3.0)

Hi, > I don't know what's in the "watchdog" package. I would try the test > program in the kernel sources: > Documentation/watchdog/src/watchdog-simple.c. > > It looks like if you kill any other process that has /dev/watchdog > open (use "lsof" to check), then start watchdog-simple, then suspend

Bug#685108: linux-image-3.2.0-3-amd64: Error message on each boot: [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed

Package: src:linux Version: 3.2.21-3 Severity: normal Dear Maintainer, I am receiving the following error message twice on each boot: [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed My Asus X53SM laptop has a Sandy Bridge CPU (Core i5 2450M), and google suggests that this error i

Bug#568008: linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device

Hi, somewhen during the last three weeks, this error went away on my system. I am however not sure whether this is due to some configuration change, or whether the bug was fixed. Did anyone else experience this problem and saw it go away recently? Kind regards, Ralf -- To UNSUBSCRIBE, email

Bug#638863: linux-image-3.0.0-1-amd64: Errors/warnings show during startup - forward to upstream?

Hi, from what I understood, it is acknowledged that this is actually a bug in the upstream kernel, so I'd like to report it at the kernel bugzilla. However I do not know which bugzilla category to use - could someone give me a hint please? Kind regards, Ralf -- To UNSUBSCRIBE, email to debi

Bug#638863: Errors/warnings show during startup - forward to upstream?

Hi, > > from what I understood, it is acknowledged that this is actually a bug in > > the upstream kernel, so I'd like to report it at the kernel bugzilla. > > Sounds like a good idea. Please let us know the bug number if doing > so so we can track it. Here you go: https://bugzilla.kernel.org/sh

Bug#670958: [2.6.37 -> 2.6.38-rc6 regression] udev/power_supply battery oscilates between remove and add

Hi, nice to finally see some activity on this :) > > What do you recommend next? > > Nice. That narrows it down to one of 104 patches, which means > 7 rounds of bisection would narrow it down to a single patch: [...] > > If you go through step 5 enough times, it will reveal the "first bad > co

Bug#670958: [2.6.37 -> 2.6.38-rc6 regression] udev/power_supply battery oscilates between remove and add

Hi again, > 2. make sure the upstream kernel reproduces the bug: > > cd linux > cp /boot/config-$(uname -r) .config; # current configuration > scripts/config --disable DEBUG_INFO > make localmodconfig; # optional: minimize configuration > make deb-pkg; # optionally

Bug#670958: [regression] HP ProBook 451x: udev/power_supply battery oscilates between remove and add

Hi, > So far I have determined that the following HP laptop models are > affected: > - HP Probook 451x > - HP Compaq 315 (Ralf's) > - HP 6735-s (alculquicondor from the Archlinux forum thread) It's a compaq 615 ;-) > > ACPI functionalities that are broken so far: > - power_supply (battery and AC

Bug#670958: [regression] HP laptops: udev/power_supply battery oscilates between remove and add

Hi, > An alternative set of instructions is at [2]. > > If you get a chance to try this, please describe the result to Andy by > replying-to-all to his message (i.e., not this one). Whoever is first > should probably also mention that pertinent is misspelled. ;-) If you > have any questions, pl

Bug#898767: linux-image-4.16.0-1-amd64: (temporary, unreliable) hang on boot since upgrade to 4.16

Package: src:linux Version: 4.16.5-1 Severity: grave Justification: renders package unusable Dear Maintainer, since the upgrade to kerkenl 4.16, the system does not boot reliably any more. Instead, most of the time, it hangs showing the following messages: [2.639465] nouveau :01:00.0: bu

Bug#890039: linux-image-4.14.0-3-amd64: unable to handle kernel NULL pointer dereference

Package: src:linux Version: 4.14.13-1 Severity: normal Dear Maintainer, I was in the middle of an `aptitude upgrade` and rebooting a virtual machine at the same time, when my machine froze entirely. After a reboot, I found the following at the tail of the journal: Feb 10 11:42:25 r-thinktop sys

Bug#906728: linux-perf-4.17: "perf report" fails with "failed to process sample"

Package: linux-perf-4.17 Version: 4.17.14-1 Severity: important Dear Maintainer, fairly frequently, after recording perf data with perf record -F99 --call-graph dwarf [...] when I then immediately do perf report I get an error message saying failed to process sample 0x44098e [0x8]: f

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Package: linux-image-4.18.0-0.bpo.3-amd64 Version: 4.18.20-2~bpo9+1 Severity: normal Tags: upstream Dear Maintainer, I reported an upstream bug at that got a patch submitted with .

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: >> Package: linux-image-4.18.0-0.bpo.3-amd64 >> Version: 4.18.20-2~bpo9+1 >> Severity: normal >> Tags: upstream >> >> Dear Maintainer, >> >> I reported an upstream bug at >>

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > Once a version uploaded to sid, migrates to testing, it can be > prepared for stable-backports based on that. > > So what will need to happen here: upload of 4.19.13-2 to unstable > (actually possibly only >= 4.19.14-1 if we do not have pressure to > upload 4.19.13-2), then wait it migrates

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

Package: linux-image-4.9.0-8-amd64 Version: 4.9.144-3 Severity: critical Justification: breaks the whole system Dear Maintainer, after installing the kernel updates that got released to Debian stable earlier today or yesterday, we saw all the three updated systems fail in the same way: after 3-5h

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

Oh, I should probably also mention that these machines all run an extra kernel module compiled via dkms: batman-adv 2019.0 from . The same kernel module also runs on a fourth machine with the same setup, but which hasn't gotten the kernel update yet, and that machine run

Bug#924349: linux-image-4.19.0-2-amd64: IPv6 reverse path filtering incorrectly removes IPv6 traffic from bridge

Package: src:linux Version: 4.19.16-1 Severity: normal Dear Maintainer, since a recent update, IPv6 communication between two of my VMs stopped working. You can see some of the debugging effort at . It turned out that setting IPv6_rpfilter=no

Bug#924349: linux-image-4.19.0-2-amd64: IPv6 reverse path filtering incorrectly removes IPv6 traffic from bridge

Hi Salvatore, >> A self-compiled upstream 4.20.14 kernel does not show this problem, but the >> latest kernel in testing still does. > > have you tried to isolate the fixing commit for this issue? No, I have not. We are having a string of weird issues in our network (that we run in our free time

Bug#924349: linux-image-4.19.0-2-amd64: IPv6 reverse path filtering incorrectly removes IPv6 traffic from bridge

Hi, >> No, I have not. >> We are having a string of weird issues in our network (that we run in our >> free >> time) so far this year so all the time I had went into debugging this and >> other >> issues. >> >> Would it be helpful for you to know the fixing commit? > > If the fixing commit can