From: Teck Choon Giam <giamteckchoon@gmail.com>
To: MaoXiaoyun <tinnycloud@hotmail.com>
Cc: jeremy@goop.org, xen devel <xen-devel@lists.xensource.com>,
keir@xen.org, ian.campbell@citrix.com, konrad.wilk@oracle.com,
dave@ivt.com.au
Subject: Re: kernel BUG at arch/x86/xen/mmu.c:1872
Date: Mon, 11 Apr 2011 23:25:19 +0800 [thread overview]
Message-ID: <BANLkTimKWanNYTjrEHaik_Z1eLXptoN1kQ@mail.gmail.com> (raw)
In-Reply-To: <BLU157-w116F1BB57ABFDE535C7851DAA80@phx.gbl>
2011/4/11 MaoXiaoyun <tinnycloud@hotmail.com>:
> Hi:
>
> I believe this is the fix at much extent.
> Since I have my own test cases which with this patch, my test case will
> success in 30 rounds run.
> Every round takes 8hours. While without this patch, tests fail evey
> round in 15minutes.
>
> So this really means fix most of the things.
>
> But during running, I met another crash, from the log it it looks like
> has relation with
> this BUG, since the crash log shows it is tlb related and this BUG also tlb
> related.
Are you able to run another test with cpuidle=0 cpufreq=none in kernel
boot option? Just curious whether can you reproduce the tlb bug when
you boot with cpuidle=0 cpufreq=none... ...
>
> Well, I'm also have poor knowledge of kernel.
> Hope someone from Xen Devel offer some help.
>
> Many thanks.
>
>> Date: Mon, 11 Apr 2011 20:16:53 +0800
>> Subject: Re: kernel BUG at arch/x86/xen/mmu.c:1872
>> From: giamteckchoon@gmail.com
>> To: tinnycloud@hotmail.com
>> CC: xen-devel@lists.xensource.com; dave@ivt.com.au;
>> ian.campbell@citrix.com; konrad.wilk@oracle.com; jeremy@goop.org;
>> keir@xen.org
>>
>> >
>> > Hi,
>> >
>> > Sorry, since this mmu related BUG has been troubled me for very
>> > long... I really want to "kill" this BUG but my knowledge in kernel
>> > hacking and/or xen is very limited.
>> >
>> > While waiting for Jeremy or Konrad or others ...
>> >
>> > Many thanks for spending time to track down this mmu related BUG. I
>> > have backported the commit from
>> >
>> > http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=64141da587241301ce8638cc945f8b67853156ec
>> > to 2.6.32.36 PVOPS kernel and patch attached. I won't know whether
>> > did I backport it correctly nor does it affects anything. I am
>> > currently testing the 2.6.32.36 PVOPS kernel with this patch applied
>> > and also unset CONFIG_DEBUG_PAGEALLOC. Currently running testcrash.sh
>> > loop 1000 as I am unable to reproduce this mmu BUG 1872 in
>> > testcrash.sh loop 100. Please note that when CONFIG_DEBUG_PAGEALLOC
>> > is unset, I can reproduce this mmu BUG 1872 easily within <50
>> > testcrash.sh loop cycle with PVOPS version 2.6.32.24 to 2.6.32.36
>> > kernel. Now test with this backport patch to see whether I can
>> > reproduce this mmu BUG... ...
>> >
>> > Kindest regards,
>> > Giam Teck Choon
>> >
>>
>> I have tested with my backport patch and it is working fine as I am
>> unable to reproduce the mmu.c 1872 or 1860 bug with
>> CONFIG_DEBUG_PAGEALLOC not set. I tested with testcrash.sh loop 100
>> and 1000. Now doing testcrash.sh loop 10000.
>>
>> Xiaoyun, is it possible for you to test my patch and see whether can
>> you reproduce the mmu.c 1872/1860 bug?
>>
>> Can anyone of you review my patch?
>>
>> I will post a format patch according to
>> Documentation/SubmittingPatches in my next reply and hopefully can be
>> reviewed.
>>
>> Thanks.
>>
>> Kindest regards,
>> Giam Teck Choon
>
next prev parent reply other threads:[~2011-04-11 15:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <COL0-MC1-F14hmBzxHs00230882@col0-mc1-f14.Col0.hotmail.com>
2011-04-08 11:24 ` kernel BUG at arch/x86/xen/mmu.c:1860! MaoXiaoyun
2011-04-08 11:46 ` MaoXiaoyun
2011-04-10 3:57 ` kernel BUG at arch/x86/xen/mmu.c:1872 MaoXiaoyun
2011-04-10 4:29 ` MaoXiaoyun
2011-04-10 13:57 ` MaoXiaoyun
2011-04-10 20:14 ` Teck Choon Giam
2011-04-11 12:16 ` Teck Choon Giam
2011-04-11 12:22 ` Teck Choon Giam
2011-04-11 12:31 ` MaoXiaoyun
2011-04-11 15:25 ` Teck Choon Giam [this message]
2011-04-12 3:30 ` MaoXiaoyun
2011-04-12 16:08 ` Teck Choon Giam
2011-04-11 18:08 ` Jeremy Fitzhardinge
2011-04-12 3:35 ` MaoXiaoyun
2011-04-12 6:48 ` Grant Table Error on 2.6.32.36 + Xen 4.0.1 MaoXiaoyun
2011-04-12 8:46 ` Konrad Rzeszutek Wilk
2011-04-12 9:02 ` MaoXiaoyun
2011-04-12 9:11 ` Kernel BUG at arch/x86/mm/tlb.c:61 MaoXiaoyun
2011-04-12 10:00 ` Konrad Rzeszutek Wilk
2011-04-12 10:10 ` MaoXiaoyun
2011-04-14 6:16 ` MaoXiaoyun
2011-04-14 7:26 ` Teck Choon Giam
2011-04-14 7:56 ` MaoXiaoyun
2011-04-14 11:16 ` MaoXiaoyun
2011-04-15 12:23 ` MaoXiaoyun
2011-04-15 21:22 ` Jeremy Fitzhardinge
2011-04-18 15:20 ` MaoXiaoyun
2011-04-25 3:15 ` MaoXiaoyun
2011-04-26 5:52 ` Tian, Kevin
2011-04-26 7:04 ` MaoXiaoyun
2011-04-26 8:31 ` Tian, Kevin
2011-04-28 23:29 ` Jeremy Fitzhardinge
2011-04-29 0:19 ` Tian, Kevin
2011-04-29 1:50 ` MaoXiaoyun
2011-04-29 1:57 ` Tian, Kevin
2011-04-25 4:42 ` MaoXiaoyun
2011-04-25 12:54 ` MaoXiaoyun
2011-04-25 13:11 ` MaoXiaoyun
2011-04-25 15:05 ` MaoXiaoyun
2011-04-26 5:55 ` Tian, Kevin
2011-04-12 16:32 ` kernel BUG at arch/x86/xen/mmu.c:1872 Teck Choon Giam
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=BANLkTimKWanNYTjrEHaik_Z1eLXptoN1kQ@mail.gmail.com \
--to=giamteckchoon@gmail.com \
--cc=dave@ivt.com.au \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=tinnycloud@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).