Bug 185747 - kernel panic booting 2.6.9-34smp on quad dual-core
kernel panic booting 2.6.9-34smp on quad dual-core
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: grub (Show other bugs)
4.0
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-17 10:50 EST by Wayne Arnold
Modified: 2011-07-27 14:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-07-27 14:03:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Wayne Arnold 2006-03-17 10:50:12 EST
Description of problem:

Updated a Boxx APEXX4 system (quad dual-core Opteron 875) Tyan S4881 from RHEL
AS 4 Update 2 (2.6.9-22.0.1smp) to Update 3 (2.6.9-34smp)  8GB memory

When attempting to boot from the new kernel, 2.6.9-34smp,  get a kernel panic on
not being able to find the Volume  /bin/lvm exited abnormally.  Booting with old
kernel 22.0.1smp works fine.  needs to use metadata to find the volume but finds it.

booting kernel
SRAT: lapic 16 too large
SRAT: SRAT not used

powernow-k8: init not cpu 0
...
powernow-k8: init not cpu 0
Red Hat nash version 4.2.1.6 starting
  Reading all physical Volumes  This may take a while...
  No volumes found
  Unabel to find volume group "VolGroup00"
Error: /bin/lvm exited abnormally
mount: error 6 mounting ext3  pid 358
mount: error 2 mounting none
switchroot: mount failed 22
umount /initrd/dev failed: 2
kernel panic - not syncing: Attempt to kill init!


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

RHEL 4 AS Update 3

How reproducible:

Always happens


Steps to Reproduce:
1. reboot the system with kernel 2.6.9-34smp
2.
3.
  
Actual results:     kernel panic

Expected results:   boot normally

Additional info:

Output from when running 2.6.9-22.0.1.ELsmp kernel

[root@lnx-boxx64 warnold]# lvdisplay
  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol00
  VG Name                VolGroup00
  LV UUID                09cw7w-TAkX-95F1-a1Oq-U5VE-Cvc5-BfIMk8
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                109.62 GB
  Current LE             3508
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:0

  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol01
  VG Name                VolGroup00
  LV UUID                ph3f0Y-StSl-56pd-eWIG-4LsU-cG9o-Lwda51
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                1.94 GB
  Current LE             62
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:1

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