Synopsis: [iwi] [panic] iwi panic when issuing /etc/rc.d/netif restart on
8-STABLE r205159
Responsible-Changed-From-To: freebsd-fs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Mar 15 08:31:21 UTC 2010
Responsible-Changed-Why:
oops.
pointed out by: brucec
http://ww
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
On Mon, Mar 15, 2010 at 08:31:45AM +, lini...@freebsd.org wrote:
> Synopsis: [iwi] [panic] iwi panic when issuing /etc/rc.d/netif restart on
> 8-STABLE r205159
I am more than happy to work with somebody on this bug if you need
access to the machine (SSH, it's a laptop so it doesn't have a
ser
Hi,
> On Sat, 13 Mar 2010 20:25:29 +0800
> Earl Lapus said:
earl> I was browsing through the ping6 code and I noticed that one
earl> particular call to getaddrinfo() didn't have a freeaddrinfo() pair.
earl> All calls to getaddrinfo() should have an equivalent freeaddrinfo(),
right?
Yup
I confirm this problem for another server:
stable 8 amd64 + vlan + carp
Whenever I join a bridge with a vlan interface:
ifconfig bridge0 addm vlan35
The system soon or later freezes.
This time it has happened after 3 days of normal behavior.
No logs, no dump.
On 03.03.2010 12:30, Giulio Fer
On Tue, Mar 16, 2010 at 12:06 AM, Hajimu UMEMOTO wrote:
>
> Yup, it should be good practice. But, this is rather intentional.
> The `hostname' variable points to res->ai_canonname, and is used
> later. This is why the `res' variable is declared globally.
>
> Sincerely,
>
I see. I was unable to
Old Synopsis: [arp] proxyarp broken in 8.0
New Synopsis: [arp] proxyarp broken in 8.0 [regression]
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Mar 16 04:10:40 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://
On Feb 28, 1:30 pm, to.my.troc...@gmail.com (Mikolaj Golub) wrote:
> But I have faced with another issue (not related to your patch, as it is
> observed with unpatched kernel too). When I try to run concurrently two
> create/destroy scripts with the same interface the system panics:
>
> Unread p
