On Mon, Mar 30, 2009 at 09:52:55PM +0300, Ilpo Järvinen wrote:
quoted text
> On Mon, 30 Mar 2009, Markus Trippelsdorf wrote:
> 
> > On Mon, Mar 30, 2009 at 07:01:22PM +0300, Ilpo Järvinen wrote:
> > > On Sat, 28 Mar 2009, Markus Trippelsdorf wrote:
> > > > On Sat, Mar 28, 2009 at 10:29:58AM +0200, Ilpo Järvinen wrote:
> > > 
> > > ...And, let me guess, you're in X and therefore unable to catch a final 
> > > oops if any would be printed? It would be nice to get around that as well, 
> > > either use serial/netconsole or hang in text mode while waiting for the 
> > > crash (should be too hard if you are able to setup the workload first 
> > > and then switch away from X and if reproducing takes about an hour)...
> > 
> > OK, I will try this later.
> 
> Lets hope that gives some clue where it ends up going boom (if it is 
> caused by TCP we certainly should see something more sensible in console 
> than just a hang)... ...I once again read through tcp commits but just 
> cannot find anything that could cause fackets_out miscount, not to speak 
> of crash prone changes so we'll just have to wait and see...

The machine hanged again this night and I took two pictures:
http://www.mypicx.com/uploadimg/1055813374_03302009_2.jpg
http://www.mypicx.com/uploadimg/1543678904_03302009_1.jpg

But this time there was no tcp related warning in the logs.

I then pulled the lateset git changes, rebuild, rebooted and setup the
workload again. The machine was still up and running in the morning 
(~4 hours uptime). So it may well be that the issue was fixed with
the latest changes. If it ever occurs again I will notify you.

Thanks for your assistance so far,

-- 
Markus
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html