Re: SS5/170 hanging with 2.2.14 kernel

2000-03-01 Thread Stephen Zander
> "Romain" == Romain Dolbeau <[EMAIL PROTECTED]> writes:
Romain> Not responding to Stop-A is unusual. But there's an easy
Romain> way on the SS5/170 : the TurboSPARC chip is buggy, and
Romain> there's a code sequence that lock up the CPU...

P'rhaps, thoug I have more thqan one SS5/170 running happily without
major dramas.  I've actaully found a repeatable failure mode with the
HME card, though.

ping -f 

generates and opps the first time and locks hard if repeated so I
think there's some interaction between the 100Mb interrupt spped and
the CPU/MMU.

Romain> # int main(int argc, char** argv) { white(1) ; } #

I'm guessing that should be 'while' not 'white' :)

-- 
Stephen

"Farcical aquatic ceremonies are no basis for a system of government!"


Re: SS5/170 hanging with 2.2.14 kernel

2000-02-29 Thread Romain Dolbeau
> I get no opps, but the machine will not respond to anything including
> Stop-A.  Did anything significant change between .13 & .14 for
> sparc32?  Is there anything I should enable to help provide kernel
> dumps?

Not responding to Stop-A is unusual. But there's an easy way on
the SS5/170 : the TurboSPARC chip is buggy, and there's a code
sequence that lock up the CPU... and gcc _can_ generate
thay code sequence ! It happens on Solaris, anyway...

try compiling:

#
int
main(int argc, char** argv)
{
 white(1)
 ;
}
#

use gcc -O1 (or -O2, can't remember), and lockup your SS5/170... :-(

_maybe_ that's what you are seeing, if it happens only on the 5/170.

HTH

-- 
DOLBEAU Romain   | l'histoire est entierement vraie, puisque
ENS Cachan / Ker Lann| je l'ai imaginee d'un bout a l'autre
[EMAIL PROTECTED]|   -- Boris Vian


Re: SS5/170 hanging with 2.2.14 kernel.

2000-02-25 Thread Ben Collins
On Thu, Feb 24, 2000 at 07:58:20PM -0800, Stephen Zander wrote:
> > "Stephen" == Stephen Zander <[EMAIL PROTECTED]> writes:
> Stephen> After recently upgrading my kernel version and adding a
> Stephen> HME card to my SS5/170, I'm now experiencing random
> Stephen> lockup on a very regular basis.  I also added support for
> Stephen> CS4231 at the same time as I added HME support and am now
> Stephen> using fbgetty if that makes any difference.
> 
> Well, backing down to .13 didn't help so now I'm left wodering about
> the sunhme driver.  Currently, the box is up on .14 with the lance
> card active and the hme quiessed and all is fine.  I'll give it
> something to do & see..

Strange, the hme driver has been working fine for me on 2.2.9 an up to
2.2.15-pre9. Then again this is on sparc64, so it is likely related to
just sparc32.

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
` [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED] '
 `---=--===-=-=-=-===-==---=--=---'


Re: SS5/170 hanging with 2.2.14 kernel.

2000-02-25 Thread Stephen Zander
> "Stephen" == Stephen Zander <[EMAIL PROTECTED]> writes:
Stephen> After recently upgrading my kernel version and adding a
Stephen> HME card to my SS5/170, I'm now experiencing random
Stephen> lockup on a very regular basis.  I also added support for
Stephen> CS4231 at the same time as I added HME support and am now
Stephen> using fbgetty if that makes any difference.

Well, backing down to .13 didn't help so now I'm left wodering about
the sunhme driver.  Currently, the box is up on .14 with the lance
card active and the hme quiessed and all is fine.  I'll give it
something to do & see..

-- 
Stephen

"If I claimed I was emporer just cause some moistened bint lobbed a
scimitar at me they'd put me away"


SS5/170 hanging with 2.2.14 kernel.

2000-02-24 Thread Stephen Zander

After recently upgrading my kernel version and adding a HME card to my
SS5/170, I'm now experiencing random lockup on a very regular basis.
I also added support for CS4231 at the same time as I added HME
support and am now using fbgetty if that makes any difference.

I get no opps, but the machine will not respond to anything including
Stop-A.  Did anything significant change between .13 & .14 for
sparc32?  Is there anything I should enable to help provide kernel
dumps?

I'm now rebuilding a .13 kernel to see if it makes a difference as the
machine had been running flawlessly prior to this upgrade.

kernel: 2.2.14
compiler: gcc 2.95.2
/proc/cpuinfo:
cpu : Fujitsu TurboSparc MB86907
fpu : reserved
promlib : Version 3 Revision 2
prom: 2.29
type: sun4m
ncpus probed: 1
ncpus active: 1
BogoMips: 169.57
MMU type: Fujitsu TurboSparc
invall  : 1307
invmm   : 1531
invrnge : 2454
invpg   : 23272
contexts: 256

-- 
Stephen

"A duck!"