FreeBSD_HEAD_i386 - Build #2866 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2866/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2866/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2866/console
Change summaries:
298
FreeBSD_HEAD_i386 - Build #2865 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2865/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2865/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/2865/console
Change summaries:
2
On 15/04/2016 14:20, Steven Hartland wrote:
> Prior to Warners commit there was no NCQ TRIM support in FreeBSD, so while it
> was working with standard non-NCQ TRIM (and I can corroborate that as we use
> the
> 840's and 850's all over with ZFS with TRIM enabled) its possible that it
> could
> ca
On Fri, Apr 15, 2016 at 11:49 AM, olli hauer wrote:
> On 2016-04-15 06:19, Warner Losh wrote:
> > On Thu, Apr 14, 2016 at 9:56 PM, Warren Block
> wrote:
> >
> >> On Thu, 14 Apr 2016, Warner Losh wrote:
> >>
> >> The CAM I/O scheduler has been committed to current. This work is
> described
> >>>
On Fri, Apr 15, 2016 at 11:49 AM, olli hauer wrote:
> On 2016-04-15 06:19, Warner Losh wrote:
> > On Thu, Apr 14, 2016 at 9:56 PM, Warren Block
> wrote:
> >
> >> On Thu, 14 Apr 2016, Warner Losh wrote:
> >>
> >> The CAM I/O scheduler has been committed to current. This work is
> described
> >>>
On 15 April 2016 at 09:26, Allan Jude wrote:
> On 2016-04-15 12:13, Maxim Sobolev wrote:
>> Great, work Warner, thanks! Small note, though. The CAM_IOSCHED_NETFLIX
>> seems like a quite poor name for a kernel option. IMHO there is no good
>> reason for polluting it with the name of the company tha
On Fri, Apr 15, 2016 at 10:30 AM, Warner Losh wrote:
>
>
> On Fri, Apr 15, 2016 at 11:25 AM, Maxim Sobolev
> wrote:
>
>> Conrad, yes, you can, but sticking it into FreeBSD source tree IMHO
>> restricts your options somewhat. If it's your private code you can easily
>> put F-world into it and nob
On 2016-04-15 06:19, Warner Losh wrote:
> On Thu, Apr 14, 2016 at 9:56 PM, Warren Block wrote:
>
>> On Thu, 14 Apr 2016, Warner Losh wrote:
>>
>> The CAM I/O scheduler has been committed to current. This work is described
>>> in https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the
On Fri, Apr 15, 2016 at 11:25 AM, Maxim Sobolev wrote:
> Conrad, yes, you can, but sticking it into FreeBSD source tree IMHO
> restricts your options somewhat. If it's your private code you can easily
> put F-world into it and nobody obviously cares apart from your co-workers
> and your boss. Wou
Conrad, yes, you can, but sticking it into FreeBSD source tree IMHO
restricts your options somewhat. If it's your private code you can easily
put F-world into it and nobody obviously cares apart from your co-workers
and your boss. Would probably be considered highly inappropriate by most to
merge i
On 15 April 2016 at 17:22, Conrad Meyer wrote:
If you implement a new IO scheduler you can name it whatever you like.
> "NG" isn't any more meaningful than "Netflix."
>
True, but _NETFLIX as a suffix is bad for three reasons:
1st- it creates a precedent for every sponsoring co. to want their n
On Wed, Apr 12, 2016 at 11:01PM, Paul Wootton wrote:
>On Tue, Apr 12, 2016 at 02:02PM, Paul Wootton wrote:
>
>With the help of Konstantin, I have got a proper disassembly.
>
>I have recompiled a few times so my new panic is
>instruction pointer = 0x20:0x80fed2d9
>stack pointer
Max,
If you implement a new IO scheduler you can name it whatever you like.
"NG" isn't any more meaningful than "Netflix."
Best,
Conrad
On Fri, Apr 15, 2016 at 9:13 AM, Maxim Sobolev wrote:
> Great, work Warner, thanks! Small note, though. The CAM_IOSCHED_NETFLIX
> seems like a quite poor name
On Fri, Apr 15, 2016 at 10:26 AM, Allan Jude wrote:
> On 2016-04-15 12:13, Maxim Sobolev wrote:
> > Great, work Warner, thanks! Small note, though. The CAM_IOSCHED_NETFLIX
> > seems like a quite poor name for a kernel option. IMHO there is no good
> > reason for polluting it with the name of the
On 2016-04-15 12:13, Maxim Sobolev wrote:
> Great, work Warner, thanks! Small note, though. The CAM_IOSCHED_NETFLIX
> seems like a quite poor name for a kernel option. IMHO there is no good
> reason for polluting it with the name of the company that sponsored the
> development. I don't think we hav
Great, work Warner, thanks! Small note, though. The CAM_IOSCHED_NETFLIX
seems like a quite poor name for a kernel option. IMHO there is no good
reason for polluting it with the name of the company that sponsored the
development. I don't think we have any precedents of doing this unless the
option i
Hi,
Great news!
usually I read your emails going to freebad-net/jails but seems i missed
this.
I remmember Roman(?) went over and tried to patch current viamge against
open PRs but somewhere the work stopped (or maybe i mssed this too :).
is there some patch to test?
Thanks for your hard work.
Sam
On Fri, 15 Apr 2016 07:29:23 -0600
Warner Losh wrote:
> Do you have this problem w/o CAM_NETFLIX_IOSCHED?
I not have problem without option CAM_NETFLIX_IOSCHED.
>
> What version of virtualbox? I've not booted with that in 3 years.
virtualbox-ose-4.3.36
>
> Warner
>
> On Fri, Apr 15, 2016 a
> On 15 Apr 2016, at 15:32 , Sami Halabi wrote:
>
> Hi,
> Myabe i missed something... what isbthe work about? is it about stabilizimg
> current viamge or something else?
Yes more stable top-down-teardown and reducing the possible memory leaks.
/bz
__
Hi,
Myabe i missed something... what isbthe work about? is it about stabilizimg
current viamge or something else?
Sami
בתאריך 15 באפר׳ 2016 18:24, "Bjoern A. Zeeb" <
bzeeb-li...@lists.zabbadoz.net> כתב:
>
> > On 15 Apr 2016, at 13:49 , Ernie Luzar wrote:
> >
> > Is the VIMAGE revamp by "Bjoern
> On 15 Apr 2016, at 13:49 , Ernie Luzar wrote:
>
> Is the VIMAGE revamp by "Bjoern A. Zeeb” completed and is it going to be
> included in 11.0?
It’s not completed yet but I’ll try to make sure as much as possible will be in
HEAD before the code slush date.
Bjoern
__
On Fri, Apr 15, 2016 at 05:11:54PM +0300, Vladimir Zakharov wrote:
> On Fri, Apr 15, 2016, Konstantin Belousov wrote:
> > On Fri, Apr 15, 2016 at 02:38:18PM +0300, Vladimir Zakharov wrote:
> > > On Fri, Apr 15, 2016, Konstantin Belousov wrote:
> > > > On Fri, Apr 15, 2016 at 01:26:44PM +0300, Vladi
On Fri, Apr 15, 2016 at 7:51 AM, O. Hartmann
wrote:
> On Thu, 14 Apr 2016 22:19:23 -0600
> Warner Losh wrote:
>
> > On Thu, Apr 14, 2016 at 9:56 PM, Warren Block
> wrote:
> >
> > > On Thu, 14 Apr 2016, Warner Losh wrote:
> > >
> > > The CAM I/O scheduler has been committed to current. This work
On Fri, Apr 15, 2016, Konstantin Belousov wrote:
> On Fri, Apr 15, 2016 at 02:38:18PM +0300, Vladimir Zakharov wrote:
> > On Fri, Apr 15, 2016, Konstantin Belousov wrote:
> > > On Fri, Apr 15, 2016 at 01:26:44PM +0300, Vladimir Zakharov wrote:
> > > > Hello
> > > >
> > > > Setting 'kern.eventtimer
On Thu, 14 Apr 2016 22:19:23 -0600
Warner Losh wrote:
> On Thu, Apr 14, 2016 at 9:56 PM, Warren Block wrote:
>
> > On Thu, 14 Apr 2016, Warner Losh wrote:
> >
> > The CAM I/O scheduler has been committed to current. This work is
> > described
> >> in https://people.freebsd.org/~imp/bsdcan2015
Glen Barber wrote:
As many are aware, one of the major user-facing changes to FreeBSD in
11.0-RELEASE is packaging the base system with pkg(8). Originally, the
11.0-RELEASE code slush was scheduled to start on April 22, 2016, which
is only a week away at this point.
With the packaged base syste
On Fri, Apr 15, 2016 at 12:00 AM, Gerrit Kühn
wrote:
> On Thu, 14 Apr 2016 22:19:23 -0600 Warner Losh wrote
> about Re: Heads up:
>
> WL> Crucial/Micron M500 (all firmware prior to MU07)
>
> I have a couple of these. Where can I get the latest firmware? On
> http://www.crucial.com/usa/en/support
Do you have this problem w/o CAM_NETFLIX_IOSCHED?
What version of virtualbox? I've not booted with that in 3 years.
Warner
On Fri, Apr 15, 2016 at 2:44 AM, Ivan Klymenko wrote:
> On Thu, 14 Apr 2016 16:42:33 -0600
> Warner Losh wrote:
>
> > The CAM I/O scheduler has been committed to current.
> On Apr 15, 2016, at 7:14 AM, Tommi Pernila wrote:
>
> Hi,
>
> On Friday, 15 April 2016, Steven Hartland wrote:
>
>> On 15/04/2016 09:11, Kurt Jaeger wrote:
>>
>>> Hi!
>>>
>>> avg wrote:
>>>
For what it's worth, I have been using the following SSDs since
September of 2015 :
On Fri, Apr 15, 2016 at 02:06:43PM +0100, Paul Wootton wrote:
> On Wed, Apr 12, 2016 at 11:01PM, Paul Wootton wrote:
> >On Tue, Apr 12, 2016 at 02:02PM, Paul Wootton wrote:
> >
> >With the help of Konstantin, I have got a proper disassembly.
> >
> >I have recompiled a few times so my new panic is
>
Hi,
On Friday, 15 April 2016, Steven Hartland wrote:
> On 15/04/2016 09:11, Kurt Jaeger wrote:
>
>> Hi!
>>
>> avg wrote:
>>
>>> For what it's worth, I have been using the following SSDs since
>>> September of 2015 :
>>>
>>> ada2: ACS-2 ATA SATA 3.x device
>>> ada3: ACS-2 ATA SATA 3.x device
>>
On Fri, Apr 15, 2016 at 02:38:18PM +0300, Vladimir Zakharov wrote:
> On Fri, Apr 15, 2016, Konstantin Belousov wrote:
> > On Fri, Apr 15, 2016 at 01:26:44PM +0300, Vladimir Zakharov wrote:
> > > Hello
> > >
> > > Setting 'kern.eventtimer.periodic = 1' in /etc/sysctl.conf leads to
> > > GENERIC-NOD
On Fri, Apr 15, 2016, Vladimir Zakharov wrote:
> $ kgdb /boot/kernel/kernel
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain co
On Fri, Apr 15, 2016, Konstantin Belousov wrote:
> On Fri, Apr 15, 2016 at 01:26:44PM +0300, Vladimir Zakharov wrote:
> > Hello
> >
> > Setting 'kern.eventtimer.periodic = 1' in /etc/sysctl.conf leads to
> > GENERIC-NODEBUG panic. GENERIC loads without problems.
> > So do GENERIC-NODEBUG as of r29
On 15/04/2016 09:11, Kurt Jaeger wrote:
Hi!
avg wrote:
For what it's worth, I have been using the following SSDs since September of
2015 :
ada2: ACS-2 ATA SATA 3.x device
ada3: ACS-2 ATA SATA 3.x device
I have one in use with zfs and trim:
ada1: ACS-2 ATA SATA 3.x device
Works as my por
On Fri, Apr 15, 2016 at 01:26:44PM +0300, Vladimir Zakharov wrote:
> Hello
>
> Setting 'kern.eventtimer.periodic = 1' in /etc/sysctl.conf leads to
> GENERIC-NODEBUG panic. GENERIC loads without problems.
> So do GENERIC-NODEBUG as of r297245.
>
> https://imgur.com/0DtDU3m
>
> $ uname -a
>
> Fre
Hello
Setting 'kern.eventtimer.periodic = 1' in /etc/sysctl.conf leads to
GENERIC-NODEBUG panic. GENERIC loads without problems.
So do GENERIC-NODEBUG as of r297245.
https://imgur.com/0DtDU3m
$ uname -a
FreeBSD vzakharov 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r298037: Fri Apr
15 12:27:40 MSK 2016
On Thu, 14 Apr 2016 16:42:33 -0600
Warner Losh wrote:
> The CAM I/O scheduler has been committed to current. This work is
> described in
> https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the
> default scheduler doesn't change the default (old) behavior.
>
> One possible issue, h
Hi!
avg wrote:
> For what it's worth, I have been using the following SSDs since September of
> 2015 :
>
> ada2: ACS-2 ATA SATA 3.x device
> ada3: ACS-2 ATA SATA 3.x device
I have one in use with zfs and trim:
ada1: ACS-2 ATA SATA 3.x device
Works as my ports build hosts, and is fine as fa
On 15/04/2016 07:19, Warner Losh wrote:
> Samsung 830 all firmware
> Samsung 840 all firmware
> Samsung 850 all firmware
>
> All of these are at least 18 months old (if not older). There's some
> confusing in Linux lists on
> the full impact of the Samsung drives (there was a bug in the Linux
> im
On 2016-Apr-14, at 1:41 PM, Bryan Drewery wrote:
> . . .Please try this patch though:
>
> https://people.freebsd.org/~bdrewery/patches/libcompat-xcpp.diff
So far so good. . .
TARGET_ARCH=amd64 hosted on amd64: buildworld/buildkernel built without
reporting any errors.
TARGET_ARCH=armv6 host
41 matches
Mail list logo
