From: "Christopher S. Aker" <caker@theshore.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.6.18-skas-v9-pre9 broken
Date: Tue, 26 Dec 2006 00:39:59 -0500 [thread overview]
Message-ID: <4590B5AF.10303@theshore.net> (raw)
In-Reply-To: <458AAA0D.4020507@theshore.net>
Christopher S. Aker wrote:
> Blaisorblade wrote:
>> An important question: you reverted to a 2.6.18 + skas kernel or a 2.6.17 one?
>> A similar bug is being discussed about a regression in 2.6.18 vanilla...
> All my hosts are running at most 2.6.16.x, so this very well could be a
> regression in post 2.6.16 kernels.
Confirmed. This is a regression in post 2.6.16.x kernels (well, at least
2.6.19). Had a user hit the "VFS: Mounted root (ext3 filesystem)
readonly" hang on a 2.6.19 kernel with skas3-v8.2, running 2.6.19-um
Any ideas?
-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
prev parent reply other threads:[~2006-12-26 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 21:59 [uml-devel] 2.6.18-skas-v9-pre9 broken Christopher S. Aker
2006-10-06 21:54 ` 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 [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=4590B5AF.10303@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.