Jun 27 13:56:27 dragon kernel: Workqueue: events_long ucsi_init_work [typec_ucsi] Jun 27 13:56:27 dragon kernel: RIP: 0010:ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] Jun 27 13:56:27 dragon kernel: Code: 89 e5 41 56 49 89 ce 41 55 49 89 d5 41 54 53 89 f3 e8 83 2b fe ff 4c 89 f2 4c 89 ee 89 df 48 03 78 10 49 89 c4 e8 1f 34 c7 d1 <49> 8b 45 00 4c 89 e7 be 01 00 00 00 49 89 44 24 50 e8 c9 fc ff ff Jun 27 13:56:27 dragon kernel: RSP: 0018:ffffb347c0683d78 EFLAGS: 00010282 Jun 27 13:56:27 dragon kernel: RAX: ffffb347c0185002 RBX: 0000000000000002 RCX: 0000000000000000 Jun 27 13:56:27 dragon kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb347c0185002 Jun 27 13:56:27 dragon kernel: RBP: ffffb347c0683d98 R08: 0000000000000000 R09: 0000000000000000 Jun 27 13:56:27 dragon kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff9c370214a7a8 Jun 27 13:56:27 dragon kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff9c37010c1db8 Jun 27 13:56:27 dragon kernel: FS: 0000000000000000(0000) GS:ffff9c3e8d280000(0000) knlGS:0000000000000000 Jun 27 13:56:27 dragon kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 27 13:56:27 dragon kernel: CR2: 0000000000000000 CR3: 000000052e83a000 CR4: 0000000000750ee0 Jun 27 13:56:27 dragon kernel: PKRU: 55555554 Jun 27 13:56:27 dragon kernel: Call Trace: Jun 27 13:56:27 dragon kernel: <TASK> Jun 27 13:56:27 dragon kernel: ? show_regs+0x6d/0x80 Jun 27 13:56:27 dragon kernel: ? __die+0x24/0x80 Jun 27 13:56:27 dragon kernel: ? page_fault_oops+0x99/0x1b0 Jun 27 13:56:27 dragon kernel: ? do_user_addr_fault+0x335/0x720 Jun 27 13:56:27 dragon kernel: ? acpi_evaluate_object+0x1e7/0x470 Jun 27 13:56:27 dragon kernel: ? exc_page_fault+0x80/0x1b0 Jun 27 13:56:27 dragon kernel: ? asm_exc_page_fault+0x27/0x30 Jun 27 13:56:27 dragon kernel: ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] Jun 27 13:56:27 dragon kernel: ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] Jun 27 13:56:27 dragon kernel: ucsi_exec_command+0xdf/0x100 [typec_ucsi] Jun 27 13:56:27 dragon kernel: ucsi_send_command+0x4b/0xf0 [typec_ucsi] Jun 27 13:56:27 dragon kernel: ucsi_init+0x33/0x270 [typec_ucsi] Jun 27 13:56:27 dragon kernel: ucsi_init_work+0x18/0x80 [typec_ucsi] Jun 27 13:56:27 dragon kernel: process_one_work+0x222/0x430 Jun 27 13:56:27 dragon kernel: worker_thread+0x50/0x3f0 Jun 27 13:56:27 dragon kernel: ? __pfx_worker_thread+0x10/0x10 Jun 27 13:56:27 dragon kernel: kthread+0xe6/0x110 Jun 27 13:56:27 dragon kernel: ? __pfx_kthread+0x10/0x10 Jun 27 13:56:27 dragon kernel: ret_from_fork+0x29/0x50 Jun 27 13:56:27 dragon kernel: </TASK> Jun 27 13:56:27 dragon kernel: Modules linked in: nvme ucsi_acpi atlantic crc32_pclmul thunderbolt nvme_core spi_intel_pci typec_ucsi i2c_i801 ahci macsec spi_intel i2c_smbus nvme_common xhci_pci typec libahci xhci_pci_renesas video wmi pinctrl_alderlake Jun 27 13:56:27 dragon kernel: CR2: 0000000000000000 Jun 27 13:56:27 dragon kernel: ---[ end trace 0000000000000000 ]---
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025120 Title: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
