Bug#992131: R8169 CRASH! (rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100))

Still happening with 6.6 on Sid...

Bug#947685: still occuring on Linux 6.1.0-9-amd64 x86_64

I'm still having 6.1.0-9-amd64 on hold. Latest 6.5 does not fix it yet.

Bug#1039965: linux-image-6.1.0-9-amd64: crash on boot

I've found workaround: adding i915.enable_dc=0 to kernel boot parameters fixes (workarounds) this issue.

Bug#1039965: linux-image-6.1.0-9-amd64: crash on boot

Forgot to mention that my machine runs on i7-11700. Also tried Testing (Trixie) LiveCD with Linux 6.4 and it works fine.

Bug#1039965: linux-image-6.1.0-9-amd64: crash on boot

I blieve I have similar issue with linux-image-6.1.0-0.deb11.9-amd64 and linux-image-6.1.0-0.deb11.11-amd64 from backports installed in Debian 11. linux-image-6.1.0-0.deb11.7-amd64 works fine. I can boot with nomodeset too. Debian 12.1 Live CD also hangs doring boot! Here are some i915-related

Bug#992131: R8169 CRASH! (rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100))

This is probably relevant upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=209839

Bug#947685: still occuring on Linux 6.1.0-9-amd64 x86_64

Here's some more info - it first crashes and then starts logging these messages: Jun 20 19:37:31 kernel: [ cut here ] Jun 20 19:37:31 kernel: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0 timed out Jun 20 19:37:31 kernel: WARNING: CPU: 7 PID: 0 at

Bug#992131: R8169 CRASH! (rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100))

I've just started getting this on Sid with 6.3: Jun 19 20:17:43 kernel: r8169 :05:00.1: can't disable ASPM; OS doesn't have ASPM control Jun 19 20:17:43 kernel: r8169 :05:00.1 enp5s0f1: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). On Sat, 18 Jun 2022 16:02:28 +0200

Bug#947685: still occuring on Linux 6.1.0-9-amd64 x86_64

I have started getting issues again with recent 6.3 upgrade in Sid, network become unstable: Jun 19 20:17:43 kernel: r8169 :05:00.1: can't disable ASPM; OS doesn't have ASPM control Jun 19 20:17:43 kernel: r8169 :05:00.1 enp5s0f1: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update

On Sun, 24 Apr 2022 11:20:30 +0200 Salvatore Bonaccorso wrote: Would you be able to test the current kernel from unstable so we can confirm it's fixed in 5.17.3-1? I've installed 5.18 from bullseye-backports: Aug 19 23:45:36 dl380 kernel: [0.00] Linux version 5.18.0-0.bpo.1-amd64

Bug#1012835: linux-image-5.10.0-15-amd64: entropy dropped to 256 from ~4k after 5.10.120-1 update

Package: src:linux Version: 5.10.120-1 Severity: normal Dear Maintainer, I've noticed in Munin graphs that entropy dropped significantly after reboot to 5.10.120-1. Please see images attached. Not sure if this is actually a problem/bug, but that kind of drop "out of nowhere" seems at least

Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update

2022-04-24 12:20, Salvatore Bonaccorso rašė: Would you be able to test the current kernel from unstable so we can confirm it's fixed in 5.17.3-1? I am not sure if I want to install kernel from unstable into production machine.. :) . I believe I'll wait for Bullseye backport to see if it

Bug#1010745: usb-storage: kernel taks hung when copying data via USB SATA adapter from external SSD with bad blocks

Package: src:linux Version: 5.16.12-1~bpo11+1 Severity: normal Dear Maintainer, It seems we can't use Linux for cloning drive data from faulty drives (with bad blocks) using USB SATA adapters. I wanted to clone data from this old SSD: ``` Device Model: LITEONIT LCM-128M3S 2.5" 7mm 128GB

Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update

It seems that this might be fixed in ~5.17, based on this [0] message in thread that speaks about problem seemingly similar to mine: Yes, I expect to submit it into the next merge window (not the current v5.16 merge window, but v5.17). However, if your situation is urgent, and if it works for

Bug#947685: linux-image-5.4.0-1-amd64: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0 timed out

On Sun, 2 May 2021 14:03:24 +0200 Salvatore Bonaccorso wrote: is this still reproducible with a recent kernel? I am running linux-image-5.16.0-6-amd64 5.16.18-1 with commented-out (disabled) workaround "ethtool -K enp5s0f1 tx off sg off tso off" and I no longer see any problems.

Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update

Package: src:linux Version: 5.10.106-1 Severity: minor Dear Maintainer, After linux-image-5.10.0-12-amd64 5.10.103-1 was installed, kernel log started to be "spammed" with "clocksource:" messages on HP ProLiant DL380 G6 server. Same on latest 5.10.0-13 package. Version 5.10.103-1 changelog does

Bug#775215: Closing this bug

I cannot reproduces this because remounting to produces "mount: /: mount point is busy." error.

Bug#956511: linux-image-5.5.0-1-amd64: general protection fault in i915_active_ref with 5.5

