Re: [2.5.52, ALSA] Unable to handle kernel paging request at virtual address 32347363

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Jochen Hein <jochen@jochen.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.5.52, ALSA] Unable to handle kernel paging request at virtual address 32347363
Date: Fri, 20 Dec 2002 20:30:25 +0100	[thread overview]
Message-ID: <87y96kbi9a.fsf@gswi1164.jochen.org> (raw)
In-Reply-To: <87u1hcv4qb.fsf@gswi1164.jochen.org> (Jochen Hein's message of "Tue, 17 Dec 2002 20:30:14 +0100")

Jochen Hein <jochen@jochen.org> writes:

> This is when loading the cs4232 driver for my Thinkpad 600.
>
> Unable to handle kernel paging request at virtual address 32347363
[...]
> How can I decode the addresses in the modules?

Now with CONFIG_KALLSYMS enabled:

root@gswi1164:~# ./alsa start
Starting ALSA sound driver (version 0.9.0rc5):Unable to handle kernel paging request at virtual address 32347363
 printing eip:
c6aae81c
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0060:[<c6aae81c>]    Not tainted
EFLAGS: 00010286
EIP is at gcc2_compiled.+0x1c/0x6c [snd]
eax: c4924664   ebx: 32347363   ecx: c6ab5540   edx: c4924614
esi: c6ab3351   edi: 32347363   ebp: c35eff38   esp: c35eff2c
ds: 0068   es: 0068   ss: 0068
Process modprobe (pid: 15481, threadinfo=c35ee000 task=c2a713a0)
Stack: c4924614 32347363 c6ae17a0 c35eff54 c6aad660 32347363 00000000 00000000
       c6ae17a0 00000004 c35eff90 c6ae407a 00000001 32347363 c6ad3000 00000004
       00000000 00000000 c6ae17a0 00000000 00000010 c6ac3324 c6ac33b4 00000000
Call Trace:
 [<c6ae17a0>] enable+0x0/0x20 [snd_cs4232]
 [<c6aad660>] snd_card_new+0x40/0x24c [snd]
 [<c6ae17a0>] enable+0x0/0x20 [snd_cs4232]
 [<c6ae407a>] +0x7a/0x34c [snd_cs4232]
 [<c6ae17a0>] enable+0x0/0x20 [snd_cs4232]
 [<c6ae436c>] alsa_card_cs423x_init+0x20/0x54 [snd_cs4232]
 [<c012cab7>] sys_init_module+0x113/0x1a4
 [<c0108cd7>] syscall_call+0x7/0xb

Code: ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 74 34 83
 ./alsa: line 261: 15481 Speicherzugriffsfehler  /sbin/modprobe $line >/dev/null 2>&1
 (cs4232)

ksymopps decodes that as:

Code: ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 74 34 83


>>EIP; c6aae81c <END_OF_CODE+667afbc/????>   <=====

Trace; c6ae17a0 <END_OF_CODE+66adf40/????>
Trace; c6aad660 <END_OF_CODE+6679e00/????>
Trace; c6ae17a0 <END_OF_CODE+66adf40/????>
Trace; c6ae407a <END_OF_CODE+66b081a/????>
Trace; c6ae17a0 <END_OF_CODE+66adf40/????>
Trace; c6ae436c <END_OF_CODE+66b0b0c/????>
Trace; c012cab7 <sys_init_module+113/1a4>
Trace; c0108cd7 <syscall_call+7/b>

Code;  c6aae81c <END_OF_CODE+667afbc/????>
00000000 <_EIP>:
Code;  c6aae81c <END_OF_CODE+667afbc/????>   <=====
   0:   ae                        scas   %es:(%edi),%al   <=====
Code;  c6aae81d <END_OF_CODE+667afbd/????>
   1:   75 08                     jne    b <_EIP+0xb>
Code;  c6aae81f <END_OF_CODE+667afbf/????>
   3:   84 c0                     test   %al,%al
Code;  c6aae821 <END_OF_CODE+667afc1/????>
   5:   75 f8                     jne    ffffffff <_EIP+0xffffffff>
Code;  c6aae823 <END_OF_CODE+667afc3/????>
   7:   31 c0                     xor    %eax,%eax
Code;  c6aae825 <END_OF_CODE+667afc5/????>
   9:   eb 04                     jmp    f <_EIP+0xf>
Code;  c6aae827 <END_OF_CODE+667afc7/????>
   b:   19 c0                     sbb    %eax,%eax
Code;  c6aae829 <END_OF_CODE+667afc9/????>
   d:   0c 01                     or     $0x1,%al
Code;  c6aae82b <END_OF_CODE+667afcb/????>
   f:   85 c0                     test   %eax,%eax
Code;  c6aae82d <END_OF_CODE+667afcd/????>
  11:   74 34                     je     47 <_EIP+0x47>
Code;  c6aae82f <END_OF_CODE+667afcf/????>
  13:   83 00 00                  addl   $0x0,(%eax)


1 warning and 1 error issued.  Results may not be reliable.

     prev parent reply	other threads:[~2002-12-20 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 19:13 [2.5.52, ALSA] Unable to handle kernel paging request at virtual address 32347363 Jochen Hein
2002-12-20 19:30 ` Jochen Hein [this message]

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=87y96kbi9a.fsf@gswi1164.jochen.org \
    --to=jochen@jochen.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 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.