Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 822753

Summary: anaconda exits abnormally when installing RHEL7 to iSCSI SAN
Product: Red Hat Enterprise Linux 7 Reporter: Xiaowei Li <xiaoli>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0CC: qcai
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-22 08:41:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
console.log none

Description Xiaowei Li 2012-05-18 04:20:39 UTC
Description of problem:


Version-Release number of selected component (if applicable):
RHEL7 2012-05-14 tree

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
logs @ https://beaker.engineering.redhat.com/jobs/234325

Comment 1 Xiaowei Li 2012-05-18 04:21:19 UTC
Created attachment 585329 [details]
anaconda.log

Comment 2 Xiaowei Li 2012-05-18 04:21:52 UTC
Created attachment 585330 [details]
console.log

Comment 3 Xiaowei Li 2012-05-18 06:17:48 UTC
seems like it's the environment issue. will add more comments.
mark it as low priority first.

Comment 4 Chris Lumens 2012-05-18 14:18:10 UTC
The kernel stack traces in your console.log probably have something to do with this.

Comment 5 Qian Cai 2012-05-21 03:02:19 UTC
[   21.285409] qla4xxx 0000:05:04.1: qla4xxx_isr_decode_mailbox: LINK UP 
[   26.407203] scsi0: AEN 8029, mbox_sts[2]=0003, mbox_sts[3]=0005 
[   26.479063] qla4xxx 0000:05:04.1: 0 firmare IOCBs available (224). 
[   26.486501] qla4xxx 0000:05:04.1: qla4xxx_request_irqs: irq 19 attached 
[   26.493208]  QLogic iSCSI HBA Driver version: 5.02.00-k12 
[   26.493210]   QLogic ISP4022 @ 0000:05:04.1, host#=0, fw=03.00.01.53 
[   26.504968] qla4xxx 0000:05:04.1: get_fw_boot_info: Get FW boot info for 0x4022 func 1 
[   26.513042] qla4xxx 0000:05:04.1: qla4xxx_probe_adapter:ISCSI boot info setup failed 
[   26.521310] qla4xxx 0000:05:04.1: qla4xxx_get_fwddb_entry: DDB[0] MB0 4000 Tot 1 Next 2 State 0000 ConnErr 00000000 0.0.0.0 :0000 "" 
[   26.533703] qla4xxx 0000:05:04.1: qla4xxx_get_fwddb_entry: DDB[2] MB0 4000 Tot 1 Next 0 State 0001 ConnErr 00000000 10.16.41.222 :3260 "iqn.1992-08.com.netapp:sn.151753773" 
[   27.496265]  
[   27.497072] ================================= 
[   27.497072] [ INFO: inconsistent lock state ] 
[   27.497072] 3.3.0-0.12.el7.x86_64 #1 Not tainted 
[   27.497072] --------------------------------- 
[   27.497072] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage. 
[   27.497072] swapper/0/0 [HC0[0]:SC1[1]:HE1:SE0] takes: 
[   27.497072]  (&(&k->k_lock)->rlock){+.?...}, at: [<ffffffff8163917f>] klist_next+0x2f/0x120 
[   27.497072] {SOFTIRQ-ON-W} state was registered at: 
[   27.497072]   [<ffffffff810cdf50>] __lock_acquire+0x640/0x1ad0 
[   27.497072]   [<ffffffff810cfab1>] lock_acquire+0xa1/0x1e0 
[   27.497072]   [<ffffffff816621d6>] _raw_spin_lock+0x46/0x80 
[   27.497072]   [<ffffffff81639129>] klist_add_tail+0x29/0x50 
[   27.497072]   [<ffffffff8141b18e>] bus_add_device+0x18e/0x1d0 
[   27.497072]   [<ffffffff81419379>] device_add+0x599/0x6f0 
[   27.497072]   [<ffffffff814194ee>] device_register+0x1e/0x30 
[   27.497072]   [<ffffffff8142ba04>] add_memory_section+0x1b4/0x270 
[   27.497072]   [<ffffffff81c63a9c>] memory_dev_init+0x114/0x12b 
[   27.497072]   [<ffffffff81c63826>] driver_init+0x31/0x33 
[   27.497072]   [<ffffffff81c2bd1a>] kernel_init+0xd2/0x164 
[   27.497072]   [<ffffffff8166cdb4>] kernel_thread_helper+0x4/0x10 
[   27.497072] irq event stamp: 128188 
[   27.497072] hardirqs last  enabled at (128188): [<ffffffff81662bf0>] _raw_spin_unlock_irq+0x30/0x50 
[   27.497072] hardirqs last disabled at (128187): [<ffffffff816622df>] _raw_spin_lock_irq+0x1f/0x90 
[   27.497072] softirqs last  enabled at (128184): [<ffffffff8106bcb3>] _local_bh_enable+0x13/0x20 
[   27.497072] softirqs last disabled at (128185): [<ffffffff8166ceac>] call_softirq+0x1c/0x30 
[   27.497072]  
[   27.497072] other info that might help us debug this: 
[   27.497072]  Possible unsafe locking scenario: 
[   27.497072]  
[   27.497072]        CPU0 
[   27.497072]        ---- 
[   27.497072]   lock(&(&k->k_lock)->rlock); 
[   27.497072]   <Interrupt> 
[   27.497072]     lock(&(&k->k_lock)->rlock); 
[   27.497072]  
[   27.497072]  *** DEADLOCK *** 
[   27.497072]  
[   27.497072] 1 lock held by swapper/0/0: 
[   27.497072]  #0:  (&ha->timer){+.-...}, at: [<ffffffff81075f91>] __run_timers+0xf1/0x610 
[   27.497072]  
[   27.497072] stack backtrace: 
[   27.497072] Pid: 0, comm: swapper/0 Not tainted 3.3.0-0.12.el7.x86_64 #1 
[   27.497072] Call Trace: 
[   27.497072]  <IRQ>  [<ffffffff81656a42>] print_usage_bug+0x1f7/0x208 
[   27.497072]  [<ffffffff810273df>] ? save_stack_trace+0x2f/0x50 
[   27.497072]  [<ffffffff810ccd20>] ? print_shortest_lock_dependencies+0x1c0/0x1c0 
[   27.497072]  [<ffffffff810cd8d2>] mark_lock+0x272/0x2b0 
[   27.497072]  [<ffffffff810cdee2>] __lock_acquire+0x5d2/0x1ad0 
[   27.497072]  [<ffffffff810273df>] ? save_stack_trace+0x2f/0x50 
[   27.497072]  [<ffffffff810ca81f>] ? save_trace+0x3f/0xd0 
[   27.497072]  [<ffffffff810cd873>] ? mark_lock+0x213/0x2b0 
[   27.497072]  [<ffffffff810cfab1>] lock_acquire+0xa1/0x1e0 
[   27.497072]  [<ffffffff8163917f>] ? klist_next+0x2f/0x120 
[   27.497072]  [<ffffffff814175c0>] ? put_device+0x20/0x20 
[   27.497072]  [<ffffffff816621d6>] _raw_spin_lock+0x46/0x80 
[   27.497072]  [<ffffffff8163917f>] ? klist_next+0x2f/0x120 
[   27.497072]  [<ffffffffa01aff40>] ? qla4xxx_soft_reset+0x1d0/0x1d0 [qla4xxx] 
[   27.497072]  [<ffffffff8163917f>] klist_next+0x2f/0x120 
[   27.497072]  [<ffffffffa01aff40>] ? qla4xxx_soft_reset+0x1d0/0x1d0 [qla4xxx] 
[   27.497072]  [<ffffffffa00232f0>] ? show_iface_port+0x30/0x30 [scsi_transport_iscsi] 
[   27.497072]  [<ffffffff81417921>] device_for_each_child+0x41/0x70 
[   27.497072]  [<ffffffffa01b2e50>] ? qla4_8xxx_watchdog+0x310/0x310 [qla4xxx] 
[   27.497072]  [<ffffffffa00243dc>] iscsi_host_for_each_session+0x1c/0x20 [scsi_transport_iscsi] 
[   27.497072]  [<ffffffffa01b2e71>] qla4xxx_timer+0x21/0x1f0 [qla4xxx] 
[   27.497072]  [<ffffffffa01b2e50>] ? qla4_8xxx_watchdog+0x310/0x310 [qla4xxx] 
[   27.497072]  [<ffffffff81076026>] __run_timers+0x186/0x610 
[   27.497072]  [<ffffffff81075f91>] ? __run_timers+0xf1/0x610 
[   27.497072]  [<ffffffff8106d0d9>] ? __do_softirq+0x89/0x380 
[   27.497072]  [<ffffffff810764e1>] run_timer_softirq+0x31/0x40 
[   27.497072]  [<ffffffff8106d130>] __do_softirq+0xe0/0x380 
[   27.497072]  [<ffffffff8166ceac>] call_softirq+0x1c/0x30 
[   27.497072]  [<ffffffff8101a5c5>] do_softirq+0xa5/0xe0 
[   27.497072]  [<ffffffff8106d745>] irq_exit+0xd5/0xe0 
[   27.497072]  [<ffffffff8166d82e>] smp_apic_timer_interrupt+0x6e/0x99 
[   27.497072]  [<ffffffff8166c4b3>] apic_timer_interrupt+0x73/0x80 
[   27.497072]  <EOI>  [<ffffffff81113c70>] ? rcu_idle_enter_common.isra.36+0x3d0/0x4b0 
[   27.497072]  [<ffffffff810212ca>] ? mwait_idle+0x9a/0x4f0 
[   27.497072]  [<ffffffff810212c1>] ? mwait_idle+0x91/0x4f0 
[   27.497072]  [<ffffffff81017266>] cpu_idle+0x106/0x140 
[   27.497072]  [<ffffffff8163980f>] rest_init+0x133/0x144 
[   27.497072]  [<ffffffff81639755>] ? rest_init+0x79/0x144 
[   27.497072]  [<ffffffff81c2bc3d>] start_kernel+0x3f7/0x402 
[   27.497072]  [<ffffffff81c2b346>] x86_64_start_reservations+0x131/0x135 
[   27.497072]  [<ffffffff81c2b44a>] x86_64_start_kernel+0x100/0x10f

Comment 6 Xiaowei Li 2012-05-22 08:41:07 UTC
This is the environment issue. close it.