Tive problema semelhante...

Esse servidor � do tipo grife (Itautec, Dell ..) ou uma m�quina comum que
est� sendo utilizada para este fim?

Vou explicar o motivo da minha pergunta:

Muitas empresas compras m�quinas parrudas, mas que n�o foram homologadas, ou
seja n�o foram suficientemente testadas...
As vezes o pessoal que vende esses m�quinas toma como base de bom
funcionamento um simples instala��o de Windows XP (Podem xingar a vontade
:-(  )

Nunca instalaram um N.O.S de verdade, simulando acessos, CPU streess, Memory
Streess etc...
Para voc� ter uma id�ia, troquei um desses servidores por um equipamento que
foi designado como desktop, mas que pela proced�ncia digo que foi
homologado.
Resultado um "uptime" de mais de 60 dias desde a troca, sem erros,
travamentos...

Seu eu tivesse que apostar uma caixa de Boehmia ou uma camisa do Tux :-) eu
diria que � problema de mem�ria.

Isso n�o que dizer que a mem�ria est� defeituosa,  por exemplo, j� tive
casos de uma mem�ria de de FSB de 400 Mhz, com um processador de FSB de
266Mhz , simplesmente travar o sistema, embora que em teoria deveria
funcionar (teoria, pois muitos fabricantes n�o recomendam esse tipo de
mistura).

Bem se fosse eu come�aria analizando o hardware:
FSB Processador
FSB Mem�ria
Ver hist�rico da placa m�e.

Abra�os

Hever

----- Original Message -----
From: "Bruno" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, April 14, 2005 10:55 PM
Subject: (linux-br)Kernel BUG


> Prezados,
>
> possuo um servidor que tinha o Red Hat 9 instalado rodando proxy e named.
> Eventualmente este
> servidor travava. Acabei por instalar o Mandrake 10 neste servidor e a
> instabilidade diminuiu, no entanto
> eventualmente o mesmo trava, mas em algumas ocasi�es surgem mensagens de
> "kernel BUG", que ora matam
> o squid (mas ele volta automaticamente) e ora matam o named (que n�o volta
> automaticamente).
> Quando o servidor trava completamente, nada � logado.
>
> Envio abaixo a transcri��o das mensagens obtidas.
>
> Ser� um problema de hardware? Este server possui duas placas de rede 3Com
> 905 e um onboard Sis que n�o � utilizada.
>
> Mais uma vez grato,
>
> Bruno
>
>
> ==================================================================
>
>
> Apr 14 13:40:37 server kernel: ------------[ cut here ]------------
> Apr 14 13:40:37 server kernel: kernel BUG at net/core/dev.c:1207!
> Apr 14 13:40:37 server kernel: invalid operand: 0000 [#2]
> Apr 14 13:40:37 server kernel: CPU: 0
> Apr 14 13:40:37 server kernel: EIP: 0060:[skb_checksum_help+27/144] Not
> tainted VLI
> Apr 14 13:40:37 server kernel: EIP: 0060:[<c0260b5b>] Not tainted VLI
> Apr 14 13:40:37 server kernel: EFLAGS: 00010212
> Apr 14 13:40:37 server kernel: EIP is at skb_checksum_help+0x1b/0x90
> Apr 14 13:40:37 server kernel: eax: 00000046 ebx: c6ad8ec0 ecx: 03587e70
> edx: cb24a7c0
> Apr 14 13:40:37 server kernel: esi: c3618010 edi: cb9d8000 ebp: cbc31be4
> esp: cbc31bd8
> Apr 14 13:40:37 server kernel: ds: 007b es: 007b ss: 0068
> Apr 14 13:40:37 server kernel: Process named (pid: 1029,
threadinfo=cbc30000
> task=cc0c9340)
> Apr 14 13:40:37 server kernel: Stack: c3618010 00000003 cb9d8000 cbc31c04
> c0269f41 c6ad8ec0 00000000 cb24a7c0
> Apr 14 13:40:37 server kernel: c3618010 00000040 c6ad8ec0 cbc31c48
c027c3bd
> 00000002 00000003 c6ad8ec0
> Apr 14 13:40:37 server kernel: 00000000 cb9d8000 c027c810 80000000
00000014
> 00000040 c6b9fe80 00000000
> Apr 14 13:40:37 server kernel: Call Trace:
> Apr 14 13:40:37 server kernel: [nf_hook_slow+161/240]
nf_hook_slow+0xa1/0xf0
> Apr 14 13:40:37 server kernel: [<c0269f41>] nf_hook_slow+0xa1/0xf0
> Apr 14 13:40:37 server kernel: [ip_push_pending_frames+845/1040]
> ip_push_pending_frames+0x34d/0x410
> Apr 14 13:40:37 server kernel: [<c027c3bd>]
> ip_push_pending_frames+0x34d/0x410
> Apr 14 13:40:37 server kernel: [dst_output+0/48] dst_output+0x0/0x30
> Apr 14 13:40:37 server kernel: [<c027c810>] dst_output+0x0/0x30
> Apr 14 13:40:37 server kernel: [udp_push_pending_frames+417/624]
> udp_push_pending_frames+0x1a1/0x270
> Apr 14 13:40:37 server kernel: [<c02982c1>]
> udp_push_pending_frames+0x1a1/0x270
> Apr 14 13:40:37 server kernel: [udp_sendmsg+1424/1632]
> udp_sendmsg+0x590/0x660
> Apr 14 13:40:37 server kernel: [<c0298970>] udp_sendmsg+0x590/0x660
> Apr 14 13:40:37 server kernel: [inet_sendmsg+58/80] inet_sendmsg+0x3a/0x50
> Apr 14 13:40:37 server kernel: [<c029f9ca>] inet_sendmsg+0x3a/0x50
> Apr 14 13:40:37 server kernel: [sock_sendmsg+129/176]
sock_sendmsg+0x81/0xb0
> Apr 14 13:40:37 server kernel: [<c0259491>] sock_sendmsg+0x81/0xb0
> Apr 14 13:40:37 server kernel: [sock_recvmsg+136/192]
sock_recvmsg+0x88/0xc0
> Apr 14 13:40:37 server kernel: [<c0259548>] sock_recvmsg+0x88/0xc0
> Apr 14 13:40:37 server kernel: [__wake_up_common+38/80]
> __wake_up_common+0x26/0x50
> Apr 14 13:40:37 server kernel: [<c011ff06>] __wake_up_common+0x26/0x50
> Apr 14 13:40:37 server kernel: [__wake_up+17/32] __wake_up+0x11/0x20
> Apr 14 13:40:37 server kernel: [<c011ff41>] __wake_up+0x11/0x20
> Apr 14 13:40:37 server kernel: [move_addr_to_kernel+66/128]
> move_addr_to_kernel+0x42/0x80
> Apr 14 13:40:37 server kernel: [<c0258fa2>] move_addr_to_kernel+0x42/0x80
> Apr 14 13:40:37 server kernel: [verify_iovec+81/208]
verify_iovec+0x51/0xd0
> Apr 14 13:40:37 server kernel: [<c025e0c1>] verify_iovec+0x51/0xd0
> Apr 14 13:40:37 server kernel: [sys_sendmsg+458/720]
sys_sendmsg+0x1ca/0x2d0
> Apr 14 13:40:37 server kernel: [<c025a96a>] sys_sendmsg+0x1ca/0x2d0
> Apr 14 13:40:37 server kernel: [recalc_task_prio+156/512]
> recalc_task_prio+0x9c/0x200
> Apr 14 13:40:37 server kernel: [<c011ed3c>] recalc_task_prio+0x9c/0x200
> Apr 14 13:40:37 server kernel: [schedule_timeout+160/176]
> schedule_timeout+0xa0/0xb0
> Apr 14 13:40:37 server kernel: [<c012a3b0>] schedule_timeout+0xa0/0xb0
> Apr 14 13:40:37 server kernel: [queue_me+89/112] queue_me+0x59/0x70
> Apr 14 13:40:37 server kernel: [<c01336d9>] queue_me+0x59/0x70
> Apr 14 13:40:37 server kernel: [try_to_wake_up+149/320]
> try_to_wake_up+0x95/0x140
> Apr 14 13:40:37 server kernel: [<c011ef35>] try_to_wake_up+0x95/0x140
> Apr 14 13:40:37 server kernel: [__wake_up_common+38/80]
> __wake_up_common+0x26/0x50
> Apr 14 13:40:37 server kernel: [<c011ff06>] __wake_up_common+0x26/0x50
> Apr 14 13:40:37 server kernel: [__wake_up+17/32] __wake_up+0x11/0x20
> Apr 14 13:40:37 server kernel: [<c011ff41>] __wake_up+0x11/0x20
> Apr 14 13:40:37 server kernel: [wake_futex+44/112] wake_futex+0x2c/0x70
> Apr 14 13:40:37 server kernel: [<c013341c>] wake_futex+0x2c/0x70
> Apr 14 13:40:37 server kernel: [futex_wake+122/176] futex_wake+0x7a/0xb0
> Apr 14 13:40:37 server kernel: [<c01334da>] futex_wake+0x7a/0xb0
> Apr 14 13:40:37 server kernel: [sys_socketcall+160/480]
> sys_socketcall+0xa0/0x1e0
> Apr 14 13:40:37 server kernel: [<c025ad20>] sys_socketcall+0xa0/0x1e0
> Apr 14 13:40:37 server kernel: [sysenter_past_esp+82/121]
> sysenter_past_esp+0x52/0x79
> Apr 14 13:40:37 server kernel: [<c010afa9>] sysenter_past_esp+0x52/0x79
> Apr 14 13:40:37 server kernel:
> Apr 14 13:40:37 server kernel: Code: a8 eb 0d 90 90 90 90 90 90 90 90 90
90
> 90 90 90 55 89 e5 57 56 53 8b 5d 08 8b 4b 20 8b b3 a0 00 00 00 29 f1 8b 43
> 64 39 c1 7e 08 <0f> 0b b7 04 64 ac 30 c0 29 c8 6a 00 50 51 53 e8 01 cf ff
ff
> 8b
>
>
============================================================================
==============================
>
> Apr 14 21:09:43 server kernel: invalid operand: 0000 [#3]
> Apr 14 21:09:43 server kernel: CPU: 0
> Apr 14 21:09:43 server squid[1293]: Squid Parent: child process 20183
exited
> due to signal 11
> Apr 14 21:09:43 server kernel: EIP:
> 0060:[__crc_serial8250_resume_port+1601939/3500414] Not tainted VLI
> Apr 14 21:09:43 server kernel: EIP: 0060:[<c738fdcd>] Not tainted VLI
> Apr 14 21:09:43 server kernel: EFLAGS: 00010203
> Apr 14 21:09:43 server kernel: EIP is at 0xc738fdcd
> Apr 14 21:09:43 server kernel: eax: 1277472a ebx: 28e104d5 ecx: fe993641
> edx: c738fdb0
> Apr 14 21:09:43 server kernel: esi: c04134e1 edi: 00000291 ebp: 00005000
> esp: c738fd9c
> Apr 14 21:09:43 server kernel: ds: 007b es: 007b ss: 0068
> Apr 14 21:09:43 server kernel: Process squid (pid: 20183,
> threadinfo=c738e000 task=cb0e0140)
> Apr 14 21:09:43 server kernel: Stack: c01eee83 c738fdb0 c04134e8 425f0647
> 000b50d7 49d4b3c8 fe993641 02915000
> Apr 14 21:09:43 server kernel: c3a08027 c980f320 49d4b3c8 c2d425cc
c738feac
> c029058e 49d4b3c8 fe993641
> Apr 14 21:09:43 server kernel: 00000291 00005000 fe993641 50002238
00000000
> fe993641 c2d4266c c2d425cc
> Apr 14 21:09:43 server kernel: Call Trace:
> Apr 14 21:09:43 server kernel: [secure_tcp_sequence_number+131/192]
> secure_tcp_sequence_number+0x83/0xc0
> Apr 14 21:09:43 server kernel: [<c01eee83>]
> secure_tcp_sequence_number+0x83/0xc0
> Apr 14 21:09:43 server kernel: [tcp_v4_connect+1294/1584]
> tcp_v4_connect+0x50e/0x630
> Apr 14 21:09:43 server kernel: [<c029058e>] tcp_v4_connect+0x50e/0x630
> Apr 14 21:09:43 server kernel: [inet_stream_connect+279/432]
> inet_stream_connect+0x117/0x1b0
> Apr 14 21:09:43 server kernel: [<c029f767>]
inet_stream_connect+0x117/0x1b0
> Apr 14 21:09:43 server kernel: [sys_connect+95/128] sys_connect+0x5f/0x80
> Apr 14 21:09:43 server kernel: [<c025a2ff>] sys_connect+0x5f/0x80
> Apr 14 21:09:43 server kernel: [sprintf+20/32] sprintf+0x14/0x20
> Apr 14 21:09:43 server kernel: [<c01c43e4>] sprintf+0x14/0x20
> Apr 14 21:09:43 server kernel: [tcp_setsockopt+136/1648]
> tcp_setsockopt+0x88/0x670
> Apr 14 21:09:43 server kernel: [<c0283008>] tcp_setsockopt+0x88/0x670
> Apr 14 21:09:43 server kernel: [inet_setsockopt+35/48]
> inet_setsockopt+0x23/0x30
> Apr 14 21:09:43 server kernel: [<c029ef53>] inet_setsockopt+0x23/0x30
> Apr 14 21:09:43 server kernel: [sys_setsockopt+72/128]
> sys_setsockopt+0x48/0x80
> Apr 14 21:09:43 server kernel: [<c025a6a8>] sys_setsockopt+0x48/0x80
> Apr 14 21:09:43 server kernel: [sys_setsockopt+86/128]
> sys_setsockopt+0x56/0x80
> Apr 14 21:09:43 server kernel: [<c025a6b6>] sys_setsockopt+0x56/0x80
> Apr 14 21:09:43 server kernel: [sys_socketcall+402/480]
> sys_socketcall+0x192/0x1e0
> Apr 14 21:09:43 server kernel: [<c025ae12>] sys_socketcall+0x192/0x1e0
> Apr 14 21:09:43 server kernel: [sys_fcntl64+66/128] sys_fcntl64+0x42/0x80
> Apr 14 21:09:43 server kernel: [<c01633d2>] sys_fcntl64+0x42/0x80
> Apr 14 21:09:43 server kernel: [sysenter_past_esp+82/121]
> sysenter_past_esp+0x52/0x79
> Apr 14 21:09:43 server kernel: [<c010afa9>] sysenter_past_esp+0x52/0x79
> Apr 14 21:09:43 server kernel:
> Apr 14 21:09:43 server kernel: Code: 38 c7 e8 34 41 c0 47 06 5f 42 d7 50
0b
> 00 c8 b3 d4 49 41 36 99 fe 00 50 91 02 27 80 a0 c3 20 f3 80 c9 c8 b3 d4 49
> cc 25 d4 c2 ac <fe> 38 c7 8e 05 29 c0 c8 b3 d4 49 41 36 99 fe 91 02 00 00
00
> 50
>
> --------------------------------------------------------------------------
-
> Esta lista � patrocinada pela Conectiva S.A. Visite
http://www.conectiva.com.br
>
> Arquivo: http://bazar2.conectiva.com.br/mailman/listinfo/linux-br
> Regras de utiliza��o da lista: http://linux-br.conectiva.com.br
> FAQ: http://www.zago.eti.br/menu.html

---------------------------------------------------------------------------
Esta lista � patrocinada pela Conectiva S.A. Visite http://www.conectiva.com.br

Arquivo: http://bazar2.conectiva.com.br/mailman/listinfo/linux-br
Regras de utiliza��o da lista: http://linux-br.conectiva.com.br
FAQ: http://www.zago.eti.br/menu.html

Responder a