Re: SCSI support

On Fri, 31 May 2002 18:49:38 +0200, Christian Limpach wrote:

Hi again.

> Hi!
> 
> > It happens each time I try to use it. It's up for several minutes
> > and then the above happens. Machine itself wasn't doing anything, it
> > was waiting for my input since I've run disklabel -e -I sd0. As for
> > the network, yes it's rather busy. Every now and then I also see
> > kernel messages about some ARP issues (I think it's about mismatched
> > addresses, but I didn't pay attention to it). Perhaps it would help
> > if I try to hook it up to a switch where it would see less traffic ?
> > Note that I didn't see such issues when I was using kernel w/o SCSI
> > support (I think it was 1.5.1) and doing FTP transfers and such. But
> > I guess this doesn't mean much since only network card was active at
> > the time.
> 
> could you try a recent kernel without SCSI support, like:
> ftp://lola.pin.lu:21/pub/NetBSD/arch/next68k/snapshot/20020520-current/binar
> y/kernel/netbsd-GENERIC.gz

I have tried it. Unfortunately this one is even worse ;(. See attached
file - it scrolls so fast I can't even see anything. Luckily I can boot
with your SCSI kernel and run dmesg afterwards. Does this help at all ?
messages file is missing some stuff at the beginning, due to a crash I
guess. If you need it let me know and I will try to grab that somehow.
I think it goes boom right after it mentions wsdisplay0 or somesuch.
The last part of messages file is from the reboot after I switched to
the "SCSI" kernel which works for several minutes (the one I mentioned
in my initial report).

> Also, your previous kernel might have been compiled without DIAGNOSTIC
> in which case those errors are silently ignored (and packets dropped).
> If you can build a kernel, then you could also try a kernel with SCSI
> but with the panic commented out, it's in
> sys/arch/next68k/dev/mb8795.c around line 1066.

That may well be. I have always used generic kernel from netbsd.org.
I doubt I can compile the kernel right now since generic kernel doesn't
even work.

> Could you also write down those ARP messages you mentioned?  Or
> anything that would help to let me reprdouce this problem would make
> it easier to fix it ;-)

Here, I grabbed one from logs, I think it can be safely ignored :

Jun 24 13:11:55 next /netbsd: arp info overwritten for 10.17.3.115 by  
00:06:53:f5:55:70

As for reproducing it - I don't have any special means to do it. I just
power it on, boot it and wait 10 - 20 minutes and it goes boom.

Thanks,
    Goran

-- 

Writing about music is like dancing about architecture.
    -- Frank Zappa