RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1442663 - [bnx2fc FCoE] can't start 2nd kernel
Summary: [bnx2fc FCoE] can't start 2nd kernel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1352763 1473055 1690729
TreeView+ depends on / blocked
 
Reported: 2017-04-17 02:27 UTC by Qiao Zhao
Modified: 2019-03-20 06:13 UTC (History)
11 users (show)

Fixed In Version: dracut-033-546.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:26:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3232 0 None None None 2018-10-30 11:28:40 UTC

Description Qiao Zhao 2017-04-17 02:27:02 UTC 
Description of problem:
There is my env & steps:
storageqe-53.rhts.eng.pek2.redhat.com  -- boot from local disk
S1: install fcoe-utils package first, start fcoe and lldpad service
S2: find fcoe disk: fipvlan -a -c -s
# fipvlan -a -c -s
Starting FCoE on interface enp17s0f0.200
Starting FCoE on interface enp17s0f1.200
Fibre Channel Forwarders Discovered
interface       | VLAN | FCF MAC          
------------------------------------------
enp17s0f0       | 200  | 54:7f:ee:6d:52:80
enp17s0f1       | 200  | 54:7f:ee:6d:52:80

S3: kdump.cnnf configuation:
# grep -v ^# /etc/kdump.conf 

ext4 UUID="26b7bea8-d1c9-4f75-82d7-2ba95ac68d74"
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31

S4: Trigger

1) when use crashkernel=auto, will occur oom-killer on 2nd kernel
2) change crashkernel=256M, occur Warning: dracut-initqueue timeout - starting timeout scripts when start disk device
        - (copy from console log) random: nonblocking pool is initialized 

] Found device ServeRAID_M5110e 2.
[    8.739476] bnx2x 0000:11:00.0 enp17s0f0: using MSI-X  IRQs: sp 42  fp[0] 44 ... fp[0] 44
[    8.850219] bnx2x 0000:11:00.0 enp17s0f0: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit
[    8.893325] bnx2fc: [11]: FCOE_INIT passed
[    8.897903] 8021q: adding VLAN 0 to HW filter on device enp17s0f0
[   10.429471] bnx2x 0000:11:00.1 enp17s0f1: using MSI-X  IRQs: sp 46  fp[0] 48 ... fp[0] 48
[   10.540270] bnx2x 0000:11:00.1 enp17s0f1: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit
[   10.583376] bnx2fc: [11]: FCOE_INIT passed
[   10.587954] 8021q: adding VLAN 0 to HW filter on device enp17s0f1
[    
  OK    
] Found device /dev/mapper/rhel_storageqe--53-root.
         Starting File System Check on /dev/mapper/rhel_storageqe--53-root...
[    
  OK    
] Started File System Check on /dev/mapper/rhel_storageqe--53-root.
[  100.048008] random: nonblocking pool is initialized
[  133.074632] dracut-initqueue[267]: Warning: dracut-initqueue timeout - starting timeout scripts
[  133.672720] dracut-initqueue[267]: Warning: dracut-initqueue timeout - starting timeout scripts
[  134.179080] dracut-initqueue[267]: Warning: dracut-initqueue timeout - starting timeout scripts 

Full log: 
http://lacrosse.corp.redhat.com/qzhao/log/rhel7_fcoe_bnx2fc_non-san-boot_st53.log

Version-Release number of selected component (if applicable):
kernel-3.10.0-632.el7.x86_64
kexec-tools-2.0.14-3.el7.x86_64
fcoe-utils-1.0.32-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Full log: http://lacrosse.corp.redhat.com/qzhao/log/rhel7_fcoe_bnx2fc_non-san-boot_st53.log
Comment 2 Qiao Zhao 2017-04-20 05:53:11 UTC 
I retest this problem on RHEL-7.3 GA tree, got the same error:

[    7.296154] Console: switching to colour frame buffer device 128x48
[    7.397805] mgag200 0000:04:00.0: fb0: mgadrmfb frame buffer device
[    7.405498] [drm] Initialized mgag200 1.0.0 20110418 for 0000:04:00.0 on minor 0
[    7.714492] sd 0:2:0:0: [sda] 7809794048 512-byte logical blocks: (3.99 TB/3.63 TiB)
[    7.745707] sd 0:2:0:0: [sda] Write Protect is off
[    7.754592] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
[    7.809833]  sda: sda1 sda2 sda3
[    7.813926] sd 0:2:0:0: [sda] Attached SCSI disk
[  OK  ] Found device ServeRAID_M5110e 2.
[    8.538898] bnx2x 0000:11:00.0 enp17s0f0: using MSI-X  IRQs: sp 42  fp[0] 44 ... fp[0] 44
[    8.647618] bnx2x 0000:11:00.0 enp17s0f0: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit
[    8.690853] bnx2fc: [11]: FCOE_INIT passed
[    8.695432] 8021q: adding VLAN 0 to HW filter on device enp17s0f0
[   10.217000] bnx2x 0000:11:00.1 enp17s0f1: using MSI-X  IRQs: sp 46  fp[0] 48 ... fp[0] 48
[   10.327725] bnx2x 0000:11:00.1 enp17s0f1: NIC Link is Up, 10000 Mbps full duplex, Flow control: ON - receive & transmit
[   10.370954] bnx2fc: [11]: FCOE_INIT passed
[   10.375532] 8021q: adding VLAN 0 to HW filter on device enp17s0f1
[  OK  ] Found device /dev/mapper/rhel_storageqe--53-root.
         Starting File System Check on /dev/mapper/rhel_storageqe--53-root...
[  OK  ] Started File System Check on /dev/mapper/rhel_storageqe--53-root.
[  132.911698] dracut-initqueue[269]: Warning: dracut-initqueue timeout - starting timeout scripts
[  133.502129] dracut-initqueue[269]: Warning: dracut-initqueue timeout - starting timeout scripts


Version:
kernel-3.10.0-514.el7.x86_64
kexec-tools-2.0.7-50.el7.x86_64
fcoe-utils-1.0.31-1.git5dfd3e4.el7.x86_64
Comment 3 Baoquan He 2017-07-25 09:03:06 UTC 
I got the storageqe-53.rhts.eng.pek2.redhat.com, after enabling fcoe and multipath, it print warning when execute "multipath -t":

[root@storageqe-53 ~]# multipath -t
Jul 25 04:54:29 | DM multipath kernel driver not loaded
Jul 25 04:54:29 | ignoring extra data starting with '04:51:50' on line 1 of /etc/multipath.conf
Jul 25 04:54:29 | /etc/multipath.conf line 1, invalid keyword: Jul
Jul 25 04:54:29 | ignoring extra data starting with '04:51:50' on line 2 of /etc/multipath.conf
Jul 25 04:54:29 | /etc/multipath.conf line 2, invalid keyword: Jul
Jul 25 04:54:29 | DM multipath kernel driver not loaded

Seems the kernel driver of multipath is not loaded. There could be anything wrong with fcoe hardware setting or fcoe kernel driver issue.

Since Xunlei also is handling several fcoe bugs, so reassign this bug to xunlei according to Dave's suggestion.

Thanks
Baoquan
Comment 4 Xunlei Pang 2017-07-25 11:32:05 UTC 
(In reply to Qiao Zhao from comment #0)
> Description of problem:
> There is my env & steps:
> storageqe-53.rhts.eng.pek2.redhat.com  -- boot from local disk
> S1: install fcoe-utils package first, start fcoe and lldpad service
> S2: find fcoe disk: fipvlan -a -c -s
> # fipvlan -a -c -s
> Starting FCoE on interface enp17s0f0.200
> Starting FCoE on interface enp17s0f1.200
> Fibre Channel Forwarders Discovered
> interface       | VLAN | FCF MAC          
> ------------------------------------------
> enp17s0f0       | 200  | 54:7f:ee:6d:52:80
> enp17s0f1       | 200  | 54:7f:ee:6d:52:80
> 
> S3: kdump.cnnf configuation:
> # grep -v ^# /etc/kdump.conf 
> 
> ext4 UUID="26b7bea8-d1c9-4f75-82d7-2ba95ac68d74"

Hi Qiao,

Since UUID should be changed on this machine after restallation, do you remember which dump disk does that UUID refer to?

[root@storageqe-53 ~]# lsblk 
NAME                                MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda                                   8:0    0  3.7T  0 disk  
├─sda1                                8:1    0    1M  0 part  
├─sda2                                8:2    0    1G  0 part  /boot
└─sda3                                8:3    0  3.7T  0 part  
  ├─rhel_storageqe--53-root         253:0    0   50G  0 lvm   /
  ├─rhel_storageqe--53-swap         253:1    0 15.7G  0 lvm   [SWAP]
  └─rhel_storageqe--53-home         253:2    0  3.6T  0 lvm   /home
sdb                                   8:16   0   30G  0 disk  
└─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
sdc                                   8:32   0    2G  0 disk  
└─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
sdd                                   8:48   0    2G  0 disk  
└─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
sde                                   8:64   0    2G  0 disk  
└─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath 
sdf                                   8:80   0   30G  0 disk  
└─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
sdg                                   8:96   0    2G  0 disk  
└─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
sdh                                   8:112  0    2G  0 disk  
└─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
sdi                                   8:128  0    2G  0 disk  
└─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath 
sdj                                   8:144  0   30G  0 disk  
└─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
sdk                                   8:160  0    2G  0 disk  
└─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
sdl                                   8:176  0    2G  0 disk  
└─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
sdm                                   8:192  0    2G  0 disk  
└─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath 
sdn                                   8:208  0   30G  0 disk  
└─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
sdo                                   8:224  0    2G  0 disk  
└─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
sdp                                   8:240  0    2G  0 disk  
└─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
sdq                                  65:0    0    2G  0 disk  
└─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath
Comment 5 Qiao Zhao 2017-07-26 07:03:18 UTC 
(In reply to Xunlei Pang from comment #4)
> (In reply to Qiao Zhao from comment #0)
> > Description of problem:
> > There is my env & steps:
> > storageqe-53.rhts.eng.pek2.redhat.com  -- boot from local disk
> > S1: install fcoe-utils package first, start fcoe and lldpad service
> > S2: find fcoe disk: fipvlan -a -c -s
> > # fipvlan -a -c -s
> > Starting FCoE on interface enp17s0f0.200
> > Starting FCoE on interface enp17s0f1.200
> > Fibre Channel Forwarders Discovered
> > interface       | VLAN | FCF MAC          
> > ------------------------------------------
> > enp17s0f0       | 200  | 54:7f:ee:6d:52:80
> > enp17s0f1       | 200  | 54:7f:ee:6d:52:80
> > 
> > S3: kdump.cnnf configuation:
> > # grep -v ^# /etc/kdump.conf 
> > 
> > ext4 UUID="26b7bea8-d1c9-4f75-82d7-2ba95ac68d74"
> 
> Hi Qiao,
> 
> Since UUID should be changed on this machine after restallation, do you
> remember which dump disk does that UUID refer to?
> 
> [root@storageqe-53 ~]# lsblk 
> NAME                                MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
> sda                                   8:0    0  3.7T  0 disk  
> ├─sda1                                8:1    0    1M  0 part  
> ├─sda2                                8:2    0    1G  0 part  /boot
> └─sda3                                8:3    0  3.7T  0 part  
>   ├─rhel_storageqe--53-root         253:0    0   50G  0 lvm   /
>   ├─rhel_storageqe--53-swap         253:1    0 15.7G  0 lvm   [SWAP]
>   └─rhel_storageqe--53-home         253:2    0  3.6T  0 lvm   /home
> sdb                                   8:16   0   30G  0 disk  
> └─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
> sdc                                   8:32   0    2G  0 disk  
> └─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
> sdd                                   8:48   0    2G  0 disk  
> └─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
> sde                                   8:64   0    2G  0 disk  
> └─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath 
> sdf                                   8:80   0   30G  0 disk  
> └─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
> sdg                                   8:96   0    2G  0 disk  
> └─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
> sdh                                   8:112  0    2G  0 disk  
> └─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
> sdi                                   8:128  0    2G  0 disk  
> └─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath 
> sdj                                   8:144  0   30G  0 disk  
> └─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
> sdk                                   8:160  0    2G  0 disk  
> └─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
> sdl                                   8:176  0    2G  0 disk  
> └─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
> sdm                                   8:192  0    2G  0 disk  
> └─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath 
> sdn                                   8:208  0   30G  0 disk  
> └─360a9800042566643352b476d67496d30 253:3    0   30G  0 mpath 
> sdo                                   8:224  0    2G  0 disk  
> └─360a9800042566643352b476d67496e52 253:4    0    2G  0 mpath 
> sdp                                   8:240  0    2G  0 disk  
> └─360a9800042566643352b476d67496e54 253:5    0    2G  0 mpath 
> sdq                                  65:0    0    2G  0 disk  
> └─360a9800042566643352b476d67496e56 253:6    0    2G  0 mpath

Sorry, i forgot this. I need retest it.
Comment 6 Xunlei Pang 2017-07-26 07:23:06 UTC 
Hi Qiao(In reply to Qiao Zhao from comment #5)
> (In reply to Xunlei Pang from comment #4)
> > (In reply to Qiao Zhao from comment #0)
> > > Description of problem:
> > > There is my env & steps:
> > > storageqe-53.rhts.eng.pek2.redhat.com  -- boot from local disk
> > > S1: install fcoe-utils package first, start fcoe and lldpad service
> > > S2: find fcoe disk: fipvlan -a -c -s
> > > # fipvlan -a -c -s
> > > Starting FCoE on interface enp17s0f0.200
> > > Starting FCoE on interface enp17s0f1.200
> > > Fibre Channel Forwarders Discovered
> > > interface       | VLAN | FCF MAC          
> > > ------------------------------------------
> > > enp17s0f0       | 200  | 54:7f:ee:6d:52:80
> > > enp17s0f1       | 200  | 54:7f:ee:6d:52:80
> > > 
> > > S3: kdump.cnnf configuation:
> > > # grep -v ^# /etc/kdump.conf 
> > > 
> > > ext4 UUID="26b7bea8-d1c9-4f75-82d7-2ba95ac68d74"
> > 
> > Hi Qiao,
> > 
> > Since UUID should be changed on this machine after restallation, do you
> > remember which dump disk does that UUID refer to?
> > 
> 
> Sorry, i forgot this. I need retest it.

Hi Qiao, Baoquan currently owns the machine, you can contact him if you want to retest.
Comment 29 Baoquan He 2018-05-28 06:52:51 UTC 
From the current dracut in rhel7, the commit mentioned in #comment 20 is not back ported yet.
Comment 31 Lukáš Nykrýn 2018-06-20 10:06:12 UTC 
https://github.com/dracutdevs/dracut/commit/f055e5126f7d28553c3886a865e5f13fdc4c18d2
Comment 32 Lukáš Nykrýn 2018-06-20 10:06:38 UTC 
I will include the patch in proper build.
Comment 35 Martin Banas 2018-08-08 12:30:56 UTC 
Hi Qiao Zhao,
Is there anything else do be done in this bugzilla or can it be considered as Done/Verified?

Thanks,
M.
Comment 36 Qiao Zhao 2018-08-09 03:13:51 UTC 
(In reply to Martin Banas from comment #35)
> Hi Qiao Zhao,
> Is there anything else do be done in this bugzilla or can it be considered
> as Done/Verified?
> 
> Thanks,
> M.

Yes, feel free to set Verified this bugzilla. According to comment#34, this FCoE device can work on 2nd kernel on new dracut. Add for other oom issues, let we track it on bz#1371086.

--
Thanks,
Qiao
Comment 37 Martin Banas 2018-08-09 07:39:28 UTC 
Thanks!
Comment 39 errata-xmlrpc 2018-10-30 11:26:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3232
Note You need to log in before you can comment on or make changes to this bug.