RE: Help - IRQ problems probably

["Burke, Thomas G." <thomas_g_burke md northgrum com>]

As I recall, it's actually the other way around.  If my machine wants to
talk to your machine (ie netscape to apache httpd), my machine sends a
request to your machine's http port.  Your machine (if it's running a httpd)
replies from that port, and sets aside one of the higher ports for the
actual communication to run through, thereby freeing up the actual http port
to listen for new requests.

> -----Original Message-----
> From:	Mark W. Knecht [SMTP:mknecht controlnet com]
> Sent:	Tuesday, July 10, 2001 1:51 PM
> To:	redhat-install-list redhat com
> Subject:	RE: Help - IRQ problems probably
> 
> Brad,
>    Normally (and I'm not really knowledgeable here, but I'll poke around a
> bit) when another machine attempts to talk to my machine, saying it wants
> DNS services, or FTP services or what not, the first thing it does is
> sends
> a packet at a high port number, like 7101, requesting service on the 'well
> known port. The high port number is somewhat random, as far as I know.
> (Train me someone!!) This way a machine can query other machines for
> services without actually using the service. I suppose this works better
> for
> security or something.
> 
>    I have seen some problems like this with passive transfers across
> firewalls, and certainly not being able to open a port sounds like the
> port
> is closed. Ports being closed are what firewalls do best. Are you running
> a
> firewall on this machine? Is ipchains running or something?
> 
>    Again, I agree with Thomas. The NIC is up, and the fact that it's
> talking
> to you about ports implies that it's communicating with your OS. For this
> to
> happen, I think IRQ's would have to be working, but please remember, I'm a
> chip designer, acknowledged permanent Linux newbie, and not a
> knowledgeable
> IT guy. I think your problem lies elsewhere.
> 
> Take care,
> Mark
> 
> -----Original Message-----
> From: redhat-install-list-admin redhat com
> [mailto:redhat-install-list-admin redhat com]On Behalf Of Burke, Thomas
> G.
> Sent: Tuesday, July 10, 2001 10:09 AM
> To: 'redhat-install-list redhat com'
> Subject: RE: Help - IRQ problems probably
> 
> 
> This isn't NIC not working...  It says it's successfully started.
> Something
> istrying to use port 7101 & is being disallowed.  Now, I dunno why that
> would change depending upon installation of an IDE drive, but there it
> is...
> 
> > -----Original Message-----
> > From:	Mugleston, Brad [SMTP:brad mugleston gwl com]
> > Sent:	Tuesday, July 10, 2001 1:00 PM
> > To:	redhat-install-list redhat com
> > Cc:	'home ecentral'
> > Subject:	RE: Help - IRQ problems probably
> >
> > Mark,
> >
> > Thanks for the information.  And to answer your question - Yep, it's
> > broke.
> > My NIC doesn't work with my IDE's installed.  I get the following:
> >
> > 	Jul  8 22:35:29 mugleston network: Bringing up interface eth0
> > succeeded
> >
> > 	Jul  8 22:35:42 mugleston local: Cannot open TCPIP port 7101
> > 	Jul  8 22:35:42 mugleston local: Better try another port!
> >
> > I assumed it was my IRQ (both the IDE card and the NEC use IRQ 11) but
> > checking under windows it uses both there also.  Any idea why I cannot
> > open
> > my TCPIP port 7101 and how I would get it to try a different port?
> >
> > Brad
> >
> > > -----Original Message-----
> > > From:	Mark W. Knecht [SMTP:mknecht controlnet com]
> > > Sent:	Monday, July 09, 2001 4:59 PM
> > > To:	redhat-install-list redhat com
> > > Cc:	'home ecentral'
> > > Subject:	RE: Help - IRQ problems probably
> > >
> > > Brad,
> > >    First of all, why do you feel you need to change it? Are you seeing
> > > some
> > > performance problems? If not, then PCI devices are designed to share
> > > interrupts, and if the drivers are written correctly they do this just
> > > fine.
> > >
> > >    On the other hand, assuming you do have a reason, or just want to
> > play,
> > > then there are a number of issues to address here. The first is that
> to
> > do
> > > this you'll need to have a manual for your motherboard the identifies
> > how
> > > PCI Interrupts (different than the interrupts your are showing below)
> > are
> > > physically routed. Most PCI motherboards (like my Asus A7V133)
> actually
> > > force certain slots to share an INTR line. This line, or trace on the
> > > motherboard is eventually hooked to a IRQ inside the chipset. If your
> > > Ethernet and ATA controller are in slots that share an INTR line, then
> > no
> > > amount of playing with BIOS or config files will ever put them on
> > > different
> > > IRQ's. You'll just move them both around. If this is the case, then
> one
> > of
> > > the cards will need to be moved to another slot.
> > >
> > >    If you want to see what we're all faced with in the area of using
> PCs
> > > to
> > > record music, go look in the User Conferences at www.digidesign.com
> > > (Support - User Conferences - Pro Tools LE for Windows
> Troubleshooting)
> > > and
> > > you'll find a tremendous amount of info about exactly that problem. On
> > > these
> > > machines we're pretty much forced to run two disks, one for Windows
> and
> > > one
> > > for audio, and everyone deals with this stuff all the time.
> > >
> > >    My recommendation - If it ain't broke, don't fix it.
> > >
> > > Mark
> > >
> > > -----Original Message-----
> > > From: redhat-install-list-admin redhat com
> > > [mailto:redhat-install-list-admin redhat com]On Behalf Of Mugleston,
> > > Brad
> > > Sent: Monday, July 09, 2001 3:14 PM
> > > To: RedHat
> > > Cc: home ecentral
> > > Subject: Help - IRQ problems probably
> > >
> > >
> > > I'm back,  I'm the one that had the problem with the new IDE card.
> Well
> > > it's working but now my Network card isn't working.  Following is some
> > of
> > > my
> > > "/var/log/messages" file.   To me it looks like my IDE card and
> Ethernet
> > > card (eth0) are both using IRQ 11. My question is how do I change
> that?
> > > When I was probing my IDE card it had IRQ 11 and so does the eth0
> card.
> > I
> > > know the IDE card is Plug and Play so can I just change it?  If so
> what
> > do
> > > you recommend?
> > >
> > > Thanks
> > >
> > > Brad
> > >
> > >
> > >
> > > Jul  8 22:35:30 mugleston kernel: ide_setup: ide1=0xdcd8,0xdcd2,11
> > > Jul  8 22:35:30 mugleston kernel:
> > > Jul  8 22:35:30 mugleston kernel: ide_setup: ide2=0xdcc8,0xdcd6,11
> > > Jul  8 22:35:30 mugleston kernel:
> > >
> > >
> > > Jul  8 22:35:30 mugleston kernel: PIIX4: IDE controller on PCI bus 00
> > dev
> > > 39
> > > Jul  8 22:35:30 mugleston kernel: PIIX4: not 100% native mode: will
> > probe
> > > irqs later
> > > Jul  8 22:35:30 mugleston kernel:     ide0: BM-DMA at 0xffa0-0xffa7,
> > BIOS
> > > settings: hda:DMA, hdb:pio
> > > Jul  8 22:35:30 mugleston kernel: hda: Maxtor 92041U4, ATA DISK drive
> > > Jul  8 22:35:30 mugleston kernel: hde: CD-ROM 40X/AKU, ATAPI CDROM
> drive
> > > Jul  8 22:35:30 mugleston kernel: hdf: PCRW804, ATAPI CDROM drive
> > > Jul  8 22:35:30 mugleston kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > > Jul  8 22:35:30 mugleston kernel: ide2 at 0xdcc8-0xdccf,0xdcd6 on irq
> 11
> > > Jul  8 22:35:30 mugleston kernel: hda: Maxtor 92041U4, 19541MB w/512kB
> > > Cache, CHS=2491/255/63
> > > Jul  8 22:35:30 mugleston kernel: hde: ATAPI 40X CD-ROM drive, 128kB
> > Cache
> > > Jul  8 22:35:30 mugleston kernel: Uniform CDROM driver Revision: 2.54
> > > Jul  8 22:35:30 mugleston kernel: hdf: ATAPI 32X CD-ROM DVD-RAM
> CD-R/RW
> > > drive, 2048kB Cache
> > >
> > >
> > > Jul  8 22:35:30 mugleston kernel: 3c59x.c:v0.99H 11/17/98 Donald
> Becker
> > > http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
> > > Jul  8 22:35:30 mugleston kernel: eth0: 3Com 3c905B Cyclone 100baseTx
> at
> > > 0xdc00,  00:c0:4f:6e:88:39, IRQ 11
> > > Jul  8 22:35:30 mugleston kernel:   8K byte-wide RAM 5:3 Rx:Tx split,
> > > 10baseT interface.
> > >
> > > Jul  8 22:35:29 mugleston network: Bringing up interface eth0
> succeeded
> > >
> > > Jul  8 22:35:42 mugleston local: Cannot open TCPIP port 7101
> > > Jul  8 22:35:42 mugleston local: Better try another port!
> > >
> > >
> > >
> > > _______________________________________________
> > > Redhat-install-list mailing list
> > > Redhat-install-list redhat com
> > > https://listman.redhat.com/mailman/listinfo/redhat-install-list
> > >
> > >
> > >
> > > _______________________________________________
> > > Redhat-install-list mailing list
> > > Redhat-install-list redhat com
> > > https://listman.redhat.com/mailman/listinfo/redhat-install-list
> >
> >
> >
> > _______________________________________________
> > Redhat-install-list mailing list
> > Redhat-install-list redhat com
> > https://listman.redhat.com/mailman/listinfo/redhat-install-list
> 
> 
> 
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list
> 
> 
> 
> _______________________________________________
> Redhat-install-list mailing list
> Redhat-install-list redhat com
> https://listman.redhat.com/mailman/listinfo/redhat-install-list