daily CVS update output

2017-10-10 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/base/shl.mi P src/distrib/sets/lists/comp/mi P src/distrib/sets/lists/comp/shl.mi P src/distrib/sets/lists/debug/mi P src/distrib/sets/lists/debug/shl.mi P src/doc/3RDPARTY P src/external/bsd/acpica/bin/iasl/Makefile P src/lib/Makefile U

Re: HEADS-UP: SATA NCQ support merged (from jdolecek-ncq branch)

2017-10-10 Thread Thor Lancelot Simon
On Tue, Oct 10, 2017 at 11:11:54PM +0200, Jarom??r Dole??ek wrote: > I've fixed the compilation for ALL kernels. > > 2017-10-10 17:34 GMT+02:00 Michael : > > I tried sequential reads ( dd if=/dev/rwd0c ... ) and throughput took a > > significant hit. I used to get about

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
The timeouts when running under VirtualBox disappeared, but of course the panic on my T61p remains. Chavdar Ivanov On Tue, 10 Oct 2017 at 22:40 Jaromír Doleček wrote: > Hey, > > can you try with dev/scsipi/atapi_wdc.c 1.128? That should resolve the > timeouts for

Re: HEADS-UP: SATA NCQ support merged (from jdolecek-ncq branch)

2017-10-10 Thread Jaromír Doleček
I've fixed the compilation for ALL kernels. 2017-10-10 17:34 GMT+02:00 Michael : > I tried sequential reads ( dd if=/dev/rwd0c ... ) and throughput took a > significant hit. I used to get about 120MB/s with the siisata, now it > fluctuates between 80 and 90MB/s, ahcisata

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Jaromír Doleček
Hey, can you try with dev/scsipi/atapi_wdc.c 1.128? That should resolve the timeouts for atapi, at least it did for me. Jaromir 2017-10-10 8:08 GMT+02:00 Rares Aioanei : > I get that also on VBox, except it doesn't try to add cd0a as a swap > device, nor does it show an

arm make release failure when building BEAGLEBONE

2017-10-10 Thread Dave Tyson
This is from the current source tree a little earlier today, cross compiling arm on amd64: ./build.sh -j 4 -U -u -x -m evbearmv7hf-el -O /home/dtyson/cross/obj -T /home/dtyson/cross/tools release Might be fallout from the ata changes.. ... # compile compat/uipc_syscalls_30.o

Automated report: NetBSD-current/i386 build success

2017-10-10 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: 2017.10.10.16.04.59 christos src/distrib/sets/lists/comp/mi,v 1.2150 2017.10.10.16.30.23 jdolecek src/sys/dev/ic/mvsata.c,v 1.38 2017.10.10.16.44.24

Automated report: NetBSD-current/i386 build failure

2017-10-10 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 2017.10.10.15.38.00. An extract from the build.sh output follows: postinstall-fix-obsolete_stand ===> . ---

Re: HEADS-UP: SATA NCQ support merged (from jdolecek-ncq branch)

2017-10-10 Thread Michael
Hello, On Sat, 7 Oct 2017 18:34:04 +0200 Jaromír Doleček wrote: > I've merged the NCQ branch to HEAD. Nice, thanks! > The code was quite extensively tested on that harware on amd64. Other archs > and drivers compile, but I had no way to test them. Particularily, I

Re: UEFI boot NetBSD?

2017-10-10 Thread Michael van Elst
mueller6...@twc.com ("Thomas Mueller") writes: >So how would the load or boot code find the kernel? The EFI-bootloader finds /boot.cfg in the EFI partitition and can be directed to load the kernel from the root partitition, i.e. something like "boot hd0b:netbsd". -- --

Re: UEFI boot NetBSD?

2017-10-10 Thread Thomas Mueller
> On Tue, Oct 10, 2017 at 03:03:22AM +, Thomas Mueller wrote: > > Is it currently possible to boot newer versions of NetBSD in UEFI mode? > -8 and -current should work, but the installer has not yet been updated > to reflect it. > > How would the boot/load code know where to find the root

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Rares Aioanei
I get that also on VBox, except it doesn't try to add cd0a as a swap device, nor does it show an endless stream of "lost interrupt" messages; eventually I get a login prompt. This is with yesterday's latest -CURRENT. On Sun, Oct 8, 2017 at 5:17 PM, Chavdar Ivanov wrote: > I

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
Examining the relevant commit in this period, it is only the NCQ update which has anything to doç ... Merge support for SATA NCQ (Native Command Queueing) from jdolecek-ncq branch ... It is way too complicated for me to try to back it out piecemeal to find something. But as far as I understand it

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
A bit sad responding to myself... Anyway, https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201710060130Z/amd64/binary/kernel/netbsd-GENERIC.gz works fine. https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201710071630Z/amd64/binary/kernel/netbsd-GENERIC.gz crashes, in case someone else is hit by

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
The same happens with the kernel built some hour ago. The last kernel I am running on the T61p is from 05/10/2017. I just tested https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201710081900Z/amd64/binary/kernel/netbsd-GENERIC.gz with exactly the same result. There have been quite a few recent