Bug 221749 - kernel: BUG: soft lockup detected on CPU#0!, followed by BUG: unable to handle kernel NULL pointer dereference at virtual address 000001b8
kernel: BUG: soft lockup detected on CPU#0!, followed by BUG: unable to handl...
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-01-07 04:36 EST by andrew.berridge
Modified: 2008-08-02 19:40 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 13:19:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Output recorded in /var/log/messages (9.21 KB, text/plain)
2007-01-07 04:36 EST, andrew.berridge
no flags Details

  None (edit)
Description andrew.berridge 2007-01-07 04:36:53 EST
Description of problem:

When running "modprobe initio", to load kernel module for Initio SCSI support,
machine hangs, with the following:

kernel: BUG: soft lockup detected on CPU#0!

and also:

kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address

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

kernel 2.6.18-1.2869.fc6xen

How reproducible:

Every time...

Steps to Reproduce:
1. modprobe initio
Actual results:

Expected results:
Module loaded

Additional info:
This problem did not occur with my FC5 install, just with a brand-new FC6 install.
Comment 1 andrew.berridge 2007-01-07 04:36:53 EST
Created attachment 144998 [details]
Output recorded in /var/log/messages
Comment 2 Dave Jones 2007-03-19 18:04:37 EDT
Does this happen in the non-xen kernel too ?
(Also, try the latest kernel from updates-testing to make sure the bug is still
Comment 3 Bug Zapper 2008-04-04 01:31:09 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 4 Bug Zapper 2008-05-06 13:19:01 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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