Pessoal, estou com o seguinte problema:
Estamos com o kernels do Openmosix (2.4.21-openmosix1smp &
2.4.22-openmosix1) instalados, sendo q a primeiro micro � um xeon 2.8 duplo
processado e o segundo � um petium III 1.8 monoprocessado com o arquivo
/etc/openmosix.map no primeiro(master) e no segundo(cluster1) n� configurado
da seguinte forma:
# Static openMosix configuration
# ==============================
#
# Each line in this file should contain 3 fields, statically mapping
# IP addresses to openMosix node-numbers:
#
# 1) The first openMosix node-number in this range.
# 2) The IP address of the above node (or node-name from /etc/hosts).
# 3) The number of nodes in this range.
#
# Note: If you don't create a valid IP <-> node-number mapping, the
# autodiscovery daemon will be started, automatically assigning
# node-numbers to all visible openMosix machines.
#
# Example: 10 machines with IP addresses 192.168.1.50 - 192.168.1.59
# which will have openMosix node-numbers 1-10:
#
# 1 192.168.1.50 10
#
# MOSIX-# IP number-of-nodes
# ============================
1 192.168.10.1 2
As maquinas se encontram e consigo configurar o samba para enxergar o micro
cluster1 atrav�s do master na minha rede, o problema � que sempre que gero
um extress no trafego, ou seja, inicio uma c�pia muito pesada de dados o
micro de exibe no cluster1 a seguinte mensagem na tela em loop:
Code: 0f 0b 93 00 3a 70 2f c0 90 eb fe 90 90 90 90 90 90 90 90 90
kernel BUG in header file at line 252
n header file at line 252
kernel BUG at panic.c:147!
invalid operand: 0000
CPU: 1
EIP: 0010:[<c0129fe7>] Not tainted
EFLAGS: 00010282
eax: 00000026 ebx: f5083f74 ecx: 00000001 edx: 01000000
esi: f4ed4000 edi: f4ed4000 ebp: 00000449 esp: f5083f20
ds: 0018 es: 0018 ss: 0018
Process smbd (pid: 2064, stackpage=f5083000)
Stack: c02f62c0 000000fc c0166ace 000000fc f4ed4000 f5083f74 f4ed4000
c0166917
f4ed4000 f5083f74 f4ed4000 c0166cb0 08205ac0 f500b6b4 f5082000
f5083f74
bffff230 bfffed68 c0161b3e 00000000 f50dca40 c1e0fd80 c1e0fd80
00000000fStack: c02f62c0 000000fc c0166ace 000000fc f4f02000 f5083f74
f4f02000 c0166917
Stack: c02f62c0 000000fc c0166ace 000000fc f4f02000 f5083f74 f4f02000
c0166917
f4f02000 f5083f74 f4f02000 c0166cb0 08205ac0 f50ad294 f5082000
f5083f74
bffff230 bfffed68 c0161b3e 00000000 f50dc7c0 c1e0fd80 c1e0fd80
00000000
Call Trace: [<c0166ace>] [<c0166917>] [<c0166cb0>] [<c0161b3e>]
[<c01d7170>]
[<c010c828>]
Code: 0f 0b 93 00 3a 70 2f c0 90 eb fe 90 90 90 90 90 90 90 90 90
kernel BUG in header file at line 252
n header file at line 252!
kernel BUG at panic.c:147!
invalid operand: 0000
CPU: 1
:EIP: 0010:[<c0129fe7>] Not tainted
EIP: 0010:[<c0129fe7>] Not tainted
Stack: c02f62c0 000000fc c0166ace 000000fc f4f02000 f5083f74 f4f02000
c0166917
Stack: c02f62c0 000000fc c0166ace 000000fc f4f02000 f5083f74 f4f02000
c0166917
esp:
f4f02000 c0166917
Stack: c02f62c0 000000fc c0166ace 000000fc f4f02000 f5083f74 f4f02000
c0166917
Stack: c02f62c0 000000fc c0166ace 000000fc f4f02000 f5083f74 f4f02000
c0166917
Stack: c02f62c0 000000fc c0166ace 000000fc f4f02000 f5083f74
f4f02000c0166917
f4f02000 f5083f74 f4f02000 c0166cb0 08205ac0 f50ad294 f5082000
f5083f74
bffff230 bfffed68 c0161b3e 00000000 f50dc7c0 c1e0fd80 c1e0fd80
00000000
Call Trace: [<c0166ace>] [<c0166917>] [<c0166cb0>] [<c0161b3e>]
[<c01d7170>]
[<c010c828>]
Algu�m tem alguma id�ia do que pode estar ocorrendo?
Valeu a todos
Vitor
---------------------------------------------------------------------------
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
