Hardware issue or crostini bug

890 views
Skip to first unread message

Joseph Callen

unread,
Dec 29, 2022, 10:24:57 AM12/29/22
to ChromiumOS Discussion
Hi! 
I am new to ChromeOS and Crostini (IdeaPad Duet 5) so bear with me. 

I enabled #crostini-multi-container so that I could run a fedora 37 as well as debian.
That worked perfectly fine last night and coming in this morning I get:

Launching vmshell failed: Error starting crostini for terminal: 74 (START_LXD_FAILED_SIGNAL)

crosh> vsh termina
(termina) chronos@localhost ~ $ lxc list
Error: Get "http://unix.socket/1.0": dial unix /mnt/stateful/lxd/unix.socket: connect: connection refused


There are a number of kernel panics on the termina vm

Dec 29 09:19:10 <13> VM(32): [ 1.554849] ------------[ cut here ]------------ Dec 29 09:19:10 <13> VM(32): [ 1.557832] WARNING: CPU: 6 PID: 1 at include/linux/msi.h:219 __pci_enable_msix_range+0x340/0x5b0 Dec 29 09:19:10 <13> VM(32): [ 1.564151] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 5.10.147-20158-g0a75306e5639 #1 Dec 29 09:19:10 <13> VM(32): [ 1.569130] Hardware name: linux,dummy-virt (DT) Dec 29 09:19:10 <13> VM(32): [ 1.571816] pstate: 60c00005 (nZCv daif +PAN +UAO -TCO BTYPE=--)

Dec 29 09:19:10 <13> VM(32): [ 1.701978] ------------[ cut here ]------------ Dec 29 09:19:10 <13> VM(32): [ 1.704415] WARNING: CPU: 6 PID: 1 at include/linux/msi.h:225 free_msi_irqs+0xe4/0x174 Dec 29 09:19:10 <13> VM(32): [ 1.708143] CPU: 6 PID: 1 Comm: swapper/0 Tainted: G W 5.10.147-20158-g0a75306e5639 #1 Dec 29 09:19:10 <13> VM(32): [ 1.712470] Hardware name: linux,dummy-virt (DT)

And a very unhappy lxd_helper

Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: SIGILL: illegal instruction#012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: PC=0xf05d15e m=0 sigcode=1#012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: signal arrived during cgo execution#012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: instruction bytes: 0xff 0xeb 0x28 0x0 0x9d 0xe5 0x2 0x0 0x10 0xe3 0x3 0x0 0x0 0xa 0x34 0x0#012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: #012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: goroutine 1 [syscall]:#012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: runtime.cgocall(0xfe7f988, 0x127f38bc)#012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: #011/usr/lib/go/armv7a-cros-linux-gnueabihf/src/runtime/cgocall.go:158 +0x60 fp=0x127f38a4 sp=0x127f388c pc=0xf0025d8#012 Dec 29 09:19:19 <14> VM(32): tremplin[204]: 2022/12/29 14:19:19 lxd_helper.go:141: lxd stderr: github.com/canonical/go-dqlite/internal/bindings._Cfunc_dqlite_node_create(0x1, 0x12368f60, 0x12344518, 0x12842bdc)#012

I submitted a ticket to Lenovo but I am kinda questioning how far I will get there.
Thinking maybe I should just return this device.

Any advice or assistance would be appreciated
Thanks!
Joe


system_logs_20221229-150718.txt.zip

Joseph Callen

unread,
Dec 29, 2022, 1:17:06 PM12/29/22
to ChromiumOS Discussion, Joseph Callen
Additional information:
- Kernel panics are a red herring. Seems to happen even when just using debian (penguin)

- I am able to reproduce:
1.) remove linux environment
2.) poweroff, poweron
3.) create linux environment
4.) create fedora container via UI
5.) install deps:
Changing steps, no useradd, the user is already there
The user needs to be added to wheel, and visudo to remove password
install ssd-client, there are pam-sss errors
Use these tools since they are more recent: https://copr.fedorainfracloud.org/coprs/leo/cros-guest-tools/

6.) shutdown all containers and applications
7.) poweroff
8.) start penguin container, lxd does not start

dragon788

unread,
Dec 29, 2022, 8:30:45 PM12/29/22
to jcpow...@gmail.com, ChromiumOS Discussion
There is an issue with systemd >244.0 not pulling an IPv4 address if /sys is read write due to udev trying to start and blowing up.

This happens on Arch as well. You can write an override file to prevent the issue. There's a known issue in the lxd/lxc tracker.

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss
---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-dis...@chromium.org.

David Munro

unread,
Dec 29, 2022, 8:36:57 PM12/29/22
to jcpow...@gmail.com, James Ye, ChromiumOS Discussion, clumptini
+James Ye , CC clumptini.

dqlite SIGILL, IdeaPad Duet 5 has a snapdragon, so I guess this is yet another LXD+ARM issue.

Which OS version? Can you please file feedback and include something distinctive in the description so we can easily find it?

Thanks,
Dave.

James Ye

unread,
Dec 29, 2022, 10:22:35 PM12/29/22
to ChromiumOS Discussion, David Munro, ChromiumOS Discussion, clumptini, jcpow...@gmail.com, James Ye
This has exactly the same symptoms as https://issuetracker.google.com/issues/256946320 which has been fixed in ChromeOS 109. It's not a hardware issue, but a LXD crash due to an incompatibility with the ARM architecture in a library.

109 is currently in beta, but should arrive in stable next month.

Cheers,
  James

Joseph Callen

unread,
Dec 30, 2022, 7:26:53 AM12/30/22
to ChromiumOS Discussion, jam...@google.com, david...@google.com, ChromiumOS Discussion, clumptini, Joseph Callen
Thanks all!

I can confirm the issue has been resolved with: Version 109.0.5414.41 (Official Build) beta (32-bit)
Reply all
Reply to author
Forward
0 new messages