Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #86791 > unrolled thread

Bug#1102422: tpm tpm0: tpm_try_transmit: send(): error -62

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1102422: tpm tpm0: tpm_try_transmit: send(): error -62 Jiann-Ming Su <sujiannming@gmail.com> - 2025-04-09 04:10 +0200
    Processed: Re: Bug#1102422: tpm tpm0: tpm_try_transmit: send():  error -62 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-04-10 10:20 +0200
    Bug#1102422: tpm tpm0: tpm_try_transmit: send(): error -62 Emanuele Rocca <ema@debian.org> - 2025-04-10 10:20 +0200
    Bug#1102422: tpm tpm0: tpm_try_transmit: send(): error -62 Emanuele Rocca <ema@debian.org> - 2025-04-11 11:50 +0200
    Bug#1102422: Closing this bug (BTS maintenance for src:linux bugs) carnil@debian.org - 2025-09-13 23:00 +0200

#86791 — Bug#1102422: tpm tpm0: tpm_try_transmit: send(): error -62

[Multipart message — attachments visible in raw view] — view raw

Package: linux-image-6.1.0-32-amd64
Version: 6.1.129-1

Sudden 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

[toc] | [next] | [standalone]

#86806 — Processed: Re: Bug#1102422: tpm tpm0: tpm_try_transmit: send(): error -62

Processing control commands:

> tag -1 moreinfo
Bug #1102422 [src:linux] tpm tpm0: tpm_try_transmit: send(): error -62
Added tag(s) moreinfo.

-- 
1102422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102422
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#86807

Control: tag -1 moreinfo

Hi Jiann-Ming,

On 2025-04-08 09:57, Jiann-Ming Su wrote:
> Package: linux-image-6.1.0-32-amd64
> Version: 6.1.129-1
> 
> Sudden 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",

We need some more information in order to debug this problem.

- Did any previous kernel version work fine for you?
- Does the issue arise after performing some specific tpm operations?
- Have you by any chance upgraded/downgraded your coreboot firmware?
- Please share the full output from dmesg.
- Please try a more recent kernel from bookworm-backports to see if the
  problem can still be reproduced. See https://backports.debian.org/Instructions/

Thanks,
  Emanuele

[toc] | [prev] | [next] | [standalone]

#86829

Hi,

On 2025-04-10 08:30, Jiann-Ming Su wrote:
> I did not see any such message from linux-image-6.1.0-31.

Can the issue be reliably reproduced? Is it sufficient to boot into
linux-image-6.1.0-32-amd64 to see the errors, and rebooting into
linux-image-6.1.0-31-amd64 shows no errors?

> I don't think this particular system is doing any tpm operations.
> Please see attached kern.log.xz.

Very useful, thank you. I have a similar Chromebook and cannot reproduce
the isse. My system also uses the Chromebox firmware (though a more
recent version, see below). Including some dmesg output here for
reference:

[    0.000000] efi: EFI v2.70 by EDK II
[    0.000000] efi: SMBIOS=0x1ffd6000 SMBIOS 3.0=0x1ffd4000 ACPI=0x1fffe000 ACPI 2.0=0x1fffe014 MEMATTR=0x1ec35418 MOKvar=0x1ff9d000 
[...]
[    0.000000] DMI: GOOGLE Celes/Celes, BIOS MrChromebox-4.19.1 01/29/2023
[...]
[    1.646156] tpm_tis 00:07: 1.2 TPM (device-id 0xB, rev-id 16)

The tpm_tis output is exactly the same as yours.

It seems that on your system the errors show up some minutes after boot,
not immediately. From your dmesg output:

[   12.732250] tun: Universal TUN/TAP device driver, 1.6
[  524.061466] tpm tpm0: tpm_try_transmit: send(): error -62
[... log flood follows ...]

This makes me wonder if perhaps some of the applications you're running
use the tpm in some way that triggers the issue, and maybe I'm not
running those? Which destkop environment, if any, are you using?
Could you share the output of `sudo journalctl -b`?

Also, could you try installing the tpm-tools package and running the
following (possibly before the tpm_try_transmit errors begin)?

$ /usr/sbin/tpm_version

On my system I get:

  TPM 1.2 Version Info:
  Chip Version:        1.2.4.34
  Spec Level:          2
  Errata Revision:     3
  TPM Vendor ID:       IFX
  Vendor Specific data: 042203f2 0274706d 3338ffff ff
  TPM Version:         01010000
  Manufacturer Info:   49465800

Finally, I see that you're booting your kernel with pci=noaer. Any
specific reasons for that?

Thanks,
  Emanuele

[toc] | [prev] | [next] | [standalone]

#89241 — Bug#1102422: Closing this bug (BTS maintenance for src:linux bugs)

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web