On Sat, Aug 24, 2013 at 09:35:12AM +0800, Julian Elischer wrote:
> On 8/24/13 3:23 AM, Mark Felder wrote:
> > On Fri, Aug 23, 2013, at 13:20, Julian Elischer wrote:
> >> On 8/23/13 7:55 PM, Poul-Henning Kamp wrote:
> >>> In message <52174d51.2050...@digsys.bg>, Daniel Kalchev writes:
> >>>
> >
On 23 Aug 2013, at 13:30, Bernhard Fröhlich wrote:
> lang/gcc42 is on the list of ports that have USE_GCC=any. So you would need
> to fix it first to be able to compile it with clang 3.3 from base.
What is the issue with the gcc 4.2.1 build (aside from the fact that it has a
terrifying number o
On 24 Aug 2013, at 02:35, Julian Elischer wrote:
> I don't know.. whatever RootBSD run, but the fact that I needed gcc for
> anything suggests that we should keep it around for a while.
Please point to the FreeBSD PRs and clang bug reports that you have filed about
this. I have been running a
On 23 Aug 2013, at 23:37, Warner Losh wrote:
> I'd dispute the 'and surely it seems like it does' part of this. Non x86
> architectures will continue to use gcc because clang just isn't ready at this
> time for them. Some are very close (arm), some are close (powerpc64, mips*),
> some are no w
> If the 150 ports that only work with gcc, all work with a ports
> > gcc and do not need the gcc from base, would the following be OK ?
> >
> > - 9.x gcc default and clang in base;
> > - 10.x clang default and gcc in ports;
>
> Well, we write rules and we brake them. ;-)
>
> Just say that we know
On 24 Aug 2013, at 11:30, "Sam Fourman Jr." wrote:
> So I vote, let's not give ourselves the burden of "lugging" dead weight in
> base
> for another 5 years. (in 2017 do we still want to be worrying about gcc in
> base?)
Perhaps more to the point, in 2017 do we want to be responsible for maintai
On 08/23/13 23:14, Ivan Klymenko wrote:
wing error:
http://privatepaste.com/46f9477022
Not sure if this helps:
https://wiki.freebsd.org/PkgPrimer
Using portbuilder inside a jail
When building 9-stable ports in a 9-stable jail under -current you might
want to set the UNAME_r enviroment varia
Hi,
I'm having problems with frequent disconnects of my AirLive WL-1600USB
hardware. After this happens the all reconnects fail and the only way
to fix it is to reboot the machine, while reboot I get this kernel
panic:
http://people.freebsd.org/~pawel/urtw-panic.jpg
Sadly when I get to this my U
Hi,
For some time now I get this:
[corn:~]> route get
route: writing to routing socket: Invalid argument
Is this just my build or anyone can confirm this?
--
pozdrawiam / with regards
Paweł Pękala
___
freebsd-current@freebsd.org mailing list
http://l
On Sat, Aug 24, 2013 at 06:30:24AM -0400, Sam Fourman Jr. wrote:
> > If the 150 ports that only work with gcc, all work with a ports
>
> > > gcc and do not need the gcc from base, would the following be OK ?
> > >
> > > - 9.x gcc default and clang in base;
> > > - 10.x clang default and gcc in po
On 24 Aug 2013, at 12:51, Slawa Olhovchenkov wrote:
> Oh, I remember. mplayer on i386 can't be builded witch clang -- clang
> don't understand inlined asm.
Clang supports inline asm. If there is some specific inline asm syntax that
clang does not recognise, then please will you point me to the
> In my opinion this just needs to happen, if ports break, we deal with that
> > on a case by case basis.
>
> Oh, I remember. mplayer on i386 can't be builded witch clang -- clang
> don't understand inlined asm.
>
>
Well, in this case, you would just have the mplayer maintainer configure the
port
On Sat, Aug 24, 2013 at 12:11:16PM +, Sam Fourman Jr. wrote:
> > In my opinion this just needs to happen, if ports break, we deal with that
>
> > > on a case by case basis.
> >
> > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang
> > don't understand inlined asm.
> >
> >
On Sat, Aug 24, 2013 at 2:42 PM, Pawel Pekala wrote:
> Hi,
>
> For some time now I get this:
>
> [corn:~]> route get
> route: writing to routing socket: Invalid argument
>
> Is this just my build or anyone can confirm this?
>
> --
> pozdrawiam / with regards
> Paweł Pękala
Nothing wrong there, yo
В Sat, 24 Aug 2013 13:26:01 +0200
Hans Petter Selasky пишет:
> On 08/23/13 23:14, Ivan Klymenko wrote:
> > wing error:
> > http://privatepaste.com/46f9477022
>
> Not sure if this helps:
>
> https://wiki.freebsd.org/PkgPrimer
>
> Using portbuilder inside a jail
>
> When building 9-stable ports
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.08.2013 00:54, Adrian Chadd wrote:
> Hi,
>
> I'd like to commit this to -10. It migrates the if_lagg locking
> from a rw lock to a rm lock. We see a bit of contention between the
> transmit and
We're running lagg with rmlock on several hundred h
В Sat, 24 Aug 2013 13:26:01 +0200
Hans Petter Selasky пишет:
> On 08/23/13 23:14, Ivan Klymenko wrote:
> > wing error:
> > http://privatepaste.com/46f9477022
>
> Not sure if this helps:
>
> https://wiki.freebsd.org/PkgPrimer
>
> Using portbuilder inside a jail
>
> When building 9-stable ports
On Sat, 24 Aug 2013, Alexander V. Chernikov wrote:
On 24.08.2013 00:54, Adrian Chadd wrote:
I'd like to commit this to -10. It migrates the if_lagg locking
from a rw lock to a rm lock. We see a bit of contention between the
transmit and
We're running lagg with rmlock on several hundred heavi
TB --- 2013-08-24 13:30:16 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 13:30:16 - 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 --- 2013
On 8/24/13 7:19 PM, David Chisnall wrote:
On 24 Aug 2013, at 11:30, "Sam Fourman Jr." wrote:
So I vote, let's not give ourselves the burden of "lugging" dead weight in
base
for another 5 years. (in 2017 do we still want to be worrying about gcc in
base?)
Perhaps more to the point, in 2017 do
On 8/24/13 3:41 PM, Roman Divacky wrote:
On Sat, Aug 24, 2013 at 09:35:12AM +0800, Julian Elischer wrote:
On 8/24/13 3:23 AM, Mark Felder wrote:
On Fri, Aug 23, 2013, at 13:20, Julian Elischer wrote:
On 8/23/13 7:55 PM, Poul-Henning Kamp wrote:
In message <52174d51.2050...@digsys.bg>, Daniel
Hello,
regarding this PR I made some further observation. Even the
acpi_ec_write seems to not have any effect on the brightness, the values
set to the appropriate register (IBM_EC_BRIGHTNESS 0x31) survive a
reboot.
Looks like the values are stored correctly, but EC doesn't care for them
w
On Sat, Aug 24, 2013 at 01:10:46PM +0100, David Chisnall wrote:
> On 24 Aug 2013, at 12:51, Slawa Olhovchenkov wrote:
>
> > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang
> > don't understand inlined asm.
>
> Clang supports inline asm. If there is some specific inline as
On Aug 24, 2013, at 4:05 AM, David Chisnall wrote:
> On 23 Aug 2013, at 23:37, Warner Losh wrote:
>
>> I'd dispute the 'and surely it seems like it does' part of this. Non x86
>> architectures will continue to use gcc because clang just isn't ready at
>> this time for them. Some are very clos
On Aug 24, 2013, at 6:11 AM, Sam Fourman Jr. wrote:
>> In my opinion this just needs to happen, if ports break, we deal with that
>
>>> on a case by case basis.
>>
>> Oh, I remember. mplayer on i386 can't be builded witch clang -- clang
>> don't understand inlined asm.
>>
>>
> Well, in this
Sorry, I meant "line contention" rather than "lock contention". Yes, you're
right.
-adrian
On 24 August 2013 07:16, Robert Watson wrote:
> On Sat, 24 Aug 2013, Alexander V. Chernikov wrote:
>
> On 24.08.2013 00:54, Adrian Chadd wrote:
>>
>>>
>>> I'd like to commit this to -10. It migrates
.. well, where'd you point it to?
-adrian
On 23 August 2013 23:04, Hideki Yamamoto wrote:
> Hi,
>
> I solved my problem by myself.
> I update PACKAGESITE in /usr/local/etc/pkg.conf in accordance with
> the information in another expert web site.
>
> ---
>
>
>
> 2013/8/24 Hideki Yamamoto
>
>
You know, I could be a total jerk and say:
"If you push gcc out to a port, and you have the 'external compiler'
toolchain support working correctly enough to build with this, why don't we
just push clang out to a port, and be done with it?"
... just saying.
-adrian
TB --- 2013-08-24 13:52:52 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 13:52:52 - 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 --- 2013
On 8/24/13 7:16 AM, Robert Watson wrote:
On Sat, 24 Aug 2013, Alexander V. Chernikov wrote:
On 24.08.2013 00:54, Adrian Chadd wrote:
I'd like to commit this to -10. It migrates the if_lagg locking
from a rw lock to a rm lock. We see a bit of contention between the
transmit and
We're running
On 8/24/13 9:33 AM, Adrian Chadd wrote:
You know, I could be a total jerk and say:
"If you push gcc out to a port, and you have the 'external compiler'
toolchain support working correctly enough to build with this, why don't we
just push clang out to a port, and be done with it?"
... just sayin
According to Adrian Chadd:
> .. well, where'd you point it to?
On my own machine I generate the packages myself with poudriere because I have
multiple jails I update. On a more generic machine, I use pkg-test.freebsd.org.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.f
On 24 Aug 2013, at 17:36, Alfred Perlstein wrote:
>> We should distinguish "lock contention" from "line contention". When
>> acquiring a rwlock on multiple CPUs concurrently, the cache lines used to
>> implement the lock are contended, as they must bounce between caches via the
>> cache cohere
On 24/08/2013 17:08, Matthias Petermann wrote:
> regarding this PR I made some further observation. Even the acpi_ec_write
> seems to not have any effect on the brightness, the values set to the
> appropriate register (IBM_EC_BRIGHTNESS 0x31) survive a reboot.
My LCD brightness control stopped
On 8/24/13 10:47 AM, Robert N. M. Watson wrote:
On 24 Aug 2013, at 17:36, Alfred Perlstein wrote:
We should distinguish "lock contention" from "line contention". When acquiring a rwlock
on multiple CPUs concurrently, the cache lines used to implement the lock are contended, as they must bounce
On 08/24/13 02:14, Hans Petter Selasky wrote:
On 08/24/13 02:44, George Mitchell wrote:
On 08/23/13 07:11, George Mitchell wrote:
On 08/23/13 02:18, Hans Petter Selasky wrote:
On 08/23/13 02:29, George Mitchell wrote:
On 08/22/13 07:34, Hans Petter Selasky wrote:
Give that the printer wo
Am 24.08.2013 20:02, schrieb Dominic Fandrey:
My LCD brightness control stopped working when I switched to NEW_XORG
with Intel KMS (on stable/9).
It's the same issue when I run in console only mode (without Xorg,
without KMS kernel module loaded).
What Lenovo model are you using?
___
Hihi,
There's two parts to my patch:
* one is migrating the rwlock to rmlock - not because of counters, but
because the lock is protecting consistency when changing the lagg config
* one is adding a new lock specifically to ensure that the callout is
atomically created/called/destroyed
The latte
On Sat, Aug 24, 2013 at 01:05:13AM +0400, Slawa Olhovchenkov wrote:
> On Fri, Aug 23, 2013 at 06:54:44AM -0700, Adrian Chadd wrote:
>
> > Hi!
> >
> > If firewire code doesn't build on clang correctly, have you filed a bug so
> > it gets looked at before 10.0 is released? that's pretty broken
> >
On Sat, Aug 24, 2013 at 12:33 PM, Adrian Chadd wrote:
> You know, I could be a total jerk and say:
>
> "If you push gcc out to a port, and you have the 'external compiler'
> toolchain support working correctly enough to build with this, why don't we
> just push clang out to a port, and be done wi
TB --- 2013-08-24 18:00:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 18:00:20 - 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 --- 2013
TB --- 2013-08-24 18:00:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 18:00:20 - 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 --- 2013
On Aug 24, 2013, at 3:04 PM, Sam Fourman Jr. wrote:
>
>
>
> On Sat, Aug 24, 2013 at 12:33 PM, Adrian Chadd wrote:
> You know, I could be a total jerk and say:
>
> "If you push gcc out to a port, and you have the 'external compiler'
> toolchain support working correctly enough to build with t
TB --- 2013-08-24 18:00:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 18:00:20 - 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 --- 2013
On Aug 24, 2013, at 12:14 PM, Alfred Perlstein wrote:
> On 8/24/13 10:47 AM, Robert N. M. Watson wrote:
>> On 24 Aug 2013, at 17:36, Alfred Perlstein wrote:
>>
We should distinguish "lock contention" from "line contention". When
acquiring a rwlock on multiple CPUs concurrently, the c
Hello,
regarding the issue mentioned in the subject (Lenovo Thinkpad X121e not
able to resume after suspend to ram) there is finally some progress. I
found this few months old discussion[1] on freebsd-acpi (related to
Thinkpad X201):
"I had a similar problem. After syncing with FreeBSD 10-CU
TB --- 2013-08-24 18:00:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 18:00:20 - 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 --- 2013
TB --- 2013-08-24 21:26:46 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 21:26:46 - 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 --- 2013
On Sat, Aug 24, 2013 at 07:42:17PM +0400, Slawa Olhovchenkov wrote:
> On Sat, Aug 24, 2013 at 01:10:46PM +0100, David Chisnall wrote:
>
> > On 24 Aug 2013, at 12:51, Slawa Olhovchenkov wrote:
> >
> > > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang
> > > don't understand
On 24 Aug 2013, at 23:42, Slawa Olhovchenkov wrote:
> And i found PR about clang and mplayer: ports/176272
> This PR contains log with build error log.
Please file clang bugs at http://llvm.org/bugs/
David
signature.asc
Description: Message signed with OpenPGP using GPGMail
Both full core.txt's are available at:
http://www.lerctr.org/~ler/FreeBSD/
borg.lerctr.org dumped core - see /var/crash/vmcore.0
Sat Aug 24 17:35:31 CDT 2013
FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r254807: Sat Aug
24 16:52:42 CDT 2013 r...@borg.lerctr.org:/usr/obj/
TB --- 2013-08-24 21:13:27 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 21:13:27 - 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 --- 2013
TB --- 2013-08-24 22:01:41 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 22:01:41 - 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 --- 2013
On Sat, Aug 24, 2013 at 11:44:38PM +0100, David Chisnall wrote:
> On 24 Aug 2013, at 23:42, Slawa Olhovchenkov wrote:
>
> > And i found PR about clang and mplayer: ports/176272
> > This PR contains log with build error log.
>
> Please file clang bugs at http://llvm.org/bugs/
>
As if this is go
TB --- 2013-08-24 23:04:44 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 23:04:44 - 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 --- 2013
TB --- 2013-08-24 21:04:52 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 21:04:52 - 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 --- 2013
TB --- 2013-08-24 22:29:46 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 22:29:46 - 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 --- 2013
TB --- 2013-08-24 23:04:23 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-24 23:04:23 - 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 --- 2013
And another:
borg.lerctr.org dumped core - see /var/crash/vmcore.2
Sat Aug 24 20:29:48 CDT 2013
FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r254807: Sat Aug
24 16:52:42 CDT 2013 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE
amd64
panic: sorele
GNU gdb 6.1.1 [F
TB --- 2013-08-25 02:30:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-25 02:30:25 - 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 --- 2013
TB --- 2013-08-25 02:30:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-25 02:30:25 - 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 --- 2013
TB --- 2013-08-25 02:30:25 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-25 02:30:25 - 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 --- 2013
And a 4th:
borg.lerctr.org dumped core - see /var/crash/vmcore.3
Sun Aug 25 01:52:10 CDT 2013
FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r254807: Sat Aug
24 16:52:42 CDT 2013 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE
amd64
panic: page fault
GNU gdb 6.1.1
63 matches
Mail list logo
