From: Jan Rychter <jan@rychter.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.22-pre5: rmmod i810_audio caused an oops
Date: Sun, 13 Jul 2003 14:34:50 -0700 [thread overview]
Message-ID: <m2smpayuth.fsf@tnuctip.rychter.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]
Typing 'rmmod i810_audio' proced this oops. Perhaps that's useful info.
I can't reproduce this at will -- this happened after unloading alsa,
loading i810_audio, then trying to unload it.
Unable to handle kernel NULL pointer dereference at virtual address 00000004
d09dccdf
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<d09dccdf>] Tainted: P Z
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: cfb295a0 ecx: d09df9b8 edx: 00000000
esi: cf6f85f8 edi: cf6f8400 ebp: 00000003 esp: c8e0ff5c
ds: 0018 es: 0018 ss: 0018
Process rmmod (pid: 10044, stackpage=c8e0f000)
Stack: 00000000 d09e54b9 cfb295a0 00000000 cfe2dc00 d09e7240 d09e1000 bfffeb08
c01f7996 cfe2dc00 d09e1000 fffffff0 d09e58aa d09e7240 c01181f3 d09e1000
fffffff0 cb610000 bfffeb08 c0117597 d09e1000 00000000 c8e0e000 00000001
Call Trace: [<d09e54b9>] [<d09e7240>] [<c01f7996>] [<d09e58aa>] [<d09e7240>]
[<c01181f3>] [<c0117597>] [<c01086df>]
Code: 89 50 04 89 02 c7 03 00 00 00 00 c7 43 04 00 00 00 00 ff 05
>>EIP; d09dccdf <[ac97_codec]ac97_release_codec+1b/58> <=====
>>ebx; cfb295a0 <_end+f820788/10501248>
>>ecx; d09df9b8 <[ac97_codec]codec_sem+0/13>
>>esi; cf6f85f8 <_end+f3ef7e0/10501248>
>>edi; cf6f8400 <_end+f3ef5e8/10501248>
>>esp; c8e0ff5c <_end+8b07144/10501248>
Trace; d09e54b9 <[ac97_codec].data.end+5aee/9695>
Trace; d09e7240 <[ac97_codec].data.end+7875/9695>
Trace; c01f7996 <pci_unregister_driver+3a/54>
Trace; d09e58aa <[ac97_codec].data.end+5edf/9695>
Trace; d09e7240 <[ac97_codec].data.end+7875/9695>
Trace; c01181f3 <free_module+17/98>
Trace; c0117597 <sys_delete_module+f3/1b0>
Trace; c01086df <system_call+33/38>
Code; d09dccdf <[ac97_codec]ac97_release_codec+1b/58>
00000000 <_EIP>:
Code; d09dccdf <[ac97_codec]ac97_release_codec+1b/58> <=====
0: 89 50 04 mov %edx,0x4(%eax) <=====
Code; d09dcce2 <[ac97_codec]ac97_release_codec+1e/58>
3: 89 02 mov %eax,(%edx)
Code; d09dcce4 <[ac97_codec]ac97_release_codec+20/58>
5: c7 03 00 00 00 00 movl $0x0,(%ebx)
Code; d09dccea <[ac97_codec]ac97_release_codec+26/58>
b: c7 43 04 00 00 00 00 movl $0x0,0x4(%ebx)
Code; d09dccf1 <[ac97_codec]ac97_release_codec+2d/58>
12: ff 05 00 00 00 00 incl 0x0
--J.
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
reply other threads:[~2003-07-13 21:19 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=m2smpayuth.fsf@tnuctip.rychter.com \
--to=jan@rychter.com \
--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