[Bug 1140464] New: grub: error message "error: serial port `com0' isn't found. error: terminal `serial' isn't found."
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464 Bug ID: 1140464 Summary: grub: error message "error: serial port `com0' isn't found. error: terminal `serial' isn't found." Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: okurz@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- ## Observation On the serial terminal (SOL from IPMI) of an aarch64 machine I can see the following error messages immediately after the message `Welcome to GRUB!`: ``` error: serial port `com0' isn't found. error: terminal `serial' isn't found. error: terminal `serial' isn't found. ``` but the grub menu appears correctly though in the SOL session. /etc/default/grub contains: ``` GRUB_SERIAL_COMMAND="serial --unit=0 --speed=115200 --parity=no" ``` output on dmesg regarding any serial port: ``` [ 0.278976] Serial: AMBA PL011 UART driver [ 2.621554] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 2.827127] Serial: AMBA driver [ 2.827201] msm_serial: driver initialized [ 2.869881] ARMH0011:00: ttyAMA0 at MMIO 0x602b0000 (irq = 8, base_baud = 0) is a SBSA [ 2.869917] console [ttyAMA0] enabled ``` I assume the configuration comes from the YaST installer? ## Further details External references I have found: * https://forum.up-community.org/discussion/1883/i-installed-ubuntu-16-04-2-de... * https://lists.gnu.org/archive/html/help-grub/2017-01/msg00018.html -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464#c1
--- Comment #1 from Michael Chang
## Observation
On the serial terminal (SOL from IPMI) of an aarch64 machine I can see the following error messages immediately after the message `Welcome to GRUB!`:
``` error: serial port `com0' isn't found. error: terminal `serial' isn't found. error: terminal `serial' isn't found. ```
Yes, the aarch64 cpu doesn't have io ports to access ns8250/UART device, that's why having "com0 isn't found" as "com0" represents first ns8250 device found by grub and is default device name if omitted in the serial command. For aarch64, the efi serial input/output protocol is used to configure the serial device, and syntax could be looking like. GRUB_SERIAL_COMMAND="serial --unit=0 --speed=115200 --parity=no efi0" It depends on running UEFI firmware to work, if implemented. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464#c2
--- Comment #2 from Michael Chang
The aarch64 has no ns8250 (In reply to Oliver Kurz from comment #0)
GRUB_SERIAL_COMMAND="serial --unit=0 --speed=115200 --parity=no efi0"
No. --unit=0 may binds to com0, maybe GRUB_SERIAL_COMMAND="serial efi0 --speed=115200 --parity=no" Test on aarch64 server is really needed to know how it works. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464#c3
--- Comment #3 from Oliver Kurz
Test on aarch64 server is really needed to know how it works.
I see. So do I read this as you plan to do this? I guess this could be emulated with qemu easily. Feel free to use openQA itself, e.g. using the approach as described on http://open.qa/docs/#_triggering_tests_based_on_an_any_remote_git_refspec_or... you could adapt some test to do this in a scratch git branch. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464
http://bugzilla.opensuse.org/show_bug.cgi?id=1140464#c4
--- Comment #4 from Michael Chang
(In reply to Michael Chang from comment #2)
Test on aarch64 server is really needed to know how it works.
I just tested on physical aarch64 server and it worked with the sequence below grub> terminal_output Active output terminals: console Available output terminals: gfxterm serial_* grub> terminal_input Active input terminals: console Available input terminals: serial_* grub> serial efi0 --speed=115200 --parity=no grub> terminal_output Active output terminals: console Available output terminals: gfxterm serial_efi0 grub> terminal_input Active input terminals: console Available input terminals: serial_efi0 grub> terminal_output serial_efi0; terminal_input serial_efi0 To connect it from a linux box: screen /dev/ttyUSB0 115200
I see. So do I read this as you plan to do this? I guess this could be emulated with qemu easily. Feel free to use openQA itself, e.g. using the approach as described on http://open.qa/docs/ #_triggering_tests_based_on_an_any_remote_git_refspec_or_open_github_pull_req uest you could adapt some test to do this in a scratch git branch.
I suppose you were mentioning some aarch64 openQA testcases needs to be changed to use the corrected serial command. I am not much into openQA so it will require more time to work on verifying it directly by the article you provided. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com