From: rui.sousa@conexant.com
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org,
Matthew Harrell <mharrell@bittwiddlers.com>
Subject: Re: 2.4.{1,2pre1} oops in via82cxxx_audio (?)
Date: Mon, 5 Feb 2001 21:27:20 +0100 [thread overview]
Message-ID: <OF9056ECFB.0D139AF2-ONC12569EA.006E4DDA@conexant.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On 05/02/01 20:55 Jeff Garzik wrote:
> rui.sousa@conexant.com wrote:
> >
> > On Mon, 5 Feb 2001, Matthew Harrell wrote:
> >
> > > : Ouch. After applying the attached patch, do any of the assertions
> > > : trigger? (You should get a message 'Assertion failed! ...' right
before
> > > : the oops)
> > >
> > > : + assert (chan->sgtable != NULL);
> > >
> > > Yep, I get this one "chan->sgtable != NULL". I have no idea what
this means
> > > but I got it one out of the two times I tried.
> > >
> >
> > Is there any other device on the same irq?
>
> Yes, it looks like:
>
> Matthew Harrell wrote:
> > PCI: Found IRQ 10 for device 00:14.5
> > PCI: The same IRQ used for device 00:04.0
>
> 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...
Matthew, can you try the attached patched and report the output?
You should apply it on a clean 2.4.1 (without the patches Jeff sent you).
Try only sound playback.
Rui Sousa
(See attached file: patch)
[-- Attachment #2: patch --]
[-- Type: application/octet-stream, Size: 706 bytes --]
--- via82cxxx_audio.c.orig Mon Feb 5 21:17:19 2001
+++ via82cxxx_audio.c Mon Feb 5 21:23:13 2001
@@ -1598,6 +1598,7 @@
{
struct via_info *card = dev_id;
u32 status32;
+ u8 status;
/* to minimize interrupt sharing costs, we use the SGD status
* shadow register to check the status of all inputs and
@@ -1609,6 +1610,12 @@
return;
DPRINTK ("intr, status32 == 0x%08X\n", status32);
+
+ if (card->ch_out.sgtable == NULL) {
+ status = inb (card->baseaddr + VIA_BASE0_PCM_OUT_CHAN) & (VIA_SGD_FLAG | VIA_SGD_EOL | VIA_SGD_STOPPED);
+ printk("%x %x\n", status32, status);
+ return;
+ }
/* synchronize interrupt handling under SMP. this spinlock
* goes away completely on UP
next reply other threads:[~2001-02-05 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 20:27 rui.sousa [this message]
2001-02-05 20:34 ` Jeff Garzik
-- 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=OF9056ECFB.0D139AF2-ONC12569EA.006E4DDA@conexant.com \
--to=rui.sousa@conexant.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrell@bittwiddlers.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®