Bug 1123525

Summary: Errors during boot of updated system on Raspberry Pi 2
Product: [openSUSE] openSUSE Distribution Reporter: Freek de Kruijf <freek>
Component: BasesystemAssignee: Daniel Molkentin <daniel>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: fbui, freek, thomas.blume
Version: Leap 15.0   
Target Milestone: ---   
Hardware: armv7   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: mkinitrd.log.xz
mkinitrd.log from the RPi2

Description Freek de Kruijf 2019-01-29 14:46:53 UTC
On the Raspberry Pi 2 I use Leap 15.0 which is fully updated. During boot I see the following (error) messages on the console:

Failed (-5)
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   No ethernet found.
starting USB...
USB0:   Core Release: 2.80a
scanning bus 0 for devices... error in inquiry
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found EFI removable media binary efi/boot/bootarm.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@7e202000.blk...
Found 4 disks
544256 bytes read in 25 ms (20.8 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
## Starting EFI application at 01000000 ...
Welcome to GRUB!

error: file `/boot/grub2/fonts/unicode.pf2' not found.

Welcome to openSUSE Leap 15.0 dracut-044-lp150.14.12.1 (Initramfs)!

[ other messages ...]

[  OK  ] Started Load Kernel Modules.
[FAILED] Failed to start Setup Virtual Console.
See 'systemctl status systemd-vconsole-setup.service' for details.
[DEPEND] Dependency failed for dracut ask for additional cmdline parameters.
Comment 1 Freek de Kruijf 2019-01-29 15:49:52 UTC
I added a symbolic link in /boot/grub2/fonts/ to /boot/unicode.pf2 and the massage about file `/boot/grub2/fonts/unicode.pf2' not found is gone.
Comment 2 Franck Bui 2019-01-31 10:27:27 UTC
Please avoid opening a single bug report for several issues.

So what does "systemctl status systemd-vconsole-setup.service" report ?
Comment 3 Freek de Kruijf 2019-01-31 11:34:10 UTC
(In reply to Franck Bui from comment #2)
> Please avoid opening a single bug report for several issues.
> 
> So what does "systemctl status systemd-vconsole-setup.service" report ?

Right after a reboot I get the following

# systemctl status systemd-vconsole-setup.service
● systemd-vconsole-setup.service - Setup Virtual Console
   Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2019-01-15 11:05:22 CET; 2 weeks 2 days ago
     Docs: man:systemd-vconsole-setup.service(8)
           man:vconsole.conf(5)
 Main PID: 160 (code=exited, status=1/FAILURE)

jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: cannot open file us.map.gz
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

The above date is the date present in the boot image. Only later a new date from systemd-timesyncd Jan 31 is present, which gets further updated when the network has come up.

After the system became live I did:

# systemctl start systemd-vconsole-setup.service

After which I got:
# journalctl -b -u systemd-vconsole-setup
-- Logs begin at Wed 2018-10-31 14:45:42 CET, end at Thu 2019-01-31 12:18:51 CET. --
jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: cannot open file us.map.gz
jan 31 12:16:33 rpi2150hon systemd[1]: Starting Setup Virtual Console...
jan 31 12:16:33 rpi2150hon systemd[1]: Started Setup Virtual Console.

The first output line is during boot, the next 2 lines result from the start command.
Comment 4 Freek de Kruijf 2019-01-31 11:35:51 UTC
(In reply to Franck Bui from comment #2)
> Please avoid opening a single bug report for several issues.

Should I make another report about:

file `/boot/grub2/fonts/unicode.pf2' not found.
???
Comment 5 Franck Bui 2019-01-31 11:40:58 UTC
(In reply to Freek de Kruijf from comment #4)
> Should I make another report about:
> 
> file `/boot/grub2/fonts/unicode.pf2' not found.
> ???

yes.
Comment 6 Franck Bui 2019-01-31 11:43:33 UTC
(In reply to Freek de Kruijf from comment #3)
> jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: cannot open file
> us.map.gz

On my system the keymap is at /usr/share/kbd/keymaps/xkb/us.map.gz and is owned by kbd package:

 $ rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz
 kbd-2.0.4-9.1.x86_64

It's also part of initrd:

> $ lsinitrd | grep us.map
> -rw-r--r--   1 root     root         2004 Aug  6 12:03 usr/share/kbd/keymaps/legacy/i386/qwerty/us.map
> -rw-r--r--   1 root     root       121059 Aug  6 12:18 usr/share/kbd/keymaps/xkb/us.map

What about your system ?
Comment 7 Freek de Kruijf 2019-01-31 12:17:39 UTC
(In reply to Franck Bui from comment #5)
> (In reply to Freek de Kruijf from comment #4)
> > Should I make another report about:
> > 
> > file `/boot/grub2/fonts/unicode.pf2' not found.
> > ???
> 
> yes.

See https://bugzilla.suse.com/show_bug.cgi?id=1123856
Comment 8 Freek de Kruijf 2019-01-31 12:24:00 UTC
(In reply to Franck Bui from comment #6)
> (In reply to Freek de Kruijf from comment #3)
> > jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: cannot open file
> > us.map.gz
> 
> On my system the keymap is at /usr/share/kbd/keymaps/xkb/us.map.gz and is
> owned by kbd package:
> 
>  $ rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz
>  kbd-2.0.4-9.1.x86_64
> 
> It's also part of initrd:
> 
> > $ lsinitrd | grep us.map
> > -rw-r--r--   1 root     root         2004 Aug  6 12:03 usr/share/kbd/keymaps/legacy/i386/qwerty/us.map
> > -rw-r--r--   1 root     root       121059 Aug  6 12:18 usr/share/kbd/keymaps/xkb/us.map
> 
> What about your system ?

Same.
# rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz
kbd-2.0.4-9.1.x86_64

# lsinitrd | grep us.map

shows nothing.

I have:

# lsinitrd | grep '\.map'
-rw-r--r--   1 root     root        11915 Aug  6 12:03 usr/share/kbd/keymaps/legacy/i386/qwerty/us-acentos.map
Comment 9 Franck Bui 2019-01-31 12:35:56 UTC
(In reply to Freek de Kruijf from comment #8)
> # lsinitrd | grep us.map
> 
> shows nothing.
> 
> I have:
> 
> # lsinitrd | grep '\.map'
> -rw-r--r--   1 root     root        11915 Aug  6 12:03
> usr/share/kbd/keymaps/legacy/i386/qwerty/us-acentos.map

Daniel, could you have a look and see why the right keymap (us.map) is not included in initrd here ?
Comment 11 Thomas Blume 2019-02-01 09:29:46 UTC
(In reply to Freek de Kruijf from comment #8)
> # rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz
> kbd-2.0.4-9.1.x86_64
> 
> # lsinitrd | grep us.map
> 
> shows nothing.
> 
> I have:
> 
> # lsinitrd | grep '\.map'
> -rw-r--r--   1 root     root        11915 Aug  6 12:03
> usr/share/kbd/keymaps/legacy/i386/qwerty/us-acentos.map

Please provide:

/var/log/YaST2/mkinitrd.log
Comment 12 Freek de Kruijf 2019-02-01 12:38:05 UTC
Created attachment 795805 [details]
mkinitrd.log.xz

mkinitrd.log.xz
Comment 13 Thomas Blume 2019-02-01 13:21:11 UTC
(In reply to Freek de Kruijf from comment #12)
> Created attachment 795805 [details]
> mkinitrd.log.xz
> 
> mkinitrd.log.xz

Thanks, the log shows this error:

I: *** Including module: i18n ***
W: Could not find FONT_MAP none!

Can you please attach /etc/vconsole.conf?
Comment 14 Franck Bui 2019-02-01 13:25:01 UTC
(In reply to Thomas Blume from comment #13)
> I: *** Including module: i18n ***
> W: Could not find FONT_MAP none!
> 

Ah then it's a duplicate of bsc#1013573
Comment 15 Thomas Blume 2019-02-01 13:56:59 UTC
(In reply to Franck Bui from comment #14)
> (In reply to Thomas Blume from comment #13)
> > I: *** Including module: i18n ***
> > W: Could not find FONT_MAP none!
> > 
> 
> Ah then it's a duplicate of bsc#1013573

Indeed, marking as duplicate then.

*** This bug has been marked as a duplicate of bug 1013573 ***
Comment 16 Freek de Kruijf 2019-02-01 14:13:20 UTC
(In reply to Thomas Blume from comment #13)
> (In reply to Freek de Kruijf from comment #12)
> > Created attachment 795805 [details]
> > mkinitrd.log.xz
> > 
> > mkinitrd.log.xz
> 
> Thanks, the log shows this error:
> 
> I: *** Including module: i18n ***
> W: Could not find FONT_MAP none!
> 
> Can you please attach /etc/vconsole.conf?

(In reply to Freek de Kruijf from comment #12)
> Created attachment 795805 [details]
> mkinitrd.log.xz
> 
> mkinitrd.log.xz

I am sorry this was the wrong file, not from the Raspberry Pi 2.
The correct one is attached now.
Comment 17 Freek de Kruijf 2019-02-01 14:15:43 UTC
Created attachment 795813 [details]
mkinitrd.log from the RPi2

This is the correct one from the Raspberry Pi 2 (Leap 15.0).
It may not be a duplicate.
Comment 18 Freek de Kruijf 2019-02-01 21:06:24 UTC
(In reply to Thomas Blume from comment #13)
> (In reply to Freek de Kruijf from comment #12)
> > Created attachment 795805 [details]
> > mkinitrd.log.xz
> > 
> > mkinitrd.log.xz
> 
> Thanks, the log shows this error:
> 
> I: *** Including module: i18n ***
> W: Could not find FONT_MAP none!
> 
> Can you please attach /etc/vconsole.conf?

# more /etc/vconsole.conf 
KEYMAP=us.map.gz
Comment 19 Thomas Blume 2019-02-04 12:04:02 UTC
(In reply to Freek de Kruijf from comment #16)
> I am sorry this was the wrong file, not from the Raspberry Pi 2.
> The correct one is attached now.

Ok, reopening.
The information from comment#8 must also be from another machine:

-->
# rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz
kbd-2.0.4-9.1.x86_64
              ^^^^^^^
[...]
# lsinitrd | grep '\.map'
-rw-r--r--   1 root     root        11915 Aug  6 12:03 usr/share/kbd/keymaps/legacy/i386/qwerty/us-acentos.map
        ^^^^
--<

Raspberry P2 has architecture arm instead of x86_64 or i386.
Can you please double check and attach the output from your Raspberry.

(In reply to Freek de Kruijf from comment #18)
> > Can you please attach /etc/vconsole.conf?
> 
> # more /etc/vconsole.conf 
> KEYMAP=us.map.gz

Please remove the .gz suffix from the keymap name, otherwise systemd-vconsole-setup will fail:

-->
Feb 04 12:45:49 linux-s9lv systemd-vconsole-setup[127]: Executing "/usr/bin/loadkeys -q -C /dev/tty1 -u us.map.gz"...
[...]
Feb 04 12:45:49 linux-s9lv systemd-vconsole-setup[127]: /usr/bin/loadkeys failed with error code 1.
--<
Comment 20 Freek de Kruijf 2019-02-04 15:29:30 UTC
(In reply to Thomas Blume from comment #19)
> (In reply to Freek de Kruijf from comment #16)
> > I am sorry this was the wrong file, not from the Raspberry Pi 2.
> > The correct one is attached now.
> 
> Ok, reopening.



# rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz
kbd-2.0.4-lp150.6.2.armv7hl
# lsinitrd | grep '\.map'
-rw-r--r--   1 root     root          249 May  8  2018 usr/share/kbd/keymaps/legacy/i386/include/euro1.map
-rw-r--r--   1 root     root         2004 May  8  2018 usr/share/kbd/keymaps/legacy/i386/qwerty/us.map
-rw-r--r--   1 root     root       121059 May  8  2018 usr/share/kbd/keymaps/xkb/us.map
# more /etc/vconsole.conf
KEYMAP=us.map.gz
rpi2150hon:~ #

> Please remove the .gz suffix from the keymap name, otherwise systemd-vconsole-setup will fail:

When I change the above to KEYMAP=us.map I get an error message:
jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: /usr/bin/loadkeys failed with error code 1.
jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: cannot open file us.map.gz
jan 15 11:05:22 rpi2150hon systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE
jan 15 11:05:22 rpi2150hon systemd[1]: Failed to start Setup Virtual Console.
jan 15 11:05:22 rpi2150hon systemd[1]: systemd-vconsole-setup.service: Unit entered failed state.

So KEYMAP=us.map.gz seems OK.
Comment 21 Thomas Blume 2019-02-05 09:05:24 UTC
(In reply to Freek de Kruijf from comment #20)
> # rpm -qf /usr/share/kbd/keymaps/xkb/us.map.gz
> kbd-2.0.4-lp150.6.2.armv7hl
> # lsinitrd | grep '\.map'
> -rw-r--r--   1 root     root          249 May  8  2018
> usr/share/kbd/keymaps/legacy/i386/include/euro1.map
> -rw-r--r--   1 root     root         2004 May  8  2018
> usr/share/kbd/keymaps/legacy/i386/qwerty/us.map
> -rw-r--r--   1 root     root       121059 May  8  2018
> usr/share/kbd/keymaps/xkb/us.map
> # more /etc/vconsole.conf
> KEYMAP=us.map.gz
> rpi2150hon:~ #
> 
> > Please remove the .gz suffix from the keymap name, otherwise systemd-vconsole-setup will fail:
> 
> When I change the above to KEYMAP=us.map I get an error message:
> jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: /usr/bin/loadkeys
> failed with error code 1.
> jan 15 11:05:22 rpi2150hon systemd-vconsole-setup[160]: cannot open file
> us.map.gz
> jan 15 11:05:22 rpi2150hon systemd[1]: systemd-vconsole-setup.service: Main
> process exited, code=exited, status=1/FAILURE
> jan 15 11:05:22 rpi2150hon systemd[1]: Failed to start Setup Virtual Console.
> jan 15 11:05:22 rpi2150hon systemd[1]: systemd-vconsole-setup.service: Unit
> entered failed state.
> 
> So KEYMAP=us.map.gz seems OK.

Hm, that is pretty strange.
The lsinitrd above shows that there is no file us.map.gz in the initrd.
When I set:

KEYMAP=us.map.gz

on my testmachine.
I get in the debug logs:

-->
Feb 05 09:32:33 linux-s9lv systemd-vconsole-setup[130]: cannot open file us.map.gz
[...]
Feb 05 09:32:33 linux-s9lv systemd-vconsole-setup[130]: Executing "/usr/bin/loadkeys -q -C /dev/tty1 -u us.map.gz"...
[...]
Feb 05 09:32:33 linux-s9lv systemd-vconsole-setup[130]: /usr/bin/loadkeys failed with error code 1.
--<

So in my tests, the keymap setup in the initrd fails, when using the .gz suffix.
Could you please set:

KEYMAP=us.map

in /etc/vconsole.conf

then run:

mkinitrd

and reboot with the boot option "quiet" removed and the boot option "debug" set?
Afterwards, please attach the output of:

journalctl -axb | grep systemd-vconsole-setup
Comment 22 Freek de Kruijf 2019-02-05 11:19:19 UTC
(In reply to Thomas Blume from comment #21)
> So in my tests, the keymap setup in the initrd fails, when using the .gz
> suffix.
> Could you please set:
> 
> KEYMAP=us.map
> 
> in /etc/vconsole.conf
> 
> then run:
> 
> mkinitrd
> 
> and reboot with the boot option "quiet" removed and the boot option "debug"
> set?

Could not find quiet in /boot/grub2/grub.cfg
Added at the end of the line starting with linux debug
The line now reads:
                linux   /boot/zImage-4.12.14-lp150.12.45-lpae root=UUID=fb7f00e9-5158-46a5-8768-90577062e283  loglevel=3 splash=silent plymouth.enable=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200n8 kgdboc=ttyAMA0,115200 rootflags=commit=120,data=writeback root=UUID=fb7f00e9-5158-46a5-8768-90577062e283 rw debug


> Afterwards, please attach the output of:
> 
> journalctl -axb | grep systemd-vconsole-setup

# journalctl -axb | grep systemd-vconsole-setup
-- Subject: Unit systemd-vconsole-setup.service has finished start-up
-- Unit systemd-vconsole-setup.service has finished starting up.
Comment 23 Thomas Blume 2019-02-07 12:17:22 UTC
(In reply to Freek de Kruijf from comment #22)
> (In reply to Thomas Blume from comment #21)
> > So in my tests, the keymap setup in the initrd fails, when using the .gz
> > suffix.
> > Could you please set:
> > 
> > KEYMAP=us.map
> > 
> > in /etc/vconsole.conf
> > 
> > then run:
> > 
> > mkinitrd
> > 
> > and reboot with the boot option "quiet" removed and the boot option "debug"
> > set?
> 
> Could not find quiet in /boot/grub2/grub.cfg
> Added at the end of the line starting with linux debug
> The line now reads:
>                 linux   /boot/zImage-4.12.14-lp150.12.45-lpae
> root=UUID=fb7f00e9-5158-46a5-8768-90577062e283  loglevel=3 splash=silent
> plymouth.enable=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200n8
> kgdboc=ttyAMA0,115200 rootflags=commit=120,data=writeback
> root=UUID=fb7f00e9-5158-46a5-8768-90577062e283 rw debug
> 
> 
> > Afterwards, please attach the output of:
> > 
> > journalctl -axb | grep systemd-vconsole-setup
> 
> # journalctl -axb | grep systemd-vconsole-setup
> -- Subject: Unit systemd-vconsole-setup.service has finished start-up
> -- Unit systemd-vconsole-setup.service has finished starting up.

Seems that he vconsole setup error is fixed with this configuration.
Can you confirm this?
Comment 24 Freek de Kruijf 2019-02-07 13:25:56 UTC
(In reply to Thomas Blume from comment #23)
> Seems that he vconsole setup error is fixed with this configuration.
> Can you confirm this?

Repeated the setup without debug on the linux line and got the same result.

Seems OK.
Comment 25 Thomas Blume 2019-02-07 14:24:09 UTC
(In reply to Freek de Kruijf from comment #24)
> (In reply to Thomas Blume from comment #23)
> > Seems that he vconsole setup error is fixed with this configuration.
> > Can you confirm this?
> 
> Repeated the setup without debug on the linux line and got the same result.
> 
> Seems OK.

Ok thanks, closing therewith.