Re: status of autotuning freebsd for 9.2
On 13.07.2013 09:47, Alfred Perlstein wrote: Andre, we have a number of people running this patch in the following configurations: 6-8GB ram + 10gigE ethernet using iozone over NFS. As you haven't seen any problems yet I've asked RE to green light the MFC. -- Andre We're rolling it into the PCBSD rolling update as well. I'm thinking it makes sense to roll this into the 9.2 release to give us more scalability. -Alfred On 7/7/13 1:34 AM, Andre Oppermann wrote: On 07.07.2013 08:32, Alfred Perlstein wrote: Andre, Are you going to have time to MFC things from -current for auto-tuning -stable before 9.2? I simply ran out of time on Friday and MFCing such a big change requires more testing. I fear (maybe unnecessarily?) that we are about to ship yet another release that can't do basic 10gigE when sufficient memory exists. There was some debate with myself whether such a behavior changing MFC would be appropriate for a mid-stream stable release. I guess yes, though a number of people who currently set the parameters manually would have to remove their tuning settings. If you don't have time, then let me know and I'll see what I can do. Can you help me with with testing? ___ 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: script(1), cfmakeraw() and Ctrl-Z
On 15.07.2013 04:37, Jilles Tjoelker wrote: > On Mon, Jul 15, 2013 at 12:14:19AM +0700, Eugene Grosbein wrote: >> I've noted that commands like "script -qa /tmp/log sleep 100" >> cannot be suspended with Ctrl-Z keys. The reason is call to cfmakeraw() >> in script.c - if I comment it out, Ctrl-Z starts to work as expected. > >> portupgrade uses script(1) so build/install process cannot be suspended too. >> (I'm building libreoffice-4.04 now) > >> The function cfmakeraw() is used since CVS revision 1.1 when script >> was imported with other "BSD 4.4 Lite Usr.bin Sources". > >> Is cfmakeraw() really needed? > > The cfmakeraw() call ensures that the processes running within script > get all control characters. For example, you can suspend a job in the > inner shell using Ctrl+Z. This indeed makes it impossible to suspend > script itself. Is it possible to achieve same effect of passing other control characters but Ctrl-Z? So, it would be possible suspend long-running portupgrade. Eugene Grosbein ___ 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: There is an error in chmod(1)
On 15 July 2013 00:19, Torfinn Ingolfsen wrote: > There is an error in the chmod(1) man page. > tingo@kg-v2$ uname -a > FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 > CEST 2012 > r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > tingo@kg-v2$ apropos ^sticky > sticky(7)- sticky text and append-only directories > tingo@kg-v2$ man 1 chmod | grep sticky >1000(the sticky bit). See chmod(2) and sticky(8). >t The sticky bit. > setmode(3), symlink(7), chown(8), mount(8), sticky(8) > This was fixed in head (and appeared in 9.x) but never merged to 8. I just merged the related change to 8-STABLE (the stable/8 branch). Thanks for reporting! -- wbr, pluknet ___ 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: script(1), cfmakeraw() and Ctrl-Z
On Mon, Jul 15, 2013 at 12:14:19AM +0700, Eugene Grosbein wrote: > I've noted that commands like "script -qa /tmp/log sleep 100" > cannot be suspended with Ctrl-Z keys. The reason is call to cfmakeraw() > in script.c - if I comment it out, Ctrl-Z starts to work as expected. > portupgrade uses script(1) so build/install process cannot be suspended too. > (I'm building libreoffice-4.04 now) > The function cfmakeraw() is used since CVS revision 1.1 when script > was imported with other "BSD 4.4 Lite Usr.bin Sources". > Is cfmakeraw() really needed? The cfmakeraw() call ensures that the processes running within script get all control characters. For example, you can suspend a job in the inner shell using Ctrl+Z. This indeed makes it impossible to suspend script itself. -- Jilles Tjoelker ___ 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: Is ATH_ENABLE_11N supposed to work on 9-stable?
On 14 July 2013 18:41, Adrian Chadd wrote: > Nope. It's a -10 thing. Okay, thanks for clarifying. Riggs ___ 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"
There is an error in chmod(1)
There is an error in the chmod(1) man page. tingo@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo@kg-v2$ apropos ^sticky sticky(7)- sticky text and append-only directories tingo@kg-v2$ man 1 chmod | grep sticky 1000(the sticky bit). See chmod(2) and sticky(8). t The sticky bit. setmode(3), symlink(7), chown(8), mount(8), sticky(8) HTH -- Torfinn Ingolfsen ___ 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"
script(1), cfmakeraw() and Ctrl-Z
Hi! I've noted that commands like "script -qa /tmp/log sleep 100" cannot be suspended with Ctrl-Z keys. The reason is call to cfmakeraw() in script.c - if I comment it out, Ctrl-Z starts to work as expected. portupgrade uses script(1) so build/install process cannot be suspended too. (I'm building libreoffice-4.04 now) The function cfmakeraw() is used since CVS revision 1.1 when script was imported with other "BSD 4.4 Lite Usr.bin Sources". Is cfmakeraw() really needed? Eugene Grosbein ___ 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: Is ATH_ENABLE_11N supposed to work on 9-stable?
Nope. It's a -10 thing. -adrian On 14 July 2013 08:01, Thomas Zander wrote: > Hi, > > from the mailing lists I couldn't figure out whether 11n is supposed > to work on stable since the existing mail threads seem to focus on > current exclusively. > > And since the option exists in the stable kernel code as well, albeit > neither in GENERIC nor in NOTES, I thought I could give it a try > anyway. > > I had some partial success. Test in station mode, WPA2 associated > properly, light traffic (browsing the web) seems to work okay as well. > However as soon as I try to really push some data through it, e.g. > rsync large files, the card drops all network traffic until I > disassociate and re-associate with the access point again (e.g. netif > restart). > > If 11N is just not ready in -stable yet, it's not a problem, but if > it's supposed to work, I'd begin to collect debugging information. > > So, is it supposed to work on a 9-stable as of today? > > Best regards > Riggs > ___ > 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Is ATH_ENABLE_11N supposed to work on 9-stable?
Hi, from the mailing lists I couldn't figure out whether 11n is supposed to work on stable since the existing mail threads seem to focus on current exclusively. And since the option exists in the stable kernel code as well, albeit neither in GENERIC nor in NOTES, I thought I could give it a try anyway. I had some partial success. Test in station mode, WPA2 associated properly, light traffic (browsing the web) seems to work okay as well. However as soon as I try to really push some data through it, e.g. rsync large files, the card drops all network traffic until I disassociate and re-associate with the access point again (e.g. netif restart). If 11N is just not ready in -stable yet, it's not a problem, but if it's supposed to work, I'd begin to collect debugging information. So, is it supposed to work on a 9-stable as of today? Best regards Riggs ___ 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: (9.2) panic under disk load (gam_server / knlist_remove_kq)
Le Sun, 14 Jul 2013 11:59:53 +0200, Patrick Lamaiziere a écrit : Hello, > 9.2 PRERELEASE (today) / amd64 > > Hello, > > I'm seeing a panic while trying to build a poudriere repository. > > As far I can see it always happens when gam_server is started (ie > xfce is running) and under disk load (poudriere bulk build) : > (That is something new, the box was pretty stable) > > the complete crash dump (core.0.txt) is here: > http://user.lamaiziere.net/patrick/panic_gam_server.txt With WITNESS and ASSERTION on, I see a warning that looks related : Jul 14 16:23:29 roxette kernel: WARNING: destroying knlist w/ knotes on it! and the box panics just after this. Also there are too LOR just before the panic, I don't know it there are related or not : Jul 14 16:23:29 roxette kernel: lock order reversal: Jul 14 16:23:29 roxette kernel: 1st 0xfe0013335878 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:1240 Jul 14 16:23:29 roxette kernel: 2nd 0xfe00495a5488 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2335 Jul 14 16:23:29 roxette kernel: KDB: stack backtrace: Jul 14 16:23:29 roxette kernel: #0 0x8094bc36 at kdb_backtrace+0x66 Jul 14 16:23:29 roxette kernel: #1 0x809603be at _witness_debugger+0x2e Jul 14 16:23:29 roxette kernel: #2 0x80961a95 at witness_checkorder+0x865 Jul 14 16:23:29 roxette kernel: #3 0x808f8e21 at __lockmgr_args+0x1161 Jul 14 16:23:29 roxette kernel: #4 0x8099f739 at vop_stdlock+0x39 Jul 14 16:23:29 roxette kernel: #5 0x80d93593 at VOP_LOCK1_APV+0xe3 Jul 14 16:23:29 roxette kernel: #6 0x809c0727 at _vn_lock+0x47 Jul 14 16:23:29 roxette kernel: #7 0x809b42d8 at vputx+0x328 Jul 14 16:23:29 roxette kernel: #8 0x809a88d4 at dounmount+0x294 Jul 14 16:23:29 roxette kernel: #9 0x809a914e at sys_unmount+0x3ce Jul 14 16:23:29 roxette kernel: #10 0x80cec439 at amd64_syscall+0x2f9 Jul 14 16:23:29 roxette kernel: #11 0x80cd6d57 at Xfast_syscall+0xf7 Jul 14 16:23:29 roxette kernel: lock order reversal: Jul 14 16:23:29 roxette kernel: 1st 0xfe006e1eac68 ufs (ufs) @ /usr/src/sys/modules/nullfs/../../fs/nullfs/null_vnops.c:620 Jul 14 16:23:29 roxette kernel: 2nd 0x813ebda0 allproc (allproc) @ /usr/src/sys/kern/kern_descrip.c:2822 Jul 14 16:23:29 roxette kernel: KDB: stack backtrace: Jul 14 16:23:29 roxette kernel: #0 0x8094bc36 at kdb_backtrace+0x66 Jul 14 16:23:29 roxette kernel: #1 0x809603be at _witness_debugger+0x2e Jul 14 16:23:29 roxette kernel: #2 0x80961a95 at witness_checkorder+0x865 Jul 14 16:23:29 roxette kernel: #3 0x8091b1fa at _sx_slock+0x5a Jul 14 16:23:29 roxette kernel: #4 0x808d30ff at mountcheckdirs+0x3f Jul 14 16:23:29 roxette kernel: #5 0x809a891f at dounmount+0x2df Jul 14 16:23:29 roxette kernel: #6 0x809a914e at sys_unmount+0x3ce Jul 14 16:23:29 roxette kernel: #7 0x80cec439 at amd64_syscall+0x2f9 Jul 14 16:23:29 roxette kernel: #8 0x80cd6d57 at Xfast_syscall+0xf7 Jul 14 16:23:29 roxette kernel: WARNING: destroying knlist w/ knotes on it! Thanks, regards ___ 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"
(9.2) panic under disk load (gam_server / knlist_remove_kq)
9.2 PRERELEASE (today) / amd64 Hello, I'm seeing a panic while trying to build a poudriere repository. As far I can see it always happens when gam_server is started (ie xfce is running) and under disk load (poudriere bulk build) : (That is something new, the box was pretty stable) the complete crash dump (core.0.txt) is here: http://user.lamaiziere.net/patrick/panic_gam_server.txt Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 02 fault virtual address = 0x58 fault code = supervisor read data, page not present Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 02 fault virtual address = 0x58 fault code = supervisor read data, page not present instruction pointer = 0x20:0x808f1bf1 stack pointer = 0x28:0xff8108e12a40 frame pointer = 0x28:0xff8108e12a70 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 23557 (gam_server) trap number = 12 panic: page fault cpuid = 1 ... #0 doadump (textdump=) at pcpu.h:234 234 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:234 #1 0x8092e4d6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 #2 0x8092e9d7 in panic (fmt=0x1 ) at /usr/src/sys/kern/kern_shutdown.c:637 #3 0x80d13030 in trap_fatal (frame=0xc, eva=) at /usr/src/sys/amd64/amd64/trap.c:879 #4 0x80d13391 in trap_pfault (frame=0xff8108e12990, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:795 #5 0x80d13944 in trap (frame=0xff8108e12990) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0x80cfcc73 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0x808f1bf1 in knlist_remove_kq (knl=0x30, kn=0xfe003b70b280, knlislocked=0, kqislocked=0) at /usr/src/sys/kern/kern_event.c:1847 #8 0x808f4a5b in knote_fdclose (td=0xfe0009a34490, fd=9924) at /usr/src/sys/kern/kern_event.c:2065 #9 0x808ea573 in kern_close (td=0xfe0009a34490, fd=9924) at /usr/src/sys/kern/kern_descrip.c:1250 #10 0x80d127da in amd64_syscall (td=0xfe0009a34490, traced=0) at subr_syscall.c:135 #11 0x80cfcf57 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:391 #12 0x0008019e9a9c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Thanks, regards ___ 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"
