NetBSD 3.1 sysinst ifconfig error on SE/30

[Kazuyuki Inanaga]

Hi,

On 2006/11/16, at 5:13, Nuno Teixeira wrote:
> I always used kernel SBC with 1.6* and 2* with success because they  
> were
> the ones who realy work ok rebooting and shutdown without panic.  
> There's
>  the reason y I allways choose SBC.
>
> Now something change...

Yes, I think so, too.

> I'm working on my SE/30 right now...


On 2006/11/16, at 9:30, Tim & Alethea Larson wrote:
> I did a minimal (kernel and base only) upgrade (2.1 -> 3.1) on my  
> Mystic CC today, with no problems.  GENERIC kernel.


I'm glad to hear that. :)
Let's talk with all together about nice points of NetBSD-3.1.

Regards,
Kazu Inanaga

[Aaron J. Grier-2]

On Wed, Nov 15, 2006 at 07:57:17PM +0100, Hauke Fath wrote:
> The '030 Macs have an interrupt hierarchy where the timer interrupts
> have a low priority, which means that ticks get lost as soon as there
> is any significant I/O load. The Quadra 700 and later '040 Macs can be
> switched to a different hierarchy which gives the timer interrupts
> higher priority.  Apple apparently learned from its A/UX experiences.

I always wondered which device drivers were worst about not letting
clock ticks run, and seeing if there were ways to "flash" in the driver
to let the clock ticks update.

--
  Aaron J. Grier | "Not your ordinary poofy goof." | agrier@...
              "silly brewer, saaz are for pils!"  --  virt

[Hauke Fath]

At 19:50 Uhr +0100 17.11.2006, Aaron J. Grier wrote:

[lost clock interrupts]

>I always wondered which device drivers were worst about not letting
>clock ticks run, and seeing if there were ways to "flash" in the driver
>to let the clock ticks update.

The problem may be that the Macintosh is DMAless (apart from the IIfx and
the Quadra 840av, where we don't support the feature), and its cpu does all
I/O. This is as good as a hard realtime constraint: If you "shell out"
from, say, the SCSI driver, to work on a clock interrupt, and don't return
in time, you may lose a SCSI block.

I can say for sure that in the iwm(4) driver, running at splhigh is not to
protect common data structures, but to do realtime work. iwm(4) is
definitely the worst offender here (late-seventies 8-bit technology), and
an alien in a multitasking world...

        hauke

--
"It's never straight up and down"     (DEVO)

[Kazuyuki Inanaga]

On 2006/11/17, at 12:30, I wrote:
> So, can I say "Our all '030s get panic at reboot in NetBSD-3.1,
>
>    How about IIci ?
>    Does anyone know "my '030 can reboot without panic" ?

I installed NetBSD-3.1(GENERICSBC) to 2 IIcis. They work fine,
but get panic at reboot, same as "NetBSD Problem Report #35068".

It seems that GENERIC kernel works on IIci (with DiiMO, not well
tested), GENERIC kernel get same panic at reboot on IIci, too.


E-Machines Futura II LX (NuBus video card) works at 16 bit
mode (Thousands of colors) on IIci / NetBSD-3.1 X.
(Futura II LX does not work on Quadra700 at 16 bit mode.)

'030 accelerator with IIci / NetBSD-3.1
1) Daystar 50MHz / Power Central /
    onBoard Video
       PowerCache ON:  Freeze at the line wsmouse0 ... in the Boot  
sequence.
       PowerCache OFF: OK

2) DiiMO 50MHz / DiiMO 030 /
    with Futura II LX
       Cache ON:       panic: cnopen: no console device
       Cache OFF:      OK
    onBoard Video
       Cache ON:       OK

Apple cache card      No problem found

 >panic: cnopen: no console device
I've seen this panic on LC ('020) with '030 accelerator.
It appears sometimes on the accelerated machines.

NetBSD-3.1 is good for IIci, 4.0 release will come soon ?

Thanks,
Kazu Inanaga