I, too, am seeing this.
[ 1.030] cpu_topology_init: info bogus, faking it
[ 1.4812620] cpu3: 600 MHz Cortex-A53 r0p4 (Cortex V8A core)
[ 1.4812620] cpu3: DC enabled IC enabled WB enabled EABT branch
prediction enabled
[ 1.4912632] cpu3: 32KB/64B 2-way L1 VIPT Instruction cache
[
am I missing? Thanks again.
On Fri, Jul 10, 2020 at 9:19 AM Michael van Elst wrote:
> On Thu, Jul 09, 2020 at 08:53:59AM -0700, Michael Cheponis wrote:
> > It must be the dtb files.
> >
> > Yes, the console is perfect with 9.99.69 with (ahem) .17 good dtb files
>
I have been running 9.99.17 on RPi3+ and did ./build.sh current, which
produced 9.99.69 -- and it works perfectly, no garbling. I just copied
src/sys/arch/evbarm/compile/obj/GENERIC/netbsd.img to /boot/KERNEL7.IMG and
rebooted.
# sysctl -a|grep freq
machdep.cpu.frequency.target = 1400
$ grep -i ^black /usr/share/dict/words | wc
92 92 976
$ grep -i ^white /usr/share/dict/words | wc
70 70 725
It's an uphill climb, but naming
https://martinfowler.com/bliki/TwoHardThings.html is one of two hard
things. Yes, we can do better.
On Mon, Jun 15, 2020 at
$ xz -k9 really.big.file.tar (about 2 GB)
I have a 3G /c/swapfile on a rotating HD at priority 0 for swap.
*[ 1.000] NetBSD 9.99.56 (GENERIC) #0: Tue Apr 14 14:14:02 UTC 2020[
1.000]
m...@s.culver.net:/c/usr/src/sys/arch/evbarm/compile/obj/GENERIC*
*[ 102791.8683015] panic:
This particular version of 9.99.17 has been extremely stable for me for
several months. Now I tried copying the contents of sd1 to a bigger USB
(hard) disk. Didn't complete due to panic:
panic: kernel diagnostic assertion "offset < dma->udma_block->size"
failed: file
*[ 363906.7911703] unmounting file systems...[ 363909.1814446] unmounting
done[ 363909.1914472] rebootin[ 1.000] NetBSD/evbarm (fdt) booting
...[ 1.000] [ Kernel symbol table missing! ][ 1.000] pool
redzone disabled for 'kmem-8192'[ 1.000] Copyright (c) 1996, 1997,
1998,
FWIW, the last 'completely stable' -current on RPi 3B+ has been 9.99.17 as
well. I don't know what has happened, but there seem to be some
regressions from that time onward.
-Mike
On Thu, Jan 16, 2020 at 6:20 PM Robert Nestor wrote:
> I’ve got NetBSD-9.99.17 (amd64) installed and it has
*--- dependall-exec_elf32
---/c/usr/src/obj/tooldir.NetBSD-9.99.17-evbarm/bin/nbctfconvert -L VERSION
exec_elf32.o--- core_elf32.o ---# compile
exec_elf32/core_elf32.o/c/usr/src/obj/tooldir.NetBSD-9.99.17-evbarm/bin/armv7--netbsdelf-eabihf-gcc
-O2 -g -std=gnu99-Wall -Wstrict-prototypes
Dec 29 00:03:51 S /netbsd: [ 1.000] NetBSD 9.99.30 (GENERIC) #0: Fri
Dec 27 22:32:00 UTC 2019
Dec 29 00:03:51 S /netbsd: [ 1.000] m...@s.culver.net:
/c/usr/src/sys/arch/evbarm/compile/obj/GENERIC
Dec 29 00:03:51 S /netbsd: [ 28921.9058062] panic: kernel diagnostic
assertion
what does this mean? (Received last night on RPi 3B+ that has been h/w
stable):
panic: kernel diagnostic assertion "uvmexp.swpgonly + npages <=
uvmexp.swpginuse" failed: file "/c/usr/src/sys/uvm/uvm_pager.c", line 472
load averages: 3.32, 3.72, 3.93; up 0+11:45:09
09:54:27
*[ 27080.9793774] panic: kernel diagnostic assertion "!cpu_intr_p()"
failed: file "/c/usr/src/sys/uvm/pmap/pmap_tlb.c", line 980[ 27080.9793774]
cpu0: Begin traceback...[ 27080.9793774] 0xa7a29aac: netbsd:vpanic+0x16c[
27080.9793774] Bad frame pointer: 0x80ad537c[ 27080.9793774] cpu0: End
-eabihf-gcc
-O2 -pthread -std=gnu99 -Wall -Wstrict-prototypes
On Tue, Dec 24, 2019 at 7:48 AM Michael Cheponis
wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *[ 27080.9793774] panic: kernel diagnostic assertion "!cpu_intr_p
*[ 81623.3847677] panic: kernel diagnostic assertion "!cpu_intr_p()"
failed: file "/c/usr/src/sys/uvm/pmap/pmap_tlb.c", line 979[ 81623.3847677]
cpu0: Begin traceback...[ 81623.3847677] 0x9df29aac: netbsd:vpanic+0x16c[
81623.3847677] Bad frame pointer: 0x80ab79bc[ 81623.3847677] cpu0: End
Hi all,
This problem has gone away:
*[ 1.00] NetBSD 9.99.18 (GENERIC) #0: Sat Nov 30 23:05:09 UTC 2019[
1.00]
m...@s.culver.net:/c/usr/src/sys/arch/evbarm/compile/obj/GENERIC*
Thanks!
On Fri, Nov 29, 2019 at 1:56 AM Michael Cheponis
wrote:
>
>
> *[ 1.00
*[ 1.000] NetBSD 9.99.18 (GENERIC) #0: Fri Nov 29 05:33:33 UTC 2019[
1.000]
m...@s.culver.net:/c/usr/src/sys/arch/evbarm/compile/obj/GENERIC*
*...*
*[ 1.6966742] vfp2 at cpu2: NEON MPE (VFP 3.0+), rounding, NaN
propagation, denormals[ 1.7566824] sdmmc0 at bcmsdhost0[
etc/MAKEDEV.tmplmakedevs:cd ${.CURDIR} && ${HOST_SH}
MAKEDEV2manpage.sh.include http://bsd.man.mk>>.include
http://bsd.subdir.mk>>*
On Thu, Jul 25, 2019 at 12:40 PM Michael Cheponis <
michael.chepo...@gmail.com> wrote:
> Thank you. I'll have a look.
>
&
How is the ./build.sh error, below, fixed?
== 2 missing files in DESTDIR
Files in flist but missing from DESTDIR.
File wasn't installed ?
--
./usr/share/man/html8/creds_msdos.html
./usr/share/man/man8/creds_msdos.8
end of 2 missing
I'm trying to ./build.sh on an RPi 3B+ and I get this error:
*===checkflist ===> distrib/setscd
/c/usr/src/distrib/sets && DESTDIR=/c/usr/src/obj/destdir.evbarm
MACHINE=evbarm MACHINE_ARCH=earmv7hf
Here's a pretty detailed description of these flaws:
https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html
On Thu, Jan 4, 2018 at 12:25 PM, Michael Cheponis <
michael.chepo...@gmail.com> wrote:
> Guys, modern CPUs are incredibly complicated. Incredibl
Guys, modern CPUs are incredibly complicated. Incredibly. Given how
cheaply one can buy a CPU chip, it's one of the best bargains in the known
universe.
>From NYT article:
https://www.nytimes.com/2018/01/03/business/computer-flaws.html?_r=0
The Meltdown flaw is specific to Intel, but Spectre
21 matches
Mail list logo
