[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [suse-security] RAID5 on SuSE 9.0



NO, es una maquina con un motherboard Tyan! Pero el problema no es con el
ethernet, pues si la subo runlevel 1 y luego la cambio a runlevel 5 el raid5
en software NO trata de hacer el sync de los 4 disco y por lo tanto NO se
jangea! Pero entonces NO tengo el raid funcionando!!!

David

-----Original Message-----
From: Manuel Balderrábano [mailto:garibolo@xxxxxxxxxx] 
Sent: Tuesday, February 03, 2004 8:31 AM
To: David Soltero-Lugo
Subject: Re: [suse-security] RAID5 on SuSE 9.0

Hola, David.

(Asumo que hablas español.)

¿Se trata de un servidor IBM, por casualidad?

Tuve un priblema idéntico al tuyo, y al final era la forma en que la BIOS
manejaba el driver de la ethernet integrada en placa.

Lo solucioné instalando una ethernet PCI, y ahora todo va como la seda!

Un saludo.


----- Original Message ----- 
From: "David Soltero-Lugo" <david@xxxxxxxxxxxx>
To: <suse-security@xxxxxxxx>
Sent: Tuesday, February 03, 2004 10:14 AM
Subject: [suse-security] RAID5 on SuSE 9.0


>
>
> I am trying to setup a 9.0Pro machine using 4 scsi discs on a RAID5
> (software based) but I am having troubles with it. If I boot on runlevel 1
> the system does not crash, but if I boot over another runlevel, the system
> will freeze after a while with a Oops message, related to ipv6 driver,
> raid5.o, ssh, or other. Here are some of the Oops, This is a brand new
> installation with almost everything default!!!
>
> Thanks for any help you can give!
>
> David
>
>
############################################################################
> #
>
> Jan 15 22:27:39 linux kernel: md: md0: sync done.
> Jan 15 22:27:39 linux kernel: raid5: resync finished.
> Jan 15 22:47:40 linux kernel: Unable to handle kernel paging request at
> virtual address 000011e6
> Jan 15 22:47:40 linux kernel:  printing eip:
> Jan 15 22:47:40 linux kernel: c7c13ddc
> Jan 15 22:47:40 linux kernel: *pde = 00000000
> Jan 15 22:47:40 linux kernel: Oops: 0002 2.4.21-166-athlon #1 Thu Dec 18
> 18:24:05 UTC 2003
> Jan 15 22:47:40 linux kernel: CPU:    0
> Jan 15 22:47:40 linux kernel: EIP:
> 0010:[ipv6:mipv6_functions_R874e5304+51758556/804608079]    Tainted: P
> Jan 15 22:47:40 linux kernel: EIP:    0010:[<c7c13ddc>]    Tainted: P
> Jan 15 22:47:40 linux kernel: EFLAGS: 00010296
> Jan 15 22:47:40 linux kernel: eax: 00000000   ebx: 08073fc0   ecx:
00000000
> edx: 08073fd0
> Jan 15 22:47:40 linux kernel: esi: 00000030   edi: c7c13eba   ebp:
c7c13fa4
> esp: c7c13dc4
> Jan 15 22:47:40 linux kernel: ds: 0018   es: 0018   ss: 0018
> Jan 15 22:47:40 linux kernel: Process man (pid: 3459, stackpage=c7c13000)
> Jan 15 22:47:40 linux kernel: Stack: 08073fc8 c7c13ddc 00000008 08073fd4
> 00033f8d 00000000 11e68900 00000000
> Jan 15 22:47:40 linux kernel:        00000028 00000000 c8765848 c7c13f24
> 00000016 c875cb26 c7c13eba c875c3f0
> Jan 15 22:47:40 linux kernel:        c328e470 c7c13fa4 c7c13ea4 00000016
> 11e68900 00000000 0002c39a 00000000
> Jan 15 22:47:40 linux kernel: Call Trace:
>
[keybdev:__insmod_keybdev_O/lib/modules/2.4.21-166-athlon/kernel/dri+4265276
> 528/96] (216) [cached_lookup+24/112] (120) [vfs_readdir+169/176] (12)
> Jan 15 22:47:40 linux kernel: Call Trace:         [<c328e470>] (216)
> [<c0154798>] (120) [<c0159369>] (12)
> Jan 15 22:47:40 linux kernel:   [filldir64+0/288] (20)
> [sys_getdents64+91/181] (08) [filldir64+0/288] (32) [sys_fcntl64+93/192]
> (36)
> Jan 15 22:47:40 linux kernel:   [<c01599f0>] (20) [<c0159b6b>] (08)
> [<c01599f0>] (32) [<c0158acd>] (36)
> Jan 15 22:47:40 linux kernel:   [system_call+51/56] (60)
>
############################################################################
>
>
> -- 
> Check the headers for your unsubscription address
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at http://lists.suse.com
> Please read the FAQs: suse-linux-e-faq@xxxxxxxx
>
>
>
>
> -- 
> Check the headers for your unsubscription address
> For additional commands, e-mail: suse-security-help@xxxxxxxx
> Security-related bug reports go to security@xxxxxxx, not here
>



--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here