From: David F Barrera <dfbp@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: 'Robin van Leeuwen' <rvl@ttg-edam.nl>,
'xen-devel' <xen-devel@lists.xensource.com>,
Sylvain COUTANT <sco@adviseo.fr>
Subject: Re: Kernel BUG at "drivers/xen/blkfront/blkfront.c":95
Date: Mon, 29 Aug 2005 14:38:28 -0500 [thread overview]
Message-ID: <1125344308.6018.28.camel@dbarrera_tp> (raw)
In-Reply-To: <e6b48b6f510af0a1591bddce4e1ddc50@cl.cam.ac.uk>
On Mon, 2005-08-29 at 17:11 +0100, Keir Fraser wrote:
> On 29 Aug 2005, at 16:42, David F Barrera wrote:
>
> > I tried it on a RHEL 4 box this morning as of the following changesets,
> > and DomU still crashed:
>
> That's one changeset too old! The very next changese
> t contains the
> (likely) fix.
That's what I though might be the case. I retested using a later pull,
and the problem has been resolved. Thx.
changeset: 6461:936be0ae823fd3a94ea06d92fdacad65b85d6014
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Mon Aug 29 09:53:38 2005
summary: Fix page_is_ram() start-of-day checks, and the watch
routine
>
> It has a comment starting "Allocate a request-id space per vbd in
> blkfront.".
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2005-08-29 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 19:16 Kernel BUG at "drivers/xen/blkfront/blkfront.c":95 Robin van Leeuwen
2005-08-27 21:36 ` Robin van Leeuwen
2005-08-28 9:36 ` Keir Fraser
2005-08-28 9:58 ` Sylvain COUTANT
2005-08-29 14:15 ` Keir Fraser
2005-08-29 15:42 ` David F Barrera
2005-08-29 16:11 ` Keir Fraser
2005-08-29 19:38 ` David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-27 21:29 Ian Pratt
2005-08-29 14:15 ` David F Barrera
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=1125344308.6018.28.camel@dbarrera_tp \
--to=dfbp@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=rvl@ttg-edam.nl \
--cc=sco@adviseo.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.