Hi,
every few days or so, my -STABLE NFS server (v3 and v4) gets wedged with a ton
of messages about nfsd server cache flooded, try to increase nfsrc_floodlevel
in the log, and nfsstat shows TCPPeak at 16385. It requires a reboot to
unwedge, restarting the server does not help.
The clients
Bezüglich Kevin Oberman's Nachricht vom 08.08.2013 01:11 (localtime):
On Wed, Aug 7, 2013 at 11:04 AM, Harald Schmalzbauer
h.schmalzba...@omnilan.de wrote:
Bezüglich Attilio Rao's Nachricht vom 14.10.2012 02:27 (localtime):
On Fri, Sep 21, 2012 at 1:22 AM, Attilio Rao atti...@freebsd.org
Am 07.08.2013 21:01 (UTC+1) schrieb Rainer Hurling:
Thanks, Bapt, for answering.
Am 07.08.2013 19:43, schrieb Baptiste Daroussin:
On Wed, Aug 07, 2013 at 07:28:41PM +0200, Rainer Hurling wrote:
After introducing r253839 on HEAD (/head/contrib/binutils/ld/ldmain.c),
I recognized some wired
Lars Eggert wrote:
Hi,
every few days or so, my -STABLE NFS server (v3 and v4) gets wedged
with a ton of messages about nfsd server cache flooded, try to
increase nfsrc_floodlevel in the log, and nfsstat shows TCPPeak at
16385. It requires a reboot to unwedge, restarting the server does
On Tuesday, August 06, 2013 2:30:54 pm Glen Barber wrote:
On Tue, Aug 06, 2013 at 01:11:07PM -0500, Matthew D. Fuller wrote:
On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of
Glen Barber, and lo! it spake thus:
The error generated is non-fatal, and once I receive response
On Thu, Aug 08, 2013 at 11:14:05AM -0400, John Baldwin wrote:
On Tuesday, August 06, 2013 2:30:54 pm Glen Barber wrote:
On Tue, Aug 06, 2013 at 01:11:07PM -0500, Matthew D. Fuller wrote:
On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of
Glen Barber, and lo! it spake thus:
The most recent CURRENT doesn't work with the x11/nvidia-driver (which
is at 319.25 in the ports and 325.15 from nVidia).
After build- and installworld AND successfully rebuilding port
x11/nvidia-driver, the system crashes immediately after a reboot as
soon the kernel module nvidia.ko seems to
On 08/08/13 14:10, O. Hartmann wrote:
The most recent CURRENT doesn't work with the x11/nvidia-driver (which
is at 319.25 in the ports and 325.15 from nVidia).
After build- and installworld AND successfully rebuilding port
x11/nvidia-driver, the system crashes immediately after a reboot as
soon
Can you go over some previous versions in -HEAD and see when it was introduced?
-adrian
On 8 August 2013 11:10, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
The most recent CURRENT doesn't work with the x11/nvidia-driver (which
is at 319.25 in the ports and 325.15 from nVidia).
After
On Aug 7, 2013, at 10:16 PM, Warner Losh i...@bsdimp.com wrote:
On Aug 5, 2013, at 11:20 AM, Adrian Chadd wrote:
.. and I bet it's not a design pattern, and this is total conjecture on my
part:
* the original drivers weren't SMP safe;
* noone really sat down and figured out how to
On Thu, Aug 8, 2013 at 1:31 AM, Harald Schmalzbauer
h.schmalzba...@omnilan.de wrote:
Bezüglich Kevin Oberman's Nachricht vom 08.08.2013 01:11 (localtime):
On Wed, Aug 7, 2013 at 11:04 AM, Harald Schmalzbauer
h.schmalzba...@omnilan.de wrote:
Bezüglich Attilio Rao's Nachricht vom
On Thu, 2013-08-08 at 11:30 -0700, Adrian Chadd wrote:
Can you go over some previous versions in -HEAD and see when it was
introduced?
-adrian
On 8 August 2013 11:10, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
The most recent CURRENT doesn't work with the x11/nvidia-driver
Hi guys,
I've just got a panic with:
FreeBSD obiwan 10.0-CURRENT FreeBSD 10.0-CURRENT #21: Sun Jul 21 21:37:10 CEST
2013 root@obiwan:/usr/obj/usr/src/sys/OBIWAN amd64
I have a core around if needed.
obiwan:/usr/src# svn info
Path: .
Working Copy Root Path: /usr/src
URL:
Woo! Tell Jeff! File a PR! Set everything on fire!
-adrian
On 8 August 2013 14:39, Sean Bruno sean_br...@yahoo.com wrote:
On Thu, 2013-08-08 at 11:30 -0700, Adrian Chadd wrote:
Can you go over some previous versions in -HEAD and see when it was
introduced?
-adrian
On 8 August 2013
.. and it's not just about saturate the port with traffic.
It's also about what happens if I shut down the MAC whilst I'm in the
process of programming in new RX/TX descriptors?
The ath(4) driver had a spectacular behaviour where if you mess things
up the wrong way it will quite happily DMA crap
Yup, it's an incredibly unsafe pattern. It also leads to the pattern where
auxiliary processing is handed off to a taskqueue, which then interleaves
the lock ownership with the ithread and produces out-of-order packet
reception.
Scott
On Aug 8, 2013, at 5:18 PM, Adrian Chadd adr...@freebsd.org
On Thu, 8 Aug 2013 11:30:23 -0700
Adrian Chadd adr...@freebsd.org wrote:
Can you go over some previous versions in -HEAD and see when it was
introduced?
Not that easy. I tried simply rebuilding the kernel with older sources,
but then the compiler fails compiling the nvidia port. I think I have
On Thu, 08 Aug 2013 14:39:21 -0700
Sean Bruno sean_br...@yahoo.com wrote:
On Thu, 2013-08-08 at 11:30 -0700, Adrian Chadd wrote:
Can you go over some previous versions in -HEAD and see when it was
introduced?
-adrian
On 8 August 2013 11:10, O. Hartmann
18 matches
Mail list logo
