... I still think the SRV record stuff is a bad idea.
Well, I think it's a great idea - because I plan on supporting it in
the next HTTP thing I write - but not having an A record is going to
continue to bite things.
Also, http+pkg:// isn't a defined protocol either and some strict
proxies may ac
Hi,
Can you please try 10-STABLE or 11-CURRENT? 10-CURRENT indicates that
you're a little behind in the source tree(s).
There's been a bit of work recently that may improve things in general for you.
Thanks!
-a
On 31 October 2013 07:00, Venkata Duvvuru
wrote:
> Hi,
> In Freebsd 10.0-current
Hi,
On 29 October 2013 08:10, Venkata Duvvuru
wrote:
> Hi,
> In Freebsd 10.0-current with Emulex's OCE driver, I observe that the bottom
> half is hogging all the CPU which is leading to system sluggishness. I used
> the same hardware to check the behavior on 9.1-RELEASE, everything is fine,
>
ot of that stuff out
there and right now xorg+console works fine for those.
Thanks,
-adrian
On 25 October 2013 07:18, Aleksandr Rybalko wrote:
> On Fri, 25 Oct 2013 15:10:44 +0100
> symbol...@gmx.com wrote:
>
> > On Fri, Oct 25, 2013 at 06:43:54AM -0700, Adrian Chadd wrote:
&g
lease target.
What do others think?
-adrian
On 25 October 2013 06:39, Aleksandr Rybalko wrote:
> On Fri, 25 Oct 2013 06:29:37 -0700
> Adrian Chadd wrote:
>
> > Erm, I don't think this is really ready for -HEAD yet?
> >
>
> Lets do it "really ready" :)))
Erm, I don't think this is really ready for -HEAD yet?
-adrian
On 25 October 2013 06:04, Aleksandr Rybalko wrote:
> On Fri, 25 Oct 2013 15:18:47 +0300
> Aleksandr Rybalko wrote:
>
> > Hello fellow hackers!
> >
> > I finally reach the point when I can work with newcons instead of
> > syscon
Hi!
Would you please create a PR with the patches attached? That way it's not
lost.
Thanks!
-a
On 24 October 2013 06:56, Alexandre Martins wrote:
> Dear,
>
> We have seen some issues with the VIA VX900 chipset. The main trouble is
> that
> some SATA hard drive are not seen by the kernel (BI
On 23 October 2013 15:31, Vincent Hoffman wrote:
> On 23/10/2013 18:35, Eitan Adler wrote:
>
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd
> wrote:
>
> If there are drivers that people absolutely need fixed then they should
> stand up and say "hey, I really w
Hi,
The later driver model isn't supported by ndisulator. We'd have to
implement all the newer NDIS stuff for wifi and ethernet.
In the later NDIS layer the Microsoft Wireless Services implement a bunch
of stuff that used to be up to the driver. Ie, the driver just exposed an
ethernet "device" wi
And the link momentum is strong now. There's driver source.
Adrian
On Oct 23, 2013 2:41 PM, "John Baldwin" wrote:
> On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote:
> > On 23 October 2013 11:09, Alfred Perlstein wrote:
> >
> >
> > > Eh
Because the Linux stuff is mostly very GPL.
Adrian
On Oct 23, 2013 2:15 PM, "Alfred Perlstein" wrote:
> On 10/23/13 11:11 AM, Adrian Chadd wrote:
>
>> On 23 October 2013 11:09, Alfred Perlstein wrote:
>>
>>
>> Eh, having taken a stab at portin
On 23 October 2013 11:09, Alfred Perlstein wrote:
> Eh, having taken a stab at porting the bwl blob already, I would strongly
>> oppose removing NDIS. If you do that I will just stop using my netbook
>> with a Broadcom part altogether as I wouldn't be able to use it to try to
>> test bwl change
On 23 October 2013 10:40, Allan Jude wrote:
> I think the point Adrian is trying to make, is that the NDISulator needs
> a maintainer, and rather than someone working on that hack, that person
> should spend their time on native drivers.
>
It's partially that.
It's also that a lot of the stuff
Hi!
On 23 October 2013 02:18, Anton Shterenlikht wrote:
> After updating to r256624, the system is very unresponsive,
> and really unusable - any command (ps, df, top, ls, etc.)
> might take up to 1 min to return. However, I could not get
> it to panic.
>
> So I reverted back to r255488.
> This
vers,
> > but that work via NDISulator, we should keep it.
>
> Yes, best keep it while it helps some people.
>
>
> Adrian Chadd wrote:
>
> > It's honestly about time that these were updated, fixed and/or ported to
> > FreeBSD.
> >
> > So, I'm stil
On 21 October 2013 12:59, Andrey V. Elsukov wrote:
> On 19.10.2013 10:01, Thomas Mueller wrote:
> > I too would like to see more effort writing new Ethernet and wifi
> > drivers and porting from other operating systems.
> >
> > But I would like to keep the NDISulator/NDISwrapper as a fallback.
>
I don't know how many times i can say "it needs a maintainer" and "it needs
updating."
So yeah, it needs (a) a maintainer, (b) updating.
-adrian
On 18 October 2013 15:47, Alfred Perlstein wrote:
> On 10/18/13 2:04 PM, Nathan Whitehorn wrote:
>
>> On 10/18/13 16:01, Steve Kargl wrote:
>>
>>
bwn(4) requires a lot more than just an additional PCI ID.
The driver is somewhat architected for all the different RF and PHY modules
that plug into the internal bus (the whole SIBA thing) but it does sorely
need updating.
Thanks,
-adrian
On 18 October 2013 14:04, Nathan Whitehorn wrote:
Hi,
On 18 October 2013 13:53, Steve Wills wrote:
> I would love to have a native driver for this:
>
> none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4
> rev=0x01 hdr=0x00
> vendor = 'Broadcom Corporation'
> device = 'BCM4313 802.11b/g/n Wireless LAN Control
Hi all,
I'd like to remove the NDISulator. I've had many requests to update it to
the latest NDIS version and support more of the 64 bit wifi drivers. But,
to be perfectly honest, I have no desire to keep hacking at this. The world
has changed quite a bit - we can port/reimplement drivers from Lin
On 9 October 2013 11:28, Bruce Cran wrote:
> On 10/9/2013 3:17 PM, Alfred Perlstein wrote:
>
>> Only a few years ago you could take a dvd or memstick of FreeBSD and have
>> 1000s of packages to choose from during your install. That is broken now?
>>
>
> At some point it was decided that the inst
I've iterated my views on these things a few times.
I honestly am not all _that_ interested in trying to build a polished OS.
I'd rather participate in building an OS toolkit that let's PCBSD, pfsense,
"that storage appliance I keep forgetting the name of (heh)", etc all build
OSes on top of it.
I think that's great. But, as we are increasingly finding, theres no stable
ports snapshot, so unless we as a project change how packages are managed,
there may not really be a stable, predictable version of things once
they're moved from base to a package. A number of users and companies like
that
Hi,
Note the noise floor differences.. wonder why that is.
Rui ported the uwrtn stuff, right? He may be able to help. The driver is
recent and its likely there are bugs to shake out.
-adrian
On Oct 8, 2013 2:49 PM, "Julian H. Stacey" wrote:
> > I too am seeing
> > urtwn0: timeout waiting
On 7 October 2013 16:58, Lyndon Nerenberg wrote:
>
> On 2013-10-07, at 4:49 PM, Adrian Chadd wrote:
>
> > I've asked on IRC to figure out when this was first proposed.
>
> Adrian, something to keep in mind is that the majority of your code's
> users will neve
I've asked on IRC to figure out when this was first proposed. I'll see if
it was announced anywhere or if Eitan snuck it in.
-a
On 7 October 2013 16:46, Julian Elischer wrote:
> On 10/8/13 7:37 AM, Adrian Chadd wrote:
>
>> Hi!
>>
>> Then you and others sh
Hi!
Then you and others should stand up and provide feedback like this far, far
earlier in the development process.
If everyone who communicates says "x" and no-one says anything about the
other letters "a"->"w", "y", "z", then we as developers don't really have a
good cross-section of what peopl
.. don't be surprised how many people do exactly this; then compile what
handful of things they need from source in order to make a server.
-adrian
On 7 October 2013 14:53, David Chisnall wrote:
> On 7 Oct 2013, at 22:14, Lyndon Nerenberg wrote:
>
> > "Install from ports" is a non-starter.
drian
On 7 October 2013 13:26, Ian Lepore wrote:
> On Mon, 2013-10-07 at 13:15 -0700, Adrian Chadd wrote:
> > Hi,
> >
> > You should add:
> >
> > *[snip]
> > * a DELAY(1) or something.
> >
>
> Why? Why oh why do people write
>
> while (
Hi,
You should add:
* a loop counter, to break out after a while;
* a DELAY(1) or something.
-adrian
On 7 October 2013 12:54, Zbigniew Bodek wrote:
> Hello.
>
> I would like to present a patch for ns8250 serial that I would like to
> commit in the near future (if there are no objections).
On 17 September 2013 16:22, Ian Lepore wrote:
> On Tue, 2013-09-17 at 14:56 -0700, Adrian Chadd wrote:
> > ... I'd rather see if we can actually separate out things some more so
> > these builds can shrink.
> >
> > Eg, if there's malloc related functi
... I'd rather see if we can actually separate out things some more so
these builds can shrink.
Eg, if there's malloc related functions that aren't used, maybe we should
break malloc down into a directory full of functions.
I'm not surprised libc++ is doing .. that. It's likely better on the
comp
On 16 September 2013 21:01, Garrett Cooper wrote:
> On Sep 16, 2013, at 6:12 PM, Glen Barber wrote:
>
> > On Mon, Sep 16, 2013 at 04:53:14PM -0700, Garrett Cooper wrote:
> >> Can people PLEASE build/test their changes on
> >> and off on multiple VMs?
> >
> > Welcome to the world two weeks after t
... can you post the boot messages?
Can you boot with verbose turned on?
-adrian
On 15 September 2013 22:54, Lundberg, Johannes <
johan...@brilliantservice.co.jp> wrote:
> Hi
>
> Installing current on a MacBook Air 2013 model from USB memstick (special
> build) works fine but booting from th
>
>
> The results are interesting. On amd64:
>
> - devd suddenly becomes 500 KB in size, instead of a megabyte,
> - init's size drops from 900 KB to 600 KB,
> - clang becomes a megabyte smaller.
>
.. so, I'd like to know specific information as to why these three are now
smaller. So what's going o
r-freebsd-m...@freebsd.org [mailto:owner-freebsd-
> > m...@freebsd.org] On Behalf Of Joe Holden
> > Sent: 15 September 2013 23:28
> > To: 'Adrian Chadd'; 'freebsd-current'; freebsd-m...@freebsd.org
> > Subject: RE: how do i cross build world/kernel with clang?
>
[snip]
ok. So I can work around this for these MIPS AP images by echoing something
into /dev/random ?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freeb
Hi!
On 7 September 2013 13:38, Ian Lepore wrote:
> I keep trying to say this, and I keep getting the feeling that it just
> doesn't register with anyone I say it to, like I'm speaking some
> language from another planet or something...
>
> There may be NO entropy of any sort available on an em
On 2 September 2013 09:48, Gary Palmer wrote:
> While not helpful in getting a native driver working, does the device
> work under the NDIS emulation layer with the Windows driver?
>
I don't know. But the wifi NDIS stuff has evolved quite significantly over
the years and I don't know if the ndi
On 2 September 2013 00:47, David Chisnall wrote:
> On 2 Sep 2013, at 03:01, John-Mark Gurney wrote:
>
> > b/crtn.o: warning: linking PIC files with non-PIC files
>
> I think that this is an issue in our import of clang. I'll have to check
> whether I upstreamed the code, but it's basically just
did you contribute this stuff back up to the linux driver?
-adrian
On 31 August 2013 21:30, Jason Birch wrote:
>
> Yup. I hope I get some positive responses from Broadcom. I really don't
>> want to port the Linux driver(s), it's just plain silly.
>>
>
> I've noticed a hell of a lot of problem
Hi!
How do i cross-build a mips world/kernel with clang?
ie, how do I tell the build system to build a mips targetted clang instead
of gcc and use that to build everything?
Thanks,
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.fre
On 31 August 2013 11:44, Lundberg, Johannes wrote:
> Hi Adrian
>
> That's great! Good luck to you :)
>
>
Yup. I hope I get some positive responses from Broadcom. I really don't
want to port the Linux driver(s), it's just plain silly.
-adrian
___
freeb
I've begun trying to hunt down someone at Broadcom to talk about the 11ac
driver.
Wish me luck.
(And install/run FreeBSD on mac hardware..)
-adrian
On 30 August 2013 09:25, Lundberg, Johannes wrote:
> Hi
>
> I thought I'd give a progress report on running FreeBSD 10 on a MacBook Air
> 11"
... well, this is why Peter committed svnlite to -HEAD. To avoid this kind
of not-easy-to-recover-from breakage..
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any ma
.. after tinkering in the USB world, i wonder what's wrong with this:
* created a basic markup / description language to encapsulate what PCI/USB
probing requires;
* generated both config files _and_ .c / .h files for drivers to include;
* have the kernel build process do .device_description -> .c
Hm! Are they dynamically loaded if you insert the cards?
(Ie, has devd been taught about them as appropriate?)
-adrian
On 29 August 2013 02:15, Kimmo Paasiala wrote:
> In reference to this FreeBSD forums post:
>
> http://forums.freebsd.org/showpost.php?p=231135&postcount=4
>
> Would it be a
Hm!
Is there a Linux driver for this SSD? Does Linux approximately boot on this
thing?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
Hihi,
There's two parts to my patch:
* one is migrating the rwlock to rmlock - not because of counters, but
because the lock is protecting consistency when changing the lagg config
* one is adding a new lock specifically to ensure that the callout is
atomically created/called/destroyed
The latte
You know, I could be a total jerk and say:
"If you push gcc out to a port, and you have the 'external compiler'
toolchain support working correctly enough to build with this, why don't we
just push clang out to a port, and be done with it?"
... just saying.
-adrian
.. well, where'd you point it to?
-adrian
On 23 August 2013 23:04, Hideki Yamamoto wrote:
> Hi,
>
> I solved my problem by myself.
> I update PACKAGESITE in /usr/local/etc/pkg.conf in accordance with
> the information in another expert web site.
>
> ---
>
>
>
> 2013/8/24 Hideki Yamamoto
>
>
Sorry, I meant "line contention" rather than "lock contention". Yes, you're
right.
-adrian
On 24 August 2013 07:16, Robert Watson wrote:
> On Sat, 24 Aug 2013, Alexander V. Chernikov wrote:
>
> On 24.08.2013 00:54, Adrian Chadd wrote:
>>
>>>
Hi,
I'd like to commit this to -10. It migrates the if_lagg locking from a rw
lock to a rm lock. We see a bit of contention between the transmit and
receive sides of lagg during traffic loads (10+ gigabit per second.) Using
rmlocks eliminate this.
http://people.freebsd.org/~adrian/netflix/2013081
Hi!
If firewire code doesn't build on clang correctly, have you filed a bug so
it gets looked at before 10.0 is released? that's pretty broken
code/behaviour.
-adrian
On 23 August 2013 04:46, Slawa Olhovchenkov wrote:
> On Fri, Aug 23, 2013 at 06:42:21PM +0800, Julian Elischer wrote:
>
> >
Yes! Please file a PR!
-adrian
On 19 August 2013 12:33, Vitja Makarov wrote:
> Hi!
>
> Recently I was playing with small socket timeouts. setsockopt(2)
> SO_RCVTIMEO and found a problem with it: if timeout is small enough
> read(2) may return before timeout is actually expired.
>
> I was un
Attempt #2:
http://people.freebsd.org/~adrian/netflix/20130816-hwpmc-sbx-1.diff
I've verified that I get counter events from this! But I need to load up a
system more to trigger contention to validate that they're doing the right
thing.
Unfortunately there's an erratum on this which we need to a
Oh, _this_ is the cause! Cool. I wondered about it.
Thanks for chasing this down!
-adrian
On 15 August 2013 11:13, Dimitry Andric wrote:
> On Jul 28, 2013, at 15:15, Dmitry Morozovsky wrote:
> ...
> > on my builder I have consistent error:
> >
> >
> /usr/obj/i386.i386/FreeBSD/pristine/src.
Hm, do we disable building the base with ICONV support in -HEAD?
I'd like to trim it out so I can slim down embedded builds.
Thanks!
-adrian
On 10 August 2013 10:33, Peter Wemm wrote:
> I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2.
>
> https://www.google-melan
Hi,
This (and maybe more?) events are applicable to both the sandy bridge and
sandy bridge xeon CPUs.
This is from the Intel SDM June 2013 Volume #3.
David/Jim, does this look fine to you?
Thanks,
ndex: sys/dev/hwpmc/hwpmc_core.c
===
... bug peter. And alfred. Alfred broke this stuff. :)
-adrian
On 12 August 2013 21:33, Sean Bruno wrote:
> On Mon, 2013-08-12 at 21:36 -0600, Scott Long wrote:
>> On Aug 12, 2013, at 1:43 PM, Sean Bruno wrote:
>>
>> > http://people.freebsd.org/~sbruno/10_i386_vmfault.txt
>> >
>> > I can neve
On 10 August 2013 19:19, AN wrote:
> Hi All:
>
> I am having a major problem on current at the moment, and I could really use
> some help. I am at R253966 on amd64, my problem is the machine is panicing
> with: ffs_valloc: dup alloc
>
> I have booted into single user mode and run fsck, it reports
Hi,
I can reproduce it locally, purely by booting an unchanged amd64 GENERIC.
Are you testing it against an _unmodified_ GENERIC, on amd64?
If it doesn't panic for you but it does panic for me (and I'll go and
get the svn version once I reboot to the old kernel and test) then
there may be a hidd
Try running the svnlite version of svn upgrade.
(svnlite upgrade)
-adrian
On 10 August 2013 07:02, Lev Serebryakov wrote:
> Hello, Freebsd-current.
> You wrote 10 августа 2013 г., 15:18:46:
>
> LS>> Latest revisions of -CURRENT built with "nanobsd" script haven't
> revision
> LS>> in "unam
Hi,
I'll test out the iwn patch, thanks!
-adrian
On 9 August 2013 20:56, Scott Long wrote:
> All,
>
> Subversion rev 250418 affected approximately 63 drivers by making them
> vulnerable to resource allocation failures on motherboards with buggy BIOSes.
> The revision itself is good, but i
t;
> I think since ssh still works, that just the display or graphics port
> is off.
>
> It may be worth trying to do some acpi_calls via ssh to try to hack
> the display back on...
>
> Matt
>
> On 08/09/13 08:57, John Baldwin wrote:
>> On Friday, August 09, 2013 4:37
Hi!
Hm, resurrecting this thread, I'll try this on my X230 tomorrow and
see if it makes the (non-xorg, console only) video work on resume.
If it does, what will it take to automatically determine that this
kind of work-around is needed?
Thanks!
-adrian
On 14 June 2013 16:00, matt wrote:
> O
.. and it's not just about "saturate the port" with traffic.
It's also about "what happens if I shut down the MAC whilst I'm in the
process of programming in new RX/TX descriptors?"
The ath(4) driver had a spectacular behaviour where if you mess things
up the wrong way it will quite happily DMA c
Woo! Tell Jeff! File a PR! Set everything on fire!
-adrian
On 8 August 2013 14:39, Sean Bruno wrote:
> On Thu, 2013-08-08 at 11:30 -0700, Adrian Chadd wrote:
>> Can you go over some previous versions in -HEAD and see when it was
>> introduced?
>>
>>
>>
>
Can you go over some previous versions in -HEAD and see when it was introduced?
-adrian
On 8 August 2013 11:10, O. Hartmann wrote:
> The most recent CURRENT doesn't work with the x11/nvidia-driver (which
> is at 319.25 in the ports and 325.15 from nVidia).
>
> After build- and installworld AND
No, brian said two things:
* the flag, protected by the core lock
* per-queue flags
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubs
.. and I bet it's not a design pattern, and this is total conjecture on my part:
* the original drivers weren't SMP safe;
* noone really sat down and figured out how to correctly synchronise
all of this stuff;
* people did the minimum amount of work to keep the driver from
immediately crashing, bu
5 August 2013 10:13, Navdeep Parhar wrote:
> On 08/05/13 09:15, Luigi Rizzo wrote:
>> On Mon, Aug 5, 2013 at 5:46 PM, Adrian Chadd wrote:
>>
>>> On 5 August 2013 07:59, Bryan Venteicher
>>> wrote:
>>>
>>>> What I've done in my drivers is:
On 5 August 2013 07:59, Bryan Venteicher wrote:
> What I've done in my drivers is:
> * Lock the core mutex
> * Clear IFF_DRV_RUNNING
> * Lock/unlock each queue's lock
.. and I think that's the only sane way of doing it.
I'm going to (soon) propose something similar for cxgbe/ixgbe as we
u
... wait, so the new version of wpa_supplicant takes 10 seconds to
even start doing anything?
Or are the rc scripts to blame?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
I think you were lucky.
dhclient shouldn't start running until wpa_supplicant has completed
authentication.
-adrian
On 29 July 2013 02:59, Lars Engels wrote:
> On Fri, Jul 26, 2013 at 02:34:51PM +0200, Jean-Sébastien Pédron wrote:
>> Hi!
>>
>> At $WORK, we use 802.1X to authenticate computers
Hi all,
I have some reasonably drastic net80211 stack changes planned over the
next few months which require some driver work to make happen. The
specific big change is to call net80211 for each mbuf transmit
completion so it can kick-start the next transmit from a software
staging queue. Since th
I mean, try -10 on it and report back.
-adrian
___
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"
On 25 July 2013 02:51, Wojciech Puchar wrote:
>> improved with a higher kern.hz rating. Unless the future holds an emu20k2,
>> there will be RAM used from the motherboard.
>> 1. I will need a real-time or a faster kernel- hence the high rate wanted-
>> because the devices to be built will be used
Well, why is it reducing latency? That's the thing you should investigate.
Is it because processes aren't getting enough time? or too much time?
Or the audio device isn't getting enough time to run? etc.
-adrian
On 24 July 2013 15:35, Super Bisquit wrote:
> http://lists.freebsd.org/pipermail/
Hi Pedro,
Bapt tells me that there are FUSE issues in the most recent -HEAD and
it's stopping poudriere from running.
What's the story here?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curren
Ok, so.
On 23 July 2013 07:12, Andrey Fesenko wrote:
>>> i'm horrible news, after update my notebook not nave wi-fi :(
>>> full update system, build and install world and kernel.
What did it used to run?
>>> Jul 23 15:34:27 x220 wpa_supplicant[2572]: wlan0: Failed to initiate AP scan
>>> Jul
The ethernet, or wifi, or both?
-adrian
On 23 July 2013 00:26, Sam Fourman Jr. wrote:
> Hello list,
>
> I decided to use a Old Asus Motherboard, for a Router / Firewall
> I decided to use -HEAD to get the latest WIFI support...
>
> I seem to have to ifconfig down and ifconfig up the interfaces
.. are two copies of wpa_supplicant running?
-adrian
On 23 July 2013 06:09, Andrey Fesenko wrote:
> Hello,
> i'm horrible news, after update my notebook not nave wi-fi :(
> full update system, build and install world and kernel.
>
> # uname -a
> FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CUR
Hi,
This patch adds and hw.ixgbe tree and adds rxd/txd. These are already
tunables but it wasn't easy to see if these were being set.
I'd like to commit this soon.
Thanks!
-adrian
adrian@freebsd-10-hack2:~/work/freebsd/head/src/sys/dev/ixgbe % svn diff .
Index: ixgbe.c
===
Hi kib,
Is there a wiki page or some other kind of documentation descibing how
AMT works?
I'd like to set this up at home on some newer machines (read: buy
machines that have this) but I don't know what/where to start.
Thanks!
-adrian
On 22 July 2013 02:51, Konstantin Belousov wrote:
> On S
Hiya,
I'd like to start doing test builds of the mips stuff (specifically
mips4kc, mips24k and mips74k) on freebsd-head with clang/llvm.
What changes are needed to the makefile framework to enable this?
Thanks,
-Adrian
___
freebsd-current@freebsd.org
Hi! Great catch!
Neel - any ideas why this change would stop Joel's machine from
cleanly shutting down?
-adrian
On 21 July 2013 00:20, Joel Dahl wrote:
> On Tue, Jul 16, 2013 at 10:48:35PM +0200, Joel Dahl wrote:
>> Hi,
>>
>> Yesterday I upgraded my Lenovo x220 to the latest current (r253368)
On 17 July 2013 04:26, Andriy Gapon wrote:
> on 16/07/2013 22:40 Adrian Chadd said the following:
>> :( So it's a deadlock. Ok, so what's next?
>
> A creative process...
Wonderful. :)
> One possibility is to add getnewvnode_reserve() calls before the ZFS
>
On 16 July 2013 12:32, Andriy Gapon wrote:
> vmcore.0 was useless for some reason - an interesting address was not
> accessible.
Eek.
> vmcore.1 seems to be very similar and is actually useful.
Oh good.
> This problem looks like an interesting deadlock involving ZFS and VFS and
> vnode
> sh
Guys,
Devin runs a _lot_ of FreeBSD stuff at his work. If anything we as a
community should be making his life easier, not act like he's just
clueless and doing it wrong.
-adrian
On 14 July 2013 16:24, Rainer Duffner wrote:
>
> Am 15.07.2013 um 00:43 schrieb Craig Rodrigues :
>
>> On Sat, Jul
... I bet you could do that. I bet you could build the rpm inside a
linux jail and have the relevant uname bits overridden in the right
way.
-adrian
On 14 July 2013 09:52, Teske, Devin wrote:
>
> On Jul 14, 2013, at 8:01 AM, Chris Rees wrote:
>
>> On 14 Jul 2013, at 08:29, Teske, Devin wrote:
>
On 11 July 2013 07:51, Gleb Smirnoff wrote:
> On Thu, Jul 11, 2013 at 07:45:19AM -0700, Adrian Chadd wrote:
> A> I reference the source/dest FDs in the queue method. Is that not good
> enough?
>
> I see. Should probably work, but needs testing.
It's terrible - I'd
I reference the source/dest FDs in the queue method. Is that not good enough?
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@fr
On 11 July 2013 02:36, Konstantin Belousov wrote:
> No, it is not disk I/O which is problematic there. It is socket I/O
> e.g. wait for the socket buffers lomark in the kern_sendfile() which
> causes unbounded sleep. Look for the sbwait() call, both in the
> kern_sendfile() itself, and in the pru
Hiya,
I'm more interested in the API than the implementation at the moment.
Yes, you're right - it should eventually be driven using disk io
completion upcalls which triggers the push of data into the socket
buffer. I totally agree.
I'm hacking up some libevent-ish looking thing that uses kqueue
On 11 July 2013 00:05, Navdeep Parhar wrote:
> On Wed, Jul 10, 2013 at 10:38:47PM -0700, Adrian Chadd wrote:
>> I don't get why this is dying. any ideas?
>
> Maybe because sparc64's ucontext.h is getting pulled in, and it has
> this:
>
> #define mc_flags
I don't get why this is dying. any ideas?
adrian
On 10 July 2013 21:18, FreeBSD Tinderbox wrote:
> TB --- 2013-07-11 02:56:02 - tinderbox 2.10 running on
> freebsd-current.sentex.ca
> TB --- 2013-07-11 02:56:02 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
> FreeBSD 8.3-PRERELEASE #0: M
Hiya,
I've started writing an aio_sendfile() syscall.
http://people.freebsd.org/~adrian/ath/20130710-aio-sendfile-3.diff
Yes, the diff is against -HEAD and not stable/9.
It's totally horrible, hackish and likely bad. I've only done some
very, very basic testing to ensure it actually works; i ha
I still get issues with latest stable/9 and panics during or just
after a bunch of disk IO.
I can try to reproduce this if you'd like.
-adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
On 9 July 2013 23:27, Andriy Gapon wrote:
> on 09/07/2013 16:03 Adrian Chadd said the following:
>> Does anyone have any ideas as to what's going on?
>
> Please provide output of 'thread apply all bt' from kgdb, then perhaps someone
> might be able to tell.
601 - 700 of 1259 matches
Mail list logo
