kernel panics at google

[yoann en mandrakesoft.com]

David desJardins <desj en google.com> writes:

> yoann en mandrakesoft.com writes:
> > Maybe giving a trace of the kind of packet received before the crash
> > could help understanding / tracing the problem...
> > 
> > tcpdump -s2000 -vvv -w outfile
> > ( make sure no private data are passing on the network ).
> 
> I'm afraid this really isn't practical.  Each webserver handles well
> over 100 requests/second at peak times, and goes days between crashes.
> It also communicates with hundreds of different servers.  We can't
> possibly tcpdump every single packet, even in the most skeletal form,
> and even if the webservers didn't have other work to do.
I know that, 
but it is probably the most easy way to find the problem :-(

> 
> > Also, you should modify tcpdump call fflush() after each
> > line it append to the file.
> 
> And flushing after every line would be even more expensive.
Clearly...


-- 
		-- Yoann http://www.security-addict.org
 It is well known that M$ product don't make a free() after a malloc(),
the unix community wish them good luck for their future developement.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo en vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/