No help description when we press "h" in Petitboot Language Selection page

On OpenBMC, in a good case, i have observed that Petitboot request for the System Boot Options 4 times both for parameter 0x05 and 0x61 What is the rationale behind that, is there an inefficiency?

IPMI GET_SYS_BOOT_OPTIONS
IPMI Response:
0x000000: 00 01 05 80 0c 00 00 00 ........
IPMI Incoming: Seq 0x10, NetFn 0x00, CMD: 0x09
0x000000: 61 00 00 a..
IPMI GET_SYS_BOOT_OPTIONS
getHostNetworkData failed for get_sys_boot_options.
ERROR:[0xFF] handling NetFn:[0x0], Cmd:[0x9]
IPMI Response:
0x000000: ff 01 61 00 00 00 00 00 00 00 00 00 00 00 00 00 ..a.............
0x000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000030: 00 00 00 ...
IPMI Incoming: Seq 0x11, NetFn 0x00, CMD: 0x09
0x000000: 05 00 00 ...
IPMI GET_SYS_BOOT_OPTIONS
IPMI Response:
0x000000: 00 01 05 80 0c 00 00 00 ........
IPMI Incoming: Seq 0x12, NetFn 0x00, CMD: 0x09
0x000000: 61 00 00 a..
IPMI GET_SYS_BOOT_OPTIONS
getHostNetworkData failed for get_sys_boot_options.
ERROR:[0xFF] handling NetFn:[0x0], Cmd:[0x9]
IPMI Response:
0x000000: ff 01 61 00 00 00 00 00 00 00 00 00 00 00 00 00 ..a.............
0x000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000030: 00 00 00 ...
IPMI Incoming: Seq 0x13, NetFn 0x00, CMD: 0x09
0x000000: 05 00 00 ...
IPMI GET_SYS_BOOT_OPTIONS
IPMI Response:
0x000000: 00 01 05 80 0c 00 00 00 ........
IPMI Incoming: Seq 0x14, NetFn 0x00, CMD: 0x09
0x000000: 61 00 00 a..
IPMI GET_SYS_BOOT_OPTIONS
getHostNetworkData failed for get_sys_boot_options.
ERROR:[0xFF] handling NetFn:[0x0], Cmd:[0x9]
IPMI Response:
0x000000: ff 01 61 00 00 00 00 00 00 00 00 00 00 00 00 00 ..a.............
0x000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000030: 00 00 00 ...
IPMI Incoming: Seq 0x15, NetFn 0x00, CMD: 0x09
0x000000: 05 00 00 ...
IPMI GET_SYS_BOOT_OPTIONS
IPMI Response:
0x000000: 00 01 05 80 0c 00 00 00 ........
IPMI Incoming: Seq 0x16, NetFn 0x00, CMD: 0x09
0x000000: 61 00 00 a..
IPMI GET_SYS_BOOT_OPTIONS
getHostNetworkData failed for get_sys_boot_options.
ERROR:[0xFF] handling NetFn:[0x0], Cmd:[0x9]
IPMI Response:
0x000000: ff 01 61 00 00 00 00 00 00 00 00 00 00 00 00 00 ..a.............
0x000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x000030: 00 00 00

Being able to collapse boot options under their respective device header would help make the display more readable on machines with a large amount of boot options.

(Copied from BZ)

When building petitboot, I was able to successfully run ./configure, only to have the following happen when I try to run make:

  YACC     discover/grub2/grub2-parser.c
./ylwrap: line 176: yacc: command not found

I think the configure script should probably check for these?

I will probably get you a patch if I don't forget!

It would be really nice if Petitboot could boot from an ISO image itself rather than needing manual unpacking.
Initial support is inlcuded in an unmerged series (http://patchwork.ozlabs.org/patch/686304/) but some extra magic is needed to support the installer OS accessing the ISO again during installation (eg. via reserved memory, etc)

It would be helpful if we can add petitboot cmdline utilities to aid test frameworks

E:g:-
discover_nw
discover_disk

it can just return true or false based on the discovery status, it can be even be sub options to pb-discover also

Petitboot's settings screen relies on tools such as nvram to be present in order to persist settings. The UI should warn the user that these settings will not be saved when the required tool is not present.

I have "Any Disk" setup and autoboot set to 10, I think. The autoboot timer never fires and heads off into FreeBSD.

http://people.freebsd.org/sbruno/pb-sos.tar.gz

The system's BMC can usually be configured via ipmitool, eg network settings. We could expose these options in the UI instead of needing to drop to the shell.

Allow a HTTP proxy to be set or specified from within the Petitboot client

(Copied from BZ)

Noticed while editing command line for kernel over IPMI on garrison. can not go to start of line and then go forward character at a time.

IPMI Specification defines a number of "boot parameters" that can be set via Set System Boot Options command. Among those parameters are:

• 5: Boot flags
• 7: Boot initiator mailbox

The former is fully supported by Petitboot, while the latter isn't. The data contained in the "mailbox" is not specified except for the size and the first four data bytes. It is proposed to develop a specification for this mailbox to be used to communicate additional boot parameters from BMC to Petitboot beyond those settable via "Boot flags". Specifically, a UUID of the desired boot partition needs to be settable.

Support for that will then be added into OpenBMC.

Please refer to the attached picture

When petitboot (ver. 1.10.1) initiates loading of a chosen system, it clears the terminal and prints title with shell prompt:

Exiting petitboot. Type 'exit' to return.
You may run 'pb-sos' to gather diagnostic data
No password set, running as root. You may set a password in the System Configuration screen.
# 

That prompt is not interactive and it looks like the system hangs for 3-5 seconds and then start kexec.
This behavior might be misleading to the end-user.

In plugins page, the hotkeys "N", "G", "C", "I" would leaves the plugin page to "Option editor", "Status log", "System configuration", "System information" respectively.
Looks like the hotkey in plugin page are inherit from main page. Is it normal?

Another observation, after entering plugin page, the bottom line shows "Enter=install, e=details, x=exit, h=helpanguage, g=log, h=help". Seems there is not refresh the bottom line.

petitboot version : v1.6.3

Some way of having system specific configuration options, perhaps including crazy workarounds that are very platform specific (e.g. nvram settings, hostboot attribute overrides, etc)

A suggestion from a group that's been using some OpenPOWER machines: it'd be neat if network boot options that were x86 kernels didn't show up/showed up disabled on the OpenPOWER machines.

We found the timeout function in Petitboot would not count down if we plug in the network cable when system power on, and the auto-boot function seems no function, too. (ps. our system use PXE boot, no hard drive)

If option 210 (prepathprefix) is a valid URL with a port specified the port is missing when Petitboot uses that URL for discovery, eg:

[00:43:13] user_event_process: 139 bytes
[00:43:13] user_event dhcp event:
[00:43:13]      device: enP4p1s0f1
[00:43:13]      pxepathprefix => http://fs.ozlabs.ibm.com:80/~sam/
...
[00:43:13] Running command:
 exe:  /usr/bin/wget
 argv: '/usr/bin/wget' '-O' '/tmp/pb-CmMbP3' '--quiet' 'http://fs.ozlabs.ibm.com/~sam/pxelinux.cfg/01-98-be-94-83-00-97

Support all the LVM magic.

Platform: Firestone

Firmware Version:
PNOR: op-build tag V1.8
BMC: AMI's version 2.13.92578 of 03172016_Src_Release

Scenario

1. Console keyboard can’t work.
2. BMC KVM keyboard can’t work.
3. BMC SOL keyboard CAN work.
4. Plug again the USB keyboard. The keyboard will work.
5. Go to the OS. The keyboard will work.
6. Petitboot shell only get two USB Devices. Can't get keyboard.

 / # lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003

1. Show some errors message in Skiboot.

[   28.428725] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   28.738770] ehci-pci: EHCI PCI platform driver
[   28.898450] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   29.159950] ohci-pci: OHCI PCI platform driver
[   29.569686] xhci_hcd 0003:0d:00.0: xHCI Host Controller
[   29.737621] xhci_hcd 0003:0d:00.0: new USB bus registered, assigned bus number 1
[   29.827904] xhci_hcd 0003:0d:00.0: Using 64-bit DMA iommu bypass
[   30.013013] xhci_hcd 0003:0d:00.0: hcc params 0x0270f06d hci version 0x96 quirks 0x00000000
[   30.158136] hub 1-0:1.0: USB hub found
[   30.545330] hub 1-0:1.0: 4 ports detected
[   30.852700] xhci_hcd 0003:0d:00.0: xHCI Host Controller
[   31.044243] xhci_hcd 0003:0d:00.0: new USB bus registered, assigned bus number 2
**[   31.142863] usb usb1-port1: couldn't allocate usb_device**
**[   31.142877] usb usb1-port3: couldn't allocate usb_device**
[   31.587662] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[   32.018553] hub 2-0:1.0: USB hub found
[   32.067570] hub 2-0:1.0: 4 ports detected

How to reproduce

1. Use BMC KVM to operate Petitboot menu.
2. If keyboard can work, reboot system by KVM menu.
3. Go to step1, test again.

When connecting via IPMI/serial the user may be greeted with a blank screen. This is because Petitboot doesn't have a way of knowing if anyone is connected to the console and won't know to redraw the screen. Pressing a key often works but not always, for example if pressing 'Enter' in a screen where that has no affect. It would be good to try and recognise when a user connects or periodically redraw the screen.
An initial attempt was made at redrawing the screen but still needs some work: http://patchwork.ozlabs.org/patch/786475/

