From: Blaisorblade <blaisorblade@yahoo.it>
To: Rob Landley <rob@landley.net>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SIGSEGV and SA_NODEFER
Date: Fri, 21 Jan 2005 20:58:16 +0100 [thread overview]
Message-ID: <200501212058.16992.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200501211318.16848.rob@landley.net>
On Friday 21 January 2005 19:18, Rob Landley wrote:
> On Friday 21 January 2005 07:35 am, Blaisorblade wrote:
> > > Ooh, ooh! Hang in TT mode is what I'm seeing with my makefile hang.
> > > (sh -x dosn't help if the makefile doesn't call out to stuff with it.)
> > >
> > > If the previous patch doesn't address it, is there a new patch I could
> > > try?
> >
> > Well, you solved this problem with the 2.6.11-rc1-mm2, right (from the
> > message below)?
>
> With 2.6.11-rc1-mm2, my toolchain build runs through to completion under
> UML. (Very very slowly, but it does. Tested on a 1.6 ghz 2 meg cache
> computer, which runs it under UML at about the speed of my 700 mhz 128k
> cache laptop without UML. But hey, it's using tt mode, and completing
> correctly. That's the important thing...)
>
> > The patch which was merged there is the one posted with title
> > "[uml-devel] [PATCH] Fix stack corruption" on this list..., I guess... it
> > will be in 2.6.9-bs6 and 2.6.10-bb1 (both to release) - are you willing
> > to test one of them, when I do the release? I'd be very thankful to
> > accept your help...
>
> I'll happily try out 2.6.10-bb1, sure.
> The mm2 changelog says it has:
That is -mm1, I've already looked at both... the patches listed below are
minor fixes / improvements...
The name of the 2.6.11-rc1-mm2 patch which probably fixed your issue is:
uml-fix-a-stack-corruption-crash.patch
If it's not a problem, try removing it from -mm2 and recompiling, and test if
you get the crash with the new kernel (which is what I expect)...
>
> More later, lunch is over...
Here, now, I must go to dinner... bye!
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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-01-21 19:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 21:28 [uml-devel] SIGSEGV and SA_NODEFER Jeff Dike
2005-01-20 0:07 ` Blaisorblade
2005-01-20 3:52 ` Rob Landley
2005-01-21 12:35 ` Blaisorblade
2005-01-21 18:18 ` Rob Landley
2005-01-21 19:58 ` Blaisorblade [this message]
2005-01-22 16:34 ` Rob Landley
2005-01-24 19:45 ` Blaisorblade
2005-01-25 1:38 ` Rob Landley
[not found] ` <20050125084506.GA562@bytesex>
2005-01-25 10:16 ` Blaisorblade
2005-01-25 10:16 ` Rob Landley
2005-01-25 11:40 ` Blaisorblade
2005-01-25 17:30 ` Rob Landley
2005-01-25 19:34 ` Blaisorblade
2005-01-25 19:30 ` Rob Landley
2005-01-25 20:50 ` Blaisorblade
2005-01-25 22:43 ` Rob Landley
2005-01-21 13:09 ` Blaisorblade
2005-01-21 16:56 ` 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=200501212058.16992.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=rob@landley.net \
--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