public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.59-mjb3 (scalability / NUMA patchset)
Date: Mon, 03 Feb 2003 10:42:02 -0800	[thread overview]
Message-ID: <315150000.1044297722@flay> (raw)
In-Reply-To: <1044297228.29537.5.camel@markh1.pdx.osdl.net>

>> The patchset contains mainly scalability and NUMA stuff, and anything 
>> else that stops things from irritating me. It's meant to be pretty stable, 
>> not so much a testing ground for new stuff.
>> 
>> I'd be very interested in feedback from anyone willing to test on any 
>> platform, however large or small.
>> 
>> http://www.aracnet.com/~fletch/linux/2.5.59/patch-2.5.59-mjb3.bz2
>> 
> 
> I tried 2.5.59-mjb3 today on our 16 processor numaq and got a boot
> hang.  I had been running 2.5.59-mjb2 previously.  I have included the
> console output and my config file.   

What gcc are you using? I'm betting 3.2 ... 2.95 seems to work fine.
(still might be an issue with the patch, just trying to track it down)

M.



  reply	other threads:[~2003-02-03 18:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  0:30 2.5.47-mjb3 (scalability / NUMA patchset) Martin J. Bligh
2002-12-09  6:11 ` 2.5.50-mjb1 " Martin J. Bligh
2002-12-09  9:06   ` William Lee Irwin III
2002-12-10  6:42   ` 2.5.50-mjb2 " Martin J. Bligh
2002-12-10  6:49     ` William Lee Irwin III
2002-12-17  8:10     ` 2.5.52-mjb1 " Martin J. Bligh
2002-12-17 15:57       ` William Lee Irwin III
2002-12-17 17:49       ` William Lee Irwin III
2002-12-17 19:31         ` Martin J. Bligh
2002-12-24  8:11       ` 2.5.53-mjb1 " Martin J. Bligh
2003-01-03  7:37         ` 2.5.54-mjb1 " Martin J. Bligh
2003-01-06  2:58           ` 2.5.54-mjb2 " Martin J. Bligh
2003-01-09  8:31             ` 2.5.54-mjb3 " Martin J. Bligh
2003-01-10  7:21               ` 2.5.55-mjb1 " Martin J. Bligh
2003-01-14  8:05                 ` 2.5.58-mjb1 " Martin J. Bligh
2003-01-17  7:11                   ` 2.5.58-mjb2 " Martin J. Bligh
2003-01-17  9:49                     ` William Lee Irwin III
2003-01-17 15:44                       ` Martin J. Bligh
2003-01-21  8:19                     ` 2.5.59-mjb1 " Martin J. Bligh
2003-01-29  2:16                       ` 2.5.59-mjb2 " Martin J. Bligh
2003-02-03  2:08                         ` 2.5.59-mjb3 " Martin J. Bligh
2003-02-03 18:33                           ` Mark Haverkamp
2003-02-03 18:42                             ` Martin J. Bligh [this message]
2003-02-03 18:55                               ` Mark Haverkamp
2003-02-03 19:03                                 ` Martin J. Bligh
2003-02-03 19:35                                   ` Mark Haverkamp
2003-02-04  8:59                                 ` Martin J. Bligh
2003-02-07  7:37                           ` 2.5.59-mjb4 " Martin J. Bligh
2003-02-09  3:26                             ` 2.5.59-mjb5 " Martin J. Bligh
2003-02-11 18:03                               ` 2.5.59-mjb6 " Martin J. Bligh

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=315150000.1044297722@flay \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@osdl.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