Can someone please take care of this? I'm a little busy for the next
couple days.
Feel free to commit to the contrib code.
Thanks!
-adrian
On 8 November 2013 07:24, Dimitry Andric wrote:
> On 08 Nov 2013, at 16:08, Adrian Chadd wrote:
>> On 8 November 2013 02:32, FreeBSD Ti
On 9 November 2013 16:05, Daniel O'Connor wrote:
>
> On 10 Nov 2013, at 24:24, Matthew Seaman wrote:
>>
>> 2) Should ports / packages populate these cron.d directories?
>>
>> This is a much more interesting question. Effectively its asking
>> if a port / package should provide some
On 9 November 2013 16:28, Allan Jude wrote:
> Well, what about making these extra directories optional then?
>
> packages install the crontab entries, but crond ignores them unless you add:
>
> cron_flags="--scandir /etc/cron.d --scandir /usr/local/etc/cron.d"
>
> or something to that effect
>
>
On 9 November 2013 17:40, Allan Jude wrote:
> On 2013-11-09 20:05, Adrian Chadd wrote:
>> On 9 November 2013 16:28, Allan Jude wrote:
>>
>>> Well, what about making these extra directories optional then?
>>>
>>> packages install the crontab entr
On 9 November 2013 17:58, Allan Jude wrote:
> Well, if the rc.conf config is specific to the daemon being installed by
> the package, then the existing /etc/rc.conf.d/ system works fine, it
> just falls down a little on xorg configuring hald, unless you just make
> the xorg package create /etc/rc
Hi!
On 9 November 2013 18:29, Brandon Gooch wrote:
> Turns out that not enabling MRR causes my Intel Ultimate N WiFi Link
> 5300 to hang after only a few moments of use.
That's .. odd. Ok.
> For now, I've just reverted only those aspects of r257133, enabling
> MRR and keeping the rate index loo
Sure, flip on 'wlandebug +rate' (assuming you compiled with IEEE80211_DEBUG)
-a
On 9 November 2013 21:08, Brandon Gooch wrote:
> On Sat, Nov 9, 2013 at 8:46 PM, Adrian Chadd wrote:
>> Hi!
>>
>> On 9 November 2013 18:29, Brandon Gooch wrote:
>>> Turns o
Oh, and you need to print out the tx->rate field using "0x%04x",
rather than %d. The completion value is in hex.
-adrian
On 9 November 2013 22:18, Adrian Chadd wrote:
> Sure, flip on 'wlandebug +rate' (assuming you compiled with IEEE80211_DEBUG)
>
>
> -a
&g
yup, same info as brandon. :)
-a
On 10 November 2013 04:17, Stefan Farfeleder wrote:
> On Sat, Nov 09, 2013 at 08:29:30PM -0600, Brandon Gooch wrote:
>> Turns out that not enabling MRR causes my Intel Ultimate N WiFi Link
>> 5300 to hang after only a few moments of use.
>>
>> For now, I've just
etting 'linkq' to start at the selected rate, as
linkq is an index into that table, not the initial rate.
Thanks!
-adrian
On 10 November 2013 08:33, Stefan Farfeleder wrote:
> On Sun, Nov 10, 2013 at 05:14:58AM -0800, Adrian Chadd wrote:
>> yup, same info as brandon. :)
>
And for reference, here's the paper:
http://hal.inria.fr/docs/00/07/07/84/PDF/RR-5208.pdf
-adrian
On 10 November 2013 10:48, Adrian Chadd wrote:
> Right near the end there you have 'status 83' which means 'transmit
> failed, long retry hit' (the status codes
te retry once the new hardware support is in. I would
really appreciate help here with these. Everyone with iwn hardware will
appreciate it :)
Thanks,
Adrian
Adrian
On Nov 10, 2013 11:34 AM, "Stefan Farfeleder" wrote:
> On Sun, Nov 10, 2013 at 10:48:48AM -0800, Adrian Chadd w
Hi!
Your patch does three things:
* adds a couple new buckets;
* reduces some lock contention
* does the aggressive backpressure.
So, do you get any benefits from just the first one, or first two?
-adrian
On 17 November 2013 15:09, Alexander Motin wrote:
> Hi.
>
> I've created patch, base
On 18 November 2013 01:20, Alexander Motin wrote:
> On 18.11.2013 10:41, Adrian Chadd wrote:
>>
>> Your patch does three things:
>>
>> * adds a couple new buckets;
>
>
> These new buckets make bucket size self-tuning more soft and precise.
> Without
Remember that for Netflix, we have a mostly non-cachable workload
(with some very specific exceptions!) and thus we churn through VM
pages at a presitidigious rate. 20gbit sec, or ~ 2.4 gigabytes a
second, or ~ 680,000 4 kilobyte pages a second. It's quite frightening
and it's only likely to increa
[snip]
wiki.freebsd.org/FreeBSD/mips has links to the MIPS emulator setups.
There's no excuse to avoid testing on MIPS. :-)
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
r258446 built, installed and booted fine. I'll try a more recent i386
in a chroot soon.
Would someone please double-check -HEAD on i386 and see if it's ok?
Thanks,
-adrian
On 21 November 2013 19:23, Adrian Chadd wrote:
> hi,
>
> I just updated a laptop from a month old
On 22 November 2013 01:11, Andreas Tobler wrote:
> - Original Message
> From: Adrian Chadd
> To: freebsd-current
> Subject: Re: i386 update to latest -HEAD broke things
> Date: 22/11/13 10:05
>
>> r258446 built, installed and booted fine. I'll t
hi,
I just updated a laptop from a month old -HEAD to the latest -HEAD.
Things .. didn't work.
* No processes ran - they'd complain about being out of anonymous memory
* /rescue/sh works fine, but /rescue/dhclient seems to be doing the
wrong thing with regards to which dhclient-script it calls
*
Hi,
Here's part #2 in my sendfile refactoring. This is a little more
intrusive than the first patch.
http://people.freebsd.org/~adrian/netflix/20131126-sendfile-sync-refactor-2.diff
My aim here is to move the sendfile_sync stuff out of uipc_syscalls.c
and out of sendfile-only code and into somet
Hi,
It's definitely a work in progress, as you've observed.
On 28 November 2013 00:20, Konstantin Belousov wrote:
> On Wed, Nov 27, 2013 at 11:36:44AM -0800, Adrian Chadd wrote:
>> Hi,
>>
>> Here's part #2 in my sendfile refactoring. This is a little mo
hi all,
I'd like a developer or two to organise the MFC of anything that's in
net80211 on -HEAD back to -10 before 10.0-REL.
There's a few critical fixes that need to go in but I just don't have
the time to do it myself. :(
Thanks!
-adrian
___
free
On 28 November 2013 19:04, Glen Barber wrote:
> On Thu, Nov 28, 2013 at 06:54:56PM -0800, Adrian Chadd wrote:
>> I'd like a developer or two to organise the MFC of anything that's in
>> net80211 on -HEAD back to -10 before 10.0-REL.
>>
>> There's a few cr
Sure, is there a TCP version of this patch floating around? How's it
doing load balancing to multiple listeners?
-a
On 29 November 2013 11:28, Oleg Moskalenko wrote:
> It would be nice to have this feature compiled and supported in FreeBSD
> kernel by default.
>
> Thanks
> Oleg
>
>
> On Fri, No
The reason I wouldn't implement this is to avoid having code that
_relies_ on this behaviour in order to function or perform well.
Heck, it may not even be portable to other operating systems. Except,
Linux, I guess.
-adrian
___
freebsd-current@freebsd
+1, this caught us out with sendfile testing very recently :(
-a
On 30 November 2013 05:56, Konstantin Belousov wrote:
> I propose to unconditionally add the switch -fno-strict-overflow to the
> kernel compilation. See the patch at the end of message for exact change
> proposed.
>
> What does
On 30 November 2013 15:25, Dimitry Andric wrote:
> On 30 Nov 2013, at 14:56, Konstantin Belousov wrote:
>> I propose to unconditionally add the switch -fno-strict-overflow to the
>> kernel compilation. See the patch at the end of message for exact change
>> proposed.
>>
>> What does it do. It d
Hi! Thanks for the writeup!
On 1 December 2013 20:17, Sepherosa Ziehau wrote:
> I also put up a brief description of SO_REUSEPORT in dfly; may be useful to
> you:
> http://leaf.dragonflybsd.org/~sephe/netisr_so_reuseport.txt
Ok, so given this, how do you guarantee the UTHREAD stays on the given
On 2 December 2013 03:45, Sepherosa Ziehau wrote:
>
> On Mon, Dec 2, 2013 at 1:02 PM, Adrian Chadd wrote:
>
>> Ok, so given this, how do you guarantee the UTHREAD stays on the given
>> CPU? You assume it stays on the CPU that the initial listen socket was
>> created
I was thinking of n netisrs per m CPUs, where n < m; or maybe 1 netisr
for m CPUs, where m is less than the total number.
Having 48 cores contending on netisr stuff is a bit crazy. It's highly
unlikely you need that many cores doing packet pushing.
-a
A lot of work has gone on in -current with the iwn driver. It's quite
possible that the recent changes has broken things.
Would you please do this:
* recompile with IWN_DEBUG defined in your kernel cofig
* sysctl dev.iwn.0.debug=0x13ff
(That turns on command debugging, tx/rx debugging, interrupt
fixed before we consider a merge back.
Thanks,
-a
On 7 December 2013 06:03, Matthias Petermann wrote:
> Hello Adrian,
>
> Am 04.11.2013 06:59, schrieb Adrian Chadd:
>> [snip]
>>
>> For what it's worth, I've started merging this stuff into -HEAD.
>>
ssign requested address
> Dec 8 11:11:54 x201i wpa_supplicant[10682]: ioctl[SIOCS80211, op=103,
> val=0, arg_len=128]: Device not configured
> Dec 8 11:11:54 x201i wpa_supplicant[10682]: wlan0: Failed to initiate AP
> scan
> Dec 8 11:11:55 x201i dhclient[10805]: send_packet: Invalid argum
Which svn rev introduced the regression?
-a
On 8 December 2013 10:19, Olivier Cochard-Labbé wrote:
> On Sun, Dec 8, 2013 at 6:31 PM, Stefan Hegnauer
> wrote:
>> Hi,
>>
>>
>> Since late summer - sorry, no exact date / svn revision - nanobsd.sh fails
>> at the last stage when building the disk i
OK, I'll see if my centrino 1xx / 1xxx units match yours and are problematic.
Please file a PR!
-a
On 7 December 2013 05:34, 乔楚 wrote:
> Today ,I upgrade my freebsd from 10-beta4 to current.
> Now, my freebsd can't connect to wireless AP. Wireless LAN strike.
>
> iwn0 in /var/log/message:
> De
Hi,
I'd like to start committing this to FreeBSD-HEAD:
http://people.freebsd.org/~adrian/netflix/20131211-sendfile-kqueue-11.diff
It implements kqueue notifications for sendfile so users can get an
asynchronous notification that the underlying mbufs have been freed.
This allows userland users of
And yes, I know this breaks the 32 bit compat sendfile call. I'm
thinking of how to fix this without just duplicating all of that code.
Thanks,
-a
On 12 December 2013 12:41, Adrian Chadd wrote:
> Hi,
>
> I'd like to start committing this to FreeBSD-HEAD:
>
> http://p
Are you able to make it do delayed firmware loading?
Adrian
On Dec 13, 2013 3:23 AM, "Jean-Sébastien Pédron"
wrote:
> On 10.12.2013 12:21, Markiyan Kushnir wrote:
> > Hello,
>
> Hi!
>
> First, a quick note: freebsd-current@ and current@ are the same list.
>
> > There seems to be a difference in
My bad, lemme go figure out what the hell causes this to break on
these platforms.
-a
On 16 December 2013 17:34, FreeBSD Tinderbox wrote:
> TB --- 2013-12-16 22:00:19 - tinderbox 2.20 running on
> freebsd-current.sentex.ca
> TB --- 2013-12-16 22:00:19 - FreeBSD freebsd-current.sentex.ca 8.3-PR
Hi,
The MAC of the lagg needs to be the same as the wireless interface.
I'm going to just state right now that using lagg as the failover
method for doing wireless/wired integration isn't supported by me. If
someone wants to make it supported then they need to claim it. :)
-a
On 17 December 2
I'm the wireless stack maintainer and I currently don't support that.
Sorry.
-a
On 17 December 2013 08:10, dan_partelly wrote:
> On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd
> wrote:
>> Hi,
>
> All 3 MACs are the same. wpi0 is set to the MAC of bg0. Wlan0
On 17 December 2013 08:12, Nikolai Lifanov wrote:
> Also, this method is still described in the handbook:
> https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-lagg-wired-and-wireless
>
> If this isn't supposed to work, then the handbook needs to be updated.
I'd be really ha
Ive no idea sorry. Its likely an ifnet change and not anything WiFi
specific. :(
On Dec 17, 2013 12:04 PM, "dan_partelly" wrote:
>
> Yes, this is correct. A simple list of the interfaces with ifconfig
> makes the system recover and restart activity on the secondary port.
> Its a good starting poi
I'm rapidly wondering if building this way should become unsupported. Too
muxh unknown stuff is needed at startup and wed have to load all firmware
bits to make it remotely work.
On Dec 17, 2013 2:08 PM, "Steve Kargl"
wrote:
> On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
> >
>
[snip]
So the standard trop of UNLOCK/WORK/RELOCK is pretty dangerous.
There's no state re-validation going on when you re-acquire that lock.
So, although it meets the lock requirements, it may not be 'correct'.
It's scattered throughout the code base (wifi drivers aren't an
exception here either
What's at frame 10?
And list the IP, ie:
list *0x817da911
-a
On 18 December 2013 23:04, Sergey V. Dyatko wrote:
> Hi,
>
> I have following setup:
>
> wlans_ral0="wlan0"
> ifconfig_wlan0="WPA"
>
> cloned_interfaces="lagg0 bridge0 tap0"
> ifconfig_lagg0="laggproto failover laggport alc0
Would you mind filing a PR?
-a
On 18 December 2013 09:27, Kurt Lidl wrote:
> A while ago, it was reported that the ISO images that FreeBSD generates
> have a variety of problems (thread starts here):
>
> http://lists.freebsd.org/pipermail/freebsd-stable/2013-April/073050.html
>
> And again for t
Well there's a null node pointer. Need to figure out why. Its totally legit
to have them too, so the code has to cope.
Grr.
Adrian
On Dec 19, 2013 2:07 AM, "Sergey V. Dyatko" wrote:
> On Wed, 18 Dec 2013 23:40:23 -0800
> Adrian Chadd wrote:
>
> > What's a
so appreciated.
Have a read of the FreeBSD handbook:
https://www.freebsd.org/doc/handbook/
And if you have questions about the networking side of things, please
don't hesitate to email the list(s). We can turn whatever
question/answers you have into a chapter or two in the handbook.
-a
Hi,
Please file a PR and then ask the developer (pjd@) very nicely to take
a look at it.
Thanks,
-adrian
On 20 December 2013 12:45, Stefan Hegnauer wrote:
> When using 'WITHOUT_CAPSICUM=YES', 'WITHOUT_CASPER=YES' my nanobsd builds in
> a Virtualbox VM (i386, march=geode, GENERIC without debu
The point is that some people like an audit trail. The audit trail for
some people involves remote logging of syslog messages to a log host.
This would include when packages are installed.
-adrian
On 21 December 2013 15:49, Steve Kargl
wrote:
> On Sat, Dec 21, 2013 at 06:47:01PM -0500, Glen Ba
Hm! Cool! I'll give this a spin tomorrow on my
frequently-very-lock-busy boxes and get back to you.
-a
On 23 December 2013 09:52, Rang, Anton wrote:
> The HWPMC hooks are never invoked except when using the soft PMC feature for
> performance monitoring. This trivial patch hints as much to the
On 24 December 2013 12:41, wrote:
> John Baldwin wrote, On 12/23/2013 17:50:
>
>> It needs fixing, but the fix needs to be correct.
>
>
> Though a fix should not be delayed by decades...
THe problem here is that a lot of people (and no offence to the patch
author or other developers!) just go "U
Hi,
I just fixed the Intel 6150 support. I'm emailing this from said Intel 6150.
Please update to the very latest -HEAD and try!
Thanks!
-a
On 22 December 2013 06:25, Hannes Mehnert wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA384
>
> Hi,
>
> I'm running current and iwn fails to
On 17 December 2013 22:41, wrote:
> Jean-Sébastien Pédron wrote, On 12/17/2013 22:20:
>
>> On 16.12.2013 08:36, d...@gmx.com wrote:
>>>
>>> Still nobody wants to apply Robert Noland's DRM patch?
>>
>>
>> What problem(s) does this patch fix?
>
>
> It fixes non-deterministic lockups when the (old,
On 30 December 2013 16:32, wrote:
>
>
> Oops, I meant panics, not lockups. The kernel panics exactly because -- as I
> gather -- the assertions are already there.
>
> There are lockup issues even with the patch applied (for the most part, only
> when using, in Xorg.conf: Option "AccelMethod" "EXA
Hi!
Would you mind a recent 11-amd64 snapshot? Hans has committed a few
fixes to the driver recently.
Thanks!
-a
On 5 January 2014 19:01, Huang Wen Hui wrote:
> Hi,
>
> I am trying to install FreeBSD on MacBookPro Late 2013, I got 3 main
> problems:
>
> 1. USB problem
>
> This MacBookPro mod
That just adds the IDs, it doesn't add the support code. :(
-a
On 5 January 2014 20:50, 乔楚 wrote:
> I found there have patchs for Haswell which posted by Neel Chauhan.
>
> http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044727.html
> http://lists.freebsd.org/pipermail/freebsd
.. are you getting this USB_ERR_TIMEOUT even with the xhci code from -9?
-a
On 5 January 2014 23:10, Hans Petter Selasky wrote:
> On 01/06/14 05:11, Huang Wen Hui wrote:
>>
>> Hi,
>>
>> USB still have a lot of USB_ERR_TIMEOUT, but Internal keyboard and
>> external keyboard found and works!
>>
Right, but it used to work. That's the confusing bit. How'd you make
it not work? :)
-a
On 6 January 2014 01:52, Hans Petter Selasky wrote:
> On 01/06/14 10:41, Huang Wen Hui wrote:
>>
>> % grep xhci dmesg-xhci-debug.txt | more
>> xhci0: mem 0xc1e0-0xc1e0 at
>> device 20.0 on pci0
>> x
It's likely used elsewhere; it's the kind of thing you abuse when
doing header rewriting and reinjection. So, what's the NAT and such
code using?
-a
On 9 January 2014 11:21, Luigi Rizzo wrote:
> a lot of arch-specific headers (sys/${ARCH}/include/in_cksum.h)
> have a lengthy definition for
>
>
Just try copying the whole iwn driver from -head to -10.
-a
On 12 January 2014 05:27, Oliver Pinter wrote:
> Hi all!
>
> I got this firmware crash with 10-STABLE + backported iwn patches from
> CURRENT:
>
> iwn0: device timeout
> wlan0: link state changed to UP
> wlan0: link state changed to D
On 15 January 2014 03:34, Gleb Smirnoff wrote:
[snip]
> Damn, what a mess. I'd like to go towards absolutely unmodified packets
> for the 11-release cycle.
Well, now's the time to _start_ this. :-) Not 6 months before 11.0 :P
-a
___
freebsd-current@
It's actually fpu code in ndis drivers. I'm going to deprecate NDIS
this year, so ..
OTOH, the FPU save support would be cool.
-a
On 22 January 2014 20:10, Miguel Clara wrote:
> Getting a panic: Unregistered use of FPU in kernel
>
>
> There seems to be a patch for FreeBSD 10, but not sure if
t; Hi Adrian, when you say "I'm going to deprecate NDIS", does this also
> mean there a change to have this driver working without ndis in
> freebsd?
>
> I tried
> kldload if_bwi
> kldload if_bwn
>
> But none of them work for 4313 it seems! :(
>
> On Thu,
... who's the author of this? Why aren't they posting updates to
FreeBSD-HEAD so it can be included in the base system?
Does anyone have a contact email for the author, Vadislav?
-a
On 24 January 2014 03:52, Thomas Mueller wrote:
> To Miguel Clara, you might try a USB wireless adapter. I use
On 24 January 2014 08:47, Vlad Movchan wrote:
> NDISulator on github (and mirror on gitorious) is a FreeBSD ndis
> module+binaries forked by Paul B. Mahol in 2009 (I've sent Paul's email
> address privately to Adrian).
> Almost every change in this project was made by Paul.
> My part is small - I'
Oh! The NDIS FPU patch is limited to the NDIS module.
Tell you what, I'll get that committed to -HEAD soon. Would you poke
the original author and see if he's willing to work with you and I on
getting this stuff into -HEAD?
-a
___
freebsd-current@free
Hi,
This doesn't compile on i386. Would you mind figuring out why that is
and submitting a patch that compiles on both amd64 and i386?
Thanks!
-a
On 24 January 2014 12:11, Vlad Movchan wrote:
>
> On Fri, Jan 24, 2014 at 8:16 PM, Adrian Chadd wrote:
>>
>>
>> Is
> On Tue, Jan 28, 2014 at 2:38 AM, Adrian Chadd wrote:
>>
>> Hi,
>>
>> This doesn't compile on i386. Would you mind figuring out why that is
>> and submitting a patch that compiles on both amd64 and i386?
>>
>> Thanks!
>>
>>
>> -a
&
holy crap, cool!
Hans? Any chance we could get this into -HEAD?
-a
On 28 January 2014 17:43, Huang Wen Hui wrote:
> Hi,
> I have a working trackpad driver for my MBP 2013, I am not C programmer
> usually,
> so the code may ugly. If someone like to test, you can download it from
> http://sw.
Hi guys,
I'm running up to date -HEAD (from Jan 26) on a Lenovo T400 with:
vgapci0@pci0:0:2:0: class=0x03 card=0x20e417aa chip=0x2a428086
rev=0x07 hdr=0x00
vendor = 'Intel Corporation'
device = 'Mobile 4 Series Chipset Integrated Graphics Controller'
class = displ
On 29 January 2014 13:51, Colin Percival wrote:
> On 01/29/14 12:51, Lars Engels wrote:
>> On Sat, Jan 25, 2014 at 09:11:04AM -0600, Mark Felder wrote:
>>> On Sat, Jan 25, 2014, at 5:32, Lars Engels wrote:
Also using freebsd-update behind a proxy is really slow. Even with a
very fast int
So now that i have everything else working on this x230, I'm taking a
fresh look at the acpi brightness support.
I'm in the same boat - only PEG works. But I have integrated graphics
only, rather than both integrated and nvidia graphics.
A cursory reading of the linux acpi and video / video-detec
[snip]
My experiences with newcons/drm2:
* suspend/resume occasionally throws up a panic in the softclock code,
with some vaguely invalid looking newcons timer entry. THis happens
after it comes out of suspend, after af ew seconds. It sucks and makes
things rather unusable.
* Occasionally a resum
Yeah, we need:
* usb fixed up
* bootloader (loader) needs more ram, as it runs out of memory trying
to read in the kernel - seabios unfortunately lies about how much is
actually there
* graphics - haswell, right?
* atkbd patches
* mouse / i2c bus driver ported over
The wifi, works great.
-a
On
eone to test this patch. The issue of problem has been identified
> thanks to Mattew Dillon at DragonFlyBSD.
>
>
> On 02/12/14 08:51, Adrian Chadd wrote:
>>
>> Yeah, we need:
>>
>> * usb fixed up
>
>
> http://svnweb.freebsd.org/changeset/base/261795
On 12 February 2014 04:30, Matthias Apitz wrote:
> El día Wednesday, February 12, 2014 a las 12:48:31AM -0800, Adrian Chadd
> escribió:
>
>> I have one of these, but I haven't yet sat down to try freebsd-head
>> again. The default problems with the bootloader sucks.
>
On 17 February 2014 03:32, Gleb Smirnoff wrote:
> On Mon, Feb 17, 2014 at 11:24:21AM +, David Chisnall wrote:
> D> > Now for the new sendfile. The core idea is that sendfile()
> D> > schedules the I/O, but doesn't wait for it to complete. It
> D> > returns immediately to the process, and I/O
On 18 February 2014 10:28, John Baldwin wrote:
> On Monday, February 17, 2014 6:24:21 am David Chisnall wrote:
>> P.S. If aio() is creating a new thread per request, rather than scheduling
> them from a pool, then that is also likely a bug. The aio APIs were designed
> so that systems with DMA co
..blah, the "filesystem code is all blocking.."
-a
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Hi,
This patch binds the per-CPU timeout swi threads to the CPU they're on.
The scheduler may decide that a preempted kernel thread that's still
runnable and this can happen during things like per-CPU TCP timers
firing.
Thanks,
Index: sys/kern/kern_timeout.c
Hi,
This patch adds callgraph annotation to pmcstat via -a. It doesn't
(yet) add line numbers; I'll see if I can easily add that without too
much effort.
This is like (and based on) the -m option but the -m option only
prints the first entry in the callgraph. It isn't very useful if you
want to s
.. and now with file:line information:
http://people.freebsd.org/~adrian/netflix/20140218-pmcstat-callgraph-annotate-2.diff
It doesn't yet correctly handle klds - the address calculation stuff
isn't taking the load addr into account.
-a
___
freebsd-cu
On 19 February 2014 11:40, Alexander Motin wrote:
> Hi.
>
> Clock interrupt threads, same as other ones are only softly bound to
> specific CPUs by scheduler preferring to run them on CPUs where they are
> scheduled. So far that was enough to balance load, but allowed threads to
> migrate, if need
On 19 February 2014 11:59, Alexander Motin wrote:
>> So if we're moving towards supporting (among others) a pcbgroup / RSS
>> hash style work load distribution across CPUs to minimise
>> per-connection lock contention, we really don't want the scheduler to
>> decide it can schedule things on othe
On 19 February 2014 14:09, Alexander Motin wrote:
> On 19.02.2014 23:44, Slawa Olhovchenkov wrote:
>>
>> On Wed, Feb 19, 2014 at 11:04:49PM +0200, Alexander Motin wrote:
>>
>>> On 19.02.2014 22:04, Adrian Chadd wrote:
>>>>
>>>> On 19 February
On 20 February 2014 11:17, John Baldwin wrote:
> (A further variant of this would be to divorce cpu0's swi from the
> catch-all softclock and let the catch-all softclock float, but bind
> all the per-cpu swis)
I like this idea. If something (eg per-CPU TCP timers, if it's turned
on) makes a very
On 21 February 2014 20:59, Allan Jude wrote:
> I can see the remote controlled installer being especially useful for
> 'appliance' type devices, like FreeNAS, pfSense, FUDO, etc.
>
> How would your phone find the address of the machine once it boots off
> the USB, so you could access the web serv
Hi,
Please file PRs for these. The author is quite prompt at fixing these issues.
-a
On 22 February 2014 15:05, Matthew Rezny wrote:
>> Hello,
>>
>> Unfortunately, this is the case with *zips from Dropbox (Download
>> as .zip) directory option.
>>
>> $ /usr/bin/unzip file.zip
>> Archive: fi
Hi,
Yeah, there's likely something missing. But I just at the moment have
no time to debug this.
-a
On 26 February 2014 04:37, Tom Murphy wrote:
> Hi all,
>
> I compiled a fresh kernel from -HEAD and rebooted in the hope that my
> laptop's wifi would now be supported (I saw the commit messa
a connection. It situation 100% reproducible in 11n mode,
> but in 11g works fine.
>
> http://docs.freebsd.org/cgi/mid.cgi?5304B48E.8070404
>
> 26.02.2014 17:09, Adrian Chadd пишет:
>> Hi,
>>
>> Yeah, there's likely something missing. But I just at the moment ha
On 26 February 2014 23:52, Alexandr wrote:
> Tom, could you:
>
> 1. compile kernel WITH_IWNDEBUG
> 2. sysctl dev.iwn.0.debug=0x1
> 3. wlandebug -i wlan0 auth+assoc
> 4. Associate with AP in 11n mode
> 5. Send us appropriate /var/log/messages
>
> Then I try to compare it with my log.
Please do. I'
Hi,
Yes there are issues; I'm too busy to try and chase them down.
I'd appreciate some help in chasing down why things are unhappy.
Thanks,
-a
On 27 February 2014 17:17, Kaho Toshikazu wrote:
> Hello, -current members
>
> I have a similar problem with Centrino Wireless-N 1000.
> It ope
Hi,
On my i386 -HEAD laptops (running -HEAD as of last night, but it's
been a problem for a while) I occasionally hit a point where I get an
FPE on _all_ processes upon resume.
I can still do a clean shutdown through the power-button method, but I
can't do anything else.
Has anyone seen this bef
y iwn debug messages to this email starting
> with the point I tried to associate to the Wifi.
>
> Thanks again for looking at this!
>
> Kind regards,
> Tom
>
> On Thu, Feb 27, 2014 at 12:13:51PM -0800, Adrian Chadd wrote:
>> On 26 February 2014 23:52, Alexandr wro
... how'd this ever work in the past then?
-a
On 28 February 2014 13:08, John Baldwin wrote:
> On Friday, February 28, 2014 1:15:45 pm Adrian Chadd wrote:
>> Hi,
>>
>> On my i386 -HEAD laptops (running -HEAD as of last night, but it's
>> been a problem fo
On 28 February 2014 15:35, Adrian Chadd wrote:
> ... how'd this ever work in the past then?
>
.. and I've submitted it as a PR:
kern/187152
Thanks,
-a
>
> -a
>
>
> On 28 February 2014 13:08, John Baldwin wrote:
>> On Friday, February 28, 2014
ch 2014 11:11, John Baldwin wrote:
> On Friday, February 28, 2014 9:00:57 pm Adrian Chadd wrote:
>> On 28 February 2014 15:35, Adrian Chadd wrote:
>> > ... how'd this ever work in the past then?
>> >
>>
>> .. and I've submitted it as a PR:
>>
Have you filed a PR? :-P
-a
On 3 March 2014 14:09, Craig Rodrigues wrote:
> [Resending]
>
>
> Hi,
>
> As part of the Jenkins deployment in the FreeBSD cluster
> the jenkins-admin team observed that when running Jenkins on FreeBSD 10,
> the Java virtual machine from the openjdk6 or openjdk7 por
801 - 900 of 1259 matches
Mail list logo
