mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: rui.sousa@conexant.com
Cc: linux-kernel@vger.kernel.org,
	Matthew Harrell <mharrell@bittwiddlers.com>
Subject: Re: 2.4.{1,2pre1} oops in via82cxxx_audio (?)
Date: Mon, 05 Feb 2001 15:34:52 -0500	[thread overview]
Message-ID: <3A7F0E6C.D5ECA790@mandrakesoft.com> (raw)
In-Reply-To: <OF9056ECFB.0D139AF2-ONC12569EA.006E4DDA@conexant.com>

rui.sousa@conexant.com wrote:
> On 05/02/01 20:55 Jeff Garzik wrote:
> > The attached patch, sent to Matthew privately, apparently has fixed his
> > problem.  Right now it looks like an out-of-band interrupt...   The
> > interrupt is enabled via request_irq, and its shared so the interrupt
> > handler will be called.  However the channel isn't active so the SG
> > table hasn't been allocated yet.
> 
> But your interrupt status register should indicate that it wasn't the
> sound device that generated the interrupt...

Agreed -- iobase is uninitalized, I believe.

-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-05 20:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 20:27 rui.sousa
2001-02-05 20:34 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-05 15:44 Matthew Harrell
2001-02-05 16:02 ` Matthew Harrell
     [not found] ` <200102051819.KAA31027@penguin.transmeta.com>
2001-02-05 18:27   ` Jeff Garzik
2001-02-05 18:55     ` Matthew Harrell

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=3A7F0E6C.D5ECA790@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrell@bittwiddlers.com \
    --cc=rui.sousa@conexant.com \
    /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

all inboxes | Powered by JetHome®