All of lore.kernel.org
 help / color / mirror / Atom feed
From: N N Ashok <nalkunda@cse.msu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Ethernet card interrupt conflict
Date: Mon, 07 Apr 2003 03:21:22 +0000	[thread overview]
Message-ID: <marc-lartc-104968582827785@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104906315525645@msgid-missing>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 06 April 2003 17:49, yuxiao jia scrawled:
> Hello
>
> Thanks for your reply, when two ethernet card share same IRQ, only one card
> can work
>
> for example eth0 and eth2 share same IRQ, eth0 IP address is 172.16.30.1,
> eth2 is 172.16.50.1,
>
> I only can ping gateway of eth0 (e.g 172.16.30.2), canot ping 172.16.50.2
>
> I try lilo.conf "append="noapic" and change BIOS, do not work for me
>
> I canot undetsand when Linux boot, no matther how I change slot, it only
> can boot 3 ethernet card,
> I can  run "ifconfig eth3 up" make the four card up, but still shared eth0
> and eth2 canot work well
>
> thanks
>
> yuxiao.
>
>
>
> ----- Original Message -----
> From: "N N Ashok" <nalkunda@cse.msu.edu>
> To: "yuxiao jia" <yxjia@site.uottawa.ca>; <lartc@mailman.ds9a.nl>
> Sent: Sunday, April 06, 2003 4:14 PM
> Subject: Re: [LARTC] Ethernet card interrupt conflict
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Sunday 30 March 2003 17:20, yuxiao jia scrawled:
> > > Hello all
> > >
> > > I install 4 ethernet card in my Linux router. When I use
> > >
> > > cat /proc/interrupt      it show me two interface use same IRQ
> > >
> > > ...11:...........eth0 and eth2
> > >
> > > I want to know how I can modify the eth0 to another unsued IRQ or avoid
> > > this things happen
> > >
> > > Thanks
> > >
> > > Regrads
> > >
> > > yuxiao
> >
> > I also have such an entry in my /proc/interrupts.
> >  11:     423024          XT-PIC  eth2, eth3
> >
> > They are on a 4-port Ethernet card. Also does this have any negative
>
> effect on
>
> > the performance? Just curious, cos everything seems to be working fine
> > for
>
> me
>
> > now.
> >
> > Thanks,
> > Ashok
> >
<snipped footer>

Hi,
  I just pinged my eth2 and eth3 (which have the same interrupt) and both 
responded properly to the pings. I made each one the default route to my 
machine and there was no problem.

- -- 

- -----------------------------------------------------------------------------
My public key:
   gpg --recv-keys --keyserver blackhole.pca.dfn.de DCB44F2E
- -----------------------------------------------------------------------------
"...there is nothing so unnatural as the commonplace."
Sir Arthur Conan Doyle in "Adventures of Sherlock Holmes: A Case of Identity"
- -----------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+kO61RhXpVty0Ty4RAq8qAJ0bw8QRvlQQyIIfzFgbQ3KyM1LQowCdG4ot
ibVA0+X4hAO4AAh9gBU/odY=Aq9f
-----END PGP SIGNATURE-----

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-04-07  3:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-30 22:20 [LARTC] Ethernet card interrupt conflict yuxiao jia
2003-04-06 20:14 ` N N Ashok
2003-04-06 21:49 ` yuxiao jia
2003-04-07  3:21 ` N N Ashok [this message]
2003-04-07 10:15 ` Bartek Krajnik

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=marc-lartc-104968582827785@msgid-missing \
    --to=nalkunda@cse.msu.edu \
    --cc=lartc@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.