RE: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Ada pter

RE: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Ada pter

[SUPPORT]

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

Hi Guys,

I've been seeing problems with various tape drives and PPR. And a SCSI 3 SE
disk is interesting as well! SE and PPR don't get on too well;) The problems
we are seeing are generally indicated by a "phase change 6-7" error. And I
know there are others who have had problems from various messages on this
list

This wouldn't be too much of a problem but rather than then reverting to
using legacy sync and wide it just keeps trying PPR - for ever as far as I
can make out. And the drives struggle on using async;(

The following may help as a temporary fix for those who are desperate. We
are using this while we get on with higher priority items and we find time
to look at it more closely.

--- 2.6.9a/drivers/scsi/scsi_scan.c	2004-10-11 03:58:24.000000000 +0100
+++ 2.6.9b/drivers/scsi/scsi_scan.c	2004-11-04 12:20:09.000000000 +0000
@@ -578,7 +578,7 @@
 	sdev->lockable = sdev->removable;
 	sdev->soft_reset = (inq_result[7] & 1) && ((inq_result[3] & 7) ==
2);
 
-	if (sdev->scsi_level >= SCSI_3 || (sdev->inquiry_len > 56 &&
+	if (/*sdev->scsi_level >= SCSI_3 ||*/ (sdev->inquiry_len > 56 &&
 		inq_result[56] & 0x04))
 		sdev->ppr = 1;
 	if (inq_result[7] & 0x60)

Using this all the drives I've tried that normally use PPR still use PPR.
The drives that do not support PPR no longer cause problems - PPR is no
longer sent to these problem drives.

Matthew - I have attached some bits of SCSI analyser traces which I hope may
be useful. An IBM SCSI 3 SE disk and a couple of LTO tape drives - IBM and
HP. The HP causes severe problems as modprobe hangs without the fix. I have
also seen drives that do unexpected disconnects if they get sent PPR.

Sorry no logs from linux/sym53c8xx - I may be can find some if you want to
see whats happening there.

I have been toying with the idea of disabling PPR capability if PPR is
rejected - forcing sdev->ppr=0 in the driver when it determines PPR has been
rejected - but I'm not sure that's right. There are drives which reject
negotiation - legacy sync and wide at least - while they are initialising
but will then accept it later on.

Question - where does the full source for the sym53c8xx_2 driver live these
days now that Gerard no long maintains it?


Regards
Richard


Richard Waltham
Bridgeworks Ltd
135 Somerford Road,
Christchurch
Dorset, BH23 3PY
England.

Tel 0870 121 0708
Fax 0870 121 0709

Email: richardw@4bridgeworks.com



> -----Original Message-----
> From: Matthew Wilcox [mailto:matthew@wil.cx]
> Sent: 05 November 2004 13:44
> To: Thomas Babut
> Cc: linux-kernel@vger.kernel.org; Linux SCSI; matthew@wil.cx;
> groudier@free.fr
> Subject: Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI
> Adapter
> 
> 
> On Fri, Nov 05, 2004 at 01:52:32PM +0100, Thomas Babut wrote:
> > Here I am again with some news. :)
> 
> Um, again?  This is the first I've heard from you.  BTW, 
> Gerard seems to
> be unreachable, which is why I took over the driver.
> 
> > I tried last night Kernel 2.6.0 and 2.6.1 (both vanilla) 
> and the system 
> > bootet up with the controller! Then I tried this:
> > 
> > 1) unpack vanilla Kernel 2.6.9
> > 2) copy drivers/scsi/sym53c8xx_comm.h, 
> drivers/scsi/sym53c8xx_defs.h and 
> > the whole directory drivers/scsi/sym53c8xx_2/* from Kernel 
> 2.6.1 into 
> > the Kernel 2.6.9 source
> > 
> > It booted, too. But on all this three 2.6 Kernels the 
> SCSI-Harddisk has 
> > got very poor performance. With Kernel 2.4.26 and 2.4.27 it 
> makes almost 
> > 30 MB/s. With all three 2.6 Kernels it makes about 5 MB/s.
> 
> Sounds like your drive isn't negotiating the correct transfer rate.
> If it's able to do 30MB/s, I guess it should be negotiating at least
> wide, 20MHz -- 5MB/s sounds like asynchronous.
> 
> > (see 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=109953598029428&w=2 
> > for detailed hardware specs and other informations)
> 
> Hrm.  Domain validation is failing.  I bet what's going on is that the
> controller is U160-capable, so we're sending a PPR message to 
> the drive
> which is going haywire.  I do hope we don't have to start blacklisting
> drives as being PPR-incapable.
> 
> Can you turn on negotiation debugging and send me the result?  If you
> have 2.1.18m, that's sym53c8xx.debug=0x200 ... earlier than that, it's
> sym53c8xx=debug:0x200
> 
> Now ... you say:
> 
> > sym0: SCSI BUS reset detected.
> > sym0: SCSI BUS has been reset.
> > sym0: SCSI BUS operation completed.
> > 
> > At this point only a hard-reset helps.
> 
> Do you mean the machine freezes at this point, or you can't 
> boot because
> this drive has your root partition on it and it can't be 
> found?  If the
> former, this is another bug that needs to be fixed.
> 
> -- 
> "Next the statesmen will invent cheap lies, putting the blame upon 
> the nation that is attacked, and every man will be glad of those
> conscience-soothing falsities, and will diligently study 
> them, and refuse
> to examine any refutations of them; and thus he will by and 
> by convince 
> himself that the war is just, and will thank God for the better sleep 
> he enjoys after this process of grotesque self-deception." -- 
> Mark Twain
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


[-- Attachment #2: HP_LTO.txt --]
[-- Type: text/plain, Size: 2055 bytes --]

Protocol Phase Analysis
   File name: LINUX6.DTT
Marker range: ANCHOR(70) to CURRENT(96)
Session name: None
Session desc: None
 Session ids: iids:7 tid(lun)[devtype]:3(0)[1]
Sess filters: None
Session date: 2-Nov-04  10:38:58 - 10:41:03
NNNNN = Phase Event Number (1st event is 0)
SSS.mmm_uuu_nnn = Difference Time (Secs.milli_micro_nano)
NNNNN SSS.mmm_uuu_nnn
   70           3_300  Arb
   71           2_192  Arbwin 7
   72           0_800 +Select 7,3
   73           0_716 +Sel/Resel End
   74           4_060 +MsgOut C0 Identify
   75      14_066_128  CMD - Inquiry     
                        12 00 00 00 32 00
   76          18_660  DataIn (N)
                    0h: 01 80 03 02 2D 00 01 30 ....-..0
                    8h: 48 50 20 20 20 20 20 20 HP      
                   10h: 55 6C 74 72 69 75 6D 20 Ultrium 
                   18h: 31 2D 53 43 53 49 20 20 1-SCSI  
                   20h: 45 31 32 44 00 00 00 00 E12D....
                   28h: 00 00 00 24 44 52 2D 31 ...$DR-1
                   30h: 30 00                   0.
                       (50 Bytes)
   77       1_240_728  DEnd  50 Bytes
   78           1_460  Status 00 Good
   79           2_936  MsgIn  00 Cmd Complete
   80          67_264 Bus Free
   81           3_404  Arb
   82           2_188  Arbwin 7
   83           0_800 +Select 7,3
   84           0_708 +Sel/Resel End
   85         442_892 +MsgOut C0 Identify
                              01 06 04
                        Parallel Protocol Pw:?,off:?,Width:?,
                        flags:?
   86  20.000_481_056 +MsgIn  07 Msg Reject
   87         201_336 Bus Reset
   88  10.003_609_516 Bus Free
   89           3_504  Arb
   90           2_188  Arbwin 7
   91           0_804 +Select 7,3
   92           0_720 +Sel/Resel End
   93         249_068 +MsgOut C0 Identify
                              01 06 04
                        Parallel Protocol Pw:?,off:?,Width:?,
                        flags:?
   94  15.001_441_328 +MsgIn  07 Msg Reject
   95         201_704 Bus Reset
   96           0_000 Bus Free

[-- Attachment #3: IBM_DSK.txt --]
[-- Type: text/plain, Size: 2026 bytes --]

Protocol Phase Analysis
   File name: LINUX8.DTT
Marker range: ANCHOR(89) to CURRENT(101)
Session name: None
Session desc: None
 Session ids: iids:7 tid(lun)[devtype]:2(0)[0]
Sess filters: None
Session date: 2-Nov-04  12:56:07 - 12:58:54
NNNNN = Phase Event Number (1st event is 0)
SSS.mmm_uuu_nnn = Difference Time (Secs.milli_micro_nano)
NNNNN SSS.mmm_uuu_nnn
   89           3_304  Arb
   90           2_204  Arbwin 7
   91           1_000 +Select 7,2
   92           1_608 +Sel/Resel End
   93         268_012 +MsgOut C0 Identify
                              01 06 04 0A 00 00 01 00
                        Parallel Protocol Pw:25ns,
                        off:0,Width:16 bits,
                        IU=0 DT=0 QAS=0
   94          43_052  MsgIn  07 Msg Reject
   95         287_268  CMD - Inquiry     
                        12 00 00 00 A4 00
   96       6_890_292  DataIn (N)
                    0h: 00 00 03 02 9F 00 01 3A .......:
                    8h: 49 42 4D 20 20 20 20 20 IBM     
                   10h: 44 4E 45 53 2D 33 30 39 DNES-309
                   18h: 31 37 30 57 20 20 20 20 170W    
                   20h: 53 41 33 30 41 4A 31 33 SA30AJ13
                   28h: 4B 31 31 36 00 00 00 00 K116....
                   30h: 00 00 00 00 00 00 00 00 ........
                   38h: 00 00 00 00 00 00 00 00 ........
                   40h: 00 00 00 00 00 00 00 00 ........
                   48h: 00 00 00 00 00 00 00 00 ........
                   50h: 00 00 00 00 00 00 00 00 ........
                   58h: 00 00 00 00 00 00 00 00 ........
                   60h: 28 43 29 20 43 6F 70 79 (C) Copy
                   68h: 72 69 67 68 74 20 49 42 right IB
                   70h: 4D 20 43 6F 72 70 2E 20 M Corp. 
                   78h: 31 39 39 38 2E 20 41 6C 1998. Al
                       (128 Bytes)
   97         101_564  DEnd  164 Bytes  0.024 MB/S
   98           2_156  Status 00 Good
   99           2_520  MsgIn  00 Cmd Complete
  100          76_796 Bus Free
  101           0_000  Arb

[-- Attachment #4: IBM_LTO.txt --]
[-- Type: text/plain, Size: 1273 bytes --]

Protocol Phase Analysis
   File name: TREBER7.DTT
Marker range: ANCHOR(101) to CURRENT(113)
Session name: None
Session desc: None
 Session ids: iids:7 tid(lun)[devtype]:2(0)[1]
Sess filters: None
Session date: 18-Oct-04  15:04:24 - 15:06:33
NNNNN = Phase Event Number (1st event is 0)
SSS.mmm_uuu_nnn = Difference Time (Secs.milli_micro_nano)
NNNNN SSS.mmm_uuu_nnn
  101           3_300  Arb
  102           2_188  Arbwin 7
  103         198_808 +Select 7,2
  104          23_016 +Sel/Resel End
  105       1_752_620 +MsgOut C0 Identify
                              01 06
                        Extended Msg+Len
  106       4_837_064 +MsgIn  07 Msg Reject
  107       1_104_660  CMD - Inquiry     
                        12 00 00 00 26 00
  108           9_788  DataIn (N)
                    0h: 01 80 03 02 21 00 01 30 ....!..0
                    8h: 49 42 4D 20 20 20 20 20 IBM     
                   10h: 55 4C 54 33 35 38 30 2D ULT3580-
                   18h: 54 44 31 20 20 20 20 20 TD1     
                   20h: 31 38 4E 32 00 00       18N2..
                       (38 Bytes)
  109           4_440  DEnd  38 Bytes
  110           1_236  Status 00 Good
  111           1_736  MsgIn  00 Cmd Complete
  112          44_392 Bus Free
  113           0_000  Arb

RE: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Tony Battersby]

> I have also seen drives that do unexpected disconnects if they get
sent PPR.

I too have seen a single-ended Exabyte Mammoth tape drive go to
unexpected bus free right after receiving the second byte of the PPR
extended message (01 06 - bus free).  Evidently it does not expect to
receive an extended message of that length.

I submitted a patch to sym53c8xx_2 in lk 2.4.x a few days ago to avoid
PPR on a SE or HVD bus, which fixes the problem for me.

Anthony J. Battersby
Cybernetics

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Matthew Wilcox]

On Fri, Nov 05, 2004 at 12:01:40PM -0500, Tony Battersby wrote:
> > I have also seen drives that do unexpected disconnects if they get
> sent PPR.
> 
> I too have seen a single-ended Exabyte Mammoth tape drive go to
> unexpected bus free right after receiving the second byte of the PPR
> extended message (01 06 - bus free).  Evidently it does not expect to
> receive an extended message of that length.
> 
> I submitted a patch to sym53c8xx_2 in lk 2.4.x a few days ago to avoid
> PPR on a SE or HVD bus, which fixes the problem for me.

Yup, but that won't solve Thomas Babut's problem, because his drive is
in LVD mode.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Ada pter

[Matthew Wilcox]

On Fri, Nov 05, 2004 at 04:25:03PM -0000, SUPPORT wrote:
> I've been seeing problems with various tape drives and PPR. And a SCSI 3 SE
> disk is interesting as well! SE and PPR don't get on too well;)

... yes ...

I think we should *never* attempt PPR on a SE bus, even when the drive
supports it.  We've seen bugs in Seagate drive firmware because of this,
so let's stop doing it.

How does this patch (whitespace damaged, apply by hand) make people feel?

--- linux-2.6/drivers/scsi/sym53c8xx_2/sym_hipd.c       2004-11-02 12:59:53.0000
00000 -0700
+++ sym2-2.6/drivers/scsi/sym53c8xx_2/sym_hipd.c        2004-11-05 13:20:18.0000
00000 -0700
@@ -1455,7 +1455,7 @@
                st->options &= ~PPR_OPT_DT;
        }
 
-       if (!(np->features & FE_ULTRA3))
+       if (np->scsi_mode != SMODE_LVD || !(np->features & FE_ULTRA3))
                st->options &= ~PPR_OPT_DT;
 
        if (st->options & PPR_OPT_DT) {


> Matthew - I have attached some bits of SCSI analyser traces which I hope may
> be useful. An IBM SCSI 3 SE disk and a couple of LTO tape drives - IBM and
> HP. The HP causes severe problems as modprobe hangs without the fix. I have
> also seen drives that do unexpected disconnects if they get sent PPR.

Thanks, those are interesting.  It's good to see that we really are
spitting PPR out onto the wire when we shouldn't be.

> I have been toying with the idea of disabling PPR capability if PPR is
> rejected - forcing sdev->ppr=0 in the driver when it determines PPR has been
> rejected - but I'm not sure that's right. There are drives which reject
> negotiation - legacy sync and wide at least - while they are initialising
> but will then accept it later on.

I think disabling PPR on an SE bus should be a better fix than that.

> Question - where does the full source for the sym53c8xx_2 driver live these
> days now that Gerard no long maintains it?

My primary development for this driver lives in the parisc-linux CVS.
I publish patches on an irregular basis.  If this patch fixes a
significant number of problems (and it seems it might), I'll do a
2.1.18n release.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Ada pter

[Thomas Babut]

Matthew Wilcox wrote:
> On Fri, Nov 05, 2004 at 04:25:03PM -0000, SUPPORT wrote:
> 
>>I've been seeing problems with various tape drives and PPR. And a SCSI 3 SE
>>disk is interesting as well! SE and PPR don't get on too well;)
> 
> 
> ... yes ...
> 
> I think we should *never* attempt PPR on a SE bus, even when the drive
> supports it.  We've seen bugs in Seagate drive firmware because of this,
> so let's stop doing it.
> 
> How does this patch (whitespace damaged, apply by hand) make people feel?
> 
> --- linux-2.6/drivers/scsi/sym53c8xx_2/sym_hipd.c       2004-11-02 12:59:53.0000
> 00000 -0700
> +++ sym2-2.6/drivers/scsi/sym53c8xx_2/sym_hipd.c        2004-11-05 13:20:18.0000
> 00000 -0700
> @@ -1455,7 +1455,7 @@
>                 st->options &= ~PPR_OPT_DT;
>         }
>  
> -       if (!(np->features & FE_ULTRA3))
> +       if (np->scsi_mode != SMODE_LVD || !(np->features & FE_ULTRA3))
>                 st->options &= ~PPR_OPT_DT;
>  
>         if (st->options & PPR_OPT_DT) {
> 
> 
> 
>>Matthew - I have attached some bits of SCSI analyser traces which I hope may
>>be useful. An IBM SCSI 3 SE disk and a couple of LTO tape drives - IBM and
>>HP. The HP causes severe problems as modprobe hangs without the fix. I have
>>also seen drives that do unexpected disconnects if they get sent PPR.
> 
> 
> Thanks, those are interesting.  It's good to see that we really are
> spitting PPR out onto the wire when we shouldn't be.
> 
> 
>>I have been toying with the idea of disabling PPR capability if PPR is
>>rejected - forcing sdev->ppr=0 in the driver when it determines PPR has been
>>rejected - but I'm not sure that's right. There are drives which reject
>>negotiation - legacy sync and wide at least - while they are initialising
>>but will then accept it later on.
> 
> 
> I think disabling PPR on an SE bus should be a better fix than that.
> 
> 
>>Question - where does the full source for the sym53c8xx_2 driver live these
>>days now that Gerard no long maintains it?
> 
> 
> My primary development for this driver lives in the parisc-linux CVS.
> I publish patches on an irregular basis.  If this patch fixes a
> significant number of problems (and it seems it might), I'll do a
> 2.1.18n release.
> 

None of the patches you posted solved my problems. I'm loosing hope... ;)

Regards,
Thomas Babut

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Ada pter

[Doug Ledford]

On Sat, 2004-11-06 at 00:44 +0100, Thomas Babut wrote:

> None of the patches you posted solved my problems. I'm loosing hope... ;)

Well, having "been there, done that" many years ago when PPR messages
were first defined, here's the logic I found that worked in all cases:

OK, in the INQUIRY snoop area of the completion handler, I did the
appropriate card/device checks to determine if we should enable PPR:

if (bus_mode == LVD && sdev->scsi_level >= 3 &&
	host->user_transfer_settings >= MIN_DT_SPEED)
	use_ppr = 1;
else if (bus_mode == LVD && sdev->scsi_level < 3 && 
	(inquiry_len >= 57 && inq_data[56] & INQUIRY_DT_BIT) &&
	host->user_transfer_settings >= MIN_DT_SPEED)
	use_ppr = 1;
else
	use_sdtr_wdtr = 1;

In the event we set ppr on a device that can't handle it, I had to go
into the interrupt handler routine and in both the case of BUSFREE and
MSG_REJECT, if we were in the process of sending a ppr message and we
get either one of these in return, then turn off ppr messages for the
device (otherwise, we can get into an infinite loop were we accidentally
turned PPR on for a device that won't tolerate it for whatever reason,
and in fact once I know the ppr message has been rejected, the interrupt
handler would rewrite the ppr message into the closest possible
WDTR/SDTR message pair, assert ATNO on the bus to get us back in message
out phase, and proceed to go ahead and send the WDTR message, then wait
for a WDTR return, then assert ATNO again so we have a chance to do the
SDTR, then wait for the SDTR return, then proceed with the other
phases).

Finally, there are devices out there that do target initiated speed
negotiations.  If we get an incoming PPR message from a device, then you
are free to skip all those other checks in the INQUIRY snoop area and
just immediately set PPR on this device.  Now, you still need to do the
things like check that the bus is LVD before actually enabling LVD
speeds, but an unsolicited incoming PPR message is a dead giveaway that
the device supports PPR messages.  So, in the incoming message handling
portion of the interrupt handler, if we get an unsolicited PPR message
from a device, then we override any other settings we may have on the
device in terms of whether or not it supports PPR messages and we
disable the whole INQUIRY snoop operation for this device because we
don't want the INQUIRY snoop to disable PPR now that we know for a fact
that it's supported on this device.

Implement that, and you won't have these problems any more.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc.
         1801 Varsity Dr.
         Raleigh, NC 27606

RE: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Tony Battersby]

> Finally, there are devices out there that do target initiated speed
> negotiations.  If we get an incoming PPR message from a device

The spec says:

"PPR may be originated by SCSI initiator ports but shall not be
originated by SCSI target ports."

"WDTR and SDTR may be originated by either SCSI target ports or SCSI
initiator ports."

Unless someone has seen a counter-example, the case of target-originated
PPR negotiations can probably be ignored.

Anthony J. Battersby
Cybernetics

RE: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Doug Ledford]

On Mon, 2004-11-08 at 09:44 -0500, Tony Battersby wrote:
> > Finally, there are devices out there that do target initiated speed
> > negotiations.  If we get an incoming PPR message from a device
> 
> The spec says:
> 
> "PPR may be originated by SCSI initiator ports but shall not be
> originated by SCSI target ports."

Yeah, what the spec says and what devices do are not always one and the
same thing.

> "WDTR and SDTR may be originated by either SCSI target ports or SCSI
> initiator ports."
> 
> Unless someone has seen a counter-example, the case of target-originated
> PPR negotiations can probably be ignored.

DEC SCSI-2 hard disks that were installed with modified firmware.
Specifically, the Vaxen class computers they were hooked up to A) didn't
expect and handle SCSI-3 devices properly, B) didn't handle the DT bit
in the INQUIRY data properly, C) but DEC still wanted the devices to
talk 160MByte/s transfer rates, so the firmware was modified to send
preemptive PPR messages.  Problem solved something like 4 years ago, but
it existed at the time and physical devices may still exist in the
field.  In any case, yeah, the spec says otherwise, but I wouldn't rely
on that since getting this wrong leads to an infinite speed negotiation
loop.  Infinite loops suck...better safe than sorry on this issue IMO.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc.
         1801 Varsity Dr.
         Raleigh, NC 27606

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Thomas Babut]

Hi all,

yesterday I tried some new Kernels...

2.4.28-bk1 with sym53c8xx: works with normal Performance
Bootlog:
Nov 19 01:31:39 srv kernel: SCSI subsystem driver Revision: 1.00
Nov 19 01:31:39 srv kernel: sym53c8xx: at PCI bus 0, device 8, function 0
Nov 19 01:31:39 srv kernel: sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
Nov 19 01:31:39 srv kernel: sym53c8xx: 53c1010-33 detected with Symbios 
NVRAM
Nov 19 01:31:39 srv kernel: sym53c8xx: at PCI bus 0, device 8, function 1
Nov 19 01:31:39 srv kernel: sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
Nov 19 01:31:39 srv kernel: sym53c8xx: 53c1010-33 detected with Symbios 
NVRAM
Nov 19 01:31:39 srv kernel: sym53c1010-33-0: rev 0x1 on pci bus 0 device 
8 function 0 irq 9
Nov 19 01:31:39 srv kernel: sym53c1010-33-0: Symbios format NVRAM, ID 7, 
Fast-80, Parity Checking
Nov 19 01:31:39 srv kernel: sym53c1010-33-0: on-chip RAM at 0xf9000000
Nov 19 01:31:39 srv kernel: sym53c1010-33-0: restart (scsi reset).
Nov 19 01:31:39 srv kernel: sym53c1010-33-0: handling phase mismatch 
from SCRIPTS.
Nov 19 01:31:39 srv kernel: sym53c1010-33-0: Downloading SCSI SCRIPTS.
Nov 19 01:31:39 srv kernel: sym53c1010-33-1: rev 0x1 on pci bus 0 device 
8 function 1 irq 11
Nov 19 01:31:39 srv kernel: sym53c1010-33-1: Symbios format NVRAM, ID 7, 
Fast-80, Parity Checking
Nov 19 01:31:39 srv kernel: sym53c1010-33-1: on-chip RAM at 0xf8000000
Nov 19 01:31:39 srv kernel: sym53c1010-33-1: restart (scsi reset).
Nov 19 01:31:39 srv kernel: sym53c1010-33-1: handling phase mismatch 
from SCRIPTS.
Nov 19 01:31:39 srv kernel: sym53c1010-33-1: Downloading SCSI SCRIPTS.
Nov 19 01:31:39 srv kernel: scsi0 : sym53c8xx-1.7.3c-20010512
Nov 19 01:31:39 srv kernel: scsi1 : sym53c8xx-1.7.3c-20010512
Nov 19 01:31:39 srv kernel: blk: queue f7e9a018, I/O limit 1048575Mb 
(mask 0xffffffffff)
Nov 19 01:31:39 srv kernel:   Vendor: QUANTUM   Model: ATLAS10K2-TY367J 
  Rev: DDD6
Nov 19 01:31:39 srv kernel:   Type:   Direct-Access 
  ANSI SCSI revision: 03
Nov 19 01:31:39 srv kernel: blk: queue f7e67e18, I/O limit 1048575Mb 
(mask 0xffffffffff)
Nov 19 01:31:39 srv kernel: sym53c1010-33-0-<2,0>: tagged command queue 
depth set to 8
Nov 19 01:31:39 srv kernel: Attached scsi disk sda at scsi0, channel 0, 
id 2, lun 0
Nov 19 01:31:39 srv kernel: sym53c1010-33-0-<2,*>: FAST-40 SCSI 40.0 
MB/s (25.0 ns, offset 31)
Nov 19 01:31:39 srv kernel: SCSI device sda: 71721820 512-byte hdwr 
sectors (36722 MB)
Nov 19 01:31:39 srv kernel: Partition check:
Nov 19 01:31:39 srv kernel:  sda: sda1 sda2

2.4.28-bk1 with sym53c8xx2: works, but poor performance (max. 5 MByte/s)
Bootlog:
Nov 19 01:27:19 srv kernel: SCSI subsystem driver Revision: 1.00
Nov 19 01:27:19 srv kernel: sym.0.8.0: setting PCI_COMMAND_PARITY...
Nov 19 01:27:19 srv kernel: sym.0.8.1: setting PCI_COMMAND_PARITY...
Nov 19 01:27:19 srv kernel: sym0: <1010-33> rev 0x1 on pci bus 0 device 
8 function 0 irq 9
Nov 19 01:27:19 srv kernel: sym0: using 64 bit DMA addressing
Nov 19 01:27:19 srv kernel: sym0: Symbios NVRAM, ID 7, Fast-80, LVD, 
parity checking
Nov 19 01:27:19 srv kernel: sym0: open drain IRQ line driver, using 
on-chip SRAM
Nov 19 01:27:19 srv kernel: sym0: using LOAD/STORE-based firmware.
Nov 19 01:27:19 srv kernel: sym0: handling phase mismatch from SCRIPTS.
Nov 19 01:27:19 srv kernel: sym0: SCSI BUS has been reset.
Nov 19 01:27:19 srv kernel: sym1: <1010-33> rev 0x1 on pci bus 0 device 
8 function 1 irq 11
Nov 19 01:27:19 srv kernel: sym1: using 64 bit DMA addressing
Nov 19 01:27:19 srv kernel: sym1: Symbios NVRAM, ID 7, Fast-80, LVD, 
parity checking
Nov 19 01:27:19 srv kernel: sym1: open drain IRQ line driver, using 
on-chip SRAM
Nov 19 01:27:19 srv kernel: sym1: using LOAD/STORE-based firmware.
Nov 19 01:27:19 srv kernel: sym1: handling phase mismatch from SCRIPTS.
Nov 19 01:27:19 srv kernel: sym1: SCSI BUS has been reset.
Nov 19 01:27:19 srv kernel: scsi0 : sym-2.1.17a
Nov 19 01:27:19 srv kernel: scsi1 : sym-2.1.17a
Nov 19 01:27:19 srv kernel: blk: queue f7e9a018, I/O limit 1048575Mb 
(mask 0xffffffffff)
Nov 19 01:27:19 srv kernel:   Vendor: QUANTUM   Model: ATLAS10K2-TY367J 
  Rev: DDD6
Nov 19 01:27:19 srv kernel:   Type:   Direct-Access 
  ANSI SCSI revision: 03
Nov 19 01:27:19 srv kernel: blk: queue f7e64e18, I/O limit 1048575Mb 
(mask 0xffffffffff)
Nov 19 01:27:19 srv kernel: sym0:2:0: tagged command queuing enabled, 
command queue depth 16.
Nov 19 01:27:19 srv kernel: Attached scsi disk sda at scsi0, channel 0, 
id 2, lun 0
Nov 19 01:27:19 srv kernel: sym0:2:0:M_REJECT to send for : 1-3-1-9-1f.
Nov 19 01:27:19 srv kernel: SCSI device sda: 71721820 512-byte hdwr 
sectors (36722 MB)
Nov 19 01:27:19 srv kernel: Partition check:
Nov 19 01:27:19 srv kernel:  sda: sda1 sda2

2.6.10-rc2-bk3 with sym53c8xx2: System doesn't come up, same errors as 
before
No bootlog because of the lack of physical access to the machine.

I still would like to run Kernel 2.6. :)

Regards,
Thomas Babut

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Thomas Babut]

Would it be possible to integrate the sym53c8xx (1, not sym53c8xx_2) 
driver from Kernel 2.4.28 in 2.6? For me it would be the working 
solution to use my SCSI-Controller with Kernel 2.6.

Perhaps someone could make a patch for Kernel 2.6 which adds the old driver.

Thanks.

Regards,
Thomas Babut

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Matthew Wilcox]

On Tue, Nov 23, 2004 at 02:39:17AM +0100, Thomas Babut wrote:
> Would it be possible to integrate the sym53c8xx (1, not sym53c8xx_2) 
> driver from Kernel 2.4.28 in 2.6? For me it would be the working 
> solution to use my SCSI-Controller with Kernel 2.6.
> 
> Perhaps someone could make a patch for Kernel 2.6 which adds the old driver.

No.  Don't do this.  Help make sym2 work for your system.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Ingo Korb]

Matthew Wilcox <matthew@wil.cx> writes:

> On Tue, Nov 23, 2004 at 02:39:17AM +0100, Thomas Babut wrote:
>> Perhaps someone could make a patch for Kernel 2.6 which adds the old driver.
>
> No.  Don't do this.  Help make sym2 work for your system.

So what can one do? My Alphastation 200 has a 53C810 rev. 02 that only works
with the ncr53c8xx-driver from 2.4, sym53c8xx_2 just hangs. Details were
posted here about two weeks ago, without any replies.

-ik

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Thomas Babut]

Yesterday I tried Kernel 2.6.11-rc3 with newest sym53c8xx_2 driver 
(version 2.1.18n). But it still doesn't work. On boot the driver hangs 
up the system.

To remember:

0000:00:08.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 
Ultra3 SCSI Adapter (rev 01)
         Flags: bus master, medium devsel, latency 72, IRQ 11
         I/O ports at b000 [size=256]
         Memory at f8800000 (64-bit, non-prefetchable) [size=1K]
         Memory at f8000000 (64-bit, non-prefetchable) [size=8K]
         Capabilities: [40] Power Management version 2

With Kernel 2.4.29 and sym53c8xx driver it works fine. I still wish to 
run a Kernel 2.6 on that machine.

Regards,
Thomas Babut

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Thomas Babut]

I've tried now Kernel 2.6.10-rc1-bk15 with following two patches:
http://marc.theaimsgroup.com/?l=linux-scsi&m=109840610525441&w=2
http://marc.theaimsgroup.com/?l=linux-scsi&m=109844985008496&w=2

The patches applied perfectly. But the system doesn't boot up.

I've tried also on the working Kernel 2.6.9 (with drivers from 2.6.1) to 
set the following bootparams: sym53c8xx=sync:10

But it didn't change anything. Same poor performance as before.

Did I set this wrong? What would be the right way to set the speed manually?

Here is a dmesg output from 2.4.27 with normal performance (30 MB/s):

sym53c8xx: at PCI bus 0, device 8, function 0
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c1010-33 detected with Symbios NVRAM
sym53c8xx: at PCI bus 0, device 8, function 1
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c1010-33 detected with Symbios NVRAM
sym53c1010-33-0: rev 0x1 on pci bus 0 device 8 function 0 irq 9
sym53c1010-33-0: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
sym53c1010-33-0: on-chip RAM at 0xf9000000
sym53c1010-33-0: restart (scsi reset).
sym53c1010-33-0: handling phase mismatch from SCRIPTS.
sym53c1010-33-0: Downloading SCSI SCRIPTS.
sym53c1010-33-1: rev 0x1 on pci bus 0 device 8 function 1 irq 11
sym53c1010-33-1: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
sym53c1010-33-1: on-chip RAM at 0xf8000000
sym53c1010-33-1: restart (scsi reset).
sym53c1010-33-1: handling phase mismatch from SCRIPTS.
sym53c1010-33-1: Downloading SCSI SCRIPTS.
scsi0 : sym53c8xx-1.7.3c-20010512
scsi1 : sym53c8xx-1.7.3c-20010512
blk: queue f7e9bc18, I/O limit 1048575Mb (mask 0xffffffffff)
   Vendor: QUANTUM   Model: ATLAS10K2-TY367J  Rev: DDD6
   Type:   Direct-Access                      ANSI SCSI revision: 03
blk: queue f7e9ba18, I/O limit 1048575Mb (mask 0xffffffffff)
sym53c1010-33-0-<2,0>: tagged command queue depth set to 4
Attached scsi disk sda at scsi0, channel 0, id 2, lun 0
sym53c1010-33-0-<2,*>: FAST-40 SCSI 40.0 MB/s (25.0 ns, offset 31)
SCSI device sda: 71721820 512-byte hdwr sectors (36722 MB)
Partition check:
  sda: sda1 sda2

Thanks.

Regards,
Thomas Babut

RE: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Tony Battersby]

> scsi0 : sym53c8xx-1.7.3c-20010512
> scsi1 : sym53c8xx-1.7.3c-20010512

There are two LSI Logic drivers in lk 2.4.27: sym53c8xx and sym53c8xx_2.
You are using the older sym53c8xx driver here.  In 2.6.x, only
sym53c8xx_2 exists.  So you changed two variables at once:

sym53c8xx -> sym53c8xx_2
lk 2.4.27 -> lk 2.6.x

It might be useful to know how sym53c8xx_2 behaves in lk 2.4.27.

Anthony J. Battersby
Cybernetics

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Thomas Babut]

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

Here I am again with some news. :)

I tried last night Kernel 2.6.0 and 2.6.1 (both vanilla) and the system 
bootet up with the controller! Then I tried this:

1) unpack vanilla Kernel 2.6.9
2) copy drivers/scsi/sym53c8xx_comm.h, drivers/scsi/sym53c8xx_defs.h and 
the whole directory drivers/scsi/sym53c8xx_2/* from Kernel 2.6.1 into 
the Kernel 2.6.9 source

It booted, too. But on all this three 2.6 Kernels the SCSI-Harddisk has 
got very poor performance. With Kernel 2.4.26 and 2.4.27 it makes almost 
30 MB/s. With all three 2.6 Kernels it makes about 5 MB/s.

(see http://marc.theaimsgroup.com/?l=linux-kernel&m=109953598029428&w=2 
for detailed hardware specs and other informations)

Kernel-Config is attached to this mail.

Thanks for any idea.

Best regards,
Thomas Babut



[-- Attachment #2: kernel-config-2.6 --]
[-- Type: text/plain, Size: 18894 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9-1.1
# Fri Nov  5 03:15:45 2004
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_HOTPLUG is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
# CONFIG_X86_EMU486 is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_SMP=y
CONFIG_NR_CPUS=2
# CONFIG_SCHED_SMT is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_IRQBALANCE=y
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
# CONFIG_PM_DEBUG is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_BLACKLIST_YEAR=0

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_MSI is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
# CONFIG_PNPBIOS is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_LBD=y

#
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=4
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_REALM=m
# CONFIG_IP_NF_MATCH_SCTP is not set
CONFIG_IP_NF_MATCH_COMMENT=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
# CONFIG_IP_NF_NAT_LOCAL is not set
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_TARGET_NOTRACK=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=y
# CONFIG_E100_NAPI is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
# CONFIG_SERIO_RAW is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS_XATTR=y
CONFIG_DEVPTS_FS_SECURITY=y
CONFIG_TMPFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ASFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m

#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_PC=y

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Matthew Wilcox]

On Fri, Nov 05, 2004 at 01:52:32PM +0100, Thomas Babut wrote:
> Here I am again with some news. :)

Um, again?  This is the first I've heard from you.  BTW, Gerard seems to
be unreachable, which is why I took over the driver.

> I tried last night Kernel 2.6.0 and 2.6.1 (both vanilla) and the system 
> bootet up with the controller! Then I tried this:
> 
> 1) unpack vanilla Kernel 2.6.9
> 2) copy drivers/scsi/sym53c8xx_comm.h, drivers/scsi/sym53c8xx_defs.h and 
> the whole directory drivers/scsi/sym53c8xx_2/* from Kernel 2.6.1 into 
> the Kernel 2.6.9 source
> 
> It booted, too. But on all this three 2.6 Kernels the SCSI-Harddisk has 
> got very poor performance. With Kernel 2.4.26 and 2.4.27 it makes almost 
> 30 MB/s. With all three 2.6 Kernels it makes about 5 MB/s.

Sounds like your drive isn't negotiating the correct transfer rate.
If it's able to do 30MB/s, I guess it should be negotiating at least
wide, 20MHz -- 5MB/s sounds like asynchronous.

> (see http://marc.theaimsgroup.com/?l=linux-kernel&m=109953598029428&w=2 
> for detailed hardware specs and other informations)

Hrm.  Domain validation is failing.  I bet what's going on is that the
controller is U160-capable, so we're sending a PPR message to the drive
which is going haywire.  I do hope we don't have to start blacklisting
drives as being PPR-incapable.

Can you turn on negotiation debugging and send me the result?  If you
have 2.1.18m, that's sym53c8xx.debug=0x200 ... earlier than that, it's
sym53c8xx=debug:0x200

Now ... you say:

> sym0: SCSI BUS reset detected.
> sym0: SCSI BUS has been reset.
> sym0: SCSI BUS operation completed.
> 
> At this point only a hard-reset helps.

Do you mean the machine freezes at this point, or you can't boot because
this drive has your root partition on it and it can't be found?  If the
former, this is another bug that needs to be fixed.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Thomas Babut]

Matthew Wilcox wrote:
> On Fri, Nov 05, 2004 at 01:52:32PM +0100, Thomas Babut wrote:
> Sounds like your drive isn't negotiating the correct transfer rate.
> If it's able to do 30MB/s, I guess it should be negotiating at least
> wide, 20MHz -- 5MB/s sounds like asynchronous.
dmesg output from Kernel 2.6.9 with the drivers from 2.6.1:

Nov  5 03:30:07 srv kernel: sym0: Symbios NVRAM, ID 7, Fast-80, LVD,
parity checking
Nov  5 03:30:07 srv kernel: sym0: open drain IRQ line driver, using
on-chip SRAM
Nov  5 03:30:07 srv kernel: sym0: using LOAD/STORE-based firmware.
Nov  5 03:30:07 srv kernel: sym0: handling phase mismatch from SCRIPTS.
Nov  5 03:30:07 srv kernel: sym0: SCSI BUS has been reset.
Nov  5 03:30:07 srv kernel: scsi0 : sym-2.1.18f
Nov  5 03:30:07 srv kernel: Using anticipatory io scheduler
Nov  5 03:30:07 srv kernel:   Vendor: QUANTUM   Model: ATLAS10K2-TY367J
  Rev: DDD6
Nov  5 03:30:07 srv kernel:   Type:   Direct-Access
  ANSI SCSI revision: 03
Nov  5 03:30:07 srv kernel: sym0:2:0: tagged command queuing enabled,
command queue depth 4.
Nov  5 03:30:07 srv kernel: sym0:2:0:M_REJECT to send for : 1-3-1-9-1f.
Nov  5 03:30:07 srv kernel: sym1: <1010-33> rev 0x1 at pci 0000:00:08.1
irq 11
Nov  5 03:30:07 srv kernel: sym1: Symbios NVRAM, ID 7, Fast-80, LVD,
parity checking
Nov  5 03:30:07 srv kernel: sym1: open drain IRQ line driver, using
on-chip SRAM
Nov  5 03:30:07 srv kernel: sym1: using LOAD/STORE-based firmware.
Nov  5 03:30:07 srv kernel: sym1: handling phase mismatch from SCRIPTS.
Nov  5 03:30:07 srv kernel: sym1: SCSI BUS has been reset.
Nov  5 03:30:07 srv kernel: scsi1 : sym-2.1.18f
Nov  5 03:30:07 srv kernel: SCSI device sda: 71721820 512-byte hdwr
sectors (36722 MB)
Nov  5 03:30:07 srv kernel: SCSI device sda: drive cache: write back
Nov  5 03:30:07 srv kernel:  sda: sda1 sda2
Nov  5 03:30:07 srv kernel: Attached scsi disk sda at scsi0, channel 0,
id 2, lun 0

> 
> Can you turn on negotiation debugging and send me the result?  If you
> have 2.1.18m, that's sym53c8xx.debug=0x200 ... earlier than that, it's
> sym53c8xx=debug:0x200
Sorry, I can't because this a dedicated server. :(

>>sym0: SCSI BUS reset detected.
>>sym0: SCSI BUS has been reset.
>>sym0: SCSI BUS operation completed.
>>
>>At this point only a hard-reset helps.
> 
> 
> Do you mean the machine freezes at this point, or you can't boot because
> this drive has your root partition on it and it can't be found?  If the
> former, this is another bug that needs to be fixed.

I've got two screenshots from the local administrator:
http://tomek.tueddeln.de/screenshot1.jpg
http://tomek.tueddeln.de/screenshot2.jpg

Btw: Where can I get the newest sym53c8xx_2 driver?

Thanks.

Regards,
Thomas Babut

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Matthew Wilcox]

On Fri, Nov 05, 2004 at 02:59:25PM +0100, Thomas Babut wrote:
> >Can you turn on negotiation debugging and send me the result?  If you
> >have 2.1.18m, that's sym53c8xx.debug=0x200 ... earlier than that, it's
> >sym53c8xx=debug:0x200
> Sorry, I can't because this a dedicated server. :(

I need something to work with ... can you schedule some downtime?

> I've got two screenshots from the local administrator:
> http://tomek.tueddeln.de/screenshot1.jpg
> http://tomek.tueddeln.de/screenshot2.jpg

Hey!  There's a *lot* more information there than you gave me ;-(

I see a lot of parity errors there.  Can you check the cabling, termination,
etc?  How about putting a serial console on it so I can see all the messages?

> Btw: Where can I get the newest sym53c8xx_2 driver?

I commit to the parisc-linux CVS tree on a regular basis, then bundle up
what I have once per upstream release and send it to linux-scsi.  Last
patches:
http://marc.theaimsgroup.com/?l=linux-scsi&m=109840610525441&w=2
http://marc.theaimsgroup.com/?l=linux-scsi&m=109844985008496&w=2

James then commits it to the linux-scsi scsi-misc-2.6 BK tree.
You can see it at
http://linux-scsi.bkbits.net:8080/scsi-misc-2.6/ChangeSet@-2w?nav=index.html

I believe Andrew Morton then includes scsi-misc-2.6 in his -mm releases.

So that's four different places you can get it, depending on what's
easiest for you.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: Kernel 2.6.x hangs with Symbios Logic 53c1010 Ultra3 SCSI Adapter

[Thomas Babut]

Matthew Wilcox wrote:
> On Fri, Nov 05, 2004 at 02:59:25PM +0100, Thomas Babut wrote:
> I need something to work with ... can you schedule some downtime?
I've no physical access to this server. That's the problem. :(

> Hey!  There's a *lot* more information there than you gave me ;-(
> 
> I see a lot of parity errors there.  Can you check the cabling, termination,
> etc?  How about putting a serial console on it so I can see all the messages?
The Administrator said me that the hardware is correctly installed.
Unfortunately serial console is not possible. But with Kernel 2.4.x the
configuration runs fine.

Perhaps any other idea?

I'll try the newer scsi-drivers. Thanks.