> On Tue, Sep 18, 2007 at 11:47:05PM +0200, you [Willy Tarreau] wrote:
> > Thanks for your report. Unfortunately, I've rechecked the recent changelogs
> > and see nothing related either. At least, in order to keep trace of the
> > incident, would you please post some info about your config (CPU, RAM,
> > chipset, .config, gcc, and any possible patches you may have applied) ?
> > Maybe some of these info may remind old bad memories to some people.
> >
> > Also, do you know if this server has ECC memory ? I would more easily
> > bet for side effects of one random bit flip in memory than for some
> > massive block corruption.
> >
> > I vaguely remember about very old reports of people sometimes observing
> > zeroed out blocks during writes, which were attributed to chipset bugs
> > if my memory serves me. But I would rule this out as recent chipsets
> > look more stable than 5-10 years ago !
>
> Willy,
>
> The machine is a virtual machine on an VMware ESX 3.0.1 host.
>
> /proc/cpuinfo shows two of these:
> Dual
> model : 15
> model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz
> stepping : 8
> cpu MHz : 2333.014
> cache size : 64 KB
>
> It has 864MB of memory.
>
> .config is at:
>
http://v.iki.fi/~vherva/tmp/2.4.35-config
> The kernel is plain vanilla 2.4.35 from kernel.org, no patches.
