From: Gordon J Lee <gordonl@world.std.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IBM x360 2.2.x boot failure, 2.4.9 works fine
Date: Fri, 15 Mar 2002 20:50:35 -0500 [thread overview]
Message-ID: <3C92A4EB.C50ED834@world.std.com> (raw)
In-Reply-To: <3C927F3E.7C7FB075@world.std.com> <20020315233441.GG5563@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
Thanks for the rapid replies,
> Eeek, these machines are now in the wild? Didn't realize this :)
Yes. They are still ramping up production, and evals are scarce.
I am pretty excited about it, because on paper, even without
the hyperthreading, they should run pretty fast for I/O intensive
workloads. My current eval project is to get some empirical
performance numbers on a particular application.
> I don't know if anyone ever tried a 2.2.x kernel on these boxes :)
I'm first! Lucky me! :-)
> Is there a reason you _really_ need a 2.2.x kernel for this machine?
Longterm no, shortterm yes,
We have some modifications to the 2.2.x kernel/drivers that would cost
us some time to migrate to 2.4.x. We expect to do this, but not within
the short eval period during which I have the box. My immediate goal
is to get it running enough to take performance measurements so we
can clearly quantify the cost/benefit of migrating to this box.
> You also might try a UP 2.2.x kernel on this box to see if the problem
> is in the parsing of the APIC tables (as I think it is.)
As a matter of fact, we did try a UP 2.2.x kernel, and it worked. But then
we only have one CPU, and where is the fun in that ? :-)
So I suppose this gives further support to the mishandled APIC table
theory.
I am interested and motivated to understand the details of APIC's further.
If I were to attempt to patch up a 2.2.x kernel to workaround this problem,
what documentation should I have on hand ? I have an Intel SMP 1.4
doc, although I haven't studied it in detail yet. Is this sufficient or
are
there other Must Have documents that I will need ?
- GL
[-- Attachment #2: Card for Gordon J Lee --]
[-- Type: text/x-vcard, Size: 428 bytes --]
begin:vcard
n:Lee;Gordon
tel;fax:(617) 354-9272
tel;home:(617) 576-1779
tel;work:(617) 354-9292 x108
x-mozilla-html:TRUE
url:http://www.mazunetworks.com
org:Mazu Networks
adr:;;50 Cushing Street;Cambridge;MA;02138;USA
version:2.1
email;internet:gordonl@world.std.com
title:Principal Software Engineer
note;quoted-printable:125 Cambridge Park Drive=0D=0ACambridge, MA 02140=0D=0A=0D=0A
x-mozilla-cpt:;0
fn:Gordon Lee
end:vcard
next prev parent reply other threads:[~2002-03-16 1:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 23:09 IBM x360 2.2.x boot failure, 2.4.9 works fine Gordon J Lee
2002-03-15 23:34 ` Greg KH
2002-03-16 0:06 ` James Cleverdon
2002-03-16 1:50 ` Gordon J Lee [this message]
2002-03-16 5:58 ` Greg KH
2002-03-17 19:43 ` Jack F. Vogel
2002-03-15 23:43 ` Greg KH
2002-03-16 2:46 ` Gordon J Lee
2002-03-16 5:55 ` Greg KH
2002-03-16 17:27 ` Gordon J Lee
2002-03-16 17:34 ` Greg KH
2002-03-16 17:53 ` Gordon J Lee
2002-03-16 19:40 ` Greg KH
2002-03-16 19:54 ` Dave Jones
2002-03-16 20:51 ` Alan Cox
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=3C92A4EB.C50ED834@world.std.com \
--to=gordonl@world.std.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 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.