Re: XFS or Kernel Problem / Bug

[Stefan Priebe - FH <studium@profihost.com>]

Hi!

Mhm are you shure? I mean i have this problem on 5 servers - all with 
the same mainboard. I cannot believe, that all 5 servers have a hardware 
problem that starts on the same day.

The other thing is - that they all work fine with 2.6.16.x and all other 
kernels before. I mean some of them were used with 2.6.x since two years 
without any problem...

Stefan


Chuck Ebbert schrieb:
> 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.
>