mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Darren Dupre" <darren@dmdtech.org>
To: "Adam Kropelin" <akropel1@rochester.rr.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: "DV failed to configure device" for Quantum DLT4000 tape drive on Adaptec 2940UW, 2.6.0-test11
Date: Sat, 29 Nov 2003 14:20:09 -0600	[thread overview]
Message-ID: <012301c3b6b6$2feb9fe0$1e01a8c0@dmdtech2> (raw)
In-Reply-To: <20031129163806.A14451@mail.kroptech.com>

Hmm. That does reflect exactly what happened in my situation. I turned on
the tape drive, inserted a tape, and while it was busy rewinding, I inserted
the aic7xxx module.

I just tried inserting the module again, this time with no tape in the drive
as I turned it on and it initializes just fine and loads the st module. It
works fine doing everything else AFAIK.

But it still complains when I unload the modules..

Adam Kropelin <akropel1@rochester.rr.com>
>
> I've seen this same issue with my Quantum DLT4000 & 2940UW as well. It
> seems to have to do with there being a tape in the drive when the
> aic7xxx driver initializes. It looks to me like the DLT4000 does not
> respond to the DV configuration attempt when it is in the middle of
> rewinding a tape. If the rewind takes long enough, aic7xxx times out the
> configuration and gives the message you saw.
>
> I run a completely static kernel so in my case the problem happens when
> I reboot the machine with a tape still in the drive and the tape is
> positioned near the end. When the 2940UW BIOS initializes it triggers
> the DLT4000 to start rewinding the tape and if the tape is positioned
> far enough along it can still be rewinding when the kernel boots and
> aic7xxx tries to perform the DV configuration.
>
> --Adam
>
>


      reply	other threads:[~2003-11-29 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29 18:31 Darren Dupre
2003-11-29 18:53 ` Darren Dupre
2003-11-29 21:38 ` Adam Kropelin
2003-11-29 20:20   ` Darren Dupre [this message]

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='012301c3b6b6$2feb9fe0$1e01a8c0@dmdtech2' \
    --to=darren@dmdtech.org \
    --cc=akropel1@rochester.rr.com \
    --cc=linux-kernel@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

Powered by JetHome