Re: NFSv4 console messages (locks lost etc.)
Hi, On Jun 29, 2013, at 2:45, Rick Macklem wrote: > Btw, a NFSv4 mounted root fs will not work correctly, because the client > name is generated from the host uuid, which isn't set when the root fs > is mounted. I'm not sure what the client would use as its client name, > but this will definitely break things badly if multiple clients use the > same name. (And this might explain the lease expiry problem.) ah, now that explains a lot. Since these are diskless clients, I had set hostid_enable="NO" in order to turn off the "/etc/rc: WARNING: could not store hostuuid in /etc/hostid" warning. Turning this back on seems to have fixed the issue. (It might make sense to have the NFSv4 code throw a warning when the hostid isn't set, if it depends on it?) Thanks, Lars ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r248583 Kernel panic: negative refcount 0xfffffe0031b59168
On 1/07/2013 3:26 PM, Gleb Kurtsou wrote: > On (30/06/2013 13:18), Mateusz Guzik wrote: >> On Sun, Jun 30, 2013 at 05:21:42PM +1000, Kubilay Kocak wrote: >>> I'm seeing what I believe is related panic, reliably being generated by >>> the Python regression test suite on a newly created FreeBSD 10-CURRENT >>> buildbot. >>> >>> Symptoms first seen in an freebsd.org FTP snapshot dated "Thu May 30 >>> 20:01:46 UTC 2013" and also reproducible on a freshly updated r252400 >>> >>> It is additionally reproducible after checking out pure upstream python >>> sources, using the following steps: >>> >>> hg clone http://hg.python.org/cpython >>> cd cpython && configure && make buildbottest >>> >>> An interesting possible correlation is that it seems to drop out >>> during/around "test_socket" >>> >> >> Turns out the bug is quite funny ;) > > Patch fixes chrome for me. > > Thanks! > >> +1 Python regression test no longer cause a panic after applying this. Fantastic work Mateusz, thank you. -- Kubilay Kocak ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Proposal: multi-instance and self-contained rc.d script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiroki Sato ha scritto: > 1. Multi-instance support > > In the implementation, load_rc_config() reads variables for all > instances and run_rc_command() runs each instance in order. When > doing "rc.d/foo stop", run_rc_command() stops the instances in > reverse order. I haven't looked at the implementation, but a useful feature that's usually missing is these multi-instance implementations and that is available in the multi-rc.d scripts scenario (take tomcat7 rc script as an example) is the ability to start/stop a single instance. Not always the instances are related each other, sometime they serve completely different purposes/applications and would be very useful to allow starting/stopping them independently. If we can get the best from the two implementations it'll be a win-win solution. > 2. Self-contained rc.d script I like the idea of defaults inside the scripts, but I like also a file that lists all available knobs with default values. If it can be automatically generated from the scripts for human reading purpose only, I'll appreciate it. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlHRXDUACgkQgRXp2M5fVU2C5QCfbRJAmtDUwJVid45FyWU1TSgr SF4An26x5n4nq7qI12C57TdvaB9hFjuq =IErn -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Zoneminder build failure
On Sun, 30 Jun 2013 16:19:48 -0500, Saul A. Peebsen wrote: Running -CURRENT, I'm getting this: c++ -O2 -pipe -march=core2 -fno-strict-aliasing -L/usr/local/lib -L/usr/local/lib/mysql -lpthread -o zmc zmc.o zm_box.o zm_buffer.o zm_camera.o zm_comms.o zm_config.o zm_coord.o zm.o zm_db.o zm_logger.o zm_event.o zm_exception.o zm_file_camera.o zm_ffmpeg_camera.o zm_image.o zm_jpeg.o zm_local_camera.o zm_monitor.o zm_ffmpeg.o zm_mpeg.o zm_poly.o zm_regexp.o zm_remote_camera.o zm_remote_camera_http.o zm_remote_camera_rtsp.o zm_rtp.o zm_rtp_ctrl.o zm_rtp_data.o zm_rtp_source.o zm_rtsp.o zm_sdp.o zm_signal.o zm_stream.o zm_thread.o zm_time.o zm_timer.o zm_user.o zm_utils.o zm_zone.o -lz -lbz2 -lswscale -lavdevice -lavformat -lavcodec -lavutil -lz -lpcre -lcrypto -lc -lpthread -ljpeg -lmysqlclient zm_timer.o: In function `Timer::TimerThread::run()': zm_timer.cpp:(.text+0x428): undefined reference to `ThreadData::setValue(bool)' c++: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Is there a fix for it? I haven't had a chance to look at that port or build it recently, but is it being built by CLANG on current? If so, is it fixed if you tell it to build with GCC? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: Unrecoverable machine check exception
Pretty sure the cause of this was "User error: CPU too hot". Please don't waste your time on it. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
too many warnigns for variable 'cons_next_next'
Hi,
could somebody help me, please, with too many following warnings:
sys/buf_ring.h:189:33: warning: variable 'cons_next_next' set but not used
As the warning is produced by header which is included a lot, the important
warnings are visible poorly among them. I think that buf_ring_dequeue_sc()
in sys/buf_ring.h could be change to suppress the warning this way:
static __inline void *
buf_ring_dequeue_sc(struct buf_ring *br)
{
- uint32_t cons_head, cons_next, cons_next_next;
+ uint32_t cons_head, cons_next, cons_next_next __unused;
uint32_t prod_tail;
void *buf;
cons_head = br->br_cons_head;
prod_tail = br->br_prod_tail;
+ if (cons_head == prod_tail)
+ return (NULL);
cons_next = (cons_head + 1) & br->br_cons_mask;
- cons_next_next = (cons_head + 2) & br->br_cons_mask;
- if (cons_head == prod_tail)
- return (NULL);
#ifdef PREFETCH_DEFINED
+ cons_next_next = (cons_head + 2) & br->br_cons_mask;
if (cons_next != prod_tail) {
prefetch(br->br_ring[cons_next]);
if (cons_next_next != prod_tail)
prefetch(br->br_ring[cons_next_next]);
}
#endif
Thanks for any respond,
Svata
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: too many warnigns for variable 'cons_next_next'
On 1 July 2013 17:11, Svatopluk Kraus wrote:
> Hi,
>
> could somebody help me, please, with too many following warnings:
> sys/buf_ring.h:189:33: warning: variable 'cons_next_next' set but not used
>
> As the warning is produced by header which is included a lot, the important
> warnings are visible poorly among them. I think that buf_ring_dequeue_sc()
> in sys/buf_ring.h could be change to suppress the warning this way:
> static __inline void *
> buf_ring_dequeue_sc(struct buf_ring *br)
> {
> - uint32_t cons_head, cons_next, cons_next_next;
> + uint32_t cons_head, cons_next, cons_next_next __unused;
> uint32_t prod_tail;
> void *buf;
>
> cons_head = br->br_cons_head;
> prod_tail = br->br_prod_tail;
>
> + if (cons_head == prod_tail)
> + return (NULL);
>
> cons_next = (cons_head + 1) & br->br_cons_mask;
> - cons_next_next = (cons_head + 2) & br->br_cons_mask;
>
> - if (cons_head == prod_tail)
> - return (NULL);
> #ifdef PREFETCH_DEFINED
> + cons_next_next = (cons_head + 2) & br->br_cons_mask;
> if (cons_next != prod_tail) {
> prefetch(br->br_ring[cons_next]);
> if (cons_next_next != prod_tail)
> prefetch(br->br_ring[cons_next_next]);
> }
> #endif
>
Why not put its declaration under #ifdef as well? YMMV.
--
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: too many warnigns for variable 'cons_next_next'
On Mon, Jul 1, 2013 at 3:40 PM, Sergey Kandaurov wrote:
> On 1 July 2013 17:11, Svatopluk Kraus wrote:
> > Hi,
> >
> > could somebody help me, please, with too many following warnings:
> > sys/buf_ring.h:189:33: warning: variable 'cons_next_next' set but not
> used
> >
> > As the warning is produced by header which is included a lot, the
> important
> > warnings are visible poorly among them. I think that
> buf_ring_dequeue_sc()
> > in sys/buf_ring.h could be change to suppress the warning this way:
> > static __inline void *
> > buf_ring_dequeue_sc(struct buf_ring *br)
> > {
> > - uint32_t cons_head, cons_next, cons_next_next;
> > + uint32_t cons_head, cons_next, cons_next_next __unused;
> > uint32_t prod_tail;
> > void *buf;
> >
> > cons_head = br->br_cons_head;
> > prod_tail = br->br_prod_tail;
> >
> > + if (cons_head == prod_tail)
> > + return (NULL);
> >
> > cons_next = (cons_head + 1) & br->br_cons_mask;
> > - cons_next_next = (cons_head + 2) & br->br_cons_mask;
> >
> > - if (cons_head == prod_tail)
> > - return (NULL);
> > #ifdef PREFETCH_DEFINED
> > + cons_next_next = (cons_head + 2) & br->br_cons_mask;
> > if (cons_next != prod_tail) {
> > prefetch(br->br_ring[cons_next]);
> > if (cons_next_next != prod_tail)
> > prefetch(br->br_ring[cons_next_next]);
> > }
> > #endif
> >
>
> Why not put its declaration under #ifdef as well? YMMV.
>
> --
> wbr,
> pluknet
>
It's possible too. But, why not to do some optimalization at the same time?
Svata
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: NFSv4 console messages (locks lost etc.)
Lars Eggert wrote: > Hi, > > On Jun 29, 2013, at 2:45, Rick Macklem wrote: > > Btw, a NFSv4 mounted root fs will not work correctly, because the > > client > > name is generated from the host uuid, which isn't set when the root > > fs > > is mounted. I'm not sure what the client would use as its client > > name, > > but this will definitely break things badly if multiple clients use > > the > > same name. (And this might explain the lease expiry problem.) > > ah, now that explains a lot. Since these are diskless clients, I had > set hostid_enable="NO" in order to turn off the "/etc/rc: WARNING: > could not store hostuuid in /etc/hostid" warning. > > Turning this back on seems to have fixed the issue. > > (It might make sense to have the NFSv4 code throw a warning when the > hostid isn't set, if it depends on it?) > Yes, good suggestion. I wasn't aware there was a "hostid_enable=NO" option. Good to hear it is resolved, rick > Thanks, > Lars > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r248583 Kernel panic: negative refcount 0xfffffe0031b59168
On Sun, Jun 30, 2013 at 01:18:36PM +0200, Mateusz Guzik wrote:
> On Sun, Jun 30, 2013 at 05:21:42PM +1000, Kubilay Kocak wrote:
> > I'm seeing what I believe is related panic, reliably being generated by
> > the Python regression test suite on a newly created FreeBSD 10-CURRENT
> > buildbot.
> >
> > Symptoms first seen in an freebsd.org FTP snapshot dated "Thu May 30
> > 20:01:46 UTC 2013" and also reproducible on a freshly updated r252400
> >
> > It is additionally reproducible after checking out pure upstream python
> > sources, using the following steps:
> >
> > hg clone http://hg.python.org/cpython
> > cd cpython && configure && make buildbottest
> >
> > An interesting possible correlation is that it seems to drop out
> > during/around "test_socket"
> >
>
> Turns out the bug is quite funny ;)
>
> Try this:
> diff --git a/sys/kern/uipc_usrreq.c b/sys/kern/uipc_usrreq.c
> index 5d8e814..7a4db04 100644
> --- a/sys/kern/uipc_usrreq.c
> +++ b/sys/kern/uipc_usrreq.c
> @@ -1764,8 +1764,8 @@ unp_externalize(struct mbuf *control, struct mbuf
> **controlp, int flags)
> }
> for (i = 0; i < newfds; i++, fdp++) {
> fde = &fdesc->fd_ofiles[*fdp];
> - fde->fde_file = fdep[0]->fde_file;
> - filecaps_move(&fdep[0]->fde_caps,
> + fde->fde_file = fdep[i]->fde_file;
> + filecaps_move(&fdep[i]->fde_caps,
> &fde->fde_caps);
> if ((flags & MSG_CMSG_CLOEXEC) != 0)
> fde->fde_flags |= UF_EXCLOSE;
Thanks for tracking it down before I had time to get to it!
The change looks good.
--
Pawel Jakub Dawidek http://www.wheelsystems.com
FreeBSD committer http://www.FreeBSD.org
Am I Evil? Yes, I Am! http://mobter.com
pgpHVKRcu5rHH.pgp
Description: PGP signature
SVN mirroring question
So I need to make a branch of a freebsd branch to do some work related changes. is it feasible to have our own svn repo and mirror a single branch into it that we can base out branch off? Ialready have a full mirror.. so is it possible to keep one branch on the private repo synced up with the same branch on the mirror? We actually use P4 so the same question for P4, except that I already have some answers for that ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Zoneminder build failure
On Mon, 01 Jul 2013 06:33:51 -0500 "Mark Felder" wrote: > On Sun, 30 Jun 2013 16:19:48 -0500, Saul A. Peebsen > wrote: > > > Running -CURRENT, I'm getting this: > > > > c++ -O2 -pipe -march=core2 -fno-strict-aliasing -L/usr/local/lib > > -L/usr/local/lib/mysql -lpthread -o zmc zmc.o zm_box.o zm_buffer.o > > zm_camera.o zm_comms.o zm_config.o zm_coord.o zm.o zm_db.o > > zm_logger.o zm_event.o zm_exception.o zm_file_camera.o > > zm_ffmpeg_camera.o zm_image.o zm_jpeg.o zm_local_camera.o > > zm_monitor.o zm_ffmpeg.o zm_mpeg.o zm_poly.o zm_regexp.o > > zm_remote_camera.o zm_remote_camera_http.o zm_remote_camera_rtsp.o > > zm_rtp.o zm_rtp_ctrl.o zm_rtp_data.o zm_rtp_source.o zm_rtsp.o > > zm_sdp.o zm_signal.o zm_stream.o zm_thread.o zm_time.o zm_timer.o > > zm_user.o zm_utils.o zm_zone.o -lz -lbz2 -lswscale -lavdevice > > -lavformat -lavcodec -lavutil -lz -lpcre -lcrypto -lc -lpthread > > -ljpeg -lmysqlclient zm_timer.o: In function > > `Timer::TimerThread::run()': zm_timer.cpp:(.text+0x428): undefined > > reference to `ThreadData::setValue(bool)' c++: error: linker > > command failed with exit code 1 (use -v to see invocation) *** > > Error code 1 > > > > Is there a fix for it? > > > > I haven't had a chance to look at that port or build it recently, but > is it being built by CLANG on current? If so, is it fixed if you tell > it to build with GCC? Thanks for reply. Will try with GCC as soon as I have some time to mess with it. -- Cheers, Saul ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Kernel build fails on ARM: Cannot fork: Cannot allocate memory
On Mon, Jun 24, 2013 at 8:23 PM, Jeff Roberson wrote: > > Would any of the arm users be interested in testing a larger patch that > changes the way the kernel allocations KVA? It also has some UMA code that > lessens kernel memory utilization. > > http://people.freebsd.org/~jeff/vmem.diff > > Any reports would be helpful. Is there any ETA on getting stack tracing > fixed? I suspect the pmap recursion encountered with Kostik's patch exist > in the current kernel. The other changes in this patch my fix that as well. I know mine is not a failed case but I still went ahead and gave your diffs a whirl. I have pretty much working beaglebone black running 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r252049M: Applied your patch and rebuilt the kernel. Everything seem sane right now. For reference: root@beaglebone:~ # cc -v FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 Target: armv6-unknown-freebsd10.0 Thread model: posix root@beaglebone:~ # df -k Filesystem 1024-blocksUsed Avail Capacity Mounted on /dev/mmcsd0s2a13129204 6459024 561984453%/ devfs1 1 0 100%/dev /dev/mmcsd0s1 2020 660135933%/boot/msdos /dev/md0 29340 24 26972 0%/tmp /dev/md1 14492 64 13272 0%/var/log /dev/md2 4508 84140 0%/var/tmp root@beaglebone:~ # root@beaglebone:~ # sysctl hw.physmem hw.physmem: 536870912 root@beaglebone:~ # dmesg | less KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2013 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 10.0-CURRENT #0: Wed Jun 26 09:51:05 UTC 2013 root@beaglebone:/usr/obj/usr/src/sys/BEAGLEBONE arm FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 WARNING: WITNESS option enabled, expect reduced performance. CPU: Cortex A8-r3 rev 2 (Cortex-A core) Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext WB disabled EABT branch prediction enabled LoUU:2 LoC:2 LoUIS:1 Cache level 1: 32KB/64B 4-way data cache WT WB Read-Alloc 32KB/64B 4-way instruction cache Read-Alloc Cache level 2: 256KB/64B 8-way unified cache WT WB Read-Alloc Write-Alloc real memory = 536870912 (512 MB) avail memory = 511758336 (488 MB) Texas Instruments AM3358 Processor, Revision ES1.1 Anything in particular you want me to test other than, it seems to be working fine for me? Thanks, Hiren > > Thanks, > Jeff > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
