From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: qemu segfaulting when booting ext3 image
Date: Tue, 3 May 2011 12:32:51 -0500 [thread overview]
Message-ID: <4DC03C43.8080507@windriver.com> (raw)
In-Reply-To: <BANLkTimUw9+kWHwdw5dZ0=kUZuNSsorsdA@mail.gmail.com>
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.
>> I can't figure out one case that nfs root works and ext3 image doesn't...
Good question, I don't know. In my experience both NFS and ext3 root crashes
with the nvidia drivers. I have a patch to the version of QEMU I use that
disables all of GL to work around the problem.
I believe it's mhatle/qemu on poky-contrib... but it hasn't been updated for a
while now.
--Mark
>>
>>
>> Khem Raj wrote:
>>>
>>> Hi
>>>
>>> I am seeing qemu segfaulting when booting ext3 image. The same rootfs
>>> boots fine over nfs. It does not give any useful message
>>> as to what happened. I am using the runqemu script. Same used to work
>>> fine 3 weeks back. I tried to blame compilers but the behavior
>>> is same irrespective of gcc version I use or even eglibc/uclibc
>>>
>>> Its on x86_64/ubuntu 11.04 host.
>>>
>>> Anyone experiencing it ? bisecting can be a long excercise for this.
>>>
>>> Thanks
>>> -Khem
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-05-03 17:35 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 [this message]
2011-05-03 17:47 ` Khem Raj
2011-05-03 17:55 ` Mark Hatle
2011-05-03 18:43 ` Scott Garman
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=4DC03C43.8080507@windriver.com \
--to=mark.hatle@windriver.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 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.