From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Features and bug-fixes that went in Linux 3.2
Date: Tue, 10 Jan 2012 00:47:12 -0800 (PST) [thread overview]
Message-ID: <1326185232800-5133661.post@n5.nabble.com> (raw)
In-Reply-To: <20120109213039.GC4773@phenom.dumpdata.com>
Thanks to all for good work, I tried Precise as domU pv (with kernel 3.2) and
I have found critical regression, probably there is a bug or unexpected
cases in some blk commit
I have already report on launchpad, this is the link:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/913760
Dom0 have Squeeze kernel build 2.6.32-35squeeze2, if you need more
information just ask I hope to be helpful.
Thanks and sorry for bad english.
--
View this message in context: http://xen.1045712.n5.nabble.com/Features-and-bug-fixes-that-went-in-Linux-3-2-tp5132575p5133661.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2012-01-10 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 21:30 Features and bug-fixes that went in Linux 3.2 Konrad Rzeszutek Wilk
2012-01-09 22:26 ` James Harper
2012-01-09 22:37 ` Ian Campbell
2012-01-12 17:02 ` Laszlo Ersek
2012-01-12 17:23 ` Ian Campbell
2012-01-10 8:47 ` Fantu [this message]
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=1326185232800-5133661.post@n5.nabble.com \
--to=fantonifabio@tiscali.it \
--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).