Pyun YongHyeon wrote:
> On Tue, Mar 09, 2010 at 11:55:30PM +0200, Ian FREISLICH wrote:
> > I set the RX as high as 512 in 64 quanta but it made little difference
> > to the interrupt rate. At times where we experience the packet
> > loss and com_no_buffers increases, the interrupt rate on between
On Wed, 10 Mar 2010, Adrenalin wrote:
Hi, I would like to know if this bug has been fixed in the FreeBSD 8 Release
since I got it 3 times already on a busy box that use heavily NFS (with lots
of files).
Unfortunately my processes are not compiled with debug symbols(so I cannot
get an backtrace
On 03/09/10 12:14, Li, Qing wrote:
> This error was caused by my commit r204902 from yesterday.
>
> Please try patch at
>
> http://people.freebsd.org/~qingli/route.h.diff
This doesn't appear to be committed yet, is it still the best fix?
Doug
--
... and that's just a little bi
TB --- 2010-03-10 00:43:04 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:43:04 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-03-10 00:43:04 - cleaning the object tree
TB --- 2010-03-10 00:43:15 - cvsupping the source tree
TB --- 2010-03-10 00:43:15 - /usr/b
TB --- 2010-03-10 00:41:41 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:41 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-03-10 00:41:41 - cleaning the object tree
TB --- 2010-03-10 00:42:10 - cvsupping the source tree
TB --- 2010-03-10 00:42:10 - /usr
TB --- 2010-03-10 00:41:35 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:35 - starting HEAD tinderbox run for ia64/ia64
TB --- 2010-03-10 00:41:35 - cleaning the object tree
TB --- 2010-03-10 00:41:57 - cvsupping the source tree
TB --- 2010-03-10 00:41:57 - /usr/bin/c
TB --- 2010-03-10 00:41:39 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:39 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-03-10 00:41:39 - cleaning the object tree
TB --- 2010-03-10 00:42:06 - cvsupping the source tree
TB --- 2010-03-10 00:42:06 - /usr
TB --- 2010-03-10 00:41:39 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:41:39 - starting HEAD tinderbox run for mips/mips
TB --- 2010-03-10 00:41:39 - cleaning the object tree
TB --- 2010-03-10 00:41:51 - cvsupping the source tree
TB --- 2010-03-10 00:41:51 - /usr/bin/c
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:30 - cvsupping the source tree
TB --- 2010-03-10 00:40:30 - /usr/bin
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for i386/pc98
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:25 - cvsupping the source tree
TB --- 2010-03-10 00:40:25 - /usr/bin/c
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for i386/i386
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:27 - cvsupping the source tree
TB --- 2010-03-10 00:40:27 - /usr/bin/c
TB --- 2010-03-10 00:40:01 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-03-10 00:40:01 - starting HEAD tinderbox run for arm/arm
TB --- 2010-03-10 00:40:01 - cleaning the object tree
TB --- 2010-03-10 00:40:16 - cvsupping the source tree
TB --- 2010-03-10 00:40:16 - /usr/bin/csu
Hi, I would like to know if this bug has been fixed in the FreeBSD 8 Release
since I got it 3 times already on a busy box that use heavily NFS (with lots
of files).
Unfortunately my processes are not compiled with debug symbols(so I cannot
get an backtrace), but I've got all the php-cgi stuck in th
If you are on head/stable_7/stable_8 you can also do quick test with top mode
pmcstat -S unhalted-cycles -T (http://wiki.freebsd.org/PmcTools/PmcTop).
For more in depth post processing with source code (c+asm) you can output to
Kcachegrind (http://wiki.freebsd.org/PmcTools/PmcKcachegrind).
Fabie
trash_ctor and trash_dtor? You're running with INVARIANTS.
___
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"
> -Original Message-
> From: Ryan Stone [mailto:ryst...@gmail.com]
> Sent: Tuesday, March 09, 2010 2:31 PM
> To: David Christensen
> Cc: pyu...@gmail.com; Ian FREISLICH; curr...@freebsd.org
> Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss
>
> > What's the traffic look
> What's the traffic look like? Jumbo, standard, short frames? Any
> good ideas on profiling the code? I haven't figured out how to use
> the CPU TSC but there is a free running timer on the device that
> might be usable to calculate where the driver's time is spent.
>
> Dave
In my experience h
On Tue, Mar 09, 2010 at 11:55:30PM +0200, Ian FREISLICH wrote:
> Pyun YongHyeon wrote:
> > On Tue, Mar 09, 2010 at 03:31:55PM +0200, Ian FREISLICH wrote:
> > > Can you explain the tunables please - I'm guessing it's these:
>
> I think I asked the wrong question. What is a "Quick BD Chain"?
I don
> > > > It's been running for about 1:23 on the patched driver.
> I'm still
> > > > seeing the com_no_buffers increase:
> > > >
> > > > [firewall2.jnb1] ~ # sysctl dev.bce |grep com_no_buffers
> > > > dev.bce.0.com_no_buffers: 5642
> > > > dev.bce.1.com_no_buffers: 497
> > > > dev.bce.2.com_no_
Pyun YongHyeon wrote:
> On Tue, Mar 09, 2010 at 03:31:55PM +0200, Ian FREISLICH wrote:
> > Can you explain the tunables please - I'm guessing it's these:
I think I asked the wrong question. What is a "Quick BD Chain"?
What relation should this number have to traffic rate. Is there a
maximum and
> > > patch can fix the RX issue you're suffering from. Anyway,
> would you
> > > give it try the patch at the following URL?
> > > http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> > > The patch was generated against CURRENT and you may see a message
> > > like "Disabling COAL_NOW time
On Tue, Mar 09, 2010 at 01:31:55PM -0800, David Christensen wrote:
> > > > patch can fix the RX issue you're suffering from. Anyway,
> > would you
> > > > give it try the patch at the following URL?
> > > > http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> > > > The patch was generated a
On Tue, Mar 09, 2010 at 10:26:29AM +0200, Ian FREISLICH wrote:
> Pyun YongHyeon wrote:
> > patch can fix the RX issue you're suffering from. Anyway, would you
> > give it try the patch at the following URL?
> > http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> > The patch was generated aga
Am Sunday 07 March 2010 18:59:07 schrieb David Ehrmann:
> On 3/7/10 1:44 AM, Norikatsu Shigemura wrote:
> > Hi Devid and Julian.
> >
> > On Sat, 06 Mar 2010 22:10:28 -0800
> >
> > Julian Elischer wrote:
> >> David Ehrmann wrote:
> >>> Does FreeBSD currently support cryptographic acceleration for A
Julian Elischer wrote:
Li, Qing wrote:
This error was caused by my commit r204902 from yesterday.
[...]
I remember saying "well the patch itself is basically ok but I don't
know about the side effects". (about the ARPv2 change in general)
I'm guessing you have had a rather interesting lea
Li, Qing wrote:
This error was caused by my commit r204902 from yesterday.
[...]
I remember saying "well the patch itself is basically ok but I don't
know about the side effects". (about the ARPv2 change in general)
I'm guessing you have had a rather interesting learning experience
about h
On Tue, Mar 09, 2010 at 03:31:55PM +0200, Ian FREISLICH wrote:
> Pyun YongHyeon wrote:
> > On Mon, Mar 08, 2010 at 04:45:20PM +0200, Ian FREISLICH wrote:
> > > Pyun YongHyeon wrote:
> > > > On Fri, Mar 05, 2010 at 11:16:41PM +0200, Ian FREISLICH wrote:
> > > > > Pyun YongHyeon wrote:
> > > > > > Th
On Tue, Mar 9, 2010 at 5:14 PM, Li, Qing wrote:
> This error was caused by my commit r204902 from yesterday.
>
> Please try patch at
>
> http://people.freebsd.org/~qingli/route.h.diff
Patch fixed the problem, thanks for the quick reply and fix.
--
Renato Botelho
_
This error was caused by my commit r204902 from yesterday.
Please try patch at
http://people.freebsd.org/~qingli/route.h.diff
-- Qing
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Li, Qing
> Sent: Tuesd
Thanks for the report, I am looking at it and will get back to you.
-- Qing
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Renato Botelho
> Sent: Tuesday, March 09, 2010 10:47 AM
> To: FreeBSD Current
> Subject: E
I updated my 9.0-current amd64 today on rev. 204915 and start
to get errors like this
127.0.0.1: no route to host
I boot using kernel.old and everything back to normal. I don't know
exactly revision of my kernel.old because last change made on
sys/conf/newvers.sh simply removed this information f
Pyun YongHyeon wrote:
> On Mon, Mar 08, 2010 at 04:45:20PM +0200, Ian FREISLICH wrote:
> > Pyun YongHyeon wrote:
> > > On Fri, Mar 05, 2010 at 11:16:41PM +0200, Ian FREISLICH wrote:
> > > > Pyun YongHyeon wrote:
> > > > > Thanks for the info. Frankly, I have no idea how to explain the
> > > > > iss
On 8 March 2010, at 12:33, Robert Watson wrote:
>
> On Mon, 8 Mar 2010, Doug Hardie wrote:
>
>> I run a number of 4 core systems with em interfaces. These are production
>> systems that are unmanned and located a long way from me. Under unusual
>> conditions it can take up to 6 hours to get
Jayachandran C. wrote:
On Thu, Mar 04, 2010 at 06:34:03PM +0530, C. Jayachandran wrote:
I'm testing this on the mips platform, but I think there is an issue
with change that made sectorsize int64_t, because the ioctl
DIOCGSECTORSIZE used to read sector size seems to take u_int. This
quick chang
On 9 Mar 2010, at 00:10, James R. Van Artsdalen wrote:
> Norikatsu Shigemura wrote:
>> According to http://en.wikipedia.org/wiki/AES-NI , we can get
>> specification document: http://software.intel.com/file/20457 .
>>
>> I saw it, and consider that we can release under BSDL. Because
>
Pyun YongHyeon wrote:
> patch can fix the RX issue you're suffering from. Anyway, would you
> give it try the patch at the following URL?
> http://people.freebsd.org/~yongari/bce/bce.20100305.diff
> The patch was generated against CURRENT and you may see a message
> like "Disabling COAL_NOW timedou
36 matches
Mail list logo
