LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Unable to handle kernel NULL pointer dereference at virtual address

To: Ratz <ratz@xxxxxx>
Subject: Re: Unable to handle kernel NULL pointer dereference at virtual address
Cc: Wensong Zhang <wensong@xxxxxxxxxxxx>, "lvs-users@xxxxxxxxxxxxxxxxxxxxxx" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: Julian Anastasov <uli@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 25 Apr 2000 18:46:46 +0300 (EEST)
        Hello,

On Tue, 25 Apr 2000, Ratz wrote:

> Hi Wensong, 
> 
> Since several days I get those kernel messages running ipvs-0.9.9 patch
> on kernel 2.2.14.
> It seems to have no impact on the functionality of the service itself,
> so I think my test
> machine is somewhat f*ed up. Here's the message:
> 
> IP_VS: WRR scheduling module loaded.
> .
> .
> -> After hours
> .
> .
> Unable to handle kernel NULL pointer dereference at virtual address
> 0000002b
> current->tss.cr3 = 025e7000, %cr3 = 025e7000
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<0000002b>]

        Can you try gdb /usr/src/linux/vmlinux ?

        disassemble 0x80109391
        For 85000000, 801093f4, 801a2458, 801a3b2e too.

        Or just try with ksymoops:
/usr/src/linux/Documentation/oops-tracing.txt

> EFLAGS: 00010282
> eax: fffffff7   ebx: 8211a000   ecx: 0000002b   edx: 2ac56b74
> esi: 00000002   edi: 00000008   ebp: 7fffe788   esp: 8211bfec
> ds: 0018   es: 0018   ss: 0018
> Process standard (pid: 11422, process nr: 49, stackpage=8211b000)
> Stack: 2ac56b74 00000023 00000246 7fffe75c 0000002b 
> Call Trace: 
> Code: <1>Unable to handle kernel NULL pointer dereference at virtual
> address 000
> 0002b
> current->tss.cr3 = 025e7000, %cr3 = 025e7000
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<80109391>]
> EFLAGS: 00010046
> eax: 00000000   ebx: 00000000   ecx: 0000002b   edx: 832b0000
> esi: 0000002b   edi: 8211c000   ebp: 84800000   esp: 8211bf2c
> ds: 0018   es: 0018   ss: 0018
> Process standard (pid: 11422, process nr: 49, stackpage=8211b000)
> Stack: 0000002b 08048000 801e7d4e 00000002 00000008 7fffe788 fffffff7
> 8211a000 
>        0000002b 2ac56b74 0000002b 00010282 04000000 85000000 801093f4
> 8211bfb0 
>        801a2458 801a3b2e 00000000 00000000 8010e410 801a3b2e 8211bfb0
> 00000000 
> Call Trace: [<85000000>] [<801093f4>] [<801a2458>] [<801a3b2e>]
> [<8010e410>] [<8
> 01a3b2e>] [<80109035>] 
> Code: 8a 04 0b 89 44 24 38 50 68 50 24 1a 80 e8 cd 9b 00 00 83 c4 
> IP_VS: WRR scheduling module unloaded.
> IP_VS: WRR scheduling module loaded.
> IP_VS: WRR scheduling module unloaded.
> IP_VS: vs_ctl: invalid protocol: 00.0.0.0:0 
> 
> As a more detailed investigation with the map file showed, this seems to
> be 
> happening also on other processes, no only when deleting a template. A
> check
> back reveiled dumps for bash, sh, watch, so I'd suggest my machine is
> has
> a little problem (memory?). The strange point is, however, that it runs 
> very stable for days now. 
> 
> If somebody out there experienced the same problem, I'd like to know,
> this 
> could help me tracking down this occurency.


Regards

--
Julian Anastasov <uli@xxxxxxxxxxxxxxxxxxxxxx>



<Prev in Thread] Current Thread [Next in Thread>