> Add the following to your kernel config:
> makeoptions DEBUG=-g
> options DDB, KDB, GDB
> options INVARIANTS
> options INVARIANT_SUPPORT
> options WITNESS_KDB
> options WITNESS_SKIPSPIN
> # Add this if you're using a firewire console
> options
>
> >> Did you use a 80- or 40-ATA cable?
> >> If you've configured your drives to do UATA-66 or faster then
> >> FreeBSD (or any other OS for that matter) will crash if
> you connect a
> >> second drive...
This is new one to me! I guess my 3 x UATA-100 are super drives of some sort
not t
Anish Mistry wrote:
On Thursday 13 April 2006 07:47, Wil Hatfield wrote:
I had a similar situation under 6.0. My secondary drive would
throw DMA read
errors at bootup, adding several minutes to the boot process, so
I ran it in
PIO mode. The upgrade to 6.1 solved it, both drives work fine as
On Thu, 13 Apr 2006 21:57:58 -, Wil Hatfield <[EMAIL PROTECTED]>
wrote:
Did you use a 80- or 40-ATA cable?
If you've configured your drives to do UATA-66 or faster then
FreeBSD (or
any other OS for that matter) will crash if you connect a second
drive...
It's an 80 wire. I have two dr
On Thursday 13 April 2006 18:01, Wil Hatfield wrote:
> > Do you have a backtrace?
>
> No. To be honest I have worked a little with the debugging but that
> was a long time ago. We ran 4.10 for eons and never needed to debug
> a thing. I got spoiled I guess. So now that I need to add debugging
> and
> Do you have a backtrace?
No. To be honest I have worked a little with the debugging but that was a
long time ago. We ran 4.10 for eons and never needed to debug a thing. I got
spoiled I guess. So now that I need to add debugging and backtrace to my
arsenal of knowledge could someone point me in
> Did you use a 80- or 40-ATA cable?
> If you've configured your drives to do UATA-66 or faster then
> FreeBSD (or
> any other OS for that matter) will crash if you connect a second drive...
It's an 80 wire. I have two drives on nearly all of my machines and never
had an issue with crashing until
On Thu, 13 Apr 2006 15:53:57 -, Anish Mistry <[EMAIL PROTECTED]> wrote:
On Thursday 13 April 2006 07:47, Wil Hatfield wrote:
> I had a similar situation under 6.0. My secondary drive would
> throw DMA read
> errors at bootup, adding several minutes to the boot process, so
> I ran it in
> PI
On Thursday 13 April 2006 07:47, Wil Hatfield wrote:
> > I had a similar situation under 6.0. My secondary drive would
> > throw DMA read
> > errors at bootup, adding several minutes to the boot process, so
> > I ran it in
> > PIO mode. The upgrade to 6.1 solved it, both drives work fine as
> > DMA
> I had a similar situation under 6.0. My secondary drive would
> throw DMA read
> errors at bootup, adding several minutes to the boot process, so
> I ran it in
> PIO mode. The upgrade to 6.1 solved it, both drives work fine as DMA now.
Looks like the DMA errors are back in 6.1-RC with ATA or at
On Thursday 13 April 2006 01:58, Perttu Laine wrote:
> I have problem with ATA drive having DMA TIMEOUTs.
> It might work day or two fine with DMA mode on but then system halts on
> those dma timeout problems.
>
> hardware is:
> [EMAIL PROTECTED]:5:0: class=0x018085 card=0x4d68105a chip=0x4d6
11 matches
Mail list logo
