Bug 743787 - grub menu displays (harmless?) errors about serial console
Summary: grub menu displays (harmless?) errors about serial console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedNTH
Depends On:
Blocks: F16-accepted, F16FinalFreezeExcept
TreeView+ depends on / blocked
 
Reported: 2011-10-06 02:35 UTC by Dave Allan
Modified: 2016-04-27 00:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-03 01:49:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot of grub menu (86.65 KB, image/png)
2011-10-06 02:37 UTC, Dave Allan
no flags Details
/etc/default/grub (32 bytes, text/plain)
2011-10-25 01:21 UTC, Dave Allan
no flags Details
/boot/grub2/grub.cfg (2.75 KB, text/plain)
2011-10-25 01:22 UTC, Dave Allan
no flags Details
install log (10.30 KB, text/plain)
2011-10-25 18:10 UTC, Dave Allan
no flags Details
anaconda program log (34.27 KB, text/plain)
2011-10-25 18:11 UTC, Dave Allan
no flags Details
/etc/default/grub (317 bytes, text/plain)
2011-10-25 19:20 UTC, Dave Allan
no flags Details

Description Dave Allan 2011-10-06 02:35:10 UTC
After installing F16 Beta with serial console only, I see the following errors at the grub menu:

error: the argument `--speed=' requires an integer.
error: unknown terminal 'serial'
.
error: unknown terminal 'serial'
.

I ran into BZ 743642 during the install, so I had to manually install grub after booting into rescue mode.  I don't know how that affected things.  The errors appear to be harmless; the console behaves properly other than BZ 739522

Comment 1 Dave Allan 2011-10-06 02:37:11 UTC
Created attachment 526607 [details]
screenshot of grub menu

I've attached a screenshot of the grub menu.

Comment 2 Mads Kiilerich 2011-10-24 23:55:52 UTC
Please attach /etc/default/grub and /boot/grub2/grub.cfg.

Comment 3 Dave Allan 2011-10-25 01:21:33 UTC
Created attachment 529980 [details]
/etc/default/grub

Comment 4 Dave Allan 2011-10-25 01:22:00 UTC
Created attachment 529981 [details]
/boot/grub2/grub.cfg

Comment 5 Mads Kiilerich 2011-10-25 14:34:23 UTC
grubs complains makes sense; grub.cfg contains
  serial --unit=0 --speed=
  terminal_input serial console
  terminal_output serial console

that _must_ be caused by invalid settings in /etc/default/grub made by anaconda. The file has however been overwritten by a grub update because of bug 741045, so the evidence has been removed.

Can you reproduce the problem by installing from the latest test composes? Is it really creating a /etc/default/grub without speed? If so the anaconda log and program.log might be useful.


Just a thought ... are you using a "real" serial console where you specify the speed? Or is it some kind of virtual xen serial console where you don't specify any speed?

Comment 6 Mads Kiilerich 2011-10-25 17:09:11 UTC
/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py :
            speed = "9600"
            for opt in self.console_options.split(","):
                if opt.isdigit:
                    speed = opt
                    break

            command = "serial --unit=%s --speed=%s" % (unit, speed)

opt.isdigit is always true - it should be opt.isdigit(). That can explain why GRUB_SERIAL_COMMAND contains an invalid speed setting. Which kernel boot parameters did you use?

Comment 7 Adam Williamson 2011-10-25 17:30:41 UTC
proposing as NTH for final, for now: we're not entirely clear what consequences this causes due to the masking bug, but it looks like something that anaconda's clearly getting wrong, which it ought to be getting right, at the least.

Comment 8 Dave Allan 2011-10-25 18:09:33 UTC
(In reply to comment #5)
> grubs complains makes sense; grub.cfg contains
>   serial --unit=0 --speed=
>   terminal_input serial console
>   terminal_output serial console
> 
> that _must_ be caused by invalid settings in /etc/default/grub made by
> anaconda. The file has however been overwritten by a grub update because of bug
> 741045, so the evidence has been removed.
> 
> Can you reproduce the problem by installing from the latest test composes? Is
> it really creating a /etc/default/grub without speed? If so the anaconda log
> and program.log might be useful.

I can reproduce it using TC2.  I'll attach install.log and anaconda.program.log
 
> Just a thought ... are you using a "real" serial console where you specify the
> speed? Or is it some kind of virtual xen serial console where you don't specify
> any speed?

It's a virtual KVM console without a specified (AFAIK) speed.

Comment 9 Dave Allan 2011-10-25 18:10:16 UTC
Created attachment 530151 [details]
install log

Comment 10 Dave Allan 2011-10-25 18:11:28 UTC
Created attachment 530152 [details]
anaconda program log

Comment 11 Dave Allan 2011-10-25 18:14:36 UTC
BTW, I'm still running into BZ 743642 with TC2, so in order to get a bootable
system, I have to boot into rescue mode and install grub manually.  When I
first boot into rescue mode /boot/grub2/grub.cfg is a zero byte file.

Comment 12 Mads Kiilerich 2011-10-25 18:24:10 UTC
Ok, so it was a manual boot loader installation all the time?

How do /etc/default/grub look like?

The issue from comment 6 has been fixed in next anaconda build, but I wonder what trigged the error. How do /proc/cmdline look - especially when the installer has been booted?

Comment 13 Dave Allan 2011-10-25 18:57:17 UTC
So using the test package available in bug 736993 I was able to get the installer to run through and install grub correctly.  The error messages are still there, though.  Re-running the installer shows a command line of:

[    0.000000] Linux version 3.1.0-0.rc10.git0.1.fc16.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.6.1 20111003 (Red Hat 4.6.1-10) (GCC) ) #1 SMP Wed Oct 19 05:02:17 UTC 2011
[    0.000000] Command line: initrd=initrd.img serial console=ttyS0 updates=http://pjones.fedorapeople.org/serial-updates.img BOOT_IMAGE=vmlinuz

Comment 14 Dave Allan 2011-10-25 18:58:02 UTC
(In reply to comment #13)
> Re-running the installer shows a command line of:

I mean, I created a new VM and started another install, if that wasn't clear...

Comment 15 Mads Kiilerich 2011-10-25 19:08:02 UTC
How do /etc/default/grub look like?

Comment 16 Mads Kiilerich 2011-10-25 19:19:04 UTC
Ok, got it:

(In reply to comment #6)
> /usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py :
>             speed = "9600"
>             for opt in self.console_options.split(","):
>                 if opt.isdigit:
>                     speed = opt
>                     break
> 
>             command = "serial --unit=%s --speed=%s" % (unit, speed)

In your case console_options='' and it will thus loop through a list with an empty string and that string will be used as speed.

It will be fixed by http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=7ac1fd221759e1a095f33df235fdc1091051281e

Comment 17 Dave Allan 2011-10-25 19:20:19 UTC
Created attachment 530164 [details]
/etc/default/grub

Comment 18 Dave Allan 2011-10-25 19:21:49 UTC
(In reply to comment #16)

> It will be fixed by
> http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=7ac1fd221759e1a095f33df235fdc1091051281e

Any way I could try that out?

Comment 19 Mads Kiilerich 2011-10-25 19:37:29 UTC
(In reply to comment #18)
> Any way I could try that out?

I guess it will be included in the first f16 RC which in principle should be made today. Somebody in the qa team might know where to find something usable earlier than that.

Comment 20 Dave Allan 2011-10-25 19:46:16 UTC
Thanks, I'll try it out.

Comment 21 Adam Williamson 2011-10-25 20:11:44 UTC
Dave: can you reproduce this if you use the updates.img that fixes 743642?

Comment 22 Adam Williamson 2011-10-25 20:13:21 UTC
apologies, you already answered that. sorry.

Comment 23 Fedora Update System 2011-10-25 21:02:13 UTC
anaconda-16.23-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/anaconda-16.23-1.fc16

Comment 24 Adam Williamson 2011-10-28 18:11:14 UTC
tc3 should have the fix for this, so you can test with that:

http://dl.fedoraproject.org/pub/alt/stage/16.TC3/

please test and let us know if it's resolved. thanks!

(it should also fix the bigger 'bootloader install fails' bug, so serial console install should work OOTB now).

Comment 25 Adam Williamson 2011-10-28 19:18:47 UTC
Discussed at 2011-10-28 NTH review meeting, accepted as NTH as a visible installer bug which can't be fixed with an update and could theroetically cause some kind of serial install borkage. The fix was included in anaconda 16.23 and we're pulling that for sure anyway. We still need the verification requested in comment #24. thanks!

Comment 26 Dave Allan 2011-10-28 19:24:53 UTC
I tested the netinst image, the serial console install worked properly and the
errors are gone, so it's looking good.

Comment 27 Adam Williamson 2011-10-28 19:36:55 UTC
Thanks!

Comment 28 Adam Williamson 2011-11-03 01:49:12 UTC
Let's close, fixed anaconda has gone stable now.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


Note You need to log in before you can comment on or make changes to this bug.