Bug 61272 - kernel panic on first boot
kernel panic on first boot
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Brock Organ
:
Depends On:
Blocks: 61590
  Show dependency treegraph
 
Reported: 2002-03-15 15:16 EST by Issue Tracker
Modified: 2007-04-18 12:40 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-04-10 15:43:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
serial capture of cciss system (DL380) kernel panic (8.70 KB, text/plain)
2002-03-20 16:32 EST, Mike McLean
no flags Details

  None (edit)
Description Issue Tracker 2002-03-15 15:16:08 EST
Description of Problem:
Server : DL360 G2 
OS      : RedHat 8.0 beta 1  && beta 2
Boot ctlr : Embedded Smart Array 5i ctlr (cciss - RAID 1) 

RedHat 8.0 installation completed on DL 360G2(GRUB). At the end of installation
following error messages obeserved on the screen. 

                                            
/usr/lib/anaconda/iw/progress_gui.py:98: DeprecationWarning : Use
GtkListStore/GtkTreeView 
apply(self.dist.set_text, self.status["remaining"]["time"]+("%s"
%formatTime(remainingTime),) 
                                            
/usr/lib/anaconda/iw/progress_gui.py:98: DeprecationWarning : 
self.totalprogress.update (float(self.sizeComplete) / self.toatlSize. 

Rebooted the system after installation. kernel panic is observed with the
folowing message. 

mount : error 2 mounting ext 3 
pivtroot: pivot_root(/sysroot, /sysroot/initrd) failed : 2 
Kernel panic : No init found : Try passinf init = option to kernel. 

This also happens on DL 330G2..
Comment 1 Jeremy Katz 2002-03-18 15:03:37 EST
There's at least some confusion here since the messages given would only occur
in beta1 and not in beta2.  What does the bootloader config look like?
Comment 2 Mike McLean 2002-03-19 14:16:59 EST
I'm seeing this with Skipjack-re0318.1 on 2 different DL380s.

One has the Smart Array 5i (cciss) controller.  The other has an "Integrated
Smart Array Controller (ver 1.40)" (cpqarray).

Both are giving me the kernel panic as above (although I have not personally
observed the end of installation message -- these wer kickstart installs).
Comment 3 Mike McLean 2002-03-20 16:31:13 EST
With a newer tree (Skipjack-re0320.0) I'm still seeing the cciss lock, but the
cpqarray seems to have booted.

I have serial captured the boot messages, will attach.
Comment 4 Mike McLean 2002-03-20 16:32:42 EST
Created attachment 49267 [details]
serial capture of cciss system (DL380) kernel panic
Comment 5 Mike McLean 2002-03-20 16:35:06 EST
In the above capture, there is a notable pause (several seconds) between the
following two lines:

blk: queue f7fb9e1c, I/O limit 4095Mb (mask 0xffffffff)
Loading sym53c8xx module


Comment 6 Matt Wilson 2002-03-21 11:21:42 EST
Is this system set up in the lab?
Comment 7 Ben Levenson 2002-03-21 11:35:49 EST
At least one of these boxes (the 2-U DL380) has a symbios SCSI adapter in it. 
I'm guessing that the panic has to do w/ the 'mkinitrd' errors I found in the
install.log (after booting w/ linux rescue).
see bug# 60242
Comment 8 Jeremy Katz 2002-03-22 23:50:49 EST
Fixed in mkinitrd-3.3.6 and newer
Comment 9 Michael Fulbright 2002-04-04 19:35:32 EST
Can the bug reporter please verify this is fixed against a recent tree?
Comment 10 Michael Fulbright 2002-04-09 14:59:53 EDT
Could compaq please test the latest Skipjack beta so we can confirm this fix?
Comment 11 Mike McLean 2002-04-10 15:43:41 EDT
I haven't seen this bug with any of the recent trees (and that would include
Skipjack public beta 2).  My testing includes the two machines in the lab that
manifested the bug before (one cciss and one cpqarray).
Comment 12 Jeremy Katz 2002-04-10 18:23:18 EDT
Sounds good; thanks for testing Mike

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