From: Jamie Lenehan <lenehan@twibble.org>
To: Quercus <quercus@nosomos.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: dc395 with a scanner, failing.
Date: Thu, 3 Jun 2004 19:08:49 +1000 [thread overview]
Message-ID: <20040603090849.GA6148@twibble.org> (raw)
In-Reply-To: <40B4CA83.8020700@nosomos.org>
On Wed, May 26, 2004 at 06:49:07PM +0200, Quercus wrote:
> Hi there... I own a dc395 scsi card "working" on a Debian GNU/Linux 3.0,
> with kernels 2.4.22 and 2.6.5.
So it works fine in 2.6.5 and not 2.6.6? I'll have to look at what
other changes went in between those versions.
[...]
> What other tests should I do to send some feedback to the list and try
> to find a solution? Anyone had this same problem?
Edit the top of drivers/scsi/dc395x.c and uncomment the first
"#define DEBUG_MASK" line, rebuild the dc395x module, reload the
module and then the operation that failes again. You should then gets
lots of debugging output in one of your log file which you can then
gzip or bzip2 and then send directly to me and I'll take a look at
it.
Thanks.
Jamie.
--
Jamie Lenehan <lenehan@twibble.org>
prev parent reply other threads:[~2004-06-03 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 16:49 dc395 with a scanner, failing Quercus
2004-06-03 9:08 ` Jamie Lenehan [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=20040603090849.GA6148@twibble.org \
--to=lenehan@twibble.org \
--cc=linux-scsi@vger.kernel.org \
--cc=quercus@nosomos.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