From: Samium Gromoff <_deepfire@mail.ru>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Recent kernels sound crash solution found?
Date: Fri, 7 Sep 2001 19:26:08 +0000 (UTC) [thread overview]
Message-ID: <200109071926.f87JQ9l06082@vegae.deep.net> (raw)
Hello folks, seems that i found the potential bug which
led to the infinite trace i`ve described before.
Facts:
1. My host have 24M of RAM and on kernels 2.4.x;x>7 it started
to have n-order alloc failures.
2. In very rare circumsistances under 2.4.8-ac12 i have
1-order alloc failures.
3. sound_alloc_dmap::dmabuf.c comments states it will loop
until the buffer is alloced
4. sound_alloc_dmap::dmabuf.c comments states it wont accept buffer
lesser than 8k in size.
Logic:
3 + 4 => it loops forever when 1-order alloc fails
1 + 2 + 3 + 4 => my host crashes
* comment to point 2: very rare circumcistances includes
that some time should pass to fragment memory
cheers, Sam
next reply other threads:[~2001-09-07 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 19:26 Samium Gromoff [this message]
2001-09-07 15:16 ` Recent kernels sound crash solution found? Alan Cox
2001-09-07 20:09 ` Samium Gromoff
2001-09-07 15:54 ` Alan Cox
2001-09-07 20:16 ` Samium Gromoff
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=200109071926.f87JQ9l06082@vegae.deep.net \
--to=_deepfire@mail.ru \
--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 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.