From: Josh Brooks <user@mail.econolodgetulsa.com>
To: "Joseph D. Wagner" <wagnerjd@prodigy.net>
Cc: "'Billy Rose'" <billyrose@billyrose.net>, <bp@dynastytech.com>,
<linux-kernel@vger.kernel.org>, <felipewd@terra.com.br>
Subject: RE: CPU failures ... or something else ?
Date: Wed, 25 Dec 2002 22:35:16 -0800 (PST) [thread overview]
Message-ID: <20021225223454.I64865-100000@mail.econolodgetulsa.com> (raw)
In-Reply-To: <001d01c2aca5$dd35ff40$b9293a41@joe>
Well, that's the thing - I _didn't_ switch cpus. Sometimes the error is
cpu 0, sometimes it is cpu 1.
On Thu, 26 Dec 2002, Joseph D. Wagner wrote:
> > usually it says proc #1 in the error, but
> > the first time it said proc #0 - is that
> > interesting ?
>
> proc 0 and proc 1 are CPU 0 and CPU 1, respectively. If you switched CPU's
> and now the error is on the other proc, then it IS a CPU error.
>
> Joseph Wagner
>
> P.S. In hindsight, I probably should have read the entire thread before
> responding. 8-) You live you learn.
>
> Joseph Wagner
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-12-26 6:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 4:03 Billy Rose
2002-12-26 4:04 ` Josh Brooks
2002-12-26 2:05 ` Felipe W Damasio
2002-12-26 6:13 ` Joseph D. Wagner
2002-12-26 6:35 ` Josh Brooks [this message]
2002-12-26 6:49 ` Joseph D. Wagner
2002-12-26 7:08 ` Felipe W Damasio
-- strict thread matches above, loose matches on Subject: below --
2002-12-26 4:21 Billy Rose
2002-12-26 4:48 ` Josh Brooks
2002-12-26 3:50 Billy Rose
2002-12-26 3:54 ` Josh Brooks
2002-12-26 3:31 Billy Rose
2002-12-26 3:38 ` Josh Brooks
2002-12-26 3:13 Ro0tSiEgE
2002-12-26 3:22 ` Josh Brooks
2002-12-26 6:08 ` Joseph D. Wagner
2002-12-26 1:53 Josh Brooks
2002-12-26 1:41 ` Felipe W Damasio
2002-12-26 2:02 ` Bubba
2002-12-26 3:04 ` Josh Brooks
2002-12-26 22:37 ` Pavel Machek
2002-12-26 3:09 ` Josh Brooks
2002-12-26 3:36 ` J Sloan
2002-12-26 3:39 ` Josh Brooks
2002-12-26 3:20 ` Josh Brooks
2002-12-26 6:03 ` Joseph D. Wagner
2002-12-27 23:30 ` 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=20021225223454.I64865-100000@mail.econolodgetulsa.com \
--to=user@mail.econolodgetulsa.com \
--cc=billyrose@billyrose.net \
--cc=bp@dynastytech.com \
--cc=felipewd@terra.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=wagnerjd@prodigy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®