From: "Christopher S. Aker" <caker@theshore.net>
To: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] 2.6.10-rc2-mm3 + incrementals - Kernel panic - not syncing: Segfault with no mm
Date: Sat, 27 Nov 2004 08:43:03 -0600 [thread overview]
Message-ID: <092f01c4d48f$67dbdad0$0201a8c0@hawk> (raw)
> Host: 2.6.9+skas-v7
Correction: Host == 2.6.10-rc2-bk7
Also, I just saw Bodo's post with the same topic, altough my trace is slightly
different..
-Chris
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-11-27 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 14:43 Christopher S. Aker [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-27 14:37 [uml-devel] 2.6.10-rc2-mm3 + incrementals - Kernel panic - not syncing: Segfault with no mm Christopher S. Aker
2004-11-28 21:07 ` 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='092f01c4d48f$67dbdad0$0201a8c0@hawk' \
--to=caker@theshore.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