Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #79775 > unrolled thread
| Started by | AlMa <AlMa0@ro.ru> |
|---|---|
| First post | 2023-07-26 22:20 +0200 |
| Last post | 2025-05-01 15:00 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.kernel
Bug#1042237: upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” AlMa <AlMa0@ro.ru> - 2023-07-26 22:20 +0200
Processed: upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-07-26 22:20 +0200
Bug#1003965: Processed: upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” "Al Ma" <alma0@ro.ru> - 2023-07-27 19:40 +0200
Bug#1042237: marked as done (upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name”) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-05-01 15:00 +0200
| From | AlMa <AlMa0@ro.ru> |
|---|---|
| Date | 2023-07-26 22:20 +0200 |
| Subject | Bug#1042237: upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” |
| Message-ID | <GVT9t-2YQ2-109@gated-at.bofh.it> |
Package: linux-image-6.1.0-10-amd64
Version: 6.1.38-1
Severity: important
Control: affects -1 grub2-common os-prober grub-common
I upgraded the kernel linux-image-6.1.0-10-amd64 in Debian stable from
its prior version 6.1.37-1 to its current version 6.1.38-1 on two
different machines:
• A stationary tower with ASUS WS C422 PRO/SE with Intel Intel® Xeon®
W-2235 CPU @ 3.80GHz,
• A laptop Lenovo T14s 20T1S8EJ00 with Intel® Core™ i7-10610U CPU @ 1.80GHz.
Each time I got error messages. I have not saved the error messages from
the ASUS computer in question (and on another, very similar ASUS
computer with the same motherboard and processor, the upgrade went well
without any visible errors AFAIK), but in my recollection the error
messages are at least similar as those from the Lenovo T14s laptop. On
Lenovo T14s, I ran
aptitude upgrade linux-image-6.1.0-10-amd64
and got this (in German and partially retyped, so ask if you think there
could be a typo):
Auflösen der Abhängigkeiten ...
Die folgenden Pakete werden aktualisiert:
linux-image-6.1.0-10-amd64 linux-image-amd64
2 Pakete aktualisiert, 0 zusätzlich installiert, 0 werden entfernt und 7
nicht aktualisiert.
68,5 MB an Archiven müssen heruntergeladen werden. Nach dem Entpacken
werden 49,2 kB zusätzlich belegt sein.
Möchten Sie fortsetzen? [Y/n/?] Y
Holen: 1 http://deb.debian.org/debian stable/main amd64
linux-image-amd64 amd64 6.1.38-1 [1.484 B]
Holen: 2 http://deb.debian.org/debian stable/main amd64
linux-image-6.1.0-10-amd64 amd64 6.1.38-1 [68,5 MB]
68,5 MB wurden in 11 s heruntergeladen (6.517 kB/s)
(Lese Datenbank ... 472401 Dateien und Verzeichnisse sind derzeit
installiert.)
Vorbereitung zum Entpacken von .../linux-image-amd64_6.1.38-1_amd64.deb ...
Entpacken von linux-image-amd64 (6.1.38-1) über (6.1.37-1) ...
Vorbereitung zum Entpacken von
.../linux-image-6.1.0-10-amd64_6.1.38-1_amd64.deb ...
Entpacken von linux-image-6.1.0-10-amd64 (6.1.38-1) über (6.1.37-1) ...
linux-image-6.1.0-10-amd64 (6.1.38-1) wird eingerichtet ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-10-amd64.
dkms: autoinstall for kernel: 6.1.0-10-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-10-amd64
Found initrd image: /boot/initrd.img-6.1.0-10-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create
new boot entries.
[ 159.827157] BPF: [99738] STRUCT
[ 159.827646] BPF: size=792 vlen=95
[ 159.828125] BPF:
[ 159.828596] BPF: Invalid name
[ 159.829069] BPF:
[ 159.859864] BPF: [99715] TYPEDEF
[ 159.860353] BPF: type_id=99716
[ 159.860817] BPF:
[ 159.861276] BPF: Invalid name
[ 159.861774] BPF:
[ 159.869287] BPF: ‡ type_id=65 bits_offset=96
[ 159.869756] BPF:
[ 159.870258] BPF: Invalid name
[ 159.870763] BPF:
[ 159.879651] BPF: ‡1_data type_id=75 bits_offset=96
[ 159.880133] BPF:
[ 159.880587] BPF: Invalid name
[ 159.881040] BPF:
[ 159.887531] BPF: [99717] STRUCT
[ 159.887993] BPF: size=6 vlen=6
[ 159.888447] BPF:
[ 159.888897] BPF: Invalid name
[ 159.889349] BPF:
[ 159.894876] BPF: [99714] STRUCT
[ 159.895367] BPF: size=32 vlen=2
[ 159.895814] BPF:
[ 159.896257] BPF: Invalid name
[ 159.896701] BPF:
[ 159.904734] BPF: ‡ type_id=113 bits_offset=96
[ 159.905193] BPF:
[ 159.905645] BPF: Invalid name
[ 159.906105] BPF:
[ 159.911998] BPF: ‡ type_id=99716 bits_offset=384
[ 159.912463] BPF:
[ 159.912905] BPF: Invalid name
[ 159.913349] BPF:
[ 159.920021] BPF: [99714] TYPEDEF
[ 159.920479] BPF: type_id=78
[ 159.920935] BPF:
[ 159.921383] BPF: Invalid name
[ 159.921829] BPF:
Found Windows Boot Manager on
/dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
linux-image-amd64 (6.1.38-1) wird eingerichtet ...
Aktueller Status: 7 (-2) upgradable.
I thought I'd take note of the versions of the 9 packages (2 just
upgraded and 7 remained to be upgraded):
# dpkg -l linux-image-6.1.0-10-amd64 linux-image-amd64 linux-libc-dev
locales sudo systemd-sysv texlive-binaries usb.ids vivaldi-stable
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler:
GROSS=schlecht)
||/ Name Version Architektur
Beschreibung
+++-==========================-=======================-============-========================================================
ii linux-image-6.1.0-10-amd64 6.1.38-1 amd64
Linux 6.1 for 64-bit PCs (signed)
ii linux-image-amd64 6.1.38-1 amd64
Linux for 64-bit PCs (meta-package)
ii linux-libc-dev:amd64 6.1.37-1 amd64
Linux support headers for userspace development
ii locales 2.36-9 all GNU
C Library: National Language (locale) data [support]
ii sudo 1.9.13p3-1 amd64
Provide limited super user privileges to specific users
ii systemd-sysv 252.6-1 amd64
system and service manager - SysV compatibility symlinks
ii texlive-binaries 2022.20220321.62855-5.1 amd64
Binaries for TeX Live
ii usb.ids 2023.01.16-1 all USB
ID Repository
ii vivaldi-stable 6.1.3035.111-1 amd64
Experience the web in a whole new way with Vivaldi.
As the aforementioned error messages might be related to grub, let's
look into its configuration at /etc/default/grub:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
I have dual boot of Debian 12 with Windows 10 or 11 on all computers I
manage, and /etc/grub/default is slightly different on the Asus computer
in question. If you need the file from there, please yell.
What went wrong in the lines
“
[…] BPF: [99738] STRUCT
…
[…] BPF: Invalid name
[…] BPF:
”
? What is there we might need to fix?
Raised severity because this happens on two sufficiently different
computers. (It doesn't happen on all computers, e.g., neither on a very
similar tower with the same Asus motherboard and Intel Xeon processor
nor on an Dell Mobile Precision M6700 with the processor Intel
Core i7-3720QM; therefore severity raised only by 1 step.)
Gratefully,
AlMa
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2023-07-26 22:20 +0200 |
| Subject | Processed: upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” |
| Message-ID | <GVT9J-2YQ2-213@gated-at.bofh.it> |
| In reply to | #79775 |
Processing control commands: > affects -1 grub2-common os-prober grub-common Bug #1042237 [linux-image-6.1.0-10-amd64] upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” Added indication that 1042237 affects grub2-common, os-prober, and grub-common -- 1042237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042237 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | "Al Ma" <alma0@ro.ru> |
|---|---|
| Date | 2023-07-27 19:40 +0200 |
| Subject | Bug#1003965: Processed: upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” |
| Message-ID | <GWd7X-3bM8-1@gated-at.bofh.it> |
| In reply to | #79776 |
[Multipart message — attachments visible in raw view] — view raw
Ben, I wonder why you merged #1042237 and #1003965. The BPF messages coincide in the almost empty lines “[…] BPF:” and coincide up to spacing in “[…] BPF: Invalid name”. The coincidences seem to end here. Some of the remaining “[…] BPF: …” lines are similar but, strictly speaking, different. Moreover, in #1042237 these mesages have been read from the console, whereas in #1003965, they have been taken from the kernel log. Further, in #1042237 no information about any modules is printed, whereas in #1003965, a bunch of modules seems to get not validated and not being able to load. Finally, #1042237 occured during kernel upgrade only once (and has NOT re-occurred so far AFAIK during boot), which might indicate a problem at kernel upgrades, whereas #1003965 occured during boot. Gratefully, AlMa
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-05-01 15:00 +0200 |
| Subject | Bug#1042237: marked as done (upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name”) |
| Message-ID | <KHBG9-hzKE-13@gated-at.bofh.it> |
| In reply to | #79775 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Thu, 01 May 2025 14:50:26 +0200 (CEST) with message-id <20250501125026.8D220BE2DE0@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #1003965, regarding upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name” to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1003965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003965 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web