On Fri, Jun 17, 2005 at 10:30:25AM -0500, Greg Barniskis wrote:
I think he meant comparing 36,000 on CentOS (async) to 24,000 on
CURRENT (sync). I wondered that myself, and having searched out the
answer I find that it is declared in
On Mon, 20 Jun 2005, Eirik Øverby wrote:
Hmm. Looks like a bug in dummynet. ipfw should not be directly re-
injecting UDP traffic back into the input path from an outbound path,
or it risks re-entering, generating lock order problems, etc. It should
be getting dropped into the netisr queue
Hello twesky,
t atapci0: Intel ICH4 UDMA100 controller port
t 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on
t pci0
t ata0: channel #0 on atapci0
t ata1: channel #1 on atapci0
t The last known good stable version for me was aprox April 25, my next
t cvsup was May 17, but I
Hi, I tried ahc controller, but with ahd (29320 controller) the
situation is identical :(
I have a database server data and system on this hard drive. And for
example when I start cvsup or copy big files, this errors starts.
Somewhere on google, I read that problems might be when Tagged Queing
Hello,
i follows up these thread and i think you all digging on the false
possible error location..
I have made many performance tests with RELENG_4 related to RELENG_5
and DragonFly and Gentoo.
My results was that RELENG_5 is half as RELENG_4 fast by disk-access
(ata-related).
I have seen
At 11:09 20/06/2005, Tony Byrne wrote:
[...]
Of course, there
can be hardware reasons for timeouts such as a dying disk or cable,
but I think we've eliminated these in our case. [etc]
Don't ignore the possibility of failing controller hardware. We had
comparable mysterious problems on a
Hello Bob,
can be hardware reasons for timeouts such as a dying disk or cable,
but I think we've eliminated these in our case. [etc]
BB Don't ignore the possibility of failing controller hardware. We had
BB comparable mysterious problems on a client system, causing a lot of
BB head-scratching.
Michael Schuh wrote:
My results was that RELENG_5 is half as RELENG_4 fast by disk-access
(ata-related).
I have seen that RELENG_5 with GENERIC Kernel and only modified option HZ=2000.
the spread begind with Gentoo (mentoided from me as the slowest, but
errare humanum est)
Gentoo : 100%
Tony Byrne wrote:
Hello Bob,
can be hardware reasons for timeouts such as a dying disk or cable,
but I think we've eliminated these in our case. [etc]
BB Don't ignore the possibility of failing controller hardware. We had
BB comparable mysterious problems on a client system,
Hello,
yes random IO is more targetted to Databases.
noop, i have the installation always made in the same way, and i have respected
the different diskperformace in different disk-parts.
this was the reason for
#cd /;
at the beginning of my tests.
In the first test i have me shooting self
At 12:12 20/06/2005, Tony Byrne wrote:
Hello Bob,
can be hardware reasons for timeouts such as a dying disk or cable,
but I think we've eliminated these in our case. [etc]
BB Don't ignore the possibility of failing controller hardware. We had
BB comparable mysterious problems on a client
On Fri, 17 Jun 2005, David Sze wrote:
FreeBSD/amd64 5.4-RELEASE (libpthread, system and process scope)
FreeBSD/amd64 6.0-CURRENT (libpthread, libthr, system and process
scope)
CentOS/amd64 4.0 (i.e. RHEL4.0)
I couldn't get libthr to work on FreeBSD/amd64 5.4-RELEASE,
On 20. jun. 2005, at 10.38, Robert Watson wrote:
On Mon, 20 Jun 2005, Eirik Øverby wrote:
Hmm. Looks like a bug in dummynet. ipfw should not be directly
re- injecting UDP traffic back into the input path from an
outbound path, or it risks re-entering, generating lock order
Hello Bob,
BB It didn't to me either. Note the use of 'mysterious' :-)
BB I'd eliminated drives and cables, and then did it all over again when the
BB failure went hard, leaving the controller (or something else on the mobo).
BB With a new mobo all the annoying timeouts which I'd put down to
At 13:19 20/06/2005, Tony Byrne wrote:
Hello Bob,
BB It didn't to me either. Note the use of 'mysterious' :-)
BB I'd eliminated drives and cables, and then did it all over again when the
BB failure went hard, leaving the controller (or something else on the mobo).
BB With a new mobo all the
I had a similar problem and i changed system cases where i was getting a
ICRC error and FreeBSD refused to load or even mount the root fs, it was
also giving errors with something to do with the ATA something or other,
it turned out to be the cable i used after rebuilding the system in the
new
Zoran Kolic wrote:
Dear all!
After moving to amd64 system (64-bit),
I have problem writing cd with cdrecord.
Release 5.4
Nec 3520a (dvd writer)
If you wish to write DVDs, then you can try
/usr/ports/sysutils/dvd+rw-tools
If you just wish write CD-R/RW then you can try burncd (8) which is
Gleb Smirnoff wrote:
Dear colleagues,
today I've got problem with named exiting on signal 11. Yes, I've searched
archives and found that POKED TIMER is a problem in our threads.
Has anyone faced this problem and workarounded it? Or may be even fixed it?
Is there anywhere detailed description
I am receiving the same problems with FreeBSD 5.4-RELEASE (amd64) bind-9.3.1
DELL PE2850
2 x Intel(R) Xeon(TM) CPU 3.20GHz
4 GB RAM
named.log.0:19-Jun-2005 11:46:15.945 *** POKED TIMER ***
named.log.0:19-Jun-2005 18:34:17.314 *** POKED TIMER ***
named.log.0:20-Jun-2005 02:40:46.193 *** POKED
On Mon, Jun 20, 2005 at 10:53:19AM +0200, Eirik verby wrote:
I know enough not to call this a confirmation, but disabling
dummynet did indeed allow me to finish the backup. I never made it
past 15GBs before, now the full 19GB tar.gz file is done, and the
boxes are both still running. The
Hello Jayton,
Monday, June 20, 2005, 3:46:20 PM, you wrote:
JG I had a similar problem and i changed system cases where i was getting a
JG ICRC error and FreeBSD refused to load or even mount the root fs, it was
JG also giving errors with something to do with the ATA something or other,
JG it
On 20. jun. 2005, at 17.18, Marc Olzheim wrote:
On Mon, Jun 20, 2005 at 10:53:19AM +0200, Eirik verby wrote:
I know enough not to call this a confirmation, but disabling
dummynet did indeed allow me to finish the backup. I never made it
past 15GBs before, now the full 19GB tar.gz file is
Jayton Garnett wrote:
I had a similar problem and i changed system cases where i was getting
a ICRC error and FreeBSD refused to load or even mount the root fs, it
was also giving errors with something to do with the ATA something or
other, it turned out to be the cable i used after
On Saturday, 11. June 2005 17:05, Daniel Eischen wrote:
You can set the environment variable LIBPTHREAD_SYSTEM_SCOPE to force
libpthread to use system scope.
I've played around with that variable (set it in .xsession) and found that
kpdf (from graphics/kdegraphics3) will reproducably crash if
On Mon, 20 Jun 2005, Michael Nottebrock wrote:
On Saturday, 11. June 2005 17:05, Daniel Eischen wrote:
You can set the environment variable LIBPTHREAD_SYSTEM_SCOPE to force
libpthread to use system scope.
I've played around with that variable (set it in .xsession) and found that
kpdf
On Monday, 20. June 2005 18:53, Daniel Eischen wrote:
Works here on a month or two old -current. I'm using
/usr/local/ant/docs/appendix_e.pdf as a test (it's 60 pages or so).
Crashes for me:
[EMAIL PROTECTED]:127:~ env LIBPTHREAD_SYSTEM_SCOPE=1 kpdf
On Mon, 20 Jun 2005, Michael Nottebrock wrote:
On Monday, 20. June 2005 18:53, Daniel Eischen wrote:
Works here on a month or two old -current. I'm using
/usr/local/ant/docs/appendix_e.pdf as a test (it's 60 pages or so).
Crashes for me:
[EMAIL PROTECTED]:127:~ env
Dear friends:
I just installed FreeBSD 5.4. I have two primary HD: the first disk holds
WinXP, the second disk now has FreeBSD.
Well, the good news is that my first install of FreeBSD went perfectly. I
selected ALL for installation of ports and packages so it took a good hour
to install
On Mon, Jun 20, 2005 at 06:29:31PM +0200, Eirik verby wrote:
Hmm, does that solve kern/79208 for you as well by any chance ?
Seems not.
Now, how do I get my box back to life? ;)
Hmm, Sorry 'bout that... :-/
Marc
pgpAHJk8H7OoT.pgp
Description: PGP signature
On Mon, Jun 20, 2005 at 08:08:59AM -0700, Doug Barton wrote:
D Gleb Smirnoff wrote:
D Dear colleagues,
D
D today I've got problem with named exiting on signal 11. Yes, I've searched
D archives and found that POKED TIMER is a problem in our threads.
D
D Has anyone faced this problem and
Dear Alex and friends:
Thanks a million. And what a relief!
Benjamin
- Original Message -
From: Alex Zbyslaw [EMAIL PROTECTED]
To: Benjamin Sher [EMAIL PROTECTED]
Cc: FreeBSD-Questions Questions freebsd-questions@freebsd.org
Sent: Monday, June 20, 2005 12:41 PM
Subject: Re: After
Am Montag, 20. Juni 2005 19:36 schrieb Benjamin Sher:
Dear friends:
I just installed FreeBSD 5.4. I have two primary HD: the first disk
holds WinXP, the second disk now has FreeBSD.
Well, the good news is that my first install of FreeBSD went perfectly.
I selected ALL for installation of
Thanks for clarifying guys. Are either of you in a position to upgrade to
-stable and see if the problem persists?
Doug
--
This .signature sanitized for your protection
___
freebsd-stable@freebsd.org mailing list
Mitch Parks wrote:
On Sun, 19 Jun 2005, Doug White wrote:
On Fri, 17 Jun 2005, Mitch Parks wrote:
Below are details regarding another crash on a Dell 2600 SMP (HTT and
USB
disabled). It has been 9 days since the last crash. I didn't have the
serial
console in place for this last crash, but
On Sun, 19 Jun 2005, Mitch Parks wrote:
On Sun, 19 Jun 2005, Doug White wrote:
As noted, the ttwakeup() panic is a known bug. The best thing we have for
a fix is this patch:
http://people.freebsd.org/~mlaier/tty.t_pgrp.diff
Please give it a try and report back if you have any more panics
Philippe PEGON wrote:
Mitch Parks wrote:
On Sun, 19 Jun 2005, Doug White wrote:
On Fri, 17 Jun 2005, Mitch Parks wrote:
Below are details regarding another crash on a Dell 2600 SMP (HTT
and USB
disabled). It has been 9 days since the last crash. I didn't have
the serial
console in place
My laptop works fine with Fedora Core 4. I'm not sure it's a hardware
issue, and I don't have an identical laptop to test. Do we know the
last working stable version?
-
actually, that makes a lot of sense. my computer running FreeBSD is
actually just an
On 6/20/05, Rong-En Fan [EMAIL PROTECTED] wrote:
Hmm.. after switching from uw-imap to dovecot, this hang seems not exist
anymore. I'm guessing that possible causes by different locking mechanism
used by Postfix and uw-imap (flock and fnctl...).
Weird. I run qmail/courier-imap (tried
twesky wrote:
My laptop works fine with Fedora Core 4. I'm not sure it's a hardware
issue, and I don't have an identical laptop to test. Do we know the
last working stable version?
I just compiled the kernel from May 26th. Works fine. It looks like
for me it's broken between May 26th and May
Mitch Parks a écrit :
On Sun, 19 Jun 2005, Mitch Parks wrote:
On Sun, 19 Jun 2005, Doug White wrote:
As noted, the ttwakeup() panic is a known bug. The best thing we have
for
a fix is this patch:
http://people.freebsd.org/~mlaier/tty.t_pgrp.diff
Please give it a try and report back if
On 21/06/2005, at 1:16 AM, Danny Cooper wrote:
I am receiving the same problems with FreeBSD 5.4-RELEASE (amd64)
bind-9.3.1
DELL PE2850
2 x Intel(R) Xeon(TM) CPU 3.20GHz
4 GB RAM
named.log.0:19-Jun-2005 11:46:15.945 *** POKED TIMER ***
named.log.0:19-Jun-2005 18:34:17.314 *** POKED TIMER
Jayton Garnett [EMAIL PROTECTED] writes:
I had a similar problem and i changed system cases where i was getting a
ICRC error and FreeBSD refused to load or even mount the root fs, it was
also giving errors with something to do with the ATA something or other,
it turned out to be the cable i
I wrote:
So, kernel got the DMA error at boot and couldn't mount the root fs.
Ah, btw.. it's a SATA disk, on an ICH6 SATA150 controller.
mkb.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
Michael Schuh wrote:
Hello,
yes random IO is more targetted to Databases.
noop, i have the installation always made in the same way, and i have respected
the different diskperformace in different disk-parts.
this was the reason for
#cd /;
at the beginning of my tests.
In the first test
My custom use freeBSD 4.7 release and ask me to install JDK1.4 on it .
But when I use ports to compile JDK , the system show me a message :
You must have a version of FreeBSD later than 4.7-STABLE February 2003
or 5-CURRENT February 2003 to compile and use JDK 1.4.2.
So I have to update my 4.7
I am trying to install an USB printer
i would like to guide me through all the installation if possible.
--
Mohamed M. Maher
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
On Tue, 21 Jun 2005 13:22, Maher Mohamed wrote:
I am trying to install an USB printer
i would like to guide me through all the installation if possible.
- Run kldload ulpt
- Plug the printer in.
- Set it up like a parallel printer except the port is /dev/ulpt0
(ie using CUPS or APSfilter etc)
47 matches
Mail list logo
