From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: qemu segfaulting when booting ext3 image
Date: Tue, 03 May 2011 11:43:22 -0700 [thread overview]
Message-ID: <4DC04CCA.2030100@intel.com> (raw)
In-Reply-To: <4DC03C43.8080507@windriver.com>
On 05/03/2011 10:32 AM, Mark Hatle wrote:
> On 5/3/11 12:27 PM, Khem Raj wrote:
>> On Mon, May 2, 2011 at 5:41 PM, Zhai, Edwin<edwin.zhai@intel.com> wrote:
>>> Did you installed Nvidia proprietary driver? Any error mesg from the runqemu
>>> script?
>>
>> yes I did and I think that could be a culprit but then why would it
>> work with nfs boot.
>> there is no useful message from script it just collapses
>
> The script tries to detect the nvidia drivers. If it finds them is supposed to
> issue a warning. Sounds like your system might not have a version that it knows
> how to detect.
The Nvidia libGL bug caused a segfault in qemu when booting images, so
it should be pretty obvious if that's what's causing it.
Given that Khem is booting the nfs version successfully, and not seeing
any error message, I think this might be a new error.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-05-03 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 16:34 qemu segfaulting when booting ext3 image Khem Raj
2011-05-03 0:41 ` Zhai, Edwin
2011-05-03 17:27 ` Khem Raj
2011-05-03 17:32 ` Mark Hatle
2011-05-03 17:47 ` Khem Raj
2011-05-03 17:55 ` Mark Hatle
2011-05-03 18:43 ` Scott Garman [this message]
2011-05-03 19:08 ` Khem Raj
2011-05-05 0:40 ` Zhai, Edwin
2011-05-05 3:40 ` Khem Raj
2011-05-05 6:31 ` Zhai, Edwin
2011-05-05 6:40 ` Khem Raj
2011-05-03 20:29 ` Scott Garman
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=4DC04CCA.2030100@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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