Erro no messages

1. Erro no messages

Igor Fabiano
igois

(usa Slackware)

Enviado em 13/04/2011 - 10:46h

O que significa isso? No momento do erro minha rede toda parou!!


Apr 11 11:33:17 megatron kernel: [277245.162760] Tx Queue <0>
Apr 11 11:33:17 megatron kernel: [277245.162761] TDH <46>
Apr 11 11:33:17 megatron kernel: [277245.162762] TDT <46>
Apr 11 11:33:17 megatron kernel: [277245.162764] next_to_use <46>
Apr 11 11:33:17 megatron kernel: [277245.162765] next_to_clean <e1>
Apr 11 11:33:17 megatron kernel: [277245.162766] buffer_info[next_to_clean]
Apr 11 11:33:17 megatron kernel: [277245.162767] time_stamp <104105ddd>
Apr 11 11:33:17 megatron kernel: [277245.162768] next_to_watch <e4>
Apr 11 11:33:17 megatron kernel: [277245.162769] jiffies <104106203>
Apr 11 11:33:17 megatron kernel: [277245.162770] next_to_watch.status <1>
Apr 12 06:25:02 megatron kernel: imklog 3.18.6, log source = /proc/kmsg started.

Apr 12 08:32:16 megatron kernel: [354731.444486] Tx Queue <0>
Apr 12 08:32:16 megatron kernel: [354731.444486] TDH <64>
Apr 12 08:32:16 megatron kernel: [354731.444486] TDT <64>
Apr 12 08:32:16 megatron kernel: [354731.444486] next_to_use <64>
Apr 12 08:32:16 megatron kernel: [354731.444486] next_to_clean <7>
Apr 12 08:32:16 megatron kernel: [354731.444486] buffer_info[next_to_clean]
Apr 12 08:32:16 megatron kernel: [354731.444486] time_stamp <10530895e>
Apr 12 08:32:16 megatron kernel: [354731.444486] next_to_watch <9>
Apr 12 08:32:16 megatron kernel: [354731.444486] jiffies <105308ac9>
Apr 12 08:32:16 megatron kernel: [354731.444486] next_to_watch.status <1>
Apr 12 14:32:19 megatron kernel: [378645.245775] Tx Queue <0>
Apr 12 14:32:19 megatron kernel: [378645.245775] TDH <72>
Apr 12 14:32:19 megatron kernel: [378645.245775] TDT <72>
Apr 12 14:32:19 megatron kernel: [378645.245775] next_to_use <72>
Apr 12 14:32:19 megatron kernel: [378645.245775] next_to_clean <f4>
Apr 12 14:32:19 megatron kernel: [378645.245775] buffer_info[next_to_clean]
Apr 12 14:32:19 megatron kernel: [378645.245775] time_stamp <10582f238>
Apr 12 14:32:19 megatron kernel: [378645.245775] next_to_watch <f4>
Apr 12 14:32:19 megatron kernel: [378645.245775] jiffies <10582f363>
Apr 12 14:32:19 megatron kernel: [378645.245775] next_to_watch.status <1>
Apr 13 06:25:02 megatron kernel: imklog 3.18.6, log source = /proc/kmsg started.

Apr 13 09:35:58 megatron kernel: [448467.905581] Tx Queue <0>
Apr 13 09:35:58 megatron kernel: [448467.905583] TDH <be>
Apr 13 09:35:58 megatron kernel: [448467.905584] TDT <be>
Apr 13 09:35:58 megatron kernel: [448467.905585] next_to_use <be>
Apr 13 09:35:58 megatron kernel: [448467.905586] next_to_clean <46>
Apr 13 09:35:58 megatron kernel: [448467.905587] buffer_info[next_to_clean]
Apr 13 09:35:58 megatron kernel: [448467.905589] time_stamp <10688b416>
Apr 13 09:35:58 megatron kernel: [448467.905590] next_to_watch <46>
Apr 13 09:35:58 megatron kernel: [448467.905591] jiffies <10688b6d2>
Apr 13 09:35:58 megatron kernel: [448467.905592] next_to_watch.status <1>
Apr 13 10:18:38 megatron kernel: [451242.814584] Modules linked in: ipv6 loop snd_pcm parport_pc snd_timer parport snd soundcore pcspkr snd_page_alloc serio_raw psmouse container ac button shpchp pci_hotplug i2c_piix4 i2c_core intel_agp evdev ext3 jbd mbcache ide_cd_mod cdrom ata_generic sd_mod libata dock ide_pci_generic floppy mptspi mptscsih mptbase e1000 scsi_transport_spi scsi_mod piix ide_core thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] Apr 13 10:18:38 megatron kernel: [451242.814584] CPU 0:
Apr 13 10:18:38 megatron kernel: [451242.814584] Modules linked in: ipv6 loop snd_pcm parport_pc snd_timer parport snd soundcore pcspkr snd_page_alloc serio_raw psmouse container ac button shpchp pci_hotplug i2c_piix4 i2c_core intel_agp evdev ext3 jbd mbcache ide_cd_mod cdrom ata_generic sd_mod libata dock ide_pci_generic floppy mptspi mptscsih mptbase e1000 scsi_transport_spi scsi_mod piix ide_core thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] Apr 13 10:18:38 megatron kernel: [451242.814584] Pid: 12268, comm: squid3 Not tainted 2.6.26-2-amd64 #1 Apr 13 10:18:38 megatron kernel: [451242.814584] RIP: 0010:[<ffffffff803b4438>] [<ffffffff803b4438>] sock_wmalloc+0x0/0x54 Apr 13 10:18:38 megatron kernel: [451242.814584] RSP: 0018:ffffffff805e4da8 EFLAGS: 00010282 Apr 13 10:18:38 megatron kernel: [451242.814584] RAX: ffff810190d69800 RBX: ffff810187863440 RCX: 0000000000000020 Apr 13 10:18:38 megatron kernel: [451242.814584] RDX: 0000000000000001 RSI: 000000000000013f RDI: ffff810175b910c0 Apr 13 10:18:38 megatron kernel: [451242.814584] RBP: ffffffff805e4d20 R08: ffffffff8024ac66 R09: 0000000000000000 Apr 13 10:18:38 megatron kernel: [451242.814584] R10: ffff810080a5e000 R11: ffffffff802f377f R12: ffffffff8020cd02 Apr 13 10:18:38 megatron kernel: [451242.814584] R13: ffffffff805e4d20 R14: 00000000ffffffff R15: 0001916804793c6e Apr 13 10:18:38 megatron kernel: [451242.814584] FS: 00007fad0ace56f0(0000) GS:ffffffff8053d000(0000) knlGS:0000000000000000 Apr 13 10:18:38 megatron kernel: [451242.814584] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 13 10:18:38 megatron kernel: [451242.814584] CR2: 000000006d3a2930 CR3: 000000017346d000 CR4: 00000000000006e0 Apr 13 10:18:38 megatron kernel: [451242.814584] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 13 10:18:38 megatron kernel: [451242.814584] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Apr 13 10:18:38 megatron kernel: [451242.814584] Apr 13 10:18:38 megatron kernel: [451242.814584] Call Trace:
Apr 13 10:18:38 megatron kernel: [451242.814584] <IRQ> [<ffffffff803f04d0>] ? tcp_make_synack+0x2b/0x30a Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803f251b>] ? __tcp_v4_send_synack+0x38/0xc9 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803e2d03>] ? inet_csk_reqsk_queue_prune+0x10c/0x1ec
Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803f135b>] ? tcp_keepalive_timer+0x0/0x1c8 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803f139a>] ? tcp_keepalive_timer+0x3f/0x1c8 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803f135b>] ? tcp_keepalive_timer+0x0/0x1c8 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8023ca01>] ? run_timer_softirq+0x16a/0x1e2 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff802393cd>] ? __do_softirq+0x5c/0xd1 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8020d2dc>] ? call_softirq+0x1c/0x28 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8020f3e8>] ? do_softirq+0x3c/0x81 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8023932b>] ? irq_exit+0x3f/0x85 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8021aaab>] ? smp_apic_timer_interrupt+0x8c/0xa4
Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8020cd02>] ? apic_timer_interrupt+0x72/0x80 Apr 13 10:18:38 megatron kernel: [451242.814584] <EOI> [<ffffffff80320120>] ? copy_user_generic_string+0x30/0x40
Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803b7be0>] ? memcpy_toiovec+0x36/0x66 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803b8025>] ? skb_copy_datagram_iovec+0x49/0x1eb
Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803e64c8>] ? tcp_recvmsg+0x628/0xb06 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803b2173>] ? sock_common_recvmsg+0x30/0x45 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff803b01fa>] ? sock_aio_read+0x104/0x11c Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8029b103>] ? do_sync_read+0xc9/0x10c Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff802461d1>] ? autoremove_wake_function+0x0/0x2e Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff802463e1>] ? add_wait_queue+0x15/0x44 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8029b907>] ? vfs_read+0xbd/0x152 Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8029bcd5>] ? sys_read+0x45/0x6e Apr 13 10:18:38 megatron kernel: [451242.814584] [<ffffffff8020beda>] ? system_call_after_swapgs+0x8a/0x8f
Apr 13 10:18:38 megatron kernel: [451242.814584]



  


2. Re: Erro no messages

Renato Carneiro Pacheco
renato_pacheco

(usa Debian)

Enviado em 13/04/2011 - 11:02h

Rolou um buffer overflow ae no seu kernel na hora d tratar um determinado pacote. Veja se isso acontece com frequência pq vc pode estar sendo vítima d algum ataque ou bug do sistema. Tente atualizar o sistema (caso possua atualização) e procure saber se alguém teve o msm problema...






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts