mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: mharrell@bittwiddlers.com
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.{1,2pre1} oops in via82cxxx_audio (?)
Date: Mon, 05 Feb 2001 13:27:51 -0500	[thread overview]
Message-ID: <3A7EF0A7.343D5B7A@mandrakesoft.com> (raw)
In-Reply-To: <20010205104406.A10978@bittwiddlers.com> <200102051819.KAA31027@penguin.transmeta.com>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

> mharrell@bittwiddlers.com
> >Just realized that some of those symbols were defined in the via82cxxx_audio
> >module and I needed to load it to get them recognized.  As long as I don't
> >play any sounds the module will load fine so here is the new and improved
> >ksymoops output

> >>>EIP; d883a0a0 <[via82cxxx_audio]via_intr_channel+90/120>   <=====
> >Trace; d883a15f <[via82cxxx_audio]via_interrupt+2f/70>
> >Trace; c010a2bf <handle_IRQ_event+2f/60>
> >Trace; c010a43e <do_IRQ+6e/b0>
> >Trace; c0108f80 <ret_from_intr+0/20>
> >Trace; c01f480a <acpi_idle+1ea/2b0>
> >Trace; c01f4620 <acpi_idle+0/2b0>
> >Trace; c0107130 <default_idle+0/30>
> >Trace; c01071c2 <cpu_idle+42/60>
> >Trace; c0105000 <empty_bad_page+0/1000>
> >Trace; c0100191 <L6+0/2>
> >Code;  d883a0a0 <[via82cxxx_audio]via_intr_channel+90/120>
> >00000000 <_EIP>:
> >Code;  d883a0a0 <[via82cxxx_audio]via_intr_channel+90/120>   <=====
> >   0:   89 44 f2 04               mov    %eax,0x4(%edx,%esi,8)   <=====

Ouch.  After applying the attached patch, do any of the assertions
trigger?  (You should get a message 'Assertion failed! ...' right before
the oops)

	Jeff


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

[-- Attachment #2: via.patch --]
[-- Type: text/plain, Size: 870 bytes --]

Index: drivers/sound/via82cxxx_audio.c
===================================================================
RCS file: /cvsroot/gkernel/linux_2_4/drivers/sound/via82cxxx_audio.c,v
retrieving revision 1.1.1.11.2.1
diff -u -r1.1.1.11.2.1 via82cxxx_audio.c
--- drivers/sound/via82cxxx_audio.c	2001/02/04 19:07:03	1.1.1.11.2.1
+++ drivers/sound/via82cxxx_audio.c	2001/02/05 18:24:48
@@ -1649,6 +1649,9 @@
 	u8 status;
 	int n;
 
+	assert (chan != NULL);
+	assert (chan->sgtable != NULL);
+
 	/* check pertinent bits of status register for action bits */
 	status = inb (chan->iobase) & (VIA_SGD_FLAG | VIA_SGD_EOL | VIA_SGD_STOPPED);
 	if (!status)
@@ -1728,6 +1731,8 @@
 {
 	struct via_info *card = dev_id;
 	u32 status32;
+
+	assert (card != NULL);
 
 	/* to minimize interrupt sharing costs, we use the SGD status
 	 * shadow register to check the status of all inputs and

  parent reply	other threads:[~2001-02-05 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2001-02-05 18:55     ` Matthew Harrell
2001-02-05 20:27 rui.sousa
2001-02-05 20:34 ` Jeff Garzik

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=3A7EF0A7.343D5B7A@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrell@bittwiddlers.com \
    --cc=torvalds@transmeta.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®