All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: further IO-APIC oddities
Date: Thu, 8 Aug 2002 12:18:51 -0700	[thread overview]
Message-ID: <20020808191851.GE15685@holomorphy.com> (raw)
In-Reply-To: <73720000.1028830446@flay>

At some point in the past, I wrote:
>> It's different from 2.5.29, I can follow up with that. 2.5.29 saw all 0's,
>> so whatever it was that was scribbling over the MPC table and making the
>> ID's all 0, it's scribbling on something else now (probably mem_map).

On Thu, Aug 08, 2002 at 11:14:06AM -0700, Martin J. Bligh wrote:
> I thought that was only if you reduced NR_CPUS? And you shouldn't
> need to read the IOAPIC tables to do that - the basic array was getting
> overwritten. Or am I confusing at least two different bugs?

Sorry, I'm being obtuse. What I had in mind here was:

(1) there's been a longstanding bug where the MPC table entries with
	the IO-APIC ID's gets zeroed out
(2) this bug mysteriously went away, even though we never tracked it down
(3) bugs that smell of mem_map getting stomped on are cropping up

... and I suspect these three things are related, e.g. the MPC stuff moved
or link order changed or some such Heisenbug-ish nonsense and now it's
hitting something else. The NR_CPUS bit isn't even bootable (the panic()
happens before console_init() IIRC) so it's not quite that one. =)

Cheers,
Bill

      reply	other threads:[~2002-08-08 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 16:28 further IO-APIC oddities William Lee Irwin III
2002-08-08 17:13 ` William Lee Irwin III
2002-08-08 17:56 ` Martin J. Bligh
2002-08-08 18:07   ` William Lee Irwin III
2002-08-08 18:14     ` Martin J. Bligh
2002-08-08 19:18       ` William Lee Irwin III [this message]

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=20020808191851.GE15685@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=Martin.Bligh@us.ibm.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.