On Fri, January 8, 2010 11:31, Garrett Moore wrote:
No, I haven't isolated the cause to only be uptime related. In my original
email I mentioned that as suggested by someone in the thread, it's
probably
not directly related to system uptime, but instead related to usage - the
more usage, the
On Tue, December 29, 2009 23:33, jhell wrote:
On Tue, 29 Dec 2009 17:18, oliver.pntr@ wrote:
Hi list!
Something fails, when updated the FreeBSD's svn repo to git. Since
yesterday I get this warning:
$ git svn rebase
...
M sys/boot/pc98/kgzldr/crt.s
Couldn't find revmap for
Marc G. Fournier wrote:
I checked both fsck and fsck_ffs man page, and don't see anything in
either ... is there some way I can check if a file system is actually
'clean', without running fsck?
Google Groups revealed the following:
Atanas wrote:
Matthias Andree said the following on 7/11/06 1:48 PM:
Atanas [EMAIL PROTECTED] writes:
Recent portupgrade versions no longer obey the -M command line switch,
i.e. any optional arguments to be prepended to each make command.
How to reproduce:
# portinstall -M
Please don't top-post...
User Freebsd wrote:
On Wed, 28 Jun 2006, User Freebsd wrote:
Just got this on the console of one of hte servers that has been
causing problems ...
Expensive timeout(9) function: 0xc0520e18(0xc8b223a0) 0.296959250 s
not a very informative error, and that is all that
Marc G. Fournier wrote:
On Mon, 26 Jun 2006, Max Laier wrote:
On Monday 26 June 2006 20:25, Marc G. Fournier wrote:
I think I might have found *at least* one of the problems, and that
being
the excessively high blocked states while ps isn't finding anything ...
MySQL
We just recently
On 05/26/06 04:37, Jean-Marc Zucconi wrote:
Jonathan Noack writes:
Jean-Marc Zucconi wrote:
# tar cf /dev/null X11R6.old
# archive_write_pax_header: 'x' header failed?! This can't happen.
This seems to work fine here:
[EMAIL PROTECTED]:/usr] $ uname -rm
6.1-RELEASE i386
Kris Kennaway wrote:
On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote:
I get a very easy to reproduce panic on 6.1-STABLE :
/etc/periodic/weekly/310.locate panics with
panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated
It looks like you are using a
Jean-Marc Zucconi wrote:
# tar cf /dev/null X11R6.old
# archive_write_pax_header: 'x' header failed?! This can't happen.
This seems to work fine here:
[EMAIL PROTECTED]:/usr] $ uname -rm
6.1-RELEASE i386
[EMAIL PROTECTED]:/usr] $ tar --version
bsdtar 1.02.023, libarchive 1.02.026
Copyright
by rebuilding all dependencies or
removing '-m -s'.
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
), but that's not a
huge deal.
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
yesturday? going by the ports/graphics/dri, it
hasn't been touched in over three months.
He was referring to an update of the kernel drivers:
http://lists.freebsd.org/pipermail/cvs-src/2006-May/063838.html
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
On 05/20/06 18:42, Matthew Gardiner wrote:
On Sunday 21 May 2006 06:41, Jonathan Noack wrote:
On 05/19/06 01:44, Matthew Gardiner wrote:
On Friday 19 May 2006 05:07, Ronald Klop wrote:
This commit of the drm/dri stuff yesterday on 6-STABLE rocks.
It works out of the box on my i810.
I think
Pertti Kosunen wrote:
Dominic Marks wrote:
Is the php5-pcre module really incompatible with FreeBSD 6.1? If so,
is there a workaround or a version I can roll back to? Also, it is
just me (:-)) or is the php5 port complaining about a checksum
mismatch for everyone else?
I had some problems
Kaiwai Gardiner wrote:
Hi, I am experiencing problems compiling FreeBSD 6.1 RELEASE; the
following link has the relevant information:
http://www.freebsd.org/cgi/query-pr.cgi?pr=97240
The file does exist in the src/contrib/gcc directory, but it seems that
the compiler/installer isn't picking
is an example /etc/rc.conf entry:
ifconfig_fxp0=inet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx link0
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
On 05/12/06 07:56, gareth wrote:
On Fri 2006-05-12 (07:31), Jonathan Noack wrote:
Ah, I made a mistake in my explanation. Replace INDEX-5.db with
INDEX-5. Sorry for the confusion...
make fetchindex downloads the INDEX-x file (where 'x' is the major
release number of the version of FreeBSD
On 05/12/06 03:20, gareth wrote:
On Wed 2006-05-10 (11:29), Jonathan Noack wrote:
You are probably experiencing some of the VFS limitations in 5.3 (you'll
be pleasantly surprised by 6.1!). portsdb -Uu is very CPU and IO
intensive; it takes a long time on a fast machine. make fetchindex
this.
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
, it creates the INDEX-5.db,
so i'm not sure why i'm running 'portsdb -Uu' in the first
place?
I would highly recommend checking out portsnap; it builds an up-to-date
INDEX-5.db file automatically as part of the update process.
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
that prevent it from having to
continually scan a mailbox for every request. For my largest folders
(30,000+ messages), Dovecot was *at least* an order of magnitude faster.
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
Marc G. Fournier wrote:
In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't appear
to have it enabled, but my older i386 server that I just upgraded to 6.x
does:
user pid %cpu %mem vsz rss tt state starttime command
root 14 104.0 0.0 0 8 ?? RL
Mikhail Teterin wrote:
понеділок 01 травень 2006 17:25, Paul Allen написав:
This was originally mentioned in amd64/76224 which was closed by obrien
with the terse remark: We don't yet support building 32-bit apps on a
64-bit system. We only barely support *running* them at this point.
I may
Evren Yurtesen wrote:
James Long wrote:
Date: Sun, 16 Apr 2006 17:43:58 +0300
From: Evren Yurtesen [EMAIL PROTECTED]
Subject: CPUTYPE=athlon-xp and loader
To: freebsd-stable@freebsd.org
Message-ID: [EMAIL PROTECTED]
Hello,
I have a problem which I have found out from mailing lists that some
Stephen Clark wrote:
[LoN]Kamikaze wrote:
Stephen Clark wrote:
[LoN]Kamikaze wrote:
Alexey Karagodov wrote:
hi.
i think, this unstablity happaning just because developers trying to
make
two systems at one time, one is 6.0 and another 7.0 current and they
supporting old version, lower then
in
/usr/local/etc/cvsup/prefixes/FreeBSD.cvs/src/sys/modules/i2c/controllers/nfsmb/Makefile,v:
1: head expected
I don't see this with cvsup17.us.freebsd.org. What cvsup server are you
using? Have you tried a different one?
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
changed it in the first
place, but it caused some interesting problems...
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
looked at it as well, but I haven't had time to sit down
and bang out a solution. It's at the top of my CVSweb TODO...
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
and bang out a solution. It's at the top of my CVSweb TODO...
it's:
All tags/default branch
(i was looking for latest changes to 6.1)
Yeah, revisions on a branch which contains .0 may not appear at all...
-Jonathan
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
Martin wrote:
There is a quite nasty bug in tr(1) when using
de_DE.ISO8859-1(5) locale.
Try this please:
unsetenv LC_ALL
setenv LANG de_DE.ISO8859-1
echo v | tr a-z A-Z
I'm getting W as result. Shouldn't it be V?
(Unexpected behavior explained elsewhere in the thread.)
The correct way to
Mike Jakubik wrote:
Daniel O'Connor wrote:
On Thu, 12 Jan 2006 13:52, Mike Jakubik wrote:
powerd won't run your CPU at a specific clock frequency - it varies the
CPU frequency based on current load conditions.
The load was 0, only thing that was running was mbmon.
Fair enough.. still..
Paul.LKW wrote:
As I upgraded to 5.4 I found the raid utilities 'asr-util' no longer work
for me.
I tried to deinstall and install again, but the problem still !
The error message in the console after the comman 'raidutil -L raid' is :
Engine connect failed: COMPATILITY number
Any one
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Is that documented? In /sys/i386/conf/NOTES I see:
# You must specify at least one CPU (the one you intend to
Kevin Oberman wrote:
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Ahh, This is the sort of thing I never realized. Is there anything in
the handbook that
Scott Long wrote:
Jonathan Noack wrote:
Kevin Oberman wrote:
Scott Long wrote:
Also, taking out CPU_I586 is usually a bad idea. It offers no
performance penalties (unlike CPU_I386 and maybe CPU_I486), but
enables things like optimized bcopy.
Ahh, This is the sort of thing I never
Mike Jakubik wrote:
Mark Kirkwood wrote:
Is a minor update to the handbook needed in order avoid confusion
then? e.g. I have been commenting out CPU_I586 on all my PIII systems
in the (mistaken it would seem) belief that having CPU_I686 only was
better.
Agreed, i have always just used I686,
/2005-June/thread.html#50882
http://lists.freebsd.org/pipermail/freebsd-current/2005-June/051311.html
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
/IPv4)
http://staff.MyBSD.org.my (IPv6/IPv4)
http://tomoyo.MyBSD.org.my (IPv6/IPv4)
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
a reboot just to avoid questions
about whether the machine is up-to-date.
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
curious and
noticed that newvers.sh was one of the files changed with every security
update. From there it was code inspection...
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
AMD Features=0xc050NX,AMIE,DSP,3DNow!
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
...
Even if it was only a table of contents for that page, why not read it?
Navigation is provided to save you time. Regardless of whether it is
a table of contents for the page, a collection of links, or a
combination of the two, it is still relevant.
--
Jonathan Noack | [EMAIL PROTECTED
requires a non-trivial level of skill and effort.
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
a separate column for the thread info.
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
On 5/12/2005 9:58 AM, Matthias Buelow wrote:
Jonathan Noack wrote:
What happens if the command is long enough to overrun the screen? Is
the thread information truncated and lost? I believe this was the
argument for making a separate column for the thread info.
How about leaving either SIZE
On 5/12/2005 10:21 AM, Matthias Buelow wrote:
Jonathan Noack wrote:
I think you will have a very hard time removing anything from top
because someone will always pipe up and say, I've been using
random_option since the days when computers were measured in
MILLIhertz... *shaking fist* Why not add
.
These should be merged back to 5.4. The merging is done but ULE is still
known to cause panics for some people, especially on SMP systems. Try it
with extreme caution.
In other words, ULE is known to not be stable and will remain so until
someone fixes it.
--
Jonathan Noack | [EMAIL PROTECTED
are production
worthy, we should disable these checks for releases. That is, unless I
am missing something...
Anyone know any good thread tests to run to determine what performance
impact this is having?
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP
On 05/11/05 21:53, Daniel Eischen wrote:
On Wed, 11 May 2005, Jonathan Noack wrote:
I checked out _PTHREADS_INVARIANTS for libthr and libpthread on CURRENT.
As far as I can tell, all but one of the defines under
_PTHREADS_INVARIANTS are ASSERTs; they check for a condition and if it
is false
On 05/10/05 00:21, Billy Newsom wrote:
Jonathan Noack wrote:
On 05/09/05 23:14, Billy Newsom wrote:
From the fstab(5) man page:
The fourth field, (fs_mntops), describes the mount options associated
with the file system. It is formatted as a comma separated list of
options. It contains
0 messages received
0 signals received
7 voluntary context switches
26113 involuntary context switches
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
On 5/9/2005 1:30 PM, Jonathan Noack wrote:
On 5/9/2005 12:31 PM, Pete French wrote:
5.3 ships with SMP turned on, which makes lock operations rather
expensive on single-processor machines. 4.x does not have SMP
turned on by default. Would you be able to re-run your test with
SMP turned off?
I
On 5/8/2005 10:57 PM, Jonathan Noack wrote:
On 05/08/05 14:29, David Gurvich wrote:
cdrom /boot/loader from 5.3 has no problem. However, after updating
world from kernel, /boot/loader is replaced with cvs version. This
one goes into endless cycle of reboots. When replaced with
/boot/loader
not been tested.
When I tried to test this every threaded program died with sig 11. Does
this require me to recompile the program before it will work?
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
/dellbak nfs rw,-s,-x=2,-T 0 0
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
people and no one has stepped up to
resolve it. As it is easily worked around, I've brought it up a few
times but haven't made too big of a fuss. Come to think of it, why
didn't I ever open a PR? Hmm... perhaps I'll do that at work tomorrow
(this is on a machine at work).
--
Jonathan Noack
choice. If it doesn't work you should file a bug.
I'm not sure how to fix your VESA problem...
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description: OpenPGP digital signature
, a new instance will corrupt the shared memory of
another instance (in another jail, on another IP address, etc.) *if*
they are running on the same port. The workaround is to ensure every
instance (regardless of jail or IP address) is running on a unique port.
--
Jonathan Noack | [EMAIL PROTECTED
to
5.4-STABLE to reflect that it is once again open for less-restricted
development. As 5.4 will be released via the RELENG_5_4 branch, it is
normal and expected to have 5.4-STABLE around before 5.4-RELEASE.
--
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
signature.asc
Description
. If
this doesn't generate any leads, try make -DALWAYS_CHECK_MAKE
buildworld before building the kernel. I'm not sure but this could be
an out-of-date make.
Hope that helps.
- --
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (MingW32
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/28/2005 1:54 PM, Damian Gerow wrote:
Thus spake Jonathan Noack ([EMAIL PROTECTED]) [28/04/05 14:53]:
: Does this error happen all the time or only with ATA mkIII?
Only with ATA mkIII. I'm running a system that I rebuilt this morning
/), but it looks like ATA
mkIII didn't make it into the tree until 2 weeks after the last
snapshot. Until the next snapshot is built it looks like you're stuck
using the procedure Samuel described.
- --
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1
63 matches
Mail list logo
