RE: Revision 297176 - hyperv/evttimer: Use an independent message slot so that it can work

Hello I recently update one of my many vms from an older CURRENT revision r297196 to r297659 and on reboot it just panics with the following: FreeBSD clang version 3.8.0 (tags/RELEHSE_380/final 262564) (based on LLVM 3.8.0 ) VT(vga): text 80x25 Timecounter "Hyper-V" frequency 1000 Hz quali

Re: Revision 297176 - hyperv/evttimer: Use an independent message slot so that it can work

I have reverted this change. It will be brought back, after some code refactoring. On Fri, Apr 8, 2016 at 4:22 PM, wrote: > > Hello > > I recently update one of my many vms from an older CURRENT revision r297196 > to r297659 and on reboot it just panics with the following: > > FreeBSD clang ver

Jenkins build is still unstable: FreeBSD_HEAD #168

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Booting FreeBSD on a RPI3

I also did a build based on HardenedBSD. Networking works. https://hardenedbsd.org/~shawn/rpi3/2016-04-04/rpi3.img.xz On Thu, Apr 07, 2016 at 09:42:07PM -0400, Ted W. wrote: > I too anxiously await the widespread availability of FreeBSD on the Pi3. > If you're like me and just can't wait the ima

RE: Revision 297176 - hyperv/evttimer: Use an independent message slot so that it can work

Hi smokehydration, I guess your VM config file has something like "viridian = 1" or "viridian_enlightenment=xxx". With this, Xen tries to pretend to be Hyper-V, but obviously Xen can't be 100% Hyper-V. BTW, I know at least KVM can have the same behavior. We have to find a reliable way to disting

Jenkins build is still unstable: FreeBSD_HEAD #169

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Revision 297176 - hyperv/evttimer: Use an independent message slot so that it can work

On Fri, Apr 08, 2016 at 11:03:46AM +, Dexuan Cui wrote: > Hi smokehydration, > I guess your VM config file has something like "viridian = 1" or > "viridian_enlightenment=xxx". > > With this, Xen tries to pretend to be Hyper-V, but obviously Xen can't be > 100% Hyper-V. > BTW, I know at least

RE: Revision 297176 - hyperv/evttimer: Use an independent message slot so that it can work

> From: Konstantin Belousov [mailto:kostik...@gmail.com] > Sent: Friday, April 8, 2016 22:02 > To: Dexuan Cui > Cc: Sepherosa Ziehau ; smokehydrat...@tutanota.com; > freebsd-current@freebsd.org > Subject: Re: Revision 297176 - hyperv/evttimer: Use an independent message > slot so that it can work

stall-free memory reads ? (possibly stale) ?

Hi, I have an application with two threads sharing a memory variable, one continuously writing, one continuously reading. Because of the way my system works, the reader can tolerate reading stale data, but it should not stall on memory reads (the line is on the local cache for the reader, just mig

Re: stall-free memory reads ? (possibly stale) ?

On Fri, Apr 08, 2016 at 06:24:16PM +0200, Luigi Rizzo wrote: > Hi, > I have an application with two threads sharing a memory variable, > one continuously writing, one continuously reading. > > Because of the way my system works, the reader can tolerate reading > stale data, but it should not stall

Jenkins build is still unstable: FreeBSD_HEAD #170

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

WIFI urtwn possibly broken on 297561

Dears I'm testing the CURRENT version on a beaglebone black and have noted the follow behavior. On revision 297561 the wifi adapter stops works after a pkg update. I did the follow tests. Using the version 296898 (OK behavior) and 297561 (wrong behavior): FreeBSD beaglebone 11.0-CURRENT FreeB

Re: WIFI urtwn possibly broken on 297561

hi, try 'ifconfig wlan0 -ff -amsdu' and try again -a On 8 April 2016 at 12:35, Otacílio wrote: > Dears > > I'm testing the CURRENT version on a beaglebone black and have noted the > follow behavior. On revision 297561 the wifi adapter stops works after a pkg > update. I did the follow tests.

Re: WIFI urtwn possibly broken on 297561

The parameter --ff looks like is not valid for my adapter. First I try using prompt: = Edit /etc/motd to change this login announcement. % su Apr 8 05:04:12 beaglebone su: ota to root on /dev/ttyu

Re: WIFI urtwn possibly broken on 297561

Hi, Not '--ff', just '-ff' and '-amsdu' It's possible that one or the other of those options are a problem. I added those features recently to urtwn. Can you please do 'ifconfig -v wlan0 list sta' and 'ifconfig -v wlan0' ? Thanks, -adrian ___ freeb

Re: WIFI urtwn possibly broken on 297561

Em 08/04/2016 17:34, Adrian Chadd escreveu: Hi, Not '--ff', just '-ff' and '-amsdu' It's possible that one or the other of those options are a problem. I added those features recently to urtwn. Can you please do 'ifconfig -v wlan0 list sta' and 'ifconfig -v wlan0' ? Thanks, -adrian Sorry

Re: stall-free memory reads ? (possibly stale) ?

On Fri, Apr 08, 2016 at 06:24:16PM +0200, Luigi Rizzo wrote: > Hi, > I have an application with two threads sharing a memory variable, > one continuously writing, one continuously reading. > > Because of the way my system works, the reader can tolerate reading > stale data, but it should not stal

Re: WIFI urtwn possibly broken on 297561

ok, try "ifconfig wlan0 -ht" before starting wpa_supplicant and see if that makes it any better. You should also include IEEE80211_AMPDU_AGE in your config file if you haven't yet. Also, include IEEE80211_DEBUG in there too, and try "wlandebug +rate +ht" ? -adrian On 8 April 2016 at 13:51, O

Jenkins build is still unstable: FreeBSD_HEAD #171

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is still unstable: FreeBSD_HEAD #172

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"