Re: File corruption when using kernels 2.6.18+

2007-10-04 Thread Neil Romig
Alan Cox wrote: On Wed, 3 Oct 2007 22:35:24 +0300 "Pekka Enberg" <[EMAIL PROTECTED]> wrote: Hi Linus, On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote: I would bet that the reason the intel-optimized memcpy triggers this is that the non-temporal stores just means that you go out directly

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Linus Torvalds
On Wed, 3 Oct 2007, Robert Hancock wrote: > > Erratum 97: 128-Bit Streaming Stores May Cause Coherency Failure The Intel-optimized memcpy doesn't use the SSE registers, just regular 32-bit integer nontemporal stores (movnti). The reason is that the SSE state save is too expensive to be worth

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Robert Hancock
Linus Torvalds wrote: On Wed, 3 Oct 2007, Pekka Enberg wrote: On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote: I would bet that the reason the intel-optimized memcpy triggers this is that the non-temporal stores just means that you go out directly on the bus, and it probably just shows a

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Hiro Yoshioka
Hi, From: Linus Torvalds <[EMAIL PROTECTED]> > On Wed, 3 Oct 2007, Pekka Enberg wrote: > > > > On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote: > > > I would bet that the reason the intel-optimized memcpy triggers this is > > > that the non-temporal stores just means that you go out directly

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Alan Cox
On Wed, 3 Oct 2007 22:35:24 +0300 "Pekka Enberg" <[EMAIL PROTECTED]> wrote: > Hi Linus, > > On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote: > > I would bet that the reason the intel-optimized memcpy triggers this is > > that the non-temporal stores just means that you go out directly on the

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Linus Torvalds
On Wed, 3 Oct 2007, Pekka Enberg wrote: > > On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote: > > I would bet that the reason the intel-optimized memcpy triggers this is > > that the non-temporal stores just means that you go out directly on the > > bus, and it probably just shows a weakness

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Pekka Enberg
Hi Linus, On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote: > I would bet that the reason the intel-optimized memcpy triggers this is > that the non-temporal stores just means that you go out directly on the > bus, and it probably just shows a weakness in the chipset or bus that > doesn't show

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Linus Torvalds
On Wed, 3 Oct 2007, Pekka Enberg wrote: > Hi Neil, > > On 10/3/07, Neil Romig <[EMAIL PROTECTED]> wrote: > > > > Thanks for your help on this. I have narrowed it down to commit > > > > "c22ce143d15eb288543fe9873e1c5ac1c01b69a1 x86: cache pollution aware > > > > __copy_from_user_ll()". This fits

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Pekka Enberg
Hi Neil, On 10/3/07, Neil Romig <[EMAIL PROTECTED]> wrote: > > > Thanks for your help on this. I have narrowed it down to commit > > > "c22ce143d15eb288543fe9873e1c5ac1c01b69a1 x86: cache pollution aware > > > __copy_from_user_ll()". This fits with the errors I'm getting, so now I > > > need > >

Re: File corruption when using kernels 2.6.18+

2007-10-03 Thread Neil Romig
Pekka Enberg wrote: Hi Neil, On 10/3/07, Neil Romig <[EMAIL PROTECTED]> wrote: Thanks for your help on this. I have narrowed it down to commit "c22ce143d15eb288543fe9873e1c5ac1c01b69a1 x86: cache pollution aware __copy_from_user_ll()". This fits with the errors I'm getting, so now I need to fin

Re: File corruption when using kernels 2.6.18+

2007-10-02 Thread Pekka Enberg
Hi Neil, On 10/3/07, Neil Romig <[EMAIL PROTECTED]> wrote: > Thanks for your help on this. I have narrowed it down to commit > "c22ce143d15eb288543fe9873e1c5ac1c01b69a1 x86: cache pollution aware > __copy_from_user_ll()". This fits with the errors I'm getting, so now I need > to find out if I can

Re: File corruption when using kernels 2.6.18+

2007-10-02 Thread Chuck Ebbert
On 09/30/2007 11:40 AM, Neil Romig wrote: > I am using kernel 2.6.17.14, and would like to use newer versions for > the wireless code but I get file corruption with any kernel more recent > than this. My system uses a SiS645DX chipset (it is a rebadged CLEVO > D400E) with 5513 IDE. > > I get this

Re: File corruption when using kernels 2.6.18+

2007-10-02 Thread Neil Romig
Pekka Enberg wrote: Hi Neil, On 9/30/07, Neil Romig <[EMAIL PROTECTED]> wrote: I would suspect a memory problem but memtest86+ gives no errors despite numerous passes, and I get no errors in older kernels. Does anyone have any idea what changed in 2.6.18 to cause such an error? I don't but y

Re: File corruption when using kernels 2.6.18+

2007-09-30 Thread Pekka Enberg
Hi Neil, On 9/30/07, Neil Romig <[EMAIL PROTECTED]> wrote: > I would suspect a memory problem but memtest86+ gives no errors despite > numerous > passes, and I get no errors in older kernels. Does anyone have any idea what > changed in > 2.6.18 to cause such an error? I don't but you can try to

File corruption when using kernels 2.6.18+

2007-09-30 Thread Neil Romig
I am using kernel 2.6.17.14, and would like to use newer versions for the wireless code but I get file corruption with any kernel more recent than this. My system uses a SiS645DX chipset (it is a rebadged CLEVO D400E) with 5513 IDE. I get this corruption with read/writes, i.e using "cp", "dd", w