kernel: eth1: Null event in orinoco_interrupt!

Paul Gresham paul.gresham at clsa.com
Sat Jun 29 11:20:07 EST 2002


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.

Again any pointers on where to go next are greatly appreciated

Paul Gresham

p.s. sorry if this still comes in HTML format I'm trying to stop it but
using outlook web access is not clear what the behaviour is.


-----Original Message-----
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


More information about the wireless mailing list