Re: Panics going multiuser with NetBSD 8, 9, current

[Frank Wille <frank%phoenix.owl.de@localhost>]

John Klos wrote:

> Currently it's exactly that - an A4000, a CyberStorm Mk3, and the A4066 
> card.
>
> I don't know from where the serial number is retrieved, but maybe
> that's a CSPPC thing.

CSMk3 and CSPPC have the same product id. So as long as we don't run a PPC
function test the only way to differentiate them was the serial number,
which starts with an 'F' for the MK3.

You serial number seems to be empty. Or maybe it is somewhere else, due to a
Flash ROM update? dev/p5bus.c assumes to find it at 0xf00010.

But this is just a side note. It has definitely nothing to do with your
problems. Our boards are still treated the same by the kernel.


> I tried to build a kernel with those. DEBUG_KERNEL_START gave this 
> failure:
>
> --- amiga_init.o ---
> /usr/current/src/sys/arch/amiga/amiga/amiga_init.c: In function 
> 'start_c_finish':
> /usr/current/src/sys/arch/amiga/amiga/amiga_init.c:804:7: error: 'id' 
> undeclared (first use in this function)
>    804 |  if ((id >> 24) == 0x7D) { /* mapping on, is_draco() is valid
>        */ |       ^~

*Sigh*
Seems that nobody tested that option since a very long time. You may try it
again with
  no options DRACO
in your config file.


> FYI - in NetBSD 9 and, I think, current, my A1200 can't write to the CF 
> card that it could write to just fine with NetBSD 8, but I think that's
> a separate issue.

Probably. But tell us what happens. An error, a panic?

I seem to remember that there have been some effort to make the CF port work
with 16-bit network cards over the last years...


> ...and I get the same panic when booting via NFS...

Wow... this is really strange. Would be nice to have a second CSPPC/Mk3
A4000 for comparison. I may try to test with mine (which also has a CSPPC)
but it is defective - the Zorro bus no longer works correctly.


> The only thing I can think of that MIGHT be a factor is that this
> machine has no clock battery because it was removed ages ago.

Same for my A3000. I always set the clock via NTP.


> What if
> this has something to do with a crazy date or something else stored in
> the battery backed RAM?

As far as I know NetBSD will always use the last time from the file system,
after it displayed "WARNING: CHECK AND RESET THE DATE!".

-- 
Frank Wille