Re: dump with xen-unstable & linux 3.2.17

[Ben Guthro <ben@guthro.net>]

Are you referring to kernel, or Xen patches?

I'm currently seeing the issue in question with the xen-unstable tip
none of our patches pushed...
...or are you suggesting that the patch, as committed is incorrect?

On Tue, May 22, 2012 at 1:34 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, May 22, 2012 at 12:21:20PM -0400, Ben Guthro wrote:
>> good point.
>>
>> I'll continue to try to figure this out - but if you have anything
>> specific I can try (particular boot options, or a patch with extra
>> debugging in interesting areas) please let me know, as it is 100%
>> reproducible in my environment right now.
>
> So.. you mentioned that you are using the serial console and that
> there were some changes in the hypervisor to deal with the serial console.
>
> I sent to xen-devel some of the patches that you guys had (with
> proper authorship) - especially the one dealing with PCI serial cards.
> Jan found that one of them had an simple mistake of trying to use
> the ports before they were initialized and fixed that in xen-unstable.
> Perhaps that is missing?
>
>>
>> -Ben
>>
>> On Tue, May 22, 2012 at 12:08 PM, Jan Beulich <JBeulich@suse.com> wrote:
>> >>>> On 22.05.12 at 17:38, Ben Guthro <ben@guthro.net> wrote:
>> >> I still suspect this is something my dom0 kernel is doing incorrectly,
>> >> but I don't have much to back that up other than a gut feeling.
>> >
>> > If the Dom0 kernel can affect the scheduler in this way, then
>> > quite likely a DomU kernel can too. And even if not, it's still a
>> > problem - the scheduler just shouldn't be susceptible.
>> >
>> > Jan
>> >
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel