Re: slow zvol performance compared to files on the same pool
On Sat, Jan 3, 2009 at 7:02 PM, David Ehrmann wrote: > Andrew Snow wrote: >> >> On 7.x (where ZFS is really quite broken for server use - don't waste too >> much time on it) > > How exactly is it broken? I know there are some issues, but so serious > you'd say it's broken? It's not "broken" on 7.1, it just requires manual tuning and monitoring. Preferably, it should only be run on amd64 systems with lots of RAM, but it can be run on i386 systems with at least 2 GB of RAM (some people have it running on 32-bit systems with less RAM). ZFS in 8-CURRENT is a more recent version (v13 I believe, while 7.1 is v6), and has a bunch of auto-tuning features, along with a much higher kmem_size_max setting (512 GB vs 2 GB I believe). -- Freddie Cash fjwc...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: slow zvol performance compared to files on the same pool
> On 7.x (where ZFS is really quite broken for server use - don't waste > too much time on it) the ZVOL code did an "fsync" after every single > block write. Its a testament to your fast disks that you got as high as > 12mb/s. I don't know why your read speed was so bad, but you should try > again on 8-current as numerous fixes and improvements have happened. Ah, thatnks. That explains it perfectly. I'll re-do the read test and also give 8-CURRENT a try if I get the time. Thanks. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Make world builderror on 7.1-BETA2 with latest cvsup
On Sun, Jan 04, 2009 at 11:39:28AM +0100, Mattias Björk wrote: > Hello again, > > > Garrett Cooper wrote: > > On Fri, Jan 2, 2009 at 11:52 AM, Mattias Björk > > wrote: > >> Hello Garrett, > >> > >> > >> Sorry for top posting, but here is the attachment of the log. > >> > >> > >> Garrett Cooper wrote: > >>> On Jan 1, 2009, at 19:23, Mattias Björk wrote: > >>> > Hello everybody, > > First of all, my bad if this get sent two times. > > I have a compile error/problem when building world. > > My uname -a output is: > > FreeBSD barabolaptop 7.1-BETA2 FreeBSD 7.1-BETA2 #0: Thu Dec 4 20:52:35 > CET 2008 r...@barabolaptop:/usr/obj/usr/src/sys/BARABOLAPTOP i386 > > My make.conf looks like: > > # added by use.perl 2008-12-03 00:58:09 > PERL_VER=5.8.8 > PERL_VERSION=5.8.8 > WRKDIRPREFIX=/var/tmp > > > The options.h file in /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/options.h > > Here are the output of options.h from pastebin: > > http://pastebin.com/m254dfedf > > > When I run "make -j1 buildworld" i get the error is as following: > > http://pastebin.com/m57738677 > > I don't know much of programming (if any), but I have tried to change > things in (remove OPT_w from both places) options.h and runned > "make -j1 -DNOCLEAN buildworld" > > But that have not solve anything of this, perhaps some can shine some > light on this or have I missed something trivial? > I can build ports and so on without any problems. > > Thank you. > >>> Not enough data. Please send a full compressed version of the log to me. > >>> Thanks! > >>> -Garrett > > > > That's really odd why the symbol was redefined. Here're the relevant > > sections of the log: > > > > c_tools/../../../../contrib/gcc/gencheck.c > > In file included from ./tm.h:4, > > from > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/gencheck.c:25: > > ./options.h:901: error: redeclaration of enumerator 'OPT_w' > > ./options.h:899: error: previous definition of 'OPT_w' was here > > *** Error code 1 > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > > > Looking back, I'm not sure why OPT_w is printed into the file twice. > > I wonder if you met a rare race condition where options.sh printed out > > that line twice; then again that's unlikely, given the > > reproducibility... I could be wrong however. > > Is your source tree based off of RELENG_7 and what cvsup server is it > > synced against? > > -Garrett > > > I'm using cvsup.se.freebsd.org, cvsup.dk.freebsd.org, > cvsup.no.freebsd.org I have tried to remove /usr/src/* right now and > downloaded it again but it did not help after the build. > > So I have no idea what to do from here. > > But I guess It would be solved sometime in the future. Did you clean your /usr/obj/ directory? -- Dominik Żyła If you want a picture of the future, imagine a boot stamping on a human face - for ever.. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Make world builderror on 7.1-BETA2 with latest cvsup
Hello again, Garrett Cooper wrote: On Fri, Jan 2, 2009 at 11:52 AM, Mattias Björk wrote: Hello Garrett, Sorry for top posting, but here is the attachment of the log. Garrett Cooper wrote: On Jan 1, 2009, at 19:23, Mattias Björk wrote: Hello everybody, First of all, my bad if this get sent two times. I have a compile error/problem when building world. My uname -a output is: FreeBSD barabolaptop 7.1-BETA2 FreeBSD 7.1-BETA2 #0: Thu Dec 4 20:52:35 CET 2008 r...@barabolaptop:/usr/obj/usr/src/sys/BARABOLAPTOP i386 My make.conf looks like: # added by use.perl 2008-12-03 00:58:09 PERL_VER=5.8.8 PERL_VERSION=5.8.8 WRKDIRPREFIX=/var/tmp The options.h file in /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/options.h Here are the output of options.h from pastebin: http://pastebin.com/m254dfedf When I run "make -j1 buildworld" i get the error is as following: http://pastebin.com/m57738677 I don't know much of programming (if any), but I have tried to change things in (remove OPT_w from both places) options.h and runned "make -j1 -DNOCLEAN buildworld" But that have not solve anything of this, perhaps some can shine some light on this or have I missed something trivial? I can build ports and so on without any problems. Thank you. Not enough data. Please send a full compressed version of the log to me. Thanks! -Garrett That's really odd why the symbol was redefined. Here're the relevant sections of the log: c_tools/../../../../contrib/gcc/gencheck.c In file included from ./tm.h:4, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/gencheck.c:25: ./options.h:901: error: redeclaration of enumerator 'OPT_w' ./options.h:899: error: previous definition of 'OPT_w' was here *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 Looking back, I'm not sure why OPT_w is printed into the file twice. I wonder if you met a rare race condition where options.sh printed out that line twice; then again that's unlikely, given the reproducibility... I could be wrong however. Is your source tree based off of RELENG_7 and what cvsup server is it synced against? -Garrett I'm using cvsup.se.freebsd.org, cvsup.dk.freebsd.org, cvsup.no.freebsd.org I have tried to remove /usr/src/* right now and downloaded it again but it did not help after the build. So I have no idea what to do from here. But I guess It would be solved sometime in the future. Thanks so far :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Samsung SCX-4200 printer
Is there a way to install the SCX-4200 printer on a FreeBSD box ? The printer is delivered with the install software required for Linux. And CUPS does not seem to "know" it. Thank you in advance for any help. Harald Weis -- FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Make world builderror on 7.1-BETA2 with latest cvsup
Dominik Żyła wrote: On Sun, Jan 04, 2009 at 11:39:28AM +0100, Mattias Björk wrote: Hello again, Garrett Cooper wrote: On Fri, Jan 2, 2009 at 11:52 AM, Mattias Björk wrote: Hello Garrett, Sorry for top posting, but here is the attachment of the log. Garrett Cooper wrote: On Jan 1, 2009, at 19:23, Mattias Björk wrote: Hello everybody, First of all, my bad if this get sent two times. I have a compile error/problem when building world. My uname -a output is: FreeBSD barabolaptop 7.1-BETA2 FreeBSD 7.1-BETA2 #0: Thu Dec 4 20:52:35 CET 2008 r...@barabolaptop:/usr/obj/usr/src/sys/BARABOLAPTOP i386 My make.conf looks like: # added by use.perl 2008-12-03 00:58:09 PERL_VER=5.8.8 PERL_VERSION=5.8.8 WRKDIRPREFIX=/var/tmp The options.h file in /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/options.h Here are the output of options.h from pastebin: http://pastebin.com/m254dfedf When I run "make -j1 buildworld" i get the error is as following: http://pastebin.com/m57738677 I don't know much of programming (if any), but I have tried to change things in (remove OPT_w from both places) options.h and runned "make -j1 -DNOCLEAN buildworld" But that have not solve anything of this, perhaps some can shine some light on this or have I missed something trivial? I can build ports and so on without any problems. Thank you. Not enough data. Please send a full compressed version of the log to me. Thanks! -Garrett That's really odd why the symbol was redefined. Here're the relevant sections of the log: c_tools/../../../../contrib/gcc/gencheck.c In file included from ./tm.h:4, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/gencheck.c:25: ./options.h:901: error: redeclaration of enumerator 'OPT_w' ./options.h:899: error: previous definition of 'OPT_w' was here *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 Looking back, I'm not sure why OPT_w is printed into the file twice. I wonder if you met a rare race condition where options.sh printed out that line twice; then again that's unlikely, given the reproducibility... I could be wrong however. Is your source tree based off of RELENG_7 and what cvsup server is it synced against? -Garrett I'm using cvsup.se.freebsd.org, cvsup.dk.freebsd.org, cvsup.no.freebsd.org I have tried to remove /usr/src/* right now and downloaded it again but it did not help after the build. So I have no idea what to do from here. But I guess It would be solved sometime in the future. Did you clean your /usr/obj/ directory? Yes I have also done that, still no luck there. Thanks anyway. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic in RELENG_7_1 with fxp(4)
On Sat, Jan 03, 2009 at 10:16:58PM -0800, Garrett Cooper wrote:
> On Jan 3, 2009, at 5:17 PM, Brandon Weisz wrote:
>
> >After running 7-PRERELEASE from around November 25th, I upgraded
> >today to find the system panics repeatably on RELENG_7_1 sources. I
> >can boot back to the old kernel and it operates as expected. It
> >seems to be related to fxp(4).
> >
> >FreeBSD didy.internal 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Sat Jan 3
> >18:11:18 CST 2009 bwe...@didy.internal:/usr/obj/usr/src/sys/
> >DIDY i386
> >
> >(19:00:35 bwe...@didy ) 507 $ sudo kgdb
> >kernel.debug /var/crash/vmcore.2
> >GNU gdb 6.1.1 [FreeBSD]
> >Copyright 2004 Free Software Foundation, Inc.
> >GDB is free software, covered by the GNU General Public License, and
> >you are
> >welcome to change it and/or distribute copies of it under certain
> >conditions.
> >Type "show copying" to see the conditions.
> >There is absolutely no warranty for GDB. Type "show warranty" for
> >details.
> >This GDB was configured as "i386-marcel-freebsd"...
> >
> >Unread portion of the kernel message buffer:
> >
> >
> >Fatal trap 12: page fault while in kernel mode
> >cpuid = 0; apic id = 00
> >fault virtual address = 0x40c
> >fault code = supervisor read, page not present
> >instruction pointer = 0x20:0xc0a94510
> >stack pointer = 0x28:0xe677b878
> >frame pointer = 0x28:0xe677b88c
> >code segment= base 0x0, limit 0xf, type 0x1b
> >= DPL 0, pres 1, def32 1, gran 1
> >processor eflags= interrupt enabled, resume, IOPL = 0
> >current process = 843 (ntpd)
> >trap number = 12
> >panic: page fault
> >cpuid = 0
> >Uptime: 25s
> >Physical memory: 995 MB
> >Dumping 94 MB: 79 63 47 31 15
> >
> >Reading symbols from /boot/kernel/vesa.ko...Reading symbols from /
> >boot/kernel/vesa.ko.symbols...done.
> >done.
> >Loaded symbols for /boot/kernel/vesa.ko
> >Reading symbols from /boot/kernel/accf_http.ko...Reading symbols
> >from /boot/kernel/accf_http.ko.symbols...done.
> >done.
> >Loaded symbols for /boot/kernel/accf_http.ko
> >Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /
> >boot/kernel/acpi.ko.symbols...done.
> >done.
> >Loaded symbols for /boot/kernel/acpi.ko
> >Reading symbols from /boot/kernel/pflog.ko...Reading symbols from /
> >boot/kernel/pflog.ko.symbols...done.
> >done.
> >Loaded symbols for /boot/kernel/pflog.ko
> >Reading symbols from /boot/kernel/pf.ko...Reading symbols from /boot/
> >kernel/pf.ko.symbols...done.
> >done.
> >Loaded symbols for /boot/kernel/pf.ko
> >Reading symbols from /boot/kernel/nullfs.ko...Reading symbols from /
> >boot/kernel/nullfs.ko.symbols...done.
> >done.
> >Loaded symbols for /boot/kernel/nullfs.ko
> >Reading symbols from /boot/kernel/logo_saver.ko...Reading symbols
> >from /boot/kernel/logo_saver.ko.symbols...done.
> >done.
> >Loaded symbols for /boot/kernel/logo_saver.ko
> >#0 doadump () at pcpu.h:196
> >196 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
> >(kgdb) list *0xc0a94510
> >0xc0a94510 is in _bus_dmamap_sync (/usr/src/sys/i386/i386/
> >busdma_machdep.c:935).
> >930 CTR4(KTR_BUSDMA, "%s: tag %p tag flags 0x%x op 0x%x "
> >931 "performing bounce", __func__, op, dmat,
> >dmat->flags);
> >932
> >933 if (op & BUS_DMASYNC_PREWRITE) {
> >934 while (bpage != NULL) {
> >935 bcopy((void *)bpage->datavaddr,
> >936 (void *)bpage->vaddr,
> >937 bpage->datacount);
> >938 bpage = STAILQ_NEXT(bpage, links);
> >939 }
> >(kgdb) bt
> >#0 doadump () at pcpu.h:196
> >#1 0xc079c1b7 in boot (howto=260) at /usr/src/sys/kern/
> >kern_shutdown.c:418
> >#2 0xc079c489 in panic (fmt=Variable "fmt" is not available.
> >) at /usr/src/sys/kern/kern_shutdown.c:574
> >#3 0xc0ab03bc in trap_fatal (frame=0xe677b838, eva=1036) at /usr/
> >src/sys/i386/i386/trap.c:939
> >#4 0xc0ab0640 in trap_pfault (frame=0xe677b838, usermode=0,
> >eva=1036) at /usr/src/sys/i386/i386/trap.c:852
> >#5 0xc0ab0ffc in trap (frame=0xe677b838) at /usr/src/sys/i386/i386/
> >trap.c:530
> >#6 0xc0a96e6b in calltrap () at /usr/src/sys/i386/i386/exception.s:
> >159
> >#7 0xc0a94510 in _bus_dmamap_sync (dmat=0xc4048880, map=0xc416e800,
> >op=4) at /usr/src/sys/i386/i386/busdma_machdep.c:933
> >#8 0xc05cc3cd in fxp_start_body (ifp=0xc4163000) at /usr/src/sys/
> >dev/fxp/if_fxp.c:1396
> >#9 0xc05ccc77 in fxp_start (ifp=0xc4163000) at /usr/src/sys/dev/fxp/
> >if_fxp.c:1183
> >#10 0xc0830a89 in if_start (ifp=0xc4163000) at /usr/src/sys/net/if.c:
> >2768
> >#11 0xc08374cb in ether_output_frame (ifp=0xc4163000, m=0xc43a5600)
> >at /usr/src/sys/net/if_ethe
X11 on Dell D830 with latest 7.1-PRERELEASE
Hi, I've got a Dell Latitude D830 running 7.1-PRERELEASE/amd64 which I've just csup'd to the -STABLE as of 5-Jan-2009, and after going thru' the std build+install; XOrg now comes up with a blank screen, sometimes interspersed with green dots. I did test out X prior to doing an installworld, and that came up with no problems. However, after doing an installworld, X is now broken. Prior to this update, the D830 was running -STABLE from Nov-2008; which appeared to work fine. All ports are up to date. I'd appreciate any help in resolving this problem. Cheers. -- Jonathan Chen -- "Irrationality is the square root of all evil" - Douglas Hofstadter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 7.1-RELEASE Available...
Just a quick note for those of you not subscribed to freebsd-annou...@. FreeBSD 7.1 is (finally...) released. The announcement is here: http://www.freebsd.org/releases/7.1R/announce.html Sorry for the delays and thanks for your continued interest in and support of FreeBSD. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: X11 on Dell D830 with latest 7.1-PRERELEASE
On Sun, Jan 4, 2009 at 7:17 PM, Jonathan Chen wrote: > Hi, > > I've got a Dell Latitude D830 running 7.1-PRERELEASE/amd64 which I've > just csup'd to the -STABLE as of 5-Jan-2009, and after going thru' the > std build+install; XOrg now comes up with a blank screen, sometimes > interspersed with green dots. I did test out X prior to doing an > installworld, and that came up with no problems. However, after doing > an installworld, X is now broken. > > Prior to this update, the D830 was running -STABLE from Nov-2008; > which appeared to work fine. All ports are up to date. > > I'd appreciate any help in resolving this problem. > > Cheers. > -- > Jonathan Chen Jonathan, What video card driver are you using and have you recompiled the driver? Thanks, -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
On Wed, Dec 31, 2008 at 06:34:08AM +0100, Barbara wrote: > Hello, > one of my motherboards has an onboard Attansic network interface, I > think an AR8121. > > # pciconf -lcv > no...@pci0:4:0:0: class=0x02 > card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00 > vendor = 'Attansic > (Now owned by Atheros)' > device = 'L1 Gigabit Ethernet 10/100/1000Base-T > Ethernet Controller' > class = network > subclass = ethernet > cap > 01[40] = powerspec 2 supports D0 D3 current D0 > cap 05[48] = MSI supports > 1 message, 64 bit > cap 10[58] = PCI-Express 1 endpoint > cap 03[6c] = VPD > > > Today I decided to give it a try. > But if I try loading the if_age module, the > system prints the following lines and then it freezes. > > age0: Technology Corp, L1 Gigabit Ethernet> mem 0xfbdc-0xfbdf irq 36 at > device 0.0 on pci4 > age0: PCI device revision : 0x00b0 > age0: Chip id/revision : > 0x9006 > age0: 1280 Tx FIFO, 2364 Rx FIFO > age0: MSIX count : 0 > age0: MSI count : > 1 > age0: Using 1 MSI messages. > age0: Read request size : 512 bytes. > age0: TLP > payload size : 128 bytes. > I guess it could be related with VPD access code in age(4) or automatic power-down feature of hardware. Unfortunately I have no longer access to L1 hardware so it looks hard to write a patch for the issue. Would you try following instructions? - Shutdown your box. - Completely remove power cord from your system and wait 5 to 10 min.(Just turning system off is not enough.) - Make sure to plug UTP cable to your controller before system boot. - Plug power cord and let system boot. - Enter BIOS menu and search onboard PCIe LAN configuration in the menu. If "LAN Option ROM" was enabled, disable the option. - Some motherboard might have set another option for "Check Atheros LAN cable". If it was set, disable it. If you also have an option for "Asus Express Gate" try disabling it. - Save changes and reboot. Does that make any difference? -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
