amd64/7.0_BETA fails to probe USB devices?

Hi, I've recently been installing NetBSD on a new Lenovo RD350 server. I first tried booting from USB disk and from a USB CD-ROM drive, and both the install kernels loaded just fine. However, the boot medium was not probed by the 7.0_BETA amd64 kernel. The kernel on NetBSD 6.1.3 CD-ROM install

Failure in amd64 7.99.11

While running sysinst under qemu, I get the following, right after sysinst has run newfs: /targetroot: bad dir ino 2 at offset 0: mangled entry panic: bad dir fatal breakpoint trap in supervisor mode trap type 1 code 0 rip 80289e5d cs 8 rflags 246 cr2 7f7ff74a0830 ilevel 0 rsp

Re: Failure in amd64 7.99.13 (corrected - originally was 7.99.11)

On Apr 29, 9:04am, p...@vps1.whooppee.com (Paul Goyette) wrote: -- Subject: Re: Failure in amd64 7.99.13 (corrected - originally was 7.99.11) | Please note the correction in the subject line! Fixed, thanks. christos

Re: Failure in amd64 7.99.13 (corrected - originally was 7.99.11)

Please note the correction in the subject line! On Wed, 29 Apr 2015, Paul Goyette wrote: While running sysinst under qemu, I get the following, right after sysinst has run newfs: /targetroot: bad dir ino 2 at offset 0: mangled entry panic: bad dir fatal breakpoint trap in supervisor mode

Resume from suspend does not work on a DELL LATITUDE E6540

Hello, resume from suspend does not work on a DELL LATITUDE E6540 with NetBSD 7.99.9 (GENERIC.201504161510Z). Independend of the value of hw.acpi.sleep.vbios the laptop reboots on resume. dmesg is: ACPI Display Output Device acpiout1: brightness levels: [5-100] acpiout2 at acpivga1 (DVI,

vndcompress unexpected pass!

Just tried a: # cd /usr/src/usr.bin/vndcompress # make check ... cmp oneblock.cl2 oneblock.cl2x unexpected pass! *** Error code 1 What is that trying to test? # diff /usr/bin/vndcompress obj.amd64/vndcompress # Cheers, Patrick

Re: Build fails on extra files in DESTDIR, what does that mean?

from Ian D. Leroux: Passing the -r option to ./build.sh will force a clean of DESTDIR. That's good to know! I just went through ./build.sh again, see -r option clears both DESTDIR and TOOLDIR. I think the DESTDIR must have still had stuff from 6.99.40. Tom

daily CVS update output

Updating src tree: P src/crypto/external/bsd/heimdal/dist/kadmin/kadmin.8 P src/distrib/atari/floppies/install/Makefile P src/distrib/utils/x_ifconfig/Makefile P src/doc/3RDPARTY P src/doc/CHANGES P src/external/bsd/am-utils/dist/README P src/external/bsd/pkg_install/dist/info/pkg_info.1 P

Build fails on extra files in DESTDIR, what does that mean?

Trying to build NetBSD 7.99.10 amd64, i386, from 7.99.7 installation was stopped by === checkflist === distrib/sets cd /BETA1/netbsd-HEAD/usr/src/distrib/sets DESTDIR=/BETA1/netbsd-HEAD/usr/src/../obj/BETA1/netbsd-HEAD/usr/src/destdir.amd64 MACHINE=amd64

Re: Build fails on extra files in DESTDIR, what does that mean?

On Tue, Apr 28, 2015, at 07:40, Thomas Mueller wrote: But I am still curious about a build failing on extra files in DESTDIR and how to avoid it, remember this happening before in NetBSD but not FreeBSD. ./build.sh does an automatic make cleandir by default (if you don't pass the -u option),

Re: Build fails on extra files in DESTDIR, what does that mean?

On Tue, 28 Apr 2015 10:21:07 +0200 Ian D. Leroux idler...@fastmail.fm wrote: On Tue, Apr 28, 2015, at 07:40, Thomas Mueller wrote: But I am still curious about a build failing on extra files in DESTDIR and how to avoid it, remember this happening before in NetBSD but not FreeBSD.

Automated report: NetBSD-current/i386 build failure

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 2015.04.28.17.14.21. An extract from the build.sh output follows:

msi gcc build problem

sys/arch/x86/pci/msipci.c has: KASSERT(pci_get_capability(pc, tag, PCI_CAP_MSI, off, NULL) != 0); ... ctl = pci_conf_read(pc, tag, off + PCI_MSI_CTL); but gcc can't work out that the off was set in the first function call: --- msipic.o --- ../../../../arch/x86/pci/msipic.c: In function

Re: msi gcc build problem

On Tue, Apr 28, 2015 at 07:02:39AM +0100, Patrick Welche wrote: I have been building with NOGCCERROR=yes in mk.conf - thoughts on a more elegant solution to quell the warning? You are probably building without options DIAGNOSTIC, so the KASSERT is going away. I just fixed that file. Martin

Re: msi gcc build problem

Hi, On 2015/04/28 15:29, Martin Husemann wrote: On Tue, Apr 28, 2015 at 07:02:39AM +0100, Patrick Welche wrote: I have been building with NOGCCERROR=yes in mk.conf - thoughts on a more elegant solution to quell the warning? Sorry, I missed the build check... You are probably building