mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, adurbin@google.com
Subject: Re: 2.6.18-mm1
Date: Wed, 27 Sep 2006 08:08:09 -0600	[thread overview]
Message-ID: <m1hcyto112.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200609270951.17124.ak@suse.de> (Andi Kleen's message of "Wed, 27 Sep 2006 09:51:17 +0200")

Andi Kleen <ak@suse.de> writes:

> On Wednesday 27 September 2006 09:39, Eric W. Biederman wrote:
>> Andi Kleen <ak@suse.de> writes:
>> 
>> > On Wednesday 27 September 2006 04:04, Eric W. Biederman wrote:
>> >> 
>> >> When I apply:
>> >> x86_64-mm-insert-ioapics-and-local-apic-into-resource-map
>> >> 
>> >> My e1000 fails to initializes and complains about a bad eeprom checksum.
>> >> I haven't tracked this down to root cause yet and I am in the process of
>> > building
>> >> 2.6.18-mm1 with just that patch reverted to confirm that is the only cause.
>> >
>> > Is this with Linux BIOS?
>> 
>> Yes.  Not that it matters in this case.
>
> Well Linus BIOS is known to play very fast-and-lose regarding supplying
> correct BIOS tables.

Agreed it does tend to push the envelop of what is allowed, and doesn't
try to work around OS bugs.  Which does tend to expose things.

> Perhaps it conflicts with a broken e820 map?

No. Did you not get the other part of the discussion?

The reservation was wrong because those IOAPICs were on ordinary pci
devices.  So the two reservations for the same resource conflicted,
so the pci allocator tried to move the pci device.

The problem is totally contained within the patch under discussion.

The role LinuxBIOS plays seems to be that it is atypical to enable
ioapics as ordinary pci devices.

Eric

  reply	other threads:[~2006-09-27 14:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 11:02 2.6.18-mm1 Andrew Morton
2006-09-24 12:46 ` 2.6.18-mm1 Russell King
2006-09-24 13:11   ` 2.6.18-mm1 Russell King
2006-09-24 13:22   ` 2.6.18-mm1 Petr Baudis
2006-09-24 14:20     ` 2.6.18-mm1 Russell King
2006-09-24 14:29       ` 2.6.18-mm1 Petr Baudis
2006-09-24 14:47         ` 2.6.18-mm1 Russell King
2006-09-24 16:55           ` 2.6.18-mm1 Petr Baudis
2006-09-24 18:48           ` 2.6.18-mm1 Junio C Hamano
2006-09-24 21:34             ` 2.6.18-mm1 Russell King
2006-09-24 21:56               ` 2.6.18-mm1 Andrew Morton
2006-09-24 22:07               ` 2.6.18-mm1 Junio C Hamano
2006-09-24 16:35 ` 2.6.18-mm1 Dmitry Torokhov
2006-09-24 17:06   ` 2.6.18-mm1 Andrew Morton
2006-09-27  2:04 ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  3:11   ` 2.6.18-mm1 Andrew Morton
2006-09-27  5:12     ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  5:44       ` 2.6.18-mm1 Aaron Durbin
2006-09-27  6:20         ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  7:13   ` 2.6.18-mm1 Andi Kleen
2006-09-27  7:39     ` 2.6.18-mm1 Eric W. Biederman
2006-09-27  7:51       ` 2.6.18-mm1 Andi Kleen
2006-09-27 14:08         ` Eric W. Biederman [this message]
2006-09-27 22:06           ` 2.6.18-mm1 Aaron Durbin
2006-09-27 23:06             ` 2.6.18-mm1 Andrew Morton
2006-09-27  9:25 ` 2.6.18-mm1 Andy Whitcroft
2006-09-27 16:12   ` 2.6.18-mm1 Andrew Morton
2006-09-27 16:50     ` 2.6.18-mm1 Andy Whitcroft

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=m1hcyto112.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=adurbin@google.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome