Bug 621782 - NMI IOCK error occurred in hpsa driver in kdump kernel
NMI IOCK error occurred in hpsa driver in kdump kernel
Status: CLOSED DUPLICATE of bug 612486
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.0
All Linux
high Severity high
: rc
: ---
Assigned To: Red Hat Kernel Manager
Red Hat Kernel QE team
: RHELNAK
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-06 02:31 EDT by Cong Wang
Modified: 2013-09-29 22:19 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-06 05:23:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Cong Wang 2010-08-06 02:31:05 EDT
Description of problem:
NMI: IOCK error (debug interrupt?)
CPU 0
Modules linked in: hpsa(+) ata_piix pata_acpi cdrom netxen_nic edac_core sg
hpilo iTCO_vendor_support serio_raw hwmon ipv6 sunrpc autofs4 dm_snapshot
dm_zero dm_mirror dm_region_hash dm_log dm_mod ata_generic sd_mod crc_t10dif
ext4 mbcache jbd2

Modules linked in: hpsa(+) ata_piix pata_acpi cdrom netxen_nic edac_core sg
hpilo iTCO_vendor_support serio_raw hwmon ipv6 sunrpc autofs4 dm_snapshot
dm_zero dm_mirror dm_region_hash dm_log dm_mod ata_generic sd_mod crc_t10dif
ext4 mbcache jbd2
Pid: 179, comm: insmod Not tainted 2.6.32-44.1.el6.x86_64 #1 ProLiant DL580 G7
RIP: 0010:[<ffffffff813fab7a>]  [<ffffffff813fab7a>] pci_conf1_write+0xda/0xe0
RSP: 0018:ffff8800073f7bb8  EFLAGS: 00000002
RAX: 000000000000323a RBX: ffff880008d8c800 RCX: 0000000000000002
RDX: 0000000000000cfe RSI: 0000000000000003 RDI: 0000000000000097
RBP: ffff8800073f7be8 R08: 0000000000000002 R09: 000000000000323a
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000246
R13: 000000000000323a R14: ffffc900103f4c60 R15: 0000000000000002
FS:  0000000000000000(0000) GS:ffff880003e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000004b44dc CR3: 00000000073ee000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process insmod (pid: 179, threadinfo ffff8800073f6000, task ffff880009fa5500)
Stack:
 ffffffff81c192c0 000000000000323a 0000000000000002 ffffffff00000002
<0> ffffffff00000000 0000000000000003 ffff8800073f7bf8 ffffffff813fc744
<0> ffff8800073f7c08 ffffffff813fc7cc ffff8800073f7c48 ffffffff81269cca

Call Trace:
 [<ffffffff813fc744>] raw_pci_write+0x24/0x50
 [<ffffffff813fc7cc>] pci_write+0x2c/0x30
 [<ffffffff81269cca>] pci_bus_write_config_word+0x5a/0x80
 [<ffffffffa025235d>] hpsa_init_one+0x27b/0x1378 [hpsa]
 [<ffffffff811db175>] ? sysfs_find_dirent+0x35/0x50
 [<ffffffff811dbb75>] ? sysfs_addrm_finish+0x25/0x290
 [<ffffffff81270e07>] local_pci_probe+0x17/0x20
 [<ffffffff81271ff1>] pci_device_probe+0x101/0x120
 [<ffffffff81331e12>] ? driver_sysfs_add+0x62/0x90
 [<ffffffff81331fb0>] driver_probe_device+0xa0/0x2a0
 [<ffffffff8133225b>] __driver_attach+0xab/0xb0
 [<ffffffff813321b0>] ? __driver_attach+0x0/0xb0
 [<ffffffff81331214>] bus_for_each_dev+0x64/0x90
 [<ffffffff81331d4e>] driver_attach+0x1e/0x20
 [<ffffffff81331650>] bus_add_driver+0x200/0x300
 [<ffffffff81332586>] driver_register+0x76/0x140
 [<ffffffff814dd525>] ? notifier_call_chain+0x55/0x80
 [<ffffffff81272256>] __pci_register_driver+0x56/0xd0
 [<ffffffff810961d5>] ? __blocking_notifier_call_chain+0x65/0x80
 [<ffffffffa0259000>] ? hpsa_init+0x0/0x20 [hpsa]
 [<ffffffffa025901e>] hpsa_init+0x1e/0x20 [hpsa]
 [<ffffffff8100a04c>] do_one_initcall+0x3c/0x1d0
 [<ffffffff810aeedf>] sys_init_module+0xdf/0x250
 [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
Code: fe 48 c7 c7 6c 32 cb 81 e8 14 fc 0d 00 31 c0 c9 c3 ba fc 0c 00 00 44 89 c8 ef eb e2 89 ca 44 89 c8 83 e2 02 66 81 c2 fc 0c 66 ef <eb> d1 0f 1f 40 00 55 48 89 e5 48 83 ec 30 48 89 5d d8 4c 89 65

Version-Release number of selected component (if applicable):
2.6.32-44.1.el6.x86_64


How reproducible:
Always on hp-dl580g7-01.lab.bos.redhat.com.

Steps to Reproduce:
1. Configure kdump and start kdump service
2. Crash the first kernel and boot the kdump kernel
3. You will see the oops


Expected results:
No errors.
Comment 2 RHEL Product and Program Management 2010-08-06 02:47:32 EDT
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 3 Tomas Henzl 2010-08-06 05:23:13 EDT
This is again a P410i failing with kdump. The symptoms aren't exactly the same as in 612486 but close enough. I'm closing this as dup.

*** This bug has been marked as a duplicate of bug 612486 ***

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