Hey there! Using a full linux system as a bootloader to enable advanced features and improve boot times is a really fascinating idea, therefore I have a question: can petitboot be used for booting a linux-based operating system on a normal x86_64 desktop computer?

I understand I might be missing something very essential here, as the project seems to be aimed at the enterprise sector, but it is still interesting.

Thanks!

Improve key handling in nc-widgets to allow horizontal movement between widgets.

(Copied from BZ)

While building under buildroot:

>>> petitboot 7460bbb60ff7070c6884b700fc6370cd58703c4b Gettextizing
Copying file config.rpath
Not copying intl/ directory.
Copying file po/Makefile.in.in
Copying file po/Makevars.template
Copying file po/Rules-quot
Copying file po/boldquot.sed
Copying file po/[email protected]
Copying file po/[email protected]
Copying file po/insert-header.sin
Copying file po/quot.sed
Copying file po/remove-potcdate.sin
Adding an entry to po/ChangeLog (backup is in po/ChangeLog~)
Copying file m4/gettext.m4
Copying file m4/iconv.m4
Copying file m4/lib-ld.m4
Copying file m4/lib-link.m4
Copying file m4/lib-prefix.m4
Copying file m4/nls.m4
Copying file m4/po.m4
Copying file m4/progtest.m4
Creating m4/ChangeLog
Updating configure.ac (backup is in configure.ac~)
Creating ChangeLog

Please update po/Makevars so that it defines all the variables mentioned
in po/Makevars.template.
You can then remove po/Makevars.template.

Please run 'aclocal -I m4' to regenerate the aclocal.m4 file.
You need aclocal from GNU automake 1.9 (or newer) to do this.
Then run 'autoconf' to regenerate the configure file.

You will also need config.guess and config.sub, which you can get from the CVS
of the 'config' project at http://savannah.gnu.org/. The commands to fetch them
are
$ wget 'http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess'
$ wget 'http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub'

You might also want to copy the convenience header file gettext.h
from the /home/joel/op-build/output/host/usr/share/gettext directory into your package.
It is a wrapper around <libintl.h> that implements the configure --disable-nls
option.

Feature request to support file:/// URLs for "Retrieve config from URL" to help people in the lap/doing things they probably shouldn't.

I'm trying to install OS to the Barreleye server but petitboot don't see any disks. During server initial startup i also don't see any disks discovered on megaraid controller.
In fact we have two ssd disks installed and disk LED is light.

Wondering if this is something known?

thanks in advance,

Witherspoon firmware version: witherspoon-IBM-OP9-v2.2-rc2-9.44_prod.pnor.squashfs.tar

After flashing this firmware, petitboot does not retain the boot order, it can retain the "network" device but nothing else. For example:

I added the following boot devices to the boot order.

Autoboot: ( ) Disabled
                 (*) Enabled

  Boot Order: (0) net: enP5p1s0f1 [mac: 08:94:ef:80:27:32]
                 (1) Any Disk device
                 (2) Any CD/DVD device

                 [ Add Device ]
                 [ Clear & Boot Any ]
                 [ Clear ]

I entered the petitboot shell and typed 'reboot'. After reboot, I checked the boot order I and see that other boot devices, except net were all removed from the boot order.

Autoboot: ( ) Disabled
                 (*) Enabled

  Boot Order: (0) net: enP5p1s0f1 [mac: 08:94:ef:80:27:32]

                 [ Add Device ]
                 [ Clear & Boot Any ]
                 [ Clear ]

It looks like a bug in petitboot since and it cannot keep boot devices like disk etc

Hello. Thanks for petitboot! I am using on my ASUS D16 mainboard. I have not been able to make petitboot find anything on my RAID devices. I installed through Debian 8.9 and have tried both RAID1 with a LVM on containing the / system. I have also tried a RAID1 partition with a ext4 /boot partition on. When installing it again and creating a /boot that is primary ext4 partition, it does find the partition and can boot from it. However, having RAID booting working would be nice. Is this a feature enhancement request, or is it a bug that it does not work for?

On large cluster installs, it is possible that the DHCP exchange for network boot images does not complete ahead of the Autoboot timeout. Admins are finding nodes that do not autoboot idling at the petitboot menu only needing to hit return to complete the boot process.

When a new network device is found, can we retrigger the autoboot timeout counter to make autoboot more robust in contentious network situations?

Future - depends on changes to Skiboot to make information accessible.

(Copied from BZ)

This is mostly implemented via http://patchwork.ozlabs.org/patch/862752/ etc, but there's still some work to do to make it work nicely, such as

• working out a solution for OpenBMC machines that can't talk to themselves over NCSI
• working out more dynamically what utility to update with
• better validation of update files
• allowing partial updates? (eg. just BOOTKERNEL)

Hi

We tried to modify "Timeout" for auto-boot setting in Petitboot System Configuration and choose "OK" on Zaius system.
After we "reboot" the system, the value we previously set in configuration page will not remain. It turns back to the default value.

We use this open-power/op-build@316265f to build zaius pnor image.

Petitboot doesn't support device-mapper RAID (ie. DM_RAID). Most of the other pieces are already in place so it would be nice to have this too.

After installing an ASMedia 1062 AHCI PCIe adapter on a S812L machine, SAS disks are not found anymore and neither the SATA disks connected on the new adapter. It seems there is some kind of conflict between the ahci and ipr driver, that usually results in crashes, right after PetitBoot tries to find bootable partitions, ending up with xmon being invoked. Unfortunately, I don't have the kernel messages for this case.

What was tried next was to remove IBM SAS RAID controller, leaving only the AHCI adapter. The system stops crashing, but the adapter doesn't work properly, not detecting any disks and keeps generating warnings, like the following:

[ 11.610769] EEH: Reset with hotplug activity
[ 12.675287] ata3: failed to resume link (SControl FFFFFFFF)
[ 12.675312] ata3: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF)
[ 13.175312] ------------[ cut here ]------------
[ 13.175316] WARNING: at drivers/ata/libata-core.c:6290
[ 13.175318] Modules linked in:
[ 13.175325] CPU: 72 PID: 540 Comm: eehd Tainted: G W 4.4.116-openpower1 #1
[ 13.175329] task: c0000007f4284420 ti: c0000007f4314000 task.ti: c0000007f4314000
[ 13.175332] NIP: c000000000424188 LR: c000000000424178 CTR: c00000000007f954
[ 13.175336] REGS: c0000007f43176f0 TRAP: 0700 Tainted: G W (4.4.116-openpower1)
[ 13.175338] MSR: 9000000000029033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 24008024 XER: 20000000
[ 13.175349] CFAR: c0000000005b2794 SOFTE: 1@
[ 13.175349] GPR00: c000000000424178 c0000007f4317970 c0000000008aab00 0000000000000001@
[ 13.175349] GPR04: 0000000000000001 00000000004fb63c 00000007fafe0000 0000000000000000@
[ 13.175349] GPR08: 0000000000000000 0000000000000001 0000000000000000 0000000000000003@
[ 13.175349] GPR12: 0000000022002088 c00000000fe4fc00 c0000000000721fc c0000007f44725c0@
[ 13.175349] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000@
[ 13.175349] GPR20: 0000000000000000 0000000000000000 0000000000000000 c0000000006fcd91@
[ 13.175349] GPR24: c0000000006fcdb2 000000005ba4f50f 00000000000e99d4 c0000007f1ed5a18@
[ 13.175349] GPR28: 0000000000010e00 0000000000000001 0000000000000000 c0000007f0808000@
[ 13.175386] NIP [c000000000424188] ata_host_detach+0x9c/0x13c
[ 13.175390] LR [c000000000424178] ata_host_detach+0x8c/0x13c
[ 13.175392] Call Trace:
[ 13.175396] [c0000007f4317970] [c000000000424178] ata_host_detach+0x8c/0x13c (unreliable)
[ 13.175402] [c0000007f43179c0] [c00000000020d0a8] pci_device_remove+0x50/0x90
[ 13.175407] [c0000007f43179f0] [c0000000003dd308] __device_release_driver+0xa8/0x130
[ 13.175412] [c0000007f4317a20] [c0000000003dd3c8] device_release_driver+0x38/0x4c
[ 13.175416] [c0000007f4317a50] [c000000000206d08] pci_stop_bus_device+0x48/0xa4
[ 13.175421] [c0000007f4317a90] [c000000000206e84] pci_stop_and_remove_bus_device+0x20/0x38
[ 13.175426] [c0000007f4317ac0] [c000000000027658] pcibios_remove_pci_devices+0x58/0x70
[ 13.175431] [c0000007f4317b00] [c0000000005adb80] eeh_reset_device+0x7c/0x1ec
[ 13.175435] [c0000007f4317bb0] [c0000000000226c0] eeh_handle_normal_event+0x188/0x408
[ 13.175439] [c0000007f4317c30] [c000000000022bc0] eeh_handle_event+0xac/0x2a8
[ 13.175443] [c0000007f4317cd0] [c000000000022eec] eeh_event_handler+0x130/0x150
[ 13.175448] [c0000007f4317d80] [c0000000000722f0] kthread+0xfc/0x108

Have a method for mounting devices over iSCSI

I've come into posession of two palmetto tyan machines for use with FreeBSD. I noted that the version of petiteboot on these things is dated 2014 and I'm seeing a lot of issues from the host o/s side talking to OPAL and whatnot.

Is there a decent-ish way of updating petiteboot that I can use from inside the petiteboot linux instance or is there a prebuilt way of updating it that I don't see lying around?

