Not at all! I am glad I could contribute to the Cause :)This is my first kernel BUG report,Many thx for your report!
No, I only started building and testing kernels at 6.0.0-r3so please bear with me for a while
if I'm doing something wrong or otherwise awkward.
I've noticed it in the 6.0.0-rc3 kernel
So rc2 was working fine for you?
I see, but my knowledge of the kernel source is insufficient to pinpoint theand following patches to see if it will be fixed by other testers.These?
I've read the bug report instructions, so I hope this will be useful.
https://docs.kernel.org/admin-guide/reporting-issues.html
Just wondering, as then I maybe should make it clearer that sending a
report to just the mainling list is a bad idea, as nearly nobody will
see this.
Right now I am testing the 6.0.0-060000 Ubuntu mainline officialHowever, now we are at rc7, so keeping it for myself when the kernel isHmm. I have no idea at all what kernel change might cause this and hence
near production state might be an offence to good conscience.
In particular, it is the problem with Firefox 104.x and 105.x, which has
tabs crashing, and later it refuses to restart.
Exactly the same config works with the other Linux kernels tried (5.15.x
and 5.19.x) on the Ubuntu 22.04 system.
Firefox is a snap. The bug persisted with apparmor ON and OFF.
The kernel is compiled with KMEMLEAK and KASAN options, but otherwise it
is the default config file for Ubuntu's rc3 release candidate.
don't know whom to ask to look into this. What really would help
tremendously: if someone could bisect the problem with a vanilla kernel.
Here is a rough guide (hopefully I sooner or later find time to write
one that is more user-friedly):
https://docs.kernel.org/admin-guide/bug-bisect.html
Here is the syslog of the startup.Anyway, to be sure below issue doesn't fall through the cracks
Please find dmesg output. It is rather similar to the dmesg output of
production kernels.
/var/log/syslog:
Sep 27 18:43:20 IdeaPad-3 firefox_firefox.desktop[5811]: message
repeated 11 times: [ /snap/firefox/1883/usr/lib/firefox/firefox:
/snap/firefox/1883/usr/lib/firefox/firefox: no version information
available (required by
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so)]
Sep 27 18:43:20 IdeaPad-3 firefox_firefox.desktop[5811]:
/snap/firefox/1883/usr/lib/firefox/firefox:
/lib/x86_64-linux-gnu/libpthread.so.0: version `' not found (required by
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so)
Sep 27 18:43:20 IdeaPad-3 firefox_firefox.desktop[5811]:
/snap/firefox/1883/usr/lib/firefox/firefox:
/lib/x86_64-linux-gnu/librt.so.1: version `' not found (required by
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so)
Sep 27 18:43:20 IdeaPad-3 firefox_firefox.desktop[5811]:
/snap/firefox/1883/usr/lib/firefox/firefox:
/lib/x86_64-linux-gnu/libdl.so.2: version `' not found (required by
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so)
Sep 27 18:43:27 IdeaPad-3 firefox_firefox.desktop[2686]: Missing chrome
or resource URL: resource://gre/modules/UpdateListener.sys.mjs
Sep 27 18:43:31 IdeaPad-3 firefox_firefox.desktop[2921]:
/snap/firefox/1883/usr/lib/firefox/firefox: symbol lookup error:
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so: undefined symbol: ,
version
Sep 27 18:43:33 IdeaPad-3 systemd[1791]:
snap.firefox.firefox.8b8574d2-116e-411a-9bba-c145e8cc0aa2.scope:
Consumed 10min 18.279s CPU time.
Sep 27 18:44:49 IdeaPad-3 snapd[818]: storehelpers.go:748: cannot
refresh: snap has no updates available: "bare", "canonical-livepatch",
"core", "core18", "core20", "firefox", "gnome-3-34-1804",
"gnome-3-38-2004", "gtk-common-themes", "slack", "snap-store", "snapd",
"zoom-client"
Sep 27 19:04:59 IdeaPad-3 systemd[1791]: Started
snap.firefox.firefox.d0067088-10d8-459d-a40d-fed0c95b1481.scope.
Sep 27 19:05:04 IdeaPad-3 systemd[1791]:
snap.firefox.firefox.d0067088-10d8-459d-a40d-fed0c95b1481.scope:
Consumed 4.239s CPU time.
Sep 27 19:05:41 IdeaPad-3 systemd[1791]: Started
snap.firefox.firefox.c93d07ee-bee6-492d-aa89-2e27db5d5ae7.scope.
Sep 27 19:05:42 IdeaPad-3 systemd[1791]:
snap.firefox.firefox.c93d07ee-bee6-492d-aa89-2e27db5d5ae7.scope:
Consumed 1.256s CPU time.
Sep 27 19:06:39 IdeaPad-3 systemd[1791]: Started
snap.firefox.firefox.b4550475-1ff8-41ee-9a39-305174eeaa44.scope.
Sep 27 19:06:41 IdeaPad-3 systemd[1791]:
snap.firefox.firefox.b4550475-1ff8-41ee-9a39-305174eeaa44.scope:
Consumed 1.231s CPU time.
Sep 27 19:06:55 IdeaPad-3 systemd[1791]: Started
snap.firefox.firefox.c42cb676-a7a7-49e6-8685-610bd9c1de81.scope.
$ sudo dmesg -l err
[ 1.638759] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0], AE_NOT_FOUND (20220331/dswload2-162)
[ 1.638854] ACPI Error: AE_NOT_FOUND, During name lookup/catalog
(20220331/psobject-220)
[ 2.175611] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PC00.DGPV], AE_NOT_FOUND (20220331/psargs-330)
[ 2.175731] ACPI Error: Aborting method \_SB.PC00.PEG0.PCRP._ON due
to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 5.519037] integrity: Problem loading X.509 certificate -65
[ 10.010679] mtd device must be supplied (device name is empty)
[ 12.220863] i801_smbus 0000:00:1f.4: Transaction timeout
[ 12.222934] i801_smbus 0000:00:1f.4: Failed terminating the transaction
[ 12.223023] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[ 13.092867] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 3-.... } 6 jiffies s: 61 root: 0x8/.
[ 13.092878] rcu: blocking rcu_node structures (internal RCU debug):
[ 13.991053] mtd device must be supplied (device name is empty)
[ 15.315968] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 18.018388] ACPI BIOS Error (bug): Could not resolve symbol
[\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330)
[ 18.018857] ACPI Error: Aborting method \_SB.IETM._OSC due to
previous error (AE_NOT_FOUND) (20220331/psparse-529)
Please find attached the config file for the kernel build. Source is rc7
"master" clean after rc7 rlse.
Here is the demonstration of bug with apparmor ON and OFF:
$ sudo systemctl stop apparmor
$ firefox &
[1] 7825
$ date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: symbol lookup error: date: undefined symbol: , version GLIBC_2.2.5
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: symbol lookup error: chmod: undefined symbol: , version
xdg-user-dirs-update: error while loading shared libraries:
xdg-user-dirs-update: unsupported version 0 of Verneed record
rm: rm: no version information available (required by rm)
rm: rm: no version information available (required by rm)
rm: rm: no version information available (required by rm)
rm: rm: no version information available (required by rm)
rm: rm: no version information available (required by rm)
rm: symbol lookup error: rm: undefined symbol: , version GLIBC_2.2.5
XPCOMGlueLoad error for file
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so:
/lib/x86_64-linux-gnu/libpthread.so.0: version `' not found (required by
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so)
Couldn't load XPCOM.
[1]+ Exit 255 firefox
$
$ sudo systemctl start apparmor
$ firefox &
[1] 7996
$ date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: symbol lookup error: date: undefined symbol: , version GLIBC_2.2.5
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: chmod: no version information available (required by chmod)
chmod: symbol lookup error: chmod: undefined symbol: , version
xdg-user-dirs-update: error while loading shared libraries:
xdg-user-dirs-update: unsupported version 0 of Verneed record
XPCOMGlueLoad error for file
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so:
/lib/x86_64-linux-gnu/libpthread.so.0: version `' not found (required by
/snap/firefox/1883/usr/lib/firefox/libmozsandbox.so)
Couldn't load XPCOM.
All other apps work OK AFAICS, however I suspected a kernel bug since it
only shows only in RC kernels
(even the Ubuntu's own 6.0.0-rc3 mainline build).
Hope this helps someone. I could provide more info at request.
Kind regards,
Mirsad
[config file removed when quoting]
unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking
bot:
#regzbot ^introduced v5.19..v6.0-rc3
#regzbot title Firefox snap fails to run ("undefined symbol" and
"unsupported version 0 of Verneed record" error messages)
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/
Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replies to), as explained for
in the Linux kernel's documentation; above webpage explains why this is
important for tracked regressions.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.