Bug 173020 - Kernel panic when loading aic7xxx and 4 GB memory available
Kernel panic when loading aic7xxx and 4 GB memory available
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-11-12 11:48 EST by Göran Uddeborg
Modified: 2015-01-04 17:23 EST (History)
2 users (show)

See Also:
Fixed In Version: 2.6.15-1.1830_FC4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-07 11:43:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
(Serial) console output during boot. (12.71 KB, text/plain)
2005-11-12 11:48 EST, Göran Uddeborg
no flags Details

  None (edit)
Description Göran Uddeborg 2005-11-12 11:48:45 EST
Description of problem:
The kernel panics on bootup when loading aic7xxx.  If I restrict memory to 3 GB
(parameter men=3G) it comes up fine.

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

How reproducible:
Every time

Steps to Reproduce:
1. Boot

Additional info:
This is very similar to bug 167049.  It is not identical.  Before the SCSI
driver found units that were not there, now it gets a panic.  But the problem
appears at the same stage during boot, and it is sensitive to the fourth GB of
memory in the same way.
Comment 1 Göran Uddeborg 2005-11-12 11:48:46 EST
Created attachment 120985 [details]
(Serial) console output during boot.
Comment 2 Göran Uddeborg 2005-12-02 04:23:41 EST
The problem is still present in 2.6.14-1.1644_FC4smp
Comment 3 Dave Jones 2006-02-03 02:03:47 EST
This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.
Comment 4 Göran Uddeborg 2006-02-07 11:43:33 EST
It looks like 2.6.15 solved this problem.  It works now.

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