Re: macppc vs evbppc binary packages

>> > > We are trying to build packages on some evbppc systems (under
>> > > -6/current) and finding them a bit crashy under load.
>> >
>> > Oh, you do?  I wonder if I'm seeing the same problem...  I
>> > upgraded one of my macppc systems to 6.0_BETA in order to build
>> > packages for that, and started a single-threaded build.  It is
>> > now most likely sitting in DDB on the (vga) console back in my
>> > office while I'm on the road this week...  Previously I've not
>> > experienced such crashes with 4.0, 5.0 or 5.1.
>>
>> Unfortunately I made the same experience with macppc and ofppc. Since
>> 5.99.4x, which was quite usable, the number of problems were constantly
>> growing.
>
> True, I've seen the same, especially with SMP.
> Very recent -current seems to do a lot better though, my dual
> G4 is still running 6.99.3  with both CPUs online and build.sh
> -j4 - previously it would hang or panic under moderate IO load,
> even a build on another machine with sources via nfs from the
> G4 would trigger it.
>
> So, my 2c:
> try -current and see what happens.

I've booted 6.99.5 on my macppc, and still "no go".  It stayed
on-line for a bit longer than 6.0_BETA, but eventually all
network traffic seized up and I had to resort to the power
button.

It's unfortunate that I can't give more diagnostics -- the VGA
output doesn't appear to be there.  I'll give it a couple more
tries with OPT-CMD-O-F during the chime to see if I can get it to
give some output to the VGA screen.  If it doesn't, and appears
to sit in OF, is there some command I can type "blindly" to
trigger a screen re-initialization?

I was pretty sure I put something to init the screen in the nvram
on the mac mini before I installed NetBSD, but it's a long time
ago since I did it...

Regards,

- Håvard