Bug 22942 - Stack-dump before anaconda starts
Summary: Stack-dump before anaconda starts
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: Brock Organ
URL:
Whiteboard: Florence Beta-3
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-28 15:05 UTC by Inger Karin Haarbye
Modified: 2007-04-18 16:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-01-12 14:28:42 UTC
Embargoed:


Attachments (Terms of Use)
syslog (8.51 KB, text/plain)
2000-12-28 15:07 UTC, Inger Karin Haarbye
no flags Details

Description Inger Karin Haarbye 2000-12-28 15:05:54 UTC
ASUS P3V4X (VIA Apollo Pro133A Chipset)
384MB RAM
Celeron 566 (overclocked to 700)
Matrox G400 Max 32MB
Soundblaster Live!
Tekram DC-390-F SCSI-controller
Teles 16.3C (ISA-PnP isdn-card)
Intel Ethernet Express Pro 10/100 Ethernet Controller
Pioneer DVD-U03D 6xDVD 32xCD-ROM (SCSI)
Yamaha CDRW 8424 (SCSI)
Hansol 900P

Every time I install I get a (?) stack-dump on the screen after the modules
are loaded, before anaconda is starting. Is this a known problem, or should
I try to clock down my CPU?

(The installation proceed as nothing has happened - as far as I know).

I will attach "syslog" containing the stackdump.

Comment 1 Inger Karin Haarbye 2000-12-28 15:07:37 UTC
Created attachment 6765 [details]
syslog

Comment 2 Bill Nottingham 2000-12-28 16:41:00 UTC
kernel bug, assigning there.

Comment 3 Tim Waugh 2001-01-08 17:17:22 UTC
Just saw a patch reporting to fix this posted to linux-kernel.

Comment 4 Glen Foster 2001-01-11 21:16:24 UTC
This defect is considered MUST-FIX for Florence Gold release

Comment 5 Michael K. Johnson 2001-01-12 14:28:39 UTC
Tim, go ahead and add the patch (or attach it here) if it isn't
already in -ac4.

Comment 6 Tim Waugh 2001-01-12 15:12:36 UTC
This seems to be fixed already in 2.4.0-0.99.


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