kernel: eth1: Null event in orinoco_interrupt!

Tue Jul 16 20:41:18 EST 2002

All,
Just some follow up as I have managed to 'work around' the problem. Im using
a PCMCIA<->PCI Bridge card in a linux server. The Linux installation is
RedHat 7.3. I could not get the Lucent card to connect to the network and
any attempt to do anything with the card resulted in Interrupt errors (i.e.
pinging). However the card looked like it was working normally and even
logged properly into syslog when it came up.

The final solution was to use a different PCMCIA-PCI bridge. Basically the
one I had was using a TI chip, whereas the one that now works uses a Ricoh
chip. Other postings on other sites alerted me to problems with the TI chip.

Unresolved: These are the things I could not get to work with RH7.3
1. After building from source I had to use mkinitrd as my server is SCSI
based. I could not get this working at all and the system always tried to
boot from IDE. I gave up.
2. I was forced to rebuild RH7.3 because I wanted to use the pcmcia_cs
rather than the kernel based package. This meant I had to build a kernel
without it.
3. When trying to play around with the PCMCIA-PCI card, I could not pass any
of the standard parameters to it. i.e. passing irq_mode resulted in errors
such as parm_irq_mode not valid/recognised or something like that. I assume
this is a redhat quirk that I could not find a solution to and gave up
again.

Thanks for all the help on this message board

Regards
Paul

-----Original Message-----
From: ''David Gibson ' ' [mailto:david at gibson.dropbear.id.au] 
Sent: 30 June 2002 16:15
To: Paul Gresham
Subject: Re: kernel: eth1: Null event in orinoco_interrupt!

On Sat, Jun 29, 2002 at 01:42:08PM +0800, Paul Gresham wrote:
> Hi David,
> Yes, I have PCI card which I use in a server, then plug in the PCMCIA 
> network card. I'll do some investigation into this unless you suggest 
> a better plan! The driver says its a yenta_socket and the RH install 
> configured with my pcmcia settings as PCIC=yenta_socket I tried 
> setting PCIC=i82365 but this made no difference :(

Try fiddling with the irq_mode parameter to the PCMCIA modules (I forget
exactly which module takes the parameter).

> From: 'David Gibson '
> To: Paul Gresham
> Cc: 'Jim Carter '; ''wireless at lists.samba.org' '
> Sent: 6/29/02 12:04 PM
> Subject: Re: kernel: eth1: Null event in orinoco_interrupt!
> 
> On Sat, Jun 29, 2002 at 09:20:07AM +0800, Paul Gresham wrote:
> > Thanks guys using 11b is simple to do and thats cured the original
> error,
> > however the problems continue. I cannot access the network which 
> > I've
> set up
> > as 192.168.1.0. Whenever I try something for instance each ping of 
> > the router 192.168.1.1 will chuck the following error message into 
> > the
> syslog
> > 
> > Jun 28 17:07:52 localhost kernel: NETDEV WATCHDOG: eth1: transmit
> timed out
> > Jun 28 17:07:52 localhost kernel: eth1: Tx timeout! Resetting card. 
> > ALLOCFID=01f6, TXCOMPLFID=0192, EVSTAT=800a
> > 
> > I'd seen this error message before I did any upgrades (I've just
> upgrade to
> > RH7.3 and installed 11b of orinoco) and had exactly the same 
> > symptons.
> Card
> > seems to connect to the wireless network ok (a stable green light) 
> > but
> I get
> > the above error.
> 
> Blah.  Looks like you aren't getting any interrupts.  Is this card in 
> a PCMCIA <-> ISA/PCI bridge?
> 
> > From: David Gibson
> > To: Jim Carter
> > Cc: Paul Gresham; 'wireless at lists.samba.org'
> > Sent: 6/28/02 8:48 AM
> > Subject: Re: kernel: eth1: Null event in orinoco_interrupt!
> > 
> > On Thu, Jun 27, 2002 at 10:08:58AM -0700, Jim Carter wrote:
> > > On Thu, 27 Jun 2002, Paul Gresham wrote:
> > > > Hi, please can someone point me in the right direction. I'm 
> > > > using
> an
> > > > Orinoco Silver pcmcia card connecting to an RG1000. My linux
> server
> > is my
> > > > gateway to the web and has a pcmcia adaptor in it, which by
> default
> > loads up
> > > > as a  yenta socket
> > > > Jun 27 06:52:35 localhost kernel: eth1: Null event in
> > orinoco_interrupt!
> > > 
> > > This is excessive paranoia, attributed to sharing an IRQ between 
> > > the wireless card and something else, so when the something else
> > interrupts,
> > > the wireless card has nothing to say to the driver.  This check 
> > > was
> > removed
> > > several driver versions ago.
> > 
> > Indeed.  I put it in due to a brain fart when trying to track down 
> > another possible problem.
> > 
> > > The latest driver version is 0.12 and it can be obtained from
> > > 
> > > http://ozlabs.org/people/dgibson/dldwd/
> > 
> > Yes, but I don't suggest you use it just for now.  Go with 0.11b 
> > until I release 0.12a which should fix numerous problems with 0.12.
> > 
> 

-- 
David Gibson			| For every complex problem there is a
david at gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.  -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

-------------------------------------------------------------
Additional information is available upon request
Copyright (c) 2002 CLSA Emerging Markets. The information and statistical data herein have been obtained from sources we believe to be reliable but in no way are warranted by us as to accuracy or completeness. We do not undertake to advise you as to any change of our views. This is not a solicitation or any offer to buy or sell. CLSA Emerging Markets has produced this information for private circulation only. All information and advice is given in good faith but without any warranty. CLSA Emerging Markets, its affiliates or companies or individuals connected with CLSA Emerging Markets may have used the information set forth herein before publication and may have positions in, may from time to time purchase or sell or may be materially interested in any of the securities mentioned or related securities. This information is subject to the terms and conditions of use set forth on the www.clsa.com website. MITA (P) 405/07/2001. V.020402. 

This email is only for the use of the addressee and may contain information which is confidential, privileged or subject to copyright. If you receive this and are not the addressee, please contact the sender or postmaster at clsa.com immediately. Thank you. 

CLSA EMERGING MARKETS http://www.clsa.com 

-------------- next part --------------
HTML attachment scrubbed and removed