system lockup - ata spurious interrupts - somehow updated

[Putinas Piliponis]

As for me, it looks what ata code is not correctly handling more then one
ata controller. If I set in bios compatible mode, and I have only P-ATA+
S-ATA, everything works fine, I can boot in verbose mode, no spurious
interrupts at all. If I set in bios as bios default Enchanced mode for S-ATA
then I still can boot in verbose mode, I see plenty of spurious interrupts
on ata2 and ata3 controllers, but system is still continues booting. If I 
set
enchanced
mode for S-ATA + P-ATA I cannot boot either in verbose mode or either in
normal mode. System gets stuck forever ( or at least for long time ) after I
see:
"Mounting root from ufs:ad8s3a".
and if I boot then in verbose mode, I see nonstopable spurious interrupts on
ata2, ata3, ata4 and ata5.

This is also could explain, why 5.2.1 is still stable with 4 ide drives,
and continuesly freezing or panicing with 6 ( or more I guess ) ide drives.
and as well why for some people configuration is working, either they use
4 drives not on all different channels, but some of them maybe on same
channel ( again my guess ).

----- Original Message ----- 
From: "Elliot Finley" <lists at efinley.com>
To: "Alexander Mueller" <alex at 6by9.org>; <freebsd-current at freebsd.org>
Sent: Saturday, March 20, 2004 5:29 PM
Subject: Re: system lockup - ata related and spurious interrupts


>
> ----- Original Message ----- 
> From: "Alexander Mueller" <alex at 6by9.org>
> To: <freebsd-current at freebsd.org>
> Sent: Friday, March 19, 2004 6:26 PM
> Subject: system lockup - ata related and spurious interrupts
>
>
>> I can't offer you any help but at least I can tell you that I'm
>> experiencing exactly the same two problems: TIMEOUT - WRITE_DMA
>> when hyperthreading is enabled and inability to reboot or power
>> off when hyperthreading is disabled. My hardware is similar to
>> yours: Asus P4C800E Deluxe with P4 3.0 GHz using the onboard
>> SATA controller integrated into the ICH5. My hard disk is a
>> WD Raptor 740GD. Currently nobody seems to take care of this
>> problem although there must be quity a lot of people out there
>> running into similar troubles.
>
> plus one.
>
> Elliot
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>
>