Has this corruption appeared on both 32 and 64 bit Linux flavors, or just one?
On Wed, Oct 1, 2008 at 8:34 AM, Chuck Forsberg WA7KGX N2469R caf@omen.com wrote:
Has this corruption appeared on both 32 and 64 bit Linux flavors, or just one?
There's one driver for both platforms so I suspect it will happen on both 32 or 64 flavours.
Peter
On Wed, Oct 01, 2008 at 09:34:34AM +0100, Peter Robinson wrote:
On Wed, Oct 1, 2008 at 8:34 AM, Chuck Forsberg WA7KGX N2469R caf@omen.com wrote:
Has this corruption appeared on both 32 and 64 bit Linux flavors, or just one?
There's one driver for both platforms so I suspect it will happen on both 32 or 64 flavours.
AFAIK reasons for the problem are still unknown but reports of corruption presumably come so far from 64-bit machines. It appears that some race is involved so it may be that its window is easier to hit with 64 bits?
Michal
Michal Jaegermann wrote:
On Wed, Oct 01, 2008 at 09:34:34AM +0100, Peter Robinson wrote:
On Wed, Oct 1, 2008 at 8:34 AM, Chuck Forsberg WA7KGX N2469R caf@omen.com wrote:
Has this corruption appeared on both 32 and 64 bit Linux flavors, or just one?
There's one driver for both platforms so I suspect it will happen on both 32 or 64 flavours.
AFAIK reasons for the problem are still unknown but reports of corruption presumably come so far from 64-bit machines. It appears that some race is involved so it may be that its window is easier to hit with 64 bits?
64-bit hardware, certainly - presumably almost any hardware that has the effected Ethernet card(s) would be a Core 2 or better 64-bit machine.
But I'm fairly sure (it's been about a month, so I could be mis-remembering) I've only tried installing 32-bit versions of Fedora and Ubuntu - and my Ethernet card was affected.
Per Bothner wrote:
Michal Jaegermann wrote:
On Wed, Oct 01, 2008 at 09:34:34AM +0100, Peter Robinson wrote:
On Wed, Oct 1, 2008 at 8:34 AM, Chuck Forsberg WA7KGX N2469R caf@omen.com wrote:
Has this corruption appeared on both 32 and 64 bit Linux flavors, or just one?
There's one driver for both platforms so I suspect it will happen on both 32 or 64 flavours.
AFAIK reasons for the problem are still unknown but reports of corruption presumably come so far from 64-bit machines. It appears that some race is involved so it may be that its window is easier to hit with 64 bits?
64-bit hardware, certainly - presumably almost any hardware that has the effected Ethernet card(s) would be a Core 2 or better 64-bit machine.
But I'm fairly sure (it's been about a month, so I could be mis-remembering) I've only tried installing 32-bit versions of Fedora and Ubuntu - and my Ethernet card was affected.
I'm running 64-bit Linux (Fedora, C5, opensuse 11.0) on relevant hardware. I will _not_ try the opensuse beta (the docs suggest destruction is possible), and if I keep updating Fedora 10 alpha I suspect I will lose the Internet.
On Thu, Oct 02, 2008 at 01:47:39PM +0800, John Summerfield wrote:
I'm running 64-bit Linux (Fedora, C5, opensuse 11.0) on relevant hardware. I will _not_ try the opensuse beta (the docs suggest destruction is possible), and if I keep updating Fedora 10 alpha I suspect I will lose the Internet.
I tried F10 beta, and my ethernet card doesn't work because they disabled the e1000e driver. At least it didn't fry my NVRAM.
I wonder what kind of help I can provide seeing as I have the affected hardware, but without actually ruining my card.
On Thu, Oct 02, 2008 at 13:59:00 -0400, Chuck Anderson cra@WPI.EDU wrote:
On Thu, Oct 02, 2008 at 01:47:39PM +0800, John Summerfield wrote:
I'm running 64-bit Linux (Fedora, C5, opensuse 11.0) on relevant hardware. I will _not_ try the opensuse beta (the docs suggest destruction is possible), and if I keep updating Fedora 10 alpha I suspect I will lose the Internet.
I tried F10 beta, and my ethernet card doesn't work because they disabled the e1000e driver. At least it didn't fry my NVRAM.
I wonder what kind of help I can provide seeing as I have the affected hardware, but without actually ruining my card.
According to a comment in a koji update to the kernel today, the problem has been fixed. I haven't yet seen that announcement anywhere out. (Note this is supposed to be a real fix, not the work around previously implemented to disable the driver.)
On 10/2/08, Bruno Wolff III bruno@wolff.to wrote:
According to a comment in a koji update to the kernel today, the problem has been fixed. I haven't yet seen that announcement anywhere out.
Good catch! Here's the comment [1]
Apparently, upstream's fix was so fast this bug never made it past NEW. Now what? [2]
jerry
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=65088 [2] https://bugzilla.redhat.com/show_bug.cgi?id=459202
-
Bruno Wolff III -
Chuck Anderson -
Chuck Forsberg WA7KGX -
Jerry Amundson -
John Summerfield -
Michal Jaegermann -
Per Bothner -
Peter Robinson