Your message dated Sat, 13 Sep 2025 22:53:29 +0200 (CEST) with message-id <[🔎] 20250913205329.4B2C0BE2DE0@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #1102422, regarding tpm tpm0: tpm_try_transmit: send(): error -62 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 owner@bugs.debian.org immediately.) -- 1102422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102422 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: tpm tpm0: tpm_try_transmit: send(): error -62
- From: Jiann-Ming Su <sujiannming@gmail.com>
- Date: Tue, 8 Apr 2025 21:57:06 -0400
- Message-id: <CADjNMDYnT8v=GHN3vnxd-HojCRZ6Mz9Q8HA-nthe+dTPsoh4aQ@mail.gmail.com>
Package: linux-image-6.1.0-32-amd64Version: 6.1.129-1Sudden incessant tpm messages in dmesg on Asus Chromebox 4:tpm tpm0: tpm_try_transmit: send(): error -62"architecture": "x86_64",--
"bios_date": "08/22/2019",
"bios_vendor": "coreboot",
"bios_version": "MrChromebox-4.10",
"board_asset_tag": "NA",
"board_name": "Panther",
"board_serial": "123456789",
"board_vendor": "GOOGLE",
"board_version": "1.0",
"chassis_asset_tag": "NA",
"chassis_serial": "NA",
"chassis_vendor": "GOOGLE",
"chassis_version": "NA",Jiann-Ming Su
--- End Message ---
--- Begin Message ---
- To: 1102422-done@bugs.debian.org
- Cc: 1102422-submitter@bugs.debian.org
- Subject: Closing this bug (BTS maintenance for src:linux bugs)
- From: carnil@debian.org
- Date: Sat, 13 Sep 2025 22:53:29 +0200 (CEST)
- Message-id: <[🔎] 20250913205329.4B2C0BE2DE0@eldamar.lan>
Hi This bug was filed for a (very) old kernel or the bug is old itself without resolution. Maybe it was for a feature enablement which nobody acted on. We are sorry we were not able to timely deal with this issue. There are many open bugs for the src:linux package and thus we are closing older bugs where it's unclear if they still occur in newer versions and are still relevant to the reporter. For an overview see: https://bugs.debian.org/src:linux . If you can reproduce your issue with - the current version in unstable/testing - the latest kernel from backports or, if it was a feature addition/wishlist and still consider it relevant, then: Please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Please try to provide as much fresh details including kernel logs where relevant. In particular were an issue is coupled with specific hardware we might ask you to do additional debugging on your side as the owner of the hardware. Regards, Salvatore
--- End Message ---