From: Jeff Dike <jdike@addtoit.com>
To: Peter <p.repliesignored@rimuhosting.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.6.11 + uml.sf.net patches panic
Date: Thu, 03 Mar 2005 13:53:23 -0500 [thread overview]
Message-ID: <200503031853.j23IrNDS003496@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 03 Mar 2005 15:53:07 +1300." <42267C13.1060703@rimuhosting.com>
p.repliesignored@rimuhosting.com said:
> I'm happy to carry on using vanilla 2.6.11. But hopefully the stack
> trace below triggers some insight into a problem with one of the
> latest uml.sf.net patches.
The write_ldt just above the segfault in both stacks looks suspicious.
Could you try backing out the ldt patches:
skas-hold-own-ldt
ldt-use-stub
and see if the panic goes away?
Jeff
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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-03-03 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 2:53 [uml-devel] 2.6.11 + uml.sf.net patches panic Peter
2005-03-03 18:53 ` Jeff Dike [this message]
2005-03-04 14:23 ` Bodo Stroesser
2005-03-04 15:08 ` Bodo Stroesser
2005-03-05 23:24 ` [uml-devel] 2.6.11 + uml.sf.net patches panic (now fixed, replaced by CPU problem) Peter
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=200503031853.j23IrNDS003496@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=p.repliesignored@rimuhosting.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