archive mirror
 help / color / mirror / Atom feed
From: Kurt Garloff <>
To: Oliver Feiler <>
Subject: Re: Need help with diagnosing SCSI related (probably hardware?) problem (DC395 driver)
Date: Mon, 1 Dec 2003 16:39:16 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]


On Mon, Dec 01, 2003 at 12:08:39PM +0100, Oliver Feiler wrote:
Content-Description: signed data
> CC'ing to Kurt Garloff since he wrote the driver initially and might be the 
> best person to ask what the syslog output means. Are you still maintaining 
> the DC395 driver, Kurt, or has someone else taken maintainership in the 
> meantime?

For 2.6, Oliver Neukum and others have picked up the driver.
I maintain the 2.4 version still.

> Small followup to the described problem. I managed to get a "screenshot" from 
> the kernel's syslog output. Indeed the driver is queueing endless SCSI resets 
> with little success. These two pages (some parts may be missing. Taken with a 
> digital camera) scroll over the screen endlessly. Can someone tell me from 
> this what's going on and what it is causing the problem?
> (both 1024x768 ~100KB)

Hmm, it looks quite normal; the driver is trying to recover from errors.
Apparently the write10 (2a) timed out. Can you try to catch the first
error message? 

Kurt Garloff  <>                            Cologne, DE 
SUSE LINUX AG, Nuernberg, DE                          SUSE Labs (Head)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-12-01 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 22:38 Need help with diagnosing SCSI related (probably hardware?) problem (DC395 driver) Oliver Feiler
     [not found] ` <>
2003-12-01 15:39   ` Kurt Garloff [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).