Automated report: NetBSD-current/i386 test failure

2021-10-28 Thread NetBSD Test Fixture
This is an automatically generated notice of a new failure of the
NetBSD test suite.

The newly failing test case is:

usr.bin/indent/t_errors:option_tabsize_very_large

The above test failed in each of the last 4 test runs, and passed in
at least 26 consecutive runs before that.

The following commits were made between the last successful test and
the failed test:

2021.10.28.21.32.48 rillig src/usr.bin/indent/args.c,v 1.64
2021.10.28.21.32.49 rillig src/tests/usr.bin/indent/t_errors.sh,v 1.7
2021.10.28.21.32.49 rillig src/usr.bin/indent/indent.c,v 1.163
2021.10.28.21.35.57 rillig src/tests/usr.bin/indent/t_errors.sh,v 1.8
2021.10.28.21.35.57 rillig src/usr.bin/indent/args.c,v 1.65
2021.10.28.21.51.43 rillig src/usr.bin/indent/indent.c,v 1.164
2021.10.28.21.51.43 rillig src/usr.bin/indent/indent.h,v 1.53
2021.10.28.21.51.43 rillig src/usr.bin/indent/parse.c,v 1.43
2021.10.28.21.56.26 rillig src/usr.bin/indent/indent.c,v 1.165
2021.10.28.21.56.26 rillig src/usr.bin/indent/indent.h,v 1.54
2021.10.28.21.56.26 rillig src/usr.bin/indent/lexi.c,v 1.106
2021.10.28.22.06.23 rillig src/usr.bin/indent/indent.c,v 1.166
2021.10.28.22.06.23 rillig src/usr.bin/indent/lexi.c,v 1.107

Logs can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2021.10.html#2021.10.28.22.06.23


Re: IDENTIFY failed

2021-10-28 Thread Jun Ebihara
From: matthew green 
Subject: re: IDENTIFY failed
Date: Fri, 29 Oct 2021 07:18:09 +1100

>> > autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for 
>> > drive 0
>> https://mail-index.netbsd.org/current-users/2021/10/27/msg041615.html
> this one has reduced timeframe, too:
>> between
>> NetBSD 9.99.91 (GENERIC) #0: Tue Oct 12 19:57:53 UTC 2021 OK
>> NetBSD 9.99.92 (GENERIC) #0: Mon Oct 25 20:32:38 UTC 2021 Failed 
> which changed how some interrupt handling works, and:
>http://mail-index.netbsd.org/source-changes/2021/10/11/msg132941.html
> which removed some delays in the probe path.  possibly this one
> is more likely to be at fault since it touches the probe path
> directly.

add 
/usr/src/sys/arch/amd64/conf/GENERIC.local
options AHCISATA_EXTRA_DELAY

compile kernel
https://cdn.netbsd.org/pub/NetBSD/misc/jun/amd64/kernel/netbsd-AHCISATA_EXTRA_DELAY-9.99.92.gz

seems ok.

Thanx.
--
Jun Ebihara


daily CVS update output

2021-10-28 Thread NetBSD source update


Updating src tree:
P src/common/lib/libc/hash/sha1/sha1.c
P src/common/lib/libc/hash/sha2/sha2.c
P src/doc/3RDPARTY
P src/doc/CHANGES
P src/etc/ntp.conf
P src/external/gpl3/gcc/dist/libsanitizer/sanitizer_common/sanitizer_linux.cc
P src/lib/libc/net/getaddrinfo.c
P src/lib/libc/stdio/mktemp.3
P src/sys/arch/alpha/include/signal.h
P src/sys/arch/amd64/amd64/machdep.c
P src/sys/arch/hppa/hppa/locore.S
U src/sys/arch/hppa/hppa/sigcode.S
P src/sys/arch/hppa/include/signal.h
P src/sys/arch/i386/i386/machdep.c
P src/sys/arch/i386/include/signal.h
P src/sys/arch/i386/stand/efiboot/eficons.c
P src/sys/arch/sparc/include/signal.h
P src/sys/arch/vax/include/signal.h
P src/sys/arch/x86/include/machdep.h
P src/sys/arch/x86/x86/x86_machdep.c
P src/sys/dev/pci/hdaudio_pci.c
P src/sys/external/bsd/acpica/dist/changes.txt
P src/sys/external/bsd/acpica/dist/common/adisasm.c
P src/sys/external/bsd/acpica/dist/common/ahtable.c
P src/sys/external/bsd/acpica/dist/common/dmtable.c
P src/sys/external/bsd/acpica/dist/common/dmtbdump1.c
P src/sys/external/bsd/acpica/dist/common/dmtbdump2.c
P src/sys/external/bsd/acpica/dist/common/dmtbdump3.c
P src/sys/external/bsd/acpica/dist/common/dmtbinfo1.c
P src/sys/external/bsd/acpica/dist/common/dmtbinfo2.c
P src/sys/external/bsd/acpica/dist/common/dmtbinfo3.c
P src/sys/external/bsd/acpica/dist/compiler/aslmethod.c
P src/sys/external/bsd/acpica/dist/compiler/aslutils.c
P src/sys/external/bsd/acpica/dist/compiler/dtcompiler.h
P src/sys/external/bsd/acpica/dist/compiler/dtfield.c
P src/sys/external/bsd/acpica/dist/compiler/dttable1.c
P src/sys/external/bsd/acpica/dist/compiler/dttable2.c
P src/sys/external/bsd/acpica/dist/compiler/dttemplate.h
P src/sys/external/bsd/acpica/dist/compiler/dtutils.c
P src/sys/external/bsd/acpica/dist/compiler/preprocess.h
P src/sys/external/bsd/acpica/dist/dispatcher/dsfield.c
P src/sys/external/bsd/acpica/dist/dispatcher/dswexec.c
P src/sys/external/bsd/acpica/dist/generate/release/build.sh
P src/sys/external/bsd/acpica/dist/hardware/hwesleep.c
P src/sys/external/bsd/acpica/dist/hardware/hwsleep.c
P src/sys/external/bsd/acpica/dist/hardware/hwxfsleep.c
P src/sys/external/bsd/acpica/dist/include/acdisasm.h
P src/sys/external/bsd/acpica/dist/include/acglobal.h
P src/sys/external/bsd/acpica/dist/include/acnames.h
P src/sys/external/bsd/acpica/dist/include/acoutput.h
P src/sys/external/bsd/acpica/dist/include/acpixf.h
P src/sys/external/bsd/acpica/dist/include/actbinfo.h
P src/sys/external/bsd/acpica/dist/include/actbl1.h
P src/sys/external/bsd/acpica/dist/include/actbl2.h
P src/sys/external/bsd/acpica/dist/include/actbl3.h
P src/sys/external/bsd/acpica/dist/include/actypes.h
P src/sys/external/bsd/acpica/dist/tools/acpihelp/ahdecode.c
P src/sys/external/bsd/acpica/dist/tools/acpisrc/astable.c
P src/sys/external/bsd/acpica/dist/utilities/utosi.c
P src/tests/usr.bin/indent/opt_version.c
P src/tests/usr.bin/indent/t_errors.sh
P src/tests/usr.bin/indent/t_misc.sh
P src/usr.bin/indent/args.c
P src/usr.bin/indent/indent.c
P src/usr.bin/indent/indent.h
P src/usr.bin/indent/lexi.c
P src/usr.bin/indent/parse.c

Updating xsrc tree:


Killing core files:




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  47543380 Oct 29 03:04 ls-lRA.gz


Re: Raspberry Pi camera under NetBSD current

2021-10-28 Thread Dave Tyson
On Wednesday 27 Oct 2021 20:07:53 Dave Tyson wrote:
> On Wednesday 27 Oct 2021 18:28:31 Michael van Elst wrote:
> > dty...@anduin.org.uk (Dave Tyson) writes:
> > >I have been trying to get the raspberry pi camera to work on a model B
> > >under a recent current snapshot.
> > >
> > > NetBSD 9.99.88 (RPI) #0: Fri Sep 24 18:47:29 UTC 2021
> > > mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/RPI
> > >
> > >As standard booting off the sdcard works fine with the default
> > >config.txt,
> > >but to use the camera you need to modify this to add  start_x=1 and set
> > >the
> > >gpu mem to 128.  With the changed options you need different microcode
> > >files in the /boot partition start_x.elf and fixup_x.dat. NetBSD doesn't
> > >supply these, but I pulled versions from the git repository.
> > >
> > >The problem is that the system boots, but fails to attach the sdcard and
> > >thus cannot find root,

The attached diff of the boot messages shows some extra commands are issued to 
the bcmsdhost module in the failing case. I guess the calling sdmmc module 
doesn't like some of the data from the calls, tries to recover and fails. I'll 
try and understand the logic...

