Hi all,
On behalf of monthly@, I would like to inform you that the next
submission date for the January to March quarterly status reports is
April 21st, 2013 - less than a month away.
They don't have to be very long - anything that lets people know what
is going on inside FreeBSD is useful. Note
When I put MALLOC_PRODUCTION=yes in /etc/make/conf, make buildworld hangs
with error
/usr/src/lib/libc/stdlib/
malloc.c:126:1: error: "MALLOC_PRODUCTION" redefined
: error: this is the location of the previous definition
This is a patch, which avoid this error
--- /usr/src/lib/libc/stdlib/Makefil
On Tue, 2013-04-02 at 14:28 +0300, Dmitry Luhtionov wrote:
> When I put MALLOC_PRODUCTION=yes in /etc/make/conf, make buildworld hangs
> with error
> /usr/src/lib/libc/stdlib/
> malloc.c:126:1: error: "MALLOC_PRODUCTION" redefined
> : error: this is the location of the previous definition
>
> This
Am 31.03.2013 23:02, schrieb Scott Long:
> So what I hear you and Matthias saying, I believe, is that it should be
> easier to
> force disks to fall back to non-NCQ mode, and/or have a more responsive
> black-list for problematic controllers. Would this help the situation? It's
> hard to
> jus
Am 01.04.2013 17:07, schrieb Stefan Esser:
> Am 01.04.2013 15:14, schrieb Victor Balada Diaz:
>> Being able to configure quirks from loader.conf for disks AND controllers
>> would be great
>> and is not hard to do. If you want i can do a patch in two weeks and send it
>> to you. That
>> way it's
On Saturday, March 23, 2013 11:11:20 pm Eric van Gyzen wrote:
> At work, we discovered that our application's IPMI thread would often
> use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC,
> so it can run without sleeping for a "long" time with a slow BMC. It
> also holds the
On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote:
> Hi.
>
> On one of my fresh installed servers I am seeing the following output during
boot:
>
> gptzfsboot: error 4 lba 30
> gptzfsboot: error 4 lba 31
> gptzfsboot: error 4 lba 31
> gptzfsboot: error 4 lba 31
> gptzfsboot: error 4 lba 30
On 23 March 2013 20:11, Eric van Gyzen wrote:
> At work, we discovered that our application's IPMI thread would often use a
> lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so it can
> run without sleeping for a "long" time with a slow BMC. It also holds the
> ipmi_softc.ipmi_lo
Finally have all working as expected. I finally just erased sources and
ports, rebuilt and restarted freebsd and I'm finally ok.
Lowell, thanks for your support and suggestions. I will now try to forget
all csup, cvsup, etc. Thank goodness that portmaster still handles ports
as always and svn
On Tue, Apr 02, 2013 at 08:15:40PM -0500, Edwin L. Culp W. wrote:
> Finally have all working as expected. I finally just erased sources and
> ports, rebuilt and restarted freebsd and I'm finally ok.
>
> Lowell, thanks for your support and suggestions. I will now try to forget
> all csup, cvsup,
On Tue, 2 Apr 2013 17:07:14 -0400
John Baldwin wrote:
> On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote:
> > Hi.
> >
> > On one of my fresh installed servers I am seeing the following
> > output during
> boot:
> >
> > gptzfsboot: error 4 lba 30
...
> > gptzfsboot: error 4 lba 31
>
> H
on 03/04/2013 09:12 Sergey V. Dyatko said the following:
> On Tue, 2 Apr 2013 17:07:14 -0400
> John Baldwin wrote:
>
>> On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote:
>>> Hi.
>>>
>>> On one of my fresh installed servers I am seeing the following
>>> output during
>> boot:
>>>
>>> gptzf
12 matches
Mail list logo
