[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: kernel BUG at arch/x86/xen/mmu.c:1872
- To: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>
- From: Teck Choon Giam <giamteckchoon@xxxxxxxxx>
- Date: Wed, 13 Apr 2011 00:08:04 +0800
- Cc: jeremy@xxxxxxxx, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, keir@xxxxxxx, ian.campbell@xxxxxxxxxx, konrad.wilk@xxxxxxxxxx, dave@xxxxxxxxxx
- Delivery-date: Tue, 12 Apr 2011 09:08:51 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2Yuh7i6ve4ArucqxRQdPerelXYacmP0UtDfovTaofqs=; b=xfep7Rp8no7jwJAPcu6sDyLoEkbwudt5AK18OdIadlv8dA98LrTJ0uNfzQQbFeaNaX AhDDq5DHVLDKfuIzX1DOVzu0nGsQnruhpv9xEWVC8bWFSoKRZfOmZuC1zCbrnPdSpSJb qdvIib8u3VeWBcd3SOLHBzC0zU83lPZxLHMw4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FWpycN6X/fY5stzcOHU0RGaytphNOvd9EHhvbBcqgW4GDRB5sL4ztk8BIVXedk5MYq iC+TUEMkzrz7mzDsG6jPpMLQu3GCSfwOsKaa+9iUp69yucxiX1FFUU+M+GzT6rzLWESC vOS4X1/5VaZWxddEwBwyHbwNAjBMZDJ8CZPtA=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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@xxxxxxxxxxx>:
> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel