WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] more on crash...

To: James Harper <JamesH@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] more on crash...
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 19 Jul 2004 14:07:58 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 19 Jul 2004 14:10:05 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Mon, 19 Jul 2004 22:14:32 +1000." <5F5896A5-C248-4EAF-9BA1-69558CCA7415@mimectl>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Can you get it to crash with 'nosmp' and just one other domain (which
obviously will have to share cpu0 with dom0)? Maybe it's also worth
seeing whether having dom1 as 2.4.26 or 2.6.7 makes a difference.

 -- Keir

> okay I think I can reliably make it crash / corrupt. the server is an smp 
> 550mhz p3 xeon with 768mb memory. dom0 has 128mb of memory with no swap. dom1 
> is a backup mail server which might accept an email every few minutes. It 
> also does spam checking. dom2 is just a base debian install just sitting idle.
> 
> I have two identical 300mb files of random data (file3 & file4), and a script 
> that repeatedly compares them (call it 'compare'):
> 
> #!/bin/sh
> while [ 1 = 1 ]
> do
>  diff file3 file4 && echo okay
>  cat file3 >/dev/null
> done
> 
> I start this running in the background. (the cat is to effectively flush the 
> buffers so that the diff won't fail again on the same corruption)
> 
> I also have a little c program to allocate all memory (call it 'exhaust') 
> (unfortunately it's now crashed bad enough that I can't reboot it from home 
> so i'll send the code tomorrow if anyone's interested)
> 
> The crash only seems to occur once I start both dom1 and dom2, or at least 
> get dom0 + 1 other running on cpu 0, and then start running 'exhaust' over 
> and over. Issuing a few 'xm list's seems to help speed up the process. 
> Without running 'exhaust' at least once I can't get it to crash.
> 
> The crash that's just occured has generated a heap of oops's but most of them 
> are probably caused by corruption and won't tell anything about the original 
> error. i'll have a look and post any that seem interesting.
> 
> hope that helps...
> 
> James
 -=- MIME -=- 
--_C429E287-44E1-4346-952B-A66E425F27D7_
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

okay I think I can reliably make it crash / corrupt. the server is an smp 5=
50mhz p3 xeon with 768mb memory. dom0 has 128mb of memory with no swap. dom=
1 is a backup mail server which might accept an email every few minutes. It=
 also does spam checking. dom2 is just a base debian install just sitting i=
dle.

I have two identical 300mb files of random data (file3 & file4), and a scri=
pt that repeatedly compares them (call it 'compare'):

#!/bin/sh
while [ 1 =3D 1 ]
do
 diff file3 file4 && echo okay
 cat file3 >/dev/null
done

I start this running in the background. (the cat is to effectively flush th=
e buffers so that the diff won't fail again on the same corruption)

I also have a little c program to allocate all memory (call it 'exhaust') (=
unfortunately it's now crashed bad enough that I can't reboot it from home =
so i'll send the code tomorrow if anyone's interested)

The crash only seems to occur once I start both dom1 and dom2, or at least =
get dom0 + 1 other running on cpu 0, and then start running 'exhaust' over =
and over. Issuing a few 'xm list's seems to help speed up the process. With=
out running 'exhaust' at least once I can't get it to crash.

The crash that's just occured has generated a heap of oops's but most of th=
em are probably caused by corruption and won't tell anything about the orig=
inal error. i'll have a look and post any that seem interesting.

hope that helps...

James

--_C429E287-44E1-4346-952B-A66E425F27D7_
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#000000 size=3D2>okay I think I can reliabl=
y make it crash / corrupt. </FONT><FONT face=3DArial size=3D2><FONT face=3D=
Arial size=3D2>the server is an smp 550mhz p3 xeon with 768mb memory. dom0 =
has 128mb of memory with no swap. dom1 is a backup mail server which might =
accept an email every few minutes. It also does spam checking. dom2 is just=
 a base debian install just sitting idle.</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;</DIV></FONT>
<DIV><FONT face=3DArial size=3D2>I have two identical 300mb files of random=
 data (file3 &amp; file4), and&nbsp;</FONT><FONT face=3DArial size=3D2>a sc=
ript that repeatedly compares them (call it 'compare'):</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>#!/bin/sh<BR>while [ 1 =3D 1 ]<BR>do<BR>&n=
bsp;diff file3 file4 &amp;&amp; echo okay<BR>&nbsp;cat file3 &gt;/dev/null<=
BR>done<BR></DIV></FONT>
<DIV><FONT face=3DArial size=3D2>I start this running in the background. (t=
he cat is to effectively flush the buffers so that the diff won't fail agai=
n on the same corruption)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I also have a little c program to allocate=
 all memory (call it 'exhaust') (unfortunately it's now crashed bad enough =
that I can't reboot it from home so i'll send the code tomorrow if anyone's=
 interested)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The crash only seems to occur once I start=
 both dom1 and dom2, or at least get dom0 + 1 other running on cpu 0, and t=
hen start running 'exhaust' over and over. Issuing a few 'xm list's seems t=
o help speed up the process. Without running 'exhaust' at least once I can'=
t get it to crash.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The crash that's just occured has generate=
d a heap of oops's but most of them are probably caused by corruption and w=
on't tell anything about the original error. i'll have a look and post any =
that seem interesting.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>hope that helps...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>James</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

--_C429E287-44E1-4346-952B-A66E425F27D7_--


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>