Bug#982956: next report
I've tested following: v5.0.2 v5.2.17 v5.3.15 v5.4.19 with debian patches applied, and compiled for Pentium M CPU - suspend / resume working fine! compiling: v5.10.70 v5.10.1 makes 'task blocked for..." appear. Seems like this is 5.10 kernel issue. I'm trying kernel git 'bisect' for the first time, to find the exact bug causing this issue. Wish me luck! -- AK
Bug#998186: linux-base: Issue on func cdev_init.
Package: linux-base Version: 4.6 Severity: normal On file fs/char_dev.c function cdev_init old line is memset(cdev, 0, sizeof *cdev); and new line can bee memset(cdev, 0, sizeof (struct cdev)); Allocation issue. -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.8+ (SMP w/2 CPU cores) Kernel taint flags: TAINT_DIE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.71+deb10u1 linux-base recommends no packages. linux-base suggests no packages. -- debconf information excluded
Processed: reassign 998173 to linux
Processing commands for cont...@bugs.debian.org: > reassign 998173 linux 5.10.70-1 Bug #998173 [5.10.70-1] linux-image-5.10.0-9-amd64: with kernel version 5.10.0-9-amd64 LED is permanently blinking Warning: Unknown package '5.10.70-1' Bug reassigned from package '5.10.70-1' to 'linux'. Ignoring request to alter found versions of bug #998173 to the same values previously set Ignoring request to alter fixed versions of bug #998173 to the same values previously set Bug #998173 [linux] linux-image-5.10.0-9-amd64: with kernel version 5.10.0-9-amd64 LED is permanently blinking There is no source info for the package 'linux' at version '5.10.70-1' with architecture '' Unable to make a source version for version '5.10.70-1' Marked as found in versions 5.10.70-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 998173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 998173 to 5.10.70-1
Processing commands for cont...@bugs.debian.org: > reassign 998173 5.10.70-1 Bug #998173 [linux-image-5.10.0-9-amd64] linux-image-5.10.0-9-amd64: with kernel version 5.10.0-9-amd64 LED is permanently blinking Bug reassigned from package 'linux-image-5.10.0-9-amd64' to '5.10.70-1'. Warning: Unknown package '5.10.70-1' Warning: Unknown package '5.10.70-1' Ignoring request to alter found versions of bug #998173 to the same values previously set Warning: Unknown package '5.10.70-1' Warning: Unknown package '5.10.70-1' Ignoring request to alter fixed versions of bug #998173 to the same values previously set Warning: Unknown package '5.10.70-1' > thanks Stopping processing here. Please contact me if you need assistance. -- 998173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998173: linux-image-5.10.0-9-amd64: with kernel version 5.10.0-9-amd64 LED is permanently blinking
Package: linux-image-5.10.0-9-amd64 Severity: normal Dear Maintainer, with the upgrade from kernel version 5.10.0-8-amd64 to version 0-9-amd64 I notice a very annoying issue with my wireless card. Problem is, the LED is permanently blinking, not (as it was with the former kernel) when there is real trffic. The kernel module which is responsible for that, is ath5k.ko (This is an Atheros card) Normally the wireless LED only blinks, when there is real traffic aimed to my IP. However, with 0-9- the LED is permanently blinking. I could verify, that it is no traffic created by the notebook itself (used tcpdump) and killed all network processes (daemons/apps whatever) running on the system. But even when there were no processes running except the one needed for the connection with the router, the LED kept on blinking. Further investigation showed, that the blinking appeared due to the broadcast packages sent by the router. The wireless card thinks, this is normal traffic and the LED blinks. This is bad for me, as the LED was in the past often a good sign, when soemthing fishy is going on. If the LED is only blinking from time to time, everything is ok, but when it was blinking som,ething special is going on (i.e. an update is running or freshclam is updating, but also some brute force attacks could also be discovered.) It would be nice, if you could examine, what has changed at the new kernel, and I would be happy, when I could get the old behaviour back. At the moment I reverted back to kernel 5.10.0-8-0*, which is running perfectly. Thank you very much for all the help! Best regards Hans -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Re: Bug#996557: linux-image-5.14.0-3-686-pae-unsigned: just about every sse2 program crashes with a SIGFPE
Processing control commands: > tags -1 + moreinfo Bug #996557 [src:linux] linux-image-5.14.0-3-686-pae-unsigned: just about every sse2 program crashes with a SIGFPE Added tag(s) moreinfo. -- 996557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996557: linux-image-5.14.0-3-686-pae-unsigned: just about every sse2 program crashes with a SIGFPE
Control: tags -1 + moreinfo Hi On Fri, Oct 15, 2021 at 02:52:17PM +0200, Jiri Palecek wrote: > Package: src:linux > Version: 5.14.12-1 > Severity: serious > X-Debbugs-Cc: Jiri Palecek > > Dear Maintainer, > > when I booted my system with the latest kernel from unstable, many of > the applications didn't work. That includes plasmashell (so I couldn't > log in into plasma) and chromium. > > I ran xterm (which worked) and some of these failing programs under gdb > and found they all tripped on some sse2 instructions with a > SIGFPE. However, all the programs work under the kernel from > linux-image-5.14.0-2-. This is interesting as looking at the commits between 5.14.9 and 5.14.12 there does not seem to be much related. As pointed out by Ben offlist, the only plausible commit in this area might be 0723d4f8b179d "x86/fpu: Restore the masking out of reserved MXCSR bits". Can you thus please: Verify the issue is still present in 5.14.15 and furthermore try to bisect the commit which introduces the problem for you. In particular check if the 0723d4f8b179d commit is the culprit. Regards, Salvatore
