Hi Fabian,
On 06/20/10 03:58, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/13/10 18:12, Lawrence Stewart wrote:
The time has come to solicit some external testing for my SIFTR tool.
I'm hoping to commit it within a week or so unless problems are discovered.
I'm interested in all fee
Lawrence Stewart wrote:
> On 06/20/10 03:58, Fabian Keil wrote:
> > Lawrence Stewart wrote:
> >
> >> On 06/13/10 18:12, Lawrence Stewart wrote:
> >
> >>> The time has come to solicit some external testing for my SIFTR tool.
> >>> I'm hoping to commit it within a week or so unless problems are
>
TB --- 2010-06-20 11:25:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-20 11:25:00 - starting HEAD tinderbox run for arm/arm
TB --- 2010-06-20 11:25:00 - cleaning the object tree
TB --- 2010-06-20 11:25:06 - cvsupping the source tree
TB --- 2010-06-20 11:25:06 - /usr/bin/csu
On 06/20/10 21:15, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/20/10 03:58, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/13/10 18:12, Lawrence Stewart wrote:
The time has come to solicit some external testing for my SIFTR tool.
I'm hoping to commit it within a week or so unles
Hi Kristof.
On Sun, 13 Jun 2010 22:13:31 +0200
Kristof Provost wrote:
> > I have a OpenRD Ultimate, which has two GbE ports - if_mge(4). But
> > I couldn't use mge1 like following. So I tried to investigate.
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Hi yongari.
On Tue, 15 Jun 2010 11:09:23 -0700
Pyun YongHyeon wrote:
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > - - - - - - -
> > Jun 13 05:02:14 sidearms kernel: mge1: watchdog timeout
> > Jun 13 05:02:14 sidearms kernel: mge1: Timeout on link-up
> ^^^
Lawrence Stewart wrote:
> On 06/20/10 21:15, Fabian Keil wrote:
> > Lawrence Stewart wrote:
> >
> >> On 06/20/10 03:58, Fabian Keil wrote:
> >>> Lawrence Stewart wrote:
> >>>
> On 06/13/10 18:12, Lawrence Stewart wrote:
> >>>
> > The time has come to solicit some external testing for
On 06/20/10 22:28, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/20/10 21:15, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/20/10 03:58, Fabian Keil wrote:
Lawrence Stewartwrote:
On 06/13/10 18:12, Lawrence Stewart wrote:
The time has come to solicit some external testing
On 2010-06-20 21:03:51 (+0900), Norikatsu Shigemura wrote:
> On Sun, 13 Jun 2010 22:13:31 +0200
> Kristof Provost wrote:
> > > I have a OpenRD Ultimate, which has two GbE ports - if_mge(4). But
> > > I couldn't use mge1 like following. So I tried to investigate.
> > > - - - - - - - - - - -
Lawrence Stewart wrote:
> On 06/20/10 22:28, Fabian Keil wrote:
> > Lawrence Stewart wrote:
> >
> >> On 06/20/10 21:15, Fabian Keil wrote:
> >>> Lawrence Stewart wrote:
> >>>
> On 06/20/10 03:58, Fabian Keil wrote:
> > Lawrence Stewartwrote:
> >
> >> On 06/13/10 18:12, Law
On 06/20/10 23:15, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/20/10 22:28, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/20/10 21:15, Fabian Keil wrote:
Lawrence Stewartwrote:
On 06/20/10 03:58, Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/13/10 18:12, Lawrence
Fabian Keil wrote:
> Lawrence Stewart wrote:
>
> > On 06/20/10 22:28, Fabian Keil wrote:
> > > Taking pf (and altq) out of the picture doesn't seem to make
> > > a difference.
> >
> > Wouldn't have expected it to. Will be very curious to know if the panic
> > is triggered in GENERIC.
>
> It
TB --- 2010-06-20 13:55:40 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-20 13:55:40 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-06-20 13:55:40 - cleaning the object tree
TB --- 2010-06-20 13:55:45 - cvsupping the source tree
TB --- 2010-06-20 13:55:45 - /usr
On Sun, Jun 20, 2010 at 1:17 AM, Alexander Motin wrote:
> Brandon Gooch wrote:
>> I've been testing these patches since the first iteration
>> (et.20100606), and I haven't discovered any related issues.
>
> Thank you!
>
>> I am unclear about the number of interrupts I should expect from the
>> hpe
Hi Kristof.
On Sun, 20 Jun 2010 15:01:00 +0200
Kristof Provost wrote:
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> > - - - - - - -
> > /* Tell the MAC where to find the PHY so autoneg works */
> > - miisc = LIST_FIRST(&sc->mii->mii_phys);
> > -
Brandon Gooch wrote:
> On Sun, Jun 20, 2010 at 1:17 AM, Alexander Motin wrote:
> In by /boot/loader.conf, I now have:
>
> # Power Saving
> kern.hz="100"
> #hint.apic.0.clock="0"
> #hint.atrtc.0.clock="0"
> hint.p4tcc.0.disabled="1"
> hint.p4tcc.1.disabled="1"
> hint.acpi_throttle.0.disabled="1"
>
Could you tell me exactly how did you configure your raid? I mean
wb/read-ahead/blocksize/stripe etc.
Much appreciated.
-zsozso
On 2010.06.19. 14:26, Svein Skogen (Listmail Account) wrote:
On 19.06.2010 11:58, oizs wrote:
I tried almost everything raid 0 1 5 10 with all kind of stripes
32
I've tried almost everything now.
The battery is probably fine:
mfiutil show battery
mfi0: Battery State:
Manufacture Date: 7/25/2009
Serial Number: 3716
Manufacturer: SMP-PA1.9
Model: DLFR463
Chemistry: LION
Design Capacity: 1800 mAh
Design Voltage: 3700 mV
C
Does anyone know of a nice how to guide for achieving this?
- Original Message -
From: "Scott Long"
2. Partition alignment. If you're using classic MBR slices, everything gets misaligned by 63 sectors, making it impossible for
the controller to optimize both reads and writes. If the
FreeBSD 9.0-CURRENT #1 r209275: Fri Jun 18 08:15:15 CDT 2010
r...@clank.housenet.jrv:/usr/obj/usr/src/sys/GENERIC amd64
June 17 -CURRENT
This panic was seen under VirtualBox on a Windows host. The VM has 2
cores (the host is a Core i7).
I this infrequently under a VM. I have yet to see it o
I just set up a machine with the following GPT scheme:
=>34 5853511613 mfid0 GPT (2.7T)
34 128 1 freebsd-boot (64K)
162 862 - free - (431K)
1024 2097152 2 freebsd-ufs (1.0G)
2098176 4194304 3 freebsd-s
/dev/random and /dev/urandom are relatively slow and are not suitable
as the source of data for testing modern hard drives' sequential
throughput.
On my 3GHz dual-core amd63 box both /dev/random and /dev/urandom max
out at ~80MB/s while consuming 100% CPU time on one of the processor
cores.
That w
Yeah, there's no value in using the /dev/random devices for testing disk i/o.
Use /dev/zero instead. I've known of hardware RAID engines in the past that
can recognize certain repeating i/o benchmark patterns and optimize for them,
but I have no idea if LSI controllers do this, tho based on yo
Fabian Keil wrote:
> Fabian Keil wrote:
> > My custom kernel normally doesn't have INVARIANTS and WITNESS
> > enabled, so I'll try to enable them next.
>
> The culprit seem to be non-default KTR settings in the kernel
> while loading alq as a module.
Actually whether or not alq is loaded as a
I noticed on my i386 router running 9-CURRENT that the "debug.ncores" sysctl
appears to get its value from some kernel memory that gets updated frequently:
debug.ncores: -936629388
On line 2967 of sys/kern/kern_sig.c should the value of num_cores instead of
ncores be getting returned?
--
Bruc
On 06/20/10 08:47, Alexander Motin wrote:
While this can be done in sysctl.conf, it would be better to do it in
loader.conf to make it applied from the beginning, without on-the-fly
timers change.
You're probably right that for something this fundamental it's better to
do it in loader.conf, ho
On 20 Jun 2010, at 20:36, Fabian Keil wrote:
> Fabian Keil wrote:
>
>> Fabian Keil wrote:
>
>>> My custom kernel normally doesn't have INVARIANTS and WITNESS
>>> enabled, so I'll try to enable them next.
>>
>> The culprit seem to be non-default KTR settings in the kernel
>> while loading alq
On Sun, Jun 20, 2010 at 08:38:37PM +0100, Bruce Cran wrote:
> I noticed on my i386 router running 9-CURRENT that the "debug.ncores" sysctl
> appears to get its value from some kernel memory that gets updated frequently:
>
> debug.ncores: -936629388
>
> On line 2967 of sys/kern/kern_sig.c should
On Mon, Jun 21, 2010 at 4:50 AM, Scott Long wrote:
> I just set up a machine with the following GPT scheme:
>
> => 34 5853511613 mfid0 GPT (2.7T)
> 34 128 1 freebsd-boot (64K)
> 162 862 - free - (431K)
> 1024 2097152 2 fr
Hello,
I would like to integrate my Google Summer of Code project from the
last year [1]. In brief, it was about converting netstat(1) into a
library and providing a relatively clean API to access various
networking statistics available in the kernel. The project is far
from being complete, and
On Sun, Jun 20, 2010 at 3:35 PM, Doug Barton wrote:
> On 06/20/10 08:47, Alexander Motin wrote:
>>
>> While this can be done in sysctl.conf, it would be better to do it in
>> loader.conf to make it applied from the beginning, without on-the-fly
>> timers change.
>
> You're probably right that for
On 06/21/10 00:12, Fabian Keil wrote:
Fabian Keil wrote:
Lawrence Stewart wrote:
On 06/20/10 22:28, Fabian Keil wrote:
Taking pf (and altq) out of the picture doesn't seem to make
a difference.
Wouldn't have expected it to. Will be very curious to know if the panic
is triggered in GENE
TB --- 2010-06-21 01:50:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-21 01:50:00 - starting HEAD tinderbox run for arm/arm
TB --- 2010-06-21 01:50:00 - cleaning the object tree
TB --- 2010-06-21 01:50:07 - cvsupping the source tree
TB --- 2010-06-21 01:50:07 - /usr/bin/csu
On 06/21/10 05:44, Rui Paulo wrote:
On 20 Jun 2010, at 20:36, Fabian Keil wrote:
Fabian Keil wrote:
Fabian Keil wrote:
My custom kernel normally doesn't have INVARIANTS and WITNESS
enabled, so I'll try to enable them next.
The culprit seem to be non-default KTR settings in the kernel
TB --- 2010-06-21 04:21:31 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-06-21 04:21:31 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-06-21 04:21:31 - cleaning the object tree
TB --- 2010-06-21 04:21:37 - cvsupping the source tree
TB --- 2010-06-21 04:21:37 - /usr
Brandon Gooch wrote:
> On Sun, Jun 20, 2010 at 3:35 PM, Doug Barton wrote:
>> On 06/20/10 08:47, Alexander Motin wrote:
>>> While this can be done in sysctl.conf, it would be better to do it in
>>> loader.conf to make it applied from the beginning, without on-the-fly
>>> timers change.
>> You're p
36 matches
Mail list logo
