Bug#989571: marked as done (linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption)
Your message dated Tue, 8 Jun 2021 06:20:31 +0200 with message-id and subject line Re: Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption has caused the Debian Bug report #989571, regarding linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 989571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.13-1~bpo10+1 Severity: critical Justification: causes serious data loss Dear Maintainer, Large USB drives (example - Seagate 4TB Backup) which work perfectly fine with 4.19 are identified as incorrect size. In the case of the 4TB sized USB it's identified as a 17GB and for some unfatomable reason mounted as loop. The result is severe data corruption making all 4TB of data on the drive unrecoverable. Tested with the original USB bridge coming with the drive and after attaching the SATA drive inside to an alternative USB bridge. Same result in both cases. -- Package-specific info: ** Version: Linux version 5.10.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc-8 (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) ** Command line: BOOT_IMAGE=diskless/amd64/vmlinuz-5.10.0-0.bpo.3-amd64 initrd=diskless/amd64/initrd.img-5.10.0-0.bpo.3-amd64 root=/dev/nfs ip=dhcp nfsroot=192.168.3.3:/exports/boot/madding mitigations=off rw -- ** Tainted: S (4) * SMP kernel oops on an officially SMP incapable processor ** Kernel log: [754632.929276] nfs: server 192.168.3.3 OK [754635.600887] rpc_check_timeout: 443 callbacks suppressed [754635.600889] nfs: server 192.168.3.3 not responding, still trying [754635.612996] nfs: server 192.168.3.3 not responding, still trying [754635.625266] nfs: server 192.168.3.3 not responding, still trying [754635.625462] nfs: server 192.168.3.3 not responding, still trying [754635.637374] nfs: server 192.168.3.3 not responding, still trying [754635.649472] nfs: server 192.168.3.3 not responding, still trying [754635.661739] nfs: server 192.168.3.3 not responding, still trying [754635.661922] nfs: server 192.168.3.3 not responding, still trying [754635.673850] nfs: server 192.168.3.3 not responding, still trying [754635.686131] nfs: server 192.168.3.3 not responding, still trying [791938.374623] lxc-bridge0: port 3(tap-opsft2-0) entered blocking state [791938.374628] lxc-bridge0: port 3(tap-opsft2-0) entered forwarding state [791938.374654] lxc-bridge0: port 4(tap-opsft3-0) entered blocking state [791938.374655] lxc-bridge0: port 4(tap-opsft3-0) entered forwarding state [791938.375075] lxc-bridge0: port 2(tap-opsft1-0) entered blocking state [791938.375078] lxc-bridge0: port 2(tap-opsft1-0) entered forwarding state [791938.388241] k8-bridge0: port 2(tap-opsft1-1) entered blocking state [791938.388243] k8-bridge0: port 2(tap-opsft1-1) entered forwarding state [791938.388402] k8-bridge0: port 4(tap-opsft3-1) entered blocking state [791938.388405] k8-bridge0: port 4(tap-opsft3-1) entered forwarding state [791938.388481] k8-bridge0: port 3(tap-opsft2-1) entered blocking state [791938.388484] k8-bridge0: port 3(tap-opsft2-1) entered forwarding state [801076.265404] usb 4-2.4: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd [801076.289933] usb 4-2.4: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 [801076.289937] usb 4-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [801076.289939] usb 4-2.4: Product: ASM105x [801076.289940] usb 4-2.4: Manufacturer: ASMT [801076.289942] usb 4-2.4: SerialNumber: [801076.291139] scsi host10: uas [801076.291557] scsi 10:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6 [801076.292065] sd 10:0:0:0: Attached scsi generic sg0 type 0 [801076.292232] sd 10:0:0:0: [sda] Spinning up disk... [801077.321342] ..ready [801082.447597] sd 10:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [801082.447600] sd 10:0:0:0: [sda] 4096-byte physical blocks [801082.447673] sd 10:0:0:0: [sda] Write Protect is off [801082.447674] sd 10:0:0:0: [sda] Mode Sense: 43 00 00 00 [801082.447832] sd 10:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [801082.448032] sd 10:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) [801082.494646] sd 10:0:0:0: [sda] Attached SCSI disk
Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption
Close please. The 17G was from trying to blank the drive, which for some reason disconnected in the process resulting in a file written in /dev with the name sda. From there on the loop and so on. So there was a /dev/sda file as a left-over after that. Thanks for pointing me in the right direction and apologies. I am going to continue investigating why I got the data corruption in the first place, before I tried to blank it, but it looks like it may have been a hardware issue with the original USB-to-ATA bridge. -- Anton R. Ivanov https://www.kot-begemot.co.uk/
linux-signed-i386_5.10.40+1~bpo10+1_source.changes is NEW
binary:acpi-modules-5.10.0-0.bpo.7-686-di is NEW. binary:acpi-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:ata-modules-5.10.0-0.bpo.7-686-di is NEW. binary:ata-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.7-686-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.7-686-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:crc-modules-5.10.0-0.bpo.7-686-di is NEW. binary:crc-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.7-686-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:crypto-modules-5.10.0-0.bpo.7-686-di is NEW. binary:crypto-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:efi-modules-5.10.0-0.bpo.7-686-di is NEW. binary:efi-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:event-modules-5.10.0-0.bpo.7-686-di is NEW. binary:event-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:ext4-modules-5.10.0-0.bpo.7-686-di is NEW. binary:ext4-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.7-686-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:fat-modules-5.10.0-0.bpo.7-686-di is NEW. binary:fat-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:fb-modules-5.10.0-0.bpo.7-686-di is NEW. binary:fb-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:firewire-core-modules-5.10.0-0.bpo.7-686-di is NEW. binary:firewire-core-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:fuse-modules-5.10.0-0.bpo.7-686-di is NEW. binary:fuse-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:i2c-modules-5.10.0-0.bpo.7-686-di is NEW. binary:i2c-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:input-modules-5.10.0-0.bpo.7-686-di is NEW. binary:input-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:isofs-modules-5.10.0-0.bpo.7-686-di is NEW. binary:isofs-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:jfs-modules-5.10.0-0.bpo.7-686-di is NEW. binary:jfs-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:kernel-image-5.10.0-0.bpo.7-686-di is NEW. binary:kernel-image-5.10.0-0.bpo.7-686-pae-di is NEW. binary:linux-image-5.10.0-0.bpo.7-686 is NEW. binary:linux-image-5.10.0-0.bpo.7-686-pae is NEW. binary:linux-image-5.10.0-0.bpo.7-rt-686-pae is NEW. binary:loop-modules-5.10.0-0.bpo.7-686-di is NEW. binary:loop-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:md-modules-5.10.0-0.bpo.7-686-di is NEW. binary:md-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:mmc-core-modules-5.10.0-0.bpo.7-686-di is NEW. binary:mmc-core-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:mmc-modules-5.10.0-0.bpo.7-686-di is NEW. binary:mmc-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:mouse-modules-5.10.0-0.bpo.7-686-di is NEW. binary:mouse-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.7-686-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:multipath-modules-5.10.0-0.bpo.7-686-di is NEW. binary:multipath-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:nbd-modules-5.10.0-0.bpo.7-686-di is NEW. binary:nbd-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:nic-modules-5.10.0-0.bpo.7-686-di is NEW. binary:nic-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:nic-pcmcia-modules-5.10.0-0.bpo.7-686-di is NEW. binary:nic-pcmcia-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.7-686-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.7-686-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.7-686-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:pata-modules-5.10.0-0.bpo.7-686-di is NEW. binary:pata-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:pcmcia-modules-5.10.0-0.bpo.7-686-di is NEW. binary:pcmcia-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:pcmcia-storage-modules-5.10.0-0.bpo.7-686-di is NEW. binary:pcmcia-storage-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:ppp-modules-5.10.0-0.bpo.7-686-di is NEW. binary:ppp-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:rfkill-modules-5.10.0-0.bpo.7-686-di is NEW. binary:rfkill-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:sata-modules-5.10.0-0.bpo.7-686-di is NEW. binary:sata-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.7-686-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:scsi-modules-5.10.0-0.bpo.7-686-di is NEW. binary:scsi-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.7-686-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:serial-modules-5.10.0-0.bpo.7-686-di is NEW. binary:serial-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:sound-modules-5.10.0-0.bpo.7-686-di is NEW. binary:sound-modules-5.10.0-0.bpo.7-686-pae-di is NEW. binary:speakup-modules-5.10.0-0.bpo.7-686-di is NEW. binary:speakup-modules-5.10.0-0.bpo.7-686-pae-di is NEW.
Processing of linux-signed-i386_5.10.40+1~bpo10+1_source.changes
linux-signed-i386_5.10.40+1~bpo10+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_5.10.40+1~bpo10+1.dsc linux-signed-i386_5.10.40+1~bpo10+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: Re: Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption
Processing control commands: > severity -1 important Bug #989571 [src:linux] linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption Severity set to 'important' from 'critical' > tags -1 moreinfo Bug #989571 [src:linux] linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption Added tag(s) moreinfo. -- 989571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption
Control: severity -1 important
Control: tags -1 moreinfo
On Mon, Jun 07, 2021 at 08:43:21PM +0100, Anton Ivanov wrote:
> Version: 5.10.13-1~bpo10+1
This is not the latest version. 5.10.24 (at least) is in buster-backports.
> [801076.291139] scsi host10: uas
> [801076.291557] scsi 10:0:0:0: Direct-Access ASMT 2115 0
> PQ: 0 ANSI: 6
> [801076.292065] sd 10:0:0:0: Attached scsi generic sg0 type 0
> [801076.292232] sd 10:0:0:0: [sda] Spinning up disk...
> [801077.321342] ..ready
> [801082.447597] sd 10:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00
> TB/3.64 TiB)
> [801082.447600] sd 10:0:0:0: [sda] 4096-byte physical blocks
> [801082.447673] sd 10:0:0:0: [sda] Write Protect is off
> [801082.447674] sd 10:0:0:0: [sda] Mode Sense: 43 00 00 00
> [801082.447832] sd 10:0:0:0: [sda] Write cache: enabled, read cache: enabled,
> doesn't support DPO or FUA
> [801082.448032] sd 10:0:0:0: [sda] Optimal transfer size 33553920 bytes not a
> multiple of physical block size (4096 bytes)
> [801082.494646] sd 10:0:0:0: [sda] Attached SCSI disk
So it detects a 4TB disk called sda. Not a <20GB as you claimed.
> [801150.687429] loop: module loaded
> [801150.815997] EXT4-fs (loop0): mounted filesystem with ordered data mode.
> Opts: (null)
> [803002.579925] blk_update_request: I/O error, dev loop0, sector 0 op
> 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
> [803002.579960] blk_update_request: I/O error, dev loop0, sector 0 op
> 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
But you mount an unrelated loop0. Don't do that? Okay, write requests
fail.
> [803318.984016] EXT4-fs (loop0): mounting ext3 file system using the ext4
> subsystem
> [803318.984583] EXT4-fs (loop0): mounted filesystem with ordered data mode.
> Opts: (null)
Again you mount loop0, but now it sees an ext3, not an ext4 on it.
Something on your system creates loop devices. You have to find it.
Maybe the output of "lsblk" can help to see what you actually have.
Bastian
--
There's a way out of any cage.
-- Captain Christopher Pike, "The Menagerie" ("The Cage"),
stardate unknown.
Bug#989571: linux-image-5.10.0-0.bpo.3-amd64: Incorrect large USB disk sizing leading to data corruption
Package: src:linux Version: 5.10.13-1~bpo10+1 Severity: critical Justification: causes serious data loss Dear Maintainer, Large USB drives (example - Seagate 4TB Backup) which work perfectly fine with 4.19 are identified as incorrect size. In the case of the 4TB sized USB it's identified as a 17GB and for some unfatomable reason mounted as loop. The result is severe data corruption making all 4TB of data on the drive unrecoverable. Tested with the original USB bridge coming with the drive and after attaching the SATA drive inside to an alternative USB bridge. Same result in both cases. -- Package-specific info: ** Version: Linux version 5.10.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc-8 (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) ** Command line: BOOT_IMAGE=diskless/amd64/vmlinuz-5.10.0-0.bpo.3-amd64 initrd=diskless/amd64/initrd.img-5.10.0-0.bpo.3-amd64 root=/dev/nfs ip=dhcp nfsroot=192.168.3.3:/exports/boot/madding mitigations=off rw -- ** Tainted: S (4) * SMP kernel oops on an officially SMP incapable processor ** Kernel log: [754632.929276] nfs: server 192.168.3.3 OK [754635.600887] rpc_check_timeout: 443 callbacks suppressed [754635.600889] nfs: server 192.168.3.3 not responding, still trying [754635.612996] nfs: server 192.168.3.3 not responding, still trying [754635.625266] nfs: server 192.168.3.3 not responding, still trying [754635.625462] nfs: server 192.168.3.3 not responding, still trying [754635.637374] nfs: server 192.168.3.3 not responding, still trying [754635.649472] nfs: server 192.168.3.3 not responding, still trying [754635.661739] nfs: server 192.168.3.3 not responding, still trying [754635.661922] nfs: server 192.168.3.3 not responding, still trying [754635.673850] nfs: server 192.168.3.3 not responding, still trying [754635.686131] nfs: server 192.168.3.3 not responding, still trying [791938.374623] lxc-bridge0: port 3(tap-opsft2-0) entered blocking state [791938.374628] lxc-bridge0: port 3(tap-opsft2-0) entered forwarding state [791938.374654] lxc-bridge0: port 4(tap-opsft3-0) entered blocking state [791938.374655] lxc-bridge0: port 4(tap-opsft3-0) entered forwarding state [791938.375075] lxc-bridge0: port 2(tap-opsft1-0) entered blocking state [791938.375078] lxc-bridge0: port 2(tap-opsft1-0) entered forwarding state [791938.388241] k8-bridge0: port 2(tap-opsft1-1) entered blocking state [791938.388243] k8-bridge0: port 2(tap-opsft1-1) entered forwarding state [791938.388402] k8-bridge0: port 4(tap-opsft3-1) entered blocking state [791938.388405] k8-bridge0: port 4(tap-opsft3-1) entered forwarding state [791938.388481] k8-bridge0: port 3(tap-opsft2-1) entered blocking state [791938.388484] k8-bridge0: port 3(tap-opsft2-1) entered forwarding state [801076.265404] usb 4-2.4: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd [801076.289933] usb 4-2.4: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 [801076.289937] usb 4-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [801076.289939] usb 4-2.4: Product: ASM105x [801076.289940] usb 4-2.4: Manufacturer: ASMT [801076.289942] usb 4-2.4: SerialNumber: [801076.291139] scsi host10: uas [801076.291557] scsi 10:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6 [801076.292065] sd 10:0:0:0: Attached scsi generic sg0 type 0 [801076.292232] sd 10:0:0:0: [sda] Spinning up disk... [801077.321342] ..ready [801082.447597] sd 10:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) [801082.447600] sd 10:0:0:0: [sda] 4096-byte physical blocks [801082.447673] sd 10:0:0:0: [sda] Write Protect is off [801082.447674] sd 10:0:0:0: [sda] Mode Sense: 43 00 00 00 [801082.447832] sd 10:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [801082.448032] sd 10:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) [801082.494646] sd 10:0:0:0: [sda] Attached SCSI disk [801150.687429] loop: module loaded [801150.815997] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [803002.579925] blk_update_request: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [803002.579960] blk_update_request: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [803017.725341] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [803081.125594] blk_update_request: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [803081.125635] blk_update_request: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [803085.522063] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [803239.336895] blk_update_request: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [803239.336950] blk_update_request: I/O
Bug#927184: Closing this bug (BTS maintenance for src:linux bugs)
Thanks, Salvatore! I think there are few commits with the fix: https://git.kernel.org/linus/b69d540da7db84e836cea77fbd56a518aafa1f2f https://git.kernel.org/linus/ceb159e30ad22efa0981d544e6166003515aa896 https://git.kernel.org/linus/a927d6af53eec08661628e3992d74736e848a743 https://git.kernel.org/linus/cc1bb845adc9b3a005cbb67fd18c69af1c3aec94 https://git.kernel.org/linus/24969facd704a5f0dd8e08da86bf32a9ce972bee https://git.kernel.org/linus/b5fe22e2337d47cd68bb7d8e4103a628808c4d5e https://git.kernel.org/linus/6be3b0db6db82cf056a72cc18042048edd27f8ee https://git.kernel.org/linus/9cf545ebd591da673bb6b6c88150212ad83567a9 https://git.kernel.org/linus/e901cbc29316fb06423de5dfbc5afb78d4efda53 https://git.kernel.org/linus/64a09a7bfedee6ab97273d653dfac28e82635b61 https://git.kernel.org/linus/6ac098b2a9d3088781f1c2b7138cf38e817a3da7 I've got this list here: https://kernelnewbies.org/Linux_5.0 "Improve xfrm policy lookup performance when a lot of (several hundred or even thousands) inexact policies exist on a system" On 6/7/21 11:15 PM, Salvatore Bonaccorso wrote: Hi, On Sat, May 29, 2021 at 11:29:31PM +0500, Yury Vidineev wrote: Hi, It's fixed in the backports, but still exists in the current stable 4.19. Thanks; I have added a fixed version for that. If you are able to tackle the fxining commit(s) then we might look what we can do for 4.19.y. Regards, Salvatore
linux-signed-arm64_5.10.40+1~bpo10+1_source.changes is NEW
binary:ata-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:crc-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:crypto-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:efi-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:event-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:ext4-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:fat-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:fb-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:fuse-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:i2c-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:input-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:isofs-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:jfs-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:kernel-image-5.10.0-0.bpo.7-arm64-di is NEW. binary:leds-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:linux-image-5.10.0-0.bpo.7-arm64 is NEW. binary:linux-image-5.10.0-0.bpo.7-cloud-arm64 is NEW. binary:linux-image-5.10.0-0.bpo.7-rt-arm64 is NEW. binary:loop-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:md-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:mmc-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:multipath-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:nbd-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:nic-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:ppp-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:sata-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:scsi-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:squashfs-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:udf-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:uinput-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:usb-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:usb-serial-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:usb-storage-modules-5.10.0-0.bpo.7-arm64-di is NEW. binary:xfs-modules-5.10.0-0.bpo.7-arm64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Bug#927184: Closing this bug (BTS maintenance for src:linux bugs)
Hi, On Sat, May 29, 2021 at 11:29:31PM +0500, Yury Vidineev wrote: > Hi, > > It's fixed in the backports, but still exists in the current stable 4.19. Thanks; I have added a fixed version for that. If you are able to tackle the fxining commit(s) then we might look what we can do for 4.19.y. Regards, Salvatore
Processing of linux-signed-arm64_5.10.40+1~bpo10+1_source.changes
linux-signed-arm64_5.10.40+1~bpo10+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_5.10.40+1~bpo10+1.dsc linux-signed-arm64_5.10.40+1~bpo10+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: fixed 927184 in 5.10.40-1
Processing commands for cont...@bugs.debian.org:
> fixed 927184 5.10.40-1
Bug #927184 {Done: car...@debian.org} [src:linux] linux-image-4.19.0-4-amd64:
Linux 4.19 reports wrong numbers for NVME disks in /proc/diskstats
Marked as fixed in versions linux/5.10.40-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
927184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #989285 (http://bugs.debian.org/989285) # Bug title: linux-image-5.10.0-6-amd64: Elantech trackpoint loses sync and jumps to the corner/edge of the screen # * http://bugzilla.kernel.org/show_bug.cgi?id=209167 # * remote status changed: (?) -> NEW usertags 989285 + status-NEW thanks
linux-signed-amd64_5.10.40+1~bpo10+1_source.changes is NEW
binary:acpi-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:ata-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:btrfs-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:cdrom-core-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:crc-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:crypto-dm-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:crypto-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:efi-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:event-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:ext4-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:f2fs-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:fat-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:fb-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:firewire-core-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:fuse-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:i2c-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:input-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:isofs-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:jfs-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:kernel-image-5.10.0-0.bpo.7-amd64-di is NEW. binary:linux-image-5.10.0-0.bpo.7-amd64 is NEW. binary:linux-image-5.10.0-0.bpo.7-cloud-amd64 is NEW. binary:linux-image-5.10.0-0.bpo.7-rt-amd64 is NEW. binary:loop-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:md-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:mmc-core-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:mmc-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:mouse-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:mtd-core-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:multipath-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:nbd-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:nic-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:nic-pcmcia-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:nic-shared-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:nic-usb-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:nic-wireless-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:pata-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:pcmcia-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:pcmcia-storage-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:ppp-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:rfkill-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:sata-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:scsi-core-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:scsi-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:scsi-nic-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:serial-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:sound-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:speakup-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:squashfs-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:udf-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:uinput-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:usb-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:usb-serial-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:usb-storage-modules-5.10.0-0.bpo.7-amd64-di is NEW. binary:xfs-modules-5.10.0-0.bpo.7-amd64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Processing of linux-signed-amd64_5.10.40+1~bpo10+1_source.changes
linux-signed-amd64_5.10.40+1~bpo10+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.10.40+1~bpo10+1.dsc linux-signed-amd64_5.10.40+1~bpo10+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#836211: dpkg: Cannot upgrade some packages on overlayfs: Invalid cross-device link
On Wed, 31 Aug 2016 12:16:10 -0300 Felipe Sateler wrote:> unable to move aside './usr/share/bug/apt' to install new version: Invalid cross-device link > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) I'm hitting this bug when attempting to use debian in a container backed by overlayfs. Kernel version on host: 5.12.8.arch1-1 It works fine with kernel 5.10.41-1. -- Tomas Krizek PGP: 4A8B A48C 2AED 933B D495 C509 A1FB A5F7 EF8C 4869 OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#989551: linux-image-5.10.0-7-amd64: linux-image-5.10.0.7-amd64 hang on boot. Shows symbols: '^@^@^@' and nothing else. Debian testing.
Processing control commands: > notfound -1 5.10.28-1 Bug #989551 [src:linux] linux-image-5.10.0-7-amd64: linux-image-5.10.0.7-amd64 hang on boot. Shows symbols: '^@^@^@' and nothing else. Debian testing. No longer marked as found in versions linux/5.10.28-1. > found -1 5.10.38-1 Bug #989551 [src:linux] linux-image-5.10.0-7-amd64: linux-image-5.10.0.7-amd64 hang on boot. Shows symbols: '^@^@^@' and nothing else. Debian testing. Marked as found in versions linux/5.10.38-1. > tags -1 + moreinfo Bug #989551 [src:linux] linux-image-5.10.0-7-amd64: linux-image-5.10.0.7-amd64 hang on boot. Shows symbols: '^@^@^@' and nothing else. Debian testing. Added tag(s) moreinfo. -- 989551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989551: linux-image-5.10.0-7-amd64: linux-image-5.10.0.7-amd64 hang on boot. Shows symbols: '^@^@^@' and nothing else. Debian testing.
Control: notfound -1 5.10.28-1 Control: found -1 5.10.38-1 Control: tags -1 + moreinfo On Mon, Jun 07, 2021 at 02:09:20PM +0300, Mikhail Osipov wrote: > Package: src:linux > Version: 5.10.28-1 > Severity: important > X-Debbugs-Cc: osm...@gmail.com > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** I'm assuming here it is relating to the https://lists.debian.org/debian-kernel/2021/06/msg00066.html report, thus adjusting the found version to 5.10.38-1. Mikhail, we have only litte information here to sensibly tackle the problem. When you boot 5.10.38-1 do you get any usefull information logged in the logs? Can you attach those to the bug? Please try to boot without quiet (and splash), do you get more information printed and indication where it hangs? Regards, Salvatore
Processed: Re: Bug#989539: apt upgrade reports "possibly missing firmware" causing undue concern.
Processing control commands: > reassign -1 initramfs-tools-core Bug #989539 [apt] apt upgrade reports "possibly missing firmware" causing undue concern. Bug reassigned from package 'apt' to 'initramfs-tools-core'. No longer marked as found in versions apt/2.2.3. Ignoring request to alter fixed versions of bug #989539 to the same values previously set -- 989539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#989539: apt upgrade reports "possibly missing firmware" causing undue concern.
Control: reassign -1 initramfs-tools-core Hi, On Sun, Jun 06, 2021 at 06:00:52PM -0400, ? wrote: > This is a known issue that when users perform an apt-upgrade that > upgrades system/kernel components. > > Actual Result: "Possibly missing firmware ..." E.g. i915 > Expected Result: No messages that firmware may be missing. I don't know if more than it already checks is technically possible or if your suggestion would help (I don't have the slightest idea from which year the hardware is I am using or the exact model name without looking it up, so adding that info would confuse me just as much if not more I guess…). In either case apt has and can not do anything about it. It is output produced by one of the packages which are installed/upgraded. In this case a codesearch over Debian suggests one of the methods from /usr/share/initramfs-tools/hook-functions which is contained in initramfs-tools-core. I am therefore reassign this bug to them. Best regards David Kalnischkies signature.asc Description: PGP signature