When booting from golden side of pnor, pop up some visual warning, maybe with help explaining it.

I upgraded a palmetto based system to the latest version of petitboot from an old 2014 version. The system doesn't see the kboot.conf style FAT partiions as valid boot devices any longer. Is this something that isn't enabled by default or is this a bug of some kind?

[ 0.000000] dt-cpu-ftrs: setup for ISA 2070
[ 0.000000] dt-cpu-ftrs: not enabling: transactional-memory (disabled or unsupported by kernel)
[ 0.000000] dt-cpu-ftrs: not enabling: subcore (unknown and unsupported by kernel)
[ 0.000000] dt-cpu-ftrs: final cpu/mmu features = 0x000000ef8f5db1a7 0x3c006001
[ 0.000000] hash-mmu: Page sizes from device-tree:
[ 0.000000] hash-mmu: base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0
[ 0.000000] hash-mmu: base_shift=12: shift=16, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=7
[ 0.000000] hash-mmu: base_shift=12: shift=24, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=56
[ 0.000000] hash-mmu: base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1
[ 0.000000] hash-mmu: base_shift=16: shift=24, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=8
[ 0.000000] hash-mmu: base_shift=20: shift=20, sllp=0x0130, avpnm=0x00000000, tlbiel=0, penc=2
[ 0.000000] hash-mmu: base_shift=24: shift=24, sllp=0x0100, avpnm=0x00000001, tlbiel=0, penc=0
[ 0.000000] hash-mmu: base_shift=34: shift=34, sllp=0x0120, avpnm=0x000007ff, tlbiel=0, penc=3
[ 0.000000] Page orders: linear mapping = 24, virtual = 16, io = 16, vmemmap = 24
[ 0.000000] Using 1TB segments
[ 0.000000] hash-mmu: Initializing hash mmu with SLB
[ 0.000000] Linux version 4.18.6-openpower1 (jenkins@hudson) (gcc version 6.4.0 (Buildroot 2018.05.2-00114-g1822255eab)) #2 SMP Fri Oct 5 11:48:17 UTC 2018
[ 0.000000] OPAL: Found non-mapped LPC bus on chip 0
[ 0.000000] Using PowerNV machine description
[ 0.000000] bootconsole [udbg0] enabled
[ 0.000000] CPU maps initialized for 8 threads per core
[ 0.000000] (thread shift is 3)
[ 0.000000] Allocated 3200 bytes for 32 pacas
[ 0.000000] -----------------------------------------------------
[ 0.000000] ppc64_pft_size = 0x0
[ 0.000000] phys_mem_size = 0x400000000
[ 0.000000] dcache_bsize = 0x80
[ 0.000000] icache_bsize = 0x80
[ 0.000000] cpu_features = 0x000000ef8f5db1a7
[ 0.000000] possible = 0x0000ffefcf5fb1a7
[ 0.000000] always = 0x00000003800081a1
[ 0.000000] cpu_user_features = 0xdc0065c2 0xae000000
[ 0.000000] mmu_features = 0x7c006001
[ 0.000000] firmware_features = 0x0000000010000000
[ 0.000000] htab_address = 0x(ptrval)
[ 0.000000] htab_hash_mask = 0x1ffff
[ 0.000000] -----------------------------------------------------
[ 0.000000] numa: NODE_DATA [mem 0x3ff522700-0x3ff52bfff]
[ 0.000000] rfi-flush: ori type flush available
[ 0.000000] rfi-flush: patched 7 locations (ori type flush)
[ 0.000000] barrier-nospec: using ORI speculation barrier
[ 0.000000] barrier-nospec: patched 391 locations
[ 0.000000] stf-barrier: hwsync barrier available
[ 0.000000] stf-barrier: patched 60 entry locations (hwsync barrier)
[ 0.000000] stf-barrier: patched 7 exit locations (hwsync barrier)
[ 0.000000] Initializing IODA2 PHB (/pciex@3fffe40000000)
[ 0.000000] PCI host bridge /pciex@3fffe40000000 (primary) ranges:
[ 0.000000] MEM 0x00003fe000000000..0x00003fe07ffeffff -> 0x0000000080000000
[ 0.000000] MEM 0x0000200000000000..0x000020ffffffffff -> 0x0000200000000000 (M64 #0..15)
[ 0.000000] Using M64 #15 as default window
[ 0.000000] 256 (255) PE's M32: 0x80000000 [segment=0x800000]
[ 0.000000] M64: 0x10000000000 [segment=0x100000000]
[ 0.000000] Allocated bitmap for 2040 MSIs (base IRQ 0x800)
[ 0.000000] Initializing IODA2 PHB (/pciex@3fffe40100000)
[ 0.000000] PCI host bridge /pciex@3fffe40100000 ranges:
[ 0.000000] MEM 0x00003fe080000000..0x00003fe0fffeffff -> 0x0000000080000000
[ 0.000000] MEM 0x0000210000000000..0x000021ffffffffff -> 0x0000210000000000 (M64 #0..15)
[ 0.000000] Using M64 #15 as default window
[ 0.000000] 256 (255) PE's M32: 0x80000000 [segment=0x800000]
[ 0.000000] M64: 0x10000000000 [segment=0x100000000]
[ 0.000000] Allocated bitmap for 2040 MSIs (base IRQ 0x1000)
[ 0.000000] Initializing IODA2 PHB (/pciex@3fffe40200000)
[ 0.000000] PCI host bridge /pciex@3fffe40200000 ranges:
[ 0.000000] MEM 0x00003fe100000000..0x00003fe17ffeffff -> 0x0000000080000000
[ 0.000000] MEM 0x0000220000000000..0x000022ffffffffff -> 0x0000220000000000 (M64 #0..15)
[ 0.000000] Using M64 #15 as default window
[ 0.000000] 256 (255) PE's M32: 0x80000000 [segment=0x800000]
[ 0.000000] M64: 0x10000000000 [segment=0x100000000]
[ 0.000000] Allocated bitmap for 2040 MSIs (base IRQ 0x1800)
[ 0.000000] OPAL nvram setup, 589824 bytes
[ 0.000000] Top of RAM: 0x400000000, Total RAM: 0x400000000
[ 0.000000] Memory hole size: 0MB
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x00000003ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x00000003ffffffff]
[ 0.000
[ 0.000000] percpu: Embedded 2 pages/cpu @(ptrval) s75928 r0 d55144 u131072
[ 0.000000] pcpu-alloc: s75928 r0 d55144 u131072 alloc=1*1048576
[ 0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 12 13 14 15
[ 0.000000] pcpu-alloc: [0] 16 17 18 19 20 21 22 23 [0] 24 25 26 27 28 29 30 31
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 261920
[ 0.000000] Policy zone: DMA
[ 0.000000] Kernel command line: console=tty0 console=hvc0 ipr.fast_reboot=1 quiet
[ 0.000000] Memory: 16651648K/16777216K available (4544K kernel code, 960K rwdata, 1344K rodata, 11200K init, 1606K bss, 125568K reserved, 0K cma-reserved)
[ 0.000000] random: get_random_u64 called from __kmem_cache_create+0x34/0x4a0 with crng_init=0
[ 0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=32, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU event tracing is enabled.
[ 0.000000] RCU restricting CPUs from NR_CPUS=2048 to nr_cpu_ids=32.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=32
[ 0.000000] NR_IRQS: 512, nr_irqs: 512, preallocated irqs: 16
[ 0.000000] ICS OPAL backend registered
[ 0.000000] time_init: decrementer frequency = 512.000000 MHz
[ 0.000000] time_init: processor frequency = 4024.000000 MHz
[ 0.000004] clocksource: timebase: mask: 0xffffffffffffffff max_cycles: 0x761537d007, max_idle_ns: 440795202126 ns
[ 0.000007] clocksource: timebase mult[1f40000] shift[24] registered
[ 0.000010] clockevent: decrementer mult[83126e98] shift[32] cpu[8]
[ 0.000284] Console: colour dummy device 80x25
[ 0.000291] console [tty0] enabled
[ 0.000294] console [hvc0] enabled
[ 0.000296] bootconsole [udbg0] disabled
[ 0.000357] pid_max: default: 32768 minimum: 301
[ 0.002036] Dentry cache hash table entries: 2097152 (order: 8, 16777216 bytes)
[ 0.002942] Inode-cache hash table entries: 1048576 (order: 7, 8388608 bytes)
[ 0.003007] Mount-cache hash table entries: 32768 (order: 2, 262144 bytes)
[ 0.003037] Mountpoint-cache hash table entries: 32768 (order: 2, 262144 bytes)
[ 0.003785] EEH: PowerNV platform initialized
[ 0.003789] POWER8 performance monitor hardware support registered
[ 0.003836] Hierarchical SRCU implementation.
[ 0.004323] smp: Bringing up secondary CPUs ...
[ 0.024172] smp: Brought up 1 node, 32 CPUs
[ 0.024175]
[ 0.035914] NET: Registered protocol family 16
[ 0.036062] EEH: No capable adapters found
[ 0.036934] cpuidle: using governor menu
[ 0.165791] PCI: Probing PCI hardware
[ 0.165894] PCI host bridge to bus 0000:00
[ 0.165904] pci_bus 0000:00: root bus resource [mem 0x3fe000000000-0x3fe07ffeffff] (bus address [0x80000000-0xfffeffff])
[ 0.165911] pci_bus 0000:00: root bus resource [mem 0x200000000000-0x20fdffffffff 64bit pref]
[ 0.165917] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.165924] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to ff
[ 0.165977] pci 0000:00:00.0: [1014:03dc] type 01 class 0x060400
[ 0.166200] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 0.172802] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 0.172861] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to ff
[ 0.172914] PCI host bridge to bus 0001:00
[ 0.172923] pci_bus 0001:00: root bus resource [mem 0x3fe080000000-0x3fe0fffeffff] (bus address [0x80000000-0xfffeffff])
[ 0.172929] pci_bus 0001:00: root bus resource [mem 0x210000000000-0x21fdffffffff 64bit pref]
[ 0.172934] pci_bus 0001:00: root bus resource [bus 00-ff]
[ 0.172940] pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to ff
[ 0.172979] pci 0001:00:00.0: [1014:03dc] type 01 class 0x060400
[ 0.173190] pci 0001:00:00.0: PME# supported from D0 D3hot D3cold
[ 0.176632] pci 0001:01:00.0: [10b5:8718] type 01 class 0x060400
[ 0.176713] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x0003ffff]
[ 0.176990] pci 0001:01:00.0: PME# supported from D0 D3hot D3cold
[ 0.180323] pci 0001:00:00.0: PCI bridge to [bus 01-07]
[ 0.180640] pci 0001:02:01.0: [10b5:8718] type 01 class 0x060400
[ 0.180995] pci 0001:02:01.0: PME# supported from D0 D3hot D3cold
[ 0.181259] pci 0001:02:02.0: [10b5:8718] type 01 class 0x060400
[ 0.181617] pci 0001:02:02.0: PME# supported from D0 D3hot D3cold
[ 0.181881] pci 0001:02:03.0: [10b5:8718] type 01 class 0x060400
[ 0.182244] pci 0001:02:03.0: PME# supported from D0 D3hot D3cold
[ 0.182511] pci 0001:02:04.0: [10b5:8718] type 01 class 0x060400
[ 0.182870] pci 0001:02:04.0: PME# supported from D0 D3hot D3cold
[ 0.185791] pci 0001:01:00.0: PCI bridge to [bus 02-07]
[ 0.186152] pci 0001:03:00.0: [1a03:1150] type 01 class 0x060400
[ 0.186296] pci 0001:03:00.0: enabling Extended Tags
[ 0.186471] pci 0001:03:00.0: supports D1 D2
[ 0.186476] pci 0001:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.189801] pci 0001:02:01.0: PCI bridge to [bus 03-04]
[ 0.189853] pci 0001:03:00.0: bridge configuration invalid ([bus 04-04]), reconfiguring
[ 0.189977] pci_bus 0001:04: extended config space not accessible
[ 0.190056] pci 0001:04:00.0: [1a03:2000] type 00 class 0x030000
[ 0.190101] pci 0001:04:00.0: reg 0x10: [mem 0x00000000-0x00ffffff]
[ 0.190123] pci 0001:04:00.0: reg 0x14: [mem 0x00000000-0x0001ffff]
[ 0.190145] pci 0001:04:00.0: reg 0x18: [io 0x0000-0x007f]
[ 0.190331] pci 0001:04:00.0: supports D1 D2
[ 0.190336] pci 0001:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.193645] pci 0001:03:00.0: PCI bridge to [bus 04]
[ 0.193698] pci_bus 0001:04: busn_res: [bus 04] end is updated to 04
[ 0.193861] pci 0001:05:00.0: [104c:8241] type 00 class 0x0c0330
[ 0.193931] pci 0001:05:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit]
[ 0.193964] pci 0001:05:00.0: reg 0x18: [mem 0x00000000-0x00001fff 64bit]
[ 0.194046] pci 0001:05:00.0: BAR2 [mem size 0x00002000 64bit]: requesting alignment to 0x10000
[ 0.194187] pci 0001:05:00.0: supports D1 D2
[ 0.194192] pci 0001:05:00.0: PME# supported from D0 D1 D2 D3hot
[ 0.197511] pci 0001:02:02.0: PCI bridge to [bus 05]
[ 0.197720] pci 0001:06:00.0: [14e4:1656] type 00 class 0x020000
[ 0.197799] pci 0001:06:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit pref]
[ 0.197833] pci 0001:06:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit pref]
[ 0.197866] pci 0001:06:00.0: reg 0x20: [mem 0x00000000-0x0000ffff 64bit pref]
[ 0.198120] pci 0001:06:00.0: PME# supported from D0 D3hot D3cold
[ 0.198339] pci 0001:06:00.1: [14e4:1656] type 00 class 0x020000
[ 0.198419] pci 0001:06:00.1: reg 0x10: [mem 0x00000000-0x0000ffff 64bit pref]
[ 0.198453] pci 0001:06:00.1: reg 0x18: [mem 0x00000000-0x0000ffff 64bit pref]
[ 0.198486] pci 0001:06:00.1: reg 0x20: [mem 0x00000000-0x0000ffff 64bit pref]
[ 0.198741] pci 0001:06:00.1: PME# supported from D0 D3hot D3cold
[ 0.202021] pci 0001:02:03.0: PCI bridge to [bus 06]
[ 0.202233] pci 0001:07:00.0: [1b4b:9235] type 00 class 0x010601
[ 0.202296] pci 0001:07:00.0: reg 0x10: [io 0x8000-0x8007]
[ 0.202322] pci 0001:07:00.0: reg 0x14: [io 0x8040-0x8043]
[ 0.202347] pci 0001:07:00.0: reg 0x18: [io 0x8100-0x8107]
[ 0.202373] pci 0001:07:00.0: reg 0x1c: [io 0x8140-0x8143]
[ 0.202398] pci 0001:07:00.0: reg 0x20: [io 0x800000-0x80001f]
[ 0.202424] pci 0001:07:00.0: reg 0x24: [mem 0x00900000-0x009007ff]
[ 0.202450] pci 0001:07:00.0: reg 0x30: [mem 0x3fe0d0000000-0x3fe0d000ffff pref]
[ 0.202485] pci 0001:07:00.0: BAR5 [mem size 0x00000800]: requesting alignment to 0x10000
[ 0.202606] pci 0001:07:00.0: PME# supported from D3hot
[ 0.205922] pci 0001:02:04.0: PCI bridge to [bus 07]
[ 0.206055] pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 07
[ 0.206113] PCI host bridge to bus 0002:00
[ 0.206121] pci_bus 0002:00: root bus resource [mem 0x3fe100000000-0x3fe17ffeffff] (bus address [0x80000000-0xfffeffff])
[ 0.206127] pci_bus 0002:00: root bus resource [mem 0x220000000000-0x22fdffffffff 64bit pref]
[ 0.206133] pci_bus 0002:00: root bus resource [bus 00-ff]
[ 0.206139] pci_bus 0002:00: busn_res: [bus 00-ff] end is updated to ff
[ 0.206178] pci 0002:00:00.0: [1014:03dc] type 01 class 0x060400
[ 0.206393] pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
[ 0.212983] pci 0002:00:00.0: PCI bridge to [bus 01-ff]
[ 0.213041] pci_bus 0002:00: busn_res: [bus 00-ff] end is updated to ff
[ 0.213076] pci 0000:00 : [PE# fe] Secondary bus 0 associated with PE#fe
[ 0.213457] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 0.213487] pci_bus 0000:00: resource 4 [mem 0x3fe000000000-0x3fe07ffeffff]
[ 0.213493] pci_bus 0000:00: resource 5 [mem 0x200000000000-0x20fdffffffff 64bit pref]
[ 0.213637] pci 0001:00:00.0: BAR 9: assigned [mem 0x210000000000-0x2100ffffffff 64bit pref]
[ 0.213644] pci 0001:00:00.0: BAR 8: assigned [mem 0x3fe080000000-0x3fe082ffffff]
[ 0.213650] pci 0001:00:00.0: BAR 7: no space for [io size 0x2000]
[ 0.213656] pci 0001:00:00.0: BAR 7: failed to assign [io size 0x2000]
[ 0.213665] pci 0001:01:00.0: BAR 9: assigned [mem 0x210000000000-0x2100ffffffff 64bit pref]
[ 0.213671] pci 0001:01:00.0: BAR 8: assigned [mem 0x3fe080000000-0x3fe0827fffff]
[ 0.213678] pci 0001:01:00.0: BAR 0: assigned [mem 0x3fe082800000-0x3fe08283ffff]
[ 0.213690] pci 0001:01:00.0: BAR 7: no space for [io size 0x2000]
[ 0.213695] pci 0001:01:00.0: BAR 7: failed to assign [io size 0x2000]
[ 0.213705] pci 0001:02:03.0: BAR 9: assigned [mem 0x210000000000-0x2100ffffffff 64bit pref]
[ 0.213712] pci 0001:02:01.0: BAR 8: assigned [mem 0x3fe080000000-0x3fe0817fffff]
[ 0.213718] pci 0001:02:02.0: BAR 8: assigned [mem 0x3fe081800000-0x3fe081ffffff]
[ 0.213725] pci 0001:02:04.0: BAR 8: assigned [mem 0x3fe082000000-0x3fe0827fffff]
[ 0.213730] pci 0001:02:01.0: BAR 7: no space for [io size 0x1000]
[ 0.213736] pci 0001:02:01.0: BAR 7: failed to assign [io size 0x1000]
[ 0.213741] pci 0001:02:04.0: BAR 7: no space for [io size 0x1000]
[ 0.213747] pci 0001:02:04.0: BAR 7: failed to assign [io size 0x1000]
[ 0.213754] pci 0001:03:00.0: BAR 8: assigned [mem 0x3fe080000000-0x3fe0817fffff]
[ 0.213760] pci 0001:03:00.0: BAR 7: no space for [io size 0x1000]
[ 0.213766] pci 0001:03:00.0: BAR 7: failed to assign [io size 0x1000]
[ 0.213774] pci 0001:04:00.0: BAR 0: assigned [mem 0x3fe080000000-0x3fe080ffffff]
[ 0.213787] pci 0001:04:00.0: BAR 1: assigned [mem 0x3fe081000000-0x3fe08101ffff]
[ 0.213799] pci 0001:04:00.0: BAR 2: no space for [io size 0x0080]
[ 0.213804] pci 0001:04:00.0: BAR 2: failed to assign [io size 0x0080]
[ 0.213811] pci 0001:00 : [PE# fe] Secondary bus 0 associated with PE#fe
[ 0.214193] pci 0001:04 : [PE# fd] Secondary bus 4..4 associated with PE#fd
[ 0.214574] pci 0001:04 : [PE# fd] Setting up 32-bit TCE table at 0..80000000
[ 0.227740] IOMMU table initialized, virtual merging enabled
[ 0.227746] pci 0001:04 : [PE# fd] Setting up window#0 0..7fffffff pg=1000
[ 0.227754] pci 0001:04 : [PE# fd] Enabling 64-bit DMA bypass
[ 0.227760] pci 0001:03:00.0: PCI bridge to [bus 04]
[ 0.227774] pci 0001:03:00.0: bridge window [mem 0x3fe080000000-0x3fe0817fffff]
[ 0.227797] pci 0001:03 : [PE# fc] Secondary bus 3 associated with PE#fc
[ 0.228175] pci 0001:02:01.0: PCI bridge to [bus 03-04]
[ 0.228189] pci 0001:02:01.0: bridge window [mem 0x3fe080000000-0x3fe0817fffff]
[ 0.228212] pci 0001:05:00.0: BAR 0: assigned [mem 0x3fe081800000-0x3fe08180ffff 64bit]
[ 0.228240] pci 0001:05:00.0: BAR 2: assigned [mem 0x3fe081810000-0x3fe081811fff 64bit]
[ 0.228269] pci 0001:05 : [PE# fb] Secondary bus 5 associated with PE#fb
[ 0.228649] pci 0001:05 : [PE# fb] Setting up 32-bit TCE table at 0..80000000
[ 0.241787] pci 0001:05 : [PE# fb] Setting up window#0 0..7fffffff pg=1000
[ 0.241793] pci 0001:05 : [PE# fb] Enabling 64-bit DMA bypass
[ 0.241799] pci 0001:02:02.0: PCI bridge to [bus 05]
[ 0.241813] pci 0001:02:02.0: bridge window [mem 0x3fe081800000-0x3fe081ffffff]
[ 0.241838] pci 0001:06:00.0: BAR 0: assigned [mem 0x210000000000-0x21000000ffff 64bit pref]
[ 0.241866] pci 0001:06:00.0: BAR 2: assigned [mem 0x210000010000-0x21000001ffff 64bit pref]
[ 0.241894] pci 0001:06:00.0: BAR 4: assigned [mem 0x210000020000-0x21000002ffff 64bit pref]
[ 0.241921] pci 0001:06:00.1: BAR 0: assigned [mem 0x210000030000-0x21000003ffff 64bit pref]
[ 0.241949] pci 0001:06:00.1: BAR 2: assigned [mem 0x210000040000-0x21000004ffff 64bit pref]
[ 0.241977] pci 0001:06:00.1: BAR 4: assigned [mem 0x210000050000-0x21000005ffff 64bit pref]
[ 0.242015] pci 0001:06 : [PE# 00] Secondary bus 6 associated with PE#0
[ 0.242398] pci 0001:06 : [PE# 00] Setting up 32-bit TCE table at 0..80000000
[ 0.255568] pci 0001:06 : [PE# 00] Setting up window#0 0..7fffffff pg=1000
[ 0.255574] pci 0001:06 : [PE# 00] Enabling 64-bit DMA bypass
[ 0.255580] pci 0001:02:03.0: PCI bridge to [bus 06]
[ 0.255600] pci 0001:02:03.0: bridge window [mem 0x210000000000-0x2100ffffffff 64bit pref]
[ 0.255619] pci 0001:07:00.0: BAR 5: assigned [mem 0x3fe082000000-0x3fe0820007ff]
[ 0.255632] pci 0001:07:00.0: BAR 6: assigned [mem 0x3fe082010000-0x3fe08201ffff pref]
[ 0.255639] pci 0001:07:00.0: BAR 4: no space for [io size 0x0020]
[ 0.255644] pci 0001:07:00.0: BAR 4: failed to assign [io size 0x0020]
[ 0.255650] pci 0001:07:00.0: BAR 0: no space for [io size 0x0008]
[ 0.255656] pci 0001:07:00.0: BAR 0: failed to assign [io size 0x0008]
[ 0.255661] pci 0001:07:00.0: BAR 2: no space for [io size 0x0008]
[ 0.255667] pci 0001:07:00.0: BAR 2: failed to assign [io size 0x0008]
[ 0.255672] pci 0001:07:00.0: BAR 1: no space for [io size 0x0004]
[ 0.255678] pci 0001:07:00.0: BAR 1: failed to assign [io size 0x0004]
[ 0.255683] pci 0001:07:00.0: BAR 3: no space for [io size 0x0004]
[ 0.255689] pci 0001:07:00.0: BAR 3: failed to assign [io size 0x0004]
[ 0.255698] pci 0001:07 : [PE# fa] Secondary bus 7 associated with PE#fa
[ 0.256078] pci 0001:07 : [PE# fa] Setting up 32-bit TCE table at 0..80000000
[ 0.269235] pci 0001:07 : [PE# fa] Settin
[ 0.269240] pci 0001:07 : [PE# fa] Enabling 64-bit DMA bypass
[ 0.269246] pci 0001:02:04.0: PCI bridge to [bus 07]
[ 0.269260] pci 0001:02:04.0: bridge window [mem 0x3fe082000000-0x3fe0827fffff]
[ 0.269285] pci 0001:02 : [PE# f9] Secondary bus 2 associated with PE#f9
[ 0.269665] pci 0001:01:00.0: PCI bridge to [bus 02-07]
[ 0.269678] pci 0001:01:00.0: bridge window [mem 0x3fe080000000-0x3fe0ffefffff]
[ 0.269689] pci 0001:01:00.0: bridge window [mem 0x210000000000-0x21fdfff0ffff 64bit pref]
[ 0.269708] pci 0001:01 : [PE# f8] Secondary bus 1 associated with PE#f8
[ 0.270087] pci 0001:00:00.0: PCI bridge to [bus 01-07]
[ 0.270102] pci 0001:00:00.0: bridge window [mem 0x3fe080000000-0x3fe0ffefffff]
[ 0.270113] pci 0001:00:00.0: bridge window [mem 0x210000000000-0x21fdfff0ffff 64bit pref]
[ 0.270129] pci_bus 0001:00: Some PCI device resources are unassigned, try booting with pci=realloc
[ 0.270137] pci_bus 0001:00: resource 4 [mem 0x3fe080000000-0x3fe0fffeffff]
[ 0.270143] pci_bus 0001:00: resource 5 [mem 0x210000000000-0x21fdffffffff 64bit pref]
[ 0.270149] pci_bus 0001:01: resource 1 [mem 0x3fe080000000-0x3fe0ffefffff]
[ 0.270155] pci_bus 0001:01: resource 2 [mem 0x210000000000-0x21fdfff0ffff 64bit pref]
[ 0.270161] pci_bus 0001:02: resource 1 [mem 0x3fe080000000-0x3fe0ffefffff]
[ 0.270167] pci_bus 0001:02: resource 2 [mem 0x210000000000-0x21fdfff0ffff 64bit pref]
[ 0.270173] pci_bus 0001:03: resource 1 [mem 0x3fe080000000-0x3fe0817fffff]
[ 0.270179] pci_bus 0001:04: resource 1 [mem 0x3fe080000000-0x3fe0817fffff]
[ 0.270185] pci_bus 0001:05: resource 1 [mem 0x3fe081800000-0x3fe081ffffff]
[ 0.270192] pci_bus 0001:06: resource 2 [mem 0x210000000000-0x2100ffffffff 64bit pref]
[ 0.270197] pci_bus 0001:07: resource 1 [mem 0x3fe082000000-0x3fe0827fffff]
[ 0.270227] pci 0002:00 : [PE# fe] Secondary bus 0 associated with PE#fe
[ 0.270604] pci 0002:00:00.0: PCI bridge to [bus 01-ff]
[ 0.270634] pci_bus 0002:00: resource 4 [mem 0x3fe100000000-0x3fe17ffeffff]
[ 0.270640] pci_bus 0002:00: resource 5 [mem 0x220000000000-0x22fdffffffff 64bit pref]
[ 0.271750] PCI: Probing PCI hardware done
[ 0.274301] powernv-rng: Registering arch random hook.
[ 0.276188] pci 0001:04:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[ 0.276191] pci 0001:04:00.0: vgaarb: bridge control possible
[ 0.276195] pci 0001:04:00.0: vgaarb: setting as boot device (VGA legacy resources not available)
[ 0.276195] vgaarb: loaded
[ 0.276264] SCSI subsystem initialized
[ 0.276281] libata version 3.00 loaded.
[ 0.276328] pps_core: LinuxPPS API ver. 1 registered
[ 0.276329] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [email protected]
[ 0.276505] clocksource: Switched to clocksource timebase
[ 0.277537] NET: Registered protocol family 2
[ 0.277650] tcp_listen_portaddr_hash hash table entries: 8192 (order: 1, 131072 bytes)
[ 0.277672] TCP established hash table entries: 131072 (order: 4, 1048576 bytes)
[ 0.277919] TCP bind hash table entries: 65536 (order: 4, 1048576 bytes)
[ 0.278043] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.278077] UDP hash table entries: 8192 (order: 2, 262144 bytes)
[ 0.278110] UDP-Lite hash table entries: 8192 (order: 2, 262144 bytes)
[ 0.278195] NET: Registered protocol family 1
[ 0.278223] pci 0001:00:00.0: enabling device (0145 -> 0147)
[ 0.278228] pci 0001:01:00.0: enabling device (0545 -> 0547)
[ 0.278234] pci 0001:02:02.0: enabling device (0545 -> 0547)
[ 0.278240] pci 0001:05:00.0: enabling device (0140 -> 0142)
[ 0.278267] PCI: CLS 0 bytes, default 128
[ 1.777627] random: fast init done
[ 1.777859] Initialise system trusted keyrings
[ 1.777887] workingset: timestamp_bits=54 max_order=18 bucket_order=0
[ 1.779680] Key type asymmetric registered
[ 1.779681] Asymmetric key parser 'x509' registered
[ 1.779711] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 1.779713] io scheduler noop registered
[ 1.779752] io scheduler cfq registered (default)
[ 1.779754] io scheduler mq-deadline registered
[ 1.779755] io scheduler kyber registered
[ 1.779972] ipmi message handler version 39.2
[ 1.779974] ipmi device interface
[ 1.779995] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
[ 1.783043] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x000000, prod_id: 0xaabb, dev_id: 0x20)
[ 1.852068] IPMI Watchdog: driver initialized
[ 1.860100] hvc0: raw protocol on /ibm,opal/consoles/serial@0 (boot console)
[ 1.860104] hvc0: No interrupts property, using OPAL event
[ 1.860276] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 1.860461] powernv_rng: Registered powernv hwrng.
[ 1.861770] brd: module loaded
[ 1.862674] loop: module loaded
[ 1.862728] libphy: Fixed MDIO Bus: probed
[ 1.862823] i2c /dev entries driver
[ 1.862836] powernv-cpufreq: cpufreq pstate min 0xffffffbc nominal 0xfffffff7 max 0x0
[ 1.862838] powernv-cpufreq: Workload Optimized Frequency is disabled in the platform
[ 1.863378] powernv_idle_driver registered
[ 1.863626] ipip: IPv4 and MPLS over IPv4 tunneling driver
[ 1.864018] NET: Registered protocol family 10
[ 1.864337] Segment Routing with IPv6
[ 1.864351] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 1.864453] NET: Registered protocol family 17
[ 1.864459] Key type dns_resolver registered
[ 1.864487] drmem: No dynamic reconfiguration memory found
[ 1.864806] Loading compiled-in X.509 certificates
[ 1.869765] Loaded X.509 cert 'Build time autogenerated kernel key: 915799b5ac56586115140435be8a4f6b173ba254'
[ 1.873941] Key type encrypted registered
[ 1.873996] hctosys: unable to open rtc device (rtc0)
[ 1.874959] Freeing unused kernel memory: 11200K
[ 2.172525] udevd[1369]: starting version 3.2.5
[ 2.172737] random: udevd: uninitialized urandom read (16 bytes read)
[ 2.172779] random: udevd: uninitialized urandom read (16 bytes read)
[ 2.172818] random: udevd: uninitialized urandom read (16 bytes read)
[ 2.175921] udevd[1370]: starting eudev-3.2.5
[ 2.198685] PTP clock support registered
[ 2.204344] tg3.c:v3.137 (May 11, 2014)
[ 2.204362] pci 0001:02:03.0: enabling device (0545 -> 0547)
[ 2.204374] tg3 0001:06:00.0: enabling device (0140 -> 0142)
[ 2.204670] ahci 0001:07:00.0: version 3.0
[ 2.204679] pci 0001:02:04.0: enabling device (0545 -> 0547)
[ 2.204687] ahci 0001:07:00.0: enabling device (0141 -> 0143)
[ 2.204762] ahci 0001:07:00.0: Using 64-bit DMA iommu bypass
[ 2.211240] usbcore: registered new interface driver usbfs
[ 2.211260] usbcore: registered new interface driver hub
[ 2.211424] usbcore: registered new device driver usb
[ 2.214894] ahci 0001:07:00.0: AHCI 0001.0000 32 slots 4 ports 6 Gbps 0xf impl SATA mode
[ 2.214911] ahci 0001:07:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[ 2.215958] scsi host0: ahci
[ 2.216270] scsi host1: ahci
[ 2.216512] scsi host2: ahci
[ 2.216796] scsi host3: ahci
[ 2.216920] ata1: SATA max UDMA/133 abar m2048@0x3fe082000000 port 0x3fe082000100 irq 505
[ 2.216925] ata2: SATA max UDMA/133 abar m2048@0x3fe082000000 port 0x3fe082000180 irq 505
[ 2.216930] ata3: SATA max UDMA/133 abar m2048@0x3fe082000000 port 0x3fe082000200 irq 505
[ 2.216935] ata4: SATA max UDMA/133 abar m2048@0x3fe082000000 port 0x3fe082000280 irq 505
[ 2.220323] xhci_hcd 0001:05:00.0: xHCI Host Controller
[ 2.220334] xhci_hcd 0001:05:00.0: new USB bus registered, assigned bus number 1
[ 2.220411] xhci_hcd 0001:05:00.0: Using 64-bit DMA iommu bypass
[ 2.220471] xhci_hcd 0001:05:00.0: hcc params 0x0270f06d hci version 0x96 quirks 0x0000000004000000
[ 2.221005] hub 1-0:1.0: USB hub found
[ 2.221022] hub 1-0:1.0: 4 ports detected
[ 2.221196] xhci_hcd 0001:05:00.0: xHCI Host Controller
[ 2.221201] xhci_hcd 0001:05:00.0: new USB bus registered, assigned bus number 2
[ 2.221205] xhci_hcd 0001:05:00.0: Host supports USB 3.0 SuperSpeed
[ 2.221233] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.221370] hub 2-0:1.0: USB hub found
[ 2.221380] hub 2-0:1.0: 4 ports detected
[ 2.226589] rtc-opal opal-rtc: rtc core: registered rtc-opal as rtc0
[ 2.231586] pci 0001:02:01.0: enabling device (0545 -> 0547)
[ 2.231601] pci 0001:03:00.0: enabling device (0145 -> 0147)
[ 2.231610] ast 0001:04:00.0: enabling device (0140 -> 0142)
[ 2.231668] [drm] platform has no IO space, trying MMIO
[ 2.231672] [drm] VGA not enabled on entry, requesting chip POST
[ 2.231682] [drm] Using device-tree for configuration
[ 2.231683] [drm] AST 2400 detected
[ 2.231687] [drm] Analog VGA only
[ 2.231716] [drm] dram MCLK=408 Mhz type=7 bus_width=16 size=01000000
[ 2.231786] [TTM] Zone kernel: Available graphics memory: 8331424 kiB
[ 2.231788] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
[ 2.231789] [TTM] Initializing pool allocator
[ 2.236485] tg3 0001:06:00.0: Using 64-bit DMA iommu bypass
[ 2.236748] tg3 0001:06:00.0 eth0: Tigon3 [partno(BCM95718) rev 5717100] (PCI Express) MAC address a0:42:3f:28:47:69
[ 2.236751] tg3 0001:06:00.0 eth0: attached PHY is 5718C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 2.236754] tg3 0001:06:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 2.236756] tg3 0001:06:00.0 eth0: dma_rwctrl[00000000] dma_mask[64-bit]
[ 2.237449] tg3 0001:06:00.1: enabling device (0140 -> 0142)
[ 2.261679] at24 0-0052: 256 byte 24c02 EEPROM, writable, 1 bytes/write
[ 2.262115] at24 0-0053: 256 byte 24c02 EEPROM, writable, 1 bytes/write
[ 2.262524] at24 0-0054: 256 byte 24c02 EEPROM, writable, 1 bytes/write
[ 2.262927] at24 0-0055: 256 byte 24c02 EEPROM, writable, 1 bytes/write
[ 2.263030] at24 1-0050: 16384 byte 24c128 EEPROM, writable, 1 bytes/write
[ 2.263132] at24 1-0051: 16384 byte 24c128 EEPROM, writable, 1 bytes/write
[ 2.263236] at24 2-0050: 16384 byte 24c128 EEPROM, writable, 1 bytes/write
[ 2.263335] at24 2-0051: 16384 byte 24c128 EEPROM, writable, 1 bytes/write
[ 2.263508] at24 3-0050: 16384 byte 24c128 EEPROM, writable, 1 bytes/write
[ 2.363447] Console: switching to colour frame buffer device 128x48
[ 2.428138] ast 0001:04:00.0: fb0: astdrmfb frame buffer device
[ 2.433529] tg3 0001:06:00.1: Using 64-bit DMA iommu bypass
[ 2.433693] tg3 0001:06:00.1 eth1: Tigon3 [partno(BCM95718) rev 5717100] (PCI Express) MAC address a0:42:3f:28:47:6a
[ 2.433695] tg3 0001:06:00.1 eth1: attached PHY is 5718C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[ 2.433697] tg3 0001:06:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1]
[ 2.433698] tg3 0001:06:00.1 eth1: dma_rwctrl[00000000] dma_mask[64-bit]
[ 2.434686] tg3 0001:06:00.0 enP1p6s0f0: renamed from eth0
[ 2.476517] [drm] Initialized ast 0.1.0 20120228 for 0001:04:00.0 on minor 0
[ 2.546736] tg3 0001:06:00.1 enP1p6s0f1: renamed from eth1
[ 2.686515] usb 1-3: new high-speed USB device number 2 using xhci_hcd
[ 2.716520] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.716540] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.717724] ata4.00: ATA-9: ST1000NM0033-9ZM173, SN04, max UDMA/133
[ 2.717727] ata4.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2.717777] ata3.00: ATA-9: ST1000NM0033-9ZM173, SN04, max UDMA/133
[ 2.717780] ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2.718848] ata4.00: configured for UDMA/133
[ 2.718901] ata3.00: configured for UDMA/133
[ 2.726523] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.726540] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.727718] ata2.00: ATA-9: ST1000NM0033-9ZM173, SN04, max UDMA/133
[ 2.727720] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2.727729] ata1.00: ATA-9: ST1000NM0033-9ZM173, SN04, max UDMA/133
[ 2.727732] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[ 2.728827] ata2.00: configured for UDMA/133
[ 2.728845] ata1.00: configured for UDMA/133
[ 2.728973] scsi 0:0:0:0: Direct-Access ATA ST1000NM0033-9ZM SN04 PQ: 0 ANSI: 5
[ 2.729278] scsi 1:0:0:0: Direct-Access ATA ST1000NM0033-9ZM SN04 PQ: 0 ANSI: 5
[ 2.729606] scsi 2:0:0:0: Direct-Access ATA ST1000NM0033-9ZM SN04 PQ: 0 ANSI: 5
[ 2.729846] scsi 3:0:0:0: Direct-Access ATA ST1000NM0033-9ZM SN04 PQ: 0 ANSI: 5
[ 2.733612] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.733656] scsi 1:0:0:0: Attached scsi generic sg1 type 0
[ 2.733700] scsi 2:0:0:0: Attached scsi generic sg2 type 0
[ 2.733742] scsi 3:0:0:0: Attached scsi generic sg3 type 0
[ 2.737779] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 2.737804] sd 0:0:0:0: [sda] Write Protect is off
[ 2.737809] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.737851] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.737922] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 2.737951] sd 1:0:0:0: [sdb] Write Protect is off
[ 2.737958] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.737993] sd 2:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 2.738007] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.738019] sd 2:0:0:0: [sdc] Write Protect is off
[ 2.738025] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 2.738051] sd 3:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 2.738074] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.738076] sd 3:0:0:0: [sdd] Write Protect is off
[ 2.738081] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 2.738118] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.771521] sda: sda1 sda2 sda3
[ 2.771968] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 2.772745] sdb: sdb1 sdb2 sdb3
[ 2.773134] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 2.773519] sdd: sdd1 sdd2 sdd3
[ 2.773902] sd 3:0:0:0: [sdd] Attached SCSI removable disk
[ 2.775473] sdc: sdc1 sdc2 sdc3
[ 2.775883] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[ 2.894112] hub 1-3:1.0: USB hub found
[ 2.894468] hub 1-3:1.0: 5 ports detected
[ 2.994458] IPv6: ADDRCONF(NETDEV_UP): enP1p6s0f0: link is not ready
[ 2.995678] random: crng init done
[ 2.995681] random: 5 urandom warning(s) missed due to ratelimiting
[ 3.236509] usb 1-3.1: new high-speed USB device number 3 using xhci_hcd
[ 3.247393] IPv6: ADDRCONF(NETDEV_UP): enP1p6s0f1: link is not ready
[ 3.259493] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: [email protected]
[ 3.395732] usb-storage 1-3.1:1.0: USB Mass Storage device detected
[ 3.395842] scsi host4: usb-storage 1-3.1:1.0
[ 3.395910] usbcore: registered new interface driver usb-storage
[ 3.443083] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.443086] device-mapper: ioctl: error adding target to table
[ 3.452572] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.452575] device-mapper: ioctl: error adding target to table
[ 3.455631] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.455633] device-mapper: ioctl: error adding target to table
[ 3.458272] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.458273] device-mapper: ioctl: error adding target to table
[ 3.458913] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.458915] device-mapper: ioctl: error adding target to table
[ 3.461475] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.461476] device-mapper: ioctl: error adding target to table
[ 3.463884] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.463885] device-mapper: ioctl: error adding target to table
[ 3.465898] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.465901] device-mapper: ioctl: error adding target to table
[ 3.468475] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.468477] device-mapper: ioctl: error adding target to table
[ 3.471060] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.471062] device-mapper: ioctl: error adding target to table
[ 3.473706] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.473708] device-mapper: ioctl: error adding target to table
[ 3.474379] device-mapper: table: 254:12: linear: Device lookup failed
[ 3.474381] device-mapper: ioctl: error adding target to table
[ 3.526512] usb 1-3.3: new high-speed USB device number 4 using xhci_hcd
[ 3.691246] usb-storage 1-3.3:1.0: USB Mass Storage device detected
[ 3.691341] scsi host5: usb-storage 1-3.3:1.0
[ 3.806503] usb 1-3.4: new low-speed USB device number 5 using xhci_hcd
[ 4.019196] usbcore: registered new interface driver usbhid
[ 4.019198] usbhid: USB HID core driver
[ 4.021170] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:02.0/0001:05:00.0/usb1/1-3/1-3.4/1-3.4:1.0/0003:046B:FF10.0001/input/input0
[ 4.021215] hid-generic 0003:046B:FF10.0001: input: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0001:05:00.0-3.4/input0
[ 4.021330] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:02.0/0001:05:00.0/usb1/1-3/1-3.4/1-3.4:1.1/0003:046B:FF10.0002/input/input1
[ 4.021363] hid-generic 0003:046B:FF10.0002: input: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0001:05:00.0-3.4/input1
[ 4.397492] scsi 4:0:0:0: CD-ROM AMI Virtual CDROM0 1.00 PQ: 0 ANSI: 0 CCS
[ 4.397684] scsi 4:0:0:0: Attached scsi generic sg4 type 5
[ 4.405848] sr 4:0:0:0: [sr0] scsi-1 drive
[ 4.405850] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 4.405958] sr 4:0:0:0: Attached scsi CD-ROM sr0
[ 4.717487] scsi 5:0:0:0: Direct-Access AMI Virtual HDisk0 1.00 PQ: 0 ANSI: 0 CCS
[ 4.718230] scsi 5:0:0:1: Direct-Access AMI Virtual HDisk1 1.00 PQ: 0 ANSI: 0 CCS
[ 4.718433] sd 5:0:0:0: Attached scsi generic sg5 type 0
[ 4.718599] sd 5:0:0:1: Attached scsi generic sg6 type 0
[ 4.722100] sd 5:0:0:0: [sde] Attached SCSI removable disk
[ 4.742348] sd 5:0:0:1: [sdf] Attached SCSI removable disk
[ 6.372277] tg3 0001:06:00.0 enP1p6s0f0: Link is up at 1000 Mbps, full duplex
[ 6.372283] tg3 0001:06:00.0 enP1p6s0f0: Flow control is on for TX and on for RX
[ 6.372288] tg3 0001:06:00.0 enP1p6s0f0: EEE is disabled
[ 6.372305] IPv6: ADDRCONF(NETDEV_CHANGE): enP1p6s0f0: link becomes ready
[ 6.641837] tg3 0001:06:00.1 enP1p6s0f1: Link is up at 1000 Mbps, full duplex
[ 6.641844] tg3 0001:06:00.1 enP1p6s0f1: Flow control is on for TX and on for RX
[ 6.641847] tg3 0001:06:00.1 enP1p6s0f1: EEE is disabled
[ 6.641862] IPv6: ADDRCONF(NETDEV_CHANGE): enP1p6s0f1: link becomes ready
[ 185.886513] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 185.888678] ata1.00: configured for UDMA/133
[ 186.386513] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 186.388733] ata2.00: configured for UDMA/133
[ 186.886506] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 186.888718] ata3.00: configured for UDMA/133
[ 187.386507] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 187.388735] ata4.00: configured for UDMA/133
[ 188.113351] IPv6: ADDRCONF(NETDEV_UP): enP1p6s0f0: link is not ready
[ 188.117289] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.117291] device-mapper: ioctl: error adding target to table
[ 188.118333] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.118334] device-mapper: ioctl: error adding target to table
[ 188.121479] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.121481] device-mapper: ioctl: error adding target to table
[ 188.127891] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.127893] device-mapper: ioctl: error adding target to table
[ 188.129097] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.129099] device-mapper: ioctl: error adding target to table
[ 188.132312] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.132315] device-mapper: ioctl: error adding target to table
[ 188.139205] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.139207] device-mapper: ioctl: error adding target to table
[ 188.140072] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.140073] device-mapper: ioctl: error adding target to table
[ 188.142725] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.142727] device-mapper: ioctl: error adding target to table
[ 188.147913] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.147915] device-mapper: ioctl: error adding target to table
[ 188.148643] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.148645] device-mapper: ioctl: error adding target to table
[ 188.151119] device-mapper: table: 254:12: linear: Device lookup failed
[ 188.151120] device-mapper: ioctl: error adding target to table
[ 191.491208] tg3 0001:06:00.0 enP1p6s0f0: Link is up at 1000 Mbps, full duplex
[ 191.491215] tg3 0001:06:00.0 enP1p6s0f0: Flow control is on for TX and on for RX
[ 191.491220] tg3 0001:06:00.0 enP1p6s0f0: EEE is disabled
[ 191.491234] IPv6: ADDRCONF(NETDEV_CHANGE): enP1p6s0f0: link becomes ready
[ 528.206509] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 528.208737] ata1.00: configured for UDMA/133
[ 528.706512] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 528.708705] ata2.00: configured for UDMA/133
[ 529.206507] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 529.208652] ata3.00: configured for UDMA/133
[ 529.706513] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 529.708724] ata4.00: configured for UDMA/133
[ 530.209173] IPv6: ADDRCONF(NETDEV_UP): enP1p6s0f0: link is not ready
[ 530.212955] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.212958] device-mapper: ioctl: error adding target to table
[ 530.214217] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.214220] device-mapper: ioctl: error adding target to table
[ 530.217544] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.217546] device-mapper: ioctl: error adding target to table
[ 530.223007] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.223010] device-mapper: ioctl: error adding target to table
[ 530.223967] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.223968] device-mapper: ioctl: error adding target to table
[ 530.226864] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.226866] device-mapper: ioctl: error adding target to table
[ 530.233091] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.233094] device-mapper: ioctl: error adding target to table
[ 530.234076] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.234078] device-mapper: ioctl: error adding target to table
[ 530.237244] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.237246] device-mapper: ioctl: error adding target to table
[ 530.243572] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.243575] device-mapper: ioctl: error adding target to table
[ 530.244291] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.244292] device-mapper: ioctl: error adding target to table
[ 530.246588] device-mapper: table: 254:12: linear: Device lookup failed
[ 530.246590] device-mapper: ioctl: error adding target to table
[ 533.685341] tg3 0001:06:00.0 enP1p6s0f0: Link is up at 1000 Mbps, full duplex
[ 533.685348] tg3 0001:06:00.0 enP1p6s0f0: Flow control is on for TX and on for RX
[ 533.685354] tg3 0001:06:00.0 enP1p6s0f0: EEE is disabled
[ 533.685369] IPv6: ADDRCONF(NETDEV_CHANGE): enP1p6s0f0: link becomes ready
[ 688.206510] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 688.208725] ata1.00: configured for UDMA/133
[ 688.706514] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 688.708727] ata2.00: configured for UDMA/133
[ 689.206507] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 689.208704] ata3.00: configured for UDMA/133
[ 689.706512] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 689.708730] ata4.00: configured for UDMA/133
[ 690.205949] IPv6: ADDRCONF(NETDEV_UP): enP1p6s0f0: link is not ready
[ 690.210179] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.210182] device-mapper: ioctl: error adding target to table
[ 690.211241] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.211244] device-mapper: ioctl: error adding target to table
[ 690.214641] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.214646] device-mapper: ioctl: error adding target to table
[ 690.222445] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.222448] device-mapper: ioctl: error adding target to table
[ 690.223601] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.223603] device-mapper: ioctl: error adding target to table
[ 690.226803] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.226805] device-mapper: ioctl: error adding target to table
[ 690.233160] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.233162] device-mapper: ioctl: error adding target to table
[ 690.233997] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.233998] device-mapper: ioctl: error adding target to table
[ 690.236478] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.236480] device-mapper: ioctl: error adding target to table
[ 690.243208] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.243210] device-mapper: ioctl: error adding target to table
[ 690.244173] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.244174] device-mapper: ioctl: error adding target to table
[ 690.246669] device-mapper: table: 254:12: linear: Device lookup failed
[ 690.246671] device-mapper: ioctl: error adding target to table
[ 693.682265] tg3 0001:06:00.0 enP1p6s0f0: Link is up at 1000 Mbps, full duplex
[ 693.682272] tg3 0001:06:00.0 enP1p6s0f0: Flow control is on for TX and on for RX
[ 693.682277] tg3 0001:06:00.0 enP1p6s0f0: EEE is disabled

