From: Tachino Nobuhiro <tachino@open.nm.fujitsu.co.jp>
To: "Michael F. Robbins" <compumike@compumike.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SiS/Trident 4DWave sound driver oops
Date: Fri, 26 Oct 2001 10:37:53 +0900 [thread overview]
Message-ID: <7ktjw58u.wl@nisaaru.dvs.cs.fujitsu.co.jp> (raw)
In-Reply-To: <1004016263.1384.15.camel@tbird.robbins>
In-Reply-To: <1004016263.1384.15.camel@tbird.robbins>
Hello,
At 25 Oct 2001 09:24:21 -0400,
Michael F. Robbins <compumike@compumike.com> wrote:
>
> I just grabbed 2.4.12-ac6 and the OOPS continues. This is with
> soundcore, ac97_codec, and trident all built as modules.
>
> Again, like my previous report (which was on Linus' 2.4.12), I can
> 'modprobe soundcore' and 'modprobe ac97_codec' with no problems. Once I
> do the 'modprobe trident', I get the oops. After the oops, the system
> is still responsive, and just like Stuart Young reported, the trident
> module is stuck in "initalizing".
>
> See below for the details including the oops report itself.
>
> Mike Robbins
> compumike@compumike.com
> (Please also cc your reply to me.)
Following patch may fix your oops. Please try.
diff -u -r linux-2.4.12-ac5.org/drivers/sound/ac97_codec.c linux-2.4.12-ac5/drivers/sound/ac97_codec.c
--- linux-2.4.12-ac5.org/drivers/sound/ac97_codec.c Mon Oct 22 09:34:21 2001
+++ linux-2.4.12-ac5/drivers/sound/ac97_codec.c Fri Oct 26 10:26:41 2001
@@ -143,7 +143,6 @@
{0x83847656, "SigmaTel STAC9756/57", &sigmatel_9744_ops},
{0x83847684, "SigmaTel STAC9783/84?", &null_ops},
{0x57454301, "Winbond 83971D", &null_ops},
- {0,}
};
static const char *ac97_stereo_enhancements[] =
next prev parent reply other threads:[~2001-10-26 1:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 13:24 Michael F. Robbins
2001-10-26 1:37 ` Tachino Nobuhiro [this message]
2001-10-26 1:56 ` Tachino Nobuhiro
2001-10-26 2:36 ` Tachino Nobuhiro
2001-10-26 1:45 ` Robert Love
2001-10-26 2:02 ` Robert Love
2001-10-26 2:42 ` Robert Love
2001-10-26 3:13 ` David Weinehall
2001-10-26 3:28 ` Robert Love
2001-10-26 3:24 ` Stuart Young
2001-10-26 14:36 ` Alan Cox
2001-10-26 14:47 ` Trever L. Adams
2001-10-28 23:06 ` SiS/Trident 4DWave sound driver Stuart Young
2001-10-29 1:19 ` SiS/Trident 4DWave sound driver (Update) Stuart Young
2001-10-29 4:04 ` SiS drivers (more) Stuart Young
2001-10-26 23:43 ` SiS/Trident 4DWave sound driver oops Michael F. Robbins
-- strict thread matches above, loose matches on Subject: below --
2001-10-25 1:07 Michael F. Robbins
2001-10-25 5:55 ` Stuart Young
2001-10-25 7:02 ` Stuart Young
2001-10-23 6:15 Stuart Young
2001-10-23 16:19 ` Alan Cox
2001-10-24 23:55 ` Stuart Young
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=7ktjw58u.wl@nisaaru.dvs.cs.fujitsu.co.jp \
--to=tachino@open.nm.fujitsu.co.jp \
--cc=compumike@compumike.com \
--cc=linux-kernel@vger.kernel.org \
/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®