[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Have my PA8800 back online...

Hi Dave,

On 12/04/2017 01:43 PM, John David Anglin wrote:
On 2017-12-04, at 6:51 AM, Frank Scheiner wrote:

But after installing v4.14.x and then trying to boot it, my rp3440 seemed to have locked up after the following messages:

[   28.618056] io scheduler deadline registered
[   28.618308] io scheduler cfq registered (default)
[   28.618481] io scheduler mq-deadline registered
[   28.623261] PDC Stable Storage facility v0.30
[   28.671368] STI GSC/PCI core graphics driver Version 0.9b
[   28.671984] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[   28.708902] 0000:e0:01.1: ttyS0 at MMIO 0xfffffffff4050000 (irq = 73, base_baud = 115200) is a 16550A
[   28.731145] 0000:e0:01.1: ttyS1 at MMIO 0xfffffffff4050010 (irq = 73, base_baud = 115200) is a 16550A
[   28.731499] console  ttyS1] enabled
[   28.732307] bootconsole [ttyB0] disabled

I believe you need to change console to ttyS0 with v4.14.x.

Yes that solved it (see the bottom part of my earlier mail :-)), but was unexpected, as in the past the console used by the iLO MP of the rp3440 was always ttyS1.

  Possibly, console argument is no longer needed
on command line.

I believe it is needed to configure the console in any case. Without "console=" argument palo will add what is configured the default for a system type:

from `/usr/share/doc/palo/README.gz`
1. HP machines can use either a serial or a graphics boot console.
       Palo now figures out which one you are using and adds the
       appropriate "console=" to the end of the boot command line. It is
       only added if you don't already have "console=" in your boot
       command line.

...(e.g. ttyS1 for rp3440 since [1]) and if you manually delete the console argument when interacting with IPL to really get rid of it, the console output stops after the kernel disables ttyB0:

[    0.001572] Console: colour dummy device 160x64
[    0.002947] console [tty0] enabled
[    0.003082] bootconsole [ttyB0] disabled

But interestingly the machine this time continued to boot and was reachable via network later on.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git/commit/?id=9bb40b5ab775a077fd847c6ff99462249cc3f426

You can probably access system via network after boot completes.

No, as mentioned earlier that didn't work out when the console was configured to ttyS1 by palo. I waited several minutes and the machine was not accessible via network in this case.

Not sure if console output on a serial port of an rp3440 or related machines needs to be "consumed" by a terminal to continue. But I've seen something similar on my rp2470 (with GSP), where I needed to hit the enter key multiple times to continue the boot process, each time another few messages would appear on my terminal, but no output and no progress if I I didn't hit the enter key. Systemd was already running at this time. Strange behaviour.

Make sure palo 1.99 is installed and you have run palo at least once to update palo config on disk.

Palo 1.99 is installed.


Reply to: