Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 236275 - kernel: BUG: soft lockup detected on CPU#0!
kernel: BUG: soft lockup detected on CPU#0!
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2007-04-12 16:02 EDT by Bill Nottingham
Modified: 2014-03-16 23:06 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-30 14:47:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Nottingham 2007-04-12 16:02:03 EDT
Description of problem:

SSIA. No traceback. :/

Started with 1.3045.fc7 or so. No real rhyme or reason. Happens
when opening windows in X, or switching desktops, or sitting idle.

(Note: not using DRI/compiz.)

Version-Release number of selected component (if applicable):

Comment 1 Dave Jones 2007-04-13 15:07:19 EDT
*hand waving happens here*

Not really much to do without a traceback.
Though given softlockups stellar track record, I'm tempted to increase the
amount of time it waits before it cries wolf.
Comment 2 Dave Jones 2007-04-13 15:09:16 EDT
hmm, then again, it's at 10*HZ right now, which should be ridiculously high already.

What X driver is this?   Any chance of serial console or netconsole capture?
Comment 3 Bill Nottingham 2007-04-13 15:12:48 EDT
FWIW, most of the time it just hardlocks - only got the 'BUG' message once.
No serial port, will try !wireless to see if I can get a netdump. radeon driver.
Comment 4 Bill Nottingham 2007-04-30 14:47:21 EDT
Closing. This box has steadily locked up more and more often, and now
occasionally dies beeping in the BIOS.

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