Hi!
On 23 October 2013 02:18, Anton Shterenlikht me...@bris.ac.uk 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
On 23 October 2013 10:40, Allan Jude free...@allanjude.com 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
On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org 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
Because the Linux stuff is mostly very GPL.
Adrian
On Oct 23, 2013 2:15 PM, Alfred Perlstein bri...@mu.org wrote:
On 10/23/13 11:11 AM, Adrian Chadd wrote:
On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org wrote:
Eh, having taken a stab at porting the bwl blob already, I would
And the link momentum is strong now. There's driver source.
Adrian
On Oct 23, 2013 2:41 PM, John Baldwin j...@freebsd.org wrote:
On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote:
On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org wrote:
Eh, having taken a stab
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
On 23 October 2013 15:31, Vincent Hoffman vi...@unsane.co.uk wrote:
On 23/10/2013 18:35, Eitan Adler wrote:
On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd adr...@freebsd.org
adr...@freebsd.org wrote:
If there are drivers that people absolutely need fixed then they should
stand up and say
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 alexandre.mart...@netasq.comwrote:
Dear,
We have seen some issues with the VIA VX900 chipset. The main trouble is
that
some SATA hard drive are
Erm, I don't think this is really ready for -HEAD yet?
-adrian
On 25 October 2013 06:04, Aleksandr Rybalko r...@freebsd.org wrote:
On Fri, 25 Oct 2013 15:18:47 +0300
Aleksandr Rybalko r...@ddteam.net wrote:
Hello fellow hackers!
I finally reach the point when I can work with
target.
What do others think?
-adrian
On 25 October 2013 06:39, Aleksandr Rybalko r...@freebsd.org wrote:
On Fri, 25 Oct 2013 06:29:37 -0700
Adrian Chadd adr...@freebsd.org wrote:
Erm, I don't think this is really ready for -HEAD yet?
Lets do it really ready :)))
I'am free on that, I
there and right now xorg+console works fine for those.
Thanks,
-adrian
On 25 October 2013 07:18, Aleksandr Rybalko r...@freebsd.org 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:
3) Realise it's not yet ready
Hi,
On 29 October 2013 08:10, Venkata Duvvuru
venkatkumar.duvv...@emulex.com 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
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
venkatkumar.duvv...@emulex.com wrote:
... 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
On 1 November 2013 08:45, hiren panchasara hiren.panchas...@gmail.com wrote:
On Fri, Nov 1, 2013 at 8:32 AM, Matthias Apitz g...@unixarea.de wrote:
Hello,
Since I have updated my netbook to r255948 I see from time to time in
the console the message:
Nov 1 16:20:28 tiny-r255948
Hi!
I have an odd problem. That, honestly, can't be that odd.
I have a bunch of SATA disks that when plugged into the laptop
directly, show up as 512 byte sectors. But if I plug it in via this
iomega USB caddy, they show up as 4k sector devices.
Because of this, partitions just plainly don't
On 2 November 2013 05:28, Matthew Seaman matt...@freebsd.org wrote:
I feel no obligation to do anything to encourage people that
deliberately break the DNS. They've made their bed, and now they have
to lie in it.
Holy, holy crap.
* We (as FreeBSD) are not big enough to dictate the
On 2 November 2013 10:44, Mark Felder f...@freebsd.org wrote:
But SRV has been widely deployed since… before 2000? It’s literally the
backbone of Active Directory deployments. Here’s a list of things that his
company’s network design probably breaks:
* Office 365 (cloud Exchange hosting by
[snip]
For what it's worth, I've started merging this stuff into -HEAD.
I'm going to merge in the hardware updates but none of the PAN stuff this pass.
Since the linux iwlwifi driver doesn't at all support the 4965
chipset, cedric's stuff just plainly breaks that. So I'm going to have
to be ..
Hi!
Can you do 'sysctl dev.cpu' please? I'd like to see what sleep
state(s) your CPU is entering.
Thanks!
-adrian
On 5 November 2013 06:07, Oliver Pinter oliver.p...@gmail.com wrote:
Hi all!
The machine is a Haswell machine, the disc performance was very poor
(20-30MByte/sec).
When I
.coretemp.delta: 62
dev.cpu.3.coretemp.resolution: 1
dev.cpu.3.coretemp.tjmax: 100.0C
dev.cpu.3.coretemp.throttle_log: 0
dev.cpu.3.temperature: 38.0C
dev.cpu.3.cx_supported: C1/1/1 C2/2/67
dev.cpu.3.cx_lowest: C1
dev.cpu.3.cx_usage: 100.00% 0.00% last 1609us
On 11/5/13, Adrian Chadd adr
and sysctl machdep.idle_mwait=0
-adrian
On 5 November 2013 10:12, Adrian Chadd adr...@freebsd.org wrote:
Ok, so it's only hitting C1. It's not going into C2.
Is this a dual core CPU with hyperthreading enabled, or a quad core CPU?
How about changing the idle loop from acpi to hlt, see
.. the main reason to use machdep.idle=hlt is that it is a different code path.
But to ensure you're always going via the hlt codepath, you _first_
have to disable mwait.
The idle code first decides whether to run mwait or idle, then if it
doesn't choose mwait, it chooses machdep.idle. That's
On 8 November 2013 02:32, FreeBSD Tinderbox tinder...@freebsd.org wrote:
[snip]
cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
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 d...@freebsd.org wrote:
On 08 Nov 2013, at 16:08, Adrian Chadd adr...@freebsd.org wrote:
On 8 November 2013
On 9 November 2013 16:05, Daniel O'Connor docon...@gsoft.com.au wrote:
On 10 Nov 2013, at 24:24, Matthew Seaman matt...@freebsd.org wrote:
2) Should ports / packages populate these cron.d directories?
This is a much more interesting question. Effectively its asking
if a port
On 9 November 2013 16:28, Allan Jude free...@allanjude.com 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
On 9 November 2013 17:40, Allan Jude free...@allanjude.com wrote:
On 2013-11-09 20:05, Adrian Chadd wrote:
On 9 November 2013 16:28, Allan Jude free...@allanjude.com wrote:
Well, what about making these extra directories optional then?
packages install the crontab entries, but crond ignores
On 9 November 2013 17:58, Allan Jude free...@allanjude.com 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
Hi!
On 9 November 2013 18:29, Brandon Gooch jamesbrandongo...@gmail.com 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
Sure, flip on 'wlandebug +rate' (assuming you compiled with IEEE80211_DEBUG)
-a
On 9 November 2013 21:08, Brandon Gooch jamesbrandongo...@gmail.com wrote:
On Sat, Nov 9, 2013 at 8:46 PM, Adrian Chadd adr...@freebsd.org wrote:
Hi!
On 9 November 2013 18:29, Brandon Gooch jamesbrandongo
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 adr...@freebsd.org wrote:
Sure, flip on 'wlandebug +rate' (assuming you compiled with IEEE80211_DEBUG)
-a
On 9 November 2013 21:08
yup, same info as brandon. :)
-a
On 10 November 2013 04:17, Stefan Farfeleder stef...@freebsd.org 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
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 stef...@freebsd.org wrote:
On Sun, Nov 10, 2013 at 05:14:58AM -0800, Adrian Chadd wrote:
yup, same info as brandon. :)
http://pastebin.com/MwfL06z7
Stefan
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 adr...@freebsd.org wrote:
Right near the end there you have 'status 83' which means 'transmit
failed, long retry hit' (the status codes
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 stef...@freebsd.org wrote:
On Sun, Nov 10, 2013 at 10:48:48AM -0800, Adrian Chadd wrote:
Right near the end
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 m...@freebsd.org wrote:
Hi.
I've
On 18 November 2013 01:20, Alexander Motin m...@freebsd.org 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 them there are buckets for 1, 5, 13, 29
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
[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
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 adr...@freebsd.org wrote:
hi,
I just updated a laptop from a month old -HEAD
On 22 November 2013 01:11, Andreas Tobler andreast-l...@fgznet.ch wrote:
- Original Message
From: Adrian Chadd adr...@freebsd.org
To: freebsd-current freebsd-current@freebsd.org
Subject: Re: i386 update to latest -HEAD broke things
Date: 22/11/13 10:05
r258446 built
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
Hi,
It's definitely a work in progress, as you've observed.
On 28 November 2013 00:20, Konstantin Belousov kostik...@gmail.com 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 more
intrusive than the first
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
___
On 28 November 2013 19:04, Glen Barber g...@freebsd.org 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 critical fixes that need to go
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 mom040...@gmail.com wrote:
It would be nice to have this feature compiled and supported in FreeBSD
kernel by default.
Thanks
Oleg
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
___
+1, this caught us out with sendfile testing very recently :(
-a
On 30 November 2013 05:56, Konstantin Belousov kostik...@gmail.com 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
On 30 November 2013 15:25, Dimitry Andric d...@freebsd.org wrote:
On 30 Nov 2013, at 14:56, Konstantin Belousov kostik...@gmail.com 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
Hi! Thanks for the writeup!
On 1 December 2013 20:17, Sepherosa Ziehau sepher...@gmail.com 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
On 2 December 2013 03:45, Sepherosa Ziehau sepher...@gmail.com wrote:
On Mon, Dec 2, 2013 at 1:02 PM, Adrian Chadd adr...@freebsd.org 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,
a merge back.
Thanks,
-a
On 7 December 2013 06:03, Matthias Petermann matth...@petermann-it.de 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.
I've just installed 11.0-CURRENT r258208 on my
.
2013/12/8, Adrian Chadd adr...@freebsd.org:
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
Which svn rev introduced the regression?
-a
On 8 December 2013 10:19, Olivier Cochard-Labbé oliv...@cochard.me wrote:
On Sun, Dec 8, 2013 at 6:31 PM, Stefan Hegnauer stefan.hegna...@gmx.ch
wrote:
Hi,
Since late summer - sorry, no exact date / svn revision - nanobsd.sh fails
at the last
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, 乔楚 honestq...@gmail.com 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
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
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 adr...@freebsd.org wrote:
Hi,
I'd like to start committing this to FreeBSD-HEAD:
http
Are you able to make it do delayed firmware loading?
Adrian
On Dec 13, 2013 3:23 AM, Jean-Sébastien Pédron dumbb...@freebsd.org
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
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 tinder...@freebsd.org 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
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
I'm the wireless stack maintainer and I currently don't support that.
Sorry.
-a
On 17 December 2013 08:10, dan_partelly dan_parte...@rdsor.ro wrote:
On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd adr...@freebsd.org
wrote:
Hi,
All 3 MACs are the same. wpi0 is set to the MAC of bg0
On 17 December 2013 08:12, Nikolai Lifanov lifa...@mail.lifanov.com 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
Ive no idea sorry. Its likely an ifnet change and not anything WiFi
specific. :(
On Dec 17, 2013 12:04 PM, dan_partelly dan_parte...@rdsor.ro 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
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 s...@troutmask.apl.washington.edu
wrote:
On Mon, Dec 16, 2013 at 12:20:53PM
[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
What's at frame 10?
And list the IP, ie:
list *0x817da911
-a
On 18 December 2013 23:04, Sergey V. Dyatko sergey.dya...@gmail.com wrote:
Hi,
I have following setup:
wlans_ral0=wlan0
ifconfig_wlan0=WPA
cloned_interfaces=lagg0 bridge0 tap0
ifconfig_lagg0=laggproto failover
Would you mind filing a PR?
-a
On 18 December 2013 09:27, Kurt Lidl l...@pix.net 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
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 sergey.dya...@gmail.com wrote:
On Wed, 18 Dec 2013 23:40:23 -0800
Adrian Chadd adr...@freebsd.org wrote:
What's
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
Dan
On Tue, 17 Dec 2013 12:11:49 -0800, Adrian Chadd adrian.ch...@gmail.com
wrote:
Ive no idea sorry. Its likely
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 stefan.hegna...@gmx.ch wrote:
When using 'WITHOUT_CAPSICUM=YES', 'WITHOUT_CASPER=YES' my nanobsd builds in
a Virtualbox VM (i386, march=geode,
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 s...@troutmask.apl.washington.edu
wrote:
On Sat, Dec 21,
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 anton.r...@isilon.com wrote:
The HWPMC hooks are never invoked except when using the soft PMC feature for
performance monitoring. This trivial patch
On 24 December 2013 12:41, d...@gmx.com 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
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 han...@mehnert.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hi,
I'm running current and
On 17 December 2013 22:41, d...@gmx.com 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, drm1)
On 30 December 2013 16:32, d...@gmx.com 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
Fixed! Sorry.
Adrian
On 25 June 2011 06:12, FreeBSD Tinderbox tinder...@freebsd.org wrote:
TB --- 2011-06-24 21:10:00 - tinderbox 2.7 running on
freebsd-current.sentex.ca
TB --- 2011-06-24 21:10:00 - starting HEAD tinderbox run for arm/arm
TB --- 2011-06-24 21:10:00 - cleaning the object
This is kinda strange; that symbol doesn't exist in the net80211 or ath source.
What the heck?
adrian
On 28 June 2011 17:28, Stefan Esser st_es...@t-online.de wrote:
Hi,
is this a known issue?
My -CURRENT system (r223560M, amd64, 8GB, Atheros WLAN) panics after
minutes to hours of
On 29 June 2011 14:03, Bernhard Schmidt bschm...@freebsd.org wrote:
It's name is ieee80211_tx_mgt_timeout used to track AUTH/ASSOC
requests. Afaik there is even a similar PR about that.
Adrian, you've got a AP set up to drop either a AUTH or ASSOC
response frame?
Tell me how and I'll set it
The question here is - what context is the callback being called in?
The lack of net80211 locking has me confused and sad. :/
Adrian
On 29 June 2011 16:27, Bernhard Schmidt bschm...@freebsd.org wrote:
On Wednesday, June 29, 2011 10:03:02 Adrian Chadd wrote:
On 29 June 2011 14:03, Bernhard
The obvious question - can you bisect kernel versions to find out when it broke?
Adrian
On 3 July 2011 13:39, Doug Barton do...@freebsd.org wrote:
I have 2 ath-based pc-card adapters. If I put either one of them in the slot
while the system is up, or if I try booting with them in the slot, I
On 4 July 2011 16:37, Doug Barton do...@freebsd.org wrote:
On 07/03/2011 03:05, Adrian Chadd wrote:
The obvious question - can you bisect kernel versions to find out when it
broke?
Sorry, I thought the answer to that was obvious from my message. I have no
idea how far back the breakage goes
Has anyone re-run those IO benchmarks?
Something smells fishy there.. (with the benchmarking.)
adrian
2011/7/6 O. Hartmann ohart...@zedat.fu-berlin.de:
On 07/06/11 12:37, arrowdodger wrote:
2011/7/6 O. Hartmannohart...@zedat.fu-berlin.de
When performing an update on the ports tree via
Offer a bounty for getting it fixed?
thanks,
Adrian
On 7 July 2011 05:00, Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
On 07/06/11 21:36, Steve Kargl wrote:
On Wed, Jul 06, 2011 at 03:18:35PM -0400, Arnaud Lacombe wrote:
Hi,
On Wed, Jul 6, 2011 at 12:28 PM, Steve Kargl
On 7 July 2011 09:51, Steve Kargl s...@troutmask.apl.washington.edu wrote:
On Thu, Jul 07, 2011 at 09:17:51AM +0800, Adrian Chadd wrote:
Offer a bounty for getting it fixed?
steve == ENOMONEY jeffr == ENOTIME
And, 4BSD works.
I meant it as a more general observation.
If something doesn't
(OT, yes, but I'd like to take a stab at explaining why these things
fall to the wayside..)
On 7 July 2011 12:08, Arnaud Lacombe lacom...@gmail.com wrote:
What would be the point to even start looking at an issue? You guys
(by you, I mean official committers on public list) don't care
When
That top output is averaged and slow to adjust.
Using top as an indication as to what's really going on is likely
not a good idea.
2c,
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
Hi all,
I've updated the -current regulatory domain database to include some
of the missing 5ghz channels that are now allowed in Japan.
Please test/comment.
Thanks!
Adrian
___
freebsd-current@freebsd.org mailing list
Don't forget if_ath_pci.
Adrian
On 14 July 2011 16:59, Doug Barton do...@freebsd.org wrote:
On 07/12/2011 07:22, John Baldwin wrote:
On Monday, July 11, 2011 9:29:19 pm Doug Barton wrote:
On 07/08/2011 06:19, John Baldwin wrote:
Hmm, well that's odd. It didn't grow it enough it seems.
Unless say, you're doing package installation outside of a
chroot/jail, to populate something inside a chroot/jail before you
start said chroot/jail.
Adrian
On 17 July 2011 00:13, Chris Rees cr...@freebsd.org wrote:
On 16 Jul 2011 17:04, Stephen Montgomery-Smith step...@missouri.edu
wrote:
In order to debug this further, we need some further information from you.
Can you please narrow down the date and/or -current revision which
this particular issue occured?
Eg, if you revert back to a -current kernel from 6 months ago, does
your wifi work again?
Thanks,
Adrian
On 17 July 2011
just committed that.
Sorry, I thought that version of the patch had compiled right. Sorry ;(
adrian
2011/7/20 fidaj fi...@ukr.net:
--- Оригінальне повідомлення ---
Від кого: Hartmann, O. ohart...@zedat.fu-berlin.de
Кому: FreeBSD Current freebsd-current@freebsd.org
Дата: 19 липня
.. wait, the install-off-USB doesn't default to a read-only boot?
Adrian
On 25 July 2011 08:11, Claude Buisson clbuis...@orange.fr wrote:
On 07/24/2011 23:33, Nathan Whitehorn wrote:
On 07/24/11 16:29, eculp wrote:
I have been hearing about a new installer but I obviously have not
payed
Is it perhaps doing disk IO using mmap?
adrian
On 25 July 2011 05:25, Alexander Best arun...@freebsd.org wrote:
hi there,
i noticed that chromium, expecially in combination with nspluginwrapper and
flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 99' and after
only ~ 4
...@freebsd.org wrote:
It does not. I had tried to match the behavior of the 8.x memsticks. It's an
easy change in /usr/src/release/ARCH/make-memstick.sh to change it, however.
-Nathan
On 07/24/11 19:54, Adrian Chadd wrote:
.. wait, the install-off-USB doesn't default to a read-only boot
, Adrian Chadd wrote:
Is it perhaps doing disk IO using mmap?
how can i check, whether that's the case or not?
Use truss(1) for instance.
However, unless there are *practical* problems, a high number of page
faults is not an indication for problems. Although it may sound scary,
page
101 - 200 of 1248 matches
Mail list logo
