misc/170629: acIskjJMUP
>Number: 170629 >Category: misc >Synopsis: acIskjJMUP >Confidential: no >Severity: serious >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Aug 14 09:10:09 UTC 2012 >Closed-Date: >Last-Modified: >Originator: UDfCnHAFWUjQJzXBmD >Release:suIXbDMgiLLhgOG >Organization: pvhthwPHE >Environment: bfEl blog lo tienes en un honistg de pago o es un honistg gratuito? Si es en uno gratuito puede que al ser gratuito se permitan la licencia de poner la publicidad que ellos quieren; y puede que ese sea tu problema. +8 >Description: bfEl blog lo tienes en un honistg de pago o es un honistg gratuito? Si es en uno gratuito puede que al ser gratuito se permitan la licencia de poner la publicidad que ellos quieren; y puede que ese sea tu problema. +8 >How-To-Repeat: bfEl blog lo tienes en un honistg de pago o es un honistg gratuito? Si es en uno gratuito puede que al ser gratuito se permitan la licencia de poner la publicidad que ellos quieren; y puede que ese sea tu problema. +8 >Fix: bfEl blog lo tienes en un honistg de pago o es un honistg gratuito? Si es en uno gratuito puede que al ser gratuito se permitan la licencia de poner la publicidad que ellos quieren; y puede que ese sea tu problema. +8 >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/170630: garbled syslog messages
>Number: 170630 >Category: kern >Synopsis: garbled syslog messages >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Aug 14 09:10:10 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Frederique Rijsdijk >Release:7.4, 8.x, 9.x, 32-bit, 64-bit >Organization: Net Ground B.V. >Environment: FreeBSD srv01.server.nl 8.1-RELEASE-p6 FreeBSD 8.1-RELEASE-p6 #0: Wed Nov 23 15:41:03 CET 2011 r...@srv01.server.nl:/usr/obj/usr/src/sys/GENERIC-QUOTA amd64 FreeBSD srv02.server.nl 7.4-RELEASE-p3 FreeBSD 7.4-RELEASE-p3 #0: Tue Sep 27 14:47:23 UTC 2011 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 FreeBSD srv03.server.nl 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Tue Jun 12 00:39:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD srv04.server.nl 8.1-RELEASE-p5 FreeBSD 8.1-RELEASE-p5 #0: Tue Sep 27 16:49:00 UTC 2011 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I see these kind of 'garbled' logging on various servers, various versions and archs: <<1110>10>iippffww:: 65600 500A cAccecpetp tU DP U8D7.P2 5807..125404..61i4:p4f49w5:.0 69 :6865020.68043 .2A4c3 c6e.p82t01 .U28D4:P.5 23837 6.o.2ut52 01v2i:.5a13 4 4io.g6ubt0 : <<<11101>110i0>a1> pi7fg6b9w0 : <<111010> >0.8645.0203 6Ac.c2ep1t 2U:5D3P 8ou7t .v2i5a0. 1i4g4b.06 <<1101>1i0>pifpwf:w : 68006 80D0 eDneyn y UUDDPP 119944..113344..4411..1122::560877110 8877..225500..11..1100::5533 iinn vviiaa iiggbb00 <<110>1710>.295:02.11 4i4n. 1v0i:a2 1i gibn0 >How-To-Repeat: No idea honstly, also cannot find a common factor for this issue. But almost every admin has seen it I think. I've seen them as long as I can remember. >Fix: Some have suggested to compile this into the kernel: options PRINTF_BUFR_SIZE=128 . but I'd rather keep running GENERIC kernels (freebsd-update) >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: junk/170629: acIskjJMUP
Synopsis: acIskjJMUP State-Changed-From-To: open->closed State-Changed-By: sunpoet State-Changed-When: Tue Aug 14 09:20:36 UTC 2012 State-Changed-Why: Junk PR. Responsible-Changed-From-To: freebsd-bugs->gnats-admin Responsible-Changed-By: sunpoet Responsible-Changed-When: Tue Aug 14 09:20:36 UTC 2012 Responsible-Changed-Why: Junk PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=170629 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
bin/170631: [PATCH] Add roaming support to wpa_supplicant
>Number: 170631 >Category: bin >Synopsis: [PATCH] Add roaming support to wpa_supplicant >Confidential: no >Severity: non-critical >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Aug 14 11:00:21 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Daan Vreeken >Release:FreeBSD 10.0-CURRENT amd64 >Organization: Vitsch Electronics - http://VitschVPN.nl/ >Environment: System: FreeBSD Devel13.Vitsch.LAN 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Jan 28 21:31:14 CET 2012 root@Compile2:/usr/src/sys/amd64/compile/Multimedia amd64 >Description: The wpa_supplicant application has the ability to do roaming based on the received signal strength indication (RSSI), but currently this is broken in FreeBSD. At this moment wpa_supplicant will always report a level of 0dBm for all detected wireless networks. >How-To-Repeat: Run wpa_supplicant with the '-d' option set and with a configuration file that allows it to connect to at least two Access Points that are in the vicinity of the receiver. Note that wpa_supplicant will always report a level of '0' for all networks. >Fix: The wpa_supplicant's FreeBSD driver interface only sets 'result->qual' and 'result->noise', but not 'result->level' in wpa_driver_bsd_add_scan_entry(), while the latter is used when sorting AP's based on their signal strength. The attached patch fixes this by calculating 'result->level' according to it's definition in net80211/ieee80211_node.h . The patch also fixes a spelling error in ieee80211_var.h . If the patch somehow gets mangled in the email, it can also be downloaded from: http://www.Vitsch.nl/pub_diffs/ After applying the patch, wpa_supplicant will now successfully attempt to roam when background scanning is enabled and there is an AP with a higher signal strength. Sponsored by: Vitsch Electronics --- patch_wpa_supplicant_rssi_fix_2012_08_14.diff begins here --- Index: usr.sbin/wpa/wpa_supplicant/driver_freebsd.c === --- usr.sbin/wpa/wpa_supplicant/driver_freebsd.c(revision 238968) +++ usr.sbin/wpa/wpa_supplicant/driver_freebsd.c(working copy) @@ -693,6 +693,11 @@ result->caps = sr->isr_capinfo; result->qual = sr->isr_rssi; result->noise = sr->isr_noise; +/* + * the rssi value reported by the kernel is in 0.5dB steps relative to + * the reported noise floor. see ieee80211_node.h for details. + */ +result->level = sr->isr_rssi / 2 + sr->isr_noise; pos = (u8 *)(result + 1); Index: sys/net80211/ieee80211_var.h === --- sys/net80211/ieee80211_var.h(revision 238968) +++ sys/net80211/ieee80211_var.h(working copy) @@ -55,7 +55,7 @@ #include #include -#defineIEEE80211_TXPOWER_MAX 100 /* .5 dbM (XXX units?) */ +#defineIEEE80211_TXPOWER_MAX 100 /* .5 dBm (XXX units?) */ #defineIEEE80211_TXPOWER_MIN 0 /* kill radio */ #defineIEEE80211_DTIM_DEFAULT 1 /* default DTIM period */ --- patch_wpa_supplicant_rssi_fix_2012_08_14.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
On 9.0-RELEASE#0 sh(1) gobbles high bit until set with arg or sh recursion
Yup. They're gone except '$ set -o' or '$ set +o' (*not* '$ set') is called or yet another sh(1) is started, which doesn't need such hints. (In plain cat(1) or ee(1) or whatever everything is fine from the start.) Thanks and ciao, --steffen ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/170636: spelling mistake "oustanding" in kernel tree
>Number: 170636 >Category: kern >Synopsis: spelling mistake "oustanding" in kernel tree >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Aug 14 17:40:10 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Adam McDougall >Release:9.0-stable >Organization: >Environment: FreeBSD daemon 9.0-STABLE FreeBSD 9.0-STABLE #1: Mon Jul 16 08:02:14 EDT 2012 mcdouga9@daemon:/usr/obj/usr/src/sys/AMD64-9 amd64 >Description: I saw a typo in a SCSI error printed by the kernel on a server experiencing trouble. I did a grep to see where it occurs, sometimes just comments but some of it is live code: grep -R oustanding * sys/dev/isci/scil/scif_sas_domain.c: // oustanding requests that matches the criteria supplied by the sys/dev/isci/scil/scif_sas_domain.c: // oustanding requests that matches the criteria supplied by the sys/dev/sfxge/common/efx_mcdi.c: * by virtue of there only being one oustanding MCDI request. sys/dev/sfxge/common/efx_mcdi.c: * If there is an oustanding event-completed MCDI operation, then we sys/contrib/octeon-sdk/cvmx-mixx-defs.h: 4 oustanding timestamp interrupts, this field should sys/contrib/octeon-sdk/cvmx-dpi-defs.h: Limits the number of oustanding load requests on sys/cam/scsi/scsi_da.c: xpt_print(periph->path, "oustanding %d\n", sys/cam/ctl/scsi_ctl.c: xpt_print(periph->path, "%ju CCBs oustanding (%ju allocated, %ju " >How-To-Repeat: grep -R oustanding /usr/src/sys (I did not see this typo outside of sys) >Fix: s/oustanding/outstanding/g >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: conf/170098: virtual access points with Atheros ath driver
On Mon, Jul 23, 2012 at 6:30 PM, wrote: > Thank you very much for your problem report. > It has the internal identification `conf/170098'. > The individual assigned to look at your > report is: freebsd-bugs. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=170098 > >>Category: conf >>Responsible:freebsd-bugs >>Synopsis: virtual access points with Atheros ath driver >>Arrival-Date: Mon Jul 23 22:30:12 UTC 2012 This has been fixed by the attached 2 patches, which are applied to -HEAD in order. Thanks muchly to PseudoCylon for his work, this has taken a while but the difficult solutions are that way. thanks -kim addon.patch Description: Binary data iter.patch Description: Binary data ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: bin/166656: [patch] dhclient(8) doesn't exit os link down
The following reply was made to PR bin/166656; it has been noted by GNATS. From: Peter Jeremy To: Yuri Cc: bug-follo...@freebsd.org Subject: Re: bin/166656: [patch] dhclient(8) doesn't exit os link down Date: Wed, 15 Aug 2012 10:19:13 +1000 --aVD9QWMuhilNxW9f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Sorry for the delay in responding, I got side-tracked. On 2012-Jul-13 11:16:30 -0700, Yuri wrote: >dhclient on exit should also remove the IP address it has set. Yes, and the patch in the existing PR _should_ do that - it invokes the failure handler in the same way as the other dhclient failure modes. Unfortunately, there seems to be a separate issue in dhclient so that it is not passing the IP address to the failure handler. --=20 Peter Jeremy --aVD9QWMuhilNxW9f Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAq6wEACgkQ/opHv/APuIek3wCgiji96IJ78nGrjd7SljjADQ6d a0MAoIjy4wTjqaR6YB+BaZ9DY57EmP9n =GepU -END PGP SIGNATURE- --aVD9QWMuhilNxW9f-- ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
