warning: filename ends with '.', which is not allowed on Windows: 'tools/test/sort/bigtest/q-1.024.003.'
When I am using mercurial to initialize a freebsd repository, it prints "warning: filename ends with '.', which is not allowed on Windows: 'tools/test/sort/bigtest/q-1.024.003.' it seems filename ended with a dot is illegal on Windows, if someone wants to check out freebsd source code on Windows, it will be a problem. Regards, David Xu ___ 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: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
>From b...@0x20.net Thu Mar 6 22:02:56 2014 > >On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote: >> In my initial PR (sparc64 r261798), >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 >> >> I said that rsync was triggering this panic. >> While true, I now see that there's more to it. >> I disabled the rsync, and the cron jobs. >> Still I get exactly the same panic every >> night at 03:02: >> >> # grep Dumptime /var/crash/* >> /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 >> /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 >> /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 >> /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 >> /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 >> /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 >> /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 >> /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 >> # >> >> This is likely triggered by one of >> the daily periodic scipts, >> after about 1 min from start: >> >> # grep daily /etc/crontab >> # Perform daily/weekly/monthly maintenance. >> 1 3 * * * rootperiodic daily >> # >> >> but which one? > >Some time ago I had a similar problem with 8.x. Setting > >vm.kmem_size="512M" >vm.kmem_size_max="512M" > >in loader.conf helped. It's just a wild guess but might help. >-- >Bjoern Engels Was it also on sparc64? How did you find this out? I mean what lead you to this discovery? Thanks Anton ___ 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: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 6, 2014, at 11:28, Lowell Gilbert wrote: > Glen Barber writes: > > > On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: > >> >Can you go into /etc/periodic/daily and execute those scripts one by > >> >one? You should be able to narrow down which one is the culprit. > >> > >> unfortunately I cannot reproduce the panic > >> this way. What I did was: > >> > >> # cd /etc/periodic/daily > >> # for file in `ls` > >> do > >> echo $file > >> ./$file > >> done > >> > >> I run it twice, I could see all scripts > >> executing one after another, > >> but no panic. > >> Perhaps something else is happening at > >> the same time as daily scripts? > >> But I cannot find what. > >> > > > > It can also be one of the scripts in /etc/periodic/security. > > > > Can you retry your test in that directory, as well? > > "periodic daily" would be a slightly better test... > That won't help him narrow down the exact periodic script causing it, which is what he's trying to do. ___ 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: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
Glen Barber writes: > On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: >> >Can you go into /etc/periodic/daily and execute those scripts one by >> >one? You should be able to narrow down which one is the culprit. >> >> unfortunately I cannot reproduce the panic >> this way. What I did was: >> >> # cd /etc/periodic/daily >> # for file in `ls` >> do >> echo $file >> ./$file >> done >> >> I run it twice, I could see all scripts >> executing one after another, >> but no panic. >> Perhaps something else is happening at >> the same time as daily scripts? >> But I cannot find what. >> > > It can also be one of the scripts in /etc/periodic/security. > > Can you retry your test in that directory, as well? "periodic daily" would be a slightly better test... ___ 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: current -r262780 explodes on wlan up
On Thu, Mar 06, 2014 at 09:12:36AM +0100, O. Hartmann wrote: O> > Obviously not. I patched the kernel sources of a box in question and O> > the kernel has now r262821. The panic is gone, but there is nonetwork O> > although the interface is up, the firewall is up (IPWF) and even O> > netstat -rn shows the correct route. But the system is stuck with not O> > outbound network activities. Login as root takes 1 minute! Starting O> > services like ntp, slpad (OpenLDAP) or cups at boot phase blocks the O> > box for minutes so the booting takes roughly 10 minutes, until I can O> > try login to a network-dead machine. O> > O> > What is missing here? O> O> It seems, in my case, that no connection can be made to the DNS server. So, is only UDP affected? -- Totus tuus, Glebius. ___ 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: kgdb on CURRENT?
On 6 Mar 2014, at 16:53, Dimitry Andric wrote: > Now on a side note, it would be very nice if our kernel debugging > extensions were ported to the ports version of gdb, which is > non-ancient... :-) I believe that emaste has an lldb-based kgdb replacement on his todo list, although not yet quite at the top... David ___ 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: kgdb on CURRENT?
On 06 Mar 2014, at 17:33, Lev Serebryakov wrote: > CURRENT r262833, kernel from custom config (with symbols ad debugging > info), crash. > > savecore says "Unable to find matching kernel" > > kgdb /var/crash/vmcore.1 /boot/kerne/kernel says: > > Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in > module /boot/kernel/kernel.symbols] > > Is it local problem or kgdb is broken with latest clang import? No, clang 3.4 just defaults to DWARF4 format, which kgdb does not grok. Please put the following in your custom kernel configuration, similar to GENERIC: makeoptions DEBUG=-gdwarf-2 # Build kernel with gdb(1) debug symbols Now on a side note, it would be very nice if our kernel debugging extensions were ported to the ports version of gdb, which is non-ancient... :-) -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
kgdb on CURRENT?
Hello, Freebsd-current. CURRENT r262833, kernel from custom config (with symbols ad debugging info), crash. savecore says "Unable to find matching kernel" kgdb /var/crash/vmcore.1 /boot/kerne/kernel says: Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /boot/kernel/kernel.symbols] Is it local problem or kgdb is broken with latest clang import? -- // Black Lion AKA Lev Serebryakov ___ 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: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 06, 2014 at 08:07:14AM -0800, Anton Shterenlikht wrote: > >>From g...@freebsd.org Thu Mar 6 15:58:51 2014 > > > >On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: > >> >Can you go into /etc/periodic/daily and execute those scripts one by > >> >one? You should be able to narrow down which one is the culprit. > >>=20 > >> unfortunately I cannot reproduce the panic > >> this way. What I did was: > >>=20 > >> # cd /etc/periodic/daily > >> # for file in `ls` > >> do > >> echo $file > >> ./$file > >> done > >>=20 > >> I run it twice, I could see all scripts > >> executing one after another, > >> but no panic. > >> Perhaps something else is happening at > >> the same time as daily scripts? > >> But I cannot find what. > >>=20 > > > >It can also be one of the scripts in /etc/periodic/security. > > > >Can you retry your test in that directory, as well? > > > >Glen > > # pwd > /etc/periodic/security > # for file in `ls` > do > echo $file > ./$file > done > 100.chksetuid > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 110.neggrpperm > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 200.chkmounts > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 300.chkuid0 > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 400.passwdless > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 410.logincheck > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 460.chkportsum > > Checking for ports with mismatched checksums: > 500.ipfwdenied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 510.ipfdenied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 520.pfdenied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 550.ipfwlimit > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 610.ipf6denied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 700.kernelmsg > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 800.loginfail > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 900.tcpwrap > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > security.functions > # > > Perhaps these scripts cannot be simply > executed from the command line? > Sigh. It looks like someone "fixed" something... I'm certain this used to work when run directly. Glen pgpZuQTNUAyFB.pgp Description: PGP signature
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
>From g...@freebsd.org Thu Mar 6 15:58:51 2014 > >On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: >> >Can you go into /etc/periodic/daily and execute those scripts one by >> >one? You should be able to narrow down which one is the culprit. >>=20 >> unfortunately I cannot reproduce the panic >> this way. What I did was: >>=20 >> # cd /etc/periodic/daily >> # for file in `ls` >> do >> echo $file >> ./$file >> done >>=20 >> I run it twice, I could see all scripts >> executing one after another, >> but no panic. >> Perhaps something else is happening at >> the same time as daily scripts? >> But I cannot find what. >>=20 > >It can also be one of the scripts in /etc/periodic/security. > >Can you retry your test in that directory, as well? > >Glen # pwd /etc/periodic/security # for file in `ls` do echo $file ./$file done 100.chksetuid ASSERTION FAILED: Unexpected value for $PERIODIC: '' 110.neggrpperm ASSERTION FAILED: Unexpected value for $PERIODIC: '' 200.chkmounts ASSERTION FAILED: Unexpected value for $PERIODIC: '' 300.chkuid0 ASSERTION FAILED: Unexpected value for $PERIODIC: '' 400.passwdless ASSERTION FAILED: Unexpected value for $PERIODIC: '' 410.logincheck ASSERTION FAILED: Unexpected value for $PERIODIC: '' 460.chkportsum Checking for ports with mismatched checksums: 500.ipfwdenied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 510.ipfdenied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 520.pfdenied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 550.ipfwlimit ASSERTION FAILED: Unexpected value for $PERIODIC: '' 610.ipf6denied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 700.kernelmsg ASSERTION FAILED: Unexpected value for $PERIODIC: '' 800.loginfail ASSERTION FAILED: Unexpected value for $PERIODIC: '' 900.tcpwrap ASSERTION FAILED: Unexpected value for $PERIODIC: '' security.functions # Perhaps these scripts cannot be simply executed from the command line? Thanks Anton ___ 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: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: > >Can you go into /etc/periodic/daily and execute those scripts one by > >one? You should be able to narrow down which one is the culprit. > > unfortunately I cannot reproduce the panic > this way. What I did was: > > # cd /etc/periodic/daily > # for file in `ls` > do > echo $file > ./$file > done > > I run it twice, I could see all scripts > executing one after another, > but no panic. > Perhaps something else is happening at > the same time as daily scripts? > But I cannot find what. > It can also be one of the scripts in /etc/periodic/security. Can you retry your test in that directory, as well? Glen pgptKuJTtZEyT.pgp Description: PGP signature
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
>From: Mark Felder > >On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote: >> In my initial PR (sparc64 r261798), >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 >> >> I said that rsync was triggering this panic. >> While true, I now see that there's more to it. >> I disabled the rsync, and the cron jobs. >> Still I get exactly the same panic every >> night at 03:02: >> >> # grep Dumptime /var/crash/* >> /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 >> /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 >> /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 >> /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 >> /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 >> /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 >> /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 >> /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 >> # >> >> This is likely triggered by one of >> the daily periodic scipts, >> after about 1 min from start: >> >> # grep daily /etc/crontab >> # Perform daily/weekly/monthly maintenance. >> 1 3 * * * rootperiodic daily >> # >> >> but which one? >> > >Can you go into /etc/periodic/daily and execute those scripts one by >one? You should be able to narrow down which one is the culprit. unfortunately I cannot reproduce the panic this way. What I did was: # cd /etc/periodic/daily # for file in `ls` do echo $file ./$file done I run it twice, I could see all scripts executing one after another, but no panic. Perhaps something else is happening at the same time as daily scripts? But I cannot find what. Thanks Anton ___ 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: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote: > In my initial PR (sparc64 r261798), > > http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 > > I said that rsync was triggering this panic. > While true, I now see that there's more to it. > I disabled the rsync, and the cron jobs. > Still I get exactly the same panic every > night at 03:02: > > # grep Dumptime /var/crash/* > /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 > /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 > /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 > /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 > /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 > /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 > /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 > /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 > # > > This is likely triggered by one of > the daily periodic scipts, > after about 1 min from start: > > # grep daily /etc/crontab > # Perform daily/weekly/monthly maintenance. > 1 3 * * * rootperiodic daily > # > > but which one? > Can you go into /etc/periodic/daily and execute those scripts one by one? You should be able to narrow down which one is the culprit. ___ 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: firebox build fails post clang-3.4 merge
> > Does this mean the bug is fixed in 11-current? > Yes, the bug is fixed in 11-CURRENT, as of Subversion revision r262809. > > MFC? Is that to 10-STABLE? Your message is less than clear. > In FreeBSD, fixes are first applied to head (a.k.a -CURRENT), then > after a certain period they are merged to one more -STABLE branches, > depending on the type of fix. This procedure is traditionally called > a Merge From Current, MFC. > In this particular case, I will merge the fix to both 10-STABLE and > 9-STABLE. Older branches do not have clang, so merging the fix to > them makes no sense. > > I figure if firefox build fails, the bug would affect some other ports as > > well. > Don Lewis already mentioned the libxul port, and in general, any port > based on certain parts of the Mozilla source tree could be affected. > -Dimitry Thanks for response, but I went to FreeBSD website, got to mailing-list archives, in this case, svn-src-head. This made me feel safe that the bug was fixed, and I can rebuild 11-head system. But my last update might have been before the now-squashed bug was introduced. Tom ___ 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: current -r262780 explodes on wlan up
In message <1611.1394047...@critter.freebsd.dk>, Poul-Henning Kamp writes: > >Just tried a current kernel -r 262780 on my laptop. > >When wlan0 comes up (if_iwn) it explodes with something about witness >and rtentry.c, but it clears the screen before I can get a photo... -r262832 works. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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"
reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
In my initial PR (sparc64 r261798), http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 I said that rsync was triggering this panic. While true, I now see that there's more to it. I disabled the rsync, and the cron jobs. Still I get exactly the same panic every night at 03:02: # grep Dumptime /var/crash/* /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 # This is likely triggered by one of the daily periodic scipts, after about 1 min from start: # grep daily /etc/crontab # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily # but which one? Please help Thanks Anton ___ 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: mounting ntfs partition from /etc/fstab
Am 06.03.2014 08:35, schrieb M&S - Krasznai András: > Hi > > I am using freebsd 10 64bit on an IBM T510. > > I can not mount ntfs partition from /etc/fstab with the normal method, thatis > specifying > > /dev/ada0s2 /windows/C ntfs-3g ro 0 > 0 For me it works with /dev/ada0s2 /windows/C ntfsro,mountprog=/usr/local/bin/ntfs-3g 0 0 HTH, Rainer > > in /etc/fstab > > the mount -a command gives me an error message: > > /dev/ada0s2:Operation not supported by the device > > > but I can mount the same partition from the command line: > > ntfs-3g -o ro /dev/ada0s2 /windows/C > > works. > > > What is the cause of this problem? > > Krasznai András > rendszermérnök > M&S Informatikai Zrt. > 1136 Budapest, Pannónia u. 17/A. > Telefon: +36 1 703-2923 > Mobil:+36 30 703-2923 ___ 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: current -r262780 explodes on wlan up
On Thu, 6 Mar 2014 08:43:07 +0100 "O. Hartmann" wrote: > On Thu, 6 Mar 2014 08:37:59 +0300 > "Sergey V. Dyatko" wrote: > > > В Thu, 6 Mar 2014 12:47:07 +0800 > > 乔楚 пишет: > > > > > I have the same panic. > > > Panic at net use. > > > ping , svn, etc... > > > > It is fixed on r262806 > > > > > Obviously not. I patched the kernel sources of a box in question and > the kernel has now r262821. The panic is gone, but there is nonetwork > although the interface is up, the firewall is up (IPWF) and even > netstat -rn shows the correct route. But the system is stuck with not > outbound network activities. Login as root takes 1 minute! Starting > services like ntp, slpad (OpenLDAP) or cups at boot phase blocks the > box for minutes so the booting takes roughly 10 minutes, until I can > try login to a network-dead machine. > > What is missing here? It seems, in my case, that no connection can be made to the DNS server. signature.asc Description: PGP signature
