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: Wed, 13 Apr 2011 00:08:04 +0800 [thread overview]
Message-ID: <BANLkTin=1HirnrDt_DDTnsigaz9Dq43viw@mail.gmail.com> (raw)
In-Reply-To: <BLU157-w306778222A281548F1D216DAAB0@phx.gbl>
If it is possible, please try not to top-post as this make reading
more confusing for me at least. Thanks ;)
2011/4/12 MaoXiaoyun <tinnycloud@hotmail.com>:
> Hi:
>
> I have just kicked off cpuidle=0 "cpufreq=none" tests.
Let see whether are you able to reproduce the tlb BUG with the above.
>
> What is your Xen version? Do you use the backend driver of
> 2.6.32.36?
You are asking me?
xen-4.0.2-rc3-pre latest changeset and also xen-4.1.1-rc1-pre.
What do you mean backend driver? My testing are mostly on PV domU and
HVM on windows with LVM as storage. I do not use VDH or any PV
drivers for windows.
>
> Beside the "TLB BUG ", I've met at least two other issues
> 1)Xen4.0.1 + 2.6.32.36 kernel + backend driver from 2.6.31 ==> will
> cause "Bad grant reference " log in serial output
> 2)Xen4.0.1 + 2.6.32.36 kernel with its owen backend driver ==> will
> cause disk error like belows.
>
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> sd 0:0:0:0: rejecting I/O to offline device
> end_request: I/O error, dev tdb, sector 28699593
> end_request: I/O error, dev tdb, sector 28699673
> end_request: I/O error, dev tdb, sector 28699753
> end_request: I/O error, dev tdb, sector 28699833
> end_request: I/O error, dev tdb, sector 28699913
> end_request: I/O error, dev tdb, sector 28699993
> end_request: I/O error, dev tdb, sector 28700073
Is this related to VDH? What is the specific backend driver? These
started to surface after you applied my backport patch or regardless
the patch applied it is already there?
Thanks.
Kindest regards,
Giam Teck Choon
next prev parent reply other threads:[~2011-04-12 16:08 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
2011-04-12 3:30 ` MaoXiaoyun
2011-04-12 16:08 ` Teck Choon Giam [this message]
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='BANLkTin=1HirnrDt_DDTnsigaz9Dq43viw@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).