Bug 805018

Summary: bcrmsmac: BUG: soft lockup - CPU#1 stuck for 21s! [wpa_supplicant:882]
Product: [Fedora] Fedora Reporter: Ví­ctor Daniel Martínez O. <vdanielmo>
Component: kernelAssignee: John W. Linville <linville>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: arend, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7fdea311ecfa9d65edc8880a08364462f0be97fb wireless bcrmsmac first=3.3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-19 22:46:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Ví­ctor Daniel Martínez O. 2012-03-20 13:12:00 UTC 
libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        BOOT_IMAGE=/vmlinuz-3.3.0-0.rc7.git0.3.fc17.x86_64 root=/dev/mapper/vg_sistemas6-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_sistemas6/lv_swap KEYTABLE=us rd.lvm.lv=vg_sistemas6/lv_root rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
kernel:         3.3.0-0.rc7.git0.3.fc17.x86_64
reason:         BUG: soft lockup - CPU#1 stuck for 21s! [wpa_supplicant:882]
time:           Tue 20 Mar 2012 07:49:44 AM COT

backtrace:      Text file, 5848 bytes

smolt_data:
:
:
:General
:=================================
:UUID: 8490ba6b-9fe7-4a60-ad5e-3b0f4ba6a63d
:OS: Fedora release 17 (Beefy Miracle)
:Default run level: Unknown
:Language: en_US.utf8
:Platform: x86_64
:BogoMIPS: 4787.76
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Core(TM) i3 CPU       M 370  @ 2.40GHz
:CPU Stepping: 5
:CPU Family: 6
:CPU Model Num: 37
:Number of CPUs: 4
:CPU Speed: 2399
:System Memory: 3728
:System Swap: 5791
:Vendor: Dell Inc.
:System: Latitude E5410 0001
:Form factor: Laptop
:Kernel: 3.3.0-0.rc7.git0.3.fc17.x86_64
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Enforcing
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:
:
:Devices
:=================================
:(32902:68:4136:1065) pci, agpgart-intel, HOST/PCI, Core Processor DRAM Controller
:(5348:5760:4136:1065) pci, tg3, ETHERNET, NetXtreme BCM5761e Gigabit Ethernet PCIe
:(32902:15152:4136:1065) pci, None, SERIAL, 5 Series/3400 Series Chipset SMBus Controller
:(32902:15145:4136:1065) pci, ahci, STORAGE, 5 Series/3400 Series Chipset 4 port SATA AHCI Controller
:(32902:15113:4136:1065) pci, None, PCI/ISA, Mobile 5 Series Chipset LPC Interface Controller
:(32902:15154:4136:1065) pci, intel ips, NONE, 5 Series/3400 Series Chipset Thermal Subsystem
:(32902:15174:4136:1065) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 3
:(5348:18215:4136:16) pci, bcma-pci-bridge, NETWORK, XPS 8300
:(32902:15164:4136:1065) pci, ehci_hcd, USB, 5 Series/3400 Series Chipset USB2 Enhanced Host Controller
:(32902:9288:4136:1065) pci, None, PCI/PCI, 82801 Mobile PCI Bridge
:(32902:15204:4136:1065) pci, None, SIMPLE, 5 Series/3400 Series Chipset HECI Controller
:(4480:59426:4136:1065) pci, sdhci-pci, BASE, MMC/SD Host Controller
:(4480:58486:4136:1065) pci, yenta_cardbus, PCI/CARDBUS, N/A
:(4480:59442:4136:1065) pci, firewire_ohci, FIREWIRE, FireWire Host Controller
:(32902:70:4136:1065) pci, i915, VIDEO, Core Processor Integrated Graphics Controller
:(32902:15176:4136:1065) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 4
:(32902:15170:4136:1065) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 1
:(32902:15172:4136:1065) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 2
:(32902:15190:4136:1065) pci, snd_hda_intel, MULTIMEDIA, 5 Series/3400 Series Chipset High Definition Audio
:(32902:15156:4136:1065) pci, ehci_hcd, USB, 5 Series/3400 Series Chipset USB2 Enhanced Host Controller
:(32902:15180:4136:1065) pci, pcieport, PCI/PCI, 5 Series/3400 Series Chipset PCI Express Root Port 6
:(32902:11521:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath Architecture System Address Decoder
:(32902:11362:32902:32902) pci, None, HOST/PCI, Core Processor QuickPath Architecture Generic Non-core Registers
:(32902:11537:32902:32902) pci, None, HOST/PCI, Core Processor QPI Physical 0
:(32902:11536:32902:32902) pci, None, HOST/PCI, Core Processor QPI Link 0
:(32902:11539:32902:32902) pci, None, HOST/PCI, Core Processor Reserved
:(32902:11538:32902:32902) pci, None, HOST/PCI, Core Processor Reserved
:
:
:Filesystem Information
:=================================
:device mtpt type bsize frsize blocks bfree bavail file ffree favail
:-------------------------------------------------------------------
:/dev/mapper/vg_sistemas6-lv_root / ext4 4096 4096 13092026 11879915 11748865 3276800 3148485 3148485
:/dev/sda2 /boot ext4 1024 1024 508745 408493 382893 128016 127777 127777
:/dev/mapper/vg_sistemas6-lv_kvm WITHHELD xfs 4096 4096 37189896 32779669 32779669 148832256 148832250 148832250
:/dev/mapper/luks-3d0fc4db-33f4-4216-ae77-78014e3a23a5 /home ext4 4096 4096 26174432 12775320 11464626 6553600 6472886 6472886
:
Comment 1 Ví­ctor Daniel Martínez O. 2012-03-20 13:12:06 UTC 
Created attachment 571398 [details]
File: backtrace
Comment 2 Arend van Spriel 2012-03-20 20:04:25 UTC 
Can this be retested on a kernel with lock usage statistics enabled, ie. CONFIG_LOCK_STAT?
Comment 3 Dave Jones 2012-03-20 22:40:50 UTC 
that kernel did have that option enabled.
Comment 4 Arend van Spriel 2012-03-21 07:38:40 UTC 
(In reply to comment #1)
> Created attachment 571398 [details]
> File: backtrace

From the trace file I can only say that it is spinning. It does not tell me what process is holding the spinlock. Can you provide more trace info?
Comment 5 Stanislaw Gruszka 2012-03-21 08:43:09 UTC 
That information can be obtained by "echo t > /proc/sysrq-trigger", and then attach output of dmesg command here.
Comment 6 Dave Jones 2012-06-28 00:46:34 UTC 
*** Bug 805020 has been marked as a duplicate of this bug. ***