public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Sacher <sacher@dvoid.org>
To: linux-kernel@vger.kernel.org
Subject: Unable to handle kernel paging request at virtual address
Date: Mon, 16 Jul 2001 20:27:21 +0200	[thread overview]
Message-ID: <01071620272102.02650@jukebox.juke.net> (raw)

hi !
i not a kernel hacker, so i don't know, whom to write to.
maybe you can help !
i get several application-crashs on my redhat7.1 (updated to kernel 2.4.3-12) 
and every crash produces some kind of this:

----------------------------------------------------------------------------
Jul 16 20:04:35 jukebox kernel:  <1>Unable to handle kernel paging request at 
virtual address 41648370
Jul 16 20:04:35 jukebox kernel:  printing eip:
Jul 16 20:04:35 jukebox kernel: c013f6bc
Jul 16 20:04:35 jukebox kernel: pgd entry c8dd6414: 0000000000000000
Jul 16 20:04:35 jukebox kernel: pmd entry c8dd6414: 0000000000000000
Jul 16 20:04:35 jukebox kernel: ... pmd not present!
Jul 16 20:04:35 jukebox kernel: Oops: 0000
Jul 16 20:04:35 jukebox kernel: CPU:    0
Jul 16 20:04:35 jukebox kernel: EIP:    0010:[d_lookup+96/260]
Jul 16 20:04:35 jukebox kernel: EIP:    0010:[<c013f6bc>]
Jul 16 20:04:35 jukebox kernel: EFLAGS: 00010a87
Jul 16 20:04:35 jukebox kernel: eax: c1640000   ebx: 41648328   ecx: 0000000f 
  edx: 134b8ec9
Jul 16 20:04:35 jukebox kernel: esi: 134b8ec9   edi: c6c99f84   ebp: 41648340 
  esp: c6c99eb4
Jul 16 20:04:35 jukebox kernel: ds: 0018   es: 0018   ss: 0018
Jul 16 20:04:35 jukebox kernel: Process gkrellm (pid: 6233, 
stackpage=c6c99000)
Jul 16 20:04:35 jukebox kernel: Stack: c1648340 c43e000a 134b8ec9 00000005 
c6c99f18 134b8ec9 c6c99f84 c43e000f 
Jul 16 20:04:35 jukebox kernel:        c01377f6 ca020f60 c6c99f18 c6c99f18 
c0137eb7 ca020f60 c6c99f18 00000000 
Jul 16 20:04:35 jukebox kernel:        c6c99f04 c6c99f04 00000001 00000000 
00000000 c33df7e0 000009f7 000001f4 
Jul 16 20:04:35 jukebox kernel: Call Trace: [cached_lookup+14/72] 
[path_walk+1275/1880] [open_namei+145/1456] [filp_open+50/80] [getname+92/
152] 
Jul 16 20:04:35 jukebox kernel: Call Trace: [<c01377f6>] [<c0137eb7>] 
[<c01385c1>] [<c012dd72>] [<c0137608>] 
Jul 16 20:04:35 jukebox kernel:    [sys_open+49/148] [system_call+51/56] 
Jul 16 20:04:35 jukebox kernel:    [<c012e029>] [<c0106c1f>] 
Jul 16 20:04:35 jukebox kernel: 
Jul 16 20:04:35 jukebox kernel: Code: 39 53 48 8b 6d 00 0f 85 80 00 00 00 8b 
44 24 24 39 43 0c 75 
----------------------------------------------------------------------------

i even can compile me a new kernel (2.4.6 / 2.2.19), because everytime i try, 
i get this bug and the "make" process dies.
maybe someone can give a hint.

thanks a lot !
d.sacher


             reply	other threads:[~2001-07-16 18:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 18:27 Dominik Sacher [this message]
2001-07-19  3:13 ` Unable to handle kernel paging request at virtual address Jesse Wyant
  -- strict thread matches above, loose matches on Subject: below --
2001-11-10  4:23 Femitha Majeed
2001-11-11 21:47 ` Erik Mouw
2002-05-08  5:42 pavankvk
2007-08-09 23:17 shacky
2007-08-09 23:40 ` Dave Jones
2007-08-09 23:44   ` shacky
2007-08-10  0:09     ` Dave Jones
2007-08-10 11:03       ` shacky
2007-08-10 11:20         ` shacky

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=01071620272102.02650@jukebox.juke.net \
    --to=sacher@dvoid.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