From: Jiri Masik <masik@pc203b.fzu.cz>
To: linuxppc-dev@lists.linuxppc.org
Subject: dmasound - kernel panic
Date: 10 Aug 2000 00:02:03 +0200 [thread overview]
Message-ID: <4vu2cu9jqc.fsf@darbujan.fzu.cz> (raw)
Hi,
I'm testing the new dmasound_awacs patches snd-2.2.17p15-b1-s2.p.bz2
with the rsync pmac-benh kernel as of today.
Linux version 2.2.17pre15-ben1 (root@pbuk) (gcc version 2.95.2
20000220 (Debian GNU/Linux)) #10 Wed Aug 9 11:36:18 CEST 2000
I have a Pismo powerbook and the chip is reported as follows
DMA sound driver core [Ed 18] [4 buffers of 32k for output]
............................. [4 buffers of 32k for input]
DMA sound driver core called by PowerMac (AWACS rev 3 [screamer])
PowerMac (AWACS rev 3 [screamer]) DMA sound driver:
sound.format = 0x20 (signed 16 bit big)(Phys: signed 16 bit big)
sound.speed = 44100Hz (phys. 44100Hz)
sound.stereo = 0x1 (stereo)
write_sq.block_size = 256 write_sq.max_count = 4 write_sq.max_active = 4
write_sq.count = 4 write_sq.rear_size = 256
write_sq.active = 2 write_sq.syncing = 0
read_sq.block_size = 0 read_sq.max_count = 0 read_sq.max_active = 0
read_sq.count = 0 read_sq.rear_size = 0
read_sq.active = 0 read_sq.syncing = 0
The audio playback is working fine for mpg123, both headphones and
internal speakers. I'd like to record sounds from the built-in mic and
I've found that I can crash the kernel by cat /dev/audio. This is the
message I'm getting immediately
kernel access of bad area pc 0 lr c8822220c address 0 tsk 398
I've put the ksyms to http://darbujan.fzu.cz/~masik/ksymoops/
I'm not familiar with the kernel debugging please let me know if the
information is incomplete.
thanks,
Jiri
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-09 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-09 22:02 Jiri Masik [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-11 10:29 dmasound - kernel panic Iain Sandoe
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=4vu2cu9jqc.fsf@darbujan.fzu.cz \
--to=masik@pc203b.fzu.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).