On Sun, 12 Apr 2020 19:24:03 +0100 Ben Hutchings wrote: Is this reproducible without the nvidia drivers loaded at all? Sorry, idk, I cannot reproduce it any more.

Bug#956511: linux-image-5.5.0-1-amd64: general protection fault in i915_active_ref with 5.5

Package: src:linux Version: 5.5.13-2 Severity: important Dear Maintainer, After upgrading to 5.5 on Sid, I've experiencing full computer freeze after some time of playing, for example, minetest for some time (even though I use `optirun` to use discrete graphics). Problems are completely gone if

Bug#947685: linux-image-5.4.0-1-amd64: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0 timed out

Disabling offloading helps as workaround, see: https://lore.kernel.org/netdev/81548409-2fd3-9645-eeaf-ab8f7789b...@gmail.com/

Bug#947685: linux-image-5.4.0-1-amd64: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0 timed out

Same in 5.4.13-1.

Bug#947685: linux-image-5.4.0-1-amd64: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0 timed out

Found similar issue in kernel mailing list: https://lkml.org/lkml/2019/11/30/119 I don't know anything about these "jumbo frames" thought, but problem is similar to my issue.

Bug#947685: linux-image-5.4.0-1-amd64: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0 timed out

Same with 5.4.8-1

Bug#906769: arm kernels fail to boot

On 8/22/18 7:35 AM, Salvatore Bonaccorso wrote: armhf packages: https://people.debian.org/~carnil/tmp/linux/armhf/ armmp-lpae works fine on Odroid-HC1 SBC (Samsung Exynos5422 ARM® Cortex™-A15 Quad 2.0GHz/Cortex™-A7 Quad 1.4GHz)

Bug#906769: arm kernels fail to boot

On Mon, 20 Aug 2018 15:16:52 -0700 Vagrant Cascadian wrote: One "armmp-lpae" system appears to have successfully booted, but gets many kernel messages along these lines: [ 78.638348] INFO: rcu_sched detected stalls on CPUs/tasks: [ 78.642433] 0-...: (0 ticks this GP) idle=29c/0/0

Bug#902966: pstore: crypto_comp_decompress failed

Why is this bug marked as Done? Issue still persists with 4.17.0-2-amd64 on ASUS N551JM laptop. If users (upgrading from Strech) are expected to execute these workarounds, maybe there should be NEWS entry of some sort?

Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail

On Mon, 7 May 2018 06:40:36 +0200 "Sten Heinze" wrote:> I definitely experience a much shorter delay if I press keys on the keyboard vs. doing nothing; the delay decreases from >5 minutes to 10-20 seconds before sddm appears. Yes! I have same problem, thought not with 4.16, but with 4.17. If

Bug#874432: More info

I have found the core issue. It's not about kernel update, it's about the fact that Thunderbird package now has usr.bin.thunderbird AppArmor profile, and it conflicted with other profile usr.lib.thunderbird.thunderbird I had enabled earlier (attached). Kernel upgrade just made me to reboot

Bug#872726: linux: apparmor doesn't use proper audit event ids

This is upstream bug report: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1117804

Bug#872726: linux: apparmor doesn't use proper audit event ids

On Sun, 20 Aug 2017 16:42:55 +0200 Laurent Bigonville wrote: IMVHO, in regard to the recent proposal of enabling apparmor in debian by default, this needs to be addressed first. Yes this is very important, although we have aa-logprof to be used as auditing tool, but I agree

Bug#775215: Same on 4.8

tags 775215 +stretch thanks I can still reproduce crash with 4.8.7-1 on Debian Testing Virtualbox machine.

Bug#783449: linux-image-3.16.0-0.bpo.4-amd64: Xorg fails to start with Radeon HD 7600M on Vostro 3560 after upgrade to 3.16

2016-02-22 15:43 GMT+02:00 Andreas Beckmann : > Does that conbination even build the kernel module? Well, actually, I just figured it out that it was not successfully built. linux-headers-3.16.0-0.bpo.4-amd64 packages was missing. Now after installing headers and reinstalling

Bug#775215: Jessie crashes too

I have just tested Debian Jessie with default 3.16 kernel, it seems that it crashes too. Attached screenshot with a little different call trace.

Bug#775215: linux-image-3.2.0-4-amd64: Segmentation fault in ext4_clear_journal_err when remounting ext4 filesystem after disabling journal

Package: src:linux Version: 3.2.65-1 Severity: important Dear Maintainer, I wanted to disable journal for my root ext4 filesystem running in virtual Debian Wheezy amd64 (using Virt Manager, KVM machine), but just after remounting filesystem to 'rw' mode with disabled journal, kernel

Bug#730434: same problem

Up-to-date Debian 7.6 here, I've noticed that after coming back to work after lunch break hour (no suspend, just screen lock), Dolphin freezes. Even new Dolphin instances locks up. I am not sure how it fixes up, some times I just restart system. I've tried to run: $stat /media/public And