TB --- 2010-12-04 05:53:25 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 05:53:25 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2010-12-04 05:53:25 - cleaning the object tree
TB --- 2010-12-04 05:53:39 - cvsupping the source tree
TB --- 2010-12-04 05:53:39 - /u
TB --- 2010-12-04 06:17:06 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 06:17:06 - starting HEAD tinderbox run for sparc64/sun4v
TB --- 2010-12-04 06:17:06 - cleaning the object tree
TB --- 2010-12-04 06:17:15 - cvsupping the source tree
TB --- 2010-12-04 06:17:15 - /usr/b
TB --- 2010-12-04 05:24:03 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 05:24:03 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-12-04 05:24:03 - cleaning the object tree
TB --- 2010-12-04 05:24:15 - cvsupping the source tree
TB --- 2010-12-04 05:24:15 - /usr
TB --- 2010-12-04 05:56:49 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 05:56:49 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2010-12-04 05:56:49 - cleaning the object tree
TB --- 2010-12-04 05:57:01 - cvsupping the source tree
TB --- 2010-12-04 05:57:01 - /usr
TB --- 2010-12-04 03:35:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 03:35:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-12-04 03:35:00 - cleaning the object tree
TB --- 2010-12-04 03:35:30 - cvsupping the source tree
TB --- 2010-12-04 03:35:30 - /usr/bin
TB --- 2010-12-04 04:27:03 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 04:27:03 - starting HEAD tinderbox run for ia64/ia64
TB --- 2010-12-04 04:27:03 - cleaning the object tree
TB --- 2010-12-04 04:27:14 - cvsupping the source tree
TB --- 2010-12-04 04:27:14 - /usr/bin/c
TB --- 2010-12-04 03:35:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 03:35:00 - starting HEAD tinderbox run for i386/i386
TB --- 2010-12-04 03:35:00 - cleaning the object tree
TB --- 2010-12-04 03:35:17 - cvsupping the source tree
TB --- 2010-12-04 03:35:17 - /usr/bin/c
TB --- 2010-12-04 03:35:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 03:35:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2010-12-04 03:35:00 - cleaning the object tree
TB --- 2010-12-04 03:35:16 - cvsupping the source tree
TB --- 2010-12-04 03:35:16 - /usr/bin/c
Jung-uk Kim wrote:
On Friday 03 December 2010 01:14 pm, Andriy Gapon wrote:
on 03/12/2010 20:05 Jung-uk Kim said the following:
On Friday 03 December 2010 12:26 pm, Andriy Gapon wrote:
FreeBSD uses cpu_ticks [function pointer] in a few places for a
few things like process CPU ti
On Friday 03 December 2010 06:47 pm, Andriy Gapon wrote:
> on 03/12/2010 22:03 Jung-uk Kim said the following:
> > On Friday 03 December 2010 01:14 pm, Andriy Gapon wrote:
> >> on 03/12/2010 20:05 Jung-uk Kim said the following:
> >>> On Friday 03 December 2010 12:26 pm, Andriy Gapon wrote:
>
On 2010-12-03 10:58, Anton Shterenlikht wrote:
a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked,
not stripped
...
The branding on ia64 is wrong. The executable is not marked as being
a FreeBSD executable. It's declared as SYSV, whereas on amd64 it's
properly declare
on 03/12/2010 22:03 Jung-uk Kim said the following:
> On Friday 03 December 2010 01:14 pm, Andriy Gapon wrote:
>> on 03/12/2010 20:05 Jung-uk Kim said the following:
>>> On Friday 03 December 2010 12:26 pm, Andriy Gapon wrote:
FreeBSD uses cpu_ticks [function pointer] in a few places for a
>>>
On Friday 03 December 2010 01:14 pm, Andriy Gapon wrote:
> on 03/12/2010 20:05 Jung-uk Kim said the following:
> > On Friday 03 December 2010 12:26 pm, Andriy Gapon wrote:
> >> FreeBSD uses cpu_ticks [function pointer] in a few places for a
> >> few things like process CPU time accounting. On x86
on 03/12/2010 20:05 Jung-uk Kim said the following:
> On Friday 03 December 2010 12:26 pm, Andriy Gapon wrote:
>> FreeBSD uses cpu_ticks [function pointer] in a few places for a few
>> things like process CPU time accounting. On x86 cpu_ticks always
>> points to rdtsc. If TSC is not invariant that
On Friday 03 December 2010 12:26 pm, Andriy Gapon wrote:
> FreeBSD uses cpu_ticks [function pointer] in a few places for a few
> things like process CPU time accounting. On x86 cpu_ticks always
> points to rdtsc. If TSC is not invariant that leads to incorrect
> accounting of "CPU ticks". The code
FreeBSD uses cpu_ticks [function pointer] in a few places for a few things like
process CPU time accounting. On x86 cpu_ticks always points to rdtsc.
If TSC is not invariant that leads to incorrect accounting of "CPU ticks".
The code pretends to try to handle changing cpufreq levels, but does tha
On Thursday, December 02, 2010 2:44:00 pm David O'Brien wrote:
> Machine booted, without any mention of sf(4) in rc.conf or loader.conf and
> without sf(4) in the core kernel. This is without WITNESS or INVARIANTS.
>
> >From multi-user, I issued 'ifconfig sf0' and got the below panic.
> These are
I'd hazard a stab and say that anything AR5416 or more recent is going
to be busted power-save wise.
There's a lot missing in the HAL code for those chips.
Adrian
On 2 December 2010 23:04, Sergey Horuzhy wrote:
> Chris Buechler chrisbuechler.com> writes:
>
>>
>> Sam Leffler wrote:
>> >
>> >
- Forwarded message from Marcel Moolenaar -
On Nov 10, 2010, at 5:32 AM, Anton Shterenlikht wrote:
[ia64]
> ia64% file a.out
> a.out: ELF 64-bit LSB executable, IA-64, version 1 (SYSV), statically linked,
> not stripped
[amd64]
> amd64% file a.out
> a.out: ELF 64-bit LSB executable, x
19 matches
Mail list logo
