linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Duda <jim@duda.tzo.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: 2.6.31-rc1 with ide-tape / STT2000A
Date: Sun, 09 Aug 2009 22:28:43 -0400	[thread overview]
Message-ID: <4A7F85DB.40604@duda.tzo.com> (raw)
In-Reply-To: <20090809072823.GA2130@liondog.tnic>

On 08/09/2009 03:28 AM, Borislav Petkov wrote:
>
> If you'd like to test patches you can get Dave's linux-next git repo at
> http://git.kernel.org/?p=linux/kernel/git/davem/ide-next-2.6.git;a=summary
>
> apply the patch below and catch all boot output from your machine and
> send it to me.
>

Okay, I'm running the davem/ide-net-2.6.git version with your patch 
below.  My dmesg startup messages for ide-tape are below.  Is this what 
you were hoping to see?

ide-tape: idetape_do_request: cmd: 0x12, sector: 18446744073709551615, 
nr_sectors: 0
ide-tape: ide_tape_issue_pc: retry #0, cmd: 0x12
ide-tape: ide_tape_callback: cmd: 0x12, dsc: 0, err: 0
ide-tape: hdd <-> ht0: Seagate STT20000A rev 8A51
ide-tape: idetape_do_request: cmd: 0x1a, sector: 18446744073709551615, 
nr_sectors: 0
ide-tape: ide_tape_issue_pc: retry #0, cmd: 0x1a
ide-tape: idetape_do_request: cmd: 0x3, sector: 18446744073709551615, 
nr_sectors: 0
ide-tape: ide_tape_issue_pc: retry #0, cmd: 0x03
ide-tape: ide_tape_callback: cmd: 0x3, dsc: 0, err: 0
ide-tape: idetape_analyze_error: cmd: 0x3, sense key = 6, asc = 28, ascq = 0
ide-tape: idetape_do_request: cmd: 0x1a, sector: 18446744073709551615, 
nr_sectors: 0
ide-tape: ide_tape_issue_pc: retry #1, cmd: 0x1a
ide-tape: ide_tape_callback: cmd: 0x1a, dsc: 0, err: 0
ide-tape: idetape_do_request: cmd: 0x1a, sector: 18446744073709551615, 
nr_sectors: 0
ide-tape: ide_tape_issue_pc: retry #0, cmd: 0x1a
ide-tape: ide_tape_callback: cmd: 0x1a, dsc: 0, err: 0
ide-tape: ide_tape_get_bsize_from_bdesc: blk_size: 512, write_prot: 0
ide-tape: hdd <-> ht0: 232KBps, 6*54kB buffer, 400ms tDSC
U




  parent reply	other threads:[~2009-08-10  2:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 20:30 2.6.31-rc1 with ide-tape / STT2000A Jim Duda
2009-08-08 20:59 ` Robert Hancock
2009-08-08 21:44   ` Jim Duda
2009-08-09 16:58     ` Alan Cox
2009-08-09 19:47       ` Jim Duda
2009-08-09 20:21         ` Alan Cox
2009-08-09 20:25           ` Jim Duda
2009-08-09 20:58             ` Alan Cox
2009-08-09 22:27       ` Bartlomiej Zolnierkiewicz
2009-08-10 17:21         ` Alan Cox
2009-08-10 19:48           ` Bartlomiej Zolnierkiewicz
2009-08-10 21:20             ` Alan Cox
2009-08-10 21:42               ` Bartlomiej Zolnierkiewicz
2009-08-11  0:40       ` Jim Duda
2009-08-09  7:28 ` Borislav Petkov
2009-08-09 22:51   ` Jim Duda
2009-08-09 23:32     ` Jim Duda
2009-08-10  0:01     ` Jim Duda
2009-08-10  2:28   ` Jim Duda [this message]
2009-08-10 22:10     ` Jim Duda
2009-08-10 22:36       ` Alan Cox
2009-08-10 23:07         ` Jim Duda
2009-08-10 23:21           ` Jim Paris
2009-08-10 23:34             ` Jim Duda
2009-08-11  9:37           ` Alan Cox
2009-08-11  4:33     ` Borislav Petkov
2009-08-11 11:25       ` Jim Duda

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=4A7F85DB.40604@duda.tzo.com \
    --to=jim@duda.tzo.com \
    --cc=linux-ide@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).