From: Len Brown <len.brown@intel.com>
To: Marc Rieffel <marc@paracel.com>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel@vger.kernel.org
Subject: RE: PROBLEM: Second processor not responding in 2.4.21 and later
Date: 24 Apr 2004 04:28:29 -0400 [thread overview]
Message-ID: <1082795309.22229.8.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F93AE@hdsmsx403.hd.intel.com>
On Tue, 2004-04-20 at 12:29, Marc Rieffel wrote:
> It looks like things changed dramatically from 2.4.20-pre4 to
> 2.4.20-pre5. Can you help me figure out which of the changes was
> responsible?
>
> Thanks.
>
> Kernel Fail Pass Fail%
>
> 2.4.18-27.7.xsmp 0 3314 0.0000
> 2.4.18 5 4206 0.0012
> 2.4.19 12 25786 0.0005
> 2.4.20-pre4 2 586 0.0034
> 2.4.20-pre5 2 49 0.0392
> 2.4.20-pre6 12 745 0.0159
> 2.4.20 55 3128 0.0173
> 2.4.20-20.7smp 483 15427 0.0304
> 2.4.21-4.0.1.ELsmp 155 7278 0.0209
While a difference between 2.4.20-pre4 and -pre5 may be a clue,
it isn't the root cause, because they're both broken.
Looks like only 2.4.18-27.7.xsmp (whatever that is) got 0 failures.
Any chance you can run a test with, say, 2.6.5?
It might also be interesting to know what compiler built each kernel..
cheers,
-Len
next parent reply other threads:[~2004-04-24 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F93AE@hdsmsx403.hd.intel.com>
2004-04-24 8:28 ` Len Brown [this message]
2004-04-26 16:00 PROBLEM: Second processor not responding in 2.4.21 and later Marc Rieffel
-- strict thread matches above, loose matches on Subject: below --
2004-04-20 16:29 Marc Rieffel
2004-04-16 15:45 Marc Rieffel
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=1082795309.22229.8.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@paracel.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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