weird messages from syslog.
hello everyone, i am really weirded out by some of the messages that appear on stdout from syslog and the kernel. i dunno where to turn in order to interpret the messages so i ask if you please take a look.. and perhaps direct me to someone. thank you in advance im setting up a pc that i want to use as server. its characteristics are m/b: Gigabyte - GA965P -DQ6. Northbridge: Intel P965 chipset; Southbridge: Intel ICH8R chipset; supports 6x Sata2 drives in; simple, AHCI, or raid 0,1,5,10,JBOD Gigabyte Sata controller; an additional controller (dunno what driver goes with it in linux kernel) supports 2 additional sata2 ports and raid 0,1 configurations. also: 1x WD 40GB raptor hard drive for the OS and 4x 320GB caviar hard drivers in RAID5 for data. ok i have setup the raid5 and i think it is working fine - it is not of much interest anyway.. i just note it in case you know of smth that is slipping me... also im running slackware 11. with a kernel that compile on my own from v. 2.6.20.7 the important and the reason im writing , is cause im trying to download some files from another pc through an sftp session.. im saving to the 40GB drive. thats /dev/sda1. the name of the pc is 'stargaze' .. now some history: last night twice in trying to copy a big tar.bz2 (100MB) from that pc to stargaze. and at some point it froze ( the pc that is). so i restarted and redid the sftp session.. the file arrived. then i also tried to download with mget ... about 200 photos of size 1MB each. the pc crashed again (btw not even reset button would restart the pc). reboot the pc.. (it took ages cause it would find that the file system is NOT clean and it would initiate 'journal transactions'. ok well that message was perhaps intented for sda1.. but its possible it was for /dev/md0.... anyhow today i tried again the same 2 sftp sessions.. trying to download the same files... it worked the couple of times i tried it... but here is the weird messages im getting... on stdout and /var/log/syslog BUG: unable to handle kernel paging request at virtual address 6dcecdd9 printing eip: c02eb417 *pde = 00000000 Oops: 0000 [#1] SMP Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss appletalk psnap llc ide_scsi generic nvidia(P) snd_hda_intel snd_hda_codec jmicron snd_pcm snd_timer snd snd_page_alloc CPU: 0 EIP: 0060:[<c02eb417>] Tainted: P VLI EFLAGS: 00210046 (2.6.20.7C2D6400,2x1GBRAM800,P965-ICH8R,Marv8056,1x40GB+3x320GBr5 #5) EIP is at radix_tree_lookup+0x37/0x60 eax: 00000000 ebx: 8b372010 ecx: 434ac05a edx: 6dcecdc9 esi: 00000000 edi: 00000000 ebp: f3ccd494 esp: f2f1bd7c ds: 007b es: 007b ss: 0068 Process smbd (pid: 3739, ti=f2f1a000 task=f4243550 task.ti=f2f1a000) Stack: 00000000 00000000 c01488c0 00000052 f3ccd4a4 00000000 00000001 00000000 f7b37cc0 f2f1bda0 f2f1bda0 f2f1be3c f3ccd494 00000000 f7b37cc0 c0148add 00000004 f2f1be3c 00000000 00000001 00000020 c0148d3b 00000004 f2f1be3c Call Trace: [<c01488c0>] __do_page_cache_readahead+0x90/0x160 [<c0148add>] blockable_page_cache_readahead+0x4d/0xd0 [<c0148d3b>] page_cache_readahead+0x10b/0x1c0 [<c01424e2>] do_generic_mapping_read+0x482/0x540 [<c0142824>] generic_file_aio_read+0x194/0x1f0 [<c01425a0>] file_read_actor+0x0/0xf0 [<c0162c7d>] do_sync_read+0xbd/0x110 [<c016bd7a>] open_namei+0xda/0x550 [<c0132370>] autoremove_wake_function+0x0/0x50 [<c0162d64>] vfs_read+0x94/0x170 [<c0163111>] sys_read+0x41/0x70 [<c0102eb8>] syscall_call+0x7/0xb ======================= Code: 3a f6 c2 01 75 3e 8b 1a 31 c0 39 34 9d f0 ed 75 c0 72 28 8d 04 5b 8d 4c 00 fa 8d 76 00 8d bc 27 00 00 00 00 89 f0 d3 e8 83 e0 3f <8b> 54 82 10 85 d2 74 1c 83 e9 06 4b 75 eb 89 d0 5b 5e c3 8d b6 EIP: [<c02eb417>] radix_tree_lookup+0x37/0x60 SS:ESP 0068:f2f1bd7c <1>BUG: unable to handle kernel paging request at virtual address 6dcecdd9 printing eip: c02eb417 *pde = 00000000 Oops: 0000 [#2] SMP Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss appletalk psnap llc ide_scsi generic nvidia(P) snd_hda_intel snd_hda_codec jmicron snd_pcm snd_timer snd snd_page_alloc CPU: 0 EIP: 0060:[<c02eb417>] Tainted: P VLI EFLAGS: 00210046 (2.6.20.7C2D6400,2x1GBRAM800,P965-ICH8R,Marv8056,1x40GB+3x320GBr5 #5) EIP is at radix_tree_lookup+0x37/0x60 eax: 00000000 ebx: 8b372010 ecx: 434ac05a edx: 6dcecdc9 esi: 00000000 edi: 00000000 ebp: f3ccd494 esp: f2f93d7c ds: 007b es: 007b ss: 0068 Process smbd (pid: 3769, ti=f2f92000 task=f2f33030 task.ti=f2f92000) Stack: 00000000 00000000 c01488c0 00000052 f3ccd4a4 00000000 00000001 00000000 f437b9c0 f2f93da0 f2f93da0 f2f93e3c f3ccd494 00000000 f437b9c0 c0148add 00000004 f2f93e3c 00000000 00000001 00000020 c0148d3b 00000004 f2f93e3c Call Trace: [<c01488c0>] __do_page_cache_readahead+0x90/0x160 [<c0148add>] blockable_page_cache_readahead+0x4d/0xd0 [<c0148d3b>] page_cache_readahead+0x10b/0x1c0 [<c01424e2>] do_generic_mapping_read+0x482/0x540 [<c0142824>] generic_file_aio_read+0x194/0x1f0 [<c01425a0>] file_read_actor+0x0/0xf0 [<c0162c7d>] do_sync_read+0xbd/0x110 [<c016bd7a>] open_namei+0xda/0x550 [<c0132370>] autoremove_wake_function+0x0/0x50 [<c0162d64>] vfs_read+0x94/0x170 [<c0163111>] sys_read+0x41/0x70 [<c0102eb8>] syscall_call+0x7/0xb ======================= Code: 3a f6 c2 01 75 3e 8b 1a 31 c0 39 34 9d f0 ed 75 c0 72 28 8d 04 5b 8d 4c 00 fa 8d 76 00 8d bc 27 00 00 00 00 89 f0 d3 e8 83 e0 3f <8b> 54 82 10 85 d2 74 1c 83 e9 06 4b 75 eb 89 d0 5b 5e c3 8d b6 EIP: [<c02eb417>] radix_tree_lookup+0x37/0x60 SS:ESP 0068:f2f93d7c <1>BUG: unable to handle kernel paging request at virtual address 6dcecdd9 printing eip: c02eb417 *pde = 00000000 Oops: 0000 [#3] SMP Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss appletalk psnap llc ide_scsi generic nvidia(P) snd_hda_intel snd_hda_codec jmicron snd_pcm snd_timer snd snd_page_alloc CPU: 0 EIP: 0060:[<c02eb417>] Tainted: P VLI EFLAGS: 00210046 (2.6.20.7C2D6400,2x1GBRAM800,P965-ICH8R,Marv8056,1x40GB+3x320GBr5 #5) EIP is at radix_tree_lookup+0x37/0x60 eax: 00000000 ebx: 8b372010 ecx: 434ac05a edx: 6dcecdc9 esi: 00000000 edi: 00000000 ebp: f3ccd494 esp: f2f4fd7c ds: 007b es: 007b ss: 0068 Process smbd (pid: 3801, ti=f2f4e000 task=f7087030 task.ti=f2f4e000) Stack: 00000000 00000000 c01488c0 00000052 f3ccd4a4 00000000 00000001 00000000 f437b3c0 f2f4fda0 f2f4fda0 f2f4fe3c f3ccd494 00000000 f437b3c0 c0148add 00000004 f2f4fe3c 00000000 00000001 00000020 c0148d3b 00000004 f2f4fe3c Call Trace: [<c01488c0>] __do_page_cache_readahead+0x90/0x160 [<c0148add>] blockable_page_cache_readahead+0x4d/0xd0 [<c0148d3b>] page_cache_readahead+0x10b/0x1c0 [<c01424e2>] do_generic_mapping_read+0x482/0x540 [<c0142824>] generic_file_aio_read+0x194/0x1f0 [<c01425a0>] file_read_actor+0x0/0xf0 [<c0162c7d>] do_sync_read+0xbd/0x110 [<c016bd7a>] open_namei+0xda/0x550 [<c0132370>] autoremove_wake_function+0x0/0x50 [<c0162d64>] vfs_read+0x94/0x170 [<c0163111>] sys_read+0x41/0x70 [<c0102eb8>] syscall_call+0x7/0xb ======================= Code: 3a f6 c2 01 75 3e 8b 1a 31 c0 39 34 9d f0 ed 75 c0 72 28 8d 04 5b 8d 4c 00 fa 8d 76 00 8d bc 27 00 00 00 00 89 f0 d3 e8 83 e0 3f <8b> 54 82 10 85 d2 74 1c 83 e9 06 4b 75 eb 89 d0 5b 5e c3 8d b6 EIP: [<c02eb417>] radix_tree_lookup+0x37/0x60 SS:ESP 0068:f2f4fd7c <3><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 [<c015fc3c>] cache_alloc_refill+0xcc/0x1e0 [<c01730e3>] fcntl_setlk64+0x203/0x290 [<c01278e0>] update_wall_time+0x190/0x280 [<c04c9b75>] sys_socketcall+0x1c5/0x250 [<c0102eb8>] syscall_call+0x7/0xb ======================= BUG: unable to handle kernel paging request at virtual address 6dcecdd9 printing eip: c02eb417 *pde = 00000000 Oops: 0000 [#4] SMP Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss appletalk psnap llc ide_scsi generic nvidia(P) snd_hda_intel snd_hda_codec jmicron snd_pcm snd_timer snd snd_page_alloc CPU: 0 EIP: 0060:[<c02eb417>] Tainted: P VLI EFLAGS: 00210046 (2.6.20.7C2D6400,2x1GBRAM800,P965-ICH8R,Marv8056,1x40GB+3x320GBr5 #5) EIP is at radix_tree_lookup+0x37/0x60 eax: 00000000 ebx: 8b372010 ecx: 434ac05a edx: 6dcecdc9 esi: 00000000 edi: 00000000 ebp: f3ccd494 esp: f2615d7c ds: 007b es: 007b ss: 0068 Process smbd (pid: 3856, ti=f2614000 task=f4243550 task.ti=f2614000) Stack: 00000000 00000000 c01488c0 00000052 f3ccd4a4 00000000 00000001 00000000 f7b36800 f2615da0 f2615da0 f2615e3c f3ccd494 00000000 f7b36800 c0148add 00000004 f2615e3c 00000000 00000001 00000020 c0148d3b 00000004 f2615e3c Call Trace: [<c01488c0>] __do_page_cache_readahead+0x90/0x160 [<c0148add>] blockable_page_cache_readahead+0x4d/0xd0 [<c0148d3b>] page_cache_readahead+0x10b/0x1c0 [<c01424e2>] do_generic_mapping_read+0x482/0x540 [<c0142824>] generic_file_aio_read+0x194/0x1f0 [<c01425a0>] file_read_actor+0x0/0xf0 [<c0162c7d>] do_sync_read+0xbd/0x110 [<c016bd7a>] open_namei+0xda/0x550 [<c0132370>] autoremove_wake_function+0x0/0x50 [<c0162d64>] vfs_read+0x94/0x170 [<c0163111>] sys_read+0x41/0x70 [<c0102eb8>] syscall_call+0x7/0xb ======================= Code: 3a f6 c2 01 75 3e 8b 1a 31 c0 39 34 9d f0 ed 75 c0 72 28 8d 04 5b 8d 4c 00 fa 8d 76 00 8d bc 27 00 00 00 00 89 f0 d3 e8 83 e0 3f <8b> 54 82 10 85 d2 74 1c 83 e9 06 4b 75 eb 89 d0 5b 5e c3 8d b6 EIP: [<c02eb417>] radix_tree_lookup+0x37/0x60 SS:ESP 0068:f2615d7c <1>BUG: unable to handle kernel paging request at virtual address 6dcecdd9 printing eip: c02eb417 *pde = 00000000 Oops: 0000 [#5] SMP Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss appletalk psnap llc ide_scsi generic nvidia(P) snd_hda_intel snd_hda_codec jmicron snd_pcm snd_timer snd snd_page_alloc CPU: 0 EIP: 0060:[<c02eb417>] Tainted: P VLI EFLAGS: 00210046 (2.6.20.7C2D6400,2x1GBRAM800,P965-ICH8R,Marv8056,1x40GB+3x320GBr5 #5) EIP is at radix_tree_lookup+0x37/0x60 eax: 00000000 ebx: 8b372010 ecx: 434ac05a edx: 6dcecdc9 esi: 00000000 edi: 00000000 ebp: f3ccd494 esp: f2629d7c ds: 007b es: 007b ss: 0068 Process smbd (pid: 3886, ti=f2628000 task=c2282550 task.ti=f2628000) Stack: 00000000 00000000 c01488c0 00000052 f3ccd4a4 00000000 00000001 00000000 f4a25380 f2629da0 f2629da0 f2629e3c f3ccd494 00000000 f4a25380 c0148add 00000004 f2629e3c 00000000 00000001 00000020 c0148d3b 00000004 f2629e3c Call Trace: [<c01488c0>] __do_page_cache_readahead+0x90/0x160 [<c0148add>] blockable_page_cache_readahead+0x4d/0xd0 [<c0148d3b>] page_cache_readahead+0x10b/0x1c0 [<c01424e2>] do_generic_mapping_read+0x482/0x540 [<c0142824>] generic_file_aio_read+0x194/0x1f0 [<c01425a0>] file_read_actor+0x0/0xf0 [<c0162c7d>] do_sync_read+0xbd/0x110 [<c016bd7a>] open_namei+0xda/0x550 [<c0132370>] autoremove_wake_function+0x0/0x50 [<c0162d64>] vfs_read+0x94/0x170 [<c0163111>] sys_read+0x41/0x70 [<c0102eb8>] syscall_call+0x7/0xb ======================= Code: 3a f6 c2 01 75 3e 8b 1a 31 c0 39 34 9d f0 ed 75 c0 72 28 8d 04 5b 8d 4c 00 fa 8d 76 00 8d bc 27 00 00 00 00 89 f0 d3 e8 83 e0 3f <8b> 54 82 10 85 d2 74 1c 83 e9 06 4b 75 eb 89 d0 5b 5e c3 8d b6 EIP: [<c02eb417>] radix_tree_lookup+0x37/0x60 SS:ESP 0068:f2629d7c <1>BUG: unable to handle kernel paging request at virtual address 6dcecdd9 printing eip: c02eb417 *pde = 00000000 Oops: 0000 [#6] SMP Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss appletalk psnap llc ide_scsi generic nvidia(P) snd_hda_intel snd_hda_codec jmicron snd_pcm snd_timer snd snd_page_alloc CPU: 0 EIP: 0060:[<c02eb417>] Tainted: P VLI EFLAGS: 00210046 (2.6.20.7C2D6400,2x1GBRAM800,P965-ICH8R,Marv8056,1x40GB+3x320GBr5 #5) EIP is at radix_tree_lookup+0x37/0x60 eax: 00000000 ebx: 8b372010 ecx: 434ac05a edx: 6dcecdc9 esi: 00000000 edi: 00000000 ebp: f3ccd494 esp: f2681d7c ds: 007b es: 007b ss: 0068 Process smbd (pid: 3916, ti=f2680000 task=f2657030 task.ti=f2680000) Stack: 00000000 00000000 c01488c0 00000052 f3ccd4a4 00000000 00000001 00000000 f7b36080 f2681da0 f2681da0 f2681e3c f3ccd494 00000000 f7b36080 c0148add 00000004 f2681e3c 00000000 00000001 00000020 c0148d3b 00000004 f2681e3c Call Trace: [<c01488c0>] __do_page_cache_readahead+0x90/0x160 [<c0148add>] blockable_page_cache_readahead+0x4d/0xd0 [<c0148d3b>] page_cache_readahead+0x10b/0x1c0 [<c01424e2>] do_generic_mapping_read+0x482/0x540 [<c0142824>] generic_file_aio_read+0x194/0x1f0 [<c01425a0>] file_read_actor+0x0/0xf0 [<c0162c7d>] do_sync_read+0xbd/0x110 [<c016bd7a>] open_namei+0xda/0x550 [<c0132370>] autoremove_wake_function+0x0/0x50 [<c0162d64>] vfs_read+0x94/0x170 [<c0163111>] sys_read+0x41/0x70 [<c0102eb8>] syscall_call+0x7/0xb ======================= Code: 3a f6 c2 01 75 3e 8b 1a 31 c0 39 34 9d f0 ed 75 c0 72 28 8d 04 5b 8d 4c 00 fa 8d 76 00 8d bc 27 00 00 00 00 89 f0 d3 e8 83 e0 3f <8b> 54 82 10 85 d2 74 1c 83 e9 06 4b 75 eb 89 d0 5b 5e c3 8d b6 EIP: [<c02eb417>] radix_tree_lookup+0x37/0x60 SS:ESP 0068:f2681d7c thank you very much for your time... what i am looking for is some directiong as to whom to ask about it... nass
On Wed, 2007-04-25 at 14:22 +0300, )\(@sS wrote:
hello everyone, i am really weirded out by some of the messages that appear on stdout from syslog and the kernel. i dunno where to turn in order to interpret the messages so i ask if you please take a look.. and perhaps direct me to someone. thank you in advance
im setting up a pc that i want to use as server. its characteristics are
you can analyze these results using ksymoops, and then you should probably post to LKML, or a distribution specific mailing list. The backtraces seem to be quite consistent, but the code as displayed seems to be bogus: $ objdump -b binary -m i386 --disassemble -D qwqw qwqw: file format binary Disassembly of section .data: 0000000000000000 <.data>: 0: 3a f6 cmp %dh,%dh 2: c2 01 75 ret $0x7501 5: 3e 8b 1a mov %ds:(%edx),%ebx 8: 31 c0 xor %eax,%eax a: 39 .byte 0x39 b: 34 .byte 0x34 -- Bazsi
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' thank you.. i am already trying to post into reiserfs mailing list. btw i forgot to note that i switched the system runlevel to 1 unmounted the /dev/sda1 and did a reiserfs --check on it.... it returned no errors... nass On 4/25/07, Balazs Scheidler <bazsi@balabit.hu> wrote:
On Wed, 2007-04-25 at 14:22 +0300, )\(@sS wrote:
hello everyone, i am really weirded out by some of the messages that appear on stdout from syslog and the kernel. i dunno where to turn in order to interpret the messages so i ask if you please take a look.. and perhaps direct me to someone. thank you in advance
im setting up a pc that i want to use as server. its characteristics are
you can analyze these results using ksymoops, and then you should probably post to LKML, or a distribution specific mailing list. The backtraces seem to be quite consistent, but the code as displayed seems to be bogus:
$ objdump -b binary -m i386 --disassemble -D qwqw
qwqw: file format binary
Disassembly of section .data:
0000000000000000 <.data>: 0: 3a f6 cmp %dh,%dh 2: c2 01 75 ret $0x7501 5: 3e 8b 1a mov %ds:(%edx),%ebx 8: 31 c0 xor %eax,%eax a: 39 .byte 0x39 b: 34 .byte 0x34
-- Bazsi
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
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
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).
Just a small addition: if the OP can reproduce the problem without the nvidia module being loaded (not just unloaded), then he can follow up the issue on LKML. BTW what filesystem is this, reiser? Regards, Sandor -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
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@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@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@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
participants (3)
-
)\(＠sS
-
Balazs Scheidler
-
Geller, Sandor (IT)