public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Stefan Priebe - FH <studium@profihost.com>
Cc: linux-kernel@vger.kernel.org, stefan@priebe.ws,
	David Chinner <dgc@sgi.com>
Subject: Re: XFS or Kernel Problem / Bug
Date: Wed, 24 Jan 2007 11:51:43 -0500	[thread overview]
Message-ID: <45B78E9F.4000404@redhat.com> (raw)
In-Reply-To: <45B77C84.6070508@profihost.com>

Stefan Priebe - FH wrote:
> Sorry that is not possible - cause it is a production machine.
>
> But i've catched the error and the files from another machine -
> perhaps this helps.
>
> "BUG: unable to handle kernel NULL pointer dereference at virtual
> address 00000288"
> " printing eip:"
> "c0142ff7"
> "*pde = 00000000"
> "Oops: 0000 [#1]"
> "SMP "
> "Modules linked in: iptable_filter ip_tables x_tables"
> "CPU:    0"
> "EIP:    0060:[<c0142ff7>]    Not tainted VLI"
> "EFLAGS: 00010246   (2.6.18.6 #1) "
> "EIP is at generic_file_buffered_write+0x390/0x6cf"
> "eax: 00000000   ebx: 000001ec   ecx: ea029a40   edx: 00008002"
> "esi: 00000000   edi: e3b28c9c   ebp: 000001ec   esp: dd04bd18"
> "ds: 007b   es: 007b   ss: 0068"
> "Process proftpd (pid: 3615, ti=dd04a000 task=eba88a70 task.ti=dd04a000)"
> "Stack: e3b28d44 00000001 00000010 000001fc c036d793 000001fc c14765c0
> 00000010 "
> "       080d404c 000001ec e3b28c9c c03e78c0 e3b28d44 ea029a40 000001fc
> 00000000 "
> "       00000000 000001ec dd04beac 00d420b1 00000000 00000000 dd04bd80
> 45b1fa67 "
> "Call Trace:"
> " [<c036d793>] sock_def_readable+0x7f/0x81"
> " [<c017a03a>] file_update_time+0xad/0xcb"
> " [<c0232015>] xfs_iunlock+0x55/0x9f"
> " [<c0262eeb>] xfs_write+0xa74/0xc61"
> " [<c036a253>] sock_aio_read+0x95/0x99"
> " [<c025d9fb>] xfs_file_aio_write+0x8f/0xa0"
> " [<c015fb94>] do_sync_write+0xc9/0x10f"
> " [<c0133ad6>] autoremove_wake_function+0x0/0x57"
> " [<c015f3d5>] generic_file_llseek+0x95/0xbc"
> " [<c015facb>] do_sync_write+0x0/0x10f"
> " [<c015fc80>] vfs_write+0xa6/0x179"
> " [<c015fe24>] sys_write+0x51/0x80"
> " [<c0102d3f>] syscall_call+0x7/0xb"
> "Code: 04 89 10 8b 44 24 40 85 c0 0f 85 db 00 00 00 8b 5c 24 24 85 db
> 0f 88 c3 00 00 00 8b 4c 24 34 8b 51 18 f6 c6 10 75 73 8b 7c 24 28 <8b>
> 85 9c 00 00 00 f6 40 30 10 75 63 f6 87 48 01 00 00 01 75 5a "
> "EIP: [<c0142ff7>] generic_file_buffered_write+0x390/0x6cf SS:ESP
> 0068:dd04bd18"
>
> Files:
> http://server113-han.de-nserver.de/filemap.s
> http://server113-han.de-nserver.de/filemap.o
>
You seem to have some kind of hardware/memory problem.

Disassembly of the failing instruction from the oops:

     8b 7c 24 28               mov    0x28(%esp),%edi
     8b 85 9c 00 00 00         mov    0x9c(%ebp),%eax   <=====

Dump of the object code:

           8b 7c 24 28             mov    0x28(%esp),%edi
           8b 87 9c 00 00 00       mov    0x9c(%edi),%eax

Looks like a bit is flipped.


  reply	other threads:[~2007-01-24 16:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060801141545.B2326184@wobbly.melbourne.sgi.com>
     [not found] ` <44CED76B.20507@profihost.com>
     [not found]   ` <20060801142755.C2326184@wobbly.melbourne.sgi.com>
     [not found]     ` <44CED8F4.9080208@profihost.com>
     [not found]       ` <20060801143212.D2326184@wobbly.melbourne.sgi.com>
     [not found]         ` <44CEDA1D.5060607@profihost.com>
     [not found]           ` <20060801143803.E2326184@wobbly.melbourne.sgi.com>
     [not found]             ` <44CF36FB.6070606@profihost.com>
     [not found]               ` <20060802090915.C2344877@wobbly.melbourne.sgi.com>
     [not found]                 ` <44D07AB7.3020409@profihost.com>
     [not found]                   ` <20060802201805.A2360409@wobbly.melbourne.sgi.com>
2007-01-21 12:30                     ` XFS or Kernel Problem / Bug Stefan Priebe - FH
2007-01-22  6:18                       ` David Chinner
2007-01-22  7:51                         ` Stefan Priebe - FH
2007-01-22  8:03                           ` David Chinner
2007-01-22  8:07                             ` Stefan Priebe - FH
2007-01-23  1:10                               ` David Chinner
2007-01-23  8:31                                 ` Stefan Priebe - FH
2007-01-22  9:42                             ` Stefan Priebe - FH
2007-01-23 19:49                       ` Chuck Ebbert
2007-01-24  7:40                         ` Stefan Priebe - FH
2007-01-24 14:57                           ` Chuck Ebbert
2007-01-24 15:03                             ` Stefan Priebe - FH
2007-01-24 15:13                               ` Chuck Ebbert
2007-01-24 15:34                                 ` Stefan Priebe - FH
2007-01-24 16:51                                   ` Chuck Ebbert [this message]
2007-01-24 17:16                                     ` Stefan Priebe - FH
2007-01-24 17:56                                       ` Chuck Ebbert
2007-01-24 19:27                                         ` Stefan Priebe - FH
2007-01-25 20:52                                           ` Chuck Ebbert
2007-01-25 21:29                                             ` Stefan Priebe - FH
2007-01-30 10:44                                               ` Stefan Priebe - FH

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=45B78E9F.4000404@redhat.com \
    --to=cebbert@redhat.com \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan@priebe.ws \
    --cc=studium@profihost.com \
    /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