Dave NetBSD/evbarm (fdt) booting
 NetBSD/evbarm (fdt) booting 
 [ Kernel symbol table missing! 
 [ Kernel symbol table missing! 
 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,  
 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 
2002, 2003, 2004, 2005,
 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 
2014, 2015, 2016, 2017,
 2018, 2019, 2020, 2021 The NetBSD Foundation, Inc  All rights reserved 
 2018, 2019, 2020, 2021 The NetBSD Foundation, Inc  
All rights reserved
 Copyright (c) 1982, 1986, 1989, 1991, 1993 
 Copyright (c) 1982, 1986, 1989, 1991, 1993
 The Regents of the University of California  All rights reserved   
 The Regents of the University of California  All 
rights reserved
 NetBSD 9.99.92 (RPI) #2: Tue Oct 26 21:20:04 BST 2021  
 NetBSD 9.99.92 (RPI) #2: Tue Oct 26 21:20:04 BST 2021
root@cruncheranduinorguk:/usr/armobj/sys/arch/evbarm/compile/RPI

root@cruncheranduinorguk:/usr/armobj/sys/arch/evbarm/compile/RPI
 total memory = 384 MB  
   | total memory = 128 MB
 avail memory = 366 MB  
   | avail memory = 115 MB
 armfdt0 (root) 
 armfdt0 (root)
 simplebus0 at armfdt0: Raspberry Pi Model B Rev 2  
 simplebus0 at armfdt0: Raspberry Pi Model B Rev 2
 simplebus1 at simplebus0   
 simplebus1 at simplebus0
 simplebus2 at simplebus0   
 simplebus2 at simplebus0
 simplebus3 at simplebus0   
 simplebus3 at simplebus0
 cpus0 at simplebus0
 cpus0 at simplebus0
 cpu0 at cpus0: 700 MHz ARM1176JZ-S r0p7 (ARM11J V6ZK core) 
 cpu0 at cpus0: 700 MHz ARM1176JZ-S r0p7 (ARM11J V6ZK 
core)
 cpu0: DC enabled IC enabled WB enabled LABT
 cpu0: DC enabled IC enabled WB enabled LABT
 cpu0: L1 16KB/32B 4-way (128 set) VIPT Instruction cache   
 cpu0: L1 16KB/32B 4-way (128 set) VIPT Instruction 
cache
 cpu0: L1 16KB/32B 4-way (128 set) write-back-locking-C VIPT Data cache 
 cpu0: L1 16KB/32B 4-way (128 set) write-back-locking-C 
VIPT Data cache
 vfp0 at cpu0: VFP11, rounding, exceptions  
 vfp0 at cpu0: VFP11, rounding, exceptions
 fclock0 at simplebus2: 1920 Hz fixed clock (osc)   
 fclock0 at simplebus2: 1920 Hz fixed clock (osc)
 fclock1 at simplebus2: 48000 Hz fixed clock (otg)  
 fclock1 at simplebus2: 48000 Hz fixed clock (otg)
 simplebus4 at simplebus1   
 simplebus4 at simplebus1
 bcmicu0 at 

re: IDENTIFY failed

2021-10-28 Thread matthew green
> > wd1 at atabus1 drive 0
> > autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for 
> > drive 0
> > wd1: autoconfiguration error: IDENTIFY failed
> > wd1(ahcisata0:1:0): using PIO mode 0
> >
> > and booting fails. Reverting and booting with 9.99.90 gets me a working box:
> >
> > wd1 at atabus1 drive 0
> > wd1: 
> > wd1: drive supports 16-sector PIO transfers, LBA48 addressing
> > wd1: 9314 GB, 19377850 cyl, 16 head, 63 sec, 512 bytes/sect...
> > ...
> > wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 
> > (Ultra/133) (using DMA), NCQ (31 tags)
> >
> > I'm sure someone else saw this too, but I can't find the original post...
>
> https://mail-index.netbsd.org/current-users/2021/10/27/msg041615.html

this one has reduced timeframe, too:

> between
> NetBSD 9.99.91 (GENERIC) #0: Tue Oct 12 19:57:53 UTC 2021 OK
> NetBSD 9.99.92 (GENERIC) #0: Mon Oct 25 20:32:38 UTC 2021 Failed 

two possible changes to test reverting:

   http://mail-index.netbsd.org/source-changes/2021/10/05/msg132733.html

which changed how some interrupt handling works, and:

   http://mail-index.netbsd.org/source-changes/2021/10/11/msg132941.html

which removed some delays in the probe path.  possibly this one
is more likely to be at fault since it touches the probe path
directly.


.mrg.


Automated report: NetBSD-current/i386 build success

2021-10-28 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again.

The following commits were made between the last failed build and the
successful build:

2021.10.28.14.53.08 christos 
src/sys/external/bsd/acpica/dist/compiler/aslutils.c,v 1.30
2021.10.28.14.53.08 christos 
src/sys/external/bsd/acpica/dist/compiler/dtfield.c,v 1.19
2021.10.28.14.53.08 christos 
src/sys/external/bsd/acpica/dist/compiler/dtutils.c,v 1.18
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/hardware/hwesleep.c,v 1.11
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/hardware/hwsleep.c,v 1.13
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/hardware/hwxfsleep.c,v 1.16
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/include/acdisasm.h,v 1.23
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/include/acglobal.h,v 1.24
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/include/acoutput.h,v 1.14
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/include/acpixf.h,v 1.31
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/include/actbl1.h,v 1.19
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/include/actypes.h,v 1.25
2021.10.28.14.53.09 christos 
src/sys/external/bsd/acpica/dist/utilities/utosi.c,v 1.17
2021.10.28.14.54.32 christos src/doc/3RDPARTY,v 1.1825
2021.10.28.14.54.32 christos src/doc/CHANGES,v 1.2847
2021.10.28.15.08.05 christos src/common/lib/libc/hash/sha2/sha2.c,v 1.25
2021.10.28.15.09.08 christos src/common/lib/libc/hash/sha1/sha1.c,v 1.7

Logs can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2021.10.html#2021.10.28.15.09.08


Automated report: NetBSD-current/i386 build failure

2021-10-28 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386
build failure.

The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.10.28.14.43.18.

An extract from the build.sh output follows:

#create  sa/checkpasswd.d
CC=/tmp/build/2021.10.28.14.43.18-i386/tools/bin/i486--netbsdelf-gcc 
/tmp/build/2021.10.28.14.43.18-i386/tools/bin/nbmkdep -f checkpasswd.d.tmp  --  
 -std=gnu99 -DACPI_32BIT_PHYSICAL_ADDRESS  
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libsa
 --sysroot=/tmp/build/2021.10.28.14.43.18-i386/destdir 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../..
 -I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/..
 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libsa
 -I/tmp/build/2021.10.28.14.43.18-i386/obj/sys/arch/i386/stand/efiboot/bootia32 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../lib
 -nostdinc -D_STANDALONE -DEFIBOOT -Wall -Wmissing-prototypes -Wno-pointer-sign 
-DEFI_ALLOCATE_MAX_ADDRESS=0x1
 ULL -DHEAP_VARIABLE -DSUPPORT_CD9660 -D"devb2cdb(bno)=(bno)" -DSUPPORT_DOSFS 
-DSUPPORT_EXT2FS -DSUPPORT_BOOTP -DSUPPORT_DHCP -DSUPPORT_NFS -DSUPPORT_TFTP 
-DPASS_BIOSGEOM -DBIOSDISK_DEFAULT_SECSIZE=2048 -DLIBSA_ENABLE_LS_OP 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../external/bsd/gnu-efi/dist/inc
 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../external/bsd/gnu-efi/dist/inc/ia32
 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../external/bsd/gnu-efi/dist/inc/protocol
 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libkern/../../../common/lib/libc/quad
 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libkern/../../../common/lib/libc/string
 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libkern/../../..
 /common/lib/libc/arch/i386/string 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libkern/../../../common/lib/libc/arch/i386/atomic
 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libkern/../../../common/lib/libc/hash/sha3
 -DLIBSA_PRINTF_LONGLONG_SUPPORT -DLIBSA_PRINTF_WIDTH_SUPPORT 
-D"cdb2devb(bno)=(bno)" 
-I/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libgnuefi/../../../common/dist/zlib
 -DCOMPAT_UFS -D__INTERNAL_LIBSA_CREAD -Wno-pointer-sign 
/tmp/build/2021.10.28.14.43.18-i386/src/sys/arch/i386/stand/efiboot/bootia32/../../../../../lib/libsa/checkpasswd.c
 &&  mv -f checkpasswd.d.tmp checkpasswd.d
--- dependall-tests ---
--- test_read_format_xar.d ---
--- dependall-external ---

/tmp/build/2021.10.28.14.43.18-i386/src/sys/external/bsd/acpica/dist/compiler/dttable1.c:262:50:
 error: 'AcpiDmTableInfoAestXrupt' undeclared (first use in this function); did 
you mean 'AcpiDmTableInfoHestBank'?
  262 | Status = DtCompileTable (PFieldList, 
AcpiDmTableInfoAestXrupt,
  |  
^~~~
  |  
AcpiDmTableInfoHestBank
--- dependall-tests ---
#create  libarchive/test_read_format_xar.d

The following commits were made between the last successful build and
the failed build:

2021.10.28.14.31.20 christos 
src/external/gpl3/gcc/dist/libsanitizer/sanitizer_common/sanitizer_linux.cc,v 
1.42
2021.10.28.14.43.14 christos src/sys/external/bsd/acpica/dist/changes.txt,v 
1.1.1.29
2021.10.28.14.43.14 christos 
src/sys/external/bsd/acpica/dist/common/adisasm.c,v 1.1.1.18
2021.10.28.14.43.14 christos 
src/sys/external/bsd/acpica/dist/common/ahtable.c,v 1.1.1.13
2021.10.28.14.43.14 christos 
src/sys/external/bsd/acpica/dist/generate/release/build.sh,v 1.1.1.5
2021.10.28.14.43.15 christos 
src/sys/external/bsd/acpica/dist/common/dmtable.c,v 1.1.1.20
2021.10.28.14.43.15 christos 
src/sys/external/bsd/acpica/dist/common/dmtbdump1.c,v 1.1.1.6
2021.10.28.14.43.15 christos 
src/sys/external/bsd/acpica/dist/common/dmtbdump2.c,v 1.1.1.10
2021.10.28.14.43.15 christos 
src/sys/external/bsd/acpica/dist/common/dmtbdump3.c,v 1.1.1.8
2021.10.28.14.43.15 christos 
src/sys/external/bsd/acpica/dist/common/dmtbinfo1.c,v 1.1.1.7
2021.10.28.14.43.15 christos 
src/sys/external/bsd/acpica/dist/common/dmtbinfo2.c,v 1.1.1.8
2021.10.28.14.43.15 christos 
src/sys/external/bsd/acpica/dist/common/dmtbinfo3.c,v 1.1.1.7

Re: IDENTIFY failed

2021-10-28 Thread Chavdar Ivanov
On Thu, 28 Oct 2021 at 14:11, Patrick Welche  wrote:
>
> Updating from NetBSD-9.99.90/amd64 to 9.99.92, I get the following failure:
>
> wd1 at atabus1 drive 0
> autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for drive > 0
> wd1: autoconfiguration error: IDENTIFY failed
> wd1(ahcisata0:1:0): using PIO mode 0
>
> and booting fails. Reverting and booting with 9.99.90 gets me a working box:
>
> wd1 at atabus1 drive 0
> wd1: 
> wd1: drive supports 16-sector PIO transfers, LBA48 addressing
> wd1: 9314 GB, 19377850 cyl, 16 head, 63 sec, 512 bytes/sect...
> ...
> wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 
> (Ultra/133) (using DMA), NCQ (31 tags)
>
> I'm sure someone else saw this too, but I can't find the original post...

https://mail-index.netbsd.org/current-users/2021/10/27/msg041615.html

>
>
> Cheers,
>
> Patrick



-- 



IDENTIFY failed

2021-10-28 Thread Patrick Welche
Updating from NetBSD-9.99.90/amd64 to 9.99.92, I get the following failure:

wd1 at atabus1 drive 0
autoconfiguration error: ahcisata0 port 1: setting WDCTL_RST failed for drive 0
wd1: autoconfiguration error: IDENTIFY failed
wd1(ahcisata0:1:0): using PIO mode 0

and booting fails. Reverting and booting with 9.99.90 gets me a working box:

wd1 at atabus1 drive 0
wd1: 
wd1: drive supports 16-sector PIO transfers, LBA48 addressing
wd1: 9314 GB, 19377850 cyl, 16 head, 63 sec, 512 bytes/sect...
...
wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) 
(using DMA), NCQ (31 tags)

I'm sure someone else saw this too, but I can't find the original post...


Cheers,

Patrick


Re: Looking for various wifi hardware

2021-10-28 Thread Chavdar Ivanov
On Thu, 28 Oct 2021 at 11:39, Chavdar Ivanov  wrote:
>
> Not directly linked to that, but...
>
> On Wed, 27 Oct 2021 at 13:40, Martin Husemann  wrote:
> >
> > Hey folks,
> >
> > I am still working on wlan enhancements and would like to get more different
> > chipsets localy testable in my hands.
> >
> > I have a list of all our wlan drivers and the ones I have already marked
> > here:
> >
> > https://wiki.NetBSD.org/Driver_state_matrix/
>
> This page points to the https://wiki.netbsd.org/Wifi_renewal_on_hg/
> page, which shows
>
> hg clone https://anonhg.netbsd.org/src-draft

After I got it, I tried to build kernel and modules; the modules build
failed in some usb-based module; I then tried just to build a kernel
(all that after 'hg up wifi' reported some 260 modified files). The
failure was in  src-draft/sys/dev/ic/an.c and the error messages all
are like:

 24 /home/xci/src-draft/sys/dev/ic/an.c:270:6: error: 'struct
ieee80211com' has no member named 'ic_ifp'; did you mean 'ic_dfs'?
 28 /home/xci/src-draft/sys/dev/ic/an.c:273:16: error:
'IEEE80211_C_WEP' undeclared (first use in this function); did you
mean 'IEEE80211_C_WME'?
 33 /home/xci/src-draft/sys/dev/ic/an.c:275:6: error: 'struct
ieee80211com' has no member named 'ic_state'; did you mean 'ic_sta'?
 47 /home/xci/src-draft/sys/dev/ic/an.c:276:26: error: 'struct
ieee80211com' has no member named 'ic_myaddr'; did you mean
'ic_macaddr'?
 56 /home/xci/src-draft/sys/dev/ic/an.c:301:6: error: 'struct
ieee80211com' has no member named 'ic_ibss_chan'; did you mean
'ic_bsschan'?
 60 /home/xci/src-draft/sys/dev/ic/an.c:304:39: error: 'struct
ieee80211com' has no member named 'ic_myaddr'; did you mean
'ic_macaddr'?



>
> This now fails when using py39-mercurial 5.9.2 - in
> python3.9/site-packages/mercurial/revlogutils/rewrite.py line 592,
> with:
>
> AttributeError: 'memoryview' object has no attribute 'startswith'
>
> The easiest is to update py-mercurial to 5.9.3 (the buglet is actually
> commented there). The upgrade appears trivial.
>
> Chavdar
>
>
>
> >
> > As you can see I lack most of the USB chipsets, mostly because it is
> > not easy to order "by chipset name". If you have any pointers, please
> > contact me off-list.
> >
> > I'm also interested in PCI and PCIe cards (but only have limited test
> > slots available).
> >
> > If you happen to have any spare pcmcia or cardbus cards and could ship them
> > within Europe (and don't need them back) please also contact me off-list.
> >
> > Martin
>
>
>
> --
> 



-- 



Re: Looking for various wifi hardware

2021-10-28 Thread Chavdar Ivanov
Not directly linked to that, but...

On Wed, 27 Oct 2021 at 13:40, Martin Husemann  wrote:
>
> Hey folks,
>
> I am still working on wlan enhancements and would like to get more different
> chipsets localy testable in my hands.
>
> I have a list of all our wlan drivers and the ones I have already marked
> here:
>
> https://wiki.NetBSD.org/Driver_state_matrix/

This page points to the https://wiki.netbsd.org/Wifi_renewal_on_hg/
page, which shows

hg clone https://anonhg.netbsd.org/src-draft

This now fails when using py39-mercurial 5.9.2 - in
python3.9/site-packages/mercurial/revlogutils/rewrite.py line 592,
with:

AttributeError: 'memoryview' object has no attribute 'startswith'

The easiest is to update py-mercurial to 5.9.3 (the buglet is actually
commented there). The upgrade appears trivial.

Chavdar



>
> As you can see I lack most of the USB chipsets, mostly because it is
> not easy to order "by chipset name". If you have any pointers, please
> contact me off-list.
>
> I'm also interested in PCI and PCIe cards (but only have limited test
> slots available).
>
> If you happen to have any spare pcmcia or cardbus cards and could ship them
> within Europe (and don't need them back) please also contact me off-list.
>
> Martin



--