A Palmetto system on our network started doing this on Jan 23rd:

palm7-p1 is sending "Solicit message"s and then ignoring the DHCPv6 reply and sending the request again many times a second
where "may times a second" equates to ~10000 in 30 seconds !

Versions:

• petitboot-1.9.0
• linux-4.18.3-openpower1-paea9c85
• open-power-palmetto-c5daff7-dirty

If manually stopped pb-discover doesn't properly destroy any snapshot devices created while running. This causes the next pb-discover to be run to get confused and fail to mount the snapshots (because it doesn't recognise them) or the disks (because they're busy).

For example:

Error executing dm-task
Error creating linear base
Error creating snapshot devices for sda2
mounting device /dev/sda2 read-only
couldn't mount device /dev/sda2: mount failed: Device or resource busy

We have a power8 powerNV system showing bug 1616949 and wanted to basically keep it booting into the working kernel using grub-set-default.

Unfortunately petitboot does not seem to understand this feature.
I'm using boot-kernel to set this all up.

$ sudo ./boot-kernel  4.4.0-36-generic
selected /boot/vmlinux-4.4.0-36-generic. entry: Advanced options for Ubuntu>Ubuntu, with Linux 4.4.0-36-generic

$ head -n 4 /boot/grub/grubenv | sed 's,####\+$,###...\n,'
# GRUB Environment Block
saved_entry=Advanced options for Ubuntu>Ubuntu, with Linux 4.4.0-36-generic
next_entry=Advanced options for Ubuntu>Ubuntu, with Linux 4.4.0-36-generic
###...

$ sudo reboot

The system comes back up in the 4.4.0-45-generic kernel.

See the attached grub.cfg and grubenv for info:

• grub.cfg
• grubenv

There has been some confusion about whether IPMI boot overrides should interact with the current boot order.
For example, if the boot order specifies a particular disk and a disk override is set, should Petitboot preference the disk in the boot order, or treat all disks equally?

At the moment I'm leaning towards no interaction: IPMI overrides as I understand them are meant to cover the case of "I have no idea how this system is configured, but I want it to boot this". Giving consideration to the current config in this case would seem unexpected to me.
I think this should just be a documented behaviour, but I encourage any alternate viewpoints :)

