linux-kernel - Re: 2.9.29.2: ide-tape: panic when probing device at boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201001040115.o041FCEA025051@turbo.physics.adelaide.edu.au>
Date:	Mon, 4 Jan 2010 11:45:12 +1030 (CST)
From:	Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>
To:	tj@...nel.org (Tejun Heo)
Cc:	petkovbb@...il.com, bzolnier@...il.com (Bartlomiej Zolnierkiewicz),
	jwoithe@...sics.adelaide.edu.au (Jonathan Woithe),
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	tj@...nel.org (Tejun Heo)
Subject: Re: 2.9.29.2: ide-tape: panic when probing device at boot

Hi

> Borislav Petkov wrote:
> > Hi,
> > 
> > On Sat, May 09, 2009 at 05:57:49PM +0200, Bartlomiej Zolnierkiewicz wrote:
> >> [ cc:ing linux-ide and knowledgeable people ]
> >>
> >> Borislav/Tejun:
> >>
> >> Is the 2.6.29 problem the same thing that was fixed recently?
> > 
> > I'll let Tejun answer that one since I don't get an oops. However, now
> > that I have an ide-tape hardware here, I do get something DMA-related
> > failing during boot:
> > 
> > [    1.677012] hdb: Seagate STT8000A, ATAPI TAPE drive
> > 
> > ..
> > 
> > [    1.701097] hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
> > [    1.708289] hdb: bad DMA info in identify block
> > [    1.712872] hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
> > 
> > ..
> > 
> > [    3.450381] Uniform CD-ROM driver Revision: 3.20
> > [    5.467347] ide-tape: hdb <-> ht0: Seagate STT8000A rev 5.44
> > [    5.484852] ide-tape: hdb <-> ht0: 88KBps, 14*26kB buffer, 400ms tDS
> > 
> > and more specifically the bad DMA info in identify block thing above. I
> > haven't looked into it yet but its next on my TODO.
> 
> Yeah, I've been seeing that too (before and after my changes).
> Haven't investigated it yet.  Good that it's on your todo list.  :-)
> 
> >> Should I just push commit 1e75540ec5202cae63cd238c86bd880e3d496546
> >> ("ide-tape: remove back-to-back REQUEST_SENSE detection") to Linus
> >> or there is more needed to bring ide-tape to the world of living?
> > 
> > ... and I'm afraid we'll have to do some serious bugfixing since this
> > driver is behaving really funny :). Stay tuned, I'm on it.
> 
> Cool.

Has there been any movement on this in recent months?  I gave 2.6.30 a whirl
on the machine when that was released but it still gave major problems with
the ide-tape driver.  Is 2.6.32 likely to be improved?  If so I'll make
arrangements to test that version.

Presently I'm stuck with 2.6.24.x on this system since ide-tape holds
together enough on this version to work.  I really want to upgrade to a more
recent kernel but obviously I can't until ide-tape is functional again.

Regards
  jonathan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/