Hi,
I have exactly the same problem explained below (except with FreeBSD
8.2RC3). I lost a lot of packets on the carp interface.
I tested with a point-to-point attachment and there is no problem...
Now that I know that the problem must comes from the switch, how can I
solve it ? Is there a work
Hi,
On Wed, Feb 16, 2011 at 2:30 PM, Jack Vogel wrote:
> I've been in email conversation with Beezar, and he's clarified some
> things, I think
> I would like to try his approach to the issue, it will mean one more
> iteration of changes
> to test, would you be willing to do so?
Yes, sure.
- A
Synopsis: [iwn] iwn driver fails to power on adapter after resume
Responsible-Changed-From-To: freebsd-net->bschmidt
Responsible-Changed-By: bschmidt
Responsible-Changed-When: Thu Feb 17 07:04:59 UTC 2011
Responsible-Changed-Why:
over to me
http://www.freebsd.org/cgi/query-pr.cgi?pr=154826
_
Old Synopsis: iwn driver fails to power on adapter after resume
New Synopsis: [iwn] iwn driver fails to power on adapter after resume
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Feb 17 04:15:31 UTC 2011
Responsible-Changed-Wh
On 16 February 2011 15:51, Monthadar Al Jaberi wrote:
> I think anytime the destination node sends a PREP to the originator
> node that is not a peering node (not in direct contact with) we would
> get this panic.
Ok. Would you mind doing a quick audit to see what other KASSERT()s are
lurking a
> On 14.01.2011 18:46, Mike Tancsa wrote:
> I also have very loaded mpd/PPPoE servers that panic all the time:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/153255
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/153671
I've just got yet another panic on mpd5 box after about 30 days of upt
Yes.
2011/2/16 Jack Vogel
> I've been in email conversation with Beezar, and he's clarified some
> things, I think
> I would like to try his approach to the issue, it will mean one more
> iteration of changes
> to test, would you be willing to do so? It would be good to know for sure
> if his a
I think anytime the destination node sends a PREP to the originator
node that is not a peering node (not in direct contact with) we would
get this panic.
On Wed, Feb 16, 2011 at 8:52 PM, Adrian Chadd wrote:
> Besides being a potential DoS vector (and thus panicing on anything
> like that == bad i
Besides being a potential DoS vector (and thus panicing on anything
like that == bad idea), what legitimate-but-broken circumstances could
cause a node to hear its own announcement?
Adrian
On 15 February 2011 07:00, Monthadar Al Jaberi wrote:
> Hej,
>
> I found that a panic can be generated w
I've been in email conversation with Beezar, and he's clarified some
things, I think
I would like to try his approach to the issue, it will mean one more
iteration of changes
to test, would you be willing to do so? It would be good to know for sure if
his approach
also eliminates the problem.
Jac
Hi Jack,
On Fri, Feb 11, 2011 at 2:57 PM, Jack Vogel wrote:
> Yes, it was the fix for this, Mike has tested and confirmed it eliminates
> the problem, and yes
> I will MFC the relevant bits back to 8 and 7 for you asap.
>
I can confirm this works too. A machine showing the symptoms in a
couple of
Jay Borkenhagen wrote this message on Wed, Feb 16, 2011 at 10:47 -0500:
> After having been disappointed by one vendor *, I am returning to this
> list to seek recommendations for 1000Base-SX PCI NICs. I am looking
> to run them on FreeBSD 8 and beyond, and I need support for MTU > 1500
> bytes (i
On 2/16/11 5:20 AM, Nikolay Denev wrote:
On 15 Feb, 2011, at 21:08 , Nikolay Denev wrote:
On 15.02.2011, at 18:53, Arnaud Lacombe wrote:
Hi,
On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote:
changing it to '_' might be accceptable, '.' is much like '/' in th
filesystem.
it is a se
You're using POLLING on your physical interfaces.
Sometimes they go down and you lose your CARP interface.
OR
For whatever reason you lose your CARP interface.
Get the output from `dmesg` , see if you get logs saying your carp
interface went down then back up, there are high chances it did.
Hi again, again,
The problem seams to be even more general (so I put freebsd-net in
copy).
When I ping carp interface, I lost some pings...
ping data-test
PING data-test.embl.fr (172.26.9.236) 56(84) bytes of data.
64 bytes from data-test.embl.fr (172.26.9.236): icmp_req=7 ttl=64
time=0.183 ms
6
Hi,
After having been disappointed by one vendor *, I am returning to this
list to seek recommendations for 1000Base-SX PCI NICs. I am looking
to run them on FreeBSD 8 and beyond, and I need support for MTU > 1500
bytes (initially around 4470, but possibly closer to 9k later).
On http://www.free
On 15 Feb, 2011, at 21:08 , Nikolay Denev wrote:
> On 15.02.2011, at 18:53, Arnaud Lacombe wrote:
>
>> Hi,
>>
>> On Tue, Feb 15, 2011 at 11:30 AM, Julian Elischer wrote:
>>> changing it to '_' might be accceptable, '.' is much like '/' in th
>>> filesystem.
>>> it is a separator. You can't ha
On Wed, Feb 16, 2011 at 03:04:09PM +0600, Eugene Grosbein wrote:
E> On 16.02.2011 14:46, Gleb Smirnoff wrote:
E> > On Wed, Feb 16, 2011 at 10:13:59AM +0600, Eugene Grosbein wrote:
E> > E> I run AMD64 with 4GB of memory, lots of memory is free and
E> > E> I still get panics often, sometimes two in a
On 16.02.2011 14:46, Gleb Smirnoff wrote:
> On Wed, Feb 16, 2011 at 10:13:59AM +0600, Eugene Grosbein wrote:
> E> I run AMD64 with 4GB of memory, lots of memory is free and
> E> I still get panics often, sometimes two in a couple of hours.
> E> It does not seem memory exhaustion to me. It seems as
19 matches
Mail list logo
