compiled kernels (as of 2014-04-06) and
kernels fetched from nyftp for 20140403 and 20140406.
The following older kernel works:
NetBSD rpi 6.99.38 NetBSD 6.99.38 (RPI) #0: Sat Mar 29 06:14:39 UTC 2014
bui...@b44.netbsd.org:/home/builds/ab/HEAD/evbarm-earmhf/201403290440Z-obj/home/builds/ab/HEAD/src
any reasonably observable
progress at that point.
This happens with self compiled kernels (as of 2014-04-06) and
kernels fetched from nyftp for 20140403 and 20140406.
The following older kernel works:
NetBSD rpi 6.99.38 NetBSD 6.99.38 (RPI) #0: Sat Mar 29 06:14:39 UTC 2014
bui...@b44.netbsd.org
On Sat, 5 Apr 2014, Greg Troxel wrote:
snip
I see no fails counted. Why do you think you are out of clusters? Are
you seeing that in dmesg? Or is it just a possible lockup explanation?
The mbuf/mbufcluster explanation was offered when I first reported
this several months ago.
Please
On 2014-03-23, at 6:06 PM, David H. Gutteridge wrote:
On 2014-03-20, at 6:27 PM, David H. Gutteridge wrote:
On Tue, 18 Mar 2014 at 19:17:01, Taylor R Campbell wrote:
I merged the riastradh-drm2 branch to HEAD today. This shouldn't
cause any problems for anyone, because it touched very little
scrolling (forever?) after the initial boot kernel messages.
The boot process does not seem to make any reasonably observable
progress at that point.
This happens with self compiled kernels (as of 2014-04-06) and
kernels fetched from nyftp for 20140403 and 20140406
With up-to-date sources, I'm seeing the following error on multiple
ports (including evbcf, evbppc, mac68k, sun2, vax)
cc1: warnings being treated as errors
/build/netbsd-local/src/tests/lib/libc/ssp/h_stpncpy.c: In function 'main':
/build/netbsd-local/src/tests/lib/libc/ssp/h_stpncpy.c:44:
Updating src tree:
P src/crypto/external/bsd/heimdal/heimdal2netbsd
P src/crypto/external/bsd/heimdal/dist/lib/roken/resolve.c
P src/distrib/sets/lists/debug/mi
P src/distrib/sets/lists/man/mi
P src/distrib/sets/lists/tests/mi
U src/doc/CHANGES
P src/etc/rc.d/dhcpcd
P
