FreeBSD 9.2-RELEASE doesn't correctly detect USB mouse/keyboard
I am running vanilla 9.2-RELEASE on an HP Z230. Strangely, my USB keyboard and mouse don't work. When I attach, here is what shows: Oct 11 12:36:39 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:39 waridi kernel: ugen0.2: Unknown at usbus0 (disconnected) Oct 11 12:36:39 waridi kernel: uhub_reattach_port: could not allocate new device Oct 11 12:36:48 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:48 waridi kernel: ugen0.2: Unknown at usbus0 (disconnected) Oct 11 12:36:48 waridi kernel: uhub_reattach_port: could not allocate new device Oct 11 12:36:55 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:55 waridi kernel: ugen0.2: Unknown at usbus0 (disconnected) Oct 11 12:36:55 waridi kernel: uhub_reattach_port: could not allocate new device $ uname -a FreeBSD waridi.kihingovillage.com 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj /usr/src/sys/GENERIC amd64 I am wondering if there is something obvious I am missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 I can't hear you -- I'm using the scrambler. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Victor Sudakov wrote: I have several Supermicro-based servers with the mpt RAID adapter: # mptutil show adapter mpt0 Adapter: Board Name: UNUSED Board Assembly: Chip Name: C1068E Chip Revision: UNUSED RAID Levels: none # The problem is, I cannot configure any RAIDs (please see output below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD still sees them as separate physical discs. What am I doing wrong? I cannot use gmirror with these servers because a) if no MPT RAID is configured in BIOS setup, it cannot boot from HDD and b) if an MPT RAID *is* configured in BIOS setup, it occupies the last sector and prevents GEOM from working with these drives. Any help please? (or redirect me to a more appropriate maillist). After many unsuccessful trials and googling, we had to reconfigure the adapter from RAID mode to IT mode. It required flashing the adapter's BIOS from a Supermicro-supplied image and changing a jumper setting on the motherboard. Now as the adapter is in IT mode, it is a plain HBA the BIOS can boot from, and I have set up a gmirror on the SAS disks. After flashing the adapter BIOS, don't forget to enter its setup (Ctrl-C) and enable hotplugging of disks (called Removable Media Support in the menu, off by default). People come across similar problems and solutions on other OSes, like http://ubuntuforums.org/archive/index.php/t-973912.html -- Victor Sudakov Tomsk, Russia Russian Barefoot FAQ at http://www.barefooters.ru/barefoot.txt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Colleagues, I have several Supermicro-based servers with the mpt RAID adapter: # mptutil show adapter mpt0 Adapter: Board Name: UNUSED Board Assembly: Chip Name: C1068E Chip Revision: UNUSED RAID Levels: none # The problem is, I cannot configure any RAIDs (please see output below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD still sees them as separate physical discs. What am I doing wrong? I cannot use gmirror with these servers because a) if no MPT RAID is configured in BIOS setup, it cannot boot from HDD and b) if an MPT RAID *is* configured in BIOS setup, it occupies the last sector and prevents GEOM from working with these drives. Any help please? (or redirect me to a more appropriate maillist). # mptutil clear Are you sure you wish to clear the configuration on mpt0? [y/N] y mpt0: Configuration cleared # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # mptutil show drives mpt0 Physical Drives: da0 ( 558G) ONLINE HITACHI HUS156060VLS600 A760 SCSI-6 bus 0 id 0 da1 ( 558G) ONLINE HITACHI HUS156060VLS600 A760 SCSI-6 bus 0 id 1 da2 ( 558G) ONLINE HITACHI HUS156060VLS600 A760 SCSI-6 bus 0 id 2 da3 ( 558G) ONLINE HITACHI HUS156060VLS600 A760 SCSI-6 bus 0 id 3 # # mptutil create raid1 -v da2,da3 mptutil: Reading config page header failed: Invalid configuration page Added drive da2 with PhysDiskNum 0 mptutil: Reading config page header failed: Invalid configuration page # # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 9.2 - does not appear to support the 'dc' PCMCIA NIC driver
I have a Netgear FA511 PCMCIA NIC that worked fine under 9.1. Under 9.2 I get the following message: Oct 6 21:38:11 monitor4 kernel: dc0: ADMtek AN985 CardBus 10/100BaseTX or clon e port 0x1100-0x11ff irq 19 at device 0.0 on cardbus0 Oct 6 21:38:11 monitor4 kernel: dc0: attaching PHYs failed This used to work under 9.1, does anyone know what happened? Thanks. Kent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Failure to build FreeBSD 9.2
i recompiled my kernel with more verbose output and I see following errors before it stops: procfs registered panic: No usable event timer found! cpuid=0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x1d8/frame initclocks() mi_startup() btext() ... KDB: enter: panic [thread pid 0 tid 10] Stopped at kdb_enter+0x3b: moxq can someone help me to explain what this means and what to do next? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Failure to build FreeBSD 9.2
On Sat, 5 Oct 2013 09:40:31 +0300, Juris Kaminskis wrote: i recompiled my kernel with more verbose output and I see following errors before it stops: procfs registered panic: No usable event timer found! cpuid=0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x1d8/frame initclocks() mi_startup() btext() ... KDB: enter: panic [thread pid 0 tid 10] Stopped at kdb_enter+0x3b: moxq can someone help me to explain what this means and what to do next? In many cases, this indicates a problem introduced by the computer's BIOS settings or ACPI. Make sure ACPI is enabled and the BIOS is configured properly (e. g. no timer settings modified or features deactivated). You could also check if a newer version of the BIOS is available. In addition, there's the suggestion to add the line debug.acpi.disabled=hostres to /boot/loader.conf and reboot. Source: http://www.freebsd.org/releases/9.0R/errata.html -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Failure to build FreeBSD 9.2
2013/10/5 Polytropon free...@edvax.de On Sat, 5 Oct 2013 09:40:31 +0300, Juris Kaminskis wrote: i recompiled my kernel with more verbose output and I see following errors before it stops: procfs registered panic: No usable event timer found! cpuid=0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x1d8/frame initclocks() mi_startup() btext() ... KDB: enter: panic [thread pid 0 tid 10] Stopped at kdb_enter+0x3b: moxq can someone help me to explain what this means and what to do next? In many cases, this indicates a problem introduced by the computer's BIOS settings or ACPI. Make sure ACPI is enabled and the BIOS is configured properly (e. g. no timer settings modified or features deactivated). You could also check if a newer version of the BIOS is available. Update to new BIOS did the trick! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Failure to build FreeBSD 9.2
Hello, I am desperate trying to build FreeBSD 9.2. The same happens with FreeBSD-Current. When I build 9.1 kernel without building world everything is ok. My svn info Path: . Working Copy Root Path: /usr/src URL: http://svn0.eu.freebsd.org/base/release/9.2.0 Repository Root: http://svn0.eu.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 255954 Node Kind: directory Schedule: normal Last Changed Author: gjb Last Changed Rev: 255898 Last Changed Date: 2013-09-26 21:28:11 +0300 (Thu, 26 Sep 2013) When I do standard process: make buildworld make buildkernel make installkernel reboot my kernel hangs up and does not respond. I have tried a lot of things but nothing works. my new kernel hangs right after: pci1: ACPI PCI bus on pcib1 my uname -a FreeBSD station 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 and my dmesg output: Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ (2211.11-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x40fb2 Family = f Model = 4b Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x2001SSE3,CX16 AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x1fLAHF,CMP,SVM,ExtAPIC,CR8 real memory = 2147483648 (2048 MB) avail memory = 2045505536 (1950 MB) Event timer LAPIC quality 400 ACPI APIC Table: A M I OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: A M I OEMRSDT on motherboard acpi0: Power Button (fixed) unknown: memory range not supported unknown: memory range not supported unknown: memory range not supported acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ff0 (3) failed cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 3.0 on pci0 pcib1: failed to allocate initial memory window: 0xffb0-0xffbf pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x9800-0x98ff mem 0xc000-0xcfff irq 19 at device 0.0 on pci1 hdac0: ATI RV630 HDA Controller irq 16 at device 0.1 on pci1 pcib2: ACPI PCI-PCI bridge at device 6.0 on pci0 pci2: ACPI PCI bus on pcib2 re0: RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet port 0xa800-0xa8ff mem 0xffcff000-0xffcf irq 18 at device 0.0 on pci2 re0: Using 1 MSI message re0: Chip rev. 0x3800 re0: MAC rev. 0x miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:19:db:f6:72:d0 ahci0: ATI IXP600 AHCI SATA controller port 0xe800-0xe807,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd80f mem 0xffeffc00-0xffef irq 22 at device 18.0 on pci0 ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier supported ahcich0: AHCI channel at channel 0 on ahci0 ahcich1: AHCI channel at channel 1 on ahci0 ahcich2: AHCI channel at channel 2 on ahci0 ahcich3: AHCI channel at channel 3 on ahci0 ohci0: OHCI (generic) USB controller mem 0xffefe000-0xffefefff irq 16 at device 19.0 on pci0 usbus0 on ohci0 ohci1: OHCI (generic) USB controller mem 0xffefd000-0xffefdfff irq 17 at device 19.1 on pci0 usbus1 on ohci1 ohci2: OHCI (generic) USB controller mem 0xffefc000-0xffefcfff irq 18 at device 19.2 on pci0 usbus2 on ohci2 ohci3: OHCI (generic) USB controller mem 0xffefb000-0xffefbfff irq 17 at device 19.3 on pci0 usbus3 on ohci3 ohci4: OHCI (generic) USB controller mem 0xffefa000-0xffefafff irq 18 at device 19.4 on pci0 usbus4 on ohci4
Re: FreeBSD 9.2-RELEASE stability?
On Mon, Sep 30, 2013, at 14:01, Brett Glass wrote: How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. I upgraded our two main backup servers which are doing I/O via rsync/rsnapshot and sending ZFS snapshots to the other remote site every 15 minutes. I had several instances where the machines went unresponsive. They didn't panic, and they did respond to CTRL+ALT+DEL on the console, but they lost all networking and wouldn't do anything else. The only change was I enabled zfs prefetch which I previously had disabled for performance reasons. It never caused this issue on 9.1 when I had it enabled, though. The fix definitely was turning off prefetch again which doesn't bother me too much, but I can't use this environment to try to help debug it as it's important production data. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2-RELEASE stability?
On Tue, Oct 1, 2013 at 3:53 PM, Mark Felder f...@freebsd.org wrote: On Mon, Sep 30, 2013, at 14:01, Brett Glass wrote: How stable are folks finding FreeBSD 9.2-RELEASE to be? For me freebsd-update from 9.1 to 9.2 went smooth on my workstation laptop, the userland works fine :-) I remember myself Nakatomi BSD 9.2 on the movie (in the reception hall scene), I was su suprised back then to see BSD in this kind of movie :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2-RELEASE stability?
On Mon, Sep 30, 2013, at 14:01, Brett Glass wrote: How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. very frustrated at the moment... I've had some very strange issues crop up since upgrading from 9.1-RELEASE to 9.2-RELEASE. I'm using FreeBSD on a Xen HVM instance. My previous install was a system with a custom kernel (includes Xen HVM options) (entire base and kernel compiled with Clang 3.1 (base clang)). The system worked flawlessly. A rinse and repeat upgrade (build from source) with 9.2 is giving me some very strange issues: * Randomly when I start the VM, there is no network connectivity. I first noticed DHCP was timing out. The link appeared to be up on the xn0 interface but no data flow at all. Attempted manual interface configuration. Zilch, couldn't even get a response from the default gateway when pinging (both ipv4 and ipv6). A reboot of the machine and suddenly network connectivity is restored. Subsequently with no predictability, another reboot = no network again. No errors in dmesg or /var/log/messages. * /usr/ports/net/net-im/jabber (which appears not to have changed versions between my system upgrade) randomly aborts with signal 10 (bus error). * Programs that rely on mysql (installed percona 5.5 server) (such as jabber, powerdns etc) spew a bunch of errors saying they are unable to connect to the mysql server via /tmp/mysql.sock, after I log in and look, mysql is running just fine, and the programs that were complaining about mysql being unreachable are all operating correctly... (i have mysql set to start in /etc/rc.d before any of the programs that require it are started) -- never saw these issues in 9.1 * I run powerdns recursor for resolution of domain names. Despite having the recursor as being one of the first things in rc.conf to start (certainly before ntpdate), ntpdate decides to run before the recursor has started. This causes the lookup of the ntp server hostname to fail (using -b ip.ip.ip.ip as a flag to ntpdate rather than a host is a way to work around the issue). This was a clean build. I cleared up old libraries and rebuilt all my installed ports from scratch, I left no kruft lingering on the system to the best of my knowledge. Normally I would put something like the jabber server issue just being bad code that clang is happy to compile.. But the random network issue has the alarm bells ringing. Perhaps there is an issue with clang 3.3 generating faulty code? I havent had any kernel panics or machine freezes. This has to be a first for me with freebsd, I almost never ever have an issue after upgrading from RELEASE to RELEASE. I can probably rebuild it all again with the base gcc compiler, but clang is much much faster than the dinosaur gcc included in base and produces better code. Up in the air with this one. I might go back to 9.1, had none of these issues with it. /my 10 cents worth. BR, Alex. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2-RELEASE stability?
On Tue, Oct 1, 2013, at 18:54, ot...@ahhyes.net wrote: * I run powerdns recursor for resolution of domain names. Despite having the recursor as being one of the first things in rc.conf to start (certainly before ntpdate), ntpdate decides to run before the recursor has started. This causes the lookup of the ntp server hostname to fail (using -b ip.ip.ip.ip as a flag to ntpdate rather than a host is a way to work around the issue). Create in rc script in /usr/local/etc/rc.d that does nothing but set the REQUIRE and BEFORE fields. You can use that to re-order the startup scripts. Use the `service` command to see the new startup order -- there's a flag that will give you that output. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 9.2-RELEASE stability?
How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2-RELEASE stability?
On 9/30/2013 15:01, Brett Glass wrote: How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. --Brett Glass Just upgraded a system running in KVM, working like a charm. -- staticsafe O ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. It is not logical. Please don't CC me! I'm subscribed to whatever list I just posted on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2-RELEASE stability?
Le Mon, 30 Sep 2013 13:01:26 -0600, Brett Glass br...@lariat.net a écrit : Hello, How stable are folks finding FreeBSD 9.2-RELEASE to be? The improvements are welcome, but there have been a few troubling messages about kernel panics and VM issues on the various mailing lists. It's never clear until the release drops whether these are actual problems with the software or hardware defects in individual systems, so I am eager to hear how the new release is working for everyone. I've seen two problems if you use poudriere (on ZFS only?) which occur in some loads (ie desktop running gvfsd). One fix is in 9-STABLE and the other one should be mfced soon. May be there will be an errata for 9.2-RELEASE for this ? I think that would be nice because 9.2 is stable as a Windows 3.11 with my load :-) Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2
http://forums.macrumors.com/showthread.php?t=1619404 It is helpful too… On Aug 15, 2013, at 4:14 PM, Doug Hardie bc...@lafn.org wrote: On 15 August 2013, at 06:37, ajtiM lum...@gmail.com wrote: How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is it supported? I try Linux Mint and it works perfect. I am downloading live CD for NetBSD (jibbed) and I will see how is works but I like to install FreeBSD (not double boot, just FreeBSD). See: http://docs.freebsd.org/cgi/mid.cgi?28915479-B712-4ED0-A041-B75F2F59FECA Thats not a complete answer as I don't use any of the user interface stuff. However, it will give a starting point for you. I have updated my two newest minis to run 9.2 (latest candidate). Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freebsd 9.2 via svn
Hello list, Is it safe to start using 9.2 in the svn repos? I have a line like this in a daily crontab: svn co svn://svn.us-east.freebsd.org/base/releng/9.1 /usr/src Can I change that 9.1 to 9.2 now, or should I wait? I aim to follow 9.2-R with security updates. thanks, -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd 9.2 via svn
On Mon, 19 Aug 2013 02:28:25 +0100, John wrote: Is it safe to start using 9.2 in the svn repos? I have a line like this in a daily crontab: svn co svn://svn.us-east.freebsd.org/base/releng/9.1 /usr/src Can I change that 9.1 to 9.2 now, or should I wait? I aim to follow 9.2-R with security updates. 9.2-RELEASE hasn't been released yet. :-) http://www.freebsd.org/releases/9.2R/schedule.html If you don't use a custom kernel, why not use freebsd-update and follow the 9.2-RELEASE path with the security updates? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd 9.2 via svn
On Mon, Aug 19, 2013 at 04:17:02AM +0200, Polytropon wrote: 9.2-RELEASE hasn't been released yet. :-) well yes, there is that I suppose ;) If you don't use a custom kernel, why not use freebsd-update and follow the 9.2-RELEASE path with the security updates? Not sure if this is logic or religon, but freebsd-update makes me nervous. I'm allergic to automatic anything unless I've written it. The only times I've run generic is when installing a new system, to see what I need and what I don't. Maybe I'm just old. thanks for the input, -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd 9.2 via svn
On Mon, 19 Aug 2013 04:22:15 +0100, John wrote: If you don't use a custom kernel, why not use freebsd-update and follow the 9.2-RELEASE path with the security updates? Not sure if this is logic or religon, but freebsd-update makes me nervous. I'm allergic to automatic anything unless I've written it. The only times I've run generic is when installing a new system, to see what I need and what I don't. Maybe I'm just old. You demonstrated a valid argument for building from source. Using freebsd-update, a binary method is used for updating the _default_ system and the GENERIC kernel. If you have custom settings and therefore _intend_ to build from source, changing the version in your svn co command to the new -RELEASE-pX branch (security update branch) is safe. I've been using a similar approach with CVS to follow the -STABLE branch with a custom kernel and custom settings for building the system. If this makes me old, I should deserve several birthday parties per year. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2
Thank you very much. I will wait for 9.2 release or switch to Linux which works but it is not hat I want it… On Aug 15, 2013, at 4:14 PM, Doug Hardie bc...@lafn.org wrote: On 15 August 2013, at 06:37, ajtiM lum...@gmail.com wrote: How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is it supported? I try Linux Mint and it works perfect. I am downloading live CD for NetBSD (jibbed) and I will see how is works but I like to install FreeBSD (not double boot, just FreeBSD). See: http://docs.freebsd.org/cgi/mid.cgi?28915479-B712-4ED0-A041-B75F2F59FECA Thats not a complete answer as I don't use any of the user interface stuff. However, it will give a starting point for you. I have updated my two newest minis to run 9.2 (latest candidate). Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 9.2
Hi! I did stop using FreeBSD three months ago and with to iMac computer (older one) but I like start using FreeBSD again - I like it more. My computer is: iMac 27-inch, Late 2009 Processor 2.8 GHz Intel Core i7 Memory 8GB and graphics cars is ATI Radeon: Chipset Model: ATI Radeon HD 4850 Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 512 MB Vendor: ATI (0x1002) How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is it supported? I try Linux Mint and it works perfect. I am downloading live CD for NetBSD (jibbed) and I will see how is works but I like to install FreeBSD (not double boot, just FreeBSD). Thanks in advance. Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.2
On 15 August 2013, at 06:37, ajtiM lum...@gmail.com wrote: How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is it supported? I try Linux Mint and it works perfect. I am downloading live CD for NetBSD (jibbed) and I will see how is works but I like to install FreeBSD (not double boot, just FreeBSD). See: http://docs.freebsd.org/cgi/mid.cgi?28915479-B712-4ED0-A041-B75F2F59FECA Thats not a complete answer as I don't use any of the user interface stuff. However, it will give a starting point for you. I have updated my two newest minis to run 9.2 (latest candidate). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Terrible disk performance with LSI / FreeBSD 9.2-RC1
To follow up on this issue, at one point the stats were down to this: extended device statistics device r/s w/skr/skw/s qlen svc_t %b da00.0 0.0 0.0 0.00 0.0 0 da10.0 0.0 0.0 0.00 0.0 0 da2 127.9 0.0 202.3 0.01 47.5 100 da3 125.9 0.0 189.3 0.01 43.1 97 da4 127.9 0.0 189.8 0.01 45.8 100 da5 128.9 0.0 206.3 0.00 42.5 99 da6 127.9 0.0 202.3 0.01 46.2 98 da70.0 249.7 0.0 334.2 10 39.5 100 At some point, I figured out that 125 random iops is pretty much the limit for 7200 RPM SATA drives. So mostly what we're looking at here is the resilver of a raidz2 is the pathological worst case. Lesson learned; raidz2 is just really not viable without some kind of sort on the resilver operations. Wish I understood ZFS well enough to do something about that, but research suggests the problem is non-trivial. :( There also seems to be a separate ZFS issue related to having a very large number of snapshots (e.g. hourly for several months on a couple of filesystems). Some combination of the OS updates we've been doing trying to get this machine to 9.2-RC1 and deleting a ton of snapshots. It would be nice to know which it was; I guess we'll find out in a few months. So it seems like the combination of these two issues is mostly what is/was plaguing us. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Terrible disk performance with LSI / FreeBSD 9.2-RC1
On 8. aug. 2013, at 00:08, Frank Leonhardt fra...@fjl.co.uk wrote: As a suggestion, what happens if you read from the drives directly? Boot in single user and try reading a Gb or two using /bin/dd. It might eliminate or confirm a problem with ZFS. If not too inconvenient, it'd be very interesting to see what'd happen if you were to physically disconnect (data and power) 5 of the 6 drives, then boot and dd from the remaining disk to /dev/null. Then repeat with another drive. You could boot from USB to leave the system itself otherwise untouched. The reason I'm suggesting is that I'm wondering if this can be down to a power or cable-issue, locking things up or causing retransmits, etc. Not sure if this would always be logged, others might be able to enlighten that issue. Terje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Terrible disk performance with LSI / FreeBSD 9.2-RC1
On 08/08/2013 12:42, Terje Elde wrote: On 8. aug. 2013, at 00:08, Frank Leonhardt fra...@fjl.co.uk wrote: As a suggestion, what happens if you read from the drives directly? Boot in single user and try reading a Gb or two using /bin/dd. It might eliminate or confirm a problem with ZFS. If not too inconvenient, it'd be very interesting to see what'd happen if you were to physically disconnect (data and power) 5 of the 6 drives, then boot and dd from the remaining disk to /dev/null. Then repeat with another drive. You could boot from USB to leave the system itself otherwise untouched. The reason I'm suggesting is that I'm wondering if this can be down to a power or cable-issue, locking things up or causing retransmits, etc. Not sure if this would always be logged, others might be able to enlighten that issue. Terje And while you're at it, could you post the output of diskinfo -v /dev/[slices] - check the cylinder alignment and so on if you haven't already. Regards, Frank. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Terrible disk performance with LSI / FreeBSD 9.2-RC1
Maybe one of your drives is bad, so it's constantly doing error correction? On Tue, Aug 6, 2013 at 9:48 PM, J David j.david.li...@gmail.com wrote: We have a machine running 9.2-RC1 that's getting terrible disk I/O performance. Its performance has always been pretty bad, but it didn't really become clear how bad until we did a zpool replace on one of the drives and realized it was going to take 3 weeks to rebuild a 1TB drive. The hardware specs are: - 2 x Xeon L5420 - 32 GiB RAM - LSI Logic SAS 1068E - 2 x 32GB SSD's - 6 x 1TB Western Digital RE3 7200RPM SATA The LSI controller has the most recent firmware I'm aware of (6.36.00.00 / 1.33.00.00 dated 2011.08.24), is in IT mode, and appears to be working fine: mpt0 Adapter: Board Name: USASLP-L8i Board Assembly: USASLP-L8i Chip Name: C1068E Chip Revision: B3 RAID Levels: none mpt0 Configuration: 0 volumes, 8 drives drive da0 (30G) ONLINE FTM32GL25H 10 SATA drive da1 (29G) ONLINE SSDSA2SH032G1GN 8860 SATA drive da2 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da3 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da4 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da5 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da6 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da7 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA The eight drives are configured as ZIL, L2ARC on SSD and a six drive raidz2 on the spinning disks. We did a ZFS replace on the last drive in the line, and the resilver is proceeding at less than 800k/sec. extended device statistics device r/s w/skr/skw/s qlen svc_t %b da00.0 0.0 0.0 0.10 0.9 0 da10.0 8.2 0.019.90 0.1 0 da2 125.6 23.0 768.240.54 33.0 88 da3 126.6 23.1 769.041.34 32.3 89 da4 126.0 24.0 768.542.74 32.1 88 da5 125.9 22.0 768.240.14 31.6 87 da6 124.0 22.0 766.639.95 31.4 84 da70.0 136.9 0.0 801.30 0.6 4 The system has plenty of free RAM, is 99.7% idle, has nothing else going on, and runs like a one-legged dog. There are no error messages or any sign of a problem anywhere, other than the really terrible performance. (When not rebuilding, it does light NFS duty. That performance is similarly bad, but has never really mattered.) Similar systems running Solaris put out 10x these numbers claiming 30% busy instead of 90% busy. Does anyone have any suggestions for how I could troubleshoot this further? At this point, I'm kind of at a loss as to where to go from here. My goal is to try to phase out the Solaris machines, but this is kind of a roadblock. Thanks for any advice! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- James Gosnell, ACP ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Terrible disk performance with LSI / FreeBSD 9.2-RC1
On Wed, Aug 7, 2013 at 3:15 PM, James Gosnell jamesgosn...@gmail.com wrote: Maybe one of your drives is bad, so it's constantly doing error correction? Not according to SMART; all the drives report no problems. Also, all the drives seem to perform in lock-step for both reading and writing. E.g. when one drive in an array is failing, all the drives may be pulling the same # of reads, but the failing drive will often report 100% busy and/or multi-second svc_t's and the others will sit at 4% with 20msec svc_t's or similar. In this case, it's acting like the disks are all hugely overloaded. Except without even the high svc_t's I typically associate with overworking an array. The speeds do fluctuate. Last night it was down to 64k/sec reads per drive (about 15 reads/sec) and still reporting 90% busy on all drives. It feels like some sort of issue with the bus/controller/kernel/driver/ZFS that is affecting all the drives equally. Also, even ls takes forever (10-30 seconds for ls -lh /) but when it eventually does finish, time ls -lh / reports: 0.02 real 0.00 user 0.00 sys Really not sure what to make of that. An attempt to do ps axlww | fgrep ls while the ls was running failed, because the ps hangs just as long as the ls. So it's like the system is just repeatedly putting anything that touches the disks on hold, even if all the data being requested is clearly in cache. (Even apparently loading the binary for /bin/ls or doing ls -lh / twice in a row.) Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Terrible disk performance with LSI / FreeBSD 9.2-RC1
On 07/08/2013 21:36, J David wrote: It feels like some sort of issue with the bus/controller/kernel/driver/ZFS that is affecting all the drives equally. Also, even ls takes forever (10-30 seconds for ls -lh /) but when it eventually does finish, time ls -lh / reports: 0.02 real 0.00 user 0.00 sys Really not sure what to make of that. An attempt to do ps axlww | fgrep ls while the ls was running failed, because the ps hangs just as long as the ls. So it's like the system is just repeatedly putting anything that touches the disks on hold, even if all the data being requested is clearly in cache. (Even apparently loading the binary for /bin/ls or doing ls -lh / twice in a row.) As a suggestion, what happens if you read from the drives directly? Boot in single user and try reading a Gb or two using /bin/dd. It might eliminate or confirm a problem with ZFS. Regards, Frank. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Terrible disk performance with LSI / FreeBSD 9.2-RC1
We have a machine running 9.2-RC1 that's getting terrible disk I/O performance. Its performance has always been pretty bad, but it didn't really become clear how bad until we did a zpool replace on one of the drives and realized it was going to take 3 weeks to rebuild a 1TB drive. The hardware specs are: - 2 x Xeon L5420 - 32 GiB RAM - LSI Logic SAS 1068E - 2 x 32GB SSD's - 6 x 1TB Western Digital RE3 7200RPM SATA The LSI controller has the most recent firmware I'm aware of (6.36.00.00 / 1.33.00.00 dated 2011.08.24), is in IT mode, and appears to be working fine: mpt0 Adapter: Board Name: USASLP-L8i Board Assembly: USASLP-L8i Chip Name: C1068E Chip Revision: B3 RAID Levels: none mpt0 Configuration: 0 volumes, 8 drives drive da0 (30G) ONLINE FTM32GL25H 10 SATA drive da1 (29G) ONLINE SSDSA2SH032G1GN 8860 SATA drive da2 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da3 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da4 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da5 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da6 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA drive da7 (931G) ONLINE WDC WD1002FBYS-0 0C05 SATA The eight drives are configured as ZIL, L2ARC on SSD and a six drive raidz2 on the spinning disks. We did a ZFS replace on the last drive in the line, and the resilver is proceeding at less than 800k/sec. extended device statistics device r/s w/skr/skw/s qlen svc_t %b da00.0 0.0 0.0 0.10 0.9 0 da10.0 8.2 0.019.90 0.1 0 da2 125.6 23.0 768.240.54 33.0 88 da3 126.6 23.1 769.041.34 32.3 89 da4 126.0 24.0 768.542.74 32.1 88 da5 125.9 22.0 768.240.14 31.6 87 da6 124.0 22.0 766.639.95 31.4 84 da70.0 136.9 0.0 801.30 0.6 4 The system has plenty of free RAM, is 99.7% idle, has nothing else going on, and runs like a one-legged dog. There are no error messages or any sign of a problem anywhere, other than the really terrible performance. (When not rebuilding, it does light NFS duty. That performance is similarly bad, but has never really mattered.) Similar systems running Solaris put out 10x these numbers claiming 30% busy instead of 90% busy. Does anyone have any suggestions for how I could troubleshoot this further? At this point, I'm kind of at a loss as to where to go from here. My goal is to try to phase out the Solaris machines, but this is kind of a roadblock. Thanks for any advice! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: virtualbox-ose fails to build on FreeBSD 9.2-BETA2 #0 r253698
How to svn to 9-stable, make world (etc)? How to delete all installed ports? And then rm -rf /usr/local/*? Nice hints! Felix 发自我的 iPad 在 2013-8-5，3:53，John free...@growveg.net 写道： On 02/08/2013 16:54, John wrote: Hello list, I'm trying to install virtualbox on a new machine running FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a problem with the port or my machine? This was fixed by: commenting everything out of /etc/make.conf svn to 9-stable, make world (etc) reboot then deleting all installed ports then removing everything from /usr/local then rm -rf /usr/ports portsnap install svn then checkout ports install virtualbox-ose sorry for the noise -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: virtualbox-ose fails to build on FreeBSD 9.2-BETA2 #0 r253698
On 02/08/2013 16:54, John wrote: Hello list, I'm trying to install virtualbox on a new machine running FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a problem with the port or my machine? This was fixed by: commenting everything out of /etc/make.conf svn to 9-stable, make world (etc) reboot then deleting all installed ports then removing everything from /usr/local then rm -rf /usr/ports portsnap install svn then checkout ports install virtualbox-ose sorry for the noise -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
virtualbox-ose fails to build on FreeBSD 9.2-BETA2 #0 r253698
Hello list, I'm trying to install virtualbox on a new machine running FreeBSD 9.2-BETA2 #0 r253698. The ports version is 324162. Is it a problem with the port or my machine? Here is my make.conf: # cat /etc/make.conf CC=clang CXX=clang++ CPP=clang-cpp # added by use.perl 2013-07-30 20:08:48 PERL_VERSION=5.14.4 # no x11 WITHOUT_X11=yes I have no x11 because this is a server. Here is the error: In file included from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/VBox/log.h:36, from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:24: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:251: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:253: error: expected initializer before '*' token /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1196: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1216: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1468: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1507: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1507: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1522: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1533: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1559: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1601: error: 'PFNRTLOGPREFIX' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1638: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1699: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1719: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1748: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1781: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1801: error: 'va_list' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1830: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1838: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1847: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1856: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1928: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1937: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1946: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1955: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1966: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/include/iprt/log.h:1975: error: 'size_t' does not name a type /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:67: error: 'size_t' has not been declared /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp: In function 'void* HGSMIHeapAlloc(HGSMIHEAP*, HGSMISIZE, uint8_t, uint16_t)': /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:303: error: 'size_t' was not declared in this scope /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:303: error: expected `;' before 'cbAlloc' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp:305: error: 'cbAlloc' was not declared in this scope kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.16/out/freebsd.amd64/release/obj/HGSMIGuestR0Lib/HGSMICommon.o] Error 1 The failing command: @g++ -c
