From: "Roeland Th. Jansen" <roel@grobbebol.xs4all.nl>
To: john slee <indigoid@higherplane.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: hard lockup (no oops) on vanilla 2.4.2-pre3 with /dev/dsp
Date: Sun, 11 Feb 2001 11:22:18 +0000 [thread overview]
Message-ID: <20010211112218.A918@grobbebol.xs4all.nl> (raw)
In-Reply-To: <20010211053145.A748@higherplane.net> <E14RfmM-0002Ao-00@the-village.bc.nu> <20010211222032.A975@higherplane.net>
In-Reply-To: <20010211222032.A975@higherplane.net>; from indigoid@higherplane.net on Sun, Feb 11, 2001 at 10:20:33PM +1100
On Sun, Feb 11, 2001 at 10:20:33PM +1100, john slee wrote:
> i'm fairly sure its not ram at fault, since nothing else is acting
> strangely, and it only crops up when i use /dev/dsp.
>
> anything else i can try to narrow it down? this is just a home
> workstation, so i can try practically anything if necessary.
I missed this thread a bit but I also am experiencing problems when
using sound (playing mp3's) -- hard crashes. I am not sure wether it's X
related (xmms/X v4.0x), sound related (opensound drivers), hardware
related (dual BP6, non OC with apic patches).
could you mail privately what the issues are ? maybe I have the same
problems.
--
Grobbebol's Home | Don't give in to spammers. -o)
http://www.xs4all.nl/~bengel | Use your real e-mail address /\
Linux 2.2.16 SMP 2x466MHz / 256 MB | on Usenet. _\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-11 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-10 18:31 john slee
2001-02-10 19:33 ` Alan Cox
2001-02-11 2:19 ` john slee
2001-02-11 13:57 ` john slee
2001-02-11 11:20 ` john slee
2001-02-11 11:22 ` Roeland Th. Jansen [this message]
2001-02-11 17:12 ` Alan Cox
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=20010211112218.A918@grobbebol.xs4all.nl \
--to=roel@grobbebol.xs4all.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=indigoid@higherplane.net \
--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®