From: Doug Ledford <dledford@redhat.com>
To: Nick Papadonis <nick@coelacanth.com>
Cc: Nathan Bryant <nbryant@allegientsystems.com>,
Martin Dalecki <dalecki@evision-ventures.com>,
Thomas Gschwind <tom@infosys.tuwien.ac.at>,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: i810_audio]
Date: Thu, 03 Jan 2002 23:59:09 -0500 [thread overview]
Message-ID: <3C35369D.5040600@redhat.com> (raw)
In-Reply-To: <3C3382CA.3000503@allegientsystems.com> <3C345493.5040800@evision-ventures.com> <20020103154718.C32419@infosys.tuwien.ac.at> <3C347A12.3070404@evision-ventures.com> <3C34B35A.7000309@allegientsystems.com> <m3ell76p4h.fsf@localhost.localdomain>
Nick Papadonis wrote:
> I tried the 0.13 driver yesterday. It appears to work fine, but when
> I insert my Orinoco WaveLan card they system locks up. I reverted to
> the i810 audio driver included in kernel v2.4.16 and this problem
> isn't encountered.
>
> Is there a conflict with the orinoco and orinoco_cs drivers from
> kernel v2.4.16?
Possibly. If anything it's likely that either the orinoco or the i810
driver is not handling spurious interrupts properly. Now, since I've been
using my i810 device in a machine that doesn't share it's interrupt I can't
*personally* vouch that it handles things properly, but from looking at the
interrupt handler code, it should. The other possibility is that the
orinoco might enable interrupts on the pcmcia slot before it actually
registers its own interrupt handler. If it does, and the card already has
the interrupt line lit up, then it can generate an interrupt storm that
looks like a machine lockup. A way to test that is to unload the i810 sound
driver and anything else that might use the interrupt the orinoco uses, then
load the orinoco, wait until it's fully up and running, then load the i810
driver and see if things work that way. If it does, then it's almost
certainly an init sequence issue in the orinoco driver.
--
Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
next prev parent reply other threads:[~2002-01-04 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 21:59 [Fwd: i810_audio] Nathan Bryant
2002-01-03 12:54 ` Martin Dalecki
2002-01-03 14:47 ` Thomas Gschwind
2002-01-03 15:34 ` Martin Dalecki
2002-01-03 19:39 ` Nathan Bryant
2002-01-03 22:33 ` Nick Papadonis
2002-01-04 0:37 ` Nathan Bryant
2002-01-04 4:59 ` Doug Ledford [this message]
2002-01-04 5:09 ` Nathan Bryant
2002-01-04 5:31 ` Ben Clifford
2002-01-04 15:39 ` Doug Ledford
2002-01-04 19:37 ` Ben Clifford
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=3C35369D.5040600@redhat.com \
--to=dledford@redhat.com \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbryant@allegientsystems.com \
--cc=nick@coelacanth.com \
--cc=tom@infosys.tuwien.ac.at \
/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