Ok... so I thought I would try 2.3.5 to get some of the latest bug
fixes...
I get:
ksyms.c:138: `_set_ve' undeclared here (not in a function)
ksyms.c:138: initializer element for `__ksymtab__set_ve.value' is not constant
make[2]: *** [ksyms.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.3.5/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.3.5/kernel'
make: *** [_dir_kernel] Error 2
Basically, I want the latest, greatest kernel with the least bugs and
holes, so does anyone have a suggestion?
-----------------------------------------------------------------
Randy Carpenter - UNIX Systems Manager First Network Group
[EMAIL PROTECTED] Wapakoneta, OH
-----------------------------------------------------------------
On Thu, 10 Jun 1999, Anton Blanchard wrote:
> Date: Thu, 10 Jun 1999 12:03:25 +1000
> From: Anton Blanchard <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: Randy Carpenter <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: SMP crash...
> Resent-Date: 10 Jun 1999 03:24:15 -0000
> Resent-From: [EMAIL PROTECTED]
> Resent-cc: recipient list not shown: ;
>
>
> > I have a Sparc10 (dual SM51) running Red Hat 5.2, with kernel 2.2.1. It
> > had been running for quite a long time, until it crashed today. On the
> > console was this message repeated:
> >
> > spin_lock_irqsave(f014aa60) CPU#0 stuck at f00483a0, owner
> > PC(f0048714):CPU(0)
> > spin_lock_irqsave(f014aa60) CPU#0 stuck at f00483a0, owner
> > PC(f0048714):CPU(0)
> >
> > I am going to upgrade to a later kernel and such, but want to know if this
> > particular error pointed to anythign specific.
>
> There were a few sparc32 SMP locking problems until somewhere around 2.2.7.
>
> Anton
>
> --
> To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
>
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
