I have attempted to install wolverine on an AlphaServer 1000A/300 here
twice (once in X and once in text). The X install froze part of the way
through with no message, while the text install gave me:
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
It crashed while I wasn't looking (of course), but the CD was ejected on
the text install, so it may have been about to request disc 2 when it
crashed. I was doing a fairly minimal Custom install with only Development
and Kernel Development package groups selected.
I don't think it is anything hardware related; I installed 7.0 on this
system okay and just recently installed Digital Unix 4.0F on it as well
(this is my test machine).
Brock, do we have an AlphaServer 1000A/300 here?
I found one Alphaserver 1000 4/266 but it's not the same model,.. heck I'll use
that instead it's roughly the same.
Thus Far it seems to be installing fine... in fact it has installed fine after
Can you give me some extra info like what boot kernel it's using, what the HW
config is etc?
I used /kernels/vmlinux.gz (the only kernel I see on the CD). The
system has 512MB RAM, a pair of 2G hard drives (RZ29B), and the standard
CD-ROM (RRD45) and tape drive (TLZ07). The only card plugged in is the
ethernet card (standard DEC Tulip 21140 card).
I did a text install with no package groups selected, and it went okay.
The problem appears to be something with changing the CD maybe? The
crash in the text install was with "ncompress" displayed as the package
about to be installed, which is on disc 2 (disc 1 was ejected but the
prompt for disc 2 was not shown).
I'll do some more tests with the other drive (for the install that
worked I only installed to the first drive). I'll stay in text mode so
I can see any errors, but when it crashed, it completely froze up, so I
don't know that that will help.
Okay, I just did another install (that took two discs) and it worked
okay. The others were all "Custom" installs, for this one I did a
"Server" install and selected "DNS server". It got to ncompress, asked
for the second disc, I loaded it, and it went on and finished.
I don't know what happened the first two times; I try some more things
and let you know if it happens again.
I'm reopening this bug.
Have you tried an install with software RAID partitions? I am getting
this when I do the following:
1) Boot the system and boot the CD with "boot -fl 0 dka400"
2) The X installer loads and I go through mostly default selections (I
chose "Server" for the install type).
3) I have two disks. I partition them identically (using fdisk) and
then set up software RAID (I make the partitions type "fd").
4) I chose only "DNS Server" at the package selection screen (I didn't
choose "select individual packages").
5) The installer created the RAID partitions and filesystems, but when
it tried to format the swap space, it crashed with the same kernel
I did this several times with a couple of variations (did a "Custom"
install and selected individual packages, but still with software RAID)
and got the same kernel panic.
Has anyone tested software RAID on Alpha with this kernel?
Yes I've tested sw raid0 on a UP2000
/dev/sda1 54441 36726 14904 72% /boot
/dev/md0 103636992 5518220 92854248 6% /compile
/dev/hde6 3096240 638000 2300892 22% /home
Timing buffered disk reads: 64 MB in 9.59 seconds = 6.67 MB/sec
Timing buffered disk reads: 64 MB in 2.56 seconds = 24.97 MB/sec
Timing buffered disk reads: 64 MB in 1.30 seconds = 49.37 MB/sec
and I've been banging on this machine for oh,.. a month or so now
Linux dhcpd156.meridian.redhat.com 2.4.3-10smp #1 SMP Thu May 31 23:19:52 EDT
2001 alpha unknown
Well, all my problems are with RAID1. I sent some oopses to bug #40586,
which has been marked as a duplicate of #38791, but they are really two
different things. #40586 is that software RAID1 crashes, while #38791
is that software RAID (any level) doesn't autorun from the kernel on
I hate to keep beating a dead horse, because if nobody else is seeing
this then I guess I've just got something weird going on. I'm 99.999%
sure it isn't hardware though; I had no hardware trouble with Red Hat
7.0, Digital Unix 4.0G, or Tru64 5.1 on this box.
I have no trouble reproducing it under 7.1 RC1; I just boot up and try
to ssh in (my home directory is on the RAID1 filesystem of /usr/local).
I cannot log in and I get a kernel oops from sshd. I am running a
kernel with my patch (from #38791) and the RAID levels compiled in to
the kernel instead of modules (I was working to having the root
filesystem RAID as well). I get the same results out of the stock Red
Hat kernel though (where RAID is started by the init scripts).
Have you had the opepertunity to try this out on teh gold CD's? ie real 7.1 yet?
Yes, I tried the seawolf CDs when the hit the beta site. I still get
the same thing - oops in raid1_read_balance.
Welcome to RH 7.2...