From: Chuck Ebbert <cebbert@redhat.com>
To: Neil Romig <neil@romig.demon.co.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: File corruption when using kernels 2.6.18+
Date: Tue, 02 Oct 2007 18:30:44 -0400 [thread overview]
Message-ID: <4702C694.10402@redhat.com> (raw)
In-Reply-To: <46FFC371.9040805@romig.demon.co.uk>
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 corruption with read/writes, i.e using "cp", "dd", when
> compiling software, writing to CD, etc etc. An example:
>
> cp ../Changelog-2.6.18 .
> diff Changelog-2.6.18 ../Changelog-2.6.18
>
> 16377c16377
> < LD .top_vmlinux1
> ---
>> LD .tmp_vmlinux1
> 23954c23954
> < Date: Mon Jul 1% 04:45:11 2006 -0700
> ---
>> Date: Mon Jul 10 04:45:11 2006 -0700
Is there some pattern to the corruption, like maybe it occurs once every
N bytes in the file?
next prev parent reply other threads:[~2007-10-02 22:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 15:40 File corruption when using kernels 2.6.18+ Neil Romig
2007-09-30 16:29 ` Pekka Enberg
2007-10-02 21:05 ` Neil Romig
2007-10-03 5:18 ` Pekka Enberg
2007-10-03 18:42 ` Neil Romig
2007-10-03 18:48 ` Pekka Enberg
2007-10-03 19:22 ` Linus Torvalds
2007-10-03 19:35 ` Pekka Enberg
2007-10-03 19:54 ` Linus Torvalds
2007-10-04 1:11 ` Hiro Yoshioka
2007-10-03 20:30 ` Alan Cox
2007-10-04 18:34 ` Neil Romig
2007-10-02 22:30 ` Chuck Ebbert [this message]
[not found] <fa.VCoGTwbB+qeNlkBJ24MiuXcGSRA@ifi.uio.no>
[not found] ` <fa.R+FhT6IGmV/dDweUt/MdSeA5YbQ@ifi.uio.no>
[not found] ` <fa.7MxTIt/ik0uRFN/lMWUasYV/JyE@ifi.uio.no>
[not found] ` <fa.YJ4uCPzXT5TQElSosyz98cpuMSc@ifi.uio.no>
[not found] ` <fa.Tp9UUX9EYprQyLg0shgH1YG9DDM@ifi.uio.no>
[not found] ` <fa.PzpJEEoLXfC+eOQZjTWjdf9vdnE@ifi.uio.no>
2007-10-04 2:59 ` Robert Hancock
2007-10-04 3:39 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4702C694.10402@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@romig.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox