linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Annessi <robert@annessi.at>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: dc395x: Report
Date: Thu, 03 Aug 2006 01:24:08 +0200	[thread overview]
Message-ID: <44D13418.2000005@annessi.at> (raw)
In-Reply-To: <Pine.LNX.4.60.0608022348570.12263@poirot.grange>

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

On 08/03/06 00:07, Guennadi Liakhovetski wrote:
> On Wed, 2 Aug 2006, Robert Annessi wrote:
> 
>> BUG: warning at drivers/scsi/dc395x.c:2329/data_in_phase0()
>>  [<f884c768>] data_in_phase0+0x190/0x244 [dc395x]
>>  [<f884c15e>] dc395x_handle_interrupt+0xf7/0x128 [dc395x]
>>  [<f884c1c0>] dc395x_interrupt+0x31/0x5f [dc395x]
>>  [<c0137975>] handle_IRQ_event+0x21/0x49
>>  [<c0137a2e>] __do_IRQ+0x91/0xef
>>  [<c0104a2f>] do_IRQ+0x43/0x50
>>  [<c01032aa>] common_interrupt+0x1a/0x20
> 
> Would be interesting to find out what exactly causes these warnings. Could 
> you, please, try the patch at the bottom of this email with 2.6.18-rc3 and 
> see if the message it prints appears in dmesg - together with the NO_TAGQ 
> warkaround and without safe=1.


dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
PCI: setting IRQ 11 as level-triggered
PCI: Found IRQ 11 for device 0000:00:02.0
dc395x: Used settings: AdapterID=07, Speed=0(20.0MHz), dev_mode=0x37
dc395x:                AdaptMode=0x4e, Tags=0(01), DelayReset=1s
dc395x: (Wide) Connectors: int68  Termination: Auto Low High
dc395x: Performing initial SCSI bus reset
scsi0 : Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
dc395x: Target 00: Wide16 Sync: 48ns Offset 15 (41.7 MB/s)
  Vendor: SEAGATE   Model: ST3146807LC       Rev: 0007
  Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sda: 286749488 512-byte hdwr sectors (146816 MB)
dc395x: inconsistent counters: FIFOCNT 64, left 16777215, wide
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
dc395x: inconsistent counters: FIFOCNT 64, left 16777215, wide
SCSI device sda: drive cache: write back w/ FUA
SCSI device sda: 286749488 512-byte hdwr sectors (146816 MB)
dc395x: inconsistent counters: FIFOCNT 64, left 16777215, wide
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
dc395x: inconsistent counters: FIFOCNT 64, left 16777215, wide
SCSI device sda: drive cache: write back w/ FUA
 sda: unknown partition table
sd 0:0:0:0: Attached scsi disk sda


> Well, this looks much better to me. So, I think, we may say for you the 
> problem is solved. Globally, I think, the reason why other drivers have no 

For me the problem is definetely solved. Thank you!


> problems with this drive is because they are using results of the generic 
> inquiry evaluation code, and it chooses better communication parameters 
> than the dc395x. Would be nice to switch dc395x to do that too.

Unfortunately I don't have the skills for that - as you probably already
noticed. (;

Hopefully someone else is willing to adapt the driver.

Regards,
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2006-08-02 23:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 11:54 dc395x: Report Robert Annessi
2006-08-01 23:24 ` Guennadi Liakhovetski
2006-08-02  9:35   ` Robert Annessi
2006-08-02  9:51   ` Robert Annessi
2006-08-02 10:11     ` Guennadi Liakhovetski
2006-08-02 14:52       ` Robert Annessi
2006-08-02 22:07         ` Guennadi Liakhovetski
2006-08-02 23:24           ` Robert Annessi [this message]
2006-08-12 18:06             ` Guennadi Liakhovetski
2006-08-13 18:35               ` Robert Annessi
2006-08-13 19:47                 ` Guennadi Liakhovetski
2006-08-14 15:01                   ` Robert Annessi
2006-08-17 20:57                     ` Guennadi Liakhovetski

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=44D13418.2000005@annessi.at \
    --to=robert@annessi.at \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-scsi@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).