Subject: Re: Snapshot
To: None <matias@k-bell.com>
From: Colin Wood <cwood@ichips.intel.com>
List: port-mac68k
Date: 06/25/1999 10:34:51
[Mat_as] Giovannini wrote:
> Um, I tried GENERIC-5, GENERICSBC-5 (no need actually, but just to be
> sure), and MRG-5 on my Q800/20Mb/500Mb.
> GENERIC kernels since 1.4 release have this weird effect on me, er, my
> machine, that the keyboard (Series II Extended ISO) is initially WITH
> CAPS LOCK ON. MRG, on the other hand, correctly boots in caps lock off.

needless to say, this is really, really, weird....i can't think of
anything offhand which would cause this to occur.  you can toggle it off,
right?
 
> If things go right, should I install the rest of the snapshot?

if you really want to run -current, sure ;-)

> Is there
> any account of what changes from snapshot to snapshot?

the source-changes mailing list will give you some idea.  in general, if
you're going to be running -current, i'd suggest subscribing to both
source-changes and current-users (although the latter has a relatively
high noise ratio).  you can also look at the Changes file which is
available on both the webserver and the ftp server.

> While I'm at it (I know, this is the last thing), I'm having this
> problem much too frequently:
> 
> $ zcat /var/log/messages*.gz | grep exhausted
> Jun 11 11:22:17 nameserver /netbsd: sn0: receive buffer area exhausted
> Jun 12 13:13:15 nameserver /netbsd: sn0: receive buffer area exhausted
> Jun 15 17:44:01 nameserver /netbsd: sn0: receive buffer area exhausted
> Jun 16 13:38:02 nameserver /netbsd: sn0: receive buffer area exhausted
> Jun 17 10:09:08 nameserver /netbsd: sn0: receive buffer area exhausted
> Jun 22 16:38:05 nameserver /netbsd: sn0: receive buffer area exhausted
> Jun 24 13:28:41 nameserver /netbsd: sn0: receive buffer area exhausted
> Jun 24 17:30:40 nameserver /netbsd: sn0: receive buffer area exhausted
> 
> I "ifconfig sn0 up" a couple of times, but it gets worse and worse until
> I better reboot it. I would appreciate ideas about this.

you got me on this one....either you're getting too many packets too
quickly or else you ethernet interrupts aren't being serviced fast
enough...

later.

colin