On Fri, 20 Jul 2001, Geert Uytterhoeven wrote:
> On Sun, 8 Jul 2001, Geert Uytterhoeven wrote:
> > New findings:
> > - The problem doesn't happen with kernels <= 2.2.17. It does happen with all
> > kernels starting with 2.2.18-pre1.
> > - The only related stuff that changed in
On Sun, 8 Jul 2001, Geert Uytterhoeven wrote:
> New findings:
> - The problem doesn't happen with kernels <= 2.2.17. It does happen with all
> kernels starting with 2.2.18-pre1.
> - The only related stuff that changed in 2.2.18-pre1 seems to be the
> Sym53c8xx driver itself. I'll do
On Sun, 8 Jul 2001, Geert Uytterhoeven wrote:
New findings:
- The problem doesn't happen with kernels = 2.2.17. It does happen with all
kernels starting with 2.2.18-pre1.
- The only related stuff that changed in 2.2.18-pre1 seems to be the
Sym53c8xx driver itself. I'll do some
On Fri, 20 Jul 2001, Geert Uytterhoeven wrote:
On Sun, 8 Jul 2001, Geert Uytterhoeven wrote:
New findings:
- The problem doesn't happen with kernels = 2.2.17. It does happen with all
kernels starting with 2.2.18-pre1.
- The only related stuff that changed in 2.2.18-pre1 seems
On Sun, 8 Jul 2001, Geert Uytterhoeven wrote:
> On Thu, 21 Jun 2001, Geert Uytterhoeven wrote:
> > On Tue, 8 May 2001, Geert Uytterhoeven wrote:
> > > In the mean time I down/upgraded to 2.2.17 on my PPC box (CHRP LongTrail,
> > > Sym53c875, HP C5136A DDS1) and I can confirm that the problem
On Thu, 21 Jun 2001, Geert Uytterhoeven wrote:
> On Tue, 8 May 2001, Geert Uytterhoeven wrote:
> > In the mean time I down/upgraded to 2.2.17 on my PPC box (CHRP LongTrail,
> > Sym53c875, HP C5136A DDS1) and I can confirm that the problem does not happen
> > under 2.2.17 neither.
> >
> > My
On Thu, 21 Jun 2001, Geert Uytterhoeven wrote:
On Tue, 8 May 2001, Geert Uytterhoeven wrote:
In the mean time I down/upgraded to 2.2.17 on my PPC box (CHRP LongTrail,
Sym53c875, HP C5136A DDS1) and I can confirm that the problem does not happen
under 2.2.17 neither.
My experiences:
On Sun, 8 Jul 2001, Geert Uytterhoeven wrote:
On Thu, 21 Jun 2001, Geert Uytterhoeven wrote:
On Tue, 8 May 2001, Geert Uytterhoeven wrote:
In the mean time I down/upgraded to 2.2.17 on my PPC box (CHRP LongTrail,
Sym53c875, HP C5136A DDS1) and I can confirm that the problem does not
On Tue, 8 May 2001, Geert Uytterhoeven wrote:
> On Mon, 7 May 2001, Lorenzo Marcantonio wrote:
> > On Mon, 7 May 2001, Rob Turk wrote:
> > > Have you ruled out hardware failures? There's been a few isolated reports
> >
> > That tape drive (Sony SDT-9000, less than 2 years of service) works
> >
On Tue, 8 May 2001, Geert Uytterhoeven wrote:
On Mon, 7 May 2001, Lorenzo Marcantonio wrote:
On Mon, 7 May 2001, Rob Turk wrote:
Have you ruled out hardware failures? There's been a few isolated reports
That tape drive (Sony SDT-9000, less than 2 years of service) works
perfectly on
For comparison purposes,
I use stock kernel 2.4.4.
Use scsi tape support as module.
Tape drive is HP c1539 (aka 1533a) dds-2.
This drive is on the scsi chain of Tekram dc390, tmscsim driver
(used as module).
Hardware compression is enabled.
Under this setup,
tar cvbf 20 /dev/st0
For comparison purposes,
I use stock kernel 2.4.4.
Use scsi tape support as module.
Tape drive is HP c1539 (aka 1533a) dds-2.
This drive is on the scsi chain of Tekram dc390, tmscsim driver
(used as module).
Hardware compression is enabled.
Under this setup,
tar cvbf 20 /dev/st0
On Tue, 8 May 2001, Geert Uytterhoeven wrote:
> In the mean time I down/upgraded to 2.2.17 on my PPC box (CHRP LongTrail,
> Sym53c875, HP C5136A DDS1) and I can confirm that the problem does not happen
> under 2.2.17 neither.
>
> My experiences:
> - reading works fine, writing doesn't
Same
On Mon, 7 May 2001, Lorenzo Marcantonio wrote:
> On Mon, 7 May 2001, Rob Turk wrote:
> > Have you ruled out hardware failures? There's been a few isolated reports
>
> That tape drive (Sony SDT-9000, less than 2 years of service) works
> perfectly on Windows NT (were it was before) and even on
On Mon, 7 May 2001, Lorenzo Marcantonio wrote:
On Mon, 7 May 2001, Rob Turk wrote:
Have you ruled out hardware failures? There's been a few isolated reports
That tape drive (Sony SDT-9000, less than 2 years of service) works
perfectly on Windows NT (were it was before) and even on Linux
On Mon, 7 May 2001, Rob Turk wrote:
> Lorenzo,
>
> Have you ruled out hardware failures? There's been a few isolated reports
That tape drive (Sony SDT-9000, less than 2 years of service) works
perfectly on Windows NT (were it was before) and even on Linux 2.2
Also the cartridge was brand new.
"Lorenzo Marcantonio" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> As of my latest build [2.4.5-pre1] I've STILL got the tape corruption
> problem. Some new facts:
>
> (1) It happens only writing the tape (tried exchanging tapes with a
> brand new Alpha Digital Tru64 box). I
Lorenzo Marcantonio [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
As of my latest build [2.4.5-pre1] I've STILL got the tape corruption
problem. Some new facts:
(1) It happens only writing the tape (tried exchanging tapes with a
brand new Alpha Digital Tru64 box). I can read
On Mon, 7 May 2001, Rob Turk wrote:
Lorenzo,
Have you ruled out hardware failures? There's been a few isolated reports
That tape drive (Sony SDT-9000, less than 2 years of service) works
perfectly on Windows NT (were it was before) and even on Linux 2.2
Also the cartridge was brand new.
In article <[EMAIL PROTECTED]> you write:
>On Fri, 13 Apr 2001, Nate Eldredge wrote:
>> (32 bytes is the size of a cache line.) A memory tester might be
>> something to try (I wrote a simple program that seemed to show the
>> error better than memtest86; can send it if desired.)
>
>Already tried
On Fri, 13 Apr 2001, Nate Eldredge wrote:
> (32 bytes is the size of a cache line.) A memory tester might be
> something to try (I wrote a simple program that seemed to show the
> error better than memtest86; can send it if desired.)
Already tried that... this system has passed some 20 hours
On Fri, 13 Apr 2001, Nate Eldredge wrote:
> [EMAIL PROTECTED] wrote:
> > Well, the 2.2 distributed with Mandrake 7.2 works fine ... :)
> >
> > Hmmm... 32 CONSECUTIVE bytes are a very peculiar error. What can it be?
> >
> > Still experimenting...
>
> I once ran into a problem with 32-byte
On Fri, 13 Apr 2001, Nate Eldredge wrote:
[EMAIL PROTECTED] wrote:
Well, the 2.2 distributed with Mandrake 7.2 works fine ... :)
Hmmm... 32 CONSECUTIVE bytes are a very peculiar error. What can it be?
Still experimenting...
I once ran into a problem with 32-byte errors appearing
On Fri, 13 Apr 2001, Nate Eldredge wrote:
(32 bytes is the size of a cache line.) A memory tester might be
something to try (I wrote a simple program that seemed to show the
error better than memtest86; can send it if desired.)
Already tried that... this system has passed some 20 hours
In article [EMAIL PROTECTED] you write:
On Fri, 13 Apr 2001, Nate Eldredge wrote:
(32 bytes is the size of a cache line.) A memory tester might be
something to try (I wrote a simple program that seemed to show the
error better than memtest86; can send it if desired.)
Already tried that...
[EMAIL PROTECTED] wrote:
> Well, the 2.2 distributed with Mandrake 7.2 works fine ... :)
>
> Hmmm... 32 CONSECUTIVE bytes are a very peculiar error. What can it be?
>
> Still experimenting...
I once ran into a problem with 32-byte errors appearing in files, and
later, in memory. I eventually
On Fri, 13 Apr 2001, Geert Uytterhoeven wrote:
> On Thu, 12 Apr 2001 [EMAIL PROTECTED] wrote:
> > It seems that the tape is written incorrectly. I wrote some large file
> > (300MB)
> > and read it back four time. The read copies are all the same. They differ
> > from the original only in 32
On Thu, 12 Apr 2001 [EMAIL PROTECTED] wrote:
> Still experimenting with my SDT-9000... tried connecting it to another
> controller
> (2940AU in place of 2904, sorry but I've only Adaptec stuff :). Same
> problem.
> Tried with another tape (even with an old DDS-2 tape). Same. Even tried
> another
On Thu, 12 Apr 2001 [EMAIL PROTECTED] wrote:
Still experimenting with my SDT-9000... tried connecting it to another
controller
(2940AU in place of 2904, sorry but I've only Adaptec stuff :). Same
problem.
Tried with another tape (even with an old DDS-2 tape). Same. Even tried
another
On Fri, 13 Apr 2001, Geert Uytterhoeven wrote:
On Thu, 12 Apr 2001 [EMAIL PROTECTED] wrote:
It seems that the tape is written incorrectly. I wrote some large file
(300MB)
and read it back four time. The read copies are all the same. They differ
from the original only in 32 consecutive
[EMAIL PROTECTED] wrote:
Well, the 2.2 distributed with Mandrake 7.2 works fine ... :)
Hmmm... 32 CONSECUTIVE bytes are a very peculiar error. What can it be?
Still experimenting...
I once ran into a problem with 32-byte errors appearing in files, and
later, in memory. I eventually
On Thu, 12 Apr 2001, Gérard Roudier wrote:
> using a sym53c875 controller. In this case, kernel 2.2 was fine.
>
> > Now I'll build some old 2.2 kernel to try...
>
> If 2.2 is ok with your tape, a software error in 2.4 gets very likely, in
> my opinion.
Well, the 2.2 distributed with Mandrake
On Thu, 12 Apr 2001 [EMAIL PROTECTED] wrote:
> Still experimenting with my SDT-9000... tried connecting it to another
> controller
> (2940AU in place of 2904, sorry but I've only Adaptec stuff :). Same
> problem.
> Tried with another tape (even with an old DDS-2 tape). Same. Even tried
>
[EMAIL PROTECTED] wrote:
> It seems that the tape is written incorrectly. I wrote some large file
> (300MB)
> and read it back four time. The read copies are all the same. They differ
> from the original only in 32 consecutive bytes (the replaced values SEEM
> random). Of course, 32 bytes in
[EMAIL PROTECTED] wrote:
It seems that the tape is written incorrectly. I wrote some large file
(300MB)
and read it back four time. The read copies are all the same. They differ
from the original only in 32 consecutive bytes (the replaced values SEEM
random). Of course, 32 bytes in 300MB
On Thu, 12 Apr 2001 [EMAIL PROTECTED] wrote:
Still experimenting with my SDT-9000... tried connecting it to another
controller
(2940AU in place of 2904, sorry but I've only Adaptec stuff :). Same
problem.
Tried with another tape (even with an old DDS-2 tape). Same. Even tried
another
On Thu, 12 Apr 2001, Grard Roudier wrote:
using a sym53c875 controller. In this case, kernel 2.2 was fine.
Now I'll build some old 2.2 kernel to try...
If 2.2 is ok with your tape, a software error in 2.4 gets very likely, in
my opinion.
Well, the 2.2 distributed with Mandrake 7.2 works
37 matches
Mail list logo
