From: Blaisorblade <blaisorblade@yahoo.it>
To: Kai Tan <mineown@hotmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net, jdike@addtoit.com,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Uml left showstopper bugs for 2.6.14
Date: Wed, 2 Nov 2005 23:47:37 +0100 [thread overview]
Message-ID: <200511022347.37645.blaisorblade@yahoo.it> (raw)
In-Reply-To: <BAY101-F4507935C4D38603757606B66E0@phx.gbl>
On Wednesday 02 November 2005 22:44, Kai Tan wrote:
> I tried the first patch, got the following error:
>
> Kernel panic - not syncing: copy_context_skas0 : failed to wait for
> SIGUSR1/SIGTRAP, pid = 7182, n = 7182, errno = 0, status = 0xb7f
Ok, segmentation fault, again:
$ ./testprogs/waitstatus $[0xb7f]
WSTOPSIG(status) is 11
The signal is: Segmentation fault
> I got the same error even after applying the second patch.
Oh, sorry.
Can you just try doing a "make clean" and forcing a full recompilation? In any
case, I will try investigating further... I'll probably request you to give
me the complete binary (without debug info and compressed) along with
your .config. Please save them for now, I must check further before...
For now, IIRC you can keep running with mode=tt, right?
> My run command is the following:
>
> linux stderr=1 ubd0=../../root_fs.rh-7.2-full.pristine.20020312
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
____________________________________
Con Yahoo! Mail proteggi la tua casella di posta da virus e posta indesiderata
http://mail.yahoo.com
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-02 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 19:18 [uml-devel] Uml left showstopper bugs for 2.6.14 Blaisorblade
2005-10-09 19:37 ` [uml-devel] [PATCH 1/6] Uml: hide commands when not being verbose Paolo 'Blaisorblade' Giarrusso
2005-10-09 19:37 ` [uml-devel] [PATCH 2/6] uml: add mode=skas0 as a synonym of skas0 Paolo 'Blaisorblade' Giarrusso
2005-10-09 19:37 ` [uml-devel] [PATCH 3/6] uml: allow building .s/.i/.lst files from userspace files Paolo 'Blaisorblade' Giarrusso
2005-10-09 19:37 ` [uml-devel] [PATCH 4/6] uml: restore include breakage, breaking binary format of COW driver Paolo 'Blaisorblade' Giarrusso
2005-10-09 19:37 ` [uml-devel] [PATCH 5/6] uml: cleanup byte order macros for " Paolo 'Blaisorblade' Giarrusso
2005-10-09 19:37 ` [uml-devel] [PATCH 6/6] uml: cleanup whitespace " Paolo 'Blaisorblade' Giarrusso
2005-10-09 19:42 ` [uml-devel] Uml left showstopper bugs for 2.6.14 Blaisorblade
2005-11-02 21:44 ` Kai Tan
2005-11-02 22:47 ` Blaisorblade [this message]
2005-10-09 22:41 ` [uml-devel] " Jeff Dike
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=200511022347.37645.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mineown@hotmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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