Re: amd64/145654: amd64-curent memory leak in kernel
The following reply was made to PR amd64/145654; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, samsp...@mail.ru Cc: Subject: Re: amd64/145654: amd64-curent memory leak in kernel Date: Sun, 05 Dec 2010 15:14:32 +0200 Is still reproducible? How much RAM do you have? What panic message is printed when this happens? This could be a KVA exhaustion or fragmentation issue related to ZFS. -- Andriy Gapon ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: amd64/138688: [rum] possibly broken on 8 Beta 4 amd64: able to wpa authenticate + obtain dhclient address, no communication though.
The following reply was made to PR amd64/138688; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, micahro...@gmail.com Cc: Subject: Re: amd64/138688: [rum] possibly broken on 8 Beta 4 amd64: able to wpa authenticate + obtain dhclient address, no communication though. Date: Sun, 05 Dec 2010 16:02:09 +0200 Is this still a problem? If yes, please try discussing it on net@ mailing list. -- Andriy Gapon ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/146517: [ath] [wlan] device timeouts for ath wlan device on recent stable.
Synopsis: [ath] [wlan] device timeouts for ath wlan device on recent stable. State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Sun Dec 5 18:03:54 UTC 2010 State-Changed-Why: This was fixed in r209541/r209548 and was merged before 8.1 was released. http://www.freebsd.org/cgi/query-pr.cgi?pr=146517 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: bin/152716: hostapd(8) fails to authenticate after 2010-11-03 update
Old Synopsis: hostapd fails ti authenticate after 2010-11-03 update New Synopsis: hostapd(8) fails to authenticate after 2010-11-03 update Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 6 03:43:30 UTC 2010 Responsible-Changed-Why: Although this was an rpaulo MFC, he is not currently working on this code; so, assign it to -net. http://www.freebsd.org/cgi/query-pr.cgi?pr=152716 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
RE: EHOSTUNREACH returned for refused IPv6 connection
> Sorry, you're right: I forgot I don't have my tunnel setup so there's no > external IPv6 connectivity (I don't have an IPv6 network configured at > the moment at all). What confused me initially was the fact that ssh > displays the "No route to host" error instead of "Connection refused" > when both IPv4 and IPv6 addresses are available but only IPv4 works. I'm experiencing something which may be related. I posted a question in the FreeBSD Forums: http://forums.freebsd.org/showthread.php?t=19895 I don't get anything displayed at the application (ftp / telnet / etc.) level - it just hangs until the connection eventually times out. I do see unreachables getting into the FreeBSD box - it just seems like they don't make it down to the application level. The post I linked above has a more detailed description, as well as tcpdump output and so forth. System is 8-STABLE as of November 28th, but I see the same thing on a 6-STABLE from February 2010. Terry Kennedy http://www.tmk.com te...@tmk.com New York, NY USA ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
