Fresh current (r269328) amd64: high load average while idle, slow keyboard reaction
Hi, Previously I ran CURRENT from some time in April without any problems. Symptoms: Consistently high LA (2.6 to 8.0) with all CPUs idle. At the console, depressing and holding a key does not lead to auto-repeat. At the console, sometimes a key only appears on the terminal after another key is pressed. In xorg, key auto-repeat sorta works, but visibly slower than active xset settings, and jerky as well. Moving mouse around helps. During reboot, when the kernel prints the number of dirty buffers periodically before shutting down, it freezes and does not print the next number until I press a key. So it takes multiple presses of Shift or Control before it actually boots. Nothing suspicious according to vmstat, vmstat -i, pcmstat, top, top -SH, top -m io. What I tried, by myself and because of various advices on IRC: - replacing sc with vt disabling sc - removing atkbdc from kernel configuration - removing uart from kernel configuration - putting off for ttyu0 in /etc/ttys (it had onifconsole) No luck. Verbose dmesg can be obtained from: http://www.tobez.org/download/dmesg.verbose.2014-07-31.txt Any thought? Thanks in advance, \Anton. -- Our society can survive even a large amount of irrational regulation. -- John McCarthy ___ 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: Fresh current (r269328) amd64: high load average while idle, slow keyboard reaction
Jan, On Thu, Jul 31, 2014 at 05:56:23PM +0200, Jan Kokemüller wrote: On 31.07.2014 16:21, Anton Berezin wrote: At the console, depressing and holding a key does not lead to auto-repeat. At the console, sometimes a key only appears on the terminal after another key is pressed. Maybe this is a problem caused by a misdetected clock source? I've had this problem as well. Try to set kern.timecounter.hardware and/or kern.eventtimer.timer to other settings that are listed in kern.timecounter.choice and kern.eventtimer.choice, such as HPET which works great for me. Setting both to HPET certainly helped the LA. I cannot check the keyboard input until tomorrow, but chances are that it is indeed the fix. Thanks a bunch! \Anton. -- Our society can survive even a large amount of irrational regulation. -- John McCarthy ___ 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: sysinstall meets perl5 packages: the solution is ...?
On Tue, Jun 25, 2002 at 02:13:57PM +0200, Ollivier Robert wrote: According to Makoto Matsushita: 3) New entry 'perl5' is added to the distributions list, just like base, compat4x, crypto, XFree86, etc. Install perl5 package if perl5 package is selected. 3a) new entry perl5 added but selected by default to match what's in STABLE. POLA is respected and if some of us want to remove it, it is possible. Yes, that is surely the best solution, IMO. =Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl wrapper and PATH
On Sat, Jun 08, 2002 at 02:14:09PM -0400, Trish Lynch wrote: Anton, if you don;t get around to it this weekend, mind if I take a stab at it? No, I don't mind at all. If only we can agree who does what. :-( Cheers, \Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Head's up: NO_PERL - NO_PERL_WRAPPER
On Sun, Jun 09, 2002 at 02:39:45AM -0700, Doug Barton wrote: Per discussion with various folks, including Mark, I've moved the NO_PERL knob over to NO_PERL_WRAPPER, and documented same. Given that this is a fundamentally different thing than the old perl knobs, my opinion is that we don't need to provide compatibility, but I won't argue that point too strongly. The compatibility is a moot point either way, since there was no NO_PERL knob - it used to be called NOPERL. I'm currently working on a patch to ports/lang/perl5/files/use.perl to deal with this, and a few of the other outstanding issues. That's fine, but I am still trying to understand why do we need a wrapper at all. As was indicated (on IRC, not sure it was mentioned in the mail threads), the ability to launch /usr/bin/perl with no perl in the system is different from the inability to launch anything at all. =Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Head's up: NO_PERL - NO_PERL_WRAPPER
On Sun, Jun 09, 2002 at 04:12:37AM -0700, Doug Barton wrote: Anton Berezin wrote: The compatibility is a moot point either way, since there was no NO_PERL knob - it used to be called NOPERL. It's NOPERL in -stable, but it was NO_PERL in -current when I changed it to NO_PERL_WRAPPER. My point was that it *was* NOPERL in -current before the removal of perl. But I see you handle this case in your patch to use.perl, so no argument here. That's fine, but I am still trying to understand why do we need a wrapper at all. As was indicated (on IRC, not sure it was mentioned in the mail threads), the ability to launch /usr/bin/perl with no perl in the system is different from the inability to launch anything at all. Personally, I don't think we need a wrapper, as long as the use.perl script knows how to DTRT. My point exactly. However, given that currently we have a wrapper I thought fixing use.perl to handle it was reasonable. The keyword here is `currently'. :-) Cheers, \Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: use.perl patch for the new -current world
On Sun, Jun 09, 2002 at 04:07:43AM -0700, Doug Barton wrote: Attached is a patch that I think sufficiently updates use.perl to handle the state of the world in -current, without boning things for -stable. It also moves some duplicate code up out of the functions. Comments/suggestions welcome. Looks good. =Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl wrapper and PATH
On Sat, Jun 08, 2002 at 09:48:05AM -0400, Trish Lynch wrote: The wrapper is there so that there are no suprises to people that *expect* perl in the system. What would possibly be a good idea is that the wrapper is there, but it doesn;t actually redirect to the new perl. Then use.perl is run from the port. The case for system should be removed or some way of relinking to the wrapper instead should be provided? It sounds reasonable, but what's the point of having a wrapper at all then? The problem is that use.perl is needed on -STABLE systems, so... a different behaviour when the OS version is =5 might be needed? I don't like that but I am afraid it has to be done. I Cc:ed this to the ports maintainer just in case... If they would like I can fix use.perl to have a different behaviour on -current and thereafter, but I don;t want to step on anybody's toes. Thanks, but I think I'll try to hack something up during weekend. I am of the opinion that we don't need the wrapper and that use.perl can easily do some symlink magic to solve all outstanding issues with perl in -current. Cheers, \Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Perl script rewrites - progress (2)
Hi, On Sun, May 19, 2002 at 11:55:33AM +0200, John Hay wrote: Me too. :-( The error I see is: ### Extracting splain (with variable substitutions) ../miniperl -I../lib perlcc.PL Extracting perlcc (with variable substitutions) ../miniperl -I../lib dprofpp.PL Extracting dprofpp (with variable substitutions) Making x2p stuff make: don't know how to make built-in. Stop *** Error code 2 Stop in /usr/ports/lang/perl5/work/perl-5.6.1. *** Error code 1 Stop in /usr/ports/lang/perl5. ### ### grep built-in work/perl-5.6.1/x2p/makefile hash$(OBJ_EXT): built-in str$(OBJ_EXT): built-in util$(OBJ_EXT): built-in walk$(OBJ_EXT): built-in ### This problem should be fixed now. =Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl5 port won't build
Hi, On Sun, May 19, 2002 at 07:19:07PM -0800, Beech Rintoul wrote: I grabbed the latest ports and attempted to build p5, it errors with the following: Making x2p stuff make: don't know how to make built-in. Stop *** Error code 2 Stop in /usr/ports/lang/perl5/work/perl-5.6.1. *** Error code 1 Stop in /usr/ports/lang/perl5. Any suggestions? Yes - cvsup again. :-) Cheers, =Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Perl build breakage
On Thu, Nov 29, 2001 at 10:42:45AM -0800, Eugene M. Kim wrote: Hello, I am getting the following error in the make depend stage; could anyone shed a light? (The host system is 5-current as of around May 1.) From UPDATING (you do read UPDATING, don't you?): 20010502: Perl breakage in 20010501 was corrected at 14:18:33 PDT. 20010501: Building perl was broken at 02:25:25 PDT. Please see the old HEADS UP message, which describes the fix: http://www.freebsd.org/cgi/getmsg.cgi?fetch=192223+0+/usr/local/www/db/text/2001/freebsd-current/20010506.freebsd-current Thanks, Eugene snip snip === libperl === miniperl === perl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. snip snip Cheers, *Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Perl build breakage
On Sat, Dec 01, 2001 at 01:26:11PM -0800, Eugene M. Kim wrote: Oh, never mind. I just re-read the thread you pointed (thanks) and saw it affects the systems *installed around the breakage date*. UPDATING does not mention about this fact (it simply says `Building perl was broken'); perhaps it should be updated to mention the misfortune of the installed system and the link to the fix; Warner?). Well, that would definitely be a good idea half a year ago. Nowadays, I doubt there will be any significant number of unlucky souls having operating -current systems built between May 1st and May 2nd. You might be unique at that. ;-) Cheers, %Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: misc/15421 (was: Re: initgroups)
On Tue, Nov 20, 2001 at 03:02:39PM +0200, Ruslan Ermilov wrote: On Mon, Nov 19, 2001 at 10:28:55PM +0600, Max Khon wrote: I asked tobez (he is an originator and he took responsibility on this PR) and he said that src/ must be audited also -- he said that some initgroups() callers do not print error message because initgroups() did this previously. I'll try to do this before this weekend and I will post combined patch to audit@ While this is indeed a good thing to do, this is completely unrelated to the above mentioned problem, and should be done separately. Here's the list of src/ files that do not check the return value of initgroups(3), and may need to be fixed, but some of them explicitly ignore the result to indicate the fact they consider this error non-fatal. libexec/ftpd/ftpd.c libexec/rexecd/rexecd.c usr.bin/calendar/calendar.c usr.sbin/inetd/inetd.c There used to be *many* more problematic files. Please see http://www.freebsd.org/cgi/getmsg.cgi?fetch=801566+0+/usr/local/www/db/text/2001/freebsd-stable/20010722.freebsd-stable To my knowledge, only printjob.c was fixed, though I have not looked into every file in the list since then. But as I said in the private message, I do not feel strongly about this, and I think that the fix can be safely committed. I do not think these things are quite unrelated, though. :-) Cheers, \Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: misc/15421 (was: Re: initgroups)
On Tue, Nov 20, 2001 at 04:27:03PM +0200, Ruslan Ermilov wrote: On Tue, Nov 20, 2001 at 03:12:50PM +0100, Anton Berezin wrote: On Tue, Nov 20, 2001 at 03:02:39PM +0200, Ruslan Ermilov wrote: While this is indeed a good thing to do, this is completely unrelated to the above mentioned problem, and should be done separately. Here's the list of src/ files that do not check the return value of initgroups(3), and may need to be fixed, but some of them explicitly ignore the result to indicate the fact they consider this error non-fatal. libexec/ftpd/ftpd.c libexec/rexecd/rexecd.c usr.bin/calendar/calendar.c usr.sbin/inetd/inetd.c There used to be *many* more problematic files. Please see http://www.freebsd.org/cgi/getmsg.cgi?fetch=801566+0+/usr/local/www/db/text/2001/freebsd-stable/20010722.freebsd-stable To my knowledge, only printjob.c was fixed, though I have not looked into every file in the list since then. Yes, but I specifically left contrib/ and crypto/ files, and files that do not check the result of other calls like setgrp() etc. We do not want to omit contrib/ files, since the whole hoopla started because of the contrib/cvs/. But as I said in the private message, I do not feel strongly about this, and I think that the fix can be safely committed. I do not think these things are quite unrelated, though. :-) Not checking the return value is always BAD except when (not) done intentionally (flagged by a(void)ing the return value of a function), whether or not a function in question prints some diagnostic output on standard error; that's why I still think these problems are in fact unrelated. :-) In this case your own version of the fix should be modified from + getgrouplist(uname, agroup, groups, ngroups); + return (setgroups(ngroups, groups); to + (void) getgrouplist(uname, agroup, groups, ngroups); + return (setgroups(ngroups, groups); , to be pedantic. :-) The point I am trying to (not very strongly) make is that we at least have some indication that there is a problem with the current behavior (with the exception of the daemons with closed/redirected to /dev/null stderr). By (rightfully) fixing initgroups(), we loose even this precious little diagnostic we have. That's why initgroups() fix and the code audit are probably best done at the same time - unless we can guarantee the audit part will not be forgotten. Cheers, $Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/isa psm.c atkbdc_isa.c
On Mon, Oct 01, 2001 at 02:50:18PM +0900, Kazutaka YOKOTA wrote: Yet another turn of workaround for psm/ACPI/PnP BIOS problems currently experienced in -CURRENT. This should fix the problem that the PS/2 mouse is detected twice if the acpi module is not loaded on some systems. Can it be that this fix is responsible for PS/2 mouse being detected zero times? :-) :-( Dmesg output is in a separate message. This is most likely to be an ACPI problem. Please try disabling the acpi module (unset load_acpi at the loader prompt) and boot -v, then send me dmesg's output. Yes, it turned out to be ACPI problem - the mouse's working fine now. Sorry for bugging you. I presume you don't need a new dmesg output now? \Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/isa psm.c atkbdc_isa.c
On Tue, Sep 25, 2001 at 09:59:28AM -0700, Kazutaka YOKOTA wrote: yokota 2001/09/25 09:59:28 PDT Modified files: sys/isa psm.c atkbdc_isa.c Log: Yet another turn of workaround for psm/ACPI/PnP BIOS problems currently experienced in -CURRENT. This should fix the problem that the PS/2 mouse is detected twice if the acpi module is not loaded on some systems. Revision ChangesPath 1.24 +2 -2 src/sys/isa/atkbdc_isa.c 1.40 +84 -39src/sys/isa/psm.c Can it be that this fix is responsible for PS/2 mouse being detected zero times? :-) :-( Dmesg output is in a separate message. +Anton. -- | Anton Berezin| FreeBSD: The power to serve | | catpipe Systems ApS _ _ |_ | http://www.FreeBSD.org | | [EMAIL PROTECTED](_(_|| |[EMAIL PROTECTED] | | +45 7021 0050| Private: [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cannot print to remote printer
On Thu, Jul 12, 2001 at 08:45:55AM +0200, Joerg Wunsch wrote:
Anton Berezin [EMAIL PROTECTED] wrote:
if (fork() == 0) {
- signal(SIGCHLD, SIG_IGN);
+ signal(SIGCHLD, SIG_DFL);
This is unportable.
If you want automatic zombie reaping, better don't use the simplified
signal(3) handling, but instead spell it out as sigaction(2) using the
SA_NOCLDWAIT flag. The above won't even give you a warning on systems
that don't implement automatic zombie reaping, while with sicaction,
you'll get a compile-time error for SA_NOCLDWAIT not being defined.
Umm, I don't understand. I do not want automatic zombie reaping, I want
exactly the opposite, and my patch does just that.
Cheers,
\Anton.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: cannot print to remote printer
On Thu, Jul 12, 2001 at 10:40:12PM +0300, Giorgos Keramidas wrote: Anton Berezin [EMAIL PROTECTED] writes: Umm, I don't understand. I do not want automatic zombie reaping, I want exactly the opposite, and my patch does just that. I might be wrong in many ways, but... is it then mandatory that you `reset' SIGCHLD to SIG_DFL ? Why not leave it in it's default state, and make this patch: - signal(SIGCHLD, SIG_IGN); without adding any lines? The problem is that at this point it is not in its default state. Several screenfuls above this line, in the same function (main()), there is a line signal(SIGCHLD, reapchild); I'm in a wild rush, and I don't have the time to actually look at the code or test it. I will, soon, though... :-) =Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cannot print to remote printer
On Wed, Jul 11, 2001 at 02:55:33PM +0200, Georg-W. Koltermann wrote:
Sorry, I was offline for a while (broke my leg). I am now recovering
and slowly catching up. The laptop which had this problem won't be
back on the ethernet for another two weeks, so I won't be able to do
more testing. And maybe, since so much time has passed, I'd better
CVSup and try again.
I could reproduce your problem. The following patch appears to solve it
for me:
Index: lpd.c
===
RCS file: /home/ncvs/src/usr.sbin/lpr/lpd/lpd.c,v
retrieving revision 1.26
diff -u -r1.26 lpd.c
--- lpd.c 2001/06/25 01:45:25 1.26
+++ lpd.c 2001/07/11 19:35:11
@@ -367,7 +367,7 @@
continue;
}
if (fork() == 0) {
- signal(SIGCHLD, SIG_IGN);
+ signal(SIGCHLD, SIG_DFL);
signal(SIGHUP, SIG_IGN);
signal(SIGINT, SIG_IGN);
signal(SIGQUIT, SIG_IGN);
At 2:42 PM +0200 6/22/01, Georg-W. Koltermann wrote:
with current as of June 20 I can no longer print to a remote printer.
Syslog says filter 'f' exited (retcode=108).
I added a set -x to the filter which is a shell program, and sure
enough the last action it does is an exit 0. So the problem must
be somewhere in lpd.
=Anton.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Workaround for PS/2 mouse problems with recent -current
Commenting out hint.atkbd.0.* and hint.psm.0.* fixed the problem that others reported. Little investigation showed that the new resource_find() function in kern/subr_bus.c finds two atkbd0 and two psm0, one of each from kern_envp, and the other one from static_hints; no wildcard matches were involved. I'll leave the real solution for the more kernel-clueful here. \Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: different world breakage (Perl bootstrap, alpha)
Please see [EMAIL PROTECTED] On Tue, May 08, 2001 at 11:16:41AM -0700, Matthew Jacob wrote: === gnu/usr.bin/perl/perl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: different world breakage (Perl bootstrap, alpha)
On Tue, May 08, 2001 at 02:29:35PM -0700, Matthew Jacob wrote: And how is that piece of mail (about cvsup) pertinent? Well, there is a follow-up: [EMAIL PROTECTED] , or http://www.freebsd.org/cgi/getmsg.cgi?fetch=195431+0+/usr/local/www/db/text/2001/freebsd-current/20010506.freebsd-current Cheers, \Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -CURRENT broken in gnu/usr.bin/perl/perl
On Wed, May 02, 2001 at 08:27:36AM -0700, David Wolfskill wrote: Just glanced through cvs-all; didn't see commits more recent than my last CVSup: CVSup started from cvsup14.freebsd.org at Tue May 1 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Tue May 1 03:55:45 PDT 2001 Did you do another buildworld between these CVSup's? CVSup started from cvsup14.freebsd.org at Wed May 2 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Wed May 2 03:53:01 PDT 2001 The suspected commit is [EMAIL PROTECTED] It looks like the recent BSDPAN change has a problem - I am looking into it. The error occurred during stage 4: make dependencies: === gnu/usr.bin/perl/libperl === gnu/usr.bin/perl/perl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Hmm SelfLoader.pm was last modified: m133[3] ls -l SelfLoader.pm -rw-rw-r-- 1 david wheel 12043 Jun 25 2000 SelfLoader.pm It's at revision 1.1 Hmmm..., Cheers, +Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP! Breakage in Perl/BSDPAN
On Wed, May 02, 2001 at 11:26:49PM +0200, Mark Murray wrote: Hi Those who made a buildworld without NO_PERL=true with sources newer than Tue, 1 May 2001 02:25:25 -0700 (PDT), but older than 2001/05/02 14:18:33 PDT, must apply the following patch as root in /usr/libdata/perl/BSDPAN directory. (If you are tracking CURRENT, then CVSup and/or cvs update after this message will get you the same fix.) But for those who built world in the above timeframe, it is still necessary to apply the patch: this is one of the unfortunate cases where the state of currently installed perl modules affects the buildworld. \Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -CURRENT broken in gnu/usr.bin/perl/perl
On Wed, May 02, 2001 at 06:28:18PM +0200, Anton Berezin wrote: On Wed, May 02, 2001 at 08:27:36AM -0700, David Wolfskill wrote: It looks like the recent BSDPAN change has a problem - I am looking into it. The error occurred during stage 4: make dependencies: === gnu/usr.bin/perl/libperl === gnu/usr.bin/perl/perl Extracting config.h (with variable substitutions) Extracting cflags (with variable substitutions) Extracting writemain (with variable substitutions) Extracting myconfig (with variable substitutions) Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line syntax error at lib/SelfLoader.pm line 69, at EOF Compilation failed in require at /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm line 17. Compilation failed in require at /usr/libdata/perl/BSDPAN/Config.pm line 37. BEGIN failed--compilation aborted at /usr/libdata/perl/BSDPAN/Config.pm line 37. Compilation failed in require at /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm line 430. *** Error code 255 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 The fix has been committed. Please also see a HEADS UP message on this list. Thanks, David, for reporting this. +Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: core(5) implementation using perl(1)
On Thu, Apr 19, 2001 at 07:00:21PM +0300, Maxim Sobolev wrote: Attached script forces perl(1) to dump core, which isn't a good behaviour IMO (tested on 5-CURRENT and 4.3-RC). Why it is definitely not a good behavior for perl(1), the script is not correct anyway. You need to change " to ' to achieve the result you want. I'll try to make a shorter testcase and submit it to perl developers. Cheers, +Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: core(5) implementation using perl(1)
On Fri, Apr 20, 2001 at 04:33:48PM +0200, Anton Berezin wrote:
On Thu, Apr 19, 2001 at 07:00:21PM +0300, Maxim Sobolev wrote:
Attached script forces perl(1) to dump core, which isn't a good
behaviour IMO (tested on 5-CURRENT and 4.3-RC).
Why it is definitely not a good behavior for perl(1), the script is
not correct anyway. You need to change " to ' to achieve the result
you want.
I'll try to make a shorter testcase and submit it to perl developers.
FYI.
Here's the minimal coredump case:
$ perl -n -e 's||${}|g; s|||'
Have not tried with 5.6.1 yet.
Cheers,
=Anton.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: perl broken?
On Sat, Apr 07, 2001 at 10:41:30PM -0500, Michael Harnois wrote:
Different ports, similar problem:
/usr/bin/perl5 -I/usr/libdata/perl/5.6.0/mach -I/usr/libdata/perl/BSDPANIMAP.xs
IMAP.xsc mv IMAP.xsc IMAP.c
Arrrhgh. Thanks for the report.
Please try the following patch:
--- /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Thu Apr 5 22:21:44 2001
+++ /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Sun Apr 8 14:22:21 2001
@@ -102,6 +102,7 @@
eval "*\$name = sub {
\\\$repsub2-(
\\\$real_addr, \\\@_) };";
+ \@r;
}, \@_)
};
EOF
Cheers,
+Anton.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: perl broken?
On Sun, Apr 08, 2001 at 02:26:38PM +0200, Anton Berezin wrote:
On Sat, Apr 07, 2001 at 10:41:30PM -0500, Michael Harnois wrote:
Different ports, similar problem:
/usr/bin/perl5 -I/usr/libdata/perl/5.6.0/mach -I/usr/libdata/perl/BSDPAN
IMAP.xs IMAP.xsc mv IMAP.xsc IMAP.c
Arrrhgh. Thanks for the report.
Please try the following patch:
--- /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Thu Apr 5 22:21:44 2001
+++ /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Sun Apr 8 14:22:21 2001
@@ -102,6 +102,7 @@
eval "*\$name = sub {
\\\$repsub2-(
\\\$real_addr, \\\@_) };";
+ \@r;
}, \@_)
};
EOF
Forgot to add: you will need to make clean your port(s) to unbroke the
generated Makefile.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: building perl 5.6.0 with `-DPERL_POLLUTE'
On Wed, Mar 14, 2001 at 08:43:11PM -, Jason R. Mastaler wrote: I've noticed that lots of the perl ports are now broken since the move to perl 5.6.0. Some examples: http://bento.freebsd.org/errorlogs/5-full/p5-Crypt-IDEA-1.01.log http://bento.freebsd.org/errorlogs/5-full/p5-Devel-Peek-0.96.log With these two in particular, the problem can be fixed by compiling perl with `-DPERL_POLLUTE' to get back the missing preprocessor definitions. Would it be worth it to compile the default 5.x perl in this manner? No. It is not necessary to compile *Perl* with -DPERL_POLLUTE, it's enough to compile the module in question with -DPERL_POLLUTE. Thus, this is easily fixable for individual ports. For extensions still using the old symbols, this option can be specified via MakeMaker: perl Makefile.PL POLLUTE=1 What it says... Cheers, -Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT breaks some apps
On Sat, Jan 06, 2001 at 12:12:24AM -0500, Raymond Hicks wrote:
I have had a problem with running infobot after my recent cvsup to
current. I have heard that there is a problem with the newer perl
version.. is this a result of that? Here is error:
deepwoods# Missing braces on \N{} at ./src/Irc.pl line 131, near " $b"
Missing braces on \N{} at ./src/Irc.pl line 133, near " $b"
Missing braces on \N{} at ./src/Irc.pl line 152, within string
Compilation failed in require at ./infobot line 39.
BEGIN failed--compilation aborted at ./infobot line 42.
and here is perl -v
deepwoods# perl -v
This is perl, v5.6.0 built for i386-freebsd
(with 1 registered patch, see perl -V for more detail)
5.6.0 introduced new escape: \N{}, named chars for UTF-8. See man
charnames for details.
If you want to fix Irc.pl yourself, go there and remove unnecessary
backslashes (if one wants `N', why would one use `\N' anyway?).
HTH,
Cheers,
^Anton.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: perl vs. LOCALBASE, again
On Sun, Jul 30, 2000 at 08:45:05PM -0500, Mike Meyer wrote: Basically, the problem is that ports that install Perl modules ignore LOCALBASE for the perl modules. A little bit of investigation turns up /usr/libdata/perl/5.6.0/Config.pm, which has "/usr/local" wired through it as a prefix for nearly everything. I suspect the ideal situation would be for the Perl module installer to detect (how?) to try and sniff LOCALBASE out of /etc/make.conf if this is part of a port install. If that works, use LOCALBASE. Otherwise, use the default Config.pm values. People who want that default to be something other than /usr/local can then change those values themselves. IMHO, the easiest thing to do would be to modify the Config.pm itself. For example, it might look for, say, PERL_USE_PREFIX environment variable and change its %Config accordingly. Then the Makefiles in p5 ports will just set this variable to whatever LOCALBASE is, before invoking perl Makefile.PL. There is another problem with your idea, though. Such Perl modules will not be found by perl unless PERL5LIB points to the right place, i.e. your installed p5 ports will not work out of the box. That is pretty bad, and setting PERL5LIB globally will not help much since at least some people set it to their private directories without spelling PERL5LIB=$PERL5LIB:bla mantra. Is there someone who can *fix* this? Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
On Fri, Apr 07, 2000 at 12:57:16AM -0400, Alexander N. Kabaev wrote: I am perfectly aware of the way OpenBSD builds contrib software. I am just making a point that they have found perl 5.6.0 is stable enough to be included into their OS. It is an issue of personal relationships and politics, not the technical one. Tom Christiansen uses OpenBSD and advocates Perl to it (and other way around). Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
On Mon, Apr 03, 2000 at 07:01:10AM -0500, Thomas T. Veldhouse wrote: I would think the perl upgrade would also be done in current. I would think you would want to track this sort of thing as closely as possible - unless there is an pending release - which there isn't. Users will follow current to get the latest and greatest - bleeding edge technology. Everybody who wants to have the bleeding edge Perl on their systems is welcome to install it himself. 5.6.0 builds out of the box and passes its regression test suit just fine on 2.2.X, 3.X, 4.X, and 5.0. Help test it. Seem to me the sooner it is done, the more thoroughly tested it will be. One year ought to be long enough :) Historical evidence suggests there will be 5.6.1 *very* soon, and 5.6.2 shortly after that. Let's wait a couple of months before jumping on this vagon... :-) 5.6.0 will almost surely prove to have far too many problems to include it into FreeBSD source tree. Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Shared memory - Was: 2 Queries
On Tue, Feb 29, 2000 at 01:41:43PM -0500, Christopher Masto wrote: Personally, I have this extreme distaste for sysv shared memory. It is a very scarce resource that is not freed automatically, and seems to go completely against the unix model. Reminds me of having to free memory on the Amiga, and slowly running out of chip RAM. In any case, one major offender is imlib. Since I've recently gone Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option or things would go bad after a few minutes or hours of use. I would say that the programs you've mentioned are badly written then. It takes no more than XSync(disp,False); shmctl( shmid, IPC_RMID, 0); right after a call to XShmAttach() for a shared memory image to achieve the automatic reclamation of the memory. Shared pixmaps are different, but not that many programs should use these anyway. Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall's fdisk/disklabel broken?
On Fri, Jan 21, 2000 at 04:11:24AM +1100, james wrote: I was going to use sysinstall's disklabel to repartition/relabel one of my drives, but when i went into it in the post-installation menu it said: No disks found! BTW i'm using 4.0-CURRENT (obviously), and i cvsupp'd and make world'd about 2 days ago. I just bumped into this, half an hour ago. :-) How old is your /stand/sysinstall (it does not get updated as a make world process)? # cd /usr/src/release/sysinstall make all install Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sigisempty?
On Wed, Jan 19, 2000 at 07:03:04AM -0800, Satoshi Asami wrote: How do I test if sigset_t is empty in -current? The xview sources have this macro: #define sigisempty(s) (!(*(s))) which is ok for the old sigset_t (unsigned int) but obviously won't work for the new one since it's a struct. The very same file nfty.h already has a hack for SVR4: #ifdef SVR4 #define sigisempty(s) (!(((s)-__sigbits[0]) | ((s)-__sigbits[1]) \ | ((s)-__sigbits[2]) | ((s)-__sigbits[3]))) When I compiled xview on a -current machine I just did it the very same hacky way: #define sigisempty(s) (!(((s)-__bits[0]) | ((s)-__bits[1]) \ | ((s)-__bits[2]) | ((s)-__bits[3]))) Of course, the #if for FreeBSD and its version is necessary. Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People getting automatically unsub'ed from -arch
On Thu, Oct 14, 1999 at 06:46:15PM +0200, Ollivier Robert wrote: Someday, when you have 5 minutes free (aha!) have a look at Listar. It is a small, fast and feature-full list manager written in C with automatic bounce handling (among other things). Hmm, it sends mails itself. I doubt it can do this more effectively than postfix does. Am I wrong? Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ccd build failure
On Thu, Sep 23, 1999 at 11:46:38AM -0700, Darryl Okahata wrote:
I'd like to submit the attached perl script, which lists the status of
cvs-controlled files. In particular, it's very useful for determining
which files have been modified but not committed
With the following patch this scripts becomes even more useful (properly
handles situations when the file is missing):
--- /home/tobez/cvsinfo Thu Sep 23 21:19:53 1999
+++ cvsinfo Thu Sep 23 21:19:22 1999
@@ -69,7 +69,7 @@
$cmd = "cvs status -l";
open(IN, "$cmd 21 |") || die "$!";
while (IN) {
- if (/^File:\s+([^\s]+)\s+Status:\s+(.+)$/i){
+ if (/^File:\s+(?:no file\s+)?([^\s]+)\s+Status:\s+(.+)$/i){
$file = $1;
$status = $2;
if ($all_status || $status ne 'Up-to-date') {
Cheers,
--
Anton Berezin [EMAIL PROTECTED]
The Protein Laboratory, University of Copenhagen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
On Fri, Sep 03, 1999 at 01:04:53PM -0600, Brian Handy wrote: I was hoping for something simpler that wouldn't require me to figure out how to configure mirror-script. :-( The simplest thing I've come up with (as I wrote some days before) is $ perl -MIO -e '' I.e. *any* use of IO::File and friends fails miserably during XS bootsrap. If it is necessary, I will reinstallworld tomorrow with Aug-25 loader. Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl broken in 4.0-CURRENT ?
On Tue, Aug 31, 1999 at 02:09:00AM +0200, Pascal Hofstee wrote: I get the following errors when trying to run certain perl stuff .. like mirror: su-2.03# mirror /usr/local/lib/mirror/packages/daemonnews DynaLoader:/usr/libdata/perl/5.00503/DynaLoader.pm:188 Caught a SIGSEGV shutting down at /usr/local/bin/mirror line 3873. Yep. The easiest way to reproduce this is $ perl -MIO -e '' It dies during IO's bootstrap, but I have not investigated this further. Something in libc? Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sigpending with pthreads - bug or feature?
I don't know whether I should file a bug report on this issue.
Consider the following little program:
/* t.c */
#include stdio.h
#include signal.h
int
main( void)
{
sigset_t set;
sigpending( set);
return 0;
}
Compiling and running it:
$ cc t.c
$ ./a.out
$
And trying to do the same with threads:
$ cc -pthread t.c
/var/tmp/ccs690421.o: In function `main':
/var/tmp/ccs690421.o(.text+0x1a): undefined reference to `sigpending'
$
However,
$ nm /usr/lib/libc_r.a | grep sigpending
sigpending.o:
0040 T _thread_sys_sigpending
$
Apparently this one is not documented anywhere. Is it a missing alias
then? Or is one simply not allowed to use sigpending() with threads?
--
Anton Berezin to...@plab.ku.dk
The Protein Laboratory, University of Copenhagen
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
