linux-um archives
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Possible SKAS3 >= v8 bug
Date: Mon, 29 Aug 2005 17:12:48 -0500	[thread overview]
Message-ID: <43138860.6080505@theshore.net> (raw)
In-Reply-To: <200508211429.56287.blaisorblade@yahoo.it>

Blaisorblade wrote:
> Ok, I'm particularly suspicious of one patch, ptrace_ldt-reload-smp-fix, try 
> unapplying that one. I don't know exactly *how* it might trigger that crash, 
> but it seems a data corruption, and that code is doing exactly that.

I recompiled 2.6.12.5 with skas-v8 minus the ptrace_ldt-reload-smp-fix 
patch, and experienced another crash.  No console output was captured by 
my remote logging or console unit.

-Chris



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-08-29 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 14:13 [uml-devel] Possible SKAS3 >= v8 bug Christopher S. Aker
2005-08-11 21:07 ` Christopher S. Aker
2005-08-12  0:58   ` Christopher S. Aker
2005-08-21 12:29     ` Blaisorblade
2005-08-29 22:12       ` Christopher S. Aker [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=43138860.6080505@theshore.net \
    --to=caker@theshore.net \
    --cc=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.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