Greg Lopp on 31 Oct 2007 19:32:48 -0000


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Kernel BUG?

  • From: "Greg Lopp" <lopp@pobox.com>
  • To: "Philadelphia Linux User's Group Discussion List" <plug@lists.phillylinux.org>
  • Subject: Re: [PLUG] Kernel BUG?
  • Date: Wed, 31 Oct 2007 14:32:43 -0500
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=C2NifTNranVH1kx46QCm2y+/T9WxhHUpQlbmgDTCjSg=; b=MSiEjnJK6PjTaCXOlV37VmP0mfQu6wOJzrWUH6KzxJcnOF9nm0J+pbsSKSM2SPGHAfHpDq61ENHSwgYjrYhsTRg5v0DAxI9M7vt6G3CeqzHV49mDmaG/Y5Pi1KEx/8cz+fPeme57XwFsuYGJn2oCVhKVQUUFfbPOX9TxgAywhXw=
  • Reply-to: Philadelphia Linux User's Group Discussion List <plug@lists.phillylinux.org>
  • Sender: plug-bounces@lists.phillylinux.org
On 10/31/07, Stephen Gran <steve@lobefin.net> wrote:
On Wed, Oct 31, 2007 at 02:20:43PM -0400, Mike Leone said:
> Can anyone help me decipher this? It happened to me earlier today ...

Kernel panic, due to an unchecked parameter somewhere, it looks like.

> Debian testing, kernel 2.6.22-7. CPU is a Duron 1.6GHz, so the kernel image
> I installed is a K7 one.
>
> Linux mail 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 GNU/Linux
>
> > Oct 31 13:07:57 mail kernel: BUG: unable to handle kernel paging request at virtual address 5c000060

So a piece of memory was asked for, but the kernel couldn't satisfy the
request.

> > Oct 31 13:07:57 mail kernel: EIP:    0060:[<c018bd95>]    Not tainted VLI

Good, no dodgy out of tree modules.

> > Oct 31 13:07:57 mail kernel: EIP is at do_mpage_readpage+0x4b/0x5d2
> > Oct 31 13:07:57 mail kernel: Call Trace:
> > Oct 31 13:07:57 mail kernel:  [<e89656f5>] ext3_get_block+0x0/0xd0 [ext3]

0x0 is not a valid memory address.  Clearly a bug.  Submit it to the BTS

Uh, I don't think that nomenclature is what you are describing.  It's not trying to read 0x0, its executing at the address
ext3_get_block+0x0 (where ext3_get_block is some label found in the System.map file).  The distance between ext3_get_block and the next label is 0xd0
So the first thing ext3_get_block() does is call __do_page_cache_readahead(), which runs 0x8d of code and calls __d_lookup().....and so on until sysenter_past_esp() where the paging problem occurs.... 
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug