Re: 2.4.20 kernel panics on boot w/ AS2100
On Fri 28 Feb 2003 at 09:35:03, Jay Estabrook said:
> > After compiling with GCC 3.2, the kernel gets a little farther -- it
> > doesn't panic until I get to "Starting up SMP secondaries" and then it
> > panics with "die_if_kernel recursion detected". So I'm now doing a
> > rebuild with 3.0 (jeez I wish I had that second processor -- recompiles
> > take forever) to see if that works better. If that still panics, I'll
> > start looking at other kernel versions.
>
> Did you make sure to answer 'Use SRM as bootloader' with YES?
If that's what CONFIG_ALPHA_SRM=y means, then yes, I did.
> Also, why bother with an SMP kernel with only one CPU? There's quite
> a bit of overhead (all the locking primitives) for SMP if its not
> required...
I specified in my original post that this is a dual-processor machine.
I also tried the Debian generic 2.2.22-smp kernel last night. It boots,
but when I start recompiling the kernel, it totally freezes the machine
with spinlocks errors. It doesn't dump any kernel panic info, just
freezes. I have to hit the "reset" button and fsck the hard drives.
As of a week ago, this machine was running Debian 2.1 with a 2.2.22
kernel that I had compiled myself, with SMP running just fine (it was
doing seti@home on both processors, plus running PostgreSQL and
compiling large programs occasionally). So I know it's not the machine
itself, but some combination of the new kernel/distro/compiler.
BTW, not being nearly as experienced with Alpha hardware as I am with
Intel, why is there no "make bzImage" or "make vmlinuz" target in the
kernel? I've been using "make vmlinux" which generates these *huge*
kernels (2.8 megs stripped) even with almost everything compiled as a
module, but I'm curious because the generic Debian kernels are about 1.2
megs, even though they have a ton of drivers compiled in.
--
Soren Harward
soren@byu.edu
Reply to: