Re: [CFT] Call for testing pkg 1.5.0
On Mar 31, 2015, at 17:24, Sergei Vyshenski wrote: > Instead, the following succeded: > # cd /usr/ports/ports-mgmt/pkg-devel > # make reinstall > ... > # pkg -v > 1.4.99.16 That is expected. WITH_PKG=devel is a make(1) option that only affects ports (non-binary pkgs). -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HEADS UP: instability on stable/8
On 23 Sep 2010, at 02:44, jhell wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 09/22/2010 13:23, Rui Paulo wrote: >> Hi, While I'm merging the userland DTrace bits to stable/8 you might >> experience some instability if you use DTrace. If you use DTrace, I >> suggest you don't try to upgrade during the next 5 days. >> >> Thanks for your patience, -- Rui Paulo >> > > Thank you Rui this is much appreciated. If there is a specific version > when you start those commits could that be noted as well on this thread ? I haven't merged anything yet because I'm stuck with a technical discussion about whether or not one particular change (not DTrace related) breaks KBI. I'll let you know when I start merging things. Regards, -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
HEADS UP: instability on stable/8
Hi, While I'm merging the userland DTrace bits to stable/8 you might experience some instability if you use DTrace. If you use DTrace, I suggest you don't try to upgrade during the next 5 days. Thanks for your patience, -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ICC users compiling FreeBSD
Hi, I'm looking for people who are using the Intel Compiler to build FreeBSD. Please contact me off list, so I can get a rough estimate on how many people are using it. Regards, -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Kernel panic when unpluggin AC adaptor
Please try this patch:
Index: acpi_cpu.c
===
--- acpi_cpu.c (revision 207322)
+++ acpi_cpu.c (working copy)
@@ -997,12 +997,12 @@
if (notify != ACPI_NOTIFY_CX_STATES)
return;
+ACPI_SERIAL_BEGIN(cpu);
/* Update the list of Cx states. */
acpi_cpu_cx_cst(sc);
acpi_cpu_cx_list(sc);
/* Update the new lowest useable Cx state for all CPUs. */
-ACPI_SERIAL_BEGIN(cpu);
cpu_cx_count = 0;
for (i = 0; i < cpu_ndevices; i++) {
isc = device_get_softc(cpu_devices[i]);
Regards,
--
Rui Paulo
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Kernel panic when unpluggin AC adaptor
On 5 May 2010, at 08:40, Demelier David wrote:
> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov :
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx
>> levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'
I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with
and without the AC cord plugged in.
Regards,
--
Rui Paulo
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Kernel panic when unpluggin AC adaptor
On 4 May 2010, at 21:38, Kostik Belousov wrote:
> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov :
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>>if (cx_next->p_lvlx == NULL)
>>>printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.
I don't remember the details, but I've seen this before. Does your CPU Cx
levels change when you plug/unplug the AC adapter?
Regards,
--
Rui Paulo
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-8.0 802.11n support with ath/mwl
On 1 Mar 2010, at 03:05, Jim Pingle wrote: > On 2/28/2010 9:41 PM, Rui Paulo wrote: >> On 1 Mar 2010, at 02:26, Jim Pingle wrote: >>> Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate >>> on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug >>> and that doesn't show up on my system. Another system with a ral(4) card >>> does have that sysctl. Judging by the information in the wlandebug(8) >>> man page it appears as though this may be a side effect of mwl doing >>> much of the work in firmware. >> >> wlandebug takes an -i argument. I seem to recall you created your wlan >> interface named "mwl_wlan0", so you need to type wlandebug -i mwl_wlan0. > > I saw that, but that is hardcoded to expect wlan (wlan0, wlan1, etc) > for an interface name. Having seen that, I recompiled wlandebug without > the hardcoded interface name check and it didn't work either, but it did > toss an error for the sysctl it was trying to tweak. The whole system was designed for the interfaces to start with "wlan" and be named "wlan". > That made me look deeper at the code and see it was really just setting > the debug sysctl based on flags that wlandebug was aware of. Handy, but > the same thing could be done by hand with sysctl and some bitwise math > in a pinch, assuming the interface has the right oids. (Which mine > doesn't, for some reason...) The purpose of wlandebug is to not do any math by hand. -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-8.0 802.11n support with ath/mwl
On 1 Mar 2010, at 02:26, Jim Pingle wrote: > On 2/28/2010 7:03 PM, Rui Paulo wrote: >> On 28 Feb 2010, at 17:38, Jim Pingle wrote: >>> Are there some other bits that need set in order to have clients >>> associate with HT rates? Or some other prerequisite conditions such as >>> number of attached antennae? I do only have one antenna attached as I >>> didn't have a second pigtail for this test unit's case. The card >>> actually has three connectors. >> >> Having only 1 antenna connected will likely impact your connection. > > I'll hook up two more and try again when I get a chance, I just need to > pull them from a working unit that isn't using its wifi currently. > >>> I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), >>> or ifconfig(8) man pages about troubleshooting rates. I see plenty of >>> talk in ifconfig(8) about use and control of HT rates, but given what >>> I'm seeing in ifconfig, it should be set to use them. I've tried several >>> combinations of channels and standards (e.g. 11ng, 11na) but always end >>> up with a 54Mbps link. >>> >>> I'd appreciate any more pointers that you (or anyone else reading) may >>> have. I'd like to write up something on the topic once I get it fully >>> operational. >> >> I don't know what's happening, but I guess your Windows 7 laptop isn't >> sending the necessary HT rates in the association. Try using wlandebug to >> see what's happening. > > Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate > on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug > and that doesn't show up on my system. Another system with a ral(4) card > does have that sysctl. Judging by the information in the wlandebug(8) > man page it appears as though this may be a side effect of mwl doing > much of the work in firmware. > > I appreciate the information though, thanks for taking the time to > reply. I'll continue to work on this again once I relocate some pigtails > from another box. wlandebug takes an -i argument. I seem to recall you created your wlan interface named "mwl_wlan0", so you need to type wlandebug -i mwl_wlan0. -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-8.0 802.11n support with ath/mwl
On 28 Feb 2010, at 17:38, Jim Pingle wrote: > On 2/28/2010 7:54 AM, Rui Paulo wrote: >> On 28 Feb 2010, at 03:22, Jim Pingle wrote: >>> >>> Are you aware if similar work ongoing for the mwl(4) based 802.11n >>> cards? I picked up a couple cheap this past week and have them working >>> with hostapd but, as with the OP in the thread, only with G rates. >>> >>> The ifconfig[1] output suggests that it is using 40MHz wide ht channels >>> but devices only associate at 54Mbps[2]. >>> >>> Jim >>> >>> [1] ifconfig mwl0_wlan1 >>> mwl0_wlan1: flags=8843 metric 0 >>> mtu 1500 >>> ether 00:01:36:17:96:0e >>> inet6 fe80::201:36ff:fe17:960e%mwl0_wlan1 prefixlen 64 scopeid 0x9 >>> inet 192.168.15.1 netmask 0xff00 broadcast 192.168.15.255 >>> nd6 options=3 >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11na >>> status: running >>> ssid WatchTower channel 100 (5500 MHz 11a ht/40+) bssid 00:01:36:17:96:0e >>> regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3 >>> AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 scanvalid 60 >>> ampdulimit 64k ampdudensity 4 shortgi smps burst dtimperiod 1 >>> >>> >>> [2] ifconfig mwl0_wlan1 list sta (w/addr removed) >>> AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG >>> 1 120 54M 33.00 1537 25952 EP A RSN (rssi 68:20:20 nf >>> 0:0:0) >> >> mwl supports HT rates, but it looks like your AP is not sending HT rates to >> you. > > Thanks for the quick clarification, that's very encouraging to find out! > > In this case, the mwl card is the AP. The client line is from an > associated Windows 7 laptop with an Intel 5100abgn card which does show > the AP as 802.11n in the AP list. I'm connected and sending this message > through it right now, actually. > > Are there some other bits that need set in order to have clients > associate with HT rates? Or some other prerequisite conditions such as > number of attached antennae? I do only have one antenna attached as I > didn't have a second pigtail for this test unit's case. The card > actually has three connectors. Having only 1 antenna connected will likely impact your connection. > I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), > or ifconfig(8) man pages about troubleshooting rates. I see plenty of > talk in ifconfig(8) about use and control of HT rates, but given what > I'm seeing in ifconfig, it should be set to use them. I've tried several > combinations of channels and standards (e.g. 11ng, 11na) but always end > up with a 54Mbps link. > > I'd appreciate any more pointers that you (or anyone else reading) may > have. I'd like to write up something on the topic once I get it fully > operational. I don't know what's happening, but I guess your Windows 7 laptop isn't sending the necessary HT rates in the association. Try using wlandebug to see what's happening. -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-8.0 802.11n support with ath/mwl
On 28 Feb 2010, at 03:22, Jim Pingle wrote: > On 2/27/2010 9:09 PM, Rui Paulo wrote: >> On 27 Feb 2010, at 20:29, Robert Watson wrote: >> Progress on supporting 11n with atheros cards is on going. There's much more >> to it than adapting the rate control algorithm. Please stay tuned. > > Are you aware if similar work ongoing for the mwl(4) based 802.11n > cards? I picked up a couple cheap this past week and have them working > with hostapd but, as with the OP in the thread, only with G rates. > > The ifconfig[1] output suggests that it is using 40MHz wide ht channels > but devices only associate at 54Mbps[2]. > > Jim > > [1] ifconfig mwl0_wlan1 > mwl0_wlan1: flags=8843 metric 0 > mtu 1500 > ether 00:01:36:17:96:0e > inet6 fe80::201:36ff:fe17:960e%mwl0_wlan1 prefixlen 64 scopeid 0x9 > inet 192.168.15.1 netmask 0xff00 broadcast 192.168.15.255 > nd6 options=3 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11na > status: running > ssid WatchTower channel 100 (5500 MHz 11a ht/40+) bssid 00:01:36:17:96:0e > regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3 > AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 scanvalid 60 > ampdulimit 64k ampdudensity 4 shortgi smps burst dtimperiod 1 > > > [2] ifconfig mwl0_wlan1 list sta (w/addr removed) > AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 1 120 54M 33.00 1537 25952 EP A RSN (rssi 68:20:20 nf > 0:0:0) mwl supports HT rates, but it looks like your AP is not sending HT rates to you. -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD-8.0 802.11n support with ath
Hi, On 27 Feb 2010, at 20:29, Robert Watson wrote: > > On Sat, 27 Feb 2010, Spil Oss wrote: > >> Thanks for the confirmation! >> >> Is anything known re. a timeline for implementation of wireless-N? (8.1? >> 9.0?) > > I know that Rui Paulo is working on this actively; I've added him to the CC > line as I'm not sure if he follows freebsd-stable. > > Robert N M Watson > Computer Laboratory > University of Cambridge > >> >> Kind regards, >> >> Spil >> >> On Sat, Feb 27, 2010 at 1:43 PM, Bernhard Schmidt >> wrote: >>> On Sat, Feb 27, 2010 at 01:27:09PM +0100, Spil Oss wrote: >>>> Hi All, >>>> >>>> Got myself an Atheros AR5416 card to upgrade my HostAP to Wireless-N speed. >>>> >>>> Somehow I can't find a way to convince the driver to go into 11n mode >>>> >>>> # ifconfig wlan0 mode 11b >>>> # ifconfig wlan0 mode 11g >>>> # ifconfig wlan0 mode 11n >>>> ifconfig: SIOCSIFMEDIA (media): Device not configured >>> >>> It's either mode 11na or mode 11ng. >>> >>>> The man-page for ifconfig specifies only 11a, 11b and 11g as modes. >>>> The part is functioning fine in 11g mode. The man page also specifies 11na and 11ng, so I hope you're running 8.0, at least. >>>> >>>> Am I missing something obvious or is Wireless-N support not fully >>>> implemented yet? >>> >>> There is no rate control algo fuer 11n, afaik, you will only be able to >>> use legacy rates. Progress on supporting 11n with atheros cards is on going. There's much more to it than adapting the rate control algorithm. Please stay tuned. Regards, -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: RELEASE discs & ISO images (for future)
Vadim Goncharov wrote: Hi! 7.0-RELEASE images came out with FIVE disks - disc 1 to 3 and separate LiveFS and docs. What do they contain? I can guess that 2 and 3 are pure packages so I don't need to download them if I want to compile out from ports. And in previous releases I had to download the disc1 ONLY as it had LiveFS also - a very good improvement since 4.x times where disc2 with only LiveFS, mostly useless all the time, took separate disk. But now release announcement says that for LiveFS I need TWO disks - both disc1 and livefs disk. WHY? Why not to pack they both to a single disc1, this was very comfortable. Well, technically, you don't need both discs. LiveFS CD is bootable. Regarding to the other question, it was split because, with the introduction of new userland tools, disc1 grew to a size that did not fit on one CDROM. Regards. -- Rui Paulo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
