public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>,
	Andrew Morton <akpm@osdl.org>, Anton Blanchard <anton@samba.org>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PPC64] Improved VSID allocation algorithm
Date: Thu, 30 Sep 2004 07:53:07 +0200	[thread overview]
Message-ID: <20040930055307.GA15291@suse.de> (raw)
In-Reply-To: <20040930003846.GB25001@zax>

 On Thu, Sep 30, David Gibson wrote:

> On Wed, Sep 29, 2004 at 09:47:30PM +0200, Olaf Hering wrote:
> >  On Mon, Sep 13, David Gibson wrote:
> > 
> > > Andrew, please apply.  This patch has been tested both on SLB and
> > > segment table machines.  This new approach is far from the final word
> > > in VSID/context allocation, but it's a noticeable improvement on the
> > > old method.
> > 
> > This patch went into 2.6.9-rc2-bk2, and my p640 does not boot anymore.
> > Hangs after 'returning from prom_init', wants a power cycle.
> 
> Have you isolated the problem to the VSID allocation patch?  I think
> there may have been a number of ppc64 changes which went into
> 2.6.9-rc2-bk2.

Yes, rc2 does not boot on power3 with that patch.

-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG

  reply	other threads:[~2004-09-30  5:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13  4:11 [PPC64] Improved VSID allocation algorithm David Gibson
2004-09-29 19:47 ` Olaf Hering
2004-09-30  0:38   ` David Gibson
2004-09-30  5:53     ` Olaf Hering [this message]
2004-09-30  6:35       ` David Gibson
2004-09-30  6:40   ` Anton Blanchard
2004-09-30  6:49     ` Olaf Hering
2004-09-30  7:01     ` David Gibson
2004-09-30  8:05       ` David Gibson
2004-09-30  8:20         ` Olaf Hering

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=20040930055307.GA15291@suse.de \
    --to=olh@suse.de \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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