On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote:
Is there a specif PR to use for ports that fails with clang and does
not specify to use gcc ( devel/cdecl and deskutils/calibre so were
the culprits so far)
There is no specific PR. We have not yet placed the requirement on our
TB --- 2012-09-12 06:10:00 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-09-12 06:10:00 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-09-12
TB --- 2012-09-12 06:10:00 - tinderbox 2.9 running on freebsd-stable.sentex.ca
TB --- 2012-09-12 06:10:00 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE
FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64
TB --- 2012-09-12
On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon lini...@lonesome.com wrote:
For most of the failures, we are already aware of them, as a result of
our periodic runs. So, just filing a PR to say broken on clang doesn't
really help us all that much.
I disagree. Just a tiny bit ;-)
If the PR
On 12 Sep 2012 07:19, Christer Solskogen christer.solsko...@gmail.com
wrote:
On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon lini...@lonesome.com
wrote:
For most of the failures, we are already aware of them, as a result of
our periodic runs. So, just filing a PR to say broken on clang
On Wed, Sep 12, 2012 at 08:00:46AM +0100, Chris Rees wrote:
We don't want thousands of PRs duplicating the information from a simple
list of failures.
Thanks, that was the point I was trying to make.
mcl
___
freebsd-stable@freebsd.org mailing list
Mikolaj Golub wrote:
On Tue, Sep 11, 2012 at 10:16:57PM +0200, Miroslav Lachman wrote:
(gdb) bt
#0 0x000801046cba in refresh_disk_storage_tbl () from
/usr/lib/snmp_hostres.so
#1 0x0008010478bd in refresh_device_tbl () from
/usr/lib/snmp_hostres.so
#2 0x000801047be6 in
How about run automated test on two poudriere setups, one with CLANG set
up, other with USE_GCC=4.2 applied to all ports which marked as broken,
and find in pretty long but relatively easy way ports which should have
USE_GCC=4.2 to survive clang-era, and ports which even with that require a
bit
On Wed, Sep 12, 2012 at 11:54:51AM +0300, Alexander Yerenkow wrote:
How about run automated test on two poudriere setups, one with CLANG set
up, other with USE_GCC=4.2 applied to all ports which marked as broken,
We have been running various tests for quite some time.
Is there somewhere list
On 11/09/2012 22:03, Giulio Ferro wrote:
Well, there definitely seems to be a problem with igb and lagg.
igb alone works as it should, but doesn't seem to work properly in lagg.
To be sure I started from scratch from a 9.0 release with nothing but:
/etc/rc.conf
in src.conf. No problem so far. However I wanted to avoid building base
gcc
( the whole collection ). Is WITHOUT_GCC what I'm looking for?
It probably is. However, WITHOUT_GCC is not supported yet.
On another clang note: Is there a page specifying valid settings for
-march, my
12.09.2012 00:49, Andreas Nilsson wrote:
On another clang note: Is there a page specifying valid settings for
-march, my google-foo is failing me. Ie, I'm looking for the equivalent of
http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
I'm
On Wed, Aug 22, 2012 at 08:02:12PM +0200, Thomas Steen Rasmussen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22-08-2012 18:52, Lars Engels wrote:
On Wed, Aug 22, 2012 at 02:47:09PM +0200, Thomas Steen Rasmussen wrote:
On 22-08-2012 11:33, Lars Engels wrote:
I have a
on 12/09/2012 14:34 Lars Engels said the following:
On Wed, Aug 22, 2012 at 08:02:12PM +0200, Thomas Steen Rasmussen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22-08-2012 18:52, Lars Engels wrote:
On Wed, Aug 22, 2012 at 02:47:09PM +0200, Thomas Steen Rasmussen wrote:
On
on 12/09/2012 15:54 Andriy Gapon said the following:
on 12/09/2012 14:34 Lars Engels said the following:
Meanwhile I found out what's the cause of it. On 9.x it only hung from
time to time, but I tried a few weeks old CURRENT and it hung at every
boot at the same time.
With enabled verbose
Back in July, this error was discussed briefly on the mailing list(s).
It appears that a fix (r238182) was submitted for inclusion in 9.1 (early).
This problem still appears in 9.1-RC1.
Will the fix be included in 9.1-RELEASE (or better yet 9.1-RC2)?
Thanks.
David Boyd.
On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote:
on 12/09/2012 14:34 Lars Engels said the following:
On Wed, Aug 22, 2012 at 08:02:12PM +0200, Thomas Steen Rasmussen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22-08-2012 18:52, Lars Engels wrote:
On Wed,
on 12/09/2012 20:25 Lars Engels said the following:
On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote:
Could you try to play with different eventtimer settings (preferably in
current) ?
You can use this thread / PR as a guide:
On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote:
on 12/09/2012 20:25 Lars Engels said the following:
On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote:
Could you try to play with different eventtimer settings (preferably in
current) ?
You can use this thread / PR
On 12.09.2012 20:46, Lars Engels wrote:
On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote:
on 12/09/2012 20:25 Lars Engels said the following:
On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote:
Could you try to play with different eventtimer settings (preferably in
On 09/11/2012 11:34 PM, Freddie Cash wrote:
On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org
mailto:au...@zirakzigil.org wrote:
Well, there definitely seems to be a problem with igb and lagg.
igb alone works as it should, but doesn't seem to work properly in lagg.
To be
On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro au...@zirakzigil.org wrote:
On 09/11/2012 11:34 PM, Freddie Cash wrote:
On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org
mailto:au...@zirakzigil.org wrote:
Well, there definitely seems to be a problem with igb and lagg.
igb
On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote:
On 12.09.2012 20:46, Lars Engels wrote:
On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote:
on 12/09/2012 20:25 Lars Engels said the following:
On Wed, Sep 12, 2012 at 03:54:30PM +0300, Andriy Gapon wrote:
Could
On 12.09.2012 22:58, Lars Engels wrote:
On Wed, Sep 12, 2012 at 09:58:31PM +0300, Alexander Motin wrote:
On 12.09.2012 20:46, Lars Engels wrote:
On Wed, Sep 12, 2012 at 08:30:36PM +0300, Andriy Gapon wrote:
on 12/09/2012 20:25 Lars Engels said the following:
On Wed, Sep 12, 2012 at
Hi.
I'm running the 9.1-RC1 release.
At the end of the boot sequence, I see:
mps0: mpssas_scsiio_timeout checking sc 0xff8000759000 cm
0xff8000784380
(probe19:mps0:0:19:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 length 0 SMID
240 command timeout cm 0xff8000784380 ccb
On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash fjwc...@gmail.com wrote:
On Wed, Sep 12, 2012 at 12:22 PM, Giulio Ferro au...@zirakzigil.org
wrote:
On 09/11/2012 11:34 PM, Freddie Cash wrote:
On Sep 11, 2012 2:12 PM, Giulio Ferro au...@zirakzigil.org
mailto:au...@zirakzigil.org wrote:
On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel jfvo...@gmail.com wrote:
On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash fjwc...@gmail.com wrote:
Thanks for checking. I've used lagg(4) with igb, just not on 9.x.
You're right, it seems to be pointing to the igb(4) driver in 9.x
compared to 9.0.
On Wed, Sep 12, 2012 at 1:51 PM, Freddie Cash fjwc...@gmail.com wrote:
On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel jfvo...@gmail.com wrote:
On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash fjwc...@gmail.com
wrote:
Thanks for checking. I've used lagg(4) with igb, just not on 9.x.
You're
Zhihao Yuan lich...@gmail.com writes:
Here are many applications using GNU gettext to provide an
internationalized user interface. But I found that there isn't a
BSD-licensed gettext. (so BSD apps do not have internationalization?)
Is there one? Then I can just switch from gettext to that.
igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0
and 9-STABLE on those three boxes.
igb+lagg doesn't work for him on 9.0. Although, I don't recall if
non-LACP options were tried earlier in this thread, or if it's just
the LACP mode that's failing. If one mode
Hi!
9-STABLE has got options GEOM_RAID in GENERIC.
In real world, this change is pretty harmful and there are lots of cases
when 9.0-RELEASE systems upgraded to 9-STABLE fail to mount root UFS filesystem
or attach ZFS.
It seems, there are lots of HDDs supplied with pseudo-RAID labels at the end:
31 matches
Mail list logo
