[opensuse] Kernel lock on boot of 42.2
I get several lines saying (hand copied): Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _ Then hard lock. I have to powercycle to reboot. Ideas? -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R.
I get several lines saying (hand copied):
Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _
Then hard lock. I have to powercycle to reboot.
Ideas?
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0ahUKEwjc4aa8oZLRAhXDSSYKHQoaAp0QFggkMAE&url=https%3A%2F%2Fbbs.archlinux.org%2Fviewtopic.php%3Fid%3D52766&usg=AFQjCNGF_iTYSsTWungXSm6u9-CSBH7u-A&sig2=LkmMfn5XuplaqrCr9wat_g&cad=rja from google search "binfmt-464c" https://sourceforge.net/p/user-mode-linux/mailman/message/20181503/ <quote> The problem is that you are trying to boot a 32-bit filesystem on a 64-bit UML, and UML doesn't have 32-bit compatibility. You need to either get a 64-bit filesystem, or run a 32-bit UML. If you try the 32-bit UML and it crashes and you have a not-too-recent host kernel, it may need upgrading, as there were some 32-bit compatibility bugs fixed a while ago. </quote> ... and more -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-12-26 17:23, Patrick Shanahan wrote:
* Carlos E. R.
[12-26-16 11:09]: I get several lines saying (hand copied):
Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _
Then hard lock. I have to powercycle to reboot.
Ideas?
from google search "binfmt-464c"
https://sourceforge.net/p/user-mode-linux/mailman/message/20181503/ <quote> The problem is that you are trying to boot a 32-bit filesystem on a 64-bit UML, and UML doesn't have 32-bit compatibility. You need to either get a 64-bit filesystem, or run a 32-bit UML. If you try the 32-bit UML and it crashes and you have a not-too-recent host kernel, it may need upgrading, as there were some 32-bit compatibility bugs fixed a while ago. </quote> ... and more
But I have not tried to install UML. I have no idea what it is (even after reading a bit on google). It is a 42.2 system upgraded from 13.1 Kernel file is vmlinuz-4.4.36-8-default, the most recent possible, officially. I'm not aware of what a "32-bit filesystem" would be. This machine has always been 64 bits. Gestor:/ # locate binfmt-464c Gestor:/ # There is no such module in the filesystem. -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
26.12.2016 19:08, Carlos E. R. пишет:
I get several lines saying (hand copied):
Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _
This implies that modprobe is nor valid ELF executable (or may be simply does not have executable bits). Boot from live media and check file. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-12-26 19:41, Andrei Borzenkov wrote:
26.12.2016 19:08, Carlos E. R. пишет:
I get several lines saying (hand copied):
Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _
This implies that modprobe is nor valid ELF executable (or may be simply does not have executable bits). Boot from live media and check file.
Not that... Gestor:/ # l /sbin/modprobe lrwxrwxrwx 1 root root 13 Dec 26 14:37 /sbin/modprobe -> /usr/bin/kmod* Gestor:/ # l /usr/bin/kmod -rwxr-xr-x 1 root root 142432 Oct 7 17:50 /usr/bin/kmod* Gestor:/ # l /usr/sbin/modprobe lrwxrwxrwx 1 root root 11 Dec 26 14:37 /usr/sbin/modprobe -> ../bin/kmod* Gestor:/ # Gestor:/ # file /usr/bin/kmod /usr/bin/kmod: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.0, BuildID[sha1]=bf216189cc70d267f65056b9e332d6bb2f58f2bf, stripped Gestor:/ # -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-12-26 19:57, Carlos E. R. wrote:
On 2016-12-26 19:41, Andrei Borzenkov wrote:
26.12.2016 19:08, Carlos E. R. пишет:
I get several lines saying (hand copied):
Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _
This implies that modprobe is nor valid ELF executable (or may be simply does not have executable bits). Boot from live media and check file.
Not that...
Gestor:/ # l /sbin/modprobe lrwxrwxrwx 1 root root 13 Dec 26 14:37 /sbin/modprobe -> /usr/bin/kmod* Gestor:/ # l /usr/bin/kmod -rwxr-xr-x 1 root root 142432 Oct 7 17:50 /usr/bin/kmod* Gestor:/ # l /usr/sbin/modprobe lrwxrwxrwx 1 root root 11 Dec 26 14:37 /usr/sbin/modprobe -> ../bin/kmod* Gestor:/ # Gestor:/ # file /usr/bin/kmod /usr/bin/kmod: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.0, BuildID[sha1]=bf216189cc70d267f65056b9e332d6bb2f58f2bf, stripped Gestor:/ #
Oh, I forgot I should look at the initrd image, initrd-4.4.36-8-default. I rename it to "initrd-4.4.36-8-default.cpio" and open it with 'mc'. Its size is "16972K", but it only appears to contain: Gestor:~/tmp/cpio # tree . ├── early_cpio 2 bytes └── kernel └── x86 └── microcode └── GenuineIntel.bin 24576 3 directories, 2 files I don't understand. -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-12-26 20:04, Carlos E. R. wrote:
On 2016-12-26 19:57, Carlos E. R. wrote:
On 2016-12-26 19:41, Andrei Borzenkov wrote:
26.12.2016 19:08, Carlos E. R. пишет:
Oh, I forgot I should look at the initrd image, initrd-4.4.36-8-default. I rename it to "initrd-4.4.36-8-default.cpio" and open it with 'mc'. Its size is "16972K", but it only appears to contain:
Gestor:~/tmp/cpio # tree . ├── early_cpio 2 bytes └── kernel └── x86 └── microcode └── GenuineIntel.bin 24576
3 directories, 2 files
I don't understand.
I recreated the initrd in a chroot, and it appears to be the same thing. -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
26.12.2016 22:04, Carlos E. R. пишет:
On 2016-12-26 19:57, Carlos E. R. wrote:
On 2016-12-26 19:41, Andrei Borzenkov wrote:
26.12.2016 19:08, Carlos E. R. пишет:
I get several lines saying (hand copied):
Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _
This implies that modprobe is nor valid ELF executable (or may be simply does not have executable bits). Boot from live media and check file.
Not that...
Gestor:/ # l /sbin/modprobe lrwxrwxrwx 1 root root 13 Dec 26 14:37 /sbin/modprobe -> /usr/bin/kmod* Gestor:/ # l /usr/bin/kmod -rwxr-xr-x 1 root root 142432 Oct 7 17:50 /usr/bin/kmod* Gestor:/ # l /usr/sbin/modprobe lrwxrwxrwx 1 root root 11 Dec 26 14:37 /usr/sbin/modprobe -> ../bin/kmod* Gestor:/ # Gestor:/ # file /usr/bin/kmod /usr/bin/kmod: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.0, BuildID[sha1]=bf216189cc70d267f65056b9e332d6bb2f58f2bf, stripped Gestor:/ #
This only shows header, kernel does some more in depth checks. Can you actually run it?
Oh, I forgot I should look at the initrd image, initrd-4.4.36-8-default. I rename it to "initrd-4.4.36-8-default.cpio" and open it with 'mc'. Its size is "16972K", but it only appears to contain:
Gestor:~/tmp/cpio # tree . ├── early_cpio 2 bytes └── kernel └── x86 └── microcode └── GenuineIntel.bin 24576
3 directories, 2 files
I don't understand.
/usr/lib/dracut/skipcpio /boot/initrd | lsinitrd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-26 20:55, Andrei Borzenkov wrote:
26.12.2016 22:04, Carlos E. R. пишет:
This only shows header, kernel does some more in depth checks. Can you actually run it?
The actual problem is very different, see my last post... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhheY8ACgkQja8UbcUWM1yKrgEAlMOWdiBcDGN9xKmHYuDxUe9+ Bjx4vFm5zVG2Hw02xrYBAI8ZdLknwFcWnvWdVzU3T+3AFoXN3JR4evhnveqvVLiQ =QJ3j -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-26 17:08, Carlos E. R. wrote:
I get several lines saying (hand copied):
Freeing unused kernel memory: 264k fred Write protecting the kernel read only data: 136k request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c _
Then hard lock. I have to powercycle to reboot.
Ideas?
It is the kernel itself. I booted with a previous kernel and it runs. cer@Telcontar:~> uname -a Linux Telcontar 4.4.36-8-default #1 SMP Fri Dec 9 16:18:38 UTC 2016 (3ec5648) x86_64 x86_64 x86_64 GNU/Linux cer@Telcontar:~> l /boot/vmlinu* - -rw-r--r-- 1 root root 6868986 Dec 9 23:39 /boot/vmlinux-4.4.36-8-default.gz lrwxrwxrwx 1 root root 24 Dec 26 14:38 /boot/vmlinuz -> vmlinuz-4.4.36-8-default - -rw-r--r-- 1 root root 2026208 Jan 28 2009 /boot/vmlinuz-2.6.25.20-0.1-cer - -rw-r--r-- 1 root root 5877960 Dec 10 00:22 /boot/vmlinuz-4.4.36-8-default lrwxrwxrwx 1 root root 25 Jan 31 2010 /boot/vmlinuz-cer -> vmlinuz-2.6.25.20-0.1-cer lrwxrwxrwx 1 root root 35 Jan 31 2010 /boot/vmlinuz-cer.old -> /boot/vmlinuz-2.6.22.13-0.3-cer.old cer@Telcontar:~> But I'm unable to identify which is the faulty kernel that grub2 boots by default, it doesn't say which it is in the menu. I will have to examine grub config. Found it! menuentry 'openSUSE Leap 42.2' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-c6a59497-85b9-454c-a5d1-1dcafa6eed3d' { load_video insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt5' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5 --hint='hd0,gpt5' e99d9dcb-869d-4a24-94cf-cba32f169b8d else search --no-floppy --fs-uuid --set=root e99d9dcb-869d-4a24-94cf-cba32f169b8d fi echo 'Loading Linux cer ...' linux /vmlinuz-cer root=UUID=c6a59497-85b9-454c-a5d1-1dcafa6eed3d splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/Swap_0 splash=verbose showopts echo 'Loading initial ramdisk ...' initrd /initrd-cer } Telcontar:~ # lsblk --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | grep 1dcafa6eed3d ├─sda8 sda8 512 0 0 30G part ext4 a_main primary / c6a59497-85b9-454c-a5d1-1dcafa6eed3d 880b53b2-2202-410c-ba20-4ba1a5a47d3e 0 Telcontar:~ # lsblk --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT | grep cba32f169b8d ├─sda5 sda5 512 0 0 1G part ext2 a_boot_2 primary /boot e99d9dcb-869d-4a24-94cf-cba32f169b8d 31a69a08-1633-4a55-9780-5f1803660513 0 Telcontar:~ # The /&&/%$ thing is booting "vmlinuz-cer", which is vmlinuz-2.6.25.20-0.1-cer and dated 2010! And 32 bit! Telcontar:~ # file /boot/vmlinuz-2.6.25.20-0.1-cer /boot/vmlinuz-2.6.25.20-0.1-cer: Linux/x86 Kernel, Setup Version 0x207, bzImage, Version 2.6.25.20-0.1-cer (geeko@buildhost) #1 Wed Jan 28 19:02:29 CET , RO-rootFS, root_dev 0x1646, swap_dev 0x1, Normal VGA Telcontar:~ # Now, how do I tell grub2 to boot the correct kernel by default? Why did it pick that one, is it a bug? Of course, I can delete that old kernel, but will it then pick the right one? - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhheTkACgkQja8UbcUWM1xNuwEAgPUB66hcBreJSRT65BeCKePO is5Vd/r6Aq7MIr+4NJgA/1HzKrMk0beU0dC3NeM4zm9u/bvav0g33IeyfaZQwTg2 =/Z86 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
26.12.2016 23:10, Carlos E. R. пишет: ...
cer@Telcontar:~> l /boot/vmlinu* -rw-r--r-- 1 root root 6868986 Dec 9 23:39 /boot/vmlinux-4.4.36-8-default.gz lrwxrwxrwx 1 root root 24 Dec 26 14:38 /boot/vmlinuz -> vmlinuz-4.4.36-8-default -rw-r--r-- 1 root root 2026208 Jan 28 2009 /boot/vmlinuz-2.6.25.20-0.1-cer -rw-r--r-- 1 root root 5877960 Dec 10 00:22 /boot/vmlinuz-4.4.36-8-default lrwxrwxrwx 1 root root 25 Jan 31 2010 /boot/vmlinuz-cer -> vmlinuz-2.6.25.20-0.1-cer lrwxrwxrwx 1 root root 35 Jan 31 2010 /boot/vmlinuz-cer.old -> /boot/vmlinuz-2.6.22.13-0.3-cer.old cer@Telcontar:~>
...
The /&&/%$ thing is booting "vmlinuz-cer", which is vmlinuz-2.6.25.20-0.1-cer and dated 2010! And 32 bit!
So it was unsupported binary format after all :)
Now, how do I tell grub2 to boot the correct kernel by default?
You can tell which kernel should be default, but then it will also stick even after update. You cannot tell it to skip some kernel.
Why did it pick that one, is it a bug?
It depends on your definition of a bug. grub default scripts sort kernel names in descending order and pick up the first one as default assuming it has the highest version. It works as long as names are uniform. In your case "cer" sorts before numerical and so is considered "the most recent".
Of course, I can delete that old kernel, but will it then pick the right one?
If you delete this symlink vmlinuz-2.6.xxx should sort after vmlinuz-4.4.xxx and so not chosen as default.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-26 21:57, Andrei Borzenkov wrote:
26.12.2016 23:10, Carlos E. R. пишет: ...
cer@Telcontar:~> l /boot/vmlinu* -rw-r--r-- 1 root root 6868986 Dec 9 23:39 /boot/vmlinux-4.4.36-8-default.gz lrwxrwxrwx 1 root root 24 Dec 26 14:38 /boot/vmlinuz -> vmlinuz-4.4.36-8-default -rw-r--r-- 1 root root 2026208 Jan 28 2009 /boot/vmlinuz-2.6.25.20-0.1-cer -rw-r--r-- 1 root root 5877960 Dec 10 00:22 /boot/vmlinuz-4.4.36-8-default lrwxrwxrwx 1 root root 25 Jan 31 2010 /boot/vmlinuz-cer -> vmlinuz-2.6.25.20-0.1-cer lrwxrwxrwx 1 root root 35 Jan 31 2010 /boot/vmlinuz-cer.old -> /boot/vmlinuz-2.6.22.13-0.3-cer.old cer@Telcontar:~>
...
The /&&/%$ thing is booting "vmlinuz-cer", which is vmlinuz-2.6.25.20-0.1-cer and dated 2010! And 32 bit!
So it was unsupported binary format after all :)
Indeed, LOL :-) Apparently that old kernel came from when I updated my hardware to 64 bits.
Now, how do I tell grub2 to boot the correct kernel by default?
You can tell which kernel should be default, but then it will also stick even after update. You cannot tell it to skip some kernel.
Oh. Nor to choose a particular kernel "family". I mean, using a particular name pattern.
Why did it pick that one, is it a bug?
It depends on your definition of a bug. grub default scripts sort kernel names in descending order and pick up the first one as default assuming it has the highest version. It works as long as names are uniform. In your case "cer" sorts before numerical and so is considered "the most recent".
Oh! I see. So, this is an unexpected side effect from "upgrading" from grub 1 to 2. I was upgrading from 13.1 to Leap 42.2. YaST wanted to upgrade grub, and although I had previously decided to do that after system upgrade (at your suggestion on another thread), I went along and accepted.
Of course, I can delete that old kernel, but will it then pick the right one?
If you delete this symlink vmlinuz-2.6.xxx should sort after vmlinuz-4.4.xxx and so not chosen as default.
Ok! Will do, thanks :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhh0MMACgkQja8UbcUWM1zT2gEAgDXuHihZyeYsWKKeZXs9Brny 8k2i6d/D4Q3C6FC4bysA/ivbozi6fKF1wK10kmrMkJZVoqqOIzkvxFPqM2FbdFrI =eUJT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrei Borzenkov
-
Carlos E. R.
-
Patrick Shanahan