Bug#1108168: linux-image-6.12.32-amd64: black screen, then crash in nouveau when rebooting

With the test I've just done, I got no issues with nouveau when disconnecting and reconnecting the dock, but they appeared when I terminated the X session. See attached journalctl.out.xz file. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#1108168: linux-image-6.12.32-amd64: black screen, then crash in nouveau when rebooting

ne+0x4c/0x50 > > The driver attempted to decrement a reference count that was already 0. > This quite likely indicates a use-after-free, which is very bad news. > > On Sun, 2025-06-22 at 19:02 +0200, Vincent Lefevre wrote: > [...] > > It is known that after the dock is temp

Bug#1108168: linux-image-6.12.32-amd64: black screen, then crash in nouveau when rebooting

On 2025-06-22 14:27:51 +0200, Salvatore Bonaccorso wrote: > On Sun, Jun 22, 2025 at 01:47:10PM +0200, Vincent Lefevre wrote: > > I got a permanent black screen this morning. And after I rebooted > > via ssh (as I couldn't have any other access to the machine), the > > log

Bug#1108168: linux-image-6.12.32-amd64: black screen, then crash in nouveau when rebooting

Package: src:linux Version: 6.12.32-1 Severity: important X-Debbugs-Cc: debian-am...@lists.debian.org User: debian-am...@lists.debian.org Usertags: amd64 I got a permanent black screen this morning. And after I rebooted via ssh (as I couldn't have any other access to the machine), the logs show is

Bug#1107739: iproute2: ip-route(8) man page: incorrect "ip route delete" documentation

On 2025-06-13 18:15:55 +0200, Bjørn Mork wrote: > Vincent Lefevre writes: > > > The documentation of "ip route delete" in the ip-route(8) man page is > > incorrect. The man page says: > > > > ip route delete > > delete route > > ip

Bug#1107739: iproute2: ip-route(8) man page: incorrect "ip route delete" documentation

On 2025-06-13 11:43:46 +0100, Luca Boccassi wrote: > Please report such issues directly upstream on netdev, preferably with > a patch. There is no point in opening downstream bugs about manpages > that are just shipped as-is, it's just churn and noise. Thanks. OK, I've sent a mail to the netdev li

Bug#1107739: iproute2: ip-route(8) man page: incorrect "ip route delete" documentation

Package: iproute2 Version: 6.15.0-1 Severity: normal The documentation of "ip route delete" in the ip-route(8) man page is incorrect. The man page says: ip route delete delete route ip route del has the same arguments as ip route add, but their semantics are a bit different.

Bug#1083159: mount: tmpfs size for /tmp is randomly ignored

On 2025-05-06 12:13:24 +0200, Vincent Lefevre wrote: > On 2025-02-21 20:33:21 +0100, Salvatore Bonaccorso wrote: [...] > > So size is only showed if sbinfo->max_blocks != shmem_default_max_blocks(). > > > > Let's look at shmem_default_max_blocks(): > > &g

Bug#1083159: mount: tmpfs size for /tmp is randomly ignored

Sorry, I forgot to reply... On 2025-02-21 20:33:21 +0100, Salvatore Bonaccorso wrote: > Let's start from: > > https://www.kernel.org/doc/html/latest/filesystems/vfs.html#mount-options > > The important bits are: > > Showing options > --- > > If a filesystem accepts mount options, i

Bug#939079: Closing this bug (BTS maintenance for src:linux bugs)

Control: forwarded -1 https://gitlab.freedesktop.org/xorg/xserver/-/issues/49 On 2025-05-01 14:33:19 +0200, Salvatore Bonaccorso wrote: > Since you are able to reproduce it with a fresh kernel, can you please > report the issue upstream (please keep us in the loop so we can > monitor the progress)

Bug#939079: Closing this bug (BTS maintenance for src:linux bugs)

Control: reopen -1 Control: found -1 6.12.13-1 Same laptop as in 2023, with 2 external monitors, xdpyinfo says: screen #0: dimensions:7680x2160 pixels (2032x571 millimeters) resolution:96x96 dots per inch but xrandr gives the correct dimensions of the individual screens: 697mm x 3

Bug#792778: nouveau: screen sometimes remains blank after "xset dpms force off"

Hi, On 2025-02-20 11:09:59 +0100, Salvatore Bonaccorso wrote: > I think in meanwhile we should close this bug downstream. Yes, perhaps. > If it's still reproducible it has be handled upstream first before a > fix can flow down back to us in Debian. This was for a very old machine (2015). I don'

Bug#1098208: linux-image-6.12.13-amd64: display issue with nouveau (disp: error 00000001)

Control: tags -1 - moreinfo Control: close -1 On 2025-02-19 22:28:14 +0100, Salvatore Bonaccorso wrote: > On Mon, Feb 17, 2025 at 07:39:07PM +0100, Vincent Lefevre wrote: [...] > > Feb 17 19:37:05 disset kernel: nouveau :55:00.0: disp: error 0001 > > Feb 17 19:37:05 disset

Bug#1098226: perl: thread creation while a directory handle is open does a fchdir, affecting other threads

This is a bug visible in the perl code, so I've just reported the bug upstream. (Not sure about the severity, but this can yield incorrect file operations in the involved directory, which may be very problematic if this directory is untrusted.) On 2025-02-18 14:26:54 +0100, Vincent Lefevre

Bug#1098226: linux-image-6.12.13-amd64: newfstatat syscall ENOENT failure in multithreaded program

On 2025-02-18 14:07:36 +0100, Vincent Lefevre wrote: > On 2025-02-18 13:49:18 +0100, Vincent Lefevre wrote: > > FYI, I can also reproduce this issue on my Samsung Galaxy S23 Ultra > > phone under Termux/Android. Similarly, running the Perl script with > > "strace -f&

Bug#1098226: linux-image-6.12.13-amd64: newfstatat syscall ENOENT failure in multithreaded program

On 2025-02-18 13:49:18 +0100, Vincent Lefevre wrote: > FYI, I can also reproduce this issue on my Samsung Galaxy S23 Ultra > phone under Termux/Android. Similarly, running the Perl script with > "strace -f" also yields a lot of stat failures. I can also reproduce it un

Bug#1098226: linux-image-6.12.13-amd64: newfstatat syscall ENOENT failure in multithreaded program

FYI, I can also reproduce this issue on my Samsung Galaxy S23 Ultra phone under Termux/Android. Similarly, running the Perl script with "strace -f" also yields a lot of stat failures. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#1017720: nfs-common: No such file or directory

On 2024-04-09 15:58:21 +0200, Vincent Lefevre wrote: > The conditions seem to be: > * The directory and the files need to be recent enough: I can't > reproduce the issue with an old directory, even if I add many > new files into it. > * Concurrent "stat":

Bug#1098226: linux-image-6.12.13-amd64: newfstatat syscall ENOENT failure in multithreaded program

Package: src:linux Version: 6.12.13-1 Severity: important X-Debbugs-Cc: debian-am...@lists.debian.org User: debian-am...@lists.debian.org Usertags: amd64 In a multithreaded program (a Perl script, in my case), the newfstatat syscall[*] can fail with the ENOENT (No such file or directory) error, ev

Bug#1098208: linux-image-6.12.13-amd64: display issue with nouveau (disp: error 00000001)

Package: src:linux Version: 6.12.13-1 Severity: important X-Debbugs-Cc: debian-am...@lists.debian.org User: debian-am...@lists.debian.org Usertags: amd64 After a system upgrade, there is a display issue with nouveau: the top part of the screen is black, and I get lots of errors in the journalctl o

Bug#1084232: initramfs-tools: fails with "No space left on device" due to 2 temporary initrd copies in /boot

On 2024-10-08 20:12:11 +0200, Ben Hutchings wrote: > On Tue, 2024-10-08 at 03:41 +0200, Vincent Lefevre wrote: > > Indeed, with 3 installed kernels: > > > > Filesystem Size Used Avail Use% Mounted on > > /dev/nvme0n1p2 456M 295M 137M 69% /boot > > >

Bug#1084232: initramfs-tools: fails with "No space left on device" due to 2 temporary initrd copies in /boot

On 2024-10-07 21:23:40 +0200, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Mon, 2024-10-07 at 00:39 +0200, Vincent Lefevre wrote: > > Package: initramfs-tools > > Version: 0.145 > > Severity: normal > > > > When updating an initrd file, update-in

Bug#1084232: initramfs-tools: fails with "No space left on device" due to 2 temporary initrd copies in /boot

Control: retitle -1 initramfs-tools: update-initramfs fails with "No space left on device" due to 2 temporary initrd copies in /boot On 2024-10-07 00:39:23 +0200, Vincent Lefevre wrote: > When updating an initrd file, update-initramfs keeps 2 temporary > copies in /boot, tho

Bug#1084232: initramfs-tools: fails with "No space left on device" due to 2 temporary initrd copies in /boot

Package: initramfs-tools Version: 0.145 Severity: normal When updating an initrd file, update-initramfs keeps 2 temporary copies in /boot, though its space is typically *very* limited (456 MB by default). This means that one can keep a limited number of kernels. With the 456 MB default size and ma

Bug#1073998: linux: Purging linux-image- doesn't clean up modules.weakdep file

On 2024-10-06 16:59:17 +0200, Salvatore Bonaccorso wrote: > Hi Vincent, > > On Fri, Oct 04, 2024 at 03:48:10PM +0200, Vincent Lefevre wrote: > > This bug has been fixed in unstable kernels. Shouldn't it be fixed > > in stable kernels too (as the fix is rather trivial)

Bug#1073998: linux: Purging linux-image- doesn't clean up modules.weakdep file

This bug has been fixed in unstable kernels. Shouldn't it be fixed in stable kernels too (as the fix is rather trivial)? For instance, I still have -rw-r--r-- 1 root root 55 2024-10-04 15:30:49 /lib/modules/6.1.0-25-amd64/modules.weakdep while the kernel has been purged. So I got Purging confi

Re: Bug#1083159: mount: tmpfs size for /tmp is randomly ignored

Control: reassign -1 src:linux Control: found -1 6.10.12-1 Control: severity -1 minor Control: notforwarded -1 Control: retitle -1 linux: for tmpfs, /proc/mounts and /proc/self/mountinfo do not always show the size when corresponding to the default, at least on /tmp Summary: On my Debian/unstable

Bug#1080492: firmware-nonfree: [i915] With 20240709-2, the external monitors randomly blank for 2-3 seconds (regression)

Source: firmware-nonfree Version: 20240709-2 Severity: important First, some context: I have a Dell laptop with 2 external monitors connected via a dock. With 6.8+ Linux kernels, one of the external monitors randomly blanks for 2-3 seconds (no such issue with earlier kernels); not always the same

Bug#1072063: one of the external monitors randomly blank for 2-3 seconds with 6.8/6.9 Linux kernels (regression)

Control: found -1 6.9.12-1 Control: forwarded -1 https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11821 On 2024-07-31 20:21:12 +0200, Ben Hutchings wrote: > Could you please report this upstream following > ? Done: h

Bug#1076582: Bug#1077274: Excessive initramfs size with firmware-nvidia-graphics and plymouth

On 2024-07-29 15:59:14 +0200, Rodrigo Campos wrote: > On 7/28/24 10:33 PM, Ben Hutchings wrote: > > This issue was fixed by initramfs-tools version 0.143 in experimental. > > I have just uploaded version 0.143.1 to unstable, so you should be able > > to get the fix through a regular upgrade in a fe

Bug#1076582: Processed (with 1 error): tagging 1076539, forcibly merging 1076582 1076539

Control: notfixed -1 0.143 Control: fixed -1 initramfs-tools/0.143 There's a bug in the BTS software, which forgot the source package name for bug 1076582. On 2024-07-28 20:27:17 +, Debian Bug Tracking System wrote: > After four attempts, the following changes were unable to be made: > fixed_

Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)

On 2024-07-24 10:58:24 +0200, Diederik de Haas wrote: > Uninstalling firmware YOU DON'T NEED is a perfectly valid solution. How can one do that? I mean, get only the Nvidia firmware for my particular Nvidia card, not everything of all the existing cards (which is really the issue). > What IS a ge

Bug#1072063: one of the external monitors randomly blank for 2-3 seconds with 6.8/6.9 Linux kernels (regression)

With a desktop machine (Dell Precision Tower 7810) that has just one monitor, I've noticed a couple of times that the monitor blanked for a fraction of second. I've never noticed that in the past. I don't know whether this is related... -- Vincent Lefèvre - Web: 100% ac

Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)

