Just an FYI on that, and it may be of no relevance to this issue (But could be).
We had an issue with the bios on our HT dual proc box. Our issue was in Linux (I assume other OSs too), the machine would randomly lose processors at absolutely random times. So, what would happen is we would have 4 procs (Or 3, or whatever) on boot, then one would come, and so forth. This of course caused crashes, since if a proc running the kernel was lost we lost the OS. This could also cause applications to randomly fail as well, since the Kernel was usually camped on proc 1 of 4. So, it could be a BIOS "Feature" as well for Storable and not the actual module itself. Original Message: ----------------- From: [EMAIL PROTECTED] (Justin Mason) Date: Wed, 15 Dec 2004 10:47:30 -0800 To: [email protected] Subject: Storable and hyperthreading OK, so on the spamd hang bugs, we have: - a set of people reporting hangs predominantly (all?) when running spamd on hyperthreaded CPUs - not all HT CPUs are acting up - a hang traced into Storable::dclone() (thanks Dallas!) so I think we may have run into a perl thread-safety bug, possibly in Storable, possibly at a lower level, and running on HT cpus causes this bug to manifest itself. Another reason to get rid of our use of Storable, in my opinion. --j. -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .
