[syslog-ng] weird messages from syslog.

)\( at sS athanasios.silis at gmail.com
Thu Apr 26 00:23:05 CEST 2007


well thats definitely abit of a relief considering all the pc hardware parts
are completely new.
i don't mind doing a reinstallation of the OS... but here is smth new:
i noticed that some of the messages talked abit about 'smbd' and
'printers'..
i decided to comment out 'load printers' from smb.conf and so far (half a
day later) i haven't got the messages i ported before... i have some new
ones though:) here is a dmesg dump:

<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]
 [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]
 [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
 [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<f928897c>] _nv002554rm+0xa8/0xb4 [nvidia]
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<c0173b2a>] dput+0x8a/0x140
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
 [<c0576d45>] schedule+0x465/0x7a0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]
 [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]
 [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
 [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<c04c7ebf>] sock_sendmsg+0xbf/0x110
 [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
 [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
 [<c01353d7>] hrtimer_run_queues+0x47/0xe0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<c04c7ebf>] sock_sendmsg+0xbf/0x110
 [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
 [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c012719b>] change_clocksource+0x12b/0x170
 [<c01278e0>] update_wall_time+0x190/0x280
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<c0173b2a>] dput+0x8a/0x140
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c05171cb>] devinet_ioctl+0x2db/0x570
 [<c051830e>] inet_sock_destruct+0xbe/0x200
 [<c05783c8>] _spin_lock_bh+0x8/0x20
 [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 [<c0570033>] rpc_unlink+0xc3/0xf0
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]
 [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]
 [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
 [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c01278e0>] update_wall_time+0x190/0x280
 [<c0576d45>] schedule+0x465/0x7a0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]
 [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]
 [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
 [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
 [<c01353d7>] hrtimer_run_queues+0x47/0xe0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<c0173b2a>] dput+0x8a/0x140
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c0576d45>] schedule+0x465/0x7a0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<c04c7ebf>] sock_sendmsg+0xbf/0x110
 [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
 [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c01730e3>] fcntl_setlk64+0x203/0x290
 [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 =======================
<unknown>: hw csum failure.
 [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
 [<c0511a05>] udp_recvmsg+0x135/0x280
 [<c04cc195>] sock_common_recvmsg+0x45/0x70
 [<c04c8038>] sock_recvmsg+0xd8/0x130
 [<c04c7ebf>] sock_sendmsg+0xbf/0x110
 [<c0132370>] autoremove_wake_function+0x0/0x50
 [<c0173b2a>] dput+0x8a/0x140
 [<c02ee77b>] copy_to_user+0x2b/0x40
 [<c04c92e5>] sys_recvfrom+0xd5/0x160
 [<c015fb02>] cache_grow+0x102/0x170
 [<c04c9b75>] sys_socketcall+0x1c5/0x250
 [<c0102eb8>] syscall_call+0x7/0xb
 [<c0570033>] rpc_unlink+0xc3/0xf0
 =======================
root at Stargaze:~#

im actually reading somewhere that sky2 network driver for Yukon2 PCI-E
Marvell based controllers seems to have hw csum failures... the dump of
those is not exactly the same...

nass


On 4/25/07, Balazs Scheidler <bazsi at balabit.hu> wrote:
>
> On Wed, 2007-04-25 at 14:54 +0300, )\(@sS wrote:
> > im sorry i understood nothing of your explanation... :)
> > thats due to my lack  of any knowledge on the matter..
> > i will get ksymoops but could you break down what you mean by back
> > traces and what by 'bogus'
>
> Oopses basically happen for two reasons: software and hardware failure.
> Hardware failures tend to cause mystic and nondeterministic behaviour,
> crashing at random locations. On the consistent backtraces I meant that
> several of the Oopses that you posted had the same backtrace (e.g. the
> same crash location), which indicates that it's more likely a software
> related problem.
>
> The listing I gave you, is the direct x86 dissassembly of the code found
> at the crash location, this is reported as a sequence of bytes in the
> Oops output, right after the "Code:" label.
>
> I said it was bogus as it made no sense. This is not valid code, so
> either something corrupted the instruction pointer (by jumping to an
> invalid function pointer), or something overwrote the stack.
>
> I checked the oopses again, don't go to LKML, your kernel is tainted
> (e.g. it has a proprietary module loaded, they will not help you).
>
> --
> Bazsi
>
> _______________________________________________
> syslog-ng maillist  -  syslog-ng at lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20070426/c73047f6/attachment.html


More information about the syslog-ng mailing list