On 28/03/07, Sten Daniel Soersdal <[EMAIL PROTECTED]> wrote:
Vlad GURDIGA wrote:
> On 27/03/07, Sten Daniel Soersdal <[EMAIL PROTECTED]> wrote:
>> Vlad GURDIGA wrote:
>> > On 27/03/07, Sten Daniel Soersdal <[EMAIL PROTECTED]> wrote:
>> >> Vlad GURDIGA wrote:
>> >> > On 27/03/07, Sten Daniel Soersdal <[EMAIL PROTECTED]> wrote:
>> >> >> Vlad GURDIGA wrote:
>> >> >> > After running this:
>> >> >> >
>> >> >> > /sbin/atacontrol reinit ata2
>> >> >> >
>> >> >> > the storm was gone.
>> >> >> > My HDD in on ata4:
>> >> >> >
>> >> >> > #atacontrol info ata4
>> >> >> > Master: ad8 <ST3160812AS/3.AAD> Serial ATA II
>> >> >> > Slave: no device present
>> >> >> >
>> >> >> >
>> >> >> > Why?
>> >> >> >
>> >> >>
>> >> >> Could be one of any number of reasons and my guess is that the
>> drive
>> >> >> wants to enter sleep mode, due to overheating or energy saving. And
>> >> >> either controller, driver or both found it unreasonable.
>> >> >
>> >> > You can see the brand and model of my drive. I have Windows XP on
>> the
>> >> > same computer which works fine. Would the drive want to enter sleep
>> >> > mode only under FreeBSD?
>> >>
>> >> Depends on your workload. Perhaps you do something under FreeBSD that
>> >> generates more heat?
>> >
>> > There is no workload: the storm is there right from the boot of OS.
>> >
>> >>
>> >>
>> >> >> Perhaps you could inform us after you have researched it?
>> >> >
>> >> > I do not have a plain idea about what I could or should research in
>> >> > this case... Could you please be morespecific?
>> >>
>> >> I would start with the name of the SATA controller and drive and see
>> >> whether someone else has had the same problems (search archives and
>> >> google). Then i'd probably check temperatures, chipsets, try -CURRENT
>> >> (for driver updates to see whether that fixes it) and go from there.
>> >
>> > OK, I'll try.
>> >
>> >> See if you can identify a condition that triggers the IRQ storm.
>> >
>> > As I said, there is no special condition: the storm is there right
>> > from the boot of OS.
>> >
>>
>> It doesn't need to be a "special condition" to be a condition.
>> By your description it sounds to me like a problem caused by improper
>> initialization in BIOS but that Windows Drivers "fix", perhaps you need
>> to see if you can upgrade BIOS and SATA controller firmware.
>
> I updated BIOS right after the instalation: it means about a week or
> two ago. I guess the SATA firmware is included.
>
What are your other options?
This is what I'm trying to find out here. :)
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