Today in order for me to automate stopping at the Petitboot shell prompt I need to use an expect script to monitor port 22 for the menu and then issue arrow key strokes to select the option to drop to the shell.

Am I doing it wrong? Is there a better way? Can I set a flag on the BMC for it to drop me automatically and then present the boot status as such when it has happened?

Hi,

We change "Timeout" for auto-boot setting in Petitboot System Configuration and choose "OK", but the setting can NOT be saved. Please see the attached file: TimeoutNotSave.png

Cheers,
Boga

When we press "shift+tab" in Petitboot Language Selection page, it goes next not previous.

version: dev.20150401 on an IBM 8247-42L machine

We have two Linux installations one from an old LPAR-based setup and one that came pre-installed with the machine.

The entries mix up and are listed multiple times with no easy way to distinguish.

  [Disk: sdd2 / 6cf91c84-1d44-4611-9e69-1d37ca72e3b7]
    Ubuntu 14.04.2 LTS (14.04) (on /dev/sdc2)
    Ubuntu (on /dev/sdc2)
    Ubuntu, with Linux 3.16.0-30-generic (on /dev/sdc2)
    Ubuntu, with Linux 3.16.0-30-generic (recovery mode) (on /dev/sdc2)
    Ubuntu, with Linux 3.13.0-62-generic (on /dev/sdc2)
    Ubuntu, with Linux 3.13.0-62-generic (recovery mode) (on /dev/sdc2)
    Ubuntu, with Linux 3.19.0-25-generic (recovery mode)
    Ubuntu, with Linux 3.19.0-25-generic
    Ubuntu
  [Disk: sdf2 / 40652b06-fed4-4cdb-ba65-bec98c951927]
    Ubuntu, with Linux 3.13.0-62-generic (recovery mode)
    Ubuntu, with Linux 3.13.0-62-generic
    Ubuntu, with Linux 3.16.0-30-generic (recovery mode)
    Ubuntu, with Linux 3.16.0-30-generic
    Ubuntu

