This reminds me of 23768:09595fdf3638, which reverted WeiWang's patch of
forcing perdev-intremap as default. Could you try the attached patch on your
Xen 4.1 tree and test with patched xen.gz?
Thanks,
-Wei
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Sander Eikelenboom
Sent: Wednesday, October 19, 2011 12:30 PM
To: Huang2, Wei
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Konrad Rzeszutek Wilk
Subject: Re: [Xen-devel] Panic:: handle_irq_event_percpu
Hello Wei,
Result is that using only "1" or "1" in combination with "2" always result in
SATA I/O errors, so that doesn't boot.
Haven't tried rebooting a lot of times without iommu yet.
(the reason i bought the 890fx board in the first place)
Will try that a few times when i have some more time.
--
Sander
Wednesday, October 19, 2011, 6:38:38 PM, you wrote:
> It looks similar.
> Hi Sander, could you please test your system with the following options?
> 1. iommu=amd-iommu-perdev-intremap in xen.gz GRUB entry
> 2. pci=nosmi in pvops GRUB entry
> 3. iommu=0 in xen.gz GRUB entry [optional, only if (1) doesn't work for you]
> We were seeing an issue which was caused by messed-up interrupt remap table.
> George Dunlap's perdev interrupt map solved our problem.
> Thanks,
> -Wei
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
> Sent: Wednesday, October 19, 2011 11:08 AM
> To: Sander Eikelenboom; Huang2, Wei
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Panic:: handle_irq_event_percpu
> On Tue, Oct 18, 2011 at 08:55:19PM +0200, Sander Eikelenboom wrote:
>> Hi Konrad,
>>
>> On my system (AND phenom x6, 8gb mem) running xen 4.1.2-rc3
>> and a custom kernel based on:
>>
>> - your linux-next branch
>> - pulled in your apci/cpufreq branch
>> - pulled in latest patches from linuses tree
> Wei,
> Are those similar to what you had been seeing?
>>
>> I'm experiencing infrequent panics at boot (say 1 out of 10 or 20 boots),
>> doesn't seem to matter if it's a cold or a warm boot.
>> It always seem to happen during or shortly after booting. When it doesn't
>> occur then, it can run for at least several days/weeks (haven't seen it
>> panic then).
>> It doesn't seem to happen at a particular point at or shortly after booting,
>> but it happens before starting any guests
>>
>> Unfortunately i haven't had serial console enabled at these times, but i
>> have made some photo's.
>> The first 3 times it locked completely before being able to print a
>> stacktrace, the 4th time it did (although the photo is a bit unsharp).
>>
>>
>> So all in all, it kind of strange, i hope you can figure something out from
>> the stacktrace, if not, i will see if i can try with serial console attached.
>>
>> --
>> Sander
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
--
Best regards,
Sander mailto:linux@xxxxxxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
interrupt-map-patch.txt
Description: interrupt-map-patch.txt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home