[Bug 1969529] Re: snapd slow to seed firefox on Pi 400
** Also affects: snapd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Kinetic) Importance: High Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd slow to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd slow to seed firefox on Pi 400
Hi Dave, I did not see any I/O errors from the kernel, but in your first boot log (https://errors.ubuntu.com/oops/fa9433d0-c022-11ec-8ae0-fa163e993415) there are plenty of errors which might be related to missing files: === Apr 19 21:46:38 localhost.localdomain pulseaudio[841]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. ... Apr 19 21:46:42 localhost.localdomain udisksd[985]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory ... Apr 19 21:53:20 miss-piggy pipewire-media-session[840]: ms.core: error id:0 seq:701 res:-32 (Broken pipe): connection error Apr 19 21:53:21 miss-piggy accounts-daemon[934]: failed to check if user 'oem' in cache dir is present on system: No such file or directory Apr 19 21:53:21 miss-piggy tracker-miner-f[970]: Could not delete '.meta.isrunning': No such file or directory ... Apr 19 21:53:31 miss-piggy pulseaudio[34513]: Failed to open cookie file '/var/lib/gdm3/.config/pulse/cookie': No such file or directory === plus plenty of driver initialization errors; but on the other hand, it may be that all of that is normal -- I just wanted to make sure that we don't have to deal with a corrupted image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd slow to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd slow to seed firefox on Pi 400
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd slow to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd slow to seed firefox on Pi 400
@mardy I would be very surprised if SD card corruption was the issue here. The cards I'm using for test have had no issues booting any of the images so far (and typically whenever I've seen SD corruption before it's usually pretty obvious from boot time). Which I/O errors in the logs have caught your attention, particularly? Some are "expected" unfortunately. For example: Apr 20 12:23:25 localhost.localdomain systemd-modules-load[318]: Failed to find module 'ipmi-devintf' This is because that modules is not included in the stripped down linux- modules package from linux-raspi. Apr 20 12:23:29 localhost.localdomain kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.raspberrypi,400.bin failed with error -2 This one is because the wifi firmware blob first tries to load a device- specific configuration (the "raspberrypi,400" bit in the filename) and falls back to a generic configuration if no device-specific one is found (unfortunately it falls back rather noisily!). Apr 20 12:25:02 localhost.localdomain pulseaudio[832]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform- fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. I forget the reason for this one, but it's another of "expected" errors we see on the Pi (but audio still works happily so cleaning the false report up hasn't been a high priority). Anyway, I'll try another replication later today and see if I can gather any more info. Thanks for you attention! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd slow to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd slow to seed firefox on Pi 400
Changing the title to "slow" instead of "fails" as it appears this always resolves in practice, but the length of time to initialize is certainly a sub-optimal user experience. ** Summary changed: - snapd failing to seed firefox on Pi 400 + snapd slow to seed firefox on Pi 400 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd slow to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
