On Wed, May 06, 2009 at 08:11:21AM +0200, Borislav Petkov wrote:
> On Tue, May 05, 2009 at 11:12:59PM +0200, Mark de Wever wrote:
> > > In the mean time, Tejun has fixed some ide-tape bugs and has a git
> > > tree so if you don't want to wait for the fixes to trickle upstream
> > > and are eager to test :) you could pull from
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git ide-phase2
> > 
> > I compiled 2.6.30-rc4 + ide-phase2 +  your 'tmp fix 2' patch +
> > IDETAPE_DEBUG_LOG set to 1
> 
> Actually, I meant only the Tejun tree without my patches. Please retry again if
> you have the time or just wait a bit - I finally got an ide tape myself :) :

That's good to hear :-)

I also managed retested the drive, this time with
2.6.30-rc5 + ide-phase2 + my ide-phase2 compilation fix patch
+ IDETAPE_DEBUG_LOG

This combination seems to work :-) I wrote a small file to the tape and
could read it again.

After this test I played and tried some more things and got another
kernel warning. I haven't been able to reproduce this consistently but
it seems to occur after playing a bit with:
- writing a file to the drive
- use rewind on the drive
- use fsf 1 on the drive
- reading a file from the drive
(I know fsf 1 on /dev/ht0 is rather useless ;-))
I think this problem is not related with the problems I had before,
attached the entire dmesg, from boot to the kernel message. If you
want I can try to find a way to reproduce it.

Thanks for your effort to get the drive working again.

-- 
Regards,
Mark de Wever