Bug#1010448: firmware-misc-nonfree: Please backport: nvidia: fix symlinks for tu104/tu106 acr unload firmware

Package: firmware-misc-nonfree Version: 20210315-3 Severity: normal Tags: patch Dear Maintainer, Could you please backport this upstream fix: f8462923ed8 "nvidia: fix symlinks for tu104/tu106 acr unload firmware" I'm using nouveau with a GPU that uses the tu106 firmware. Before this fix, suspend

Bug#788999: pthread_mutex_trylock on x86 with lock elision is broken

. I think https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759197 has the same root cause. Thanks, Brian Silverman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#724805: qemu-kvm: internal error with guest kernel bug

Package: qemu-kvm Version: 1.1.2+dfsg-6 Severity: normal While working on bug 724802 (ie reproducing it repeatedly on a guest kernel), I got an error message from KVM (copied in a bit later on in this message). That bug is some kind of serio

Bug#723180: some more testing

I had some time today, so I set up a QEMU VM to work on reproducing this, and I found some interesting things. First of all, I can reproduce it pretty consistently in the VM with this kernel (the -rt one), but I can't reproduce it at all with linux-image-3.2.0-4-amd64 (the default Wheezy one). Als

Bug#723180: linux-image-3.2.0-4-rt-amd64: kernel oops with futexes and gdb reverse-next

After all of that, I can see from the logs that everything was still working enough to recognize the USB flash drive that I plugged in to boot off of. Impressive... On Tue, Sep 17, 2013 at 7:17 AM, Ben Hutchings wrote: > On Mon, 2013-09-16 at 23:13 -0700, Brian Silverman wrote: > > Pac

Bug#723180: linux-image-3.2.0-4-rt-amd64: kernel oops with futexes and gdb reverse-next

Package: src:linux Version: 3.2.46-1+deb7u1 Severity: normal I was working on some custom mutex code (implemented using futexes), and it wasn't working, so I started it up under GDB, waited until it died, and then tried reverse stepping back to where it did something wrong. I then got a kernel oop