RE: [suse-security] RAID5 on SuSE 9.0
Already 4 hours testing with out errors!!! It has to be the raid!! Any other thoughts? David -----Original Message----- From: Michael Wirth [mailto:micha@linux-install.de] Sent: Tuesday, February 03, 2004 8:39 AM To: David Soltero-Lugo Subject: Re: [suse-security] RAID5 on SuSE 9.0 David,
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) ^^^^^^^^^^^ This is almost certainly not a kernel bug, but a dirty RAM component. Try running memtest86 overnight. Then get a printout and contact your dealer for new RAMs.
Process man should never cause a kernel Oops... Greetings and good luck............Michael --- --- Michael Wirth linux-install Mühlehof 20 Phone: +49-7073-802 72119 Ammerbuch Fax: +49-7073-500282 wirth@linux-install.de Web: http://www.linux-install.de/
Did you set up the raid through Yast's partition thing or did you do it
manually? I've been running a scsi raid5 setup for months on SuSE 9.0 without
any issues.
Quoting David Soltero-Lugo
Already 4 hours testing with out errors!!! It has to be the raid!! Any other thoughts?
David
-----Original Message----- From: Michael Wirth [mailto:micha@linux-install.de] Sent: Tuesday, February 03, 2004 8:39 AM To: David Soltero-Lugo Subject: Re: [suse-security] RAID5 on SuSE 9.0
David,
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) ^^^^^^^^^^^ This is almost certainly not a kernel bug, but a dirty RAM component. Try running memtest86 overnight. Then get a printout and contact your dealer for new RAMs.
Process man should never cause a kernel Oops...
Greetings and good luck............Michael
--- --- Michael Wirth linux-install Mühlehof 20 Phone: +49-7073-802 72119 Ammerbuch Fax: +49-7073-500282 wirth@linux-install.de Web: http://www.linux-install.de/
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
Thru yast!
-----Original Message-----
From: suse@rio.vg [mailto:suse@rio.vg]
Sent: Tuesday, February 03, 2004 2:13 PM
To: suse-security@suse.com
Subject: RE: [suse-security] RAID5 on SuSE 9.0
Did you set up the raid through Yast's partition thing or did you do it
manually? I've been running a scsi raid5 setup for months on SuSE 9.0
without
any issues.
Quoting David Soltero-Lugo
Already 4 hours testing with out errors!!! It has to be the raid!! Any
other
thoughts?
David
-----Original Message----- From: Michael Wirth [mailto:micha@linux-install.de] Sent: Tuesday, February 03, 2004 8:39 AM To: David Soltero-Lugo Subject: Re: [suse-security] RAID5 on SuSE 9.0
David,
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) ^^^^^^^^^^^ This is almost certainly not a kernel bug, but a dirty RAM component. Try running memtest86 overnight. Then get a printout and contact your dealer for new RAMs.
Process man should never cause a kernel Oops...
Greetings and good luck............Michael
--- --- Michael Wirth linux-install Mühlehof 20 Phone: +49-7073-802 72119 Ammerbuch Fax: +49-7073-500282 wirth@linux-install.de Web: http://www.linux-install.de/
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
/ 2004-02-03 13:45:37 -0400 \ David Soltero-Lugo:
Already 4 hours testing with out errors!!! It has to be the raid!! Any other thoughts?
David
I once saw a buggy southbrige corrupting Memory randomly with DMA... Only one bit once in a while, every transfered some 100 MB. This cause very obscure behaviour, including Oopses. If you are able to run with DMA disabled, and the error no longer occurs, I'd say it is something in that direction. Lars Ellenberg
participants (3)
-
David Soltero-Lugo
-
Lars Ellenberg
-
suse@rio.vg