public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Currie <billc@wirelessmatrixcorp.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, lnz@dandelion.com
Subject: Re: DAC960 oops
Date: Tue, 20 Nov 2001 15:59:56 -0700	[thread overview]
Message-ID: <20011120155955.E15561@wirelessmatrixcorp.com> (raw)
In-Reply-To: <20011119114446.A15561@wirelessmatrixcorp.com> <20011120200144.W31820@suse.de>
In-Reply-To: <20011120200144.W31820@suse.de>; from axboe@suse.de on Tue, Nov 20, 2001 at 08:01:44PM +0100

On Tue, Nov 20, 2001 at 08:01:44PM +0100, Jens Axboe wrote:
> On Mon, Nov 19 2001, Bill Currie wrote:
> > I'm trying to get a DS20 with a Mylex DAC960 up-and-running (boots just fine
> > off the ide drive:) but when I modprobe DAC960, I get the following oops
> > (while ksymoops is moaning about symbols etc, I got the symbols from the exact
> > kernel running (infact, I think it's /still/ running:)):
> 
> DAC960 calls blk_cleanup_queue on a un-initialized queue, tell Leonard.

Thanks, and I'll try to do that once I've got things sorted (I discovered the
root cause of the problem was unsupported firmware version, though the oops is
unacceptable anyway:).

My current problem is finding out whether I can just pop in new roms with the
3.51 firmware and still have the DEC SRM software still work
(KZPSC-UX/KZPAC-XF). The needed sockets are there on the main board but that
doesn't mean the DEC firmware will work with 3.51 (the current firmware is
2.49).

      reply	other threads:[~2001-11-20 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 18:44 DAC960 oops Bill Currie
2001-11-20 19:01 ` Jens Axboe
2001-11-20 22:59   ` Bill Currie [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=20011120155955.E15561@wirelessmatrixcorp.com \
    --to=billc@wirelessmatrixcorp.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnz@dandelion.com \
    /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