Re: [patch 02/23] nsp32_restart_autoscsi(): remove error check

2007-11-22 Thread Adrian Bunk
AFAIR, this was the nsp32_msg() James wanted to keep, and the patch 
should therefore be dropped.

cu
Adrian


On Wed, Nov 21, 2007 at 03:12:15PM -0800, [EMAIL PROTECTED] wrote:
 From: Adrian Bunk [EMAIL PROTECTED]
 
 The Coverity checker noted that we'll anyway Oops later when we ran into
 this condition - and the error check didn't prevent that.
 
 Considering that the error condition shouldn't be possible, and we are
 not able to handle it easily, this patch simply removes the pointless
 error check.
 
 Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Signed-off-by: Andrew Morton [EMAIL PROTECTED]
 ---
 
  drivers/scsi/nsp32.c |4 
  1 file changed, 4 deletions(-)
 
 diff -puN drivers/scsi/nsp32.c~nsp32_restart_autoscsi-remove-error-check 
 drivers/scsi/nsp32.c
 --- a/drivers/scsi/nsp32.c~nsp32_restart_autoscsi-remove-error-check
 +++ a/drivers/scsi/nsp32.c
 @@ -1906,10 +1906,6 @@ static void nsp32_restart_autoscsi(struc
  
   nsp32_dbg(NSP32_DEBUG_RESTART, enter);
  
 - if (data-cur_target == NULL || data-cur_lunt == NULL) {
 - nsp32_msg(KERN_ERR, Target or Lun is invalid);
 - }
 -
   /*
* set SYNC_REG
* Don't set BM_START_ADR before setting this register.
 _

-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc3-mm1

2007-11-22 Thread Gabriel C
I have some warnings on each SCSI disc:


...

[   30.724410] scsi 0:0:0:0: Direct-Access SEAGATE  ST318406LW   0109 
PQ: 0 ANSI: 3
[   30.724419] scsi0:A:0:0: Tagged Queuing enabled.  Depth 32
[   30.724435]  target0:0:0: Beginning Domain Validation
[   30.724446]  target0:0:0: Domain Validation Initial Inquiry Failed --
[   30.724572]  target0:0:0: Ending Domain Validation
[   30.729747] scsi 0:0:1:0: Direct-Access FUJITSU  MAH3182MP0114 
PQ: 0 ANSI: 4
[   30.729754] scsi0:A:1:0: Tagged Queuing enabled.  Depth 32
[   30.729771]  target0:0:1: Beginning Domain Validation
[   30.729780]  target0:0:1: Domain Validation Initial Inquiry Failed --
[   30.729908]  target0:0:1: Ending Domain Validation

...

no idea whatever this is related but buffered disk reads are 2.XX MB/sec and 
the box is somewhat laggy.

hdparm -t on sda and sdb reports :

/dev/sda:
 Timing buffered disk reads:8 MB in  3.26 seconds =   2.46 MB/sec

/dev/sdb:
 Timing buffered disk reads:8 MB in  3.56 seconds =   2.25 MB/sec

My IDE discs are fine.

Please let me know if you need my config or any other informations.


Gabriel
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc3-mm1

2007-11-22 Thread Andrew Morton
On Fri, 23 Nov 2007 02:39:08 +0100 Gabriel C [EMAIL PROTECTED] wrote:

 I have some warnings on each SCSI disc:
 
 
 ...
 
 [   30.724410] scsi 0:0:0:0: Direct-Access SEAGATE  ST318406LW   0109 
 PQ: 0 ANSI: 3
 [   30.724419] scsi0:A:0:0: Tagged Queuing enabled.  Depth 32
 [   30.724435]  target0:0:0: Beginning Domain Validation
 [   30.724446]  target0:0:0: Domain Validation Initial Inquiry Failed --
 [   30.724572]  target0:0:0: Ending Domain Validation
 [   30.729747] scsi 0:0:1:0: Direct-Access FUJITSU  MAH3182MP0114 
 PQ: 0 ANSI: 4
 [   30.729754] scsi0:A:1:0: Tagged Queuing enabled.  Depth 32
 [   30.729771]  target0:0:1: Beginning Domain Validation
 [   30.729780]  target0:0:1: Domain Validation Initial Inquiry Failed --
 [   30.729908]  target0:0:1: Ending Domain Validation
 

Don't know what would have caused that.  But yes, something is wrong in
scsi land.

 
 no idea whatever this is related but buffered disk reads are 2.XX MB/sec and 
 the box is somewhat laggy.
 
 hdparm -t on sda and sdb reports :
 
 /dev/sda:
  Timing buffered disk reads:8 MB in  3.26 seconds =   2.46 MB/sec
 
 /dev/sdb:
  Timing buffered disk reads:8 MB in  3.56 seconds =   2.25 MB/sec
 
 My IDE discs are fine.
 
 Please let me know if you need my config or any other informations.
 

And you're the second to report very slow scsi throughput in 2.6.24-rc3-mm1.
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc3-mm1: I/O error, system hangs

2007-11-22 Thread Laurent Riffard

Le 21.11.2007 23:41, Andrew Morton a écrit :
 On Wed, 21 Nov 2007 22:45:22 +0100
 Laurent Riffard [EMAIL PROTECTED] wrote:
 
 Le 21.11.2007 05:45, Andrew Morton a écrit :
 ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/
 Hello, 

 My system hangs shortly after I logged in Gnome desktop. SysRq-W shows
 that a bunch of task are blocked in D state, they seem to wait for
 some I/O completion. I can try to hand-copy some data if requested.

 I found these messages in dmesg:

 ~$ grep -C2 end_request dmesg-2.6.24-rc3-mm1 
 EXT3-fs: mounted filesystem with ordered data mode.
 sd 0:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT 
 driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sda, sector 16460
 ReiserFS: sda7: found reiserfs format 3.6 with standard journal
 ReiserFS: sda7: using ordered data mode
 --
 ReiserFS: sda7: Using r5 hash to sort names
 sd 0:0:1:0: [sdb] Result: hostbyte=DID_NO_CONNECT 
 driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdb, sector 19632
 sd 0:0:1:0: [sdb] Result: hostbyte=DID_NO_CONNECT 
 driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdb, sector 40037363
 Adding 1048568k swap on /dev/mapper/vglinux1-lvswap.  Priority:-1 extents:1 
 across:1048568k
 lp0: using parport0 (interrupt-driven).

 These errors occur *only* with 2.6.24-rc3-mm1, they are 100% reproducible.
 2.6.24-rc3 and 2.6.24-rc2-mm1 are fine.

 Maybe something is broken in pata_via driver ?

 
 Could be - 
 libata-reimplement-ata_acpi_cbl_80wire-using-ata_acpi_gtm_xfermask.patch
 and 
 pata_amd-pata_via-de-couple-programming-of-pio-mwdma-and-udma-timings.patch
 touch pata_via.c.

None of the above...

I did a bisection, it spotted git-scsi-misc.patch. 
I just run 2.6.24-rc3-mm1 + revert-git-scsi-misc.patch, and it works fine.

I guess commit 8655a546c83fc43f0a73416bbd126d02de7ad6c0 [SCSI] Do not 
requeue requests if REQ_FAILFAST is set is the real culprit. The other 
commits are touching documentation or drivers I don't use. I'll try 
to revert only this one this evening.

-- 
laurent


-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc3-mm1

2007-11-22 Thread Gabriel C
Andrew Morton wrote:
 On Fri, 23 Nov 2007 02:39:08 +0100 Gabriel C [EMAIL PROTECTED] wrote:
 
 I have some warnings on each SCSI disc:


 ...

 [   30.724410] scsi 0:0:0:0: Direct-Access SEAGATE  ST318406LW   
 0109 PQ: 0 ANSI: 3
 [   30.724419] scsi0:A:0:0: Tagged Queuing enabled.  Depth 32
 [   30.724435]  target0:0:0: Beginning Domain Validation
 [   30.724446]  target0:0:0: Domain Validation Initial Inquiry Failed --
 [   30.724572]  target0:0:0: Ending Domain Validation
 [   30.729747] scsi 0:0:1:0: Direct-Access FUJITSU  MAH3182MP
 0114 PQ: 0 ANSI: 4
 [   30.729754] scsi0:A:1:0: Tagged Queuing enabled.  Depth 32
 [   30.729771]  target0:0:1: Beginning Domain Validation
 [   30.729780]  target0:0:1: Domain Validation Initial Inquiry Failed --
 [   30.729908]  target0:0:1: Ending Domain Validation

 
 Don't know what would have caused that.  But yes, something is wrong in
 scsi land.

Actually I'm lucky the author didn't fix that FIXME in scsi_transport_spi.c and 
I still can boot ;)

 
 no idea whatever this is related but buffered disk reads are 2.XX MB/sec and 
 the box is somewhat laggy.

 hdparm -t on sda and sdb reports :

 /dev/sda:
  Timing buffered disk reads:8 MB in  3.26 seconds =   2.46 MB/sec

 /dev/sdb:
  Timing buffered disk reads:8 MB in  3.56 seconds =   2.25 MB/sec

 My IDE discs are fine.

 Please let me know if you need my config or any other informations.

 
 And you're the second to report very slow scsi throughput in 2.6.24-rc3-mm1.
 

I found the commit which cause these problems , it is in git-scsi-misc patch 
and reverting it fixes both problems for me.

http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commitdiff_plain;h=8655a546c83fc43f0a73416bbd126d02de7ad6c0;hp=5bc717b6bdaaf52edf365eb7d9d8c89fec79df5d


-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: 2.6.24-rc3-mm1: I/O error, system hangs

2007-11-22 Thread Hannes Reinecke
Laurent Riffard wrote:
 Le 21.11.2007 23:41, Andrew Morton a écrit :
 On Wed, 21 Nov 2007 22:45:22 +0100
 Laurent Riffard [EMAIL PROTECTED] wrote:

 Le 21.11.2007 05:45, Andrew Morton a écrit :
 ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc3/2.6.24-rc3-mm1/
 Hello, 

 My system hangs shortly after I logged in Gnome desktop. SysRq-W shows
 that a bunch of task are blocked in D state, they seem to wait for
 some I/O completion. I can try to hand-copy some data if requested.

 I found these messages in dmesg:

 ~$ grep -C2 end_request dmesg-2.6.24-rc3-mm1 
 EXT3-fs: mounted filesystem with ordered data mode.
 sd 0:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT 
 driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sda, sector 16460
 ReiserFS: sda7: found reiserfs format 3.6 with standard journal
 ReiserFS: sda7: using ordered data mode
 --
 ReiserFS: sda7: Using r5 hash to sort names
 sd 0:0:1:0: [sdb] Result: hostbyte=DID_NO_CONNECT 
 driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdb, sector 19632
 sd 0:0:1:0: [sdb] Result: hostbyte=DID_NO_CONNECT 
 driverbyte=DRIVER_OK,SUGGEST_OK
 end_request: I/O error, dev sdb, sector 40037363
 Adding 1048568k swap on /dev/mapper/vglinux1-lvswap.  Priority:-1 extents:1 
 across:1048568k
 lp0: using parport0 (interrupt-driven).

 These errors occur *only* with 2.6.24-rc3-mm1, they are 100% reproducible.
 2.6.24-rc3 and 2.6.24-rc2-mm1 are fine.

 Maybe something is broken in pata_via driver ?

 Could be - 
 libata-reimplement-ata_acpi_cbl_80wire-using-ata_acpi_gtm_xfermask.patch
 and 
 pata_amd-pata_via-de-couple-programming-of-pio-mwdma-and-udma-timings.patch
 touch pata_via.c.
 
 None of the above...
 
 I did a bisection, it spotted git-scsi-misc.patch. 
 I just run 2.6.24-rc3-mm1 + revert-git-scsi-misc.patch, and it works fine.
 
 I guess commit 8655a546c83fc43f0a73416bbd126d02de7ad6c0 [SCSI] Do not 
 requeue requests if REQ_FAILFAST is set is the real culprit. The other 
 commits are touching documentation or drivers I don't use. I'll try 
 to revert only this one this evening.
 
Hmm. Weird. I'll have a look into it. Apparently I'll be returning an error 
where
I shouldn't. Checking ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke   zSeries  Storage
[EMAIL PROTECTED] +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html