public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: war@lucidpixels.com, linux-kernel@vger.kernel.org
Subject: Re: Broadcom BCM5702 Major Problems
Date: Sat, 15 Mar 2003 21:18:27 -0100	[thread overview]
Message-ID: <20030315221827.GB26890@suse.de> (raw)
In-Reply-To: <3E732F0F.6000806@colorfullife.com>

On Sat, Mar 15, 2003 at 02:47:59PM +0100, Manfred Spraul wrote:

 > >[*] IO-APIC support on uniprocessors
 > >
 > I think the subject is a bit misleading:
 > There seems to be a problem with interrupt routing if he enables IO-APIC 
 > support, both with a Broadcom nic and a 3com nic.
 > Either the MP table that is supplied by the bios is incorrect [wouldn't 
 > be a big surprise - I think Linux is the only OS that looks at MP tables 
 > of uniprocessor machines], or the ACPI interpreter did something wrong.

I've noticed on two seperate testboxes (x86 and x86-64) that 8139too
won't recieve packets unless I boot with 'noapic acpi=off' now.
And yes, it has to be both those options, one on its own of either
doesn't make the problem go away. 100% reproducable.

Doesn't seem to affect any other drivers I've tried though.

		Dave


  reply	other threads:[~2003-03-15 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-15 13:47 Broadcom BCM5702 Major Problems Manfred Spraul
2003-03-15 22:18 ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-16 20:43 leon j. breedt
2003-03-15 14:27 war
2003-03-15 13:15 war
2003-03-15  5:41 war
2003-03-15  9:34 ` Paul Rolland
2003-03-15  4:35 war
2003-03-15  2:32 war
2003-03-15  3:54 ` Andreas Dilger

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=20030315221827.GB26890@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=war@lucidpixels.com \
    /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