From: "Michael F. Robbins" <compumike@compumike.com>
To: linux-kernel@vger.kernel.org
Subject: Re: SiS/Trident 4DWave sound driver oops
Date: 24 Oct 2001 21:07:26 -0400 [thread overview]
Message-ID: <1003972047.2393.9.camel@tbird.robbins> (raw)
I have a very similar OOPS that I reported to linux-kernel just last
week: see full details at
http://uwsg.iu.edu/hypermail/linux/kernel/0110.1/1690.html
> This kernel oops is totally reproducible (on every occasion) in 2.4.9,
> 2.4.10, and 2.4.12. I have not tried earlier kernels in the 2.4
> series
I also have a totally reproduceable OOPS on 2.4.9 through 2.4.12.
Kernel 2.4.7 works just fine. If the soundcard is compiled in to the
kernel, it dies while booting. If it is compiled as a module, it dies
when attempting to load the module (typically when artsd starts).
> The machine in question is a Clevo lp200t SiS630S "all-in-one"
> machine.
My machine is an ECS K7AMA: ALi 1645 northbridge, ALi Magic 1535D+
southbridge. Sound is onboard the southbridge. I ran ksymoops on my
OOPS report, so you can see the trace at the message archive.
Mike Robbins
compumike@compumike.com
(Please also cc your reply to me.)
next reply other threads:[~2001-10-25 1:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 1:07 Michael F. Robbins [this message]
2001-10-25 5:55 ` SiS/Trident 4DWave sound driver oops Stuart Young
2001-10-25 7:02 ` Stuart Young
-- strict thread matches above, loose matches on Subject: below --
2001-10-25 13:24 Michael F. Robbins
2001-10-26 1:37 ` Tachino Nobuhiro
2001-10-26 1:45 ` Robert Love
2001-10-26 1:56 ` Tachino Nobuhiro
2001-10-26 2:02 ` Robert Love
2001-10-26 2:36 ` Tachino Nobuhiro
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-26 23:43 ` Michael F. Robbins
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=1003972047.2393.9.camel@tbird.robbins \
--to=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