Hide Forgot
Description of problem: dmesg shows BUG: soft lockup - CPU#16 stuck for 60s I used machine with 32CPU Version-Release number of selected component (if applicable): util-linux-2.13-0.56.el5 How reproducible: non deterministic I could see this issue only once on machine with 32CPU Steps to Reproduce: 1. take a machine with 32 CPU 2. mount / mount --move / umount, restart nfs do it repeatedly 3. dmesg shows 0000000300000000 000000000000000a<3>BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] Actual results: 0000000300000000 000000000000000a<3>BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] Expected results: no such a info about bug in dmesg Additional info:
dmesg showed: Checking dmesg for specific failures! BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] 0000000300000000 000000000000000a<3>BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] End of log.
there is log from console: Call Trace: [<ffffffff8012e072>] avc_has_perm+0x46/0x58 [<ffffffff8002853b>] do_wait+0xa10/0xae4 [<ffffffff8008e85b>] default_wake_function+0x0/0xe [<ffffffff800302a2>] sys_rt_sigprocmask+0xc0/0xd9 BUG: soft lockup - CPU#16 stuck for 60s! [events/16:114] CPU 16: Modules linked in: vfat fat md5 nfs nfsd exportfs nfs_acl auth_rpcgss autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf be2iscsi ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp bnx2i cnic ipv6 xfrm_nalgo crypto_api uio cxgb3i libcxgbi cxgb3 8021q libiscsi_tcp libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi loop dm_multipath scsi_dh video backlight sbs power_meter hwmon i2c_ec i2c_core dell_wmi wmi button battery asus_acpi acpi_memhotplug ac parport_pc lp parport joydev sr_mod cdrom sg netxen_nic tpm_tis i7core_edac tpm edac_mc tpm_bios serio_raw pcspkr hpilo dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod ata_piix libata shpchp cciss sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 114, comm: events/16 Not tainted 2.6.18-266.el5 #1 RIP: 0010:[<ffffffff80077761>] [<ffffffff80077761>] __smp_call_function_many+0x96/0xbc RSP: 0018:ffff81023fa0fd40 EFLAGS: 00000297 RAX: 0000000000000019 RBX: 000000000000001f RCX: 0000000000000000 RDX: 00000000000000ff RSI: 00000000000000ff RDI: 00000000000000c0 RBP: ffff81023fa0fe10 R08: 0000000000000020 R09: 0000000000000020 R10: ffff81023fa0fce0 R11: 0000000010008040 R12: ffffffffffffff10 R13: ffffffff8008d3ad R14: ffff81023fa0fda0 R15: ffffffff80154677 FS: 0000000000000000(0000) GS:ffff810243b139c0(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 00002b653eca5830 CR3: 000000033e5d6000 CR4: 00000000000006a0
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.8 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
I would like to know whether the bug have been fixed after upgrading to Red Hat Enterprise Linux 5.8 now.
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 5, and therefore is being closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide a sufficient business justification in order to re-open it.