Processed: Re: Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

2022-04-02 Thread Debian Bug Tracking System
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

2022-04-02 Thread Ryutaroh Matsumoto
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#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

2022-04-02 Thread Salvatore Bonaccorso
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



Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

2021-03-03 Thread Ryutaroh Matsumoto
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.

[7.077378] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x0, rev-id 78)
[7.082612] [ cut here ]
[7.082741] proc_thermal :00:04.0: enabling device ( -> 0002)
[7.085668] TPM returned invalid status
[7.085692] WARNING: CPU: 10 PID: 372 at drivers/char/tpm/tpm_tis_core.c:249 
tpm_tis_status+0x86/0xa0 [tpm_tis_core]
[7.091064] intel_rapl_common: Found RAPL domain package
[7.093429] Panasonic Laptop Support: probe of MAT0019:00 failed with error 
-5
[7.093991] Modules linked in: processor_thermal_device(+) ucsi_acpi(+) 
tpm_tis(+) intel_rapl_common typec_ucsi kfifo_buf tpm_tis_core 
intel_soc_dts_iosf intel_pch_thermal typec rfkill pcc_cpufreq(-) industrialio 
int3403_thermal(+) tpm int340x_thermal_zone evdev rng_core int3406_thermal 
panasonic_laptop intel_hid sparse_keymap int3400_thermal intel_pmc_core 
acpi_pad acpi_thermal_rel ac msr fuse configfs efivarfs ip_tables x_tables 
autofs4 btrfs xor raid6_pq libcrc32c hid_rmi rmi_core sr_mod cdrom hid_generic 
i915 i2c_algo_bit drm_kms_helper ahci nvme cec libahci xhci_pci xhci_hcd 
sdhci_pci nvme_core e1000e cqhci
[7.096714] intel_rapl_common: Found RAPL domain dram
[7.099285]  libata i2c_i801 drm t10_pi sdhci thunderbolt ptp usbcore 
crc_t10dif crc32_pclmul scsi_mod mmc_core i2c_hid crc32c_intel intel_lpss_pci 
i2c_smbus pps_core crct10dif_generic hid intel_lpss crct10dif_pclmul 
crct10dif_common usb_common idma64 wmi battery button fan video
[7.115229] CPU: 10 PID: 372 Comm: systemd-udevd Not tainted 5.10.0-4-amd64 
#1 Debian 5.10.19-1
[7.115230] Hardware name: Panasonic Corporation CFSV9-2/CFSV9-2L, BIOS 
V2.00L12 04/20/2020
[7.115236] RIP: 0010:tpm_tis_status+0x86/0xa0 [tpm_tis_core]
[7.115239] Code: 00 75 30 48 83 c4 18 c3 31 c0 80 3d e3 48 00 00 00 75 e0 
48 c7 c7 4c 03 ce c0 88 44 24 07 c6 05 cf 48 00 00 01 e8 9a 77 59 ca <0f> 0b 0f 
b6 44 24 07 eb c0 e8 ac ef 5c ca 66 66 2e 0f 1f 84 00 00
[7.115240] RSP: 0018:b0900064f9b0 EFLAGS: 00010282
[7.115242] RAX:  RBX: 8b2d02a72000 RCX: 8b3064498a08
[7.115243] RDX: ffd8 RSI: 0027 RDI: 8b3064498a00
[7.115244] RBP: 8b2d02a72000 R08: 8c05b320 R09: 0001
[7.115245] R10: 8c05b348 R11: 0001 R12: 8b2d18408918
[7.115246] R13: 8b2d02de1000 R14:  R15: b0900064fa82
[7.115247] FS:  7ff671d628c0() GS:8b306448() 
knlGS:
[7.115248] CS:  0010 DS:  ES:  CR0: 80050033
[7.115249] CR2: 7fbf241f8260 CR3: 000102144005 CR4: 003706e0
[7.115250] Call Trace:
[7.115257]  tpm_tis_send_data+0x3f/0x250 [tpm_tis_core]
[7.115262]  ? irq_domain_hierarchical_is_msi_remap+0x20/0x20
[7.115265]  tpm_tis_send_main+0x2e/0xf0 [tpm_tis_core]
[7.115271]  tpm_transmit+0xd8/0x3d0 [tpm]
[7.115275]  tpm_transmit_cmd+0x25/0x90 [tpm]
[7.115282]  tpm2_get_tpm_pt+0xe8/0x150 [tpm]
[7.115286]  tpm_tis_probe_irq_single+0x179/0x1f4 [tpm_tis_core]
[7.115289]  tpm_tis_core_init.cold+0x243/0x526 [tpm_tis_core]
[7.115294]  tpm_tis_plat_probe+0xd8/0xf6 [tpm_tis]
[7.115300]  platform_drv_probe+0x35/0x80
[7.115303]  really_probe+0xf2/0x440
[7.115306]  driver_probe_device+0xe1/0x150
[7.115309]  device_driver_attach+0xa1/0xb0
[7.115311]  __driver_attach+0x8a/0x150
[7.115314]  ? device_driver_attach+0xb0/0xb0
[7.115316]  ? device_driver_attach+0xb0/0xb0
[7.115318]  bus_for_each_dev+0x78/0xc0
[7.115321]  bus_add_driver+0x12b/0x1e0
[7.115323]  driver_register+0x8b/0xe0
[7.115325]  ? 0xc0d04000
[7.115330]  init_tis+0x8d/0x1000 [tpm_tis]
[7.198814]  do_one_initcall+0x44/0x1d0
[7.198818]  ? do_init_module+0x23/0x260
[7.198820]  ? kmem_cache_alloc_trace+0xf5/0x200
[7.198822]  do_init_module+0x5c/0x260
[7.198824]  __do_sys_finit_module+0xb1/0x110
[7.198827]  do_syscall_64+0x33/0x80
[7.198830]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[7.198832] RIP: 0033:0x7ff67221b9b9
[7.198834] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d a7 54 0c 00 f7 d8 64 89 01 48
[7.198835] RSP: 002b:7ffe3ba628b8 EFLAGS: 0246 ORIG_RAX: 
0139
[7.198836] RAX: ffda RBX: 55ee81379020 RCX: 7ff67221b9b9
[7.198837] RDX:  RSI: 7ff6723a6e2d RDI: 0011
[7.198838] RBP: 

