Bug 757066 - [abrt] kernel: BUG: soft lockup - CPU#4 stuck for 22s! [kworker/u:6:71]
Summary: [abrt] kernel: BUG: soft lockup - CPU#4 stuck for 22s! [kworker/u:6:71]
Keywords:
Status: CLOSED DUPLICATE of bug 755154
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5cca75ec309f85e005663b1a2e8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-25 11:50 UTC by Felipe van Schaik Willig
Modified: 2011-11-28 21:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-28 18:15:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: smolt_data (2.65 KB, text/plain)
2011-11-25 11:50 UTC, Felipe van Schaik Willig
no flags Details
File: backtrace (3.47 KB, text/plain)
2011-11-25 11:50 UTC, Felipe van Schaik Willig
no flags Details

Description Felipe van Schaik Willig 2011-11-25 11:50:07 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        BOOT_IMAGE=/boot/vmlinuz-3.1.2-1.fc16.x86_64 root=UUID=8617f20d-bca8-4d30-97a2-d95013868e64 ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=br-abnt2 quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8
comment:        My laptop simply frozen.
kernel:         3.1.2-1.fc16.x86_64
reason:         BUG: soft lockup - CPU#4 stuck for 22s! [kworker/u:6:71]
time:           Fri 25 Nov 2011 08:49:21 AM BRST

backtrace:      Text file, 3558 bytes
smolt_data:     Text file, 2718 bytes

Comment 1 Felipe van Schaik Willig 2011-11-25 11:50:11 UTC
Created attachment 536205 [details]
File: smolt_data

Comment 2 Felipe van Schaik Willig 2011-11-25 11:50:14 UTC
Created attachment 536206 [details]
File: backtrace

Comment 3 John W. Linville 2011-11-28 18:15:27 UTC

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

Comment 4 Larry Finger 2011-11-28 21:57:19 UTC
For the record, bug 755154 has a patch that should fix this.


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