From: Robert Annessi <robert@annessi.at>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: dc395x: Report
Date: Wed, 02 Aug 2006 11:35:36 +0200 [thread overview]
Message-ID: <44D071E8.8090001@annessi.at> (raw)
In-Reply-To: <Pine.LNX.4.60.0608020046510.8659@poirot.grange>
[-- Attachment #1: Type: text/plain, Size: 9073 bytes --]
On 08/02/06 01:24, Guennadi Liakhovetski wrote:
> On Tue, 1 Aug 2006, Robert Annessi wrote:
>>
>> The default settings of the module were not applicable for me.
>> When loading the module (or the driver builtin within the kernel) without any
>> additional arguments I got a bunch of these error messages:
>> "dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds"
>> (about 10 per second) and I was not able to access the disk.
>
> Ok, I think:
>
> 1) your _device_ is buggy. If you look in drivers/scsi/scsi_devinfo.c in
> scsi_static_device_list[] blask list, you'll find 2 more SEAGATE drives
> with problems with tagged commands. Try adding your drive to the list also
> with BLIST_NOTQ like
It's a decent drive I used with other controllers before - and it worked
out of the box. But maybe it's really a buggy drive..
> {"SEAGATE", "ST3146807LC", "0007", BLIST_NOTQ}
>
> or you can build dc395x as a module and before loading it add your device
> to /proc/scsi/device_info. Actually, you can even try it with your 2.6.16
> kernel, ...
>
> !!! Oh, no... dc395x doesn't use the generic blacklist table... Anyone to
> fix it? Until it is fixed you should forget the above and could try
> disabling it in the driver by either
>
> a) uncommenting the line
>
> #define DC395x_NO_TAGQ
>
> b) removing " | NTC_DO_TAG_QUEUEING" from dev mode from cfg_data
>
> c) some other dirty trick...
>
> 2) dc395x was not patched for 2.6.17, only for 2.6.18-rc*, so, would be
> quite interesting if you could test with that. We haven't had any reports
> with wide devices with this "help improve support" problem yet.
>
> 3) if you do get round to testing your system under 2.6.18-rcX, please
> first test with vanilla kernel without parameters, then with safe=1, then
> with your disk added to the blacklist (hacked dc395x.c) without and (if
> still needed) with safe=1. Please, send all (distinct) negotiation
> protocols from these tests.
Short answer: it works (more or less).
Long answer:
I tested it with a vanilla 2.6.18-rc3 and workaround a) "uncommenting
#define DC395x_NO_TAGQ in dc395x.c".
Notes:
"unknown partition table" is fine. The disk does not have a valid
partition table (dm-crypted the whole disk).
I wonder why the dc395x driver version is still the same as in 2.6.16..?
Anyway, the results are below.
Regards,
Robert
Vanilla module with no additional arguments:
<snip>
dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
PCI: Enabling device 0000:00:02.0 (0100 -> 0103)
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
scsi1 : 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
sda : READ CAPACITY failed.
sda : status=12, message=00, host=7, driver=00
sda : sense not available.
sda: test WP failed, assume Write Enabled
sda: asking for cache data failed
sda: assuming drive cache: write through
sda : READ CAPACITY failed.
sda : status=12, message=00, host=7, driver=00
sda : sense not available.
sda: test WP failed, assume Write Enabled
sda: asking for cache data failed
sda: assuming drive cache: write through
sda:<6>dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds
dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds
dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds
dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds
dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds
dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds
dc395x: QUEUE_FULL for dev <00-0> with 1 cmnds
<snap>
Vanilla module and safe=1:
<snip>
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: Using safe settings.
dc395x: Used settings: AdapterID=07, Speed=4(06.7MHz), dev_mode=0x09
dc395x: AdaptMode=0x0f, Tags=2(04), DelayReset=3s
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
Vendor: SEAGATE Model: ST3146807LC Rev: 0007
Type: Direct-Access ANSI SCSI revision: 03
SCSI device sda: 286749488 512-byte hdwr sectors (146816 MB)
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
SCSI device sda: drive cache: write back w/ FUA
SCSI device sda: 286749488 512-byte hdwr sectors (146816 MB)
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
SCSI device sda: drive cache: write back w/ FUA
sda: unknown partition table
sd 0:0:0:0: Attached scsi disk sda
<snap>
Module with NO_TAGQ workaround and no additional arguments:
<snip>
dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
PCI: Enabling device 0000:00:02.0 (0100 -> 0103)
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
scsi1 : 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)
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
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
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
SCSI device sda: drive cache: write back w/ FUA
SCSI device sda: 286749488 512-byte hdwr sectors (146816 MB)
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
[<c0100b10>] default_idle+0x0/0x59
[<c0100b41>] default_idle+0x31/0x59
[<c0100c25>] cpu_idle+0xa8/0xcf
[<c03c07b7>] start_kernel+0x1b6/0x1b8
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
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
[<c0100b10>] default_idle+0x0/0x59
[<c0100b41>] default_idle+0x31/0x59
[<c0100c25>] cpu_idle+0xa8/0xcf
[<c03c07b7>] start_kernel+0x1b6/0x1b8
SCSI device sda: drive cache: write back w/ FUA
sda: unknown partition table
sd 1:0:0:0: Attached scsi disk sda
<snap>
Module with NO_TAGQ workaround and safe=1:
<snip>
dc395x: Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
PCI: Enabling device 0000:00:02.0 (0100 -> 0103)
PCI: Found IRQ 11 for device 0000:00:02.0
dc395x: Using safe settings.
dc395x: Used settings: AdapterID=07, Speed=4(06.7MHz), dev_mode=0x09
dc395x: AdaptMode=0x0f, Tags=2(04), DelayReset=3s
dc395x: (Wide) Connectors: int68 Termination: Auto Low High
dc395x: Performing initial SCSI bus reset
scsi2 : Tekram DC395(U/UW/F), DC315(U) - ASIC TRM-S1040 v2.05, 2004/03/08
Vendor: SEAGATE Model: ST3146807LC Rev: 0007
Type: Direct-Access ANSI SCSI revision: 03
SCSI device sda: 286749488 512-byte hdwr sectors (146816 MB)
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
SCSI device sda: drive cache: write back w/ FUA
SCSI device sda: 286749488 512-byte hdwr sectors (146816 MB)
sda: Write Protect is off
sda: Mode Sense: ab 00 10 08
SCSI device sda: drive cache: write back w/ FUA
sda: unknown partition table
sd 2:0:0:0: Attached scsi disk sda
<snap>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2006-08-02 9:35 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 [this message]
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
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=44D071E8.8090001@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.