From: Josh Green <jgreen@users.sourceforge.net>
To: alsa-devel@lists.sourceforge.net
Subject: Oops with snd-ymfpci and ALSA 0.9.3a
Date: 18 May 2003 19:54:21 -0700 [thread overview]
Message-ID: <1053312860.6552.8.camel@SillyPuddy> (raw)
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
I upgraded to ALSA 0.9.3a from 0.9.2 and am getting a kernel oops upon
insertion of the snd-ymfpci module. I've attached the output from
ksymoops. This is with stock kernel 2.4.20 on a Panasonic laptop and
Mandrake 9.1. I downgraded back to 0.9.2 which works fine. I can provide
more info if needed, cheers.
Josh Green
[-- Attachment #2: alsa_oops.txt --]
[-- Type: text/plain, Size: 4383 bytes --]
ksymoops 2.4.8 on i686 2.4.20. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.20/ (default)
-m /boot/System.map-2.4.20 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
May 17 13:34:52 SillyPuddy kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000029e
May 17 13:34:52 SillyPuddy kernel: cecc7164
May 17 13:34:52 SillyPuddy kernel: *pde = 00000000
May 17 13:34:52 SillyPuddy kernel: Oops: 0002
May 17 13:34:52 SillyPuddy kernel: CPU: 0
May 17 13:34:52 SillyPuddy kernel: EIP: 0010:[usbcore:usb_devfs_handle_Re9c5f87f+1653716/12475604] Not tainted
May 17 13:34:52 SillyPuddy kernel: EIP: 0010:[<cecc7164>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
May 17 13:34:52 SillyPuddy kernel: EFLAGS: 00010296
May 17 13:34:52 SillyPuddy kernel: eax: c9a67a20 ebx: 00000286 ecx: 00000388 edx: c029d870
May 17 13:34:52 SillyPuddy kernel: esi: 00000800 edi: 00000000 ebp: cb4bee00 esp: c97c1e94
May 17 13:34:52 SillyPuddy kernel: ds: 0018 es: 0018 ss: 0018
May 17 13:34:52 SillyPuddy kernel: Process insmod (pid: 2075, stackpage=c97c1000)
May 17 13:34:52 SillyPuddy kernel: Stack: c029d870 00000388 00000004 ceccab7f 000001d2 c01292b9 00104025 00000001
May 17 13:34:52 SillyPuddy kernel: ceccabf4 09720067 00000286 00001000 c11a0388 ceccb250 ceccb2c0 cdf36c00
May 17 13:34:52 SillyPuddy kernel: 00000000 c01f6165 cdf36c00 ceccb250 cdf36c00 ceccb2c0 00000000 cecc7000
May 17 13:34:52 SillyPuddy kernel: Call Trace: [usbcore:usb_devfs_handle_Re9c5f87f+1668591/12460729] [pm_register+73/144] [usbcore:usb_devfs_handle_Re9c5f87f+1668708/12460612] [usbcore:usb_devfs_handle_Re9c5f87f+1670336/12458984] [usbcore:usb_devfs_handle_Re9c5f87f+1670448/12458872]
May 17 13:34:52 SillyPuddy kernel: Call Trace: [<ceccab7f>] [<c01292b9>] [<ceccabf4>] [<ceccb250>] [<ceccb2c0>]
May 17 13:34:52 SillyPuddy kernel: [<c01f6165>] [<ceccb250>] [<ceccb2c0>] [<c01f620c>] [<ceccb2c0>] [<cecc7839>]
May 17 13:34:52 SillyPuddy kernel: [<ceccb2c0>] [<c011ac93>] [<cecc7060>] [<ceccb0dc>] [<cecc7060>] [<c010741f>]
May 17 13:34:52 SillyPuddy kernel: Code: 89 43 18 85 c0 0f 85 21 04 00 00 8b 15 40 1a cd ce 8b 04 95
>>EIP; cecc7164 <[snd-ymfpci]snd_card_ymfpci_probe+104/750> <=====
>>eax; c9a67a20 <_end+973d79c/e7f6ddc>
>>edx; c029d870 <init_signals+190/520>
>>ebp; cb4bee00 <_end+b194b7c/e7f6ddc>
>>esp; c97c1e94 <_end+9497c10/e7f6ddc>
Trace; ceccab7f <[snd-ymfpci]__module_parm_index+3/10>
Trace; c01292b9 <pm_register+49/90>
Trace; ceccabf4 <[snd-ymfpci]__module_generic_string_info_parm_id+8/3b>
Trace; ceccb250 <[snd-ymfpci]snd_ymfpci_ids+70/c4>
Trace; ceccb2c0 <[snd-ymfpci]driver+0/40>
Trace; c01f6165 <cdrom_sysctl_info+65/6f0>
Trace; ceccb250 <[snd-ymfpci]snd_ymfpci_ids+70/c4>
Trace; ceccb2c0 <[snd-ymfpci]driver+0/40>
Trace; c01f620c <cdrom_sysctl_info+10c/6f0>
Trace; ceccb2c0 <[snd-ymfpci]driver+0/40>
Trace; cecc7839 <[snd-ymfpci]alsa_card_ymfpci_init+19/60>
Trace; ceccb2c0 <[snd-ymfpci]driver+0/40>
Trace; c011ac93 <get_exec_domain_list+53/80>
Trace; cecc7060 <[snd-ymfpci]snd_card_ymfpci_probe+0/750>
Trace; ceccb0dc <[snd-ymfpci]__module_using_checksums+362/3c6>
Trace; cecc7060 <[snd-ymfpci]snd_card_ymfpci_probe+0/750>
Trace; c010741f <system_call+33/38>
Code; cecc7164 <[snd-ymfpci]snd_card_ymfpci_probe+104/750>
00000000 <_EIP>:
Code; cecc7164 <[snd-ymfpci]snd_card_ymfpci_probe+104/750> <=====
0: 89 43 18 mov %eax,0x18(%ebx) <=====
Code; cecc7167 <[snd-ymfpci]snd_card_ymfpci_probe+107/750>
3: 85 c0 test %eax,%eax
Code; cecc7169 <[snd-ymfpci]snd_card_ymfpci_probe+109/750>
5: 0f 85 21 04 00 00 jne 42c <_EIP+0x42c>
Code; cecc716f <[snd-ymfpci]snd_card_ymfpci_probe+10f/750>
b: 8b 15 40 1a cd ce mov 0xcecd1a40,%edx
Code; cecc7175 <[snd-ymfpci]snd_card_ymfpci_probe+115/750>
11: 8b 04 95 00 00 00 00 mov 0x0(,%edx,4),%eax
next reply other threads:[~2003-05-19 2:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 2:54 Josh Green [this message]
2003-05-19 6:26 ` Oops with snd-ymfpci and ALSA 0.9.3a Clemens Ladisch
2003-06-11 4:58 ` tom burkart
2003-06-11 6:56 ` Clemens Ladisch
2003-06-11 6:58 ` tom burkart
2003-06-11 9:40 ` Clemens Ladisch
2003-06-11 13:09 ` tom burkart
2003-06-12 7:49 ` Clemens Ladisch
2003-06-12 8:07 ` tom burkart
2003-06-12 10:54 ` Jaroslav Kysela
2003-06-12 12:44 ` tom burkart
2003-06-12 13:15 ` Jaroslav Kysela
2003-06-13 2:45 ` tom burkart
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=1053312860.6552.8.camel@SillyPuddy \
--to=jgreen@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
/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.