From: Stuart Young <sgy@amc.com.au>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: SiS/Trident 4DWave sound driver oops
Date: Thu, 25 Oct 2001 09:55:09 +1000 [thread overview]
Message-ID: <5.1.0.14.0.20011025095018.02485d50@mail.amc.localnet> (raw)
In-Reply-To: <E15w4Ga-0006Q0-00@the-village.bc.nu>
In-Reply-To: <5.1.0.14.0.20011023154226.00a20ba0@mail.amc.localnet>
At 05:19 PM 23/10/01 +0100, Alan Cox wrote:
> > 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,
> > but have tried 2.2.19pre17 (will explain other SiS Chipset funny business
> > in another message). All kernels were compiled while the machine was
> > running 2.2.19pre17.
>
>Does this problem go away if you build the driver modular. Im wondering
>if it matches another mysterious and similar report
I've built the trident driver as a module, and tried the sound support as
both a module and in-line, with the same results.
Haven't tried the trident driver and sound support in-line together. I'll
give this a try and see if there is any difference, or wether my machine
just oops's at boot.
Stuart Young - sgy@amc.com.au
(aka Cefiar) - cefiar1@optushome.com.au
[All opinions expressed in the above message are my]
[own and not necessarily the views of my employer..]
next prev parent reply other threads:[~2001-10-24 23:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 6:15 Stuart Young
2001-10-23 16:19 ` Alan Cox
2001-10-24 23:55 ` Stuart Young [this message]
2001-10-25 1:07 Michael F. Robbins
2001-10-25 5:55 ` Stuart Young
2001-10-25 7:02 ` Stuart Young
2001-10-25 13:24 Michael F. Robbins
2001-10-26 1:37 ` Tachino Nobuhiro
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-26 23:43 ` Michael F. Robbins
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=5.1.0.14.0.20011025095018.02485d50@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--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®