Re[2]: ARC pressured out, how to control/stabilize ? (reformatted to text/plain)

2014-01-28 Thread Vladimir Sharun 
Dear Andriy and FreeBSD community,

After applying this path one of the systems runs fine (disk subsystem load low 
to moderate 
- 10-20% busy sustained),

Then I saw this patch was merged to the HEAD and we apply it to the one of the 
systems 
with moderate to high disk load: 30-60% busy (11.0-CURRENT #7 r261118: Fri Jan 
24 17:25:08 EET 2014)

Within 4 days we experiencing the same leak(?) as without patch: 

last pid: 53841;  load averages:  4.47,  4.18,  3.78 up 3+16:37:09  11:24:39
543 processes: 6 running, 537 sleeping
CPU:  8.7% user,  0.0% nice, 14.6% system,  1.4% interrupt, 75.3% idle
Mem: 22G Active, 1045M Inact, 98G Wired, 1288M Cache, 3284M Buf, 2246M Free
ARC: 73G Total, 3763M MFU, 62G MRU, 56M Anon, 1887M Header, 4969M Other
Swap:

The ARC is populated within 30mins under load to the max (90Gb) then start 
decreasing.

The delta between Wiread and ARC total start growing from typical 10-12Gb 
without L2 enabled
to the 25Gb with L2 enabled and counting (4 hours ago was 22Gb delta).

L2ARC statistics:

L2 ARC Size: (Adaptive) 291.63  GiB
Header Size:0.25%   734.14  MiB

L2 ARC Evicts:
Lock Retries:   682
Upon Reading:   0

L2 ARC Breakdown:   106.56m
Hit Ratio:  29.04%  30.95m
Miss Ratio: 70.96%  75.62m
Feeds:  317.18k

So, again, what shall we do to better understand/mitigate the problem further ?

Thank you.

 on 15/01/2014 12:28 Vitalij Satanivskij said the following:
  Dear Andriy and FreeBSD community,
  
  Andriy Gapon wrote:
  AG on 14/01/2014 07:27 Vladimir Sharun said the following:
  AG  Dear Andriy and FreeBSD community,
  AG  
  AG  I am not sure if the buffers are leaked somehow or if they are 
  actually in use.
  AG  It's one of the very few places where data buffers are allocated 
  without
  AG  charging ARC. In all other places it's quite easy to match 
  allocations and
  AG  deallocations. But in L2ARC it is not obvious that all buffers get 
  freed or
  AG  when that happens.
  AG  
  AG  After one week under load I think we figure out the cause: it's 
  L2ARC. 
  AG  Here's the top's header for 7d17h of the runtime:
  AG  
  AG  last pid: 46409; load averages: 0.37, 0.62, 0.70 up 7+17:14:01 
  07:24:10
  AG  173 processes: 1 running, 171 sleeping, 1 zombie
  AG  CPU: 2.0% user, 0.0% nice, 3.5% system, 0.4% interrupt, 94.2% idle
  AG  Mem: 8714M Active, 14G Inact, 96G Wired, 1929M Cache, 3309M Buf, 
  3542M Free
  AG  ARC: 85G Total, 2558M MFU, 77G MRU, 28M Anon, 1446M Header, 4802M 
  Other
  AG  
  AG  ARC related tunables:
  AG  
  AG  vm.kmem_size=110G
  AG  vfs.zfs.arc_max=90G
  AG  vfs.zfs.arc_min=42G
  AG  
  AG  For more than 7 days of hard runtime the picture clearly shows: 
  AG  Wired minus ARC = 11..12Gb, ARC grow and shrinks in 80-87Gb range and 
  the
  AG  system runs just fine.
  AG  
  AG  So what shall we do with L2ARC leakage ?
  AG 
  AG 
  AG Could you please try this patch
  AG http://cr.illumos.org/~webrev/skiselkov/3995/illumos-gate.patch ?
  AG 
  
  While applying path to curent version of arc.c (r260622) I'm found next 
  truble with compilation 
  
  olaris/uts/common/fs/zfs/arc.c -o arc.o
  /usr/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:4628:18:
   error: use of
  undeclared identifier 'abl2'
  trim_map_free(abl2-b_dev-l2ad_vdev, abl2-b_daddr,
  ^
  1 error generated.
  *** Error code 1
  
  
  the code is - 
  
  if (zio-io_error != 0) {
  /*
  * Error - drop L2ARC entry.
  */
  list_remove(buflist, ab);
  ARCSTAT_INCR(arcstat_l2_asize, -l2hdr-b_asize);
  ab-b_l2hdr = NULL;
  trim_map_free(abl2-b_dev-l2ad_vdev, abl2-b_daddr,
  ab-b_size, 0);
  kmem_free(l2hdr, sizeof (l2arc_buf_hdr_t));
  ARCSTAT_INCR(arcstat_l2_size, -ab-b_size);
  }
  
  
  Looks like it's part is freebsd specific changes.
  Can somebody help with this part of code ?
  
 
 The first hunk of the patch is renaming of abl2 to l2hdr.
 
 -- 
 Andriy Gapon
 ___
 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
 
___
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

Re: Instant panic CAM or USB subsystem

2014-01-28 Thread John Baldwin 
On Saturday, January 25, 2014 12:21:06 pm Steve Kargl wrote:
 If I plug my Samsung Intensity II cellphone into a usb port,
 I get an instant panic.  This is 100% reproducible.  I have
 the core and kernel for further debugging.  Dmesg.boot follows
 my sig.
 
 % kgdb /boot/kernel/kernel /vmcore.0
 
 Unread portion of the kernel message buffer:
 cd1 at umass-sim1 bus 1 scbus4 target 0 lun 0
 cd1: SAMSUNG CD-ROM 1.00 Removable CD-ROM SCSI-2 device 
 cd1: Serial Number 0002
 cd1: 1.000MB/s transfers
 cd1: cd present [384 x 512 byte records]
 cd1: quirks=0x1010_BYTE_ONLY
 panic: mutex CAM device lock not owned at /usr/src/sys/cam/cam_periph.c:301
 cpuid = 0
 KDB: enter: panic

scsi@ might work better for this.  It looks like when cdasync() calls 
cam_periph_alloc() it doesn't have its associated xpt_path locked.  All the 
other async xpt callbacks I looked at don't lock the xpt path either.  It 
seems they expect it to be locked by the caller when they are invoked.  It 
seems xpt_async_process_dev() doesn't always lock xpt_lock, but sometimes
locks the device instead:

/*
 * If async for specific device is to be delivered to
 * the wildcard client, take the specific device lock.
 * XXX: We may need a way for client to specify it.
 */
if ((device-lun_id == CAM_LUN_WILDCARD 
 path-device-lun_id != CAM_LUN_WILDCARD) ||
(device-target-target_id == CAM_TARGET_WILDCARD 
 path-target-target_id != CAM_TARGET_WILDCARD) ||
(device-target-bus-path_id == CAM_BUS_WILDCARD 
 path-target-bus-path_id != CAM_BUS_WILDCARD)) {
mtx_unlock(device-device_mtx);
xpt_path_lock(path);
relock = 1;
} else
relock = 0;

(*(device-target-bus-xport-async))(async_code,
device-target-bus, device-target, device, async_arg);
xpt_async_bcast(device-asyncs, async_code, path, async_arg);

if (relock) {
xpt_path_unlock(path);
mtx_lock(device-device_mtx);
}

Maybe try going up to this frame (16) in your dump and do
'p *device-target'?  However, someone with more CAM knowledge needs to look 
at this to see what is actually broken.

It seems a bit odd that it thinks your phone is a CD player.

-- 
John Baldwin
___
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

Re: any use for sys/sys/selinfo.h outside the kernel ?

2014-01-28 Thread John Baldwin 
On Wednesday, January 22, 2014 5:38:36 pm Luigi Rizzo wrote:
 Looking at sys/sys/selinfo.h i see that parts of it are in
 
   #ifdef _KERNEL
   ...
   #endif
 
 but it seems to me that also the remaining content (definition
 of struct selinfo) is only of use within the kernel -- or possibly
 to programs who want to peek into kmem.
 
 So i wonder, does it make sense to have the #ifdef _KERNEL guard
 at all, or should we push it to the entire content of the file ?
 
 Same goes probably for other files in sys/sys describing kernel
 data structures, e.g. sys/sys/socketvar.h etc.

Some things (ab)use socket ones (probably lsof for example).  I'm not
sure of any that need selinfo, though they may need it indirectly.
For example, since lsof wants to look at sockets, it needs sockbuf,
and sockbuf needs selinfo, etc.

-- 
John Baldwin
___
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

Re: Instant panic CAM or USB subsystem

2014-01-28 Thread John-Mark Gurney 
John Baldwin wrote this message on Tue, Jan 28, 2014 at 12:32 -0500:
 It seems a bit odd that it thinks your phone is a CD player.

I've seen a phone that acts like that, they use it to present software
(like sync) for install on the desktop...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
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

Re: Bad support of Kingston DataTraveler/DT USB key since 9.2 (not fixed in 10.0)

2014-01-28 Thread Olivier Cochard-Labbé 
On Wed, Jan 22, 2014 at 9:41 PM, Olivier Cochard-Labbé
oliv...@cochard.mewrote:

 I've meet the problem on FreeBSD 10.0 with a Kingston DT 101 G2 (this is
 why I've fill the PR usb/185747), but it wasn't my key then I didn't have
 access to it anymore.
  Then the author of the PR usb/180837 confirms the problem on FreeBSD 9.2
 with this same key (but he didn't have to use the same quirks on 9.2 as me
 on 10.0) and notice that the NetBSD quirks list include a list of Kingston
 DataTraveler USB keys
 And just after a new PR misc/185837 was created by another user... This why
 I wonder if there is something wrong with somes of the Kingston
 DataTraveler.

 FYI, I've just ordered 3 differents Kingston Datatraveler keys for testing
 them:
 - Kingston DataTraveler SE9
 - Kingston DataTraveler 100 G3
 - Kingston DataTraveler i G4 8
 I will test them once received.


Received all 3 keys and good news: these 3 works :-)
Then it seems only the Kingston DT 10* G2 meet problems, but I didn't
have it with me anymore for getting the VID and PID.

Just for the record, the VID/PID of the working tested keys:
- Kingston DataTraveler SE9: idVendor = 0x0951, idProduct = 0x1665,
iManufacturer
= 0x0001  Kingston, iProduct = 0x0002  DataTraveler 2.0
- Kingston DataTraveler 100 G3: idVendor = 0x0951, idProduct = 0x1666,
iManufacturer
= 0x0001  Kingston, iProduct = 0x0002  DataTraveler 3.0
- Kingston DataTraveler i G4: idVendor = 0x0951, idProduct = 0x1666,
iManufacturer
= 0x0001  Kingston, iProduct = 0x0002  DataTraveler 3.0
= The DataTraveler G4 and the DataTraveler 100 G3 have the same
VID/PID.

Regards,
___
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

Re: Instant panic CAM or USB subsystem

2014-01-28 Thread Steve Kargl 
On Tue, Jan 28, 2014 at 12:32:21PM -0500, John Baldwin wrote:
 On Saturday, January 25, 2014 12:21:06 pm Steve Kargl wrote:
  If I plug my Samsung Intensity II cellphone into a usb port,
  I get an instant panic.  This is 100% reproducible.  I have
  the core and kernel for further debugging.  Dmesg.boot follows
  my sig.
  
  % kgdb /boot/kernel/kernel /vmcore.0
  
  Unread portion of the kernel message buffer:
  cd1 at umass-sim1 bus 1 scbus4 target 0 lun 0
  cd1: SAMSUNG CD-ROM 1.00 Removable CD-ROM SCSI-2 device 
  cd1: Serial Number 0002
  cd1: 1.000MB/s transfers
  cd1: cd present [384 x 512 byte records]
  cd1: quirks=0x1010_BYTE_ONLY
  panic: mutex CAM device lock not owned at /usr/src/sys/cam/cam_periph.c:301
  cpuid = 0
  KDB: enter: panic
 
 scsi@ might work better for this.  It looks like when cdasync() calls 
 cam_periph_alloc() it doesn't have its associated xpt_path locked.  All the 
 other async xpt callbacks I looked at don't lock the xpt path either.  It 
 seems they expect it to be locked by the caller when they are invoked.  It 
 seems xpt_async_process_dev() doesn't always lock xpt_lock, but sometimes
 locks the device instead:
 
   /*
* If async for specific device is to be delivered to
* the wildcard client, take the specific device lock.
* XXX: We may need a way for client to specify it.
*/
   if ((device-lun_id == CAM_LUN_WILDCARD 
path-device-lun_id != CAM_LUN_WILDCARD) ||
   (device-target-target_id == CAM_TARGET_WILDCARD 
path-target-target_id != CAM_TARGET_WILDCARD) ||
   (device-target-bus-path_id == CAM_BUS_WILDCARD 
path-target-bus-path_id != CAM_BUS_WILDCARD)) {
   mtx_unlock(device-device_mtx);
   xpt_path_lock(path);
   relock = 1;
   } else
   relock = 0;
 
   (*(device-target-bus-xport-async))(async_code,
   device-target-bus, device-target, device, async_arg);
   xpt_async_bcast(device-asyncs, async_code, path, async_arg);
 
   if (relock) {
   xpt_path_unlock(path);
   mtx_lock(device-device_mtx);
   }
 
 Maybe try going up to this frame (16) in your dump and do
 'p *device-target'?  However, someone with more CAM knowledge needs to look 
 at this to see what is actually broken.
 
 It seems a bit odd that it thinks your phone is a CD player.

Thanks for the follow-up.  I poked around a bit, but don't
recall looking at *device-target.   Under Windows, 3 
filesystems show up, and the one causing problems is listed
as CDFS.

I'm travaling this week for owrk, so may not be able to
follow-up with more info until Sunday.

-- 
Steve
___
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

Re: Instant panic CAM or USB subsystem

2014-01-28 Thread Steve Kargl 
On Tue, Jan 28, 2014 at 09:53:52AM -0800, John-Mark Gurney wrote:
 John Baldwin wrote this message on Tue, Jan 28, 2014 at 12:32 -0500:
  It seems a bit odd that it thinks your phone is a CD player.
 
 I've seen a phone that acts like that, they use it to present software
 (like sync) for install on the desktop...
 

Yes, that appears to be the problem.  Under Windows, the phone
shows 3 filesystems and the problematic one reports CDFS.  I 
should note that I've plugged this phone into this laptop
for a few years without any issues.  I unfortunately updated
a circa Aug 2013 freebsd-current to a week old -current.  It
has not been a pleasant experience.  Unzipping or untarring
a large compressed archive onto a USB mounted hard drive
renders the system unusable for minutes at a time. unzip
and bsdtar are stuck in getblk or wdrain for 30 to 60
seconds.  System recovers for a few seconds then get stuck
again.  Rinse and repeat.  I'm not sure if it is a UFS2
or USB or some other change.
 
-- 
Steve
___
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

Change nfsstat client statistics to report actual RPC counts

2014-01-28 Thread John Baldwin 
I had always assumed that when you ran 'nfsstat -c 1' you saw counts of actual 
RPCs sent over the wire (similar to how 'netstat 1' show actual packets / 
bytes, 'iostat 1' shows actual disk transactions / bytes, etc.).  I was 
surprised to find that 'nfsstat -c' does not show actual RPC counts.  Instead, 
it shows theoretical RPC counts as if the client did no caching at all.  (This 
would be akin to 'iostat 1' showing a disk transaction for every read() system 
call).  In general when I'm using 'nfsstat -c 1', I'm using it to get a 
summary of what the NFS client is actually sending over the wire, not the 
theoretical numbers.  To that end, I have a patch to change nfsstat back to 
reporting raw RPC count deltas instead of theoretical deltas.  (It used to 
report raw RPC counts back before 4.0.)  If you are curious about the 
effectiveness of the client side caches, that data can still be obtained via 
the existing '-W' flag.

Index: nfsstat.c
===
--- nfsstat.c   (revision 261241)
+++ nfsstat.c   (working copy)
@@ -604,14 +604,15 @@
if (clientOnly) {
printf(%s %6d %6d %6d %6d %6d %6d %6d %6d,
((clientOnly  serverOnly) ? Client: : ),
-   DELTA(attrcache_hits) + DELTA(attrcache_misses),
-   DELTA(lookupcache_hits) + DELTA(lookupcache_misses),
-   DELTA(biocache_readlinks),
-   DELTA(biocache_reads),
-   DELTA(biocache_writes),
-   
nfsstats.rpccnt[NFSPROC_RENAME]-lastst.rpccnt[NFSPROC_RENAME],
-   DELTA(accesscache_hits) + DELTA(accesscache_misses),
-   DELTA(biocache_readdirs)
+   DELTA(rpccnt[NFSPROC_GETATTR]),
+   DELTA(rpccnt[NFSPROC_LOOKUP]),
+   DELTA(rpccnt[NFSPROC_READLINK]),
+   DELTA(rpccnt[NFSPROC_READ]),
+   DELTA(rpccnt[NFSPROC_WRITE]),
+   DELTA(rpccnt[NFSPROC_RENAME]),
+   DELTA(rpccnt[NFSPROC_ACCESS]),
+   DELTA(rpccnt[NFSPROC_READDIR]) +
+   DELTA(rpccnt[NFSPROC_READDIRPLUS])
);
if (widemode) {
printf( %s %s %s %s %s %s,
@@ -993,15 +994,15 @@
if (clientOnly) {
printf(%s %6d %6d %6d %6d %6d %6d %6d %6d,
((clientOnly  serverOnly) ? Client: : ),
-   DELTA(attrcache_hits) + DELTA(attrcache_misses),
-   DELTA(lookupcache_hits) + DELTA(lookupcache_misses),
-   DELTA(biocache_readlinks),
-   DELTA(biocache_reads),
-   DELTA(biocache_writes),
-   nfsstats.rpccnt[NFSPROC_RENAME] -
-   lastst.rpccnt[NFSPROC_RENAME],
-   DELTA(accesscache_hits) + DELTA(accesscache_misses),
-   DELTA(biocache_readdirs)
+   DELTA(rpccnt[NFSPROC_GETATTR]),
+   DELTA(rpccnt[NFSPROC_LOOKUP]),
+   DELTA(rpccnt[NFSPROC_READLINK]),
+   DELTA(rpccnt[NFSPROC_READ]),
+   DELTA(rpccnt[NFSPROC_WRITE]),
+   DELTA(rpccnt[NFSPROC_RENAME]),
+   DELTA(rpccnt[NFSPROC_ACCESS]),
+   DELTA(rpccnt[NFSPROC_READDIR]) +
+   DELTA(rpccnt[NFSPROC_READDIRPLUS])
);
if (widemode) {
printf( %s %s %s %s %s %s,


-- 
John Baldwin
___
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

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-28 Thread Vlad Movchan 
Hi Adrian,

I'm sorry about this mistake. I updated original PR (
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/165622) with the corrected
patch.



On Tue, Jan 28, 2014 at 2:38 AM, Adrian Chadd adr...@freebsd.org 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




-- 
Have a nice day,
Vlad Movchan
___
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

Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC

2014-01-28 Thread Adrian Chadd 
Ok, I'll take a look at it tonight, thanks!


-a


On 28 January 2014 13:08, Vlad Movchan vladislav.movc...@gmail.com wrote:
 Hi Adrian,

 I'm sorry about this mistake. I updated original PR
 (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/165622) with the corrected
 patch.



 On Tue, Jan 28, 2014 at 2:38 AM, Adrian Chadd adr...@freebsd.org 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




 --
 Have a nice day,
 Vlad Movchan
___
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

Apple Trackpad driver

2014-01-28 Thread Huang Wen Hui 
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.gddsn.org.cn/freebsd/wsp-140129.tar.gz,
I only test it on MBP2012 and MBP2013. Right now the driver have these
feature:

1. Vertical scrolling with 2 fingers movement,
2. In firefox, 2 fingers horizontal movement act as page back/forward.
3. one finger tap act as left mouse click, 2 fingers tap act as right mouse
click, and
three fingers tap act as middle mouse click.
4. you also use sysctl to modify some parameters:
hw.usb.wsp.scale_factor: 12
hw.usb.wsp.z_factor: 5
hw.usb.wsp.pressure_touch_threshold: 50
hw.usb.wsp.pressure_untouch_threshold: 10
hw.usb.wsp.pressure_tap_threshold: 120
hw.usb.wsp.scr_hor_threshold: 50

Cheers,

Huang Wen Hui
___
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

System libc++ isn't fully compatible with clang 3.4 from ports

2014-01-28 Thread Dmitry Marakasov 
Hi!

JFYI, I've just ran into shortcoming of libc++ from 10-RELEASE when used
with clang 3.4 from ports:

---
% cat test.cc
#include iostream
#include functional

int main() {
std::functionvoid() f = []() { std::cerr  test\n; };
return 0;
}
% clang++ -std=c++11 test.cc ---
% clang++34 -std=c++11 test.cc ---
In file included from test.cc:1:
In file included from /usr/include/c++/v1/iostream:38:
In file included from /usr/include/c++/v1/ios:216:
In file included from /usr/include/c++/v1/__locale:15:
In file included from /usr/include/c++/v1/string:434:
In file included from /usr/include/c++/v1/algorithm:627:
In file included from /usr/include/c++/v1/memory:603:
/usr/include/c++/v1/tuple:320:11: error: rvalue reference to type 'lambda at 
test.cc:5:28' cannot bind to lvalue of type 'lambda at test.cc:5:28'
: value(__t.get())
  ^ ~
/usr/include/c++/v1/tuple:444:8: note: in instantiation of member function 
'std::__1::__tuple_leaf0, lambda at test.cc:5:28 , false::__tuple_leaf' 
requested here
struct __tuple_impl__tuple_indices_Indx..., _Tp...
   ^
/usr/include/c++/v1/functional:1286:26: note: in instantiation of member 
function 'std::__1::__function::__funclambda at test.cc:5:28, 
std::__1::allocatorlambda at test.cc:5:28 , void ()::__func' requested here
::new (__f_) _FF(_VSTD::move(__f));
 ^
test.cc:5:28: note: in instantiation of function template specialization 
'std::__1::functionvoid ()::functionlambda at test.cc:5:28 ' requested 
here
std::functionvoid() f = []() { std::cerr  test\n; };
  ^
In file included from test.cc:1:
In file included from /usr/include/c++/v1/iostream:38:
In file included from /usr/include/c++/v1/ios:216:
In file included from /usr/include/c++/v1/__locale:15:
In file included from /usr/include/c++/v1/string:434:
In file included from /usr/include/c++/v1/algorithm:627:
In file included from /usr/include/c++/v1/memory:603:
/usr/include/c++/v1/tuple:321:10: error: static_assert failed Can not copy a 
tuple with rvalue reference member
{static_assert(!is_rvalue_reference_Hp::value, Can not copy a tuple 
with rvalue reference member);}
 ^ 
/usr/include/c++/v1/tuple:320:11: error: rvalue reference to type 
'allocator[...]' cannot bind to lvalue of type 'allocator[...]'
: value(__t.get())
  ^ ~
/usr/include/c++/v1/tuple:444:8: note: in instantiation of member function 
'std::__1::__tuple_leaf0, std::__1::allocatorlambda at test.cc:5:28  , 
false::__tuple_leaf' requested here
struct __tuple_impl__tuple_indices_Indx..., _Tp...
   ^
/usr/include/c++/v1/functional:1294:34: note: in instantiation of member 
function 'std::__1::__function::__funclambda at test.cc:5:28, 
std::__1::allocatorlambda at test.cc:5:28 , void ()::__func' requested here
::new (__hold.get()) _FF(_VSTD::move(__f), allocator_Fp(__a));
 ^
test.cc:5:28: note: in instantiation of function template specialization 
'std::__1::functionvoid ()::functionlambda at test.cc:5:28 ' requested 
here
std::functionvoid() f = []() { std::cerr  test\n; };
  ^
In file included from test.cc:1:
In file included from /usr/include/c++/v1/iostream:38:
In file included from /usr/include/c++/v1/ios:216:
In file included from /usr/include/c++/v1/__locale:15:
In file included from /usr/include/c++/v1/string:434:
In file included from /usr/include/c++/v1/algorithm:627:
In file included from /usr/include/c++/v1/memory:603:
/usr/include/c++/v1/tuple:321:10: error: static_assert failed Can not copy a 
tuple with rvalue reference member
{static_assert(!is_rvalue_reference_Hp::value, Can not copy a tuple 
with rvalue reference member);}
 ^ 
4 errors generated.
---

The cause: http://llvm.org/bugs/show_bug.cgi?id=17798, was fixed in
libc++ r194154. We probably need to update libc++ or at least backport
this into stable branches if we want to support clang 3.4 in ports.

-- 
Dmitry Marakasov   .   55B5 0596 FF1E 8D84 5F56  9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru  ..:  jabber: amd...@jabber.ruhttp://www.amdmi3.ru
___
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

Re: Apple Trackpad driver

2014-01-28 Thread Adrian Chadd 
holy crap, cool!

Hans? Any chance we could get this into -HEAD?


-a


On 28 January 2014 17:43, Huang Wen Hui huang...@gmail.com 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.gddsn.org.cn/freebsd/wsp-140129.tar.gz,
 I only test it on MBP2012 and MBP2013. Right now the driver have these
 feature:

 1. Vertical scrolling with 2 fingers movement,
 2. In firefox, 2 fingers horizontal movement act as page back/forward.
 3. one finger tap act as left mouse click, 2 fingers tap act as right mouse
 click, and
 three fingers tap act as middle mouse click.
 4. you also use sysctl to modify some parameters:
 hw.usb.wsp.scale_factor: 12
 hw.usb.wsp.z_factor: 5
 hw.usb.wsp.pressure_touch_threshold: 50
 hw.usb.wsp.pressure_untouch_threshold: 10
 hw.usb.wsp.pressure_tap_threshold: 120
 hw.usb.wsp.scr_hor_threshold: 50

 Cheers,

 Huang Wen Hui
 ___
 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
___
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

[head tinderbox] failure on armv6/arm

2014-01-28 Thread FreeBSD Tinderbox 
TB --- 2014-01-29 02:10:29 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2014-01-29 02:10:29 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2014-01-29 02:10:29 - starting HEAD tinderbox run for armv6/arm
TB --- 2014-01-29 02:10:29 - cleaning the object tree
TB --- 2014-01-29 02:10:29 - /usr/local/bin/svn stat /src
TB --- 2014-01-29 02:10:37 - At svn revision 261254
TB --- 2014-01-29 02:10:38 - building world
TB --- 2014-01-29 02:10:38 - CROSS_BUILD_TESTING=YES
TB --- 2014-01-29 02:10:38 - MAKEOBJDIRPREFIX=/obj
TB --- 2014-01-29 02:10:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2014-01-29 02:10:38 - SRCCONF=/dev/null
TB --- 2014-01-29 02:10:38 - TARGET=arm
TB --- 2014-01-29 02:10:38 - TARGET_ARCH=armv6
TB --- 2014-01-29 02:10:38 - TZ=UTC
TB --- 2014-01-29 02:10:38 - __MAKE_CONF=/dev/null
TB --- 2014-01-29 02:10:38 - cd /src
TB --- 2014-01-29 02:10:38 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Jan 29 02:10:44 UTC 2014
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 World build completed on Wed Jan 29 05:13:39 UTC 2014
TB --- 2014-01-29 05:13:39 - generating LINT kernel config
TB --- 2014-01-29 05:13:39 - cd /src/sys/arm/conf
TB --- 2014-01-29 05:13:39 - /usr/bin/make -B LINT
TB --- 2014-01-29 05:13:39 - cd /src/sys/arm/conf
TB --- 2014-01-29 05:13:39 - /usr/sbin/config -m LINT
TB --- 2014-01-29 05:13:39 - skipping LINT kernel
TB --- 2014-01-29 05:13:39 - cd /src/sys/arm/conf
TB --- 2014-01-29 05:13:39 - /usr/sbin/config -m AC100
TB --- 2014-01-29 05:13:39 - building AC100 kernel
TB --- 2014-01-29 05:13:39 - CROSS_BUILD_TESTING=YES
TB --- 2014-01-29 05:13:39 - MAKEOBJDIRPREFIX=/obj
TB --- 2014-01-29 05:13:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2014-01-29 05:13:39 - SRCCONF=/dev/null
TB --- 2014-01-29 05:13:39 - TARGET=arm
TB --- 2014-01-29 05:13:39 - TARGET_ARCH=armv6
TB --- 2014-01-29 05:13:39 - TZ=UTC
TB --- 2014-01-29 05:13:39 - __MAKE_CONF=/dev/null
TB --- 2014-01-29 05:13:39 - cd /src
TB --- 2014-01-29 05:13:39 - /usr/bin/make -B buildkernel KERNCONF=AC100
 Kernel build for AC100 started on Wed Jan 29 05:13:39 UTC 2014
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
--
cd /obj/arm.armv6/src/sys/AC100; MAKEOBJDIRPREFIX=/obj/arm.armv6  
MACHINE_ARCH=armv6  MACHINE=arm  CPUTYPE= 
GROFF_BIN_PATH=/obj/arm.armv6/src/tmp/legacy/usr/bin  
GROFF_FONT_PATH=/obj/arm.armv6/src/tmp/legacy/usr/share/groff_font  
GROFF_TMAC_PATH=/obj/arm.armv6/src/tmp/legacy/usr/share/tmac  
_SHLIBDIRPREFIX=/obj/arm.armv6/src/tmp  _LDSCRIPTROOT=  VERSION=FreeBSD 
11.0-CURRENT armv6 116  INSTALL=sh /src/tools/install.sh  
PATH=/obj/arm.armv6/src/tmp/legacy/usr/sbin:/obj/arm.armv6/src/tmp/legacy/usr/bin:/obj/arm.armv6/src/tmp/legacy/usr/games:/obj/arm.armv6/src/tmp/legacy/bin:/obj/arm.armv6/src/tmp/usr/sbin:/obj/arm.armv6/src/tmp/usr/bin:/obj/arm.armv6/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
 CC=cc  CXX=c++   CPP=cpp   AS=as AR=ar LD=ld NM=nm  OBJDUMP= 
RANLIB=ranlib STRINGS= COMPILER_TYPE=clang /obj/src/make.amd64/bmake  -B -m 
/src/share/mk  KERNEL=kernel depend -DNO_MODULES_OBJ
machine - /src/sys/arm/include
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 -Wmissing-include-dirs 
-fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -nostdinc -I. -I/src/sys 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/dev/ath 
-I/src/sys/dev/ath/ath_hal -I/src/sys/contrib/dev/ath/ath_hal 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/cxgb 
-I/src/sys/dev/cxgbe -I/src/sys/contrib/libfdt -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -funwind-tables -mllvm 
-arm-enable-ehabi -ffreestanding /src/sys/arm/arm/genassym.c
In file included from /src/sys/arm/arm/genassym.c:36:
/src/sys/sys/bus.h:585:10: fatal error: 'device_if.h' file not found
#include device_if.h
 ^
1 error generated.
*** Error code 1

Stop.
bmake[1]: stopped in /obj/arm.armv6/src/sys/AC100
*** Error code 1

Stop.
bmake: stopped in /src
*** Error code 1

Stop in /src.
TB --- 2014-01-29 05:13:42 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2014-01-29 05:13:42 - ERROR: failed to build AC100 kernel
TB --- 2014-01-29 05:13:42

[head tinderbox] failure on arm/arm

2014-01-28 Thread FreeBSD Tinderbox 
TB --- 2014-01-29 02:10:29 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2014-01-29 02:10:29 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2014-01-29 02:10:29 - starting HEAD tinderbox run for arm/arm
TB --- 2014-01-29 02:10:29 - cleaning the object tree
TB --- 2014-01-29 02:10:29 - /usr/local/bin/svn stat /src
TB --- 2014-01-29 02:10:37 - At svn revision 261254
TB --- 2014-01-29 02:10:38 - building world
TB --- 2014-01-29 02:10:38 - CROSS_BUILD_TESTING=YES
TB --- 2014-01-29 02:10:38 - MAKEOBJDIRPREFIX=/obj
TB --- 2014-01-29 02:10:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2014-01-29 02:10:38 - SRCCONF=/dev/null
TB --- 2014-01-29 02:10:38 - TARGET=arm
TB --- 2014-01-29 02:10:38 - TARGET_ARCH=arm
TB --- 2014-01-29 02:10:38 - TZ=UTC
TB --- 2014-01-29 02:10:38 - __MAKE_CONF=/dev/null
TB --- 2014-01-29 02:10:38 - cd /src
TB --- 2014-01-29 02:10:38 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Jan 29 02:10:44 UTC 2014
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 World build completed on Wed Jan 29 05:13:39 UTC 2014
TB --- 2014-01-29 05:13:39 - generating LINT kernel config
TB --- 2014-01-29 05:13:39 - cd /src/sys/arm/conf
TB --- 2014-01-29 05:13:39 - /usr/bin/make -B LINT
TB --- 2014-01-29 05:13:39 - cd /src/sys/arm/conf
TB --- 2014-01-29 05:13:39 - /usr/sbin/config -m LINT
TB --- 2014-01-29 05:13:39 - building LINT kernel
TB --- 2014-01-29 05:13:39 - CROSS_BUILD_TESTING=YES
TB --- 2014-01-29 05:13:39 - MAKEOBJDIRPREFIX=/obj
TB --- 2014-01-29 05:13:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2014-01-29 05:13:39 - SRCCONF=/dev/null
TB --- 2014-01-29 05:13:39 - TARGET=arm
TB --- 2014-01-29 05:13:39 - TARGET_ARCH=arm
TB --- 2014-01-29 05:13:39 - TZ=UTC
TB --- 2014-01-29 05:13:39 - __MAKE_CONF=/dev/null
TB --- 2014-01-29 05:13:39 - cd /src
TB --- 2014-01-29 05:13:39 - /usr/bin/make -B buildkernel KERNCONF=LINT
 Kernel build for LINT started on Wed Jan 29 05:13:39 UTC 2014
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
[...]
bmake[1]: /obj/arm.arm/src/sys/LINT/Makefile line 15669: warning: using 
previous script for obio_space.o defined here
machine - /src/sys/arm/include
cc  -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions 
-Wmissing-include-dirs -fdiagnostics-show-option 
-Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -nostdinc -I. -I/src/sys 
-I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/dev/ath 
-I/src/sys/dev/ath/ath_hal -I/src/sys/contrib/dev/ath/ath_hal 
-I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/cxgb 
-I/src/sys/dev/cxgbe -I/src/sys/contrib/libfdt -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-builtin -funwind-tables 
-mllvm -arm-enable-ehabi -ffreestanding /src/sys/arm/arm/genassym.c
In file included from /src/sys/arm/arm/genassym.c:36:
/src/sys/sys/bus.h:585:10: fatal error: 'device_if.h' file not found
#include device_if.h
 ^
1 error generated.
*** Error code 1

Stop.
bmake[1]: stopped in /obj/arm.arm/src/sys/LINT
*** Error code 1

Stop.
bmake: stopped in /src
*** Error code 1

Stop in /src.
TB --- 2014-01-29 05:14:07 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2014-01-29 05:14:07 - ERROR: failed to build LINT kernel
TB --- 2014-01-29 05:14:07 - 8715.72 user 1648.30 system 11017.43 real


http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-arm-arm.full
___
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

Re: Apple Trackpad driver

2014-01-28 Thread Lundberg, Johannes 
This is really good news :)  I will try it on my 2012 and 2013 MBAs soon!
(hopefully it is same hardware as in the pros)

--
Johannes Lundberg
BRILLIANTSERVICE CO., LTD.


On Wed, Jan 29, 2014 at 2:13 PM, Adrian Chadd adr...@freebsd.org wrote:

 holy crap, cool!

 Hans? Any chance we could get this into -HEAD?


 -a


 On 28 January 2014 17:43, Huang Wen Hui huang...@gmail.com 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.gddsn.org.cn/freebsd/wsp-140129.tar.gz,
  I only test it on MBP2012 and MBP2013. Right now the driver have these
  feature:
 
  1. Vertical scrolling with 2 fingers movement,
  2. In firefox, 2 fingers horizontal movement act as page back/forward.
  3. one finger tap act as left mouse click, 2 fingers tap act as right
 mouse
  click, and
  three fingers tap act as middle mouse click.
  4. you also use sysctl to modify some parameters:
  hw.usb.wsp.scale_factor: 12
  hw.usb.wsp.z_factor: 5
  hw.usb.wsp.pressure_touch_threshold: 50
  hw.usb.wsp.pressure_untouch_threshold: 10
  hw.usb.wsp.pressure_tap_threshold: 120
  hw.usb.wsp.scr_hor_threshold: 50
 
  Cheers,
 
  Huang Wen Hui
  ___
  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
 ___
 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


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
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