From: Sander Eikelenboom <linux@eikelenboom.it>
To: "Huang2, Wei" <Wei.Huang2@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Panic:: handle_irq_event_percpu
Date: Wed, 19 Oct 2011 19:30:02 +0200 [thread overview]
Message-ID: <707354928.20111019193003@eikelenboom.it> (raw)
In-Reply-To: <EE335F95F28A664DB4A21289D2AA053B01E6CBBBDB@SAUSEXMBP01.amd.com>
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@oracle.com]
> Sent: Wednesday, October 19, 2011 11:08 AM
> To: Sander Eikelenboom; Huang2, Wei
> Cc: xen-devel@lists.xensource.com
> 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@lists.xensource.com
>> http://lists.xensource.com/xen-devel
--
Best regards,
Sander mailto:linux@eikelenboom.it
next prev parent reply other threads:[~2011-10-19 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 18:55 Panic:: handle_irq_event_percpu Sander Eikelenboom
2011-10-19 16:08 ` Konrad Rzeszutek Wilk
2011-10-19 16:38 ` Huang2, Wei
2011-10-19 17:30 ` Sander Eikelenboom [this message]
2011-10-19 18:27 ` Huang2, Wei
2011-10-22 14:57 ` Sander Eikelenboom
2011-10-24 21:51 ` Wei Huang
2011-10-26 14:12 ` Sander Eikelenboom
2011-10-26 14:21 ` Wei Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=707354928.20111019193003@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=Wei.Huang2@amd.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.