FAQ
Hi

posted this on the forum but then found the mailing list :-) so hope it's ok to post to the list aswell.

we have a centos 4.3 server running samba, winbind and squid
authenticating by winbind to our NT domain. Once in a while in the
early hours it has the below error in /var/log/messages this causes the
machine to fail and we carn't connect to it. It's double dutch to me,
hopefully someone on here will have a suggestion though. TIA

Aug 22 04:03:15 wssproxy kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000024
Aug 22 04:03:15 wssproxy kernel: printing eip:
Aug 22 04:03:15 wssproxy kernel: c0187833
Aug 22 04:03:15 wssproxy kernel: *pde = 1859f067
Aug 22 04:03:15 wssproxy kernel: Oops: 0000 [#1]
Aug
22 04:03:15 wssproxy kernel: Modules linked in: md5 ipv6 autofs4 sunrpc
button battery ac shpchp pcnet32 mii floppy dm_snapshot dm_zero
dm_mirror ext3 jbd dm_mod mptscs$
Aug 22 04:03:15 wssproxy kernel: CPU: 0
Aug 22 04:03:15 wssproxy kernel: EIP: 0060:[<c0187833>] Not tainted VLI
Aug 22 04:03:15 wssproxy kernel: EFLAGS: 00000283 (2.6.9-34.0.2.EL)
Aug 22 04:03:15 wssproxy kernel: EIP is at iput+0x14/0x61
Aug 22 04:03:15 wssproxy kernel: eax: 00000000 ebx: d5b68bf4 ecx: d5b68c04 edx: d5b68c04
Aug 22 04:03:15 wssproxy kernel: esi: d5b68bf4 edi: 00000074 ebp: efeee9e0 esp: c17f5eec
Aug 22 04:03:15 wssproxy kernel: ds: 007b es: 007b ss: 0068
Aug 22 04:03:15 wssproxy kernel: Process kswapd0 (pid: 28, threadinfo=c17f5000 task=c17de0b0)
Aug 22 04:03:15 wssproxy kernel: Stack: dc8ba048 c0182a6d 00000000 000000d8 00000000 c01834b2 c0152e0b 0017ed00
Aug 22 04:03:15 wssproxy kernel: 00000000 000001fe 00000000 00000bff 000000d0 00000020 c0360ba0 00000000
Aug 22 04:03:15 wssproxy kernel: c0360ba0 00000000 c015444b c01131cc 00000bff c17f5f9c 0000000d 00000000
Aug 22 04:03:15 wssproxy kernel: Call Trace:
Aug 22 04:03:15 wssproxy kernel: [<c0182a6d>] prune_dcache+0x2fe/0x49d
Aug 22 04:03:15 wssproxy kernel: [<c01834b2>] shrink_dcache_memory+0x14/0x2b
Aug 22 04:03:15 wssproxy kernel: [<c0152e0b>] shrink_slab+0xf7/0x14c
Aug 22 04:03:15 wssproxy kernel: [<c015444b>] balance_pgdat+0x1b3/0x2cb
Aug 22 04:03:15 wssproxy kernel: [<c01131cc>] sched_clock+0x30/0x73
Aug 22 04:03:15 wssproxy kernel: [<c015461c>] kswapd+0xb9/0xbb
Aug 22 04:03:15 wssproxy kernel: [<c011e867>] autoremove_wake_function+0x0/0x2d
Aug 22 04:03:15 wssproxy kernel: [<c031139a>] ret_from_fork+0x6/0x14
Aug 22 04:03:15 wssproxy kernel: [<c011e867>] autoremove_wake_function+0x0/0x2d
Aug 22 04:03:15 wssproxy kernel: [<c0154563>] kswapd+0x0/0xbb
Aug 22 04:03:15 wssproxy kernel: [<c01041dd>] kernel_thread_helper+0x5/0xb
Aug
22 04:03:15 wssproxy kernel: Code: 5b 5e e9 18 de ff ff 83 78 24 00 75
05 e9 4e fb ff ff e9 72 fd ff ff 53 85 c0 89 c3 74 58 83 bb 9c 01 00 00
20 8b 80 d4 00 00 00 <8b>$
Aug 22 04:03:15 wssproxy kernel: <0>Fatal exception: panic in 5 seconds
Aug 22 04:03:16 wssproxy kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000024
Aug 22 04:03:16 wssproxy kernel: printing eip:
Aug 22 04:03:16 wssproxy kernel: c0187833
Aug 22 04:03:16 wssproxy kernel: *pde = 00000000
Aug 22 04:03:16 wssproxy kernel: Oops: 0000 [#2]
Aug
22 04:03:16 wssproxy kernel: Modules linked in: md5 ipv6 autofs4 sunrpc
button battery ac shpchp pcnet32 mii floppy dm_snapshot dm_zero
dm_mirror ext3 jbd dm_mod mptscs$
Aug 22 04:03:16 wssproxy kernel: CPU: 0
Aug 22 04:03:16 wssproxy kernel: EIP: 0060:[<c0187833>] Not tainted VLI
Aug 22 04:03:16 wssproxy kernel: EFLAGS: 00000283 (2.6.9-34.0.2.EL)
Aug 22 04:03:16 wssproxy kernel: EIP is at iput+0x14/0x61
Aug 22 04:03:16 wssproxy kernel: eax: 00000000 ebx: d5b6868c ecx: d5b6869c edx: d5b6869c
Aug 22 04:03:16 wssproxy kernel: esi: d5b6868c edi: 00000080 ebp: efeee9e0 esp: ccd32cf4
Aug 22 04:03:16 wssproxy kernel: ds: 007b es: 007b ss: 0068
Aug 22 04:03:16 wssproxy kernel: Process prelink (pid: 1580, threadinfo=ccd32000 task=c7e74c50)
Aug 22 04:03:16 wssproxy kernel: Stack: dc8bad68 c0182a6d 00000000 00000080 00000000 c01834b2 c0152e0b 0017d400
Aug 22 04:03:16 wssproxy kernel: 00000000 00000008 00000000 0002b94a 000001d2 00000020 c0360fbc 000001d2
Aug 22 04:03:16 wssproxy kernel: 0000000b ccd32db0 c01541c8 0002b94a 00000000 00000000 00000000 00000020
Aug 22 04:03:16 wssproxy kernel: Call Trace:
Aug 22 04:03:16 wssproxy kernel: [<c0182a6d>] prune_dcache+0x2fe/0x49d
Aug 22 04:03:16 wssproxy kernel: [<c01834b2>] shrink_dcache_memory+0x14/0x2b
Aug 22 04:03:16 wssproxy kernel: [<c0152e0b>] shrink_slab+0xf7/0x14c
Aug 22 04:03:16 wssproxy kernel: [<c01541c8>] try_to_free_pages+0xb9/0x189
Aug 22 04:03:16 wssproxy kernel: [<c014c3aa>] __alloc_pages+0x1fe/0x2f7
Aug 22 04:03:16 wssproxy kernel: [<c014f250>] do_page_cache_readahead+0x14b/0x262
Aug 22 04:03:16 wssproxy kernel: [<c014f4cb>] page_cache_readahead+0x164/0x20a
Aug 22 04:03:16 wssproxy kernel: [<c014872e>] do_generic_mapping_read+0x11c/0x403
Aug 22 04:03:16 wssproxy kernel: [<c0148c3e>] __generic_file_aio_read+0x160/0x17a
Aug 22 04:03:16 wssproxy kernel: [<c0148a15>] file_read_actor+0x0/0xc9
Aug 22 04:03:16 wssproxy kernel: [<c0148c98>] generic_file_aio_read+0x40/0x47
Aug 22 04:03:16 wssproxy kernel: [<c0168a4a>] do_sync_read+0x97/0xc9
Aug 22 04:03:16 wssproxy kernel: [<c0179a94>] open_namei+0x2c5/0x542
Aug 22 04:03:16 wssproxy kernel: [<c0167c76>] filp_open+0x5c/0x70
Aug 22 04:03:16 wssproxy kernel: [<c011e867>] autoremove_wake_function+0x0/0x2d
Aug 22 04:03:16 wssproxy kernel: [<c0168b32>] vfs_read+0xb6/0xe2
Aug 22 04:03:16 wssproxy kernel: [<c0168d45>] sys_read+0x3c/0x62
Aug 22 04:03:16 wssproxy kernel: [<c031147b>] syscall_call+0x7/0xb
Aug
22 04:03:16 wssproxy kernel: Code: 5b 5e e9 18 de ff ff 83 78 24 00 75
05 e9 4e fb ff ff e9 72 fd ff ff 53 85 c0 89 c3 74 58 83 bb 9c 01 00 00
20 8b 80 d4 00 00 00 <8b>$
Aug 22 04:03:16 wssproxy kernel: <0>Fatal exception: panic in 5 seconds
Aug 22 04:03:18 wssproxy ntpd[1937]: sendto(193.13.9.98): Bad file descriptor



Cheers
Andy Dean

E-Mail Disclaimer:
The information in this e-mail is confidential, and may be legally privileged.? It is intended? solely for the addressee.? Access to this e-mail by anyone else is unauthorised.? If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.centos.org/pipermail/centos/attachments/20060822/a25f0398/attachment.htm

Search Discussions

  • William L. Maltby at Aug 22, 2006 at 1:57 pm

    On Tue, 2006-08-22 at 10:28 +0100, Andy Dean wrote:
    Hi

    posted this on the forum but then found the mailing list :-) so hope
    it's ok to post to the list aswell.

    we have a centos 4.3 server running samba, winbind and squid
    authenticating by winbind to our NT domain. Once in a while in the
    early hours it has the below error in /var/log/messages this causes
    the machine to fail and we carn't connect to it. It's double dutch to
    me, hopefully someone on here will have a suggestion though. TIA

    Aug 22 04:03:15 wssproxy kernel: Unable to handle kernel NULL pointer
    dereference at virtual address 00000024
    Seems to be sort of an epidemic. Check for hardware malfunction. I am on
    my old reliable AMD K6-III as I write this due to a long pursued and
    very painful intermittent hardware failure that begins essentially with
    what you have.

    I well deserved lesson about the conspiracy that exists between
    hardware, software and the "Computing Gods of Torture" has been
    administered to me.

    A nul pointer can be due to a software error, but also caused by
    hardware failure, usually a memory error I think.

    Get the room hot and run memtest86 overnight.

    Mine was the congruence of (I think) battery backup failure,
    thunderstorms, software updates and idiocy in the wetware here. Took me
    about two months to realize that it was likely hardware. I do owe a
    [SOLVED] post after I cursed seamonkey updates, which occurred during my
    trials.

    Aug 22 04:03:15 wssproxy kernel: printing eip:
    Aug 22 04:03:15 wssproxy kernel: c0187833
    If it's *not* hardware, this eip can be used with other information by a
    programmer to determine what function and instruction was in process.
    All the below might be useful. But likely only if you have repeatability
    and post a bug.

    If it just happens occasionally and has inconsistent behavior, it'll be
    difficult to chase down. And is more likely hardware after the software
    has matured.
    <snip>
    Another one you might see is the message about glibc detecting double
    frees on software that has been running unchanged for a long time.
    Cheers
    Andy Dean
    <snip dumb "If you read this I have to kill you company blurb>
    HTH
    --
    Bill
    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: not available
    Type: application/pgp-signature
    Size: 189 bytes
    Desc: This is a digitally signed message part
    Url : http://lists.centos.org/pipermail/centos/attachments/20060822/4aa36e10/attachment.bin
  • Andy Dean at Aug 23, 2006 at 8:45 am
    Hi

    thanks for the info will run some tests on the hardware and see what that says.

    Also see if there are any updates for esx server, incase it's a problem with the way vmware managers memory / hardware.


    Cheers
    Andy Dean



    ----- Original Message -----
    From: William L. Maltby
    Sent: Tue, 8/22/2006 2:54pm
    To: CentOS General List
    Subject: Re: [CentOS] centos 4.3 on esx server high load early hours carn' t connect.

    _______________________________________________
    CentOS mailing list
    CentOS@centos.org
    http://lists.centos.org/mailman/listinfo/centos





    ----- Inline Message Follows -----

    From: ` YV? Z@wssscalix.link51.co.uk

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcentos @
categoriescentos
postedAug 22, '06 at 9:28a
activeAug 23, '06 at 8:45a
posts3
users2
websitecentos.org
irc#centos

2 users in discussion

Andy Dean: 2 posts William L. Maltby: 1 post

People

Translate

site design / logo © 2022 Grokbase