Processed: Re: Bug#977647: 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs

2020-12-31 Thread Debian Bug Tracking System
Processing control commands:

> retitle 977647 5.10.4 Debian kernel does not boot on amd64 with btrfs rootfs
Bug #977647 [src:linux] 5.10 boot hang on Panasonic CFSV9-2
Changed Bug title to '5.10.4 Debian kernel does not boot on amd64 with btrfs 
rootfs' from '5.10 boot hang on Panasonic CFSV9-2'.
> reassign 977647 linux-image-5.10.0-1-amd64 5.10.4-1
Bug #977647 [src:linux] 5.10.4 Debian kernel does not boot on amd64 with btrfs 
rootfs
Bug reassigned from package 'src:linux' to 'linux-image-5.10.0-1-amd64'.
No longer marked as found in versions linux/5.10.2-1~exp1 and 
linux/5.10.1-1~exp1.
Ignoring request to alter fixed versions of bug #977647 to the same values 
previously set
Bug #977647 [linux-image-5.10.0-1-amd64] 5.10.4 Debian kernel does not boot on 
amd64 with btrfs rootfs
Marked as found in versions linux-signed-amd64/5.10.4+1.

-- 
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

2020-12-31 Thread Ryutaroh Matsumoto
Control: retitle 977647 5.10.4 Debian kernel does not boot on amd64 with btrfs 
rootfs
Control: reassign 977647 linux-image-5.10.0-1-amd64 5.10.4-1

I installed (signed) linux-image-5.10.0-1-amd64 5.10.4-1 on my laptop 
incompatible
with Linux 5.10.2. It still fails to boot.

On the other hand, I re-confirm that
linux-image-5.9.0-5-amd64 5.9.15-1 boots well and there seems no problem with 
it...

Best regards, Ryutaroh Matsumoto