Re: Panic caused by bad memory?

On Tue, 24 Oct 2006 [EMAIL PROTECTED] wrote: I can't get a kernel dump since it fails like this each time: dumping to dev #da/0x20001, offset 2097152 dump 1024 1023 1022 1021 Aborting dump due to I/O error. status == 0xb, scsi status == 0x0 failed, reason: i/o error Bad memory seems unlikely

Re: Panic caused by bad memory?

> I can't get a kernel dump since it fails like this each time: > > dumping to dev #da/0x20001, offset 2097152 > dump 1024 1023 1022 1021 Aborting dump due to I/O error. > status == 0xb, scsi status == 0x0 > failed, reason: i/o error Bad memory seems unlikely to cause an I/O error trying to write

Panic caused by bad memory?

Hello all, Without a full dump are there any telltale signs from the panic message that can give me some sign of whether I'm dealing with a hardware or software issue? I have a box that has been running 4.11-p10 for quite some time with no problems. I upgraded a number of ports (apache/php/

Re: src.conf(5) seems to affect ports build

On Tue, Oct 24, 2006 at 04:23:40PM +0100, Florent Thoumie wrote: > On Tue, 2006-10-24 at 17:48 +0400, Ruslan Ermilov wrote: > > On Sun, Oct 22, 2006 at 05:34:36PM +0200, Jeremie Le Hen wrote: > > > Ruslan, > > > > > > On Sat, Oct 21, 2006 at 09:25:33PM +0400, Ruslan Ermilov wrote: > > > > > Also,

Re: src.conf(5) seems to affect ports build

On Tue, 2006-10-24 at 17:48 +0400, Ruslan Ermilov wrote: > On Sun, Oct 22, 2006 at 05:34:36PM +0200, Jeremie Le Hen wrote: > > Ruslan, > > > > On Sat, Oct 21, 2006 at 09:25:33PM +0400, Ruslan Ermilov wrote: > > > > Also, your patch avoids performing the WITH(OUT)_* stuff for ports in > > > > order

Re: scheduler CORE for RELENG_6

Ivan Voras writes: > Gary Jenneohn wrote: > > > Really? I've been using it since it was introduced and find it to be quite > > good on my dual-core AMD64 machine running in i386 mode. > > Any benchmarks, or description of what's improved? :) > No. I can only say that it doesn't "feel" any worse

Re: src.conf(5) seems to affect ports build

On Sun, Oct 22, 2006 at 05:34:36PM +0200, Jeremie Le Hen wrote: > Ruslan, > > On Sat, Oct 21, 2006 at 09:25:33PM +0400, Ruslan Ermilov wrote: > > > Also, your patch avoids performing the WITH(OUT)_* stuff for ports in > > > order to prevent from polluting the namespace. If there is to be > > > so

Re: scheduler CORE for RELENG_6

Gary Jenneohn wrote: Really? I've been using it since it was introduced and find it to be quite good on my dual-core AMD64 machine running in i386 mode. Any benchmarks, or description of what's improved? :) ___ freebsd-hackers@freebsd.org mailing li

Re: scheduler CORE for RELENG_6

David Xu writes: > On Tuesday 24 October 2006 17:31, Stepan A. Baranov wrote: > > Hello, > > > > I prepared patch to port scheduler from HEAD to RELENG_6. I applied > > this patch for my workstation and scheduler CORE works fine. > > > > After applying patch you can say: > > options SCHED_

Re: src.conf(5) seems to affect ports build

On Sun, 2006-10-22 at 17:34 +0200, Jeremie Le Hen wrote: > Ruslan, > > On Sat, Oct 21, 2006 at 09:25:33PM +0400, Ruslan Ermilov wrote: > > > Also, your patch avoids performing the WITH(OUT)_* stuff for ports in > > > order to prevent from polluting the namespace. If there is to be > > > some WITH

Re: scheduler CORE for RELENG_6

On Tuesday 24 October 2006 17:31, Stepan A. Baranov wrote: > Hello, > > I prepared patch to port scheduler from HEAD to RELENG_6. I applied > this patch for my workstation and scheduler CORE works fine. > > After applying patch you can say: > options SCHED_CORE # CORE scheduler

Re: 6.1-STABLE hangs, ddb shows 'acpi_timer_read'?

--On 20 October 2006 13:47 +0100 Robert Watson <[EMAIL PROTECTED]> wrote: I'm just a little hesitant to put it all in, and end up with a machine that's 80% slower :( Depends a lot on your workload. WITNESS used to really, really slow things down for kernel lock intensive workloads (VFS espe