We have to carefully check each potential entry's root UUID to figure out the right one (We have by now documented which UUID is for which installation).

Also, the disk numbers (sdf, sdh) keep changing between boots, but I guess that is a different and trivial issue altogether.

I have two disks, sda and sdb, with identical boot entries:

 *[Disk: sda2 / 0d20c4db-1f6a-43cd-8989-21099678066a]
    Ubuntu, with Linux 4.10.0-20-generic (recovery mode)
    Ubuntu, with Linux 4.10.0-20-generic
    Ubuntu
  [Disk: sdb2 / b011e264-4e00-41f3-a482-49d1e47fdaa5]
    Ubuntu, with Linux 4.10.0-20-generic (recovery mode)  
    Ubuntu, with Linux 4.10.0-20-generic
    Ubuntu

I don't know which one will autoboot. I'm guessing sda because of the asterisk?

In the log, I see Booting in 10 sec: Ubuntu, which isn't particularly useful. It'd be nice if it said Booting in 10 sec: [sda2] Ubuntu for example.

The devmapper functionality adds two relatively large shared libraries -- libdevmapper.so and (transitively) libm.so -- into the Petitboot prerequisites. For Petitboot users that don't plan to avail themselves of the devmapper functions such as LVM and RAID, it would be nice to provide a configuration option to build Petitboot without the calls to devmapper.