Same issue, hpacucli-9.40-12.0.x86_64.rpm on a related distro (*cough* Debian Wheezy).
Proliant DL365 with e200i on 1.8.6 firmware. Note even though the command hangs, the array is created and works after reboot. New drive will show up right away, but anything trying to access will block as well, in my case via pvcreate, started logging blocked messages for pvcreate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1006212 Title: cciss: hpacucli "ctrl slot=0 create type=ld drives=2:4" hangs, spews call trace in dmesg Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Confirmed Bug description: On a Hewlett-Packard ProLiant DL385 G1 running precise, linux- image-3.2.0-24-generic 3.2.0-24.39, when I issue "ctrl slot=0 create type=ld drives=2:4" via hpacucli, the command hangs. In dmesg I find the following (full dmesg attached). [ 482.228046] INFO: task .hpacucli:1384 blocked for more than 120 seconds. [ 482.249879] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 482.275399] .hpacucli D ffffffff81806240 0 1384 1367 0x00020000 [ 482.275413] ffff8801f7c6daf8 0000000000000082 ffffc90000806000 fde97dc8b0a15c03 [ 482.275431] ffff8801f7c6dfd8 ffff8801f7c6dfd8 ffff8801f7c6dfd8 0000000000013780 [ 482.275449] ffffffff81c0d020 ffff8801f81e44d0 ffffffffa004fd40 ffffffffa004fd40 [ 482.275466] Call Trace: [ 482.275486] [<ffffffff8165a88f>] schedule+0x3f/0x60 [ 482.275495] [<ffffffff8165b697>] __mutex_lock_slowpath+0xd7/0x150 [ 482.275504] [<ffffffff8165b2aa>] mutex_lock+0x2a/0x50 [ 482.275517] [<ffffffffa0038ebe>] cciss_unlocked_open+0x2e/0xd0 [cciss] [ 482.275528] [<ffffffff811b0212>] __blkdev_get+0xd2/0x460 [ 482.275538] [<ffffffff8108abc7>] ? bit_waitqueue+0x17/0xc0 [ 482.275546] [<ffffffff811b05fe>] blkdev_get+0x5e/0x1e0 [ 482.275556] [<ffffffff812fb152>] register_disk+0x162/0x180 [ 482.275564] [<ffffffff812fb224>] add_disk+0xb4/0x230 [ 482.275574] [<ffffffffa003a651>] cciss_add_disk+0x141/0x1b0 [cciss] [ 482.275584] [<ffffffffa003fbbf>] cciss_update_drive_info+0x3cf/0x490 [cciss] [ 482.275595] [<ffffffffa0040252>] rebuild_lun_table+0x282/0x3a0 [cciss] [ 482.275605] [<ffffffff8113dca8>] ? handle_mm_fault+0x1f8/0x350 [ 482.275615] [<ffffffffa0040def>] cciss_ioctl+0x29f/0x3e0 [cciss] [ 482.275625] [<ffffffffa0040f76>] do_ioctl+0x46/0x70 [cciss] [ 482.275635] [<ffffffffa00412fe>] cciss_compat_ioctl+0x1e/0xd8 [cciss] [ 482.275645] [<ffffffff81309ecd>] compat_blkdev_ioctl+0x32d/0x4b0 [ 482.275655] [<ffffffff811c838d>] compat_sys_ioctl+0xad/0x240 [ 482.275665] [<ffffffff81667470>] cstar_dispatch+0x7/0x2e [ 602.272039] INFO: task .hpacucli:1384 blocked for more than 120 seconds. [ 602.294416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 602.318038] .hpacucli D ffffffff81806240 0 1384 1367 0x00020000 [ 602.318044] ffff8801f7c6daf8 0000000000000082 ffffc90000806000 fde97dc8b0a15c03 [ 602.318050] ffff8801f7c6dfd8 ffff8801f7c6dfd8 ffff8801f7c6dfd8 0000000000013780 [ 602.318054] ffffffff81c0d020 ffff8801f81e44d0 ffffffffa004fd40 ffffffffa004fd40 [ 602.318059] Call Trace: [ 602.318076] [<ffffffff8165a88f>] schedule+0x3f/0x60 [ 602.318084] [<ffffffff8165b697>] __mutex_lock_slowpath+0xd7/0x150 [ 602.318092] [<ffffffff8165b2aa>] mutex_lock+0x2a/0x50 [ 602.318104] [<ffffffffa0038ebe>] cciss_unlocked_open+0x2e/0xd0 [cciss] [ 602.318114] [<ffffffff811b0212>] __blkdev_get+0xd2/0x460 [ 602.318123] [<ffffffff8108abc7>] ? bit_waitqueue+0x17/0xc0 [ 602.318131] [<ffffffff811b05fe>] blkdev_get+0x5e/0x1e0 [ 602.318140] [<ffffffff812fb152>] register_disk+0x162/0x180 [ 602.318147] [<ffffffff812fb224>] add_disk+0xb4/0x230 [ 602.318157] [<ffffffffa003a651>] cciss_add_disk+0x141/0x1b0 [cciss] [ 602.318167] [<ffffffffa003fbbf>] cciss_update_drive_info+0x3cf/0x490 [cciss] [ 602.318177] [<ffffffffa0040252>] rebuild_lun_table+0x282/0x3a0 [cciss] [ 602.318186] [<ffffffff8113dca8>] ? handle_mm_fault+0x1f8/0x350 [ 602.318195] [<ffffffffa0040def>] cciss_ioctl+0x29f/0x3e0 [cciss] [ 602.318204] [<ffffffffa0040f76>] do_ioctl+0x46/0x70 [cciss] [ 602.318214] [<ffffffffa00412fe>] cciss_compat_ioctl+0x1e/0xd8 [cciss] [ 602.318223] [<ffffffff81309ecd>] compat_blkdev_ioctl+0x32d/0x4b0 [ 602.318232] [<ffffffff811c838d>] compat_sys_ioctl+0xad/0x240 [ 602.318241] [<ffffffff81667470>] cstar_dispatch+0x7/0x2e [ 722.316070] INFO: task .hpacucli:1384 blocked for more than 120 seconds. [ 722.338386] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. ... and so on until I reboot the machine. When the machine is back up and I examine the array configuration in hpacucli, the new voume is present and marked "OK". The problem is also present in kernel-ppa's v3.4-precise: pjdc@prat:~$ cat /proc/version Linux version 3.4.0-030400-generic (apw@gomeisa) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1) ) #201205210521 SMP Mon May 21 09:22:02 UTC 2012 so I will tag as unfixed upstream. I am also marking as "Confirmed", being unable to run apport-collect when reproducing on 3.2, since the machine has no network due to bug #1005699. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1006212/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
