From: Scott Sams <sbsams@eos.ncsu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: BUG in dmasound.c, allocating buffers
Date: Sun, 31 Jan 1999 15:21:59 -0500 [thread overview]
Message-ID: <36B4BB67.B795BFAC@eos.ncsu.edu> (raw)
Hi,
I am running linux-2.2.0 and I noticed that the kernel crashed 4 times
in one day when I was playing mp3s (mpg123-p, gqmpeg-0.4.5), always when
a new song was going to be played, and usually after 30 minutes of
continuous play. There was absolutely no warning message on the screen
or in the logs, just the entire system froze, with the exception of the
console cursor appearing and blinking in the upper left corner of the
screen.
This got me digging into dmasound.c and looking at the cvs log. The last
version I used, this problem did not occur. This was linux-2.1.125 using
dmasound.c version 1.29. Since then, there have been several updates,
notably 1.33:
>Patch from Jes/Andreas to make it only allocate buffers when opened.
I think that the bug must lie in there, maybe in the sq_allocate_buffers
or sq_release_buffers functions.
I also saw a patch, 1.37, which said it fixed a couple of bugs that let
the user crash the kernel. I applied these by hand to my version of
dmasound.c, just to be safe, but the same crash happened later.
I don't have the knowledge to fix this bug, but I'll bet if someone who
is knowledgable looked over the code I have isolated, they will find out
what is going on.
At the very least, someone can insert some debugging output that may
help discover the problem. I will be glad to test anything.
Thanks,
Scott Sams
--
____ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Scott Sams
(____ _ _-|-|- sbsams@eos.ncsu.edu
_____)(__(_)| | http://www.catt.ncsu.edu/~sbsams
~~~~~~~~~~~~~~~~
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-01-31 20:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=36B4BB67.B795BFAC@eos.ncsu.edu \
--to=sbsams@eos.ncsu.edu \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.