From: Feng Xian <fxian@fxian.jukie.net>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: APIC problem or 3com 3c590 driver problem in smp kernel 2.4.x
Date: Sat, 2 Jun 2001 00:08:03 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0106020005170.4773-100000@tiger> (raw)
In-Reply-To: <20010601114243.G754@nightmaster.csn.tu-chemnitz.de>
It's our own's card. so it could be the card's problem. does the pci
device have to do some special thing to support APIC? my card won't work
properly on uni-processor with APIC enable kernel or smp kernel when the
card is sharing IRQ with some other pci devices.
Alex
On Fri, 1 Jun 2001, Ingo Oeser wrote:
> On Thu, May 31, 2001 at 12:27:07PM -0400, Feng Xian wrote:
> > The driver for my pci device, I have the SA_SHIRQ set.
>
> What kind of PCI device do you have? I had this problem once with
> an PCI-Matchmaker[1] based board (for which we still have the wrong
> PCI-ID btw, but my patch was rejected twice...).
>
> > Actually what I am thinking it may be APIC support problem. I rebuild my
> > kernel to use single cpu without APIC support, my device and 3c905 both
> > work fine. they don't work for SMP kernel (APIC is by default enabled)
> > Then I configured my uni-processor kernel to enable the APIC support, my
> > device won't work with the 3c905, just exactly same as it behaves in the
> > SMP kernel.
>
> With 2.2 I also had this without APIC.
>
> I have been flooded with interrupts which have been intended for
> the Cyclone card (3c905B 100BaseTX), and exited the ISR quickly
> after querying the interrupt register of my Matchmaker board
> without any ACKing, but the Cyclone never got these interrupts
> anymore.
>
> But is doesn't seem to be a 3c905 based problem, as I have
>
> 11: 95772726 XT-PIC es1371, eth0, eth1
>
> in /proc/interrupts where eth0 and eth1 are both Cyclones.
> Even the vga card has IRQ 11 assigned.
>
> So this is not really unknown ;-)
>
> Regards
>
> Ingo Oeser
>
> [1] class 0b40, vendor id: 10e8, device id: 807d
>
--
Feng Xian
_o) .~. (o_
/\\ /V\ //\
_\_V // \\ V_/_
/( )\
^^-^^
ALEX
next prev parent reply other threads:[~2001-06-02 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 2:07 Feng Xian
2001-05-31 16:15 ` Bogdan Costescu
2001-05-31 16:27 ` Feng Xian
2001-06-01 9:42 ` Ingo Oeser
2001-06-02 4:08 ` Feng Xian [this message]
2001-06-02 16:06 ` Alan Cox
2001-06-02 18:00 ` Feng Xian
2001-06-04 13:17 ` Maciej W. Rozycki
[not found] <Pine.LNX.4.10.10105311110240.759-100000@coffee.psychology.mcmaster.ca>
2001-05-31 16:23 ` Feng Xian
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=Pine.LNX.4.33.0106020005170.4773-100000@tiger \
--to=fxian@fxian.jukie.net \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--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
all inboxes | Powered by JetHome®