From: Kip Macy <kip.macy@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Kurt Garloff <kurt@garloff.de>,
Xen development list <xen-devel@lists.sourceforge.net>,
ian.pratt@cl.cam.ac.uk
Subject: Re: Linux 2.6.11 does not build SMP
Date: Sun, 13 Mar 2005 18:54:08 -0800 [thread overview]
Message-ID: <b1fa291705031318546cd80284@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503132136480.15613@chimarrao.boston.redhat.com>
On Sun, 13 Mar 2005 21:42:28 -0500 (EST), Rik van Riel <riel@redhat.com> wrote:
> On Mon, 14 Mar 2005, Ian Pratt wrote:
>
> > Guys, just remember that SMP is certainly not ready for putting in front
> > of users yet.
>
> It's been enabled in Fedora Rawhide for a few months now,
> and doesn't seem to be giving much trouble at all, at
> least not stability wise.
For you. More than half the builds I do with SMP don't make it to the
prompt. Others have frequent oopses after going through a dozen guest
boot/crash cycles.
-Kip
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-14 2:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 0:47 Linux 2.6.11 does not build SMP Ian Pratt
2005-03-14 2:42 ` Rik van Riel
2005-03-14 2:54 ` Kip Macy [this message]
2005-03-14 4:49 ` Rik van Riel
2005-03-14 5:04 ` Kip Macy
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 23:32 Kip Macy
2005-03-14 0:09 ` Kurt Garloff
2005-03-14 0:13 ` Kip Macy
2005-03-14 1:40 ` Christian Limpach
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=b1fa291705031318546cd80284@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=kurt@garloff.de \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=riel@redhat.com \
--cc=xen-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.