From: Gerry Reno <greno@verizon.net>
To: xen-devel@lists.xensource.com
Subject: Re: bug: kernel 2.6.37-12 READ FPDMA QUEUED
Date: Fri, 14 Jan 2011 10:11:26 -0500 [thread overview]
Message-ID: <4D30679E.5060803@verizon.net> (raw)
In-Reply-To: <1294995189.8240.80.camel@zakaz.uk.xensource.com>
On 01/14/2011 03:53 AM, Ian Campbell wrote:
> On 01/13/2011 04:42 PM, Konrad Rzeszutek Wilk wrote:
>
>> On Thu, 2011-01-13 at 21:53 +0000, Gerry Reno wrote:
>>
>>> Please try. Wait .. are you running this with Xen hypervisor?
>>>
>> Not yet.
>>
> Um, so why on earth are you posting to xen-devel about it then? And did
> you really not think it was worth mentioning this fact prominently up
> front?
>
The whole point of the exercise was to get dom0 and Xen working on this
machine.
On the way to that I found that I could not even get 2.6.37 running at
all on the baremetal.
I figured there was just some kernel switch I needed so I searched and
then posted on the xen-devel list thinking someone would know what
switch might be necessary. But now it seems the problem is somewhat
more involved than just a simple setting.
> If you have an issue with a bare metal kernel supplied by Ubuntu then
> you should be reporting it to the Ubuntu kernel maintainers in the first
> instance.
>
And I have. I found a Ubuntu bug,
https://bugs.launchpad.net/ubuntu/+bug/550559, that described the same
problem and posted my findings into it. As have many others.
Sorry, if this issue was of no interest to you.
prev parent reply other threads:[~2011-01-14 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 19:23 bug: kernel 2.6.37-12 READ FPDMA QUEUED Gerry Reno
2011-01-13 20:21 ` Konrad Rzeszutek Wilk
2011-01-13 20:41 ` Gerry Reno
2011-01-13 21:42 ` Konrad Rzeszutek Wilk
2011-01-13 21:53 ` Gerry Reno
2011-01-14 8:53 ` Ian Campbell
2011-01-14 15:11 ` Gerry Reno [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=4D30679E.5060803@verizon.net \
--to=greno@verizon.net \
--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.