On 2024-07-19 16:43:47 +0200, Diederik de Haas wrote: > [ not including debian-release for this ] > > On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote: > > On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote: > > > On Friday, 19 July 2024 13:08:50 CE

Bug#1072063: one of the external monitors randomly blank for 2-3 seconds with 6.8/6.9 Linux kernels (regression)

Control: found -1 6.9.8-1 Control: found -1 6.9.9-1 With the linux-image-6.9.8-amd64 6.9.8-1 kernel, the problem occurred on 2024-07-09, a first time with only one blanked monitor and a second time with both monitors blanked. I was off from 2024-07-10 to 2024-07-19 (today) in the morning. With t

Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)

On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote: > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote: > > When upgrading the firmware: > > > > [...] > > Setting up firmware-intel-graphics (20240610-1) ... > > Setting up firmware-iwlwifi (20240610-1)

Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)

On 2024-07-19 13:08:50 +0200, Vincent Lefevre wrote: > update-initramfs: Generating /boot/initrd.img-6.9.9-amd64 > zstd: error 70 : Write error : cannot write block : No space left on device > E: mkinitramfs failure zstd -q -9 -T0 70 > update-initramfs: failed for /boot/initrd.img

Bug#1076582: initramfs-tools-core: mkinitramfs failure zstd -q -9 -T0 70 (No space left on device)

Package: initramfs-tools-core Version: 0.142 Severity: grave Justification: renders package unusable When upgrading the firmware: [...] Setting up firmware-intel-graphics (20240610-1) ... Setting up firmware-iwlwifi (20240610-1) ... Setting up firmware-misc-nonfree (20240610-1) ... Setting up fir

Bug#1072063: one of the external monitors randomly blank for 2-3 seconds with 6.8/6.9 Linux kernels (regression)

Control: found -1 6.9.7-1 Control: retitle -1 one of the external monitors randomly blank for 2-3 seconds with 6.8/6.9 Linux kernels (regression) This bug is still present in linux-image-6.9.7-amd64 6.9.7-1: one of my 2 external monitors (not always the same one) gets blank for a short period. Th

Bug#1072063: one of the external monitors randomly blank for 2-3 seconds with 6.8 kernels

Control: found -1 6.8.12-1 Control: retitle -1 one of the external monitors randomly blank for 2-3 seconds with 6.8 kernels removing "linux-image-6.8.11-amd64" since this is not specific to this version. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Bl

Bug#1055945: linux-image-6.1.0-13-amd64: touchpad buttons sometimes stop working for several seconds/minutes

Control: found -1 6.8.12-1 This still occurs with the current kernel. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1072063: linux-image-6.8.11-amd64: one of the external monitors randomly blank for 2-3 seconds with 6.8 kernels

Package: src:linux Version: 6.8.11-1 Severity: important I have 2 external monitors with my Dell Precision 5570 laptop, connected via the Thunderbolt WD22TB4 dock. With the linux-image-6.8.9-amd64 kernel, then with linux-image-6.8.11-amd64, one of these monitors (not always the same one) randomly

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

Control: tags -1 unreproducible - fixed-upstream Control: close -1 On 2022-11-09 17:16:06 +0100, Vincent Lefevre wrote: > I've tried a couple of cold boots, but this did not reproduce the > issue. Perhaps the bug is rare with my laptop and more common with > some other hardware

Bug#1017720: nfs-common: No such file or directory

On 2024-04-09 14:09:43 +0200, Vincent Lefevre wrote: > Some additional information: created only once, but data may be > appended (on the creator's side, the file is created for writing, > and data are written occasionally, and at some point, the file is > closed). The error with

Bug#1017720: nfs-common: No such file or directory

On 2024-04-04 14:56:47 +0200, Vincent Lefevre wrote: > On 2023-11-29 16:19:02 +0100, Vincent Lefevre wrote: > > I have the same kind of issue at my lab with one of my programs: > > a readdir lists the file, but then a stat sometimes gives a > > "No such file or director

Bug#1017720: nfs-common: No such file or directory

On 2023-11-29 16:19:02 +0100, Vincent Lefevre wrote: > I have the same kind of issue at my lab with one of my programs: > a readdir lists the file, but then a stat sometimes gives a > "No such file or directory" error. Some clients are more affected > that others. An

Bug#1059936: Tracked down `behavior of -n is non-portable`

Control: reassign -1 klibc-utils Control: forcemerge 1055694 -1 Note: Bug 1055694 was initially described as a different bug, but it was retitled on January 9 (to match the change in coreutils), so that it became the same bug as 1059936. Hence the merge. On 2024-01-15 05:09:10 +, Alexander Hu

Bug#1059936: initramfs-tools: update-initramfs yields "cp: warning: behavior of -n is non-portable and may change in future"

Package: initramfs-tools Version: 0.142 Severity: normal I get the following warnings with coreutils 9.4-3: Processing triggers for initramfs-tools (0.142) ... update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64 [...] cp: warning: behavior of -n is non-portable and may change in future; u

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

On 2023-12-19 14:32:31 +0100, Diederik de Haas wrote: > If you manually create those links from the above "+Link:" lines, > would that fix the issues? I've added only the ga107 symlinks (since this is what is needed for my machine) with for i in acr nvdec sec2 do mkdir /usr/lib/firmware/nvidia/

Bug#1040910: Nvidia firmware missing on Testing

On 2023-07-12 11:30:22 +0200, Mauro Sacchetto wrote: > Package: firmware-misc-nonfree > Version: 20230515-3 > > My machine (with Cinnamon) has Nvidia GTX 670. > On Testing, after the last upgrades I receive: > > root@debian:~# update-initramfs -u > update-initramfs: Generating /boot/initrd.img-6.

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Another piece of information: this is a regression. With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107" gives Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: NVIDIA GA107 (b77000a1) Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: firmware: failed to load nvidia/ga107/nvdec/s

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

On 2023-12-19 04:32:02 +0100, Vincent Lefevre wrote: > firmware-misc-nonfree triggers the following warnings: > > update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64 [...] > W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin > for module nouvea

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Package: firmware-misc-nonfree Version: 20230625-1 Severity: grave Justification: renders package unusable firmware-misc-nonfree triggers the following warnings: update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for module

Bug#1055694: klibc-utils: Patch to fix cp warning

Hi, On 2023-12-07 10:43:23 +0100, Mario Izquierdo (mariodebian) wrote: > I found a small typo in initramfs-tools klibc-utils script: > > # diff -ur klibc-utils /usr/share/initramfs-tools/hooks/klibc-utils > --- klibc-utils 2023-12-07 10:35:52.738502916 +0100 > +++ /usr/share/initramfs-tools

Bug#1017720: nfs-common: No such file or directory

On 2022-08-19 13:16:47 +, Jason Breitman wrote: > Package: nfs-common > Version: 1:1.3.4-6 > Severity: important > > Kernel: 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux > > -- Description > After updating and or creating new files on our

Bug#1055931: apt ignores bullseye-backports

Hi Nis, On 2023-11-16 17:31:13 +0100, Nis Martensen wrote: > On 14.11.2023 15.17, Vincent Lefevre wrote: > >> Checking for newer versions at madison and > >> https://ftp-master.debian.org/new.html > >> > >> Your version (6.1.55-1) of linux-image-6.1.0-1

Bug#1055945: linux-image-6.1.0-13-amd64: touchpad buttons sometimes stop working for several seconds/minutes

Package: src:linux Version: 6.1.55-1 Severity: important The touchpad buttons of my new laptop sometimes stop working for several seconds or minutes (typically from 25" to 6'20"). The time between two consecutive issues also varies and can be very short, such as 30 seconds. The device in question

Bug#1055931: apt ignores bullseye-backports

Cc'ing Reportbug Maintainers. On 2023-11-14 14:51:18 +0100, Vincent Lefevre wrote: > Going back to what reportbug says, it still outputs > > [...] > Getting status for linux-image-6.1.0-13-amd64... > Verifying package integrity... > Checking for newer versions at mad

Bug#1055931: apt ignores bullseye-backports

On 2023-11-14 13:45:21 +0100, Vincent Lefevre wrote: > But "apt show -a linux-image-6.1.0-13-amd64" just gives the 6.1.55-1 > version (no 6.1.55+1~bpo11+1 version), and > > apt install -t bullseye-backports linux-image-6.1.0-13-amd64 > > also thinks that 6.1.55-1 is

Bug#939079: nouveau: screen dimensions and resolution are wrong

Control: found -1 6.1.55-1 On 2019-09-01 04:11:15 +0200, Vincent Lefevre wrote: > With the nouveau driver, I get: > > $ xdpyinfo > [...] > screen #0: > dimensions:3200x1800 pixels (846x476 millimeters) > resolution:96x96 dots per inch > [...] > > whi

Bug#970557: Closing this bug (BTS maintenance for src:linux bugs)

Hi, On 2023-09-22 17:10:37 +0200, car...@debian.org wrote: > This bug was filed for a very old kernel or the bug is old itself > without resolution. > > If you can reproduce it with > > - the current version in unstable/testing > - the latest kernel from backports [...] Just a note to say that

Bug#1051844: initramfs-tools-core: the man pages have U+2010 HYPHEN characters instead of U+002D HYPHEN-MINUS

Package: initramfs-tools-core Version: 0.142 Severity: minor In the initramfs-tools(7) man page: Both /usr/share/initramfs‐tools/scripts and /etc/initramfs‐ tools/scripts contains the following subdirectories. where the dashes are U+2010 HYPHEN. This is incorrect and breaks copy-pa

Bug#1040178: Kernel modules will not build, missing asm/orc_header.h

On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote: > This needs to be fixed before linux 6.3.0-2-* can migrate to testing, > otherwise it will break dkms module building for everyone still having > linux-headers-6.3.0-1-* installed (which is probably for the currently > running kernel). On one

Bug#945140: linux-image-5.3.0-2-amd64: system occasionally hangs for several minutes

On 2019-11-20 19:06:25 +0100, Vincent Lefevre wrote: > On 2019-11-20 12:52:09 +0100, Vincent Lefevre wrote: > > Package: src:linux > > Version: 5.3.9-2 > > Severity: important > > > > Since yesterday, the system occasionally hangs for several minutes. > >

Bug#904770: about bugs in the nouveau driver

Note concerning these bugs in the nouveau driver: I haven't done any report since a long time because I do not use the nouveau driver any longer since upstream doesn't care to look at my bug reports (even though some of them are completely reproducible) and some of these bugs make nouveau unusable

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

Hi Salvatore, On 2022-11-05 09:40:20 +0100, Salvatore Bonaccorso wrote: > Reading through the reports and > https://bugzilla.kernel.org/show_bug.cgi?id=215167 I wonder if you can > more easily reproduce your issue with doing cold boot of the machine > or reboot it. I'm asking because it looks that

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

Control: tags -1 upstream Hi Salvatore, On 2022-11-01 08:05:28 +0100, Salvatore Bonaccorso wrote: > What happens if you downgrade firmware-iwlwifi to 20210818-1? Actually, I cannot reproduce the failure with the new kernel, even with the current firmware-iwlwifi. I don't know what happened, but

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

On 2022-10-31 13:09:31 +0100, Vincent Lefevre wrote: > Package: src:linux > Version: 6.0.5-1 > Severity: grave > Justification: renders package unusable > > (Setting to grave because Bluetooth is a major component.) > > Bluetooth no longer works at all. Bluetooth works

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

Package: src:linux Version: 6.0.5-1 Severity: grave Justification: renders package unusable (Setting to grave because Bluetooth is a major component.) Bluetooth no longer works at all. zira:~> journalctl -b -g bluetooth Oct 31 12:55:16 zira kernel: Bluetooth: Core ver 2.22 Oct 31 12:55:16 zira k

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

On 2022-07-04 10:00:04 +0200, Vincent Lefevre wrote: > On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote: > > When update-initramfs runs I receive the following message: > > > > depmod: WARNING: could not open modules.builtin.modinfo at > > /var/tmp/mkinitramfs_vBlw4a

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote: > When update-initramfs runs I receive the following message: > > depmod: WARNING: could not open modules.builtin.modinfo at > /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or > directory I also got such a warning on two of

Bug#782323: linux-image-3.16.0-4-amd64: setting net.ipv6.conf.all.accept_ra to 0 has no effect, thus does not protect against SLAAC attacks

Hi, On 2022-06-01 00:35:03 +0200, Diederik de Haas wrote: > This bug was filed against kernel version 3.16 and the chance that > an upstream kernel developer will devote time to it is ~ 0%, so I'm > closing this bug. > > If you can reproduce it with > > - the current version in unstable/testing

Bug#1010209: linux-image-5.17.0-1-amd64: sr0 and sr1 I/O errors in the journalctl logs when running Wine

Package: src:linux Version: 5.17.3-1 Severity: normal While looking at the journalctl logs, I've noticed the following errors that have been regularly occurring since March 1: Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s A

Bug#1000870: nvidia: module verification failed: signature and/or required key missing - tainting kernel

Package: src:linux Version: 5.15.5-1 Severity: normal I can find in the journalctl logs: cventin kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel It seems that this has occurred since the legacy nvidia driver is used (*nvidia-legacy-390xx-*).

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

On 2021-07-21 18:28:44 -0400, Daniel Lin wrote: > Yes, I haven't used a machine with hid_apple in many years, but the > patch sign-off is OK with me. Thanks. For the reference of my patch submission a few days ago: https://www.spinics.net/lists/linux-input/msg74111.html https://lore.kernel.o

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

On 2021-06-02 17:24:38 +0200, Salvatore Bonaccorso wrote: > Hi Vincent, > > On Wed, May 26, 2021 at 12:02:12PM +0200, Vincent Lefevre wrote: [...] > > I forgot that there was > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356#35 > > > >

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

On 2021-06-02 17:24:38 +0200, Salvatore Bonaccorso wrote: > Can you, time permitting, starting from there (and needed refreshes) > try to confirm if the patch solves the issue on top of 5.10.40? First, the patch did not apply correctly on top of 5.10.46 (currently in unstable). So I've updated it

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

Control: retitle -1 Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c Control: tags -1 patch On 2021-05-26 10:39:11 +0200, Vincent Lefevre wrote: > And the cursor keys. Actually, all the keys corresponding to > > static con

Bug#757356: Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes

Control: retitle -1 Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes On 2021-05-26 09:52:16 +0200, Vincent Lefevre wrote: > No MSC_SCAN line for F1 to F12. [...] > Same issue for the Enter and Backspace keys: [...] And the cursor keys. Actuall

Bug#757356: Scan codes still not generated for F1 to F12, Enter and Backspace

Control: reopen -1 Control: found -1 5.10.38-1 On 2021-04-28 18:39:44 +0200, j...@debian.org wrote: > This bug was filed for a very old kernel. If you can reproduce it with > - the current version in unstable/testing > - the latest kernel from buster.backports > please reopen the bug, see https://

Bug#988539: linux-image-5.10.0-6-amd64: umount of a USB stick froze the system

Package: src:linux Version: 5.10.28-1 Severity: important I copied a big file (> 3 GB) on a USB stick and did "umount" on the device, and after a few dozens of seconds, the system got completely frozen (the clock stopped, I couldn't move the mouse pointer, and the keyboard wasn't reacting either)

Bug#809149: Closing this bug (BTS maintenance for src:linux bugs)

On 2021-05-09 07:21:07 -0700, car...@debian.org wrote: > This bug was filed for a very old kernel or the bug is old itself > without resolution. I confirm that the bug is obsolete. (I'm not sure I could ever reproduce it.) -- Vincent Lefèvre - Web: 100% accessible vali

Bug#792778: nouveau: screen sometimes remains blank after "xset dpms force off"

On 2021-05-08 21:30:11 +0200, Salvatore Bonaccorso wrote: > So this was more recent. I guess still present as well on a recent > kernel? I don't know, as nouveau became completely unusable for me and I'm currently using the NVIDIA driver: https://gitlab.freedesktop.org/xorg/driver/xf86-video-no

Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

FYI, other users got the same error: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848395 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772 https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1624435 https://bugs.gentoo.org/578138 In Debian bug 848395: as said b

Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument

Control: found -1 5.10.24-1 On 2021-05-08 14:53:13 +0200, Salvatore Bonaccorso wrote: > Vincent, is this still something you are able to reproduce with a > recent kernel? If not, should we close the bug? If yes, any more > insights since the last report? I still get the error in the logs due to t

Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

On 2021-05-08 14:54:58 +0200, Salvatore Bonaccorso wrote: > Is this still something you are able to reproduce and have more > insights since then? If you are not able to reproduce it anymore, > should we otherwise close the issue? zira:~> journalctl | grep 'failed with exit code 99' May 18 14:40:5

Bug#922873: linux-image-4.19.0-3-amd64: nouveau "PGRAPH TLB flush idle timeout fail" errors, machine unresponsive via ssh

Control: tags -1 - fixed-upstream Removing the fixed-upstream tags to avoid confusion since the bug is still open upstream and I've never heard of any fix. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA

Bug#922873: linux-image-4.19.0-3-amd64: nouveau "PGRAPH TLB flush idle timeout fail" errors, machine unresponsive via ssh

On 2021-05-02 13:42:28 +0200, Salvatore Bonaccorso wrote: > Can you still reproduce the issue in buster with newest 4.19.y kernel? > Can you reproduce the issue with unstable's or buster-backports > kernel? Not this issue, but I got other crashes since. The latest one: https://bugs.debian.org/c

Bug#710509: linux-image-3.8-2-amd64: Click with the middle button of the DualPoint Stick doesn't always have an immediate effect

On 2013-05-31 15:27:11 +0200, Vincent Lefevre wrote: > A click with the middle button of the DualPoint Stick (above the > touchpad) on my Dell Latitude E6400 doesn't always have an immediate > effect: I sometimes need to press a key to see the effect (pasted > data). This problem

Bug#970557: kernel crash in nouveau

Control: found -1 5.8.10-1 On 2020-09-18 18:07:35 +0200, Vincent Lefevre wrote: > Package: src:linux > Version: 5.8.7-1 > Severity: important > > A short time after updating the kernel and rebooted, the kernel > crashed in nouveau while I wasn't using the machine (I on

Bug#970557: linux-image-5.8.0-1-amd64: kernel crash in nouveau

Package: src:linux Version: 5.8.7-1 Severity: important A short time after updating the kernel and rebooted, the kernel crashed in nouveau while I wasn't using the machine (I only had an ssh session). Sep 18 17:56:26 ypig kernel: [ 1445.181686] [ cut here ] Sep 18 17:56:26

Bug#970503: linux-image-5.8.0-1-amd64: using swap makes the machine hang

On 2020-09-18 10:23:01 +0200, Vincent Lefevre wrote: > https://github.com/openzfs/zfs/issues/8552 suggests a drive firmware > bug (which could explain the absence of errors with smartctl and > badblocks), but in this case the kernel might have a way to avoid it. > > Also I'

Bug#970503: linux-image-5.8.0-1-amd64: using swap makes the machine hang

There is the same issue with the 4.19.132-1 Linux kernel from stable. I've done more tests, and from a VT shortly after the boot, "memhog 15320M" was fine, but "memhog 15350M" gave errors in the console after some time, same as in the dmesg output below. [ 406.347520] ata1.00: exception Emask 0x

Bug#970503: linux-image-5.8.0-1-amd64: using swap makes the machine hang

Package: src:linux Version: 5.8.7-1 Severity: important When swap is used (even a little), the machine hangs. A manual power-off is needed. To reproduce on my machine, which has 16 GB RAM and 20 GB swap: $ memhog 15G (command from the numactl package), e.g. just after the boot. The machine sti

Bug#970235: initramfs-tools-core: typo in /etc/initramfs-tools/initramfs.conf

Package: initramfs-tools-core Version: 0.138 Severity: minor In the latest upgrade, the following comment was added: # FSTYPE: ... # # The filesytem type(s) to support, or "auto" to use the current root # filesystem type In "The filesytem type(s)", replace "filesytem" by "filesystem". -- System

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

On 2020-09-08 13:59:07 +0200, Bastian Blank wrote: > Control: tag -1 moreinfo > Control: severity -1 important > > On Tue, Sep 08, 2020 at 01:36:45PM +0200, Vincent Lefevre wrote: > > This version fails to load kernel modules (no issues with previous > > Linux kernels p

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

Package: src:linux Version: 5.8.7-1 Severity: grave Justification: renders package unusable This version fails to load kernel modules (no issues with previous Linux kernels provided by Debian). As a consequence, X does not work. I've attached the dmesg output. -- Package-specific info: ** Versio

Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

Source: linux Version: 5.6.7-1 Severity: minor With the 5.6.0-1-amd64 Linux kernel at least, I get the following error at boot (shown by journalctl): Apr 30 11:57:16 zira systemd-udevd[489]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' f

Bug#956383: linux-image-5.5.0-1-amd64: artifacts on screen / nouveau_exa_upload_to_screen:380 - falling back to memcpy ignores tiling

On 2020-04-10 16:08:26 +0200, Vincent Lefevre wrote: > I get artifacts on screen when using xpdf or Firefox. I took a photo > for the first one; see attached file. This may be related to the > upgrade to the 5.5.13-2 kernel yesterday, as this problem never > occurred before, IIRC.

Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

Hi, On 2020-03-30 09:06:15 +0200, Ivo De Decker wrote: > On Sun, Mar 29, 2020 at 09:43:42PM +0200, Vincent Lefevre wrote: > > I don't think so, except the use of the nouveau driver, of course. > > But there were no issues for years. I think that problems started > >

  1   2   3   4   >