Re: Freeze with 2.6.32.19 and xen-4.0.1rc5, acpi problems

[Claus Rosenberger <claus.rosenberger@rocnet.de>]

 Am 25.08.2010 10:53, schrieb Pasi Kärkkäinen:
> On Wed, Aug 25, 2010 at 10:02:59AM +0200, Claus Rosenberger wrote:
>> Am 25.08.2010 01:22, schrieb Claus Rosenberger:
>>>  I checked out these options, following result
>>>>>> - acpi=ht noapic     => worked
>>>>>> - noapic             => didn't work, disk errors while booting, no functional system
>>>>>> - acpi=ht apic=debug => worked
>>>>>>
>>>>>> So it seems i definitly need the option acpi=ht or acpi=off or something like that.
>>>>>>
>>>>> Keir, Jeremy: Any idea why acpi=ht is needed to make Intel DQ45CB (Q45 chipset) work?
>>>>>
>>>>> Without "acpi=ht" the system freezes randomly without any log/debug/serialconsole output..
>>>> At a random guess, there's something strange about the SCI interrupt. 
>>>> When booting native, does "acpi" get irq 9 or something else?  Is there
>>>> a BIOS setting relating to SCI or ACPI interrupts?
>>>>
>>> The kernel was running native without that problems, i attached dmesg. I
>>> didn't find any BIOS options like that.
>>>
>>
>> a new test was done loading libata with option noacpi=1
>>
>> - acpi=ht noapic     => worked
>> - noapic             => didn't work, disk errors while booting, no functional system
>> - acpi=ht apic=debug => worked
>> - xen without options but loading libata with option noacpi=1    => worked
>>
> So only setting libata.noacpi=1 fixes (or workarounds) the problem.. hmm.
> Or setting "acpi=ht" fixes it aswell.
>
> Hopefully someone has ideas about the cause..
>
> -- Pasi
>


Now i got the error with libata.noacpi=1 too, but there was no impact so
no raid status lost or something else and it was only that one error:

[81907.801237] ata2: lost interrupt (Status 0x51)
[81907.803062] ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002
action 0xe
[81907.805221] ata2.00: SError: { RecovComm PHYRdyChg CommWake 10B8B
DevExch }
[81907.805221] ata2.00: failed command: FLUSH CACHE EXT
[81907.805221] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[81907.805221]          res 51/04:01:01:00:00/00:00:00:00:00/a0 Emask
0x10 (ATA bus error)
[81907.805221] ata2.00: status: { DRDY ERR }
[81907.805221] ata2.00: error: { ABRT }
[81907.805221] ata2.00: hard resetting link
[81908.540258] ata2.01: hard resetting link
[81909.016368] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[81909.019044] ata2.01: SATA link down (SStatus 0 SControl 300)
[81909.040964] ata2.00: configured for UDMA/133
[81909.042760] ata2: EH complete