On 15.11.24 09:15, Salvatore Bonaccorso wrote:
Greg did post a series of reverts upstream for 6.1.118-rc1, which are
to address this issue.
https://lore.kernel.org/stable/20241115063722.599985...@linuxfoundation.org/
Are you able to test this in time and report back on that the series
of revert
On 05.11.24 22:00, Salvatore Bonaccorso wrote:
Would you be able to confirm that packages in stable-backports or
testing/unstable do not expose anymore the issue?
Back end of June I switched to linux-image-6.6.13-1~bpo12+1 and had no
issues after that.
Udo
Hi,
Seeing exactly the same bug with an Broadcom Corp. BCM2045B (BDC-2.1)
bluetooth device, so its not just the Intel AX211.
Jeremy, thanks for tracking this down!
Udo
For reference, my oops:
> INFO: rcu_sched self-detected stall on CPU { 0} (t=5250 jiffies g=7643
> c=7642 q=2543)
> sending NMI to all CPUs:
> NMI backtrace for cpu 0
> CPU: 0 PID: 5205 Comm: qemu-system-x86 Not tainted 3.13-1-686-pae #1 Debian
> 3.13.10-1
> Hardware name: To Be Filled By O.E.M.
I think I'm seeing this bug too, need to check the logs later. Its
definitely some kind of oops using KVM on 3.13.
CPU: Athlon64 X2, 4Gb RAM
Kernel: linux-image-3.13-1-686-pae (3.13.10-1 and 3.13.7-1) in Jessie/i386
Bug can be avoided by booting the old 3.12 kernel.
Symptoms: Works normally, but
I've been on the full v11 patch for 2 1/2 weeks, no issues to report.
I've switched to the less intrusive patch now, again built on top of
3.2.0-0.bpo.1-686-pae, and I'll report on anything unusual.
As long as I don't report, you can assume that it either fused all of my
computers, or just wo
Am 05.04.2012 21:54, schrieb Udo Richter:
> I've applied patch v8 to the source package of of 3.2.4-1~bpo60+1, and
> the resulting kernel package fixed it for me too. I've just successfully
> hibernated 10 times in a row, before I could hardly hibernate more than
> one or two
I've applied patch v8 to the source package of of 3.2.4-1~bpo60+1, and
the resulting kernel package fixed it for me too. I've just successfully
hibernated 10 times in a row, before I could hardly hibernate more than
one or two times without hanging.
--
To UNSUBSCRIBE, email to debian-kernel-re
It seems I am seeing the same bug too, on
linux-image-3.2.0-0.bpo.1-686-pae, 3.2.4-1~bpo60+1. However, I'm on an
nVidia nForce 570 chipset (AMD A64-x2), esp. using the sata_nv driver.
About half of the hibernate-disk cycles do work, the other half starts
writing the image to some point just normal
Am 27.12.2011 21:56, schrieb Ben Hutchings:
> Can you test whether wake-on-LAN works with the current version in
> testing (3.1.5-1)? You will need to upgrade initramfs-tools and
> linux-base to install the later kernel version, but nothing else.
Seems to be working fine with 3.1.5-1, suspending
Package: linux-2.6
Version: 2.6.32-39
Severity: normal
Tags: squeeze
Between 2.6.32-35 and 2.6.32-36, the ability to wake-on-lan from
suspend-to-disk got lost for my mainboard. Waking from poweroff and from
suspend-to-ram still works. This is probably related to bug #627700. The
bug is present up
11 matches
Mail list logo
