Re: Fedora 23 Install Issues on PPC64LE Server

[Jakub Cajka]

----- Original Message -----
> From: "Adi Gangidi" 
> To: [e-mail]
> Cc: "John Hincher" , "Aaron Sullivan" , "Antony Messerli"
> , "Major Hayden" 
> Sent: Thursday, September 10, 2015 1:40:08 AM
> Subject: Fedora 23 Install Issues on PPC64LE Server
>
> Hello All

Hello,
> As I am trying to install Fedora 23 on our PPC64LE server. I am running into
> an issue with install. It has to be noted that Fedora 22/21 fail with
> similar errors on this configuration:
>
> Any pointers on narrowing this issue down would be greatly appreciated.
>
> To give details on the box:
>
> A ) Stoarage: Avago RAID controller 9361-8i (with 15 solid state drives on
> RAID0 config) Firmware version we used is 4.300.00-4429 .
>
> B) Network: Mellanox Connectx 3 pro card in the box.
>
> Here are the details. Install log is attached:
> 1. Install Process gets stuck at the following point during installation:
> (Full install logs are attached)
>
> [ 35.253098] mlx4_en: 0002:01:00.0: Port 1: Initializing port
>
> [ 35.263979] mlx4_en 0002:01:00.0: Activating port:2
>
> [ 35.271034] mlx4_en: eth1: Link Up
>
> [ 35.281464] mlx4_en: 0002:01:00.0: Port 2: Using 256 TX rings
>
> [ 35.285573] mlx4_en: 0002:01:00.0: Port 2: Using 8 RX rings
>
> [ 35.291084] mlx4_en: 0002:01:00.0: Port 2: frag:0 - size:1518 prefix:0
> stride:1536
>
> [ 35.298236] mlx4_en: 0002:01:00.0: Port 2: Initializing port
>
> [ 35.309191] <mlx4_ib> mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand
> driver v2.2-1 (Feb 2014)
>
> [ 35.327918] <mlx4_ib> mlx4_ib_add: counter index 2 for port 1 allocated 1
>
> [ 35.333372] <mlx4_ib> mlx4_ib_add: counter index 3 for port 2 allocated 1
>
> [ 35.354383] <mlx4_ib> mlx4_ib_add: counter index 2 for port 1 allocated 1
>
> [ 35.358463] <mlx4_ib> mlx4_ib_add: counter index 3 for port 2 allocated 1
>
> [ 35.363710] mlx4_en: eth3: Link Up
>
> [ 35.376411] mlx4_core 0000:01:00.0 enp1s0: renamed from eth0
>
> [ 35.432571] mlx4_core 0000:01:00.0 enp1s0d1: renamed from eth1
>
> [ 35.603694] mlx4_core 0002:01:00.0 enP2p1s0d1: renamed from eth3
>
> [ 35.692421] mlx4_core 0002:01:00.0 enP2p1s0: renamed from eth2
>
> [ 37.691861] sd 5:2:10:0: [sdl] Attached SCSI disk
>
> [ 37.692054] sd 5:2:6:0: [sdh] Attached SCSI disk
>
> [ 37.692520] sd 5:2:13:0: [sdo] Attached SCSI disk
>
> [ 37.692800] sd 5:2:14:0: [sdp] Attached SCSI disk
>
> [ 43.690839] sd 5:2:12:0: [sdn] Attached SCSI disk
>
> [ 43.691142] sd 5:2:8:0: [sdj] Attached SCSI disk
>
> [ 43.691335] sd 5:2:11:0: [sdm] Attached SCSI disk
>
> [ 43.691633] sd 5:2:9:0: [sdk] Attached SCSI disk
>
> [ 49.685080] sd 5:2:5:0: [sdg] Attached SCSI disk
>
> [ 49.685256] sd 5:2:4:0: [sdf] Attached SCSI disk
>
> [ 49.685755] sd 5:2:7:0: [sdi] Attached SCSI disk
>     2. After getting stuck for about 3-5 minutes, rescue shell kicks in as
>     below. However as soon as it loads, serial console doesn’t respond
>     anymore, resulting in not being able to collect logs from rescue shell.
> [ 235.757258] ]dracut-initqueue[1776]: Warning: Could not boot. 235.758170]
> dracut-initqueue[1776]: Warning: /dev/root does not exist Starting Setup
> Virtual Console... [ OK ] Started Setup Virtual Console. [ 236.203610]
> audit: type=1130 audit(235.750:12): pid=1 uid=0 auid=4294967295 s
> es=4294967295 subj=kernel msg='unit=systemd-vconsole-setup comm="systemd"
> exe="/ usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Starting Dracut Emergency Shell... Warning: /dev/root does not exist
> Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit
> the shell to continue. Type "journalctl" to view system logs. You might want
> to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after
> mounting them and attach it to a bug report.

The freezing console might be related to the https://bugzilla.redhat.com/show_bug.cgi?id=1255074 . Which makes debugging really annoying and painful especially combined with https://bugzilla.redhat.com/show_bug.cgi?id=1255066 (it should get fixed in next image iteration).

Do you observe same behavior of console with f21/f22?

What do you use to obtain console(ipmi sol, physical connection,...)?

What are you using as installation source(DVD, PXE, USB, remote repo,....) and what image are you using(netinst/dvd)?

Are disks already partitioned or are empty?

Have you been successful with booting/installing any other linux distribution(either LE/BE)?

Thanks for report and testing,

Jakub
> I can add details here as necessary.
>
> Best
> Adi Gangidi
> Rackspace
>
> ppc mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/ppc