Processed: Re: Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs
Processing control commands: > close -1 Bug #977647 [src:linux] 5.10.19 Debian kernel has mysterious tpm error in dmesg Marked Bug as done -- 977647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs
Control: close -1 >> The severity seems now minor. >> It has still the mysterious dmesg error on tpm as follows. >> The full dmesg log is attached. > > Do you still have the issues? Otherwise let's close this bug. No. Let's close this. Ryutaroh
Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads
On Saturday, 2 April 2022 15:36:53 CEST Francesco C wrote: > Vanilla kernel 5.16.18 built with custom .config for the specific > machine fails to boot at the same point too. As you appear to be familiar with kernel building, could you look at the patches that Damien Le Moal posted in this bug report? > I'm also trying to track stable patches in the stable tree queue > (https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/log > /) but it seems to me at the moment there not any patch about ata_pxii in > the 5.16.x branch and in the 5.17.x either. AFAICT, we're still at the stage of identifying the problem, so I don't expect anything in the stable-queue until we're past that stage. signature.asc Description: This is a digitally signed message part.
Processed: found 1006149 in 5.16.18-1
Processing commands for cont...@bugs.debian.org: > found 1006149 5.16.18-1 Bug #1006149 [src:linux] linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads Marked as found in versions linux/5.16.18-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads
linux-image-5.16.0-6-686 (5.16.18-1) still does not boot on a different machine with the same controller. Vanilla kernel 5.16.18 built with custom .config for the specific machine fails to boot at the same point too. I'm also trying to track stable patches in the stable tree queue (https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/log/) but it seems to me at the moment there not any patch about ata_pxii in the 5.16.x branch and in the 5.17.x either.
Bug#1007799: Backport to bullseye
Hi! Any chance we can get this into the bullseye kernel? Best regards, David signature.asc Description: This is a digitally signed message part
Bug#993689: marked as done (linux-image-5.10.0-0.bpo.5-amd64-unsigned: L2CAP receive buffer overflow when using PC as LDAC sink)
Your message dated Sat, 2 Apr 2022 11:26:12 +0200
with message-id
and subject line Re: Bug#993689: linux-image-5.10.0-0.bpo.5-amd64-unsigned:
L2CAP receive buffer overflow when using PC as LDAC sink
has caused the Debian Bug report #993689,
regarding linux-image-5.10.0-0.bpo.5-amd64-unsigned: L2CAP receive buffer
overflow when using PC as LDAC sink
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.)
--
993689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.10.24-1~bpo10+1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I installed bluealsa with LDAC sink support according to this instruction:
https://github.com/anonymix007/libldacdec/blob/master/README.md
The actual problem is that playback stops after a while.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I commented out "goto drop" line in net/bluetooth/l2cap_core.c
if (chan->imtu < skb->len) {
BT_ERR("Dropping L2CAP data: receive buffer overflow -
chan->imtu: %d, skb->len: %d", chan->imtu, skb->len);
//goto drop;
}
* What was the outcome of this action?
This in logs: "Bluetooth: Dropping L2CAP data: receive buffer overflow -
chan->imtu: 672, skb->len: 673" and it finally worked
* What outcome did you expect instead?
I expected it to work, but this is not the proper solution.
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: P1.80
board_vendor: ASRock
board_name: Z370 Extreme4
board_version:
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host
Bridge/DRAM Registers [8086:3ec2] (rev 07)
Subsystem: ASRock Incorporation 8th Gen Core Processor Host Bridge/DRAM
Registers [1849:3ec2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: skl_uncore
Kernel modules: ie31200_edac
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16)
[8086:1901] (rev 07) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family
USB 3.0 xHCI Controller [8086:a2af] (prog-if 30 [XHCI])
Subsystem: ASRock Incorporation 200 Series/Z370 Chipset Family USB 3.0
xHCI Controller [1849:a2af]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR-
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation 200 Series PCH
Thermal Subsystem [8086:a2b1]
Subsystem: ASRock Incorporation 200 Series PCH Thermal Subsystem
[1849:a2b1]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME
HECI [8086:a2ba]
Subsystem: ASRock Incorporation 200 Series PCH CSME HECI [1849:a2ba]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA
controller [AHCI mode] [8086:a282] (prog-if 01 [AHCI 1.0])
Subsystem: ASRock Incorporation 200 Series PCH SATA controller [AHCI
mode] [1849:a282]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF-
Bug#990127: marked as done (mt76x0 crashes repeatedly)
Your message dated with message-id and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #990127, regarding mt76x0 crashes repeatedly 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.) -- 990127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-misc-nonfree Version: 20190114-2 kernel module: mt76x0 Severity: serious Following an update recently, this driver stopped working correctly. I can now only get a working WiFi connection for a few seconds after reboot, or after waiting several minutes, making anything that requires the internet almost impossible. This was working fine until the update. Once the interface is up, the driver crashes almost immediately. It does not matter whether I use NetworkManager or do things manually with /etc/network/interfaces and then ifup. The same trace is seen in the logs and dmesg repeatedly. I have ruled out hardware issues. uname -a : Linux hope 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux # modinfo mt76x0 filename: /lib/modules/4.19.0-16-amd64/kernel/drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0.ko license:GPL firmware: mediatek/mt7610u.bin alias: usb:v0E8Dp7650d*dc*dsc*dp*icFFisc02ipFFin* alias: usb:v0E8Dp7630d*dc*dsc*dp*icFFisc02ipFFin* alias: usb:v2357p0105d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0DF6p0079d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v7392pC711d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v20F4p806Bd*dc*dsc*dp*ic*isc*ip*in* alias: usb:v293Cp5702d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v057Cp8502d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v04BBp0951d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v07B8p7610d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0586p3425d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v2001p3D02d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v2019pAB31d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0DF6p0075d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0B05p17DBd*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0B05p17D1d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v148Fp760Ad*dc*dsc*dp*ic*isc*ip*in* alias: usb:v148Fp761Ad*dc*dsc*dp*ic*isc*ip*in* alias: usb:v7392pB711d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v7392pA711d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v0E8Dp7610d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v13B1p003Ed*dc*dsc*dp*ic*isc*ip*in* alias: usb:v148Fp7610d*dc*dsc*dp*ic*isc*ip*in* depends:mac80211,mt76,cfg80211,usbcore retpoline: Y intree: Y name: mt76x0 vermagic: 4.19.0-16-amd64 SMP mod_unload modversions sig_id: PKCS#7 signer: Debian Secure Boot CA sig_key:4B:6E:F5:AB:CA:66:98:25:17:8E:05:2C:84:66:7C:CB:C0:53:1F:8C sig_hashalgo: sha256 signature: 58:62:E3:A8:7F:B6:04:24:F1:68:8E:F0:B1:AF:0B:34:8A:66:2D:A1: 59:54:49:75:B2:52:7F:FF:5D:6B:34:C5:D6:9F:5E:51:33:C3:57:BE: 38:8C:24:36:D7:C4:BE:1C:2F:62:FC:9C:A1:37:5C:04:17:59:57:0B: 35:A5:6A:9A:2B:1B:3F:D1:E3:78:CD:50:72:8E:8B:2B:3B:FF:DE:2A: FC:8A:F6:A1:BF:FE:2B:52:8D:F8:6D:4D:73:2E:D6:09:5D:4A:EB:11: D4:26:89:78:77:D9:BB:04:E6:C4:9A:5A:35:8E:1A:14:BA:84:D7:BF: 97:AB:0F:5F:A7:3E:D0:DF:DD:E2:75:F1:9E:2C:2A:48:09:AD:FF:D1: 9C:9E:61:45:44:D2:2E:DD:CE:7E:C8:96:D5:F7:A1:82:CA:33:F9:87: 5A:C8:FB:30:2B:36:45:12:2C:21:E4:23:CD:02:C5:69:93:B4:7E:A9: FD:BF:A0:CA:A2:A7:FD:B5:F1:CC:C8:F2:44:A1:23:33:C0:32:3A:B6: 2E:6A:27:B8:C7:86:91:30:4A:E5:AC:14:51:50:B0:89:09:BC:31:EB: E4:F3:27:51:63:10:29:A0:BB:3C:94:21:33:BE:0C:C7:47:56:08:BC: 4F:A2:FF:38:FF:D5:4C:DF:2C:A8:64:94:3D:6E:F3:6D # Relevant extract from dmesg: [ 996.874969] mt76x0 1-5:1.0: Error: send MCU cmd failed:-71 [ 996.875010] mt76x0 1-5:1.0: Error: MCU response pre-completed! [ 996.885414] mt76x0 1-5:1.0: Error: send MCU cmd failed:-71 [ 997.007009] mt76x0 1-5:1.0: Vendor request req:07 off:1798 failed:-71 [ 997.275141] mt76x0 1-5:1.0: Vendor request req:07 off:1718 failed:-71 [ 997.275154] [ cut here ] [ 997.275202] WARNING: CPU: 1 PID: 147 at drivers/net/wireless/mediatek/mt76/mt76x0/mac.c:55 mt76_mac_fill_tx_status.isra.2+0x29e/0x2e0 [mt76x0] [ 997.275203] Modules linked in: arc4 mt76x0 mt76 mac80211 cfg80211 bnep nfnetlink_queue nfnetlink_log bluetooth
Bug#978753: marked as done (usercopy: Kernel memory exposure attempt)
Your message dated with message-id and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #978752, regarding usercopy: Kernel memory exposure attempt 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.) -- 978752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux-image-4.19.0-13-amd64 Version: 4.19.160-2 Severity: critical Justification: breaks the whole system -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.86 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-13-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-13-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-13-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.02+dfsg1-20+deb10u2 pn linux-doc-4.19 Versions of packages linux-image-4.19.0-13-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information Caused system halt with message: usercopy: Kernel memory exposure attempt detected from SLUB object 'mm_struct(770:pm2-root.service)' (offset 272, size 320)! --- End Message --- --- Begin Message --- Hi 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 please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore--- End Message ---
Bug#939431: marked as done (linux-image-5.2.0-2-amd64: failedto reeed)
Your message dated Sat, 02 Apr 2022 02:23:07 -0700 (PDT) with message-id <624815fb.1c69fb81.4d368.4...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #939431, regarding linux-image-5.2.0-2-amd64: failedto reeed 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.) -- 939431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.2.9-2 Severity: normal Tags: upstream 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 *** -- Package-specific info: ** Version: Linux version 5.2.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-2-amd64 root=UUID=1b98e41e-8276-493e-b9ca-6994e7aa1958 ro noacpi reboot=acpi ipv6.disable=1 ** Tainted: POE (12289) * Proprietary module has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Apple Inc. product_name: Macmini4,1 product_version: 1.0 chassis_vendor: Apple Inc. chassis_version: Mac-F2208EC8 bios_vendor: Apple Inc. bios_version: MM41.88Z.0047.B00.1802021546 board_vendor: Apple Inc. board_name: Mac-F2208EC8 board_version: ** Loaded modules: uinput cpufreq_conservative cpufreq_powersave cpufreq_userspace nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core coretemp snd_hwdep kvm_intel snd_pcm_oss kvm snd_mixer_oss snd_pcm snd_timer efi_pstore snd irqbypass sg applesmc input_polldev soundcore efivars pcspkr evdev pcc_cpufreq button acpi_cpufreq nvidia(POE) drm ecryptfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_apple hid_appleir hid_generic usbhid hid sr_mod cdrom sd_mod ohci_pci ahci libahci libata ohci_hcd tg3 ehci_pci libphy ehci_hcd firewire_ohci scsi_mod ptp pps_core firewire_core crc_itu_t usbcore usb_common video ** PCI devices: 00:00.0 Host bridge [0600]: NVIDIA Corporation MCP89 HOST Bridge [10de:0d60] (rev a1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 00:03.3 RAM memory [0500]: NVIDIA Corporation MCP89 Memory Controller [10de:0d69] (rev a1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ohci-pci Kernel modules: ohci_pci 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller [10de:0d9d] (rev a2) (prog-if 20 [EHCI]) Subsystem: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller [10de:cb89] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:06.0 USB controller [0c03]: NVIDIA Corporation MCP89 OHCI USB 1.1 Controller [10de:0d9c] (rev a1) (prog-if 10 [OHCI]) Subsystem: NVIDIA Corporation MCP89 OHCI USB 1.1 Controller [10de:cb89] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ohci-pci Kernel modules: ohci_pci 00:06.1 USB controller [0c03]: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller [10de:0d9d] (rev a2) (prog-if 20 [EHCI]) Subsystem: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller [10de:cb89] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
Bug#978752: marked as done (usercopy: Kernel memory exposure attempt)
Your message dated with message-id and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #978752, regarding usercopy: Kernel memory exposure attempt 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.) -- 978752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.160-2 Severity: critical Justification: breaks the whole system -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.86 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-13-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-13-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-13-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.02+dfsg1-20+deb10u2 pn linux-doc-4.19 Versions of packages linux-image-4.19.0-13-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information --- End Message --- --- Begin Message --- Hi 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 please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore--- End Message ---
Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs
Control; tags -1 + moreinfo On Thu, Mar 04, 2021 at 10:43:23AM +0900, Ryutaroh Matsumoto wrote: > Package: src:linux > Version: 5.10.19-1 > Followup-For: Bug #977647 > Control: retitle -1 5.10.19 Debian kernel has mysterious tpm error in dmesg > Control: severity -1 minor > > Dear Maintainer, > > The boot failure problem originally reported as #977647 somehow gets fixed > in Debian kernel 5.10.19. > > The severity seems now minor. > It has still the mysterious dmesg error on tpm as follows. > The full dmesg log is attached. Do you still have the issues? Otherwise let's close this bug. Regards, Salvatore
Processed: closing 914505
Processing commands for cont...@bugs.debian.org: > close 914505 Bug #914505 [src:linux] linux: reference to netfilter chain not removed on rule replacement, subsequently system hangs Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 914505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
