Bug 1036881 - Initial Install on Dell R720 Fails with 'Pane is dead'
Summary: Initial Install on Dell R720 Fails with 'Pane is dead'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: iscsi-initiator-utils
Version: 20
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Chris Leech
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1125054 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-02 20:16 UTC by Kurt Miller
Modified: 2015-06-30 12:28 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 12:28:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output from R720 that causes anaconda to segfault (100.09 KB, text/plain)
2013-12-02 22:22 UTC, Kurt Miller
no flags Details

Description Kurt Miller 2013-12-02 20:16:15 UTC
Description of problem:

Attemping to install Fedora 20-beta on Dell R720 from DVD results in anaconda crashing immediatly to a blank screen with 'Pane is dead' message above the green tmux status bar.

Version-Release number of selected component (if applicable):
Fedora 20-beta

How reproducible:
Always

Steps to Reproduce:
1. Boot off install DVD
2. Wait for anaconda to start
3. Crashes immediatly

Actual results:
Cant install Fedora 20-beta

Expected results:
To be able to install Fedora 20-beta

Additional info:
Switching to window 3:log output:

tail: cannot open /tmp/anaconda.log for reading: No such file or directory

Switching to window 4:strorage-log output:

tail: cannot open /tmp/storage.log for reading: No such file or directory

Switching to window 4:program-log output:

tail: cannot open /tmp/program.log for reading: No such file or directory


Please advise how to work-around problem or further steps to help diagnose the problem.

Comment 1 Kurt Miller 2013-12-02 22:21:32 UTC
Some additional information:

Tried updating BIOS from 2.0.19 to 2.1.2 and tried both BIOS and UEFI boot modes. In all cases it fails.

Executing anaconda in window 2 results in a segfault which I assume is also the cause of the dead pane. Using gdb in qemu F20 install on the core file results in this backtrace:

#0  0x00007feffdb30490 in strlcat () from /lib64/libiscsi.so.0
#1  0x00007feffdb55f59 in sysfs_lookup_devpath_by_subsys_id ()
   from /lib64/libiscsi.so.0
#2  0x00007feffdb561ec in sysfs_get_value () from /lib64/libiscsi.so.0
#3  0x00007feffdb56332 in sysfs_get_str () from /lib64/libiscsi.so.0
#4  0x00007feffdb58af2 in iscsi_sysfs_read_iface () from /lib64/libiscsi.so.0
#5  0x00007feffdb58f4a in iscsi_sysfs_for_each_host ()
   from /lib64/libiscsi.so.0
#6  0x00007feffdb48a6c in iface_setup_host_bindings ()
   from /lib64/libiscsi.so.0
#7  0x00007feffdb5bf72 in libiscsi_init () from /lib64/libiscsi.so.0
#8  0x00007feffdd7bf4d in initlibiscsi ()
   from /usr/lib64/python2.7/site-packages/libiscsimodule.so
#9  0x00007ff012f43fc9 in _PyImport_LoadDynamicModule ()
   from /lib64/libpython2.7.so.1.0
#10 0x00007ff012f420a1 in ?? () from /lib64/libpython2.7.so.1.0
#11 0x00007ff012f42386 in ?? () from /lib64/libpython2.7.so.1.0
#12 0x00007ff012f42cce in PyImport_ImportModuleLevel ()
   from /lib64/libpython2.7.so.1.0
#13 0x00007ff012f294cf in ?? () from /lib64/libpython2.7.so.1.0
#14 0x00007ff012e990f3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#15 0x00007ff012f2b0e7 in PyEval_CallObjectWithKeywords ()
   from /lib64/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#16 0x00007ff012f2cbb3 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#17 0x00007ff012f3129d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#18 0x00007ff012f313a2 in PyEval_EvalCode () from /lib64/libpython2.7.so.1.0
#19 0x00007ff012f4118c in PyImport_ExecCodeModuleEx ()
   from /lib64/libpython2.7.so.1.0
#20 0x00007ff012f41408 in ?? () from /lib64/libpython2.7.so.1.0
#21 0x00007ff012f420a1 in ?? () from /lib64/libpython2.7.so.1.0
#22 0x00007ff012f422ed in ?? () from /lib64/libpython2.7.so.1.0
#23 0x00007ff012f42cce in PyImport_ImportModuleLevel ()
   from /lib64/libpython2.7.so.1.0
#24 0x00007ff012f294cf in ?? () from /lib64/libpython2.7.so.1.0
#25 0x00007ff012e990f3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#26 0x00007ff012f2b0e7 in PyEval_CallObjectWithKeywords ()
   from /lib64/libpython2.7.so.1.0
#27 0x00007ff012f2cbb3 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#28 0x00007ff012f3129d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#29 0x00007ff012f313a2 in PyEval_EvalCode () from /lib64/libpython2.7.so.1.0
#30 0x00007ff012f4118c in PyImport_ExecCodeModuleEx ()
   from /lib64/libpython2.7.so.1.0
#31 0x00007ff012f41408 in ?? () from /lib64/libpython2.7.so.1.0
#32 0x00007ff012f4289a in ?? () from /lib64/libpython2.7.so.1.0
#33 0x00007ff012f420a1 in ?? () from /lib64/libpython2.7.so.1.0
#34 0x00007ff012f42386 in ?? () from /lib64/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#35 0x00007ff012f42cce in PyImport_ImportModuleLevel ()
   from /lib64/libpython2.7.so.1.0
#36 0x00007ff012f294cf in ?? () from /lib64/libpython2.7.so.1.0
#37 0x00007ff012e990f3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#38 0x00007ff012f2b0e7 in PyEval_CallObjectWithKeywords ()
   from /lib64/libpython2.7.so.1.0
#39 0x00007ff012f2cbb3 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#40 0x00007ff012f3129d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#41 0x00007ff012f313a2 in PyEval_EvalCode () from /lib64/libpython2.7.so.1.0
#42 0x00007ff012f4118c in PyImport_ExecCodeModuleEx ()
   from /lib64/libpython2.7.so.1.0
#43 0x00007ff012f41408 in ?? () from /lib64/libpython2.7.so.1.0
#44 0x00007ff012f420a1 in ?? () from /lib64/libpython2.7.so.1.0
#45 0x00007ff012f4259f in ?? () from /lib64/libpython2.7.so.1.0
#46 0x00007ff012f42dda in PyImport_ImportModuleLevel ()
   from /lib64/libpython2.7.so.1.0
#47 0x00007ff012f294cf in ?? () from /lib64/libpython2.7.so.1.0
#48 0x00007ff012e990f3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#49 0x00007ff012f2b0e7 in PyEval_CallObjectWithKeywords ()
   from /lib64/libpython2.7.so.1.0
#50 0x00007ff012f2cbb3 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#51 0x00007ff012f3129d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#52 0x00007ff012f313a2 in PyEval_EvalCode () from /lib64/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#53 0x00007ff012f4118c in PyImport_ExecCodeModuleEx ()
   from /lib64/libpython2.7.so.1.0
#54 0x00007ff012f41408 in ?? () from /lib64/libpython2.7.so.1.0
#55 0x00007ff012f420a1 in ?? () from /lib64/libpython2.7.so.1.0
#56 0x00007ff012f4259f in ?? () from /lib64/libpython2.7.so.1.0
#57 0x00007ff012f42dda in PyImport_ImportModuleLevel ()
   from /lib64/libpython2.7.so.1.0
#58 0x00007ff012f294cf in ?? () from /lib64/libpython2.7.so.1.0
#59 0x00007ff012e990f3 in PyObject_Call () from /lib64/libpython2.7.so.1.0
#60 0x00007ff012f2b0e7 in PyEval_CallObjectWithKeywords ()
   from /lib64/libpython2.7.so.1.0
#61 0x00007ff012f2cbb3 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
#62 0x00007ff012f3129d in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
#63 0x00007ff012f313a2 in PyEval_EvalCode () from /lib64/libpython2.7.so.1.0
#64 0x00007ff012f4a7ef in ?? () from /lib64/libpython2.7.so.1.0
#65 0x00007ff012f4b9ae in PyRun_FileExFlags () from /lib64/libpython2.7.so.1.0
#66 0x00007ff012f4cc39 in PyRun_SimpleFileExFlags ()
   from /lib64/libpython2.7.so.1.0
#67 0x00007ff012f5dc4f in Py_Main () from /lib64/libpython2.7.so.1.0
#68 0x00007ff012186d65 in __libc_start_main () from /lib64/libc.so.6
#69 0x0000000000400721 in _start () 

There are 10 network ports in this server: 2x 10G + 2x 1G via intergrated NIC + 3x dual port 10G broadcom NICs. I will attach the dmesg output.

Comment 2 Kurt Miller 2013-12-02 22:22:37 UTC
Created attachment 831812 [details]
dmesg output from R720 that causes anaconda to segfault

Comment 3 Kurt Miller 2013-12-03 00:30:42 UTC
I pulled the extra NICs and tried to disable iSCSI on the intergrated NIC ports, but I guess I didn't find the right knob to turn. After disabling the onboard NIC and using an Intel 10G NIC, I was able to get the anaconda to run.

So I guess you need a NIC that supports iSCSI like the Broadcom ones to reproduce the problem.

I completed the F20 install and reinstalled the Broadcom NICs and enabled the intergrated NIC. I poked around with iscsi-initiator-utils post install to see if I could get it to segfault. If there is a particular set of commands to test please let me know.

Comment 4 Yu Watanabe 2013-12-25 04:57:05 UTC
I have similar issue, that is reported at bug #1044759, and I found a workaround.
At the kernel command line option, add the following option:

modprobe.blacklist=cnic,bnx2i

Comment 5 Johan Swensson 2014-02-05 20:45:56 UTC
(In reply to Yu Watanabe from comment #4)
> I have similar issue, that is reported at bug #1044759, and I found a
> workaround.
> At the kernel command line option, add the following option:
> 
> modprobe.blacklist=cnic,bnx2i

This works on HP Proliant DL360 G6 as well. Thanks.

Comment 6 David Shea 2014-07-31 12:25:59 UTC
*** Bug 1125054 has been marked as a duplicate of this bug. ***

Comment 7 Phil Davis 2014-12-05 14:51:59 UTC
> modprobe.blacklist=cnic,bnx2i

This also works for HP Proliant DL360 G5. Thanks.

Comment 8 Fedora End Of Life 2015-05-29 09:53:57 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Jaroslav Reznik 2015-06-30 12:28:02 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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