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
Subject: [uml-devel] 2.6.18-skas-v9-pre9 broken
Date: Thu, 05 Oct 2006 16:59:11 -0500	[thread overview]
Message-ID: <4525802F.1080900@theshore.net> (raw)

Blaisorblade,

I recently deployed a 2.6.18-skas3-v9-pre9 host, and some users weren't 
able to boot UML beyond "VFS: Mounted root (ext3 filesystem) readonly". 
  As it turns out, only 2.6-um kernels were affected, 2.4-um worked fine.

This happened both in skas3 and skas0 modes.  Jeff graciously took a 
look at some straces, and his comment was that "something broke page 
fault handling generically".

The traces are here:

http://www.theshore.net/~caker/uml/skas2.6.18-uml_trace.txt (skas3)
http://www.theshore.net/~caker/uml/skas2.6.18-uml_trace_skas0.txt

Reverting back to a skas3-v8.2 kernel fixed it.

HTH,
-Chris


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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:[~2006-10-05 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 21:59 Christopher S. Aker [this message]
2006-10-06 21:54 ` [uml-devel] 2.6.18-skas-v9-pre9 broken Blaisorblade
2006-10-06 23:57   ` Christopher S. Aker
2006-10-21  1:05 ` Blaisorblade
2006-12-21 15:36   ` Christopher S. Aker
2006-12-26  5:39     ` Christopher S. Aker

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=4525802F.1080900@theshore.net \
    --to=caker@theshore.net \
    --cc=blaisorblade@yahoo.it \
    --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