* [parisc-linux] b2k scsi disk pb
@ 2004-02-20 17:56 Joel Soete
2004-02-20 19:07 ` M. Grabert
0 siblings, 1 reply; 6+ messages in thread
From: Joel Soete @ 2004-02-20 17:56 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: parisc-linux
Hi Matthew,
I trust that you could advise me about this pb:
on my b2k since I can run 2.6 (32bit with gcc-3.3 or 64bit with gcc-3.0)
i noticed from time to time such dmesg:
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: ABORT operation started.
sym0:5:0: ABORT operation timed-out.
sym0:5:0: DEVICE RESET operation started.
sym0:5:0: DEVICE RESET operation timed-out.
sym0:5:0: BUS RESET operation started.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0:5:0: BUS RESET operation complete.
and during this time the system naturaly hang.
scsi id 5 is the one of the working boot disk (a quantum model atlas5-9lvd)
and if there is well a second disk (a seagate model ST336704LC) it is not
used.
OTC with 2.4 and sym2 driver, I never noticed this behavior (even with recent
2.4.25-rc?-pa0 :) ), so I presume that there is no disk failure (and a dd
if=/dev/sda of=/dev/null bs=1024k reach to read fully the disk without any
error).
Any idea?
Thanks in advance,
Joel
----------------------------------------------------------------------------------------
Tiscali ADSL: 19,50 €/mois, pendant 3 mois! L'Internet rapide, c'est pour
tout le monde.
http://reg.tiscali.be/default.asp?lg=fr
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [parisc-linux] b2k scsi disk pb
2004-02-20 17:56 [parisc-linux] b2k scsi disk pb Joel Soete
@ 2004-02-20 19:07 ` M. Grabert
2004-02-21 18:13 ` Joel Soete
2004-02-22 3:23 ` Grant Grundler
0 siblings, 2 replies; 6+ messages in thread
From: M. Grabert @ 2004-02-20 19:07 UTC (permalink / raw)
To: Joel Soete; +Cc: Matthew Wilcox, parisc-linux
On Fri, 20 Feb 2004, Joel Soete wrote:
> on my b2k since I can run 2.6 (32bit with gcc-3.3 or 64bit with gcc-3.0)
> i noticed from time to time such dmesg:
> sym0:5:0: ABORT operation timed-out.
> sym0:5:0: ABORT operation started.
[...]
> sym0:5:0: ABORT operation timed-out.
> sym0:5:0: DEVICE RESET operation started.
> sym0:5:0: DEVICE RESET operation timed-out.
> sym0:5:0: BUS RESET operation started.
> sym0: SCSI BUS reset detected.
> sym0: SCSI BUS has been reset.
> sym0:5:0: BUS RESET operation complete.
>
> and during this time the system naturaly hang.
(or is at least *very* slow)
> scsi id 5 is the one of the working boot disk (a quantum model atlas5-9lvd)
> and if there is well a second disk (a seagate model ST336704LC) it is not
> used.
Had the same problem when attaching a SE-SCSI device (also a Seagate, 20GB)
on my C3k (which has 2 internal LVD SCSI-drives).
Got rid of it by not using the SE-SCSI driver ;)
Try to physically detach the (not-used) ST336704LC.
> OTC with 2.4 and sym2 driver, I never noticed this behavior (even with recent
> 2.4.25-rc?-pa0 :) ), so I presume that there is no disk failure (and a dd
> if=/dev/sda of=/dev/null bs=1024k reach to read fully the disk without any
> error).
Yes, I think reading is fine, just (lots of) writing is triggering it.
Max
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [parisc-linux] b2k scsi disk pb
2004-02-20 19:07 ` M. Grabert
@ 2004-02-21 18:13 ` Joel Soete
2004-02-22 3:23 ` Grant Grundler
1 sibling, 0 replies; 6+ messages in thread
From: Joel Soete @ 2004-02-21 18:13 UTC (permalink / raw)
To: M. Grabert; +Cc: Matthew Wilcox, parisc-linux
M. Grabert wrote:
> On Fri, 20 Feb 2004, Joel Soete wrote:
>
>
>>on my b2k since I can run 2.6 (32bit with gcc-3.3 or 64bit with gcc-3.0)
>>i noticed from time to time such dmesg:
>>sym0:5:0: ABORT operation timed-out.
>>sym0:5:0: ABORT operation started.
>
>
> [...]
>
>
>>sym0:5:0: ABORT operation timed-out.
>>sym0:5:0: DEVICE RESET operation started.
>>sym0:5:0: DEVICE RESET operation timed-out.
>>sym0:5:0: BUS RESET operation started.
>>sym0: SCSI BUS reset detected.
>>sym0: SCSI BUS has been reset.
>>sym0:5:0: BUS RESET operation complete.
>>
>>and during this time the system naturaly hang.
>
>
> (or is at least *very* slow)
>
hmm for me everything stop: ls, top, ... every cmd are pending.
>
>>scsi id 5 is the one of the working boot disk (a quantum model atlas5-9lvd)
>>and if there is well a second disk (a seagate model ST336704LC) it is not
>>used.
>
>
> Had the same problem when attaching a SE-SCSI device (also a Seagate, 20GB)
> on my C3k (which has 2 internal LVD SCSI-drives).
>
> Got rid of it by not using the SE-SCSI driver ;)
> Try to physically detach the (not-used) ST336704LC.
>
It is an internal disk also but as I don't use it any more, I can try to remove it ;)
>
>>OTC with 2.4 and sym2 driver, I never noticed this behavior (even with recent
>>2.4.25-rc?-pa0 :) ), so I presume that there is no disk failure (and a dd
>>if=/dev/sda of=/dev/null bs=1024k reach to read fully the disk without any
>>error).
>
>
> Yes, I think reading is fine, just (lots of) writing is triggering it.
Max, thanks for advise,
Joel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [parisc-linux] b2k scsi disk pb
2004-02-20 19:07 ` M. Grabert
2004-02-21 18:13 ` Joel Soete
@ 2004-02-22 3:23 ` Grant Grundler
1 sibling, 0 replies; 6+ messages in thread
From: Grant Grundler @ 2004-02-22 3:23 UTC (permalink / raw)
To: M. Grabert; +Cc: Matthew Wilcox, parisc-linux
On Fri, Feb 20, 2004 at 07:07:19PM +0000, M. Grabert wrote:
>
> > sym0:5:0: ABORT operation timed-out.
> > sym0:5:0: DEVICE RESET operation started.
> > sym0:5:0: DEVICE RESET operation timed-out.
> > sym0:5:0: BUS RESET operation started.
> > sym0: SCSI BUS reset detected.
> > sym0: SCSI BUS has been reset.
> > sym0:5:0: BUS RESET operation complete.
> >
> > and during this time the system naturaly hang.
The "hang" is because no IO's are processed until 3 seconds
after the BUS RESET is issued.
> Got rid of it by not using the SE-SCSI driver ;)
> Try to physically detach the (not-used) ST336704LC.
I was pretty sure "LC" suffix meant LVD with SCA 80 pin connector.
Specs on seagate.com are easy to find if you know the model.
If both internal devices are LVD, check early sym2 dmesg output
to verify the SCSI bus is operating in LVD mode (vs SE).
grant
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [parisc-linux] b2k scsi disk pb
@ 2004-02-23 8:16 Joel Soete
2004-02-24 16:11 ` Grant Grundler
0 siblings, 1 reply; 6+ messages in thread
From: Joel Soete @ 2004-02-23 8:16 UTC (permalink / raw)
To: Grant Grundler, M. Grabert; +Cc: Matthew Wilcox, parisc-linux
Hello Grant,
>The "hang" is because no IO's are processed until 3 seconds
>after the BUS RESET is issued.
Typicaly the behaviour observed.
>> Got rid of it by not using the SE-SCSI driver ;)
>> Try to physically detach the (not-used) ST336704LC.
>
>I was pretty sure "LC" suffix meant LVD with SCA 80 pin connector.
>Specs on seagate.com are easy to find if you know the model.
In fact according <http://www.seagate.com/cgi-bin/view.cgi?/scsi/st336704.lw>
it has the two possiblity SE or LVD according HW config (a side jumper J2
if i well understand)
>If both internal devices are LVD, check early sym2 dmesg output
>to verify the SCSI bus is operating in LVD mode (vs SE).
But here they seems to work together in LVD mode:
[snip]
Uniform CD-ROM driver Revision: 3.20
sym0: <895a> rev 0x1 at pci 0000:00:0f.0 irq 129
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18i
sym0:0:0: ABORT operation started.
sym0:0:0: ABORT opera
ion complete.
sym0:0:0: DEVICE RESET operation started.
sym0:0:0: DEVICE RESET operation failed.
sym0:0:0: BUS RESET operation started.
sym0:0:0: BUS RESET operation failed.
sym0:0:0: HOST RESET operation started.
sym0:0:0: HOST RESET operation failed.
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 0 lun 0
Vendor: QUANTUM Model: ATLAS5-9LVD Rev: HP04
Type: Direct-Access ANSI SCSI revision: 03
sym0:5:0: tagged command queuing enabled, command queue depth 16.
sym0:5: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: SEAGATE Model: ST336704LC Rev: HP03
Type: Direct-Access ANSI SCSI revision: 03
sym0:6:0: tagged command queuing enabled, command queue depth 16.
sym0:6: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
[snip]
Anyway what sym2 look for at scsi id 0?
I will try also later to remove ST disk ad advise ;)
Thanks for attention and advise,
Joel
----------------------------------------------------------------------------------------
Tiscali ADSL: 19,50 €/mois, pendant 3 mois! L'Internet rapide, c'est pour
tout le monde.
http://reg.tiscali.be/default.asp?lg=fr
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [parisc-linux] b2k scsi disk pb
2004-02-23 8:16 Joel Soete
@ 2004-02-24 16:11 ` Grant Grundler
0 siblings, 0 replies; 6+ messages in thread
From: Grant Grundler @ 2004-02-24 16:11 UTC (permalink / raw)
To: Joel Soete; +Cc: parisc-linux
On Mon, Feb 23, 2004 at 09:16:16AM +0100, Joel Soete wrote:
> In fact according <http://www.seagate.com/cgi-bin/view.cgi?/scsi/st336704.lw>
> it has the two possiblity SE or LVD according HW config (a side jumper J2
> if i well understand)
Ah ok. They have a jumper to force SE signalling.
> >If both internal devices are LVD, check early sym2 dmesg output
> >to verify the SCSI bus is operating in LVD mode (vs SE).
>
> But here they seems to work together in LVD mode:
Right. means the jumper is not connected and something else is wrong.
> Anyway what sym2 look for at scsi id 0?
It's just the first one.
SCSI scans from ID 0 to 15 to find devices.
grant
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-02-24 16:11 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-20 17:56 [parisc-linux] b2k scsi disk pb Joel Soete
2004-02-20 19:07 ` M. Grabert
2004-02-21 18:13 ` Joel Soete
2004-02-22 3:23 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 8:16 Joel Soete
2004-02-24 16:11 ` Grant Grundler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox