From: Takashi Iwai <tiwai@suse.de>
To: Tim Connors <tconnors+linuxkernel031203@astro.swin.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Alsa oops, 2.6.0-test8
Date: Wed, 03 Dec 2003 12:12:54 +0100 [thread overview]
Message-ID: <s5hfzg2cfyh.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0312032050320.10546@tellurium.ssi.swin.edu.au>
At Wed, 3 Dec 2003 20:52:55 +1100 (EST),
Tim Connors wrote:
>
> 2 oopses, both alsa, different scenarios, different traces in syslog:
> 2.6.0-test8+kraxel-1 from bytesex.org (possibly not relevant - this seems to be an alsa oops)
> Sound card is ES1371.
> (I have downloaded 2.6.0-test11+kraxel-1, but haven't rebooted yet. I will
> try the same avi files, to see whtehr I can reproduce...)
>
> The first time, I was recoding /dev/dsp, and doing a debian dist-upgrade at the time. I
> didn't notice the oops until I next tried to play something a day later. The recording was
> complete, despite the oops half way through. The mplayer process segfaulted, but I thought at
> the time that might have been due to a corrupted .avi file. But I was just found out that the
> oops is repeatable at least on that file. This time, a hard lock.
it's a known bug. try to build with the frame pointer, or add
CFLAGS_rate.o = -fno-omit-frame-pointer
to sound/core/oss/Makefile.
which gcc version are you using?
--
Takashi Iwai <tiwai@suse.de> ALSA Developer - www.alsa-project.org
next prev parent reply other threads:[~2003-12-03 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 9:52 Tim Connors
2003-12-03 11:12 ` Takashi Iwai [this message]
2003-12-03 11:17 ` Herbert Xu
2003-12-05 17:19 ` Tim Connors
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=s5hfzg2cfyh.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tconnors+linuxkernel031203@astro.swin.edu.au \
/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®