well thats definitely abit of a relief considering all the pc hardware parts are completely new.<br>i don't mind doing a reinstallation of the OS... but here is smth new:<br>i noticed that some of the messages talked abit about 'smbd' and 'printers'..
<br>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:<br><br><unknown>: hw csum failure.
<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]
<br> [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]<br> [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]
<br> [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]<br> [<c02ee77b>] copy_to_user+0x2b/0x40<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<f928897c>] _nv002554rm+0xa8/0xb4 [nvidia]<br> [<c01730e3>] fcntl_setlk64+0x203/0x290
<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<c0173b2a>] dput+0x8a/0x140
<br> [<c02ee77b>] copy_to_user+0x2b/0x40<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0<br> [<c01730e3>] fcntl_setlk64+0x203/0x290<br> [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
<br> [<c0576d45>] schedule+0x465/0x7a0<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]<br> [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]
<br> [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]<br> [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
<br> [<c02ee77b>] copy_to_user+0x2b/0x40<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0<br> [<c01730e3>] fcntl_setlk64+0x203/0x290<br> [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<c04c7ebf>] sock_sendmsg+0xbf/0x110<br> [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]<br> [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]<br> [<c02ee77b>] copy_to_user+0x2b/0x40
<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0<br> [<c01730e3>] fcntl_setlk64+0x203/0x290<br> [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0<br> [<c01353d7>] hrtimer_run_queues+0x47/0xe0
<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<c04c7ebf>] sock_sendmsg+0xbf/0x110<br> [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]<br> [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]<br> [<c02ee77b>] copy_to_user+0x2b/0x40
<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c012719b>] change_clocksource+0x12b/0x170<br> [<c01278e0>] update_wall_time+0x190/0x280<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb
<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70
<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<c0173b2a>] dput+0x8a/0x140<br> [<c02ee77b>] copy_to_user+0x2b/0x40<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160
<br> [<c05171cb>] devinet_ioctl+0x2db/0x570<br> [<c051830e>] inet_sock_destruct+0xbe/0x200<br> [<c05783c8>] _spin_lock_bh+0x8/0x20<br> [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250
<br> [<c0102eb8>] syscall_call+0x7/0xb<br> [<c0570033>] rpc_unlink+0xc3/0xf0<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]<br> [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]
<br> [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]<br> [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
<br> [<c02ee77b>] copy_to_user+0x2b/0x40<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0<br> [<c01730e3>] fcntl_setlk64+0x203/0x290<br> [<c01278e0>] update_wall_time+0x190/0x280
<br> [<c0576d45>] schedule+0x465/0x7a0<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<f92733d6>] _nv003589rm+0x26/0x2c [nvidia]<br> [<f9474bef>] _nv007223rm+0x23/0x28 [nvidia]
<br> [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]<br> [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]
<br> [<c02ee77b>] copy_to_user+0x2b/0x40<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0<br> [<c01730e3>] fcntl_setlk64+0x203/0x290<br> [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0
<br> [<c01353d7>] hrtimer_run_queues+0x47/0xe0<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<c0173b2a>] dput+0x8a/0x140
<br> [<c02ee77b>] copy_to_user+0x2b/0x40<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0<br> [<c01730e3>] fcntl_setlk64+0x203/0x290<br> [<c0576d45>] schedule+0x465/0x7a0
<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120
<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<c04c7ebf>] sock_sendmsg+0xbf/0x110<br> [<f9474b30>] _nv007225rm+0x28/0x44 [nvidia]
<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<f928d77d>] rm_set_interrupts+0x129/0x15c [nvidia]<br> [<f928d796>] rm_set_interrupts+0x142/0x15c [nvidia]<br> [<c02ee77b>] copy_to_user+0x2b/0x40
<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c01730e3>] fcntl_setlk64+0x203/0x290<br> [<c01837ba>] invalidate_inode_buffers+0x1a/0xe0<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb
<br> =======================<br><unknown>: hw csum failure.<br> [<c04d056d>] skb_copy_and_csum_datagram_iovec+0x10d/0x120<br> [<c0511a05>] udp_recvmsg+0x135/0x280<br> [<c04cc195>] sock_common_recvmsg+0x45/0x70
<br> [<c04c8038>] sock_recvmsg+0xd8/0x130<br> [<c04c7ebf>] sock_sendmsg+0xbf/0x110<br> [<c0132370>] autoremove_wake_function+0x0/0x50<br> [<c0173b2a>] dput+0x8a/0x140<br> [<c02ee77b>] copy_to_user+0x2b/0x40
<br> [<c04c92e5>] sys_recvfrom+0xd5/0x160<br> [<c015fb02>] cache_grow+0x102/0x170<br> [<c04c9b75>] sys_socketcall+0x1c5/0x250<br> [<c0102eb8>] syscall_call+0x7/0xb<br> [<c0570033>] rpc_unlink+0xc3/0xf0
<br> =======================<br>root@Stargaze:~#<br><br>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...
<br><br>nass<br><br><br><div><span class="gmail_quote">On 4/25/07, <b class="gmail_sendername">Balazs Scheidler</b> <<a href="mailto:bazsi@balabit.hu">bazsi@balabit.hu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, 2007-04-25 at 14:54 +0300, )\(@sS wrote:<br>> im sorry i understood nothing of your explanation... :)<br>> thats due to my lack of any knowledge on the matter..<br>> i will get ksymoops but could you break down what you mean by back
<br>> traces and what by 'bogus'<br><br>Oopses basically happen for two reasons: software and hardware failure.<br>Hardware failures tend to cause mystic and nondeterministic behaviour,<br>crashing at random locations. On the consistent backtraces I meant that
<br>several of the Oopses that you posted had the same backtrace (e.g. the<br>same crash location), which indicates that it's more likely a software<br>related problem.<br><br>The listing I gave you, is the direct x86 dissassembly of the code found
<br>at the crash location, this is reported as a sequence of bytes in the<br>Oops output, right after the "Code:" label.<br><br>I said it was bogus as it made no sense. This is not valid code, so<br>either something corrupted the instruction pointer (by jumping to an
<br>invalid function pointer), or something overwrote the stack.<br><br>I checked the oopses again, don't go to LKML, your kernel is tainted<br>(e.g. it has a proprietary module loaded, they will not help you).<br><br>
--<br>Bazsi<br><br>_______________________________________________<br>syslog-ng maillist - <a href="mailto:syslog-ng@lists.balabit.hu">syslog-ng@lists.balabit.hu</a><br><a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng">
https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>Frequently asked questions at <a href="http://www.campin.net/syslog-ng/faq.html">http://www.campin.net/syslog-ng/faq.html</a><br><br></blockquote></div><br>