https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205264
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
K
Hans:
After talking with Gleb he tells me part of your test is to kldunload a module.
Now I think that is the source of the problem.
Probably the cleanup code failed to stop the timer and did the remove.. thus
when the timer expires it blows up.
This is not a callout issue.. I think you need to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205194
--- Comment #1 from Kristof Provost ---
I've had a quick look at this, and imagine my surprise when it turned out to
not actually be a PF bug.
Briefly, the pfsync interface doesn't have any ip6 data associated with it,
while the netinet6 c
On Fri, Dec 11, 2015 at 10:16:50AM -0500, James Craig wrote:
> On Thu, 10 Dec 2015, Mark Johnston wrote:
>
> > On Thu, Dec 10, 2015 at 10:58:11AM -0500, James Craig wrote:
> >>
> >>
> >> Hey all!
> >>
> >> I am migrating some of our services to freeBSD, and in the process of this,
> >> I have disc
Hans:
I don’t think you are getting a 1 back from the callout_reset()..
If the pending bit is set, you get a 1 back. But if you have a race where
the arp-timer is blocked on the lock (held by arp resolve) your going to
have the pending bit off.. since before calling the function the callout
code
On Thu, 10 Dec 2015, Mark Johnston wrote:
On Thu, Dec 10, 2015 at 10:58:11AM -0500, James Craig wrote:
Hey all!
I am migrating some of our services to freeBSD, and in the process of this,
I have discovered something that seems odd to me; netgroups don't seem to work
as expected.
I am trying
On 12/11/15 12:16, Hans Petter Selasky wrote:
On 12/11/15 11:12, Alexander V. Chernikov wrote:
11.12.2015, 12:15, "Hans Petter Selasky" :
Hi,
Pulling the nail out of the haystack hopefully.
Any ideas on where next to look?
Adrian: In your dump aswell I see:
la_flags = 1
That means ther
On 12/11/15 11:12, Alexander V. Chernikov wrote:
11.12.2015, 12:15, "Hans Petter Selasky" :
Hi,
Pulling the nail out of the haystack hopefully.
Any ideas on where next to look?
Adrian: In your dump aswell I see:
la_flags = 1
That means there was a race calling arptimer() and removing th
11.12.2015, 12:15, "Hans Petter Selasky" :
> Hi,
>
> Pulling the nail out of the haystack hopefully.
>
>>> Any ideas on where next to look?
>
> Adrian: In your dump aswell I see:
>
> la_flags = 1
>
> That means there was a race calling arptimer() and removing the "lle".
Yes. The interesting part h
Hi,
Pulling the nail out of the haystack hopefully.
Any ideas on where next to look?
Adrian: In your dump aswell I see:
la_flags = 1
That means there was a race calling arptimer() and removing the "lle".
Alexander: Can you comment on the following patch:
> Index: netinet/if_ether.c
>
On 10.12.15 23:02, Mark Johnston wrote:
>> some time ago Mark Johnston has published there the patch related to
>> this problem:
>> https://lists.freebsd.org/pipermail/freebsd-net/2013-February/034682.html
>>
>> Maybe Mark has something to say about it.
>
> I started trying to push this work in wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202484
--- Comment #3 from oliv...@cochard.me ---
I beleive I've found the source of the problem in this message:
https://lists.freebsd.org/pipermail/svn-src-head/2014-January/055007.html
"It also does not handle multicast filter configuration wh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202484
Andrey V. Elsukov changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #
13 matches
Mail list logo
