> IMO, any kind of memory allocation code (malloc, uma, netgraph item
> allocator) never return EPERM, they return ENOMEM or ENOBUFS.
>
> So, there is a bug somewhere else.
I think so, but for me it still looks like resource shortage. As I wrote
before, when EPERM starts appearing, I'm unable to
On Mon, Apr 11, 2011 at 12:34:56AM +0200, Przemyslaw Frasunek wrote:
P> > Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column.
P> > If you see non-zero values there, you need to increase netgraph memory
limits
P> > net.graph.maxdata and net.graph.maxalloc using /boot/loader.con
I'm having some random panics in HEAD related to mpd/netgraph also. I
thought it would be good to use this thread instead of opening another
one. I felt that Glebius patches helped my boxes (500~600 PPPoE
connections peak) panic less frequently than before, but they still
are panicing randomly. Som
On 11.04.2011 05:34, Przemyslaw Frasunek wrote:
>> Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column.
>> If you see non-zero values there, you need to increase netgraph memory limits
>> net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf.
>
> Unfortunately, incre
It used to be that if you did a 'mount' on the client server, it would
tell you what options existed on the mount ... but now, it just shows
(nfs) ... my fstab entry looks like:
192.168.1.8:/vm/neptune.hub.org /vm/neptune.hub.org
nfs rw,noauto,intr,tcp,nolockd 0 0
Mount
Synopsis: [bce] [panic] arpintr()->in_lltable_lookup() 8.1 bce(4) crash
Responsible-Changed-From-To: freebsd-net->yongari
Responsible-Changed-By: yongari
Responsible-Changed-When: Sun Apr 10 22:55:25 UTC 2011
Responsible-Changed-Why:
Grab.
http://www.freebsd.org/cgi/query-pr.cgi?pr=156026
__
Synopsis: [bce] [panic] arpintr()->in_lltable_lookup() 8.1 bce(4) crash
State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Sun Apr 10 22:54:34 UTC 2011
State-Changed-Why:
I think it's not a bug of bce(4) but arp(4) and I guess it was
fixed in 8.2-RELEASE.
Can you
Synopsis: [re] if_re.ko driver cannot handle RL8169 card properly
State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Sun Apr 10 22:44:34 UTC 2011
State-Changed-Why:
Completely remove vendor's driver, "rtl_bsd_drv_v179", and reboot
and show me the full dmesg output
> Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column.
> If you see non-zero values there, you need to increase netgraph memory limits
> net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf.
Unfortunately, increasing net.graph.maxdata & net.graph.maxalloc didn't
sol
For various reasons, I occasionally boot my netbook as a diskless
client of my main server (this is a quick/easy way to test upgrades
without needing to install them). Since I still like to use it as
a netbook in this mode (ie, wander around the house), I've run into
a couple of issues that I have
On 11.04.2011 03:45, Przemyslaw Frasunek wrote:
>> Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column.
>> If you see non-zero values there, you need to increase netgraph memory limits
>> net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf.
>
> Thanks, indeed it he
> Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column.
> If you see non-zero values there, you need to increase netgraph memory limits
> net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf.
Thanks, indeed it helped a lot. I also noticed that other zones have
non-ze
Old Synopsis: Wrong order of IPv6 NS DAD/MLD Report
New Synopsis: [ip6] Wrong order of IPv6 NS DAD/MLD Report
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Sun Apr 10 19:46:09 UTC 2011
Responsible-Changed-Why:
Over to maintainer(s
On 10.04.2011 16:00, Przemyslaw Frasunek wrote:
> Eventually I found that this issue is related to mbuf exhaustion. In
> periods when sendto() fails with EPERM, the "requests for mbufs denied"
> counter is increasing and "ngctl list" also fails.
>
Use command "vmstat -z|egrep 'ITEM|NetGraph'" and
Hi,
Does the attached patch fix the problem for you?
--
Mikolaj Golub
Index: sys/kern/uipc_socket.c
===
--- sys/kern/uipc_socket.c (revision 220485)
+++ sys/kern/uipc_socket.c (working copy)
@@ -1845,10 +1845,16 @@ dontblock:
}
W dniu 08.04.2011 22:13, Przemyslaw Frasunek pisze:
> I'm still looking for a help in investigating this issue. The problem appears
> on
> two 7.4 boxes, while 7.3 are working OK. Ktrace shows, that indeed some of
> sendto() calls on netgraph control socket are failing with EPERM:
[...]
Eventuall
16 matches
Mail list logo