http://blog.gmane.org/gmane.os.freebsd.current hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.os.freebsd.current/142274 <pre>To respond to my own mail again: * should the cardbus slot peripherals be detached and reattached upon resume? Or should it be just suspend/resumed? * here's what I see during suspend: wlan1: link state changed to DOWN [100741]: ieee80211_reset_bss: iv_bss=0xc969e000, new iv_bss=0xc96a5000 [100480] cbb0: Opening memory: [100480] ath1: detached pci0:21:0:0: Transition from D0 to D2 [100480] pci21: failed to set ACPI power state D2 on \\_SB_.PCI0.PCI1.CDBS: AE_BAD_PARAMETER [100480] vga0: saving 4612 bytes of video state [100480] vga0: saving color palette [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP0: AE_BAD_PARAMETER [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP1: AE_BAD_PARAMETER [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP2: AE_BAD_PARAMETER [100480] pci0: failed to set ACPI power state D2 on \\_SB_.PCI0.EXP3: AE_BAD_PARAMETER .. would someone with some ACPI clue please help me figure out how broken the ACPI code in my T60 BIOS is? :) Thanks, Adrian _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Adrian Chadd 2012-05-25T16:52:15 http://permalink.gmane.org/gmane.os.freebsd.current/142272 <pre> This is very true for reads, not for writes because it is a COW filesystem so writes are usually sequencial disk-wise. </pre> Jeremie Le Hen 2012-05-25T12:58:57 http://permalink.gmane.org/gmane.os.freebsd.current/142271 <pre>Hi, On Fri, 25 May 2012, Niclas Zeising wrote: NZ&gt;Sometime quite recent a change to FreeBSD CURRENT makes it almost impossible NZ&gt;to run it as a virtualbox guest, at least under Windows. If I roll back the NZ&gt;vbox machine to a (unfortunately quite old, from January) CURRENT everything NZ&gt;seems to be working. NZ&gt;The issue is that the virtual machine runs very very slow, and makes the host NZ&gt;almost impossible to work with, especially during compiles and other NZ&gt;activities involving the CPU and the disk. I have also experienced that the NZ&gt;host machine crashes, but that might be unrelated. NZ&gt;Is anyone else experiencing this, or am I doing something very wrong? I'm running current compiled with CLANG on the latest stable virtualbox under Win7. It works good, the only issue I had a couple of days ago when compiling world with -j4 (I've a 2-core with HTT) was that the CPUs were not raising their speed. They were just running on 780MHz and the compilation took half a day. A reboot of windows 'fixed' this. Normally if I do such a compile then both CPUs go up stable to 3.3GHz. I suspect that this is a bug in the BIOS or Windows where the frequency control gets stuck. NZ&gt;Let me know if I need to provide more information or if I can help in some NZ&gt;other way. Maybe first try to check with hwinfo what your CPUs are doing. harti _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Harti Brandt 2012-05-25T11:53:45 http://permalink.gmane.org/gmane.os.freebsd.current/142270 <pre>Hi! Sometime quite recent a change to FreeBSD CURRENT makes it almost impossible to run it as a virtualbox guest, at least under Windows. If I roll back the vbox machine to a (unfortunately quite old, from January) CURRENT everything seems to be working. The issue is that the virtual machine runs very very slow, and makes the host almost impossible to work with, especially during compiles and other activities involving the CPU and the disk. I have also experienced that the host machine crashes, but that might be unrelated. Is anyone else experiencing this, or am I doing something very wrong? Let me know if I need to provide more information or if I can help in some other way. Best Regards! _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Niclas Zeising 2012-05-25T11:30:57 http://permalink.gmane.org/gmane.os.freebsd.current/142269 <pre>To respond to my own email: * if I unload cbb/pccard/cardbus and reload them, suddenly the slot works. * I've been toying with S3 suspend to RAM, so I wondered if it were that. Yes, it seems to be suspend related. I'll do some more thorough testing tomorrow, but once I suspend, the ath(4) NIC gets detached from the cardbus slot, then upon resume the NIC isn't found (bus timeout) and won't be until I unload/reload the modules. Should pccard/cbb/cardbus 'properly' handle S3 suspend/resume? Does it work for anyone else? Adrian _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Adrian Chadd 2012-05-25T07:53:33 http://permalink.gmane.org/gmane.os.freebsd.current/142268 <pre>Hi all, I've just upgraded to 9-stable and I'm seeing the following error on my Lenovo Thinkpad T60. 'cbb0: Warning: Bus reset timeout' This is a very recent bug. I was running 9-stable from about 3 weeks ago (before BSDCan 2012) and cardbus was working fine. Would anyone have any culprit commits for me to try reverting? Having cardbus work on these lenovo thinkpads is very important to me and ath(4) development. :) Thanks, adrian _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Adrian Chadd 2012-05-25T07:38:26 http://permalink.gmane.org/gmane.os.freebsd.current/142267 <pre> If your disk dies then you need a redundant copy of your data - either via backups or via RAID. Normally, you'd run ZFS with some level of redundancy so that disk failures did not result in data loss. That said, ZFS is touchier about data - if it can't verify the checksums in your data, it will refuse to give it to you - whereas UFS will hand you back a pile of bytes that may or may the same as what you gave it to store. And you can't necessarily get _any_ data off a failed disk. 4TB disks are available but not really economical at present. 2TB disks still seem to be the happy medium. If your data will compress down to 2TB then save it to a disk, otherwise split your backups across a pair of disks. A 2TB disk with enclosure is &lt;&lt;USD150. If you don't trust that, buy a second set. (And if you value your data, get a trusted friend to store one copy at their house in case anything happens at your house). I have had lots of problems at $work with Solaris UFS quietly corrupting data following crashes. At least with ZFS, you have a detter chance of knowing when your data has been corrupted. </pre> Peter Jeremy 2012-05-24T21:01:28 http://permalink.gmane.org/gmane.os.freebsd.current/142266 <pre> Updated to r235926 &amp; kernel build completed successfully. Sevan _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Sevan / Venture37 2012-05-24T20:50:02 http://permalink.gmane.org/gmane.os.freebsd.current/142265 <pre> We actually use it in very random high IOP's applications with small requests, so high standard disk's aren't even an option so SDD's all the way and we see nice performance. I can't say we've compared it to say FFS as that simply doesn't provide the management tools we needed so wasn't even considered, but its far from shabby in our environment :) Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster&lt; at &gt;multiplay.co.uk. _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Steven Hartland 2012-05-24T20:30:17 http://permalink.gmane.org/gmane.os.freebsd.current/142264 <pre>2012/5/7 Steve Wills &lt;swills&lt; at &gt;freebsd.org&gt; hm.. looks like problem is still here. I'm trying update my r234992 to r235887 http://pastebin.com/stm7b8hQ _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Sergey Dyatko 2012-05-24T20:10:59 http://permalink.gmane.org/gmane.os.freebsd.current/142263 <pre> - ZFS is not optimal for situations where there are a lot of small, randomly dispersed IOs around the disk space. Like in any sort of RDBMS. Even so, ZFS is certainly my personal default nowadays. On a machine of any size, the question is not "should I use ZFS?" but "are there any good reasons why I shouldn't use ZFS? (And if so, what could I do to make it possible to use ZFS anyhow...)" With Andriy's recent patches to zfsboot to extend support for Boot Environments, it's all starting to look particularly sexy. Cheers, Matthew </pre> Matthew Seaman 2012-05-24T19:58:52 http://permalink.gmane.org/gmane.os.freebsd.current/142262 <pre> - ZFS is not optimal for situations where there are a lot of small, randomly dispersed IOs around the disk space. Like in any sort of RDBMS. Even so, ZFS is certainly my personal default nowadays. On a machine of any size, the question is not "should I use ZFS?" but "are there any good reasons why I shouldn't use ZFS? (And if so, what could I do to make it possible to use ZFS anyhow...)" With Andriy's recent patches to zfboot to extend support for Boot Environments, it's all starting to look particularly sexy. Cheers, Matthew </pre> Matthew Seaman 2012-05-24T19:58:38 http://permalink.gmane.org/gmane.os.freebsd.current/142261 <pre> Something is going wrong with your include paths; most likely your CFLAGS gets mangled. The actual mkdep command line should have been similar to (wrapped for clarity): CC='clang' \ mkdep \ -f .depend \ -a \ -I/usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/include \ -I/usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/tools/clang/include \ -I/usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen \ -I. \ -I/usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/../../lib/clang/include \ -DLLVM_ON_UNIX \ -DLLVM_ON_FREEBSD \ -D__STDC_LIMIT_MACROS \ -D__STDC_CONSTANT_MACROS \ -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd10.0\" \ -DDEFAULT_SYSROOT=\"\" \ -I/usr/obj/usr/src/tmp/legacy/usr/include \ /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/Error.cpp \ /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/Main.cpp \ /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/Record.cpp \ /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TableGenAction.cpp \ /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TableGenBackend.cpp \ /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TGLexer.cpp \ /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TGParser.cpp Are you appending or assigning to CFLAGS in make.conf/src.conf? _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Dimitry Andric 2012-05-24T19:29:52 http://permalink.gmane.org/gmane.os.freebsd.current/142260 <pre> I've seen these too, and it seems clang produces debug info which ctfconvert can't handle, for some reason. However, in my case, the kernel build doesn't abort at all, it continues and all the object files seem to work just fine. I don't know much much about the dtrace/ctfconvert stuff though, so I will have to ask somebody else to step up to investigate, and hopefully fix it. :) ... Ah, I think that it works for me, because I don't define STRIP to empty. Just as an experiment, can you try commenting that setting, and do a clean build of your kernel? _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Dimitry Andric 2012-05-24T19:21:49 http://permalink.gmane.org/gmane.os.freebsd.current/142259 <pre> Hence I dropped it in current. I have not exhausted all options, because I keep discovering things. And given the long time with FreeBSD, I tend to reexamine man pages to see what people have added and/or documented. So before I start hammering at the scripts, I'll need to go through wat is already there.. Thanx, --WjW _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Willem Jan Withagen 2012-05-24T18:01:28 http://permalink.gmane.org/gmane.os.freebsd.current/142258 <pre>Hi I'm unable to build the generic kernel, seeing lots of "failed to retrieve array bounds" errors (129 to be exact) starting with ERROR: scsi_all.c: die 43574: failed to retrieve array bounds &amp; stoping at cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/dev/ata/ata-card.c ctfconvert -L VERSION -g aic_pccard.o ctfconvert -L VERSION -g ata-card.o ctfconvert -L VERSION -g intel_dp.o ERROR: intel_dp.c: die 24561: failed to retrieve array bounds cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/dev/cs/if_cs_pccard.c 1 error *** [all] Error code 2 1 error *** [all] Error code 2 1 error *** [modules-all] Error code 2 cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/dev/ed/if_ed_pccard.c ctfconvert -L VERSION -g if_an_pccard.o ctfconvert -L VERSION -g if_cs_pccard.o ctfconvert -L VERSION -g if_ed_pccard.o 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 1 error Userland was built &amp; installed earlier this morning WITH_CLANG_IS_CC defined in src.conf, and the make.conf is as follows STRIP= CFLAGS+=-fno-omit-frame-pointer #CFLAGS= -O2 -fno-strict-aliasing -pipe #COPTFLAGS= -O -pipe #CXXFLAGS+= -fconserve-space #CPUTYPE?=core2 WITH_LCD_FILTERING="YES" VIDEO_DRIVER="intel" WITHOUT_NLS="YES" RUBY_VER=1.9 WITH_LCD_FILTERING="YES" # added by use.perl 2012-05-20 14:42:26 PERL_VERSION=5.12.4 Sevan / Venture37 _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Sevan / Venture37 2012-05-24T17:13:06 http://permalink.gmane.org/gmane.os.freebsd.current/142257 <pre> freebsd-rc&lt; at &gt; is not appropriate for discussing periodic, as the 2 are totally unrelated. At this time there is no dedicated maintainer for periodic, so if you find behavior that you don't like, and you've thoroughly exhausted the available configuration options, your only recourse is to submit a patch. hth, Doug _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Doug Barton 2012-05-24T17:05:48 http://permalink.gmane.org/gmane.os.freebsd.current/142256 <pre>Trying to build buildworld on FreeBSD 10-CURRENT/amd64 with CLANG today ends up in the following error: ===&gt; lib/clang/libllvmtablegen (obj,depend,all,install) /usr/obj/usr/src/tmp/usr/src/lib/clang/libllvmtablegen created for /usr/src/lib/clang/libllvmtablegen rm -f .depend CC='clang' mkdep -f .depend -a -I/usr/obj/usr/src/tmp/legacy/usr/include /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/Error.cpp /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/Main.cpp /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/Record.cpp /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TableGenAction.cpp /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TableGenBackend.cpp /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TGLexer.cpp /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/TGParser.cpp /usr/src/lib/clang/libllvmtablegen/../../../contrib/llvm/lib/TableGen/Error.cpp:15:10: fatal error: 'llvm/TableGen/Error.h' file not found #include "llvm/TableGen/Error.h" ^ 1 error generated. mkdep: compile failed *** [.depend] Error code 1 Stop in /usr/src/lib/clang/libllvmtablegen. *** [bootstrap-tools] Error code 1 Stop in /usr/src. *** [_bootstrap-tools] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. </pre> O. Hartmann 2012-05-24T16:53:59 http://permalink.gmane.org/gmane.os.freebsd.current/142255 <pre> Yes, please do! </pre> John Baldwin 2012-05-24T16:25:07 http://permalink.gmane.org/gmane.os.freebsd.current/142254 <pre> This is something we've solved quite nicely on PowerPC. The current code allows interrupt controllers to be regular device drivers, including support for systems with multiple interrupt controllers and domains, so I'd suggest pulling that code over if Warner hasn't done it yet. FDT (or real Open Firmware) really helps here. There's a lot of code in the PPC tree for running the same kernels on systems with very different properties (MMUs, firmware, paravirtualized and bare metal, multiple hypervisors, PICs, etc.) that may be helpful for ARM/MIPS GENERIC. The exact same PPC64 kernel can boot a PS3 under a paravirtualized hypervisor with custom firmware, a Powermac G5, or an IBM machine, with or without hypervisor, for instance. -Nathan _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Nathan Whitehorn 2012-05-24T16:21:25 http://permalink.gmane.org/gmane.os.freebsd.current/142252 <pre> On May 24, 2012, at 4:30 PM, Warner Losh wrote: I guess they all use same interrupt controller. Currently there can be only support for one intc built in kernel so that needs serious rework. Damjan _______________________________________________ freebsd-current&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe&lt; at &gt;freebsd.org" </pre> Damjan Marion 2012-05-24T15:58:25 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.os.freebsd.current