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
I tried your patch, but my laptop hung at startup.
The last line I saw on console was "Timecounters tick every 1.000 msec".
I didn't dig into the problem and don't have any information useful
for debugging, but I'm going
to play with it later today.
Dmitry
On Mon, Oct 25, 2010 at 1:29 PM, Bernha
Synopsis: ppp(8) hangs instead terminating
State-Changed-From-To: feedback->closed
State-Changed-By: jh
State-Changed-When: Mon Nov 8 16:01:56 UTC 2010
State-Changed-Why:
Feedback timeout.
http://www.freebsd.org/cgi/query-pr.cgi?pr=97392
___
freebsd-ne
Synopsis: [carp] [lagg] CARP combined with LAGG causes system panic - 7.0/amd64
Responsible-Changed-From-To: gonzo->freebsd-net
Responsible-Changed-By: gonzo
Responsible-Changed-When: Tue Nov 9 00:43:55 UTC 2010
Responsible-Changed-Why:
Over to mainainer(s)
http://www.freebsd.org/cgi/query-pr.cg
Synopsis: [gre] [patch] possible depletion of kernel stack in ip_gre.c when
net.isr.enable = 1
Responsible-Changed-From-To: gonzo->freebsd-net
Responsible-Changed-By: gonzo
Responsible-Changed-When: Tue Nov 9 00:46:12 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s)
http://www.freebsd.or
Synopsis: [ng_mppc] ng_mppc_decompress - disabling node
Responsible-Changed-From-To: gonzo->freebsd-net
Responsible-Changed-By: gonzo
Responsible-Changed-When: Tue Nov 9 00:47:38 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s)
http://www.freebsd.org/cgi/query-pr.cgi?pr=123045
___
On Fri, Nov 05, 2010 at 11:10:37AM +0100, Yamagi Burmeister wrote:
> Hi,
>
> some time ago we migrated a lot of boxes from Linux to FreeBSD. Those
> machines have a "NVIDIA nForce4 CK804 MCP4" network adapter, supported
> by nfe(4). Even if nfe(4) at least tries to enable the WOL capability of
> t
On Fri, Nov 5, 2010 at 4:47 PM, Ask Bjørn Hansen wrote:
> I agree that it was pretty dumb of the OpenBSD developers to just stomp on
> another protocol ID for their (and ours in FreeBSD ...) implementation.
Actually, in this particular case I think it was justified. The IANA
refused to allocate