From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: ALSA bugs with 2.6.12-rc1
Date: Mon, 04 Apr 2005 10:46:48 -0400 [thread overview]
Message-ID: <42515358.7020101@blue-labs.org> (raw)
It seems that 2.6.12-rc1 introduced an ALSA bug generating an oops for a
null pointer.
codec_semaphore: semaphore is not ready [0x1][0x300300]
codec_read 0: semaphore is not ready for register 0x2c
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c01d7746
*pde = 00000000
Oops: 0002 [#1]
PREEMPT
Modules linked in: orinoco_cs orinoco hermes pcmcia yenta_socket
rsrc_nonstatic pcmcia_core vfat fat nls_base i2c_sensor i2c_core eth1394
ohci1394 ieee1394 i8k
CPU: 0
EIP: 0060:[<c01d7746>] Not tainted VLI
EFLAGS: 00010202 (2.6.12-rc1)
EIP is at memcpy+0x1e/0x39
eax: 00000010 ebx: e7608180 ecx: 00000004 edx: 00000000
esi: e13d1ee4 edi: 00000000 ebp: bf924390 esp: e13d1eb4
ds: 007b es: 007b ss: 0068
Process artsd (pid: 11880, threadinfo=e13d1000 task=e1436590)
Stack: ffffffea ffffffea e13d1ef4 c02b8793 00000000 e13d1ee4 00000010
e7608180
c02b954d e7608180 e13d1ee4 00000050 00000006 00000000 00000000
00000000
00000005 00000001 00000000 00000000 00008002 00000000 00000000
00000000
Call Trace:
[<c02b8793>] snd_timer_user_append_to_tqueue+0x40/0x49
[<c02b954d>] snd_timer_user_params+0x236/0x245
[<c016f152>] do_ioctl+0x9a/0xa9
[<c016f2ef>] vfs_ioctl+0x65/0x1e1
[<c015bc34>] get_unused_fd+0x2c/0xd2
[<c016f4b0>] sys_ioctl+0x45/0x6d
[<c0102f87>] sysenter_past_esp+0x54/0x75
Code: fd 31 c0 c3 31 d2 b8 f2 ff ff ff c3 90 83 ec 0c 8b 44 24 18 8b 54
24 10 89 74 24 04 89 c1 89 7c 24 08 8b 74 24 14 c1 e9 02 89 d7 <f3> a5
a8 02 74 02 66 a5 a8 01 74 01 a4 89 d0 8b 74 24 04 8b 7c
codec_semaphore: semaphore is not ready [0x1][0x300300]
codec_read 1: semaphore is not ready for register 0x54
codec_semaphore: semaphore is not ready [0x1][0x300300]
codec_write 1: semaphore is not ready for register 0x54
This happens on multiple machines, 32b and 64bit. I'll be happy to
provide further information if needed.
-david
next reply other threads:[~2005-04-04 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 14:46 David Ford [this message]
2005-04-04 17:08 ` ALSA bugs with 2.6.12-rc1 Daniel Drake
2005-04-04 17:26 ` Takashi Iwai
2005-04-04 17:34 ` Adrian Bunk
2005-04-04 18:39 ` Jaroslav Kysela
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=42515358.7020101@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--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