Re: x11/nvidia-driver (340.24/340.32/343.13): nvidia BLOB doesn't recognize any display socket on Lenovo E540/UEFI and FBSD CURRENT

Am Sat, 20 Sep 2014 09:21:34 -0500 Larry Rosenman schrieb: > On 2014-09-20 09:10, O. Hartmann wrote: > > Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT) > > Warren Block schrieb: > > > >> On Fri, 19 Sep 2014, O. Hartmann wrote: > >> > >> > nVidia's BLOB from port x11/nvidia-driver seems to have probl

zpool frag

FRAG means fragmentation, right? Zpool fragmentation? That's news to me. If this is real how do I fix it? NAME SIZE ALLOC FREE FRAG EXPANDSZCAP DEDUP HEALTH ALTROOT pool1 75.5G 53.7G 21.8G60% -71% 1.00x ONLINE - pool2 48.8G 26.2G 22.6G68%

Jenkins build is back to normal : FreeBSD_HEAD #1502

See ___ 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: zpool frag

Backup the pool and restore it is the only way I'm aware of. - Original Message - From: "Beeblebrox" To: Sent: Sunday, September 21, 2014 9:57 AM Subject: zpool frag FRAG means fragmentation, right? Zpool fragmentation? That's news to me. If this is real how do I fix it? NAME

Re: zpool frag

On 2014-09-21 04:57, Beeblebrox wrote: > FRAG means fragmentation, right? Zpool fragmentation? That's news to me. If > this is real how do I fix it? > > NAME SIZE ALLOC FREE FRAG EXPANDSZCAP DEDUP HEALTH ALTROOT > pool1 75.5G 53.7G 21.8G60% -71% 1.00x ONL

[patch] syscons/vt keymap: Norwegian country code conflicts with default value

Hi, Recent changes in keymap namning for syscons/vt to use shorter names has exposed a conflict with the value "no" both used as country code for Norway and as a default value indicating that no keymap is set. The attached patch proposes to use "" (empty string) as default value instead. Also av

Re: zpool frag

On Sunday, September 21, 2014 11:06:10 AM Allan Jude wrote: > On 2014-09-21 04:57, Beeblebrox wrote: > > FRAG means fragmentation, right? Zpool fragmentation? That's news to me. > > If > > this is real how do I fix it? > > > > NAME SIZE ALLOC FREE FRAG EXPANDSZCAP DEDUP HEALTH >

Re: zpool frag

- Original Message - From: "Peter Wemm" On Sunday, September 21, 2014 11:06:10 AM Allan Jude wrote: > On 2014-09-21 04:57, Beeblebrox wrote: > > FRAG means fragmentation, right? Zpool fragmentation? That's news to me. > > If > > this is real how do I fix it? > > > > NAME SIZE AL

Re: zpool frag

On Sunday, September 21, 2014 06:12:09 PM Steven Hartland wrote: > - Original Message - > > > From: "Peter Wemm" > > > > On Sunday, September 21, 2014 11:06:10 AM Allan Jude wrote: > > > On 2014-09-21 04:57, Beeblebrox wrote: > > > > FRAG means fragmentation, right? Zpool fragmentation?

Re: zpool frag

On 2014-09-21 13:39, Peter Wemm wrote: > On Sunday, September 21, 2014 06:12:09 PM Steven Hartland wrote: >> - Original Message - >> >>> From: "Peter Wemm" >>> >>> On Sunday, September 21, 2014 11:06:10 AM Allan Jude wrote: On 2014-09-21 04:57, Beeblebrox wrote: > FRAG means fragm

Re: [HEADSUP] pkg(8) is now the only package management tool

Michelle Sullivan wrote: > Baptiste Daroussin wrote: > >> Hi all, >> >> The ports tree has been modified to only support pkg(8) as package management >> system for all supported version of FreeBSD. >> >> if you were still using pkg_install (pkg_* tools) you will have to upgrade >> your >> syste

Intel SoC's

I got 2 Intel SoC's at the Intel IOT Hackathon here in Austin this weekend. They are both I586/Pentium processors, with some other stuff hanging out. They currently run Yactoh Linux. I'm wondering how hard it would be to get FreeBSD up on them They are the Galileo Gen 2, and Edison boar

Re: libthr and main thread stack size

On Sep 20, 2014, at 11:06 AM, Konstantin Belousov wrote: > On Fri, Sep 19, 2014 at 03:27:25PM -0400, John Baldwin wrote: >> I suspect it was done out of reasons of being overly conservative in >> interpreting RLIMIT_STACK. I think it is quite surprising behavior >> though and would rather we make

Does the xHCI driver has a spec violation?

Hi, I encountered a issue for USB mic. In fist time, my host controller (xHCI) sends single IN-tokens every 8-SOFs. This is expected action. But, after I open, close and open, my host controller sends plural IN-tokens between SOF and SOF. In Intel Lynx Point, I could not reproduce this issue. I'

Re: Does the xHCI driver has a spec violation?

On 09/22/14 06:58, Kohji Okuno wrote: Hi, I encountered a issue for USB mic. In fist time, my host controller (xHCI) sends single IN-tokens every 8-SOFs. This is expected action. But, after I open, close and open, my host controller sends plural IN-tokens between SOF and SOF. In Intel Lynx Poi

Re: Does the xHCI driver has a spec violation?

Hi HPS, Could you refer to the following document (4.6.6 Configure Endpoint:P.99)? This document shows: If the Drop Context flag is `1' and the Add Context flag is `1', the xHC shall: o Release the current Resources and Bandwidth allocated to the endpoint and assign the new Resources and Bandwi

Re: Does the xHCI driver has a spec violation?

On 09/22/14 08:31, Kohji Okuno wrote: Hi HPS, Could you refer to the following document (4.6.6 Configure Endpoint:P.99)? This document shows: If the Drop Context flag is `1' and the Add Context flag is `1', the xHC shall: o Release the current Resources and Bandwidth allocated to the endpoin

Re: Does the xHCI driver has a spec violation?

> On 09/22/14 08:31, Kohji Okuno wrote: >> Hi HPS, >> >> Could you refer to the following document (4.6.6 Configure Endpoint:P.99)? >> This document shows: >> >> If the Drop Context flag is `1' and the Add Context flag is `1', the xHC >> shall: >> o Release the current Resources and Bandwidth alloc