From owner-freebsd-scsi Sun Nov 26 1:47:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from funkthat.com (mg128-062.ricochet.net [204.179.128.62]) by hub.freebsd.org (Postfix) with ESMTP id 4EC6937B4CF for ; Sun, 26 Nov 2000 01:47:10 -0800 (PST) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id BAA02682; Sun, 26 Nov 2000 01:48:10 -0800 (PST) Message-ID: <20001126014805.22964@hydrogen.funkthat.com> Date: Sun, 26 Nov 2000 01:48:05 -0800 From: John-Mark Gurney To: freebsd-scsi@freebsd.org Subject: Re: ncr problems (and amd) References: <20001125142603.14261@hydrogen.funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <20001125142603.14261@hydrogen.funkthat.com>; from John-Mark Gurney on Sat, Nov 25, 2000 at 02:26:03PM -0800 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John-Mark Gurney scribbled this message on Nov 25: looks like I left out an important part of the log: (da0:ncr0:0:0:0): phase change 2-3 10@038ee29c resid=4. (da0:ncr0:0:0:0): WRITE(10). CDB: 2a 0 0 3f 8a e0 0 0 60 0 (da0:ncr0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:ncr0:0:0:0): Invalid field in CDB which happened about at least six minutes before the following started (can tell by syslog messages to the console) > ncr0: timeout nccb=0xc0d92000 (skip) then later in the add (after a reboot), a similar event happened: ncr0: SCSI phase error fixup: CCB address mismatch (0xc120ac00 != 0xc11fca00) np->nccb = 0xc120ac00 (da2:ncr0:0:4:0): phase change 6-3 3@03efbdb4 resid=3. ncr0: queue empty. ncr0: SCSI phase error fixup: CCB already dequeued (0xc120ac00) ncr0: timeout nccb=0xc0f05800 (skip) ncr0: timeout nccb=0xc0f05a00 (skip) ncr0: timeout nccb=0xc0ecb800 (skip) ncr0: timeout nccb=0xc0ecbc00 (skip) ncr0: timeout nccb=0xc120ac00 (skip) which is kinda interesting, as it looks like the ccb that caused this isn't even valid (the head disaggress what virtual address it is at..) of course, I'm having troubles wrapping my head aroun the ncr driver as most of it isn't commented very well.. the last lockup had this on output: (pass1:ncr0:0:1:0): MSG_DISCONNECT received, but datapointer not saved: data=2274d90 save=e71026a0 goal=e71026c4. (pass1:ncr0:0:1:0): MSG_DISCONNECT received, but datapointer not saved: data=2274d90 save=e71026a0 goal=e71026c4. (pass2:ncr0:0:2:0): MSG_DISCONNECT received, but datapointer not saved: data=38bf390 save=e71026a0 goal=e71026c4. (pass1:ncr0:0:1:0): MSG_DISCONNECT received, but datapointer not saved: data=2274d90 save=e71026a0 goal=e71026c4. (pass2:ncr0:0:2:0): MSG_DISCONNECT received, but datapointer not saved: data=38bf190 save=e71026a0 goal=e71026c4. Nov 25 20:47:00 hydrogen su: jmg to root on /dev/ttyp6 [other unrelated activity eleted] Nov 25 22:04:07 hydrogen su: jmg to root on /dev/ttyp9 ncr0: SCSI phase error fixup: CCB address mismatch (0xc0f5c200 != 0xc0eff200) np->nccb = 0xc0f5c200 (da2:ncr0:0:4:0): phase change 6-3 3@049553b4 resid=3. ncr0: SCSI phase error fixup: CCB already dequeued (0xc0f5c200) ncr0: timeout nccb=0xc0eff400 (skip) hopefully someone can figure out why it enters the timeout and never completes... or at least provide some help in debugging this.. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 26 6:32:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front4m.grolier.fr (front4m.grolier.fr [195.36.216.54]) by hub.freebsd.org (Postfix) with ESMTP id CC03B37B479 for ; Sun, 26 Nov 2000 06:32:14 -0800 (PST) Received: from nas1-223.mea.club-internet.fr (nas1-223.mea.club-internet.fr [195.36.139.223]) by front4m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id PAA13407; Sun, 26 Nov 2000 15:30:46 +0100 (MET) Date: Sun, 26 Nov 2000 14:32:18 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: John-Mark Gurney Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ncr problems (and amd) In-Reply-To: <20001126014805.22964@hydrogen.funkthat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John - I read your 2 messages, and the problems reported by the `ncr' driver seems to me rather due to flaws in the hardware than to the `ncr' itself. Could you describe the hardware you are using and what you are doing with it. You also may check that it is properly configured in all its parts. I mean, clockings, cabling, cooling, etc ... G=E9rard. On Sun, 26 Nov 2000, John-Mark Gurney wrote: > John-Mark Gurney scribbled this message on Nov 25: >=20 > looks like I left out an important part of the log: > (da0:ncr0:0:0:0): phase change 2-3 10@038ee29c resid=3D4. > (da0:ncr0:0:0:0): WRITE(10). CDB: 2a 0 0 3f 8a e0 0 0 60 0=20 > (da0:ncr0:0:0:0): ILLEGAL REQUEST asc:24,0 > (da0:ncr0:0:0:0): Invalid field in CDB >=20 > which happened about at least six minutes before the following started > (can tell by syslog messages to the console) >=20 > > ncr0: timeout nccb=3D0xc0d92000 (skip) >=20 > then later in the add (after a reboot), a similar event happened: > ncr0: SCSI phase error fixup: CCB address mismatch (0xc120ac00 !=3D 0xc11= fca00) np->nccb =3D 0xc120ac00 > (da2:ncr0:0:4:0): phase change 6-3 3@03efbdb4 resid=3D3. > ncr0: queue empty. > ncr0: SCSI phase error fixup: CCB already dequeued (0xc120ac00) > ncr0: timeout nccb=3D0xc0f05800 (skip) > ncr0: timeout nccb=3D0xc0f05a00 (skip) > ncr0: timeout nccb=3D0xc0ecb800 (skip) > ncr0: timeout nccb=3D0xc0ecbc00 (skip) > ncr0: timeout nccb=3D0xc120ac00 (skip) >=20 > which is kinda interesting, as it looks like the ccb that caused this > isn't even valid (the head disaggress what virtual address it is at..) >=20 > of course, I'm having troubles wrapping my head aroun the ncr driver > as most of it isn't commented very well..=20 >=20 > the last lockup had this on output: > (pass1:ncr0:0:1:0): MSG_DISCONNECT received, but datapointer not saved: > =09data=3D2274d90 save=3De71026a0 goal=3De71026c4. > (pass1:ncr0:0:1:0): MSG_DISCONNECT received, but datapointer not saved: > =09data=3D2274d90 save=3De71026a0 goal=3De71026c4. > (pass2:ncr0:0:2:0): MSG_DISCONNECT received, but datapointer not saved: > =09data=3D38bf390 save=3De71026a0 goal=3De71026c4. > (pass1:ncr0:0:1:0): MSG_DISCONNECT received, but datapointer not saved: > =09data=3D2274d90 save=3De71026a0 goal=3De71026c4. > (pass2:ncr0:0:2:0): MSG_DISCONNECT received, but datapointer not saved: > =09data=3D38bf190 save=3De71026a0 goal=3De71026c4. > Nov 25 20:47:00 hydrogen su: jmg to root on /dev/ttyp6 > [other unrelated activity eleted] > Nov 25 22:04:07 hydrogen su: jmg to root on /dev/ttyp9 > ncr0: SCSI phase error fixup: CCB address mismatch (0xc0f5c200 !=3D 0xc0e= ff200) np->nccb =3D 0xc0f5c200 > (da2:ncr0:0:4:0): phase change 6-3 3@049553b4 resid=3D3. > ncr0: SCSI phase error fixup: CCB already dequeued (0xc0f5c200) > ncr0: timeout nccb=3D0xc0eff400 (skip) >=20 > hopefully someone can figure out why it enters the timeout and never > completes... or at least provide some help in debugging this.. >=20 > --=20 > John-Mark Gurney=09=09=09=09Voice: +1 408 975 9651 > Cu Networking > =09"Thank God I'm an atheist, that'd just be confusing." -- cmc >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 26 10:54: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from funkthat.com (mg128-062.ricochet.net [204.179.128.62]) by hub.freebsd.org (Postfix) with ESMTP id 2F42837B479 for ; Sun, 26 Nov 2000 10:54:00 -0800 (PST) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id KAA10096; Sun, 26 Nov 2000 10:54:47 -0800 (PST) Message-ID: <20001126105441.34721@hydrogen.funkthat.com> Date: Sun, 26 Nov 2000 10:54:41 -0800 From: John-Mark Gurney To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ncr problems (and amd) References: <20001126014805.22964@hydrogen.funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.69 In-Reply-To: =?iso-8859-1?Q?=3CPine=2ELNX=2E4=2E10=2E10011261423010=2E1005-100000=40l?= =?iso-8859-1?Q?inux=2Elocal=3E=3B_from_G=E9rard_Roudier_on_Sun=2C_Nov_26?= =?iso-8859-1?Q?=2C_2000_at_02=3A32=3A18PM_+0100?= Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gérard Roudier scribbled this message on Nov 26: > I read your 2 messages, and the problems reported by the `ncr' driver > seems to me rather due to flaws in the hardware than to the `ncr' itself. > > Could you describe the hardware you are using and what you are doing with > it. You also may check that it is properly configured in all its parts. I > mean, clockings, cabling, cooling, etc ... ok... well, the hardware is a Tekram DC-390F. Attached hardware is: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da4) at scbus0 target 4 lun 0 (pass3,da2) All are narrow except the Fujitsu. All are internal, using no special addapters. Termination is turned on on both drives at the end of the chain. Motherboard is a FICA VA-503+ VIA based chipset that is *NOT* overclocked. As for cooling, nothing special, but the case is closed and has two exhaust fans and one intake fan. When I upgraded from the Advansys Ultra SCSI card, I didn't change internal cabling for the three narrow devices (and I'd been running that for 9+ months). The cable length on the narror part of the system might be a bit long, so I plan on next crash replacing it with a cable that only has three connectors for drives instead of the current five. Though the Tekram manual lists a length of 3 meters for 4 devices or less, which I know I'm less than, for the 1.5 meters (max of 8 devices) I'm probably pretty close to. Well, it also survived daily, but I did reduce the tags all above mentioned drives to 16, which may have made a difference. But only 16 tags is so few. :( Thanks for any help you can provide. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 26 11:33:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id 6BC0337B4C5 for ; Sun, 26 Nov 2000 11:33:56 -0800 (PST) Received: from nas1-128.mea.club-internet.fr (nas1-128.mea.club-internet.fr [195.36.139.128]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id UAA12201; Sun, 26 Nov 2000 20:33:49 +0100 (MET) Date: Sun, 26 Nov 2000 19:34:00 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: John-Mark Gurney Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ncr problems (and amd) In-Reply-To: <20001126105441.34721@hydrogen.funkthat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some VIA based chipset motherboards can mess-up a lot with your controller when some feature is enabled on the chipset. I donnot remember exactly the feature that makes problems (DMA problems), but it should have something to do with `cache streaming' or `PCI streaming'. Could you look into your mother-board set-up if a feature that resembles ` streaming' is enabled and then disable it. G=E9rard. On Sun, 26 Nov 2000, John-Mark Gurney wrote: > G=E9rard Roudier scribbled this message on Nov 26: > > I read your 2 messages, and the problems reported by the `ncr' driver > > seems to me rather due to flaws in the hardware than to the `ncr' itsel= f. > >=20 > > Could you describe the hardware you are using and what you are doing wi= th > > it. You also may check that it is properly configured in all its parts.= I > > mean, clockings, cabling, cooling, etc ... >=20 > ok... well, the hardware is a Tekram DC-390F. Attached hardware is: > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da4) > at scbus0 target 4 lun 0 (pass3,da2) >=20 > All are narrow except the Fujitsu. All are internal, using no special > addapters. Termination is turned on on both drives at the end of the > chain. Motherboard is a FICA VA-503+ VIA based chipset that is *NOT* > overclocked. As for cooling, nothing special, but the case is closed > and has two exhaust fans and one intake fan. When I upgraded from the > Advansys Ultra SCSI card, I didn't change internal cabling for the > three narrow devices (and I'd been running that for 9+ months). >=20 > The cable length on the narror part of the system might be a bit long, > so I plan on next crash replacing it with a cable that only has three > connectors for drives instead of the current five. Though the Tekram > manual lists a length of 3 meters for 4 devices or less, which I know > I'm less than, for the 1.5 meters (max of 8 devices) I'm probably pretty > close to. >=20 > Well, it also survived daily, but I did reduce the tags all above > mentioned drives to 16, which may have made a difference. But only > 16 tags is so few. :( >=20 > Thanks for any help you can provide. >=20 > --=20 > John-Mark Gurney=09=09=09=09Voice: +1 408 975 9651 > Cu Networking > =09"Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 26 12:30: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from funkthat.com (mg128-062.ricochet.net [204.179.128.62]) by hub.freebsd.org (Postfix) with ESMTP id 1AB7637B479 for ; Sun, 26 Nov 2000 12:29:59 -0800 (PST) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id MAA11733; Sun, 26 Nov 2000 12:30:45 -0800 (PST) Message-ID: <20001126123040.16010@hydrogen.funkthat.com> Date: Sun, 26 Nov 2000 12:30:40 -0800 From: John-Mark Gurney To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ncr problems (and amd) References: <20001126105441.34721@hydrogen.funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.69 In-Reply-To: =?iso-8859-1?Q?=3CPine=2ELNX=2E4=2E10=2E10011261925350=2E499-100000=40li?= =?iso-8859-1?Q?nux=2Elocal=3E=3B_from_G=E9rard_Roudier_on_Sun=2C_Nov_26?= =?iso-8859-1?Q?=2C_2000_at_07=3A34=3A00PM_+0100?= Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gérard Roudier scribbled this message on Nov 26: > Some VIA based chipset motherboards can mess-up a lot with your controller > when some feature is enabled on the chipset. > > I donnot remember exactly the feature that makes problems (DMA problems), > but it should have something to do with `cache streaming' or `PCI > streaming'. > > Could you look into your mother-board set-up if a feature that resembles > ` streaming' is enabled and then disable it. there is a burst option I believe.. and I'll try to do that the next time it crashes... right now the machine doesn't even have a video card in it.. so, when I put in the shorter cable, I'll do this config change at the same time... but I don't think it's a PCI bus issue, as it looks like the ncr driver tries to retry, but the ncr is completely out to lunch and needs to be reset.. is there a way for it to detect excessive timeouts (like no command completed and all commands have timedout twice), and reinitalize the card? > On Sun, 26 Nov 2000, John-Mark Gurney wrote: > > > Gérard Roudier scribbled this message on Nov 26: > > > I read your 2 messages, and the problems reported by the `ncr' driver > > > seems to me rather due to flaws in the hardware than to the `ncr' itself. > > > > > > Could you describe the hardware you are using and what you are doing with > > > it. You also may check that it is properly configured in all its parts. I > > > mean, clockings, cabling, cooling, etc ... > > > > ok... well, the hardware is a Tekram DC-390F. Attached hardware is: > > at scbus0 target 0 lun 0 (pass0,da0) > > at scbus0 target 1 lun 0 (pass1,da1) > > at scbus0 target 2 lun 0 (pass2,da4) > > at scbus0 target 4 lun 0 (pass3,da2) > > > > All are narrow except the Fujitsu. All are internal, using no special > > addapters. Termination is turned on on both drives at the end of the > > chain. Motherboard is a FICA VA-503+ VIA based chipset that is *NOT* > > overclocked. As for cooling, nothing special, but the case is closed > > and has two exhaust fans and one intake fan. When I upgraded from the > > Advansys Ultra SCSI card, I didn't change internal cabling for the > > three narrow devices (and I'd been running that for 9+ months). > > > > The cable length on the narror part of the system might be a bit long, > > so I plan on next crash replacing it with a cable that only has three > > connectors for drives instead of the current five. Though the Tekram > > manual lists a length of 3 meters for 4 devices or less, which I know > > I'm less than, for the 1.5 meters (max of 8 devices) I'm probably pretty > > close to. > > > > Well, it also survived daily, but I did reduce the tags all above > > mentioned drives to 16, which may have made a difference. But only > > 16 tags is so few. :( > > > > Thanks for any help you can provide. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 26 13:36:28 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front4.grolier.fr (front4.grolier.fr [194.158.96.54]) by hub.freebsd.org (Postfix) with ESMTP id A37CA37B479 for ; Sun, 26 Nov 2000 13:36:24 -0800 (PST) Received: from nas15-1.vlt.club-internet.fr (nas15-1.vlt.club-internet.fr [195.36.165.1]) by front4.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA16833; Sun, 26 Nov 2000 22:36:17 +0100 (MET) Date: Sun, 26 Nov 2000 21:36:28 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: John-Mark Gurney Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ncr problems (and amd) In-Reply-To: <20001126123040.16010@hydrogen.funkthat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 26 Nov 2000, John-Mark Gurney wrote: > G=E9rard Roudier scribbled this message on Nov 26: > > Some VIA based chipset motherboards can mess-up a lot with your control= ler > > when some feature is enabled on the chipset. > >=20 > > I donnot remember exactly the feature that makes problems (DMA problems= ), > > but it should have something to do with `cache streaming' or `PCI > > streaming'. > >=20 > > Could you look into your mother-board set-up if a feature that resemble= s > > ` streaming' is enabled and then disable it. >=20 > there is a burst option I believe.. and I'll try to do that the next May-be it is ' bursting' instead, but `streaming' sounds better to me. As I wrote, I forgot the exact feature that breaks PCI DMA with the 53c875 using some VIA chipset based motherboards. > time it crashes... right now the machine doesn't even have a video > card in it.. so, when I put in the shorter cable, I'll do this config > change at the same time... >=20 > but I don't think it's a PCI bus issue, as it looks like the ncr driver If you have time for giving a try with another O/S and/or driver for your chip, this will help better that thinking, in my opinion. > tries to retry, but the ncr is completely out to lunch and needs to be > reset.. is there a way for it to detect excessive timeouts (like no > command completed and all commands have timedout twice), and reinitalize > the card? If you have time for installing 4.X you will be able to use `sym', but this will probably not work better, if as I beleive, the real cause is bad DMA happening between the PCI-SCSI chip and core-logic/memory. G=E9rard. > > On Sun, 26 Nov 2000, John-Mark Gurney wrote: > >=20 > > > G=E9rard Roudier scribbled this message on Nov 26: > > > > I read your 2 messages, and the problems reported by the `ncr' driv= er > > > > seems to me rather due to flaws in the hardware than to the `ncr' i= tself. > > > >=20 > > > > Could you describe the hardware you are using and what you are doin= g with > > > > it. You also may check that it is properly configured in all its pa= rts. I > > > > mean, clockings, cabling, cooling, etc ... > > >=20 > > > ok... well, the hardware is a Tekram DC-390F. Attached hardware is: > > > at scbus0 target 0 lun 0 (pass0,da= 0) > > > at scbus0 target 1 lun 0 (pass1,da= 1) > > > at scbus0 target 2 lun 0 (pass2,da= 4) > > > at scbus0 target 4 lun 0 (pass3,da= 2) > > >=20 > > > All are narrow except the Fujitsu. All are internal, using no specia= l > > > addapters. Termination is turned on on both drives at the end of the > > > chain. Motherboard is a FICA VA-503+ VIA based chipset that is *NOT* > > > overclocked. As for cooling, nothing special, but the case is closed > > > and has two exhaust fans and one intake fan. When I upgraded from th= e > > > Advansys Ultra SCSI card, I didn't change internal cabling for the > > > three narrow devices (and I'd been running that for 9+ months). > > >=20 > > > The cable length on the narror part of the system might be a bit long= , > > > so I plan on next crash replacing it with a cable that only has three > > > connectors for drives instead of the current five. Though the Tekram > > > manual lists a length of 3 meters for 4 devices or less, which I know > > > I'm less than, for the 1.5 meters (max of 8 devices) I'm probably pre= tty > > > close to. > > >=20 > > > Well, it also survived daily, but I did reduce the tags all above > > > mentioned drives to 16, which may have made a difference. But only > > > 16 tags is so few. :( > > >=20 > > > Thanks for any help you can provide. >=20 > --=20 > John-Mark Gurney=09=09=09=09Voice: +1 408 975 9651 > Cu Networking > =09"Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 27 10:58:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.it.helsinki.fi (post.it.helsinki.fi [128.214.205.24]) by hub.freebsd.org (Postfix) with ESMTP id 9298637B479 for ; Mon, 27 Nov 2000 10:58:46 -0800 (PST) Received: from mursu.pesa.fi (root@sirppi.helsinki.fi [128.214.205.27]) by post.it.helsinki.fi (8.11.1/8.11.0-SPAMmers-sod-off) with ESMTP id eARIwho27853; Mon, 27 Nov 2000 20:58:43 +0200 (EET) Received: (from poku@localhost) by mursu.pesa.fi (8.11.1/8.11.1) id eARIWIG11005; Mon, 27 Nov 2000 20:32:18 +0200 (EET) (envelope-from poku@mursu.pesa.fi) To: Andrea Venturoli Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Zip Zoom References: <200011251425.eAPEPmi24483@relay.flashnet.it> From: Jussi Reissell Date: 27 Nov 2000 20:32:18 +0200 In-Reply-To: Andrea Venturoli's message of "Sat, 25 Nov 2000 16:25:40 EST" Message-ID: <87y9y51d1p.fsf@mursu.pesa.fi> Lines: 53 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrea Venturoli writes: Did an wild, indiscriminating fill on your msg. Some lines may appear strange as a result. > Hello. > > I've got a problem with a FreeBSD 4.1.1-RELEASE system (although I > also tried 4.0-R, which behaves just the same. The machine is an IBM > PS VP with a 486DX2, 20MB of RAM, ISA bus, an IDE HD, a 3Com > EtherLink III, a modem and an Elsa QuickStep 1000pro ISDN card. Now > I had a spare SCSI HD along with a Zip Zoom SCSI adapter (which is > actually an Adaptec AVA-1502): ok, it can't boot, it will probably > be very slow, but it's fine for what I have to do. I plugged in the > adapter and connected the Disk (with another OS it works fine, so I > don't think it's an hardware problem). I configured my kernel with > the following lines (but it's the same with the generic kernel): > > > device aic0 at isa? device scbus device da > > > Then I rebooted, but I got the following: > > > Waiting 15 seconds for SCSI devices to settle (probe0:aic0:0:0:0) > > ccb 0xc04dbc00 - timed out, phase 0xb6, state 4 > > (probe0:aic0:0:0:0) ccb 0xc04dbc00 - timed out, phase 0xb6, state > > 4 (probe0:aic0:0:0:0) ccb 0xc04dbc00 - timed out, phase 0xb6, > > state 1 (probe0:aic0:0:0:0) ccb 0xc04dbc00 - timed out, phase > > 0xb6, state 1 ... > > After the first line, the others appear very slowly (even one per > minute); every device is probed a few times times up to device 7 > (it's a narrow bus), sometimes the number after "ccb" changes. > > I tried every IRQ the card could handle (i.e. from 9 to 12), the > kernel will always default to 12, so I "userconfig"ured it in the > other cases; I also tried using the "alternate" jumper which moves > the card from i/o ports 0x140 to 0x340, and here the kernel is smart > enough to detect it. Anyway I could not get it to work. I > double-checked and I should have no IRQ conflicts, since from 9 to > 12 there is no legacy card, only the two plug and play ones, which > get whichever ones are free. > > Any hint/suggestion? Not really. The aic driver seems to have problems if there's a Zip drive plugged in. There's a pending pr: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22733 I've stumbled on the same problem with an adaptec pccard which uses the same driver. jussi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 27 12:42:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from beloit.edu (beloit.edu [144.89.40.1]) by hub.freebsd.org (Postfix) with ESMTP id B362537B479; Mon, 27 Nov 2000 12:42:16 -0800 (PST) Received: from Eric2000.beloit.edu ([144.89.40.89]) by beloit.edu (AIX4.3/8.9.3/8.9.0) with ESMTP id OAA19056; Mon, 27 Nov 2000 14:50:05 -0600 Message-Id: <4.3.2.7.2.20001127144047.00b4c4f0@pop3.norton.antivirus> X-Sender: noodene/beloit.edu@pop3.norton.antivirus X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 27 Nov 2000 14:43:35 -0600 To: Paul Southworth , Greg Lehey From: "Eric S. Nooden" Subject: Re: Mounting a SCSI tape drive Cc: Michael Hughes , freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org In-Reply-To: References: <19991202195345.47886@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was in communication with Greg Lehey about this matter and at the time he had not come up with a solution since he had not yet received the Exabyte drives. I am also still interested in a solution since I have yet to back up my system. Thanks, Eric At 01:03 PM 11/24/2000 -0500, Paul Southworth wrote: >[About a year ago there was a thread on freebsd-questions about Exabyte >8200 drives which I would like to revive with the hope that someone found >a solution.] > >On Thu, 2 Dec 1999, Greg Lehey wrote: > >:On Thursday, 2 December 1999 at 15:17:47 -0600, Eric S. Nooden wrote: >:> At 02:29 PM 12/2/99 -0600, Michael Hughes wrote: >:>> Eric S. Nooden said in email to me: >:>>> >:>>> I am running into some problems trying to mount a tape drive. When I >run: >:>>> >:>>> mt -f /dev/nrsa0 rewind (or any command i.e. status) >:>>> >:>>> I get the following error message: >:>>> >:>>> (sa0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 >:>>> (sa0:ahc0:0:4:0): ILLEGAL REQUEST >:>>> >:>>> ***I did notice that when the command ran, the light on the tape >drive did >:>>> flash. >:>>> >:>>> The file /var/log/messages reports the following about sa0: >:>>> >:>>> sa0: at ahc0 bus 0 target 4 lun 0 >:>>> sa0: Removable Sequential Access SCSI-CCS device >:>>> sa0: 3.300MB/s transfers > >I have what appears to be an almost identical drive. Mine is reported >as " Removable Sequential Access SCSI-CCS device". > >This was a drive Exabyte made OEM for IBM and was sold in RS/6000s ten >years ago, white faceplate and round blue eject button. I am aware that >it is a piece of crap - if I can make it work this whole machine is going >to a charitable cause, otherwise the drive goes to the dumpster. > >I have it attached to a SCSI bus with a hard drive attached (id #0). The >tape is id #1. The host adapter is an Adaptec 2930C at id #7. I have >verified no SCSI ID conflicts by removing each device and probing. > >I get the exact same error message when I 'mt -f /dev/rsa0 status'. > >I am running a 4.1.1 GENERIC kernel (freshly installed OS). > >:>>> Any help in mounting this beast and get backups done would be >appreciated. >:>> >:>> Type changing dup switch 4 to on, on the MX Card. >:> >:> Thanks for replying. I unfortunately must show my ignorance and ask "What >:> is an MX Card?" Are you referring to the SCCI controller or a card >:> physically attached to the tape drive. >: >:I believe the MX board is the second from the back ot the unit. You >:should see an 8-position DIP switch on the right (looking from the >:front). Unfortunately, the units I have have special screws for which >:I don't have any screwdrivers available here. I'll see if I can >:arrange something tomorrow. > >The small screws are Torx T-8 and the large are T-10. Examining the MX 2 >card DIP block, factory settings were different from what I find on >Exabyte's web site. They say default is all switches "off". > >http://www.exabyte.com/suppserv/techsupp/8mm/fullhigh/in0011.html > >On mine, switches 2, 3, 4, 5, and 8 were on by default (ie, for use in an >RS/6000). > >I tried moving all switches to off, and all switches off but 4 on. > >When switch 4 is _off_ the drive returns an error immediately after an >'mt -f /dev/rsa0 status'. If switch 4 is _on_ it takes about 10 seconds >and then returns the same error, after blinking the drive lights and >making it's little Exabyte tape tensioning noises. > >I realize that Exabyte shipped drives with insane firmware variations >(especially OEM) but this drive previously worked (a while ago) in a Linux >box (Intel hardware) with a 1.2 kernel, which seems like a good sign. > >If anyone has the dirt on this drive, please drop me a note. > >--Paul > >Copyright (c) 1992-2000 The FreeBSD Project. >Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. >FreeBSD 4.1.1-RELEASE #0: Tue Sep 26 00:46:59 GMT 2000 > jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC >Timecounter "i8254" frequency 1193182 Hz >CPU: Pentium/P54C (99.87-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x526 Stepping = 6 > Features=0x1bf >real memory = 33488896 (32704K bytes) >config> di sn0 >config> di lnc0 >config> di le0 >config> di ie0 >config> di fe0 >config> di ed0 >config> di cs0 >config> di bt0 >config> di ata1 >config> di ata0 >config> di aic0 >config> di aha0 >config> di adv0 >config> q >avail memory = 28614656 (27944K bytes) >Preloaded elf kernel "kernel" at 0xc0416000. >Preloaded userconfig_script "/boot/kernel.conf" at 0xc041609c. >Intel Pentium detected, installing workaround for F00F bug >md0: Malloc disk >npx0: on motherboard >npx0: INT 16 interface >pcib0: on motherboard >pci0: on pcib0 >isab0: at device 7.0 on pci0 >isa0: on isab0 >atapci0: port 0xffa0-0xffaf at device 7.1 >on pci0 >atapci0: Busmastering DMA not enabled >uhci0: port 0xef80-0xef9f irq 11 >at device 7.2 on pci0 >usb0: on uhci0 >usb0: USB revision 1.0 >uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub0: 2 ports with 2 removable, self powered >chip1: port 0xfcb0-0xfcbf at >device 7.3 on pci0 >ahc0: port 0xec00-0xecff mem >0xfebef000-0xfebeffff irq 9 at device 18.0 on pci0 >aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs >pci0: at 20.0 irq 11 >ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 10 on isa0 >ep0: Ethernet address 00:a0:24:4d:35:5f >fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 >fdc0: FIFO enabled, 8 bytes threshold >fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >atkbdc0: at port 0x60,0x64 on isa0 >atkbd0: flags 0x1 irq 1 on atkbdc0 >kbd0 at atkbd0 >vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >sc0: at flags 0x100 on isa0 >sc0: VGA <16 virtual consoles, flags=0x300> >sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >sio0: type 16550A >sio1 at port 0x2f8-0x2ff irq 3 on isa0 >sio1: type 16550A >ppc0: at port 0x378-0x37f irq 7 on isa0 >ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode >ppc0: FIFO with 16/16/9 bytes threshold >plip0: on ppbus0 >lpt0: on ppbus0 >lpt0: Interrupt-driven port >ppi0: on ppbus0 >Waiting 15 seconds for SCSI devices to settle >sa0 at ahc0 bus 0 target 1 lun 0 >sa0: Removable Sequential Access SCSI-CCS device >sa0: 3.300MB/s transfers >da0 at ahc0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI-2 device >da0: 10.000MB/s transfers (10.000MHz, offset 15) >da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) >Mounting root from ufs:/dev/da0s1a >(sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 >(sa0:ahc0:0:1:0): ILLEGAL REQUEST >(sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 >(sa0:ahc0:0:1:0): ILLEGAL REQUEST >(sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 >(sa0:ahc0:0:1:0): ILLEGAL REQUEST >(sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 >(sa0:ahc0:0:1:0): ILLEGAL REQUEST >(sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 >(sa0:ahc0:0:1:0): ILLEGAL REQUEST >(sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 >(sa0:ahc0:0:1:0): ILLEGAL REQUEST To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 27 13:37:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 9DB5D37B479; Mon, 27 Nov 2000 13:37:36 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 140Vxu-0001hB-00; Mon, 27 Nov 2000 21:37:34 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eARLajD01908; Mon, 27 Nov 2000 22:36:45 +0100 (CET) (envelope-from wkb) Date: Mon, 27 Nov 2000 22:36:45 +0100 From: Wilko Bulte To: "Eric S. Nooden" Cc: Paul Southworth , Greg Lehey , Michael Hughes , freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Mounting a SCSI tape drive Message-ID: <20001127223645.C1846@freebie.demon.nl> References: <19991202195345.47886@mojave.sitaranetworks.com> <4.3.2.7.2.20001127144047.00b4c4f0@pop3.norton.antivirus> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.2.7.2.20001127144047.00b4c4f0@pop3.norton.antivirus>; from noodene@beloit.edu on Mon, Nov 27, 2000 at 02:43:35PM -0600 X-OS: FreeBSD 4.2-RELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 27, 2000 at 02:43:35PM -0600, Eric S. Nooden wrote: FYI: Nov 26 21:52:40 freebie /kernel: sa0: Removable Sequential Access SCSI-CCS device has been working well for me. Not that I use it very often, my DLT4000 is a lotter quicker/better. > I was in communication with Greg Lehey about this matter and at the time he > had not come up with a solution since he had not yet received the Exabyte > drives. I am also still interested in a solution since I have yet to back > up my system. > > Thanks, > Eric > > > At 01:03 PM 11/24/2000 -0500, Paul Southworth wrote: > > >[About a year ago there was a thread on freebsd-questions about Exabyte > >8200 drives which I would like to revive with the hope that someone found > >a solution.] > > > >On Thu, 2 Dec 1999, Greg Lehey wrote: > > > >:On Thursday, 2 December 1999 at 15:17:47 -0600, Eric S. Nooden wrote: > >:> At 02:29 PM 12/2/99 -0600, Michael Hughes wrote: > >:>> Eric S. Nooden said in email to me: > >:>>> > >:>>> I am running into some problems trying to mount a tape drive. When I > >run: > >:>>> > >:>>> mt -f /dev/nrsa0 rewind (or any command i.e. status) > >:>>> > >:>>> I get the following error message: > >:>>> > >:>>> (sa0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > >:>>> (sa0:ahc0:0:4:0): ILLEGAL REQUEST > >:>>> > >:>>> ***I did notice that when the command ran, the light on the tape > >drive did > >:>>> flash. > >:>>> > >:>>> The file /var/log/messages reports the following about sa0: > >:>>> > >:>>> sa0: at ahc0 bus 0 target 4 lun 0 > >:>>> sa0: Removable Sequential Access SCSI-CCS device > >:>>> sa0: 3.300MB/s transfers > > > >I have what appears to be an almost identical drive. Mine is reported > >as " Removable Sequential Access SCSI-CCS device". -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 27 13:39:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from locust.etext.org (locust.etext.org [216.93.75.148]) by hub.freebsd.org (Postfix) with ESMTP id 0D09237B4C5; Mon, 27 Nov 2000 13:39:35 -0800 (PST) Received: from localhost (pauls@localhost) by locust.etext.org (8.11.0/8.11.0) with ESMTP id eARLeEI81211; Mon, 27 Nov 2000 16:40:14 -0500 (EST) (envelope-from pauls@etext.org) Date: Mon, 27 Nov 2000 16:40:14 -0500 (EST) From: Paul Southworth To: Wilko Bulte Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Mounting a SCSI tape drive In-Reply-To: <20001127223645.C1846@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 27 Nov 2000, Wilko Bulte wrote: :Nov 26 21:52:40 freebie /kernel: sa0: Removable :Sequential Access SCSI-CCS device : :has been working well for me. Not that I use it very often, my DLT4000 :is a lotter quicker/better. What version of FreeBSD are you running, what SCSI controller are you using, and what are the DIP switch settings on the MX 2 card in your Exabyte? --Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 27 13:47:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id F208B37B479; Mon, 27 Nov 2000 13:47:11 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 140W77-0004Jg-00; Mon, 27 Nov 2000 21:47:05 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eARLj1M02041; Mon, 27 Nov 2000 22:45:01 +0100 (CET) (envelope-from wkb) Date: Mon, 27 Nov 2000 22:45:01 +0100 From: Wilko Bulte To: Paul Southworth Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Mounting a SCSI tape drive Message-ID: <20001127224501.A2021@freebie.demon.nl> References: <20001127223645.C1846@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from pauls@etext.org on Mon, Nov 27, 2000 at 04:40:14PM -0500 X-OS: FreeBSD 4.2-RELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 27, 2000 at 04:40:14PM -0500, Paul Southworth wrote: > On Mon, 27 Nov 2000, Wilko Bulte wrote: > > :Nov 26 21:52:40 freebie /kernel: sa0: Removable > :Sequential Access SCSI-CCS device > : > :has been working well for me. Not that I use it very often, my DLT4000 > :is a lotter quicker/better. > > > What version of FreeBSD are you running, what SCSI controller are you 4.2R / Adaptec 2940UW > using, and what are the DIP switch settings on the MX 2 card in your > Exabyte? Dunno. It is built into a DEC StorageWorks brick (homebuiltin) and I cannot check this without dismantling the whole thing. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 28 5:44:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay2.flashnet.it (libra.cyb.it [212.11.95.209]) by hub.freebsd.org (Postfix) with ESMTP id B50D837B400 for ; Tue, 28 Nov 2000 05:44:23 -0800 (PST) Received: from smtp.flashnet.it (ip215.pool-173.cyb.it [195.191.181.216]) by relay2.flashnet.it (EMS-RELAY/8.10.0) with SMTP id eASDiHq32532 for ; Tue, 28 Nov 2000 14:44:17 +0100 Message-Id: <200011281344.eASDiHq32532@relay2.flashnet.it> To: freebsd-scsi@FreeBSD.ORG X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Tue, 28 Nov 2000 14:44:14 EST From: Andrea Venturoli Reply-To: Andrea Venturoli Subject: Re: Zip Zoom Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ** Reply to note from Jussi Reissell 27 Nov 2000 20:32:18 +0200 > Not really. The aic driver seems to have problems if there's a Zip > drive plugged in. There's a pending pr: But I have none! It may not seem obvious from my message: the only device I attached to the Zip Zoom is the IBM HD. (The Zip's happily working on another machine). Bye & Thanks av. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 28 10:51:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.megacom.com.br (unknown [200.244.138.3]) by hub.freebsd.org (Postfix) with SMTP id B2ED337B402 for ; Tue, 28 Nov 2000 10:51:36 -0800 (PST) Received: from estudiosmega.com.br ([200.244.138.118] ) by ns.megacom.com.br (AppleShare IP Mail Server 6.2.1) id 71700 via TCP with SMTP; Tue, 28 Nov 2000 16:40:18 -0200 Message-ID: <3A23FBDC.9021B8A5@estudiosmega.com.br> Date: Tue, 28 Nov 2000 16:39:29 -0200 From: Eron Cardoso X-Mailer: Mozilla 4.75 (Macintosh; U; PPC) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: SYM53C1010 Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does SYM53C1010 (DC-390U3W) work with freeBSD 4.2 ? Thanks, Eron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 28 12: 6:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id 63EEB37B400 for ; Tue, 28 Nov 2000 12:06:28 -0800 (PST) Received: from nas1-64.mea.club-internet.fr (nas1-64.mea.club-internet.fr [195.36.139.64]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA03027; Tue, 28 Nov 2000 21:06:09 +0100 (MET) Date: Tue, 28 Nov 2000 20:06:17 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Eron Cardoso Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SYM53C1010 In-Reply-To: <3A23FBDC.9021B8A5@estudiosmega.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 28 Nov 2000, Eron Cardoso wrote: > Does SYM53C1010 (DC-390U3W) work with freeBSD 4.2 ? Yes. The C1010 support, including Ultra-160 DT data transfer with this chip, is available since FreeBSD-4.0. If you haven't the `sym.4' driver man page, let me know and I will send you it by private mail. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 28 14:57:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from demon.ildm.com (demon.ildm.com [216.120.42.186]) by hub.freebsd.org (Postfix) with ESMTP id 6484F37B400 for ; Tue, 28 Nov 2000 14:57:15 -0800 (PST) Received: (from root@localhost) by demon.ildm.com (8.11.1/8.11.1) id eASMxlN80242 for freebsd-scsi@freebsd.org; Tue, 28 Nov 2000 14:59:47 -0800 (PST) (envelope-from ataru) Date: Tue, 28 Nov 2000 14:59:46 -0800 From: fbscsi@ildm.com To: freebsd-scsi@freebsd.org Subject: SCSI Canisters Message-ID: <20001128145946.A80230@demon.ildm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I'm just curious... Is there a consensus on a good manufacturer for scsi canisters? Specifically, ones that work well with U2W LVD and U160? Thanks. --Brennon Church To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 28 22:40:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 563DD37B400 for ; Tue, 28 Nov 2000 22:40:27 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 1410Ep-0001KV-00; Tue, 28 Nov 2000 21:57:03 -0800 Date: Tue, 28 Nov 2000 21:56:53 -0800 (PST) From: Tom Samplonius To: fbscsi@ildm.com Cc: freebsd-scsi@freebsd.org Subject: Re: SCSI Canisters In-Reply-To: <20001128145946.A80230@demon.ildm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 28 Nov 2000 fbscsi@ildm.com wrote: > Hello all, > > I'm just curious... Is there a consensus on a good manufacturer for scsi > canisters? Specifically, ones that work well with U2W LVD and U160? > > Thanks. > > --Brennon Church Canisters? I guess you mean hot swap bays? Personally, I've sworn off those individual hotswap bays. They introduce so many connections, and so many opportunities for problems. I really don't know if it is possible to maintain U2 or U160 quality cabling first from a ribbon cable to the outside of the bay, then through the stub cable inside the cartridge to the drive. I always go for backplane type solutions that use SCA connector drives that plug right into a backplane. You only need one cable and one connector to connect the backplane to the controller. Many servers (Dell, IBM, etc) have SCSI backplanes standard in their servers. The Dell PowerEdge 4200 is nice (6 hotswap bays on a backplane). So is the IBM Netfinity 4500R/x340 (3 stock hotswap bays on a backplane, another backplane with another three drives can be added). You can get internal enclosures that use the backplanes too. I like the DPT RAIDStation 7. DPT doesn't actually make them, they just put their name on them. They are the same enclosures that NetApp uses for their storage servers. They have a SCSI (U2/U160) backplane, have redundant power and fans. Plus they are SAF-TE compliant, so drive, power, temparature, and fan status is available to your controller. With many RAID controllers, this makes drive replacements automatic, as SAF-TE enclosures allow the controller to detect drive insertion properly. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 1: 2:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EBCAB37B401; Wed, 29 Nov 2000 01:02:43 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA21554; Wed, 29 Nov 2000 01:02:14 -0800 Date: Wed, 29 Nov 2000 01:02:14 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Paul Southworth Cc: Greg Lehey , "Eric S. Nooden" , Michael Hughes , freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Mounting a SCSI tape drive In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There's an open PR about this. You have early enough f/w so that the structured mode page stuff that came in with CCS isn't known yet. On Fri, 24 Nov 2000, Paul Southworth wrote: > > [About a year ago there was a thread on freebsd-questions about Exabyte > 8200 drives which I would like to revive with the hope that someone found > a solution.] > > On Thu, 2 Dec 1999, Greg Lehey wrote: > > :On Thursday, 2 December 1999 at 15:17:47 -0600, Eric S. Nooden wrote: > :> At 02:29 PM 12/2/99 -0600, Michael Hughes wrote: > :>> Eric S. Nooden said in email to me: > :>>> > :>>> I am running into some problems trying to mount a tape drive. When I run: > :>>> > :>>> mt -f /dev/nrsa0 rewind (or any command i.e. status) > :>>> > :>>> I get the following error message: > :>>> > :>>> (sa0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > :>>> (sa0:ahc0:0:4:0): ILLEGAL REQUEST > :>>> > :>>> ***I did notice that when the command ran, the light on the tape drive did > :>>> flash. > :>>> > :>>> The file /var/log/messages reports the following about sa0: > :>>> > :>>> sa0: at ahc0 bus 0 target 4 lun 0 > :>>> sa0: Removable Sequential Access SCSI-CCS device > :>>> sa0: 3.300MB/s transfers > > I have what appears to be an almost identical drive. Mine is reported > as " Removable Sequential Access SCSI-CCS device". > > This was a drive Exabyte made OEM for IBM and was sold in RS/6000s ten > years ago, white faceplate and round blue eject button. I am aware that > it is a piece of crap - if I can make it work this whole machine is going > to a charitable cause, otherwise the drive goes to the dumpster. > > I have it attached to a SCSI bus with a hard drive attached (id #0). The > tape is id #1. The host adapter is an Adaptec 2930C at id #7. I have > verified no SCSI ID conflicts by removing each device and probing. > > I get the exact same error message when I 'mt -f /dev/rsa0 status'. > > I am running a 4.1.1 GENERIC kernel (freshly installed OS). > > :>>> Any help in mounting this beast and get backups done would be appreciated. > :>> > :>> Type changing dup switch 4 to on, on the MX Card. > :> > :> Thanks for replying. I unfortunately must show my ignorance and ask "What > :> is an MX Card?" Are you referring to the SCCI controller or a card > :> physically attached to the tape drive. > : > :I believe the MX board is the second from the back ot the unit. You > :should see an 8-position DIP switch on the right (looking from the > :front). Unfortunately, the units I have have special screws for which > :I don't have any screwdrivers available here. I'll see if I can > :arrange something tomorrow. > > The small screws are Torx T-8 and the large are T-10. Examining the MX 2 > card DIP block, factory settings were different from what I find on > Exabyte's web site. They say default is all switches "off". > > http://www.exabyte.com/suppserv/techsupp/8mm/fullhigh/in0011.html > > On mine, switches 2, 3, 4, 5, and 8 were on by default (ie, for use in an > RS/6000). > > I tried moving all switches to off, and all switches off but 4 on. > > When switch 4 is _off_ the drive returns an error immediately after an > 'mt -f /dev/rsa0 status'. If switch 4 is _on_ it takes about 10 seconds > and then returns the same error, after blinking the drive lights and > making it's little Exabyte tape tensioning noises. > > I realize that Exabyte shipped drives with insane firmware variations > (especially OEM) but this drive previously worked (a while ago) in a Linux > box (Intel hardware) with a 1.2 kernel, which seems like a good sign. > > If anyone has the dirt on this drive, please drop me a note. > > --Paul > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.1.1-RELEASE #0: Tue Sep 26 00:46:59 GMT 2000 > jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium/P54C (99.87-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x526 Stepping = 6 > Features=0x1bf > real memory = 33488896 (32704K bytes) > config> di sn0 > config> di lnc0 > config> di le0 > config> di ie0 > config> di fe0 > config> di ed0 > config> di cs0 > config> di bt0 > config> di ata1 > config> di ata0 > config> di aic0 > config> di aha0 > config> di adv0 > config> q > avail memory = 28614656 (27944K bytes) > Preloaded elf kernel "kernel" at 0xc0416000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc041609c. > Intel Pentium detected, installing workaround for F00F bug > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 > atapci0: Busmastering DMA not enabled > uhci0: port 0xef80-0xef9f irq 11 at device 7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > chip1: port 0xfcb0-0xfcbf at device 7.3 on pci0 > ahc0: port 0xec00-0xecff mem 0xfebef000-0xfebeffff irq 9 at device 18.0 on pci0 > aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs > pci0: at 20.0 irq 11 > ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 10 on isa0 > ep0: Ethernet address 00:a0:24:4d:35:5f > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > Waiting 15 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 1 lun 0 > sa0: Removable Sequential Access SCSI-CCS device > sa0: 3.300MB/s transfers > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15) > da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) > Mounting root from ufs:/dev/da0s1a > (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > (sa0:ahc0:0:1:0): ILLEGAL REQUEST > (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > (sa0:ahc0:0:1:0): ILLEGAL REQUEST > (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > (sa0:ahc0:0:1:0): ILLEGAL REQUEST > (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > (sa0:ahc0:0:1:0): ILLEGAL REQUEST > (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > (sa0:ahc0:0:1:0): ILLEGAL REQUEST > (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 > (sa0:ahc0:0:1:0): ILLEGAL REQUEST > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 6: 1:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from locust.etext.org (locust.etext.org [216.93.75.148]) by hub.freebsd.org (Postfix) with ESMTP id F122237B402; Wed, 29 Nov 2000 06:01:12 -0800 (PST) Received: from localhost (pauls@localhost) by locust.etext.org (8.11.0/8.11.0) with ESMTP id eATE1sT07487; Wed, 29 Nov 2000 09:01:55 -0500 (EST) (envelope-from pauls@etext.org) Date: Wed, 29 Nov 2000 09:01:54 -0500 (EST) From: Paul Southworth To: Matthew Jacob Cc: Greg Lehey , "Eric S. Nooden" , Michael Hughes , freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Mounting a SCSI tape drive In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 29 Nov 2000, Matthew Jacob wrote: :There's an open PR about this. You have early enough f/w so that the :structured mode page stuff that came in with CCS isn't known yet. OK - I have concluded that this drive is a waste of time, so I yanked it and replaced it with an old DAT. If my Exabyte 8200 can be useful to anyone in writing/fixing a driver, let me know and I'll ship it anywhere in the US. If I ever get it back, that would be nice, but it would be hard to be heartbroken about never seeing it again. Thanks, --Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 7:59:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from demon.ildm.com (demon.ildm.com [216.120.42.186]) by hub.freebsd.org (Postfix) with ESMTP id 0DE7637B698 for ; Wed, 29 Nov 2000 07:59:53 -0800 (PST) Received: (from root@localhost) by demon.ildm.com (8.11.1/8.11.1) id eATG2Yh82638 for freebsd-scsi@freebsd.org; Wed, 29 Nov 2000 08:02:34 -0800 (PST) (envelope-from ataru) Date: Wed, 29 Nov 2000 08:02:34 -0800 From: bchurch@ildm.com To: freebsd-scsi@freebsd.org Subject: Re: SCSI Canisters Message-ID: <20001129080234.A82620@demon.ildm.com> References: <20001128145946.A80230@demon.ildm.com> <3A24D2E4.27016268@nasby.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A24D2E4.27016268@nasby.net>; from jim@nasby.net on Wed, Nov 29, 2000 at 03:56:52AM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry about that. I'm referring to individual drive enclosures, such as the one shown here: http://www.storcase.com/dexpress/de200.asp I'm using a rather generic brand of them right now, but am looking for something more reliable. I don't really care much about extra features, such as a display on the front. Primarily, I am interested in good quality enclosures that have worked well for others. Thanks again. --Brennon Church On Wed, Nov 29, 2000 at 03:56:52AM -0600, Jim C. Nasby wrote: > Dumb question... what's a SCSI canister? > > fbscsi@ildm.com wrote: > > > > Hello all, > > > > I'm just curious... Is there a consensus on a good manufacturer for scsi > > canisters? Specifically, ones that work well with U2W LVD and U160? > > > > Thanks. > > > > --Brennon Church > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > -- > Jim C. Nasby (aka Decibel!) /^\ > jim@nasby.net /___\ > Freelance lighting designer and database developer / | \ > Member: Triangle Fraternity, Sports Car Club of America /___|___\ > > Give your computer some brain candy! www.distributed.net Team #1828 > Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 10:50:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9F2D037B402; Wed, 29 Nov 2000 10:50:05 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA23268; Wed, 29 Nov 2000 10:49:38 -0800 Date: Wed, 29 Nov 2000 10:49:33 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Paul Southworth Cc: Greg Lehey , "Eric S. Nooden" , Michael Hughes , freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Mounting a SCSI tape drive In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Actually, yes- would you? *All* of my tape drives (including an Archive QIC-150) have no troubles like this- with the exception of the lone Emulex MT-02 for which I don't think I have a working QIC-36 drive- and I won't support the MT-02 because it has all NULLs for INQUIRY data. I'll send separate mail for mailing info. -matt > On Wed, 29 Nov 2000, Matthew Jacob wrote: > > :There's an open PR about this. You have early enough f/w so that the > :structured mode page stuff that came in with CCS isn't known yet. > > OK - I have concluded that this drive is a waste of time, so I yanked it > and replaced it with an old DAT. If my Exabyte 8200 can be useful to > anyone in writing/fixing a driver, let me know and I'll ship it anywhere > in the US. If I ever get it back, that would be nice, but it would be hard > to be heartbroken about never seeing it again. > > Thanks, > > --Paul > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 11:38:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1C6F137B6B6 for ; Wed, 29 Nov 2000 11:38:36 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA23454; Wed, 29 Nov 2000 11:38:22 -0800 Date: Wed, 29 Nov 2000 11:38:17 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: "Justin T. Gibbs" , Chuck McCrobie , freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD In-Reply-To: <20001124084425.A27240@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >IntraServer card, but the sym_hipd.c does not mention anything about > > >putting it into target mode. > > > > I haven't looked to see how hard RFC2143 would be to implement, > > but both the isp (Qlogic controllers) and aic7xxx (Adaptec > > controllers) drivers have support for target mode. > > Matt once told me that isp target mode is not really well tested. > Would be interesting to have for things like shared disk - SCSI clusters > as well. FreeBSD target mode for isp isn't fully shaken out, and has some problems that I need to address for the newer SCSI controllers, but by and large it works pretty well- after all, in it's solaris instantiation, it's part of the Veritas Storage Appliance. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 11:39: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BA27937B698 for ; Wed, 29 Nov 2000 11:39:06 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA23471; Wed, 29 Nov 2000 11:39:06 -0800 Date: Wed, 29 Nov 2000 11:39:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Chuck McCrobie , freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD In-Reply-To: <200011240316.eAO3Go489714@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think this is fairly low on our list right now. > >RFC 2143 - Encapsulating IP with SCSI > > > >Is there planned FreeBSD support for this RFC? > > > >What SCSI controllers are capable of target mode? I have a NCR 875 > >IntraServer card, but the sym_hipd.c does not mention anything about > >putting it into target mode. > > I haven't looked to see how hard RFC2143 would be to implement, > but both the isp (Qlogic controllers) and aic7xxx (Adaptec > controllers) drivers have support for target mode. > > -- > Justin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 11:40:13 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 21D4037B401 for ; Wed, 29 Nov 2000 11:40:11 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA23480; Wed, 29 Nov 2000 11:40:02 -0800 Date: Wed, 29 Nov 2000 11:39:57 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Tom Samplonius Cc: Chuck McCrobie , freebsd-scsi@FreeBSD.ORG Subject: SCSI over IP [ was Re: RFC 2143 (IP over SCSI) Support in FreeBSD ] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 23 Nov 2000, Tom Samplonius wrote: > > On Thu, 23 Nov 2000, Chuck McCrobie wrote: > > > RFC 2143 - Encapsulating IP with SCSI > > > > Is there planned FreeBSD support for this RFC? > > > > What SCSI controllers are capable of target mode? I have a NCR 875 > > IntraServer card, but the sym_hipd.c does not mention anything about > > putting it into target mode. > > > > Thanks, > > Is there planned support for SCSI over IP? I've just seen a storage > server that uses SCSI over IP. The reasoning is that gigabit ethernet is > just as fast as fibrechannel, and much more standard. Both of those points are easily debatable, but the short answer is, yes, we're very interested in SCSI over IP. > They have drivers > for Linux and NT, and have announced that a driver will be released for > FreeBSD in early 2001? Apparently the driver simply probes the LAN for > SCSI devices and attaches each discovered storage server as a LUN. For > some reason the name of this product escapes me. > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 11:43:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F101E37B402 for ; Wed, 29 Nov 2000 11:43:52 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA23500; Wed, 29 Nov 2000 11:43:33 -0800 Date: Wed, 29 Nov 2000 11:43:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nat Lanza Cc: Tom Samplonius , Chuck McCrobie , freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 24 Nov 2000, Nat Lanza wrote: > Tom Samplonius writes: > > > Is there planned support for SCSI over IP? I've just seen a storage > > server that uses SCSI over IP. The reasoning is that gigabit ethernet is > > just as fast as fibrechannel, and much more standard. They have drivers > > for Linux and NT, and have announced that a driver will be released for > > FreeBSD in early 2001? Apparently the driver simply probes the LAN for > > SCSI devices and attaches each discovered storage server as a LUN. For > > some reason the name of this product escapes me. > > Please keep in mind that SCSI-over-IP is currently the topic of an > active IETF working group, and the protocol development is not > finished. It would probably be best to wait for the standard to > actually be finalized before adding support, since having support that > doesn't interoperate is not much better than having no support. The > current timeline has the standard proposal being submitted next May. Yes and no. The ANSI SCSI-2 spec took years to finalize. Same for SCSI-3. If it's a worthwhile feature, and you're dealing just with the software instantiation, it might be worth looking at doing for early releases. If you're burning silicon, hmm, that'd be questionable. > > If you're interested in following the progress of the standard, the IP > Storage working group's charter is here: > > http://www.ietf.org/html.charters/ips-charter.html > > Additionally, there is a public mailing list archived here: > > http://ips.pdl.cs.cmu.edu/mail/maillist.html > > Subscription information for the list is available on the charter > page. > > > Our lab is working on SCSI-over-IP, and our target platforms are FreeBSD > and Linux. We would most likely be interested in contributing our code to > the FreeBSD community when we're done, but it's far too early to make any > promises. Can you keep us posted on this? We'd absolutely love it if CMU (d'ya work with Garth?) did this. > > Also, discussion at the SCSI panel at BSDCon indicated that the > FreeBSD SCSI developers are certainly interested in providing a > framework in which SCSI-over-IP can be supported well. Our initial > results show that it's possible to build a system with decent > performance over 100bT and gigabit links without any modifications to > the OS -- the driver builds as a self-contained KLD, and acts much > like any other SCSI HBA driver. Ah. Cool. Is this available to be looked at? Define 'decent'... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 11:46:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from temphost.dragondata.com (temphost.dragondata.com [63.167.131.128]) by hub.freebsd.org (Postfix) with ESMTP id 3524F37B401 for ; Wed, 29 Nov 2000 11:46:29 -0800 (PST) Received: (from toasty@localhost) by temphost.dragondata.com (8.9.3/8.9.3) id NAA54487 for freebsd-scsi@freebsd.org; Wed, 29 Nov 2000 13:50:52 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200011291950.NAA54487@temphost.dragondata.com> Subject: sym driver in 4.1.1+ on Proliant To: freebsd-scsi@freebsd.org Date: Wed, 29 Nov 2000 13:50:47 -0600 (CST) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got several Compaq Proliant ML530's with the internal '896 SCSI controller. Everything works great on 4.1-RELEASE. Going to 4.1.1 or 4.2 causes sym0 to say "Cannot allocate IRQ resource", followed by a kernel trap inside the sym driver. Has anyone experienced this, or know what I can try? -- Kevin Here's a dmesg from 4.1 where things do work: (the same issue occurs on a server with no PCI cards in it, except for an fxp0) Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #0: Thu Jul 27 04:44:16 GMT 2000 root@usw4.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (863.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 402636800 (393200K bytes) avail memory = 387260416 (378184K bytes) Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: (vendor=0x0e11, dev=0xa0f0) at 3.0 pci0: at 5.0 fxp0: port 0x2400-0x243f mem 0xc6800000-0xc68fffff,0xc69fd000-0xc69fdfff irq 5 at device 8.0 on pci0 fxp0: Ethernet address 00:50:8b:ae:c5:38 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x2440-0x244f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pcib2: on motherboard pci2: on pcib2 pci2: (vendor=0x1148, dev=0x4300) at 6.0 irq 10 pcib255: on motherboard pci255: on pcib255 pcib5: on motherboard pci5: on pcib5 sym0: <896> port 0x4000-0x40ff mem 0xc6bfc000-0xc6bfdfff,0xc6bffc00-0xc6bfffff irq 11 at device 4.0 on pci5 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym1: <896> port 0x4400-0x44ff mem 0xc6bf8000-0xc6bf9fff,0xc6bfbc00-0xc6bfbfff irq 15 at device 4.1 on pci5 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking pcib1: at device 7.0 on pci5 pci6: on pcib1 sf0: port 0x5000-0x50ff mem 0xc6d80000-0xc6dfffff irq 5 at device 4.0 on pci6 sf0: Ethernet address: 00:00:d1:ed:c0:e5 miibus0: on sf0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sf1: port 0x5400-0x54ff mem 0xc6d00000-0xc6d7ffff irq 5 at device 5.0 on pci6 sf1: Ethernet address: 00:00:d1:ed:c0:e6 miibus1: on sf1 ukphy1: on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sf2: port 0x5800-0x58ff mem 0xc6c80000-0xc6cfffff irq 5 at device 6.0 on pci6 sf2: Ethernet address: 00:00:d1:ed:c0:e7 miibus2: on sf2 ukphy2: on miibus2 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sf3: port 0x5c00-0x5cff mem 0xc6c00000-0xc6c7ffff irq 5 at device 7.0 on pci6 sf3: Ethernet address: 00:00:d1:ed:c0:e8 miibus3: on sf3 ukphy3: on miibus3 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib3: at device 9.0 on pci5 pci7: on pcib3 sf4: port 0x6000-0x60ff mem 0xc6f80000-0xc6ffffff irq 5 at device 4.0 on pci7 sf4: Ethernet address: 00:00:d1:ed:c0:7d miibus4: on sf4 ukphy4: on miibus4 ukphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sf5: port 0x6400-0x64ff mem 0xc6f00000-0xc6f7ffff irq 5 at device 5.0 on pci7 sf5: Ethernet address: 00:00:d1:ed:c0:7e miibus5: on sf5 ukphy5: on miibus5 ukphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sf6: port 0x6800-0x68ff mem 0xc6e80000-0xc6efffff irq 5 at device 6.0 on pci7 sf6: Ethernet address: 00:00:d1:ed:c0:7f miibus6: on sf6 ukphy6: on miibus6 ukphy6: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sf7: port 0x6c00-0x6cff mem 0xc6e00000-0xc6e7ffff irq 5 at device 7.0 on pci7 sf7: Ethernet address: 00:00:d1:ed:c0:80 miibus7: on sf7 ukphy7: on miibus7 ukphy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto eisa0: on motherboard mainboard0: on eisa0 slot 0 eisa0: unknown card @@@0000 (0x00000000) at slot 5 eisa0: unknown card @@@0000 (0x00000000) at slot 6 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: cannot reserve I/O port range ata0-slave: identify retries exceeded acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:da0s1a da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) vinum: loaded vinum: reading configuration from /dev/da2s1b vinum: updating configuration from /dev/da1s1b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 12:17:33 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with ESMTP id AB89E37B400 for ; Wed, 29 Nov 2000 12:17:29 -0800 (PST) Received: (from magus@localhost) by hurlame.pdl.cs.cmu.edu (8.11.1/8.11.1) id eATKHJq80311; Wed, 29 Nov 2000 15:17:19 -0500 (EST) (envelope-from magus) To: mjacob@feral.com Cc: Tom Samplonius , Chuck McCrobie , freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD References: From: Nat Lanza Date: 29 Nov 2000 15:17:17 -0500 In-Reply-To: Matthew Jacob's message of "Wed, 29 Nov 2000 11:43:29 -0800 (PST)" Message-ID: Lines: 57 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > Yes and no. The ANSI SCSI-2 spec took years to finalize. Same for SCSI-3. If > it's a worthwhile feature, and you're dealing just with the software > instantiation, it might be worth looking at doing for early releases. iSCSI has a much more limited scope than the T10 work; one of the major goals is to get something working and standardized quickly. But yes, there is the possibility of the standardization process taking a long time. Even so, I'd much rather see an effort to implement iSCSI based on the draft IETF documents than one to implement some vendor's incompatible thing. > > Our lab is working on SCSI-over-IP, and our target platforms are FreeBSD > > and Linux. We would most likely be interested in contributing our code to > > the FreeBSD community when we're done, but it's far too early to make any > > promises. > > Can you keep us posted on this? We'd absolutely love it if CMU (d'ya > work with Garth?) did this. Sure. Also, yes, I do work with Garth. He's no longer the director of the Parallel Data Lab now that he's working on his startup, though. These days the lab's headed by Dave Nagle, who's really more involved in the iSCSI stuff. > Ah. Cool. Is this available to be looked at? Define 'decent'... It's not available yet, but I hope it will be before too long. Our lab's industry sponsorship obligations and the time constraints of paper deadlines limit when and how we can publically release code, unfortunately. A simple (~1500 line) server using the Linux SCSI generic layer to talk to a Quantum Atlas 10K can pull sequential read/write data over a Myrinet link at media speeds (25MB/sec or so), and one using a SCSI ramdisk as backing store can do at least 35-40MB/sec over Myrinet. We see slightly lower performance over gigabit ether, but we haven't spent too much time optimizing gigabit performance. This is with a simple userlevel server and kernel-level client, and no unusual hardware (well, other than the Myrinet, I guess) -- the machines involved are generic PII boxes, and we're using standard unmodified TCP and SCSI. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 12:31:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E20AD37B400 for ; Wed, 29 Nov 2000 12:31:15 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA23731; Wed, 29 Nov 2000 12:31:02 -0800 Date: Wed, 29 Nov 2000 12:30:57 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nat Lanza Cc: Tom Samplonius , Chuck McCrobie , freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29 Nov 2000, Nat Lanza wrote: > Matthew Jacob writes: > > > Yes and no. The ANSI SCSI-2 spec took years to finalize. Same for SCSI-3. If > > it's a worthwhile feature, and you're dealing just with the software > > instantiation, it might be worth looking at doing for early releases. > > iSCSI has a much more limited scope than the T10 work; one of the > major goals is to get something working and standardized quickly. > > But yes, there is the possibility of the standardization process > taking a long time. > > Even so, I'd much rather see an effort to implement iSCSI based on the > draft IETF documents than one to implement some vendor's incompatible > thing. Of course. Implementing some vendor solution is pointless unless you're the vendor. FreeBSD is not the vendor. Ergo, FreeBSD will not implement some vendor solution. As a corollary, FreeBSD is also not pointless. Now, is that a perfect compound negative syllogism, or what? :-) > > > > Our lab is working on SCSI-over-IP, and our target platforms are FreeBSD > > > and Linux. We would most likely be interested in contributing our code to > > > the FreeBSD community when we're done, but it's far too early to make any > > > promises. > > > > Can you keep us posted on this? We'd absolutely love it if CMU (d'ya > > work with Garth?) did this. > > Sure. > > Also, yes, I do work with Garth. He's no longer the director of the > Parallel Data Lab now that he's working on his startup, though. These > days the lab's headed by Dave Nagle, who's really more involved in the > iSCSI stuff. > > > Ah. Cool. Is this available to be looked at? Define 'decent'... > > It's not available yet, but I hope it will be before too long. Our > lab's industry sponsorship obligations and the time constraints of > paper deadlines limit when and how we can publically release code, > unfortunately. > > A simple (~1500 line) server using the Linux SCSI generic layer to > talk to a Quantum Atlas 10K can pull sequential read/write data over a > Myrinet link at media speeds (25MB/sec or so), and one using a SCSI > ramdisk as backing store can do at least 35-40MB/sec over Myrinet. We > see slightly lower performance over gigabit ether, but we haven't > spent too much time optimizing gigabit performance. > > This is with a simple userlevel server and kernel-level client, and no > unusual hardware (well, other than the Myrinet, I guess) -- the > machines involved are generic PII boxes, and we're using standard > unmodified TCP and SCSI. Huh- what was the CPU utilization? I suspect higher than native, but CPU speed arguments are more or less now like what memory utilization arguments were ten years ago (obsoleted by having enough- i.e., requiring lots of memory or CPU isn't a problem if it's cheaply available). Still, that sounds to me like the concept is proved. Depending on whether or not the FC switch vendors can get out there with 10Gb switches before the Gb ethernet switch vendors will define whether FC dies in 3 years or in 6 years. Tsk- too bad- I've put a lot of effort in so far. Well, we'll see whether the s/w portions of Fibre Channel (e.g., the SAN domain stuff) gets to be usable within IP over SCSI. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 12:36:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 3586437B400 for ; Wed, 29 Nov 2000 12:36:43 -0800 (PST) Received: by gatekeeper.veriohosting.com; Wed, 29 Nov 2000 13:36:41 -0700 (MST) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma004352; Wed, 29 Nov 00 13:36:33 -0700 Received: from localhost (chrism@localhost) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id NAA80763 for ; Wed, 29 Nov 2000 13:36:23 -0700 (MST) Date: Wed, 29 Nov 2000 13:36:17 -0700 (MST) From: Chris Mutchler To: Subject: BusLogic/Mylex SCSI controller Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I did a fresh install of v4.1 last night on my system, and unfortunately it appears the my BusLogic SCSI controller is currently supported in FreeBSD. The card is supported in linux so I thought that I might be able to port the driver into FreeBSD. Has anyone tried this already, or know of a place that I could go to read up on how to port drivers from one *nix OS to another? Any assistance or ideas would be appreciated. Thanks. Chris Mutchler. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 12:47: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with ESMTP id 4243737B400 for ; Wed, 29 Nov 2000 12:46:57 -0800 (PST) Received: (from magus@localhost) by hurlame.pdl.cs.cmu.edu (8.11.1/8.11.1) id eATKkqv80353; Wed, 29 Nov 2000 15:46:53 -0500 (EST) (envelope-from magus) To: mjacob@feral.com Cc: Tom Samplonius , Chuck McCrobie , freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD References: From: Nat Lanza Date: 29 Nov 2000 15:46:52 -0500 In-Reply-To: Matthew Jacob's message of "Wed, 29 Nov 2000 12:30:57 -0800 (PST)" Message-ID: Lines: 33 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > Huh- what was the CPU utilization? I suspect higher than native, but > CPU speed arguments are more or less now like what memory > utilization arguments were ten years ago (obsoleted by having > enough- i.e., requiring lots of memory or CPU isn't a problem if > it's cheaply available). We aren't doing much CPU measurement at the moment; our current interests lie more towards network behaviour -- congestion and routing and the like -- than towards integrating iSCSI into systems. However, simple empirical stare-at-the-machine stuff shows that the client's CPU doesn't seem to be close to being pegged. The server's closer to being pegged, but we don't care much about that -- that's the part that's easiest to throw hardware at. And yeah, you're right about the availability. The folks who care most about high-speed SANs can easily afford fast CPUs for client machines. > Well, we'll see whether the s/w portions of Fibre Channel (e.g., the > SAN domain stuff) gets to be usable within IP over SCSI. I hope so. Storage management is irritating and hard, and I'd rather not see people reinvent the world yet again. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 29 14:24: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front4.grolier.fr (front4.grolier.fr [194.158.96.54]) by hub.freebsd.org (Postfix) with ESMTP id C375337B401 for ; Wed, 29 Nov 2000 14:23:56 -0800 (PST) Received: from nas1-13.cgy.club-internet.fr (nas1-13.cgy.club-internet.fr [195.36.197.13]) by front4.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA13203; Wed, 29 Nov 2000 23:23:45 +0100 (MET) Date: Wed, 29 Nov 2000 22:23:52 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Kevin Day Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym driver in 4.1.1+ on Proliant In-Reply-To: <200011291950.NAA54487@temphost.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 29 Nov 2000, Kevin Day wrote: > I've got several Compaq Proliant ML530's with the internal '896 SCSI > controller. Everything works great on 4.1-RELEASE. Going to 4.1.1 or 4.2 > causes sym0 to say "Cannot allocate IRQ resource", followed by a kernel t= rap > inside the sym driver. Has anyone experienced this, or know what I can tr= y? It has been no change in this area of the driver between 4.1 and 4.1.1. The driver normally allocates IRQs as shared resources as PCI requires interrupt lines to be shareable. The IRQ for `sym0' appears to be #11 on the boot messages below. I you didn't change any piece of hardware neither changed the IRQ (PNP?) settings from your motherboard setup, sym0 should still be assigned IRQ 11 on your machine. Anyway, it would be interesting to know if the IRQ now assigned to `sym0' (whatever it is still IRQ11 or not) is shared by `sym0' and another device that has kernel support in your kernel config (GENERIC?) for 4.1.1 but haven't support in your kernel config for 4.1. If, for example, IRQ 11 was allocated by another driver as non shareable and `sym' tries to allocate it as shareable, allocation of this resource by `sym' will fail with exactly the message your report. G=E9rard. > -- Kevin >=20 >=20 > Here's a dmesg from 4.1 where things do work: > (the same issue occurs on a server with no PCI cards in it, except for an= fxp0) >=20 >=20 > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.1-RELEASE #0: Thu Jul 27 04:44:16 GMT 2000 > root@usw4.freebsd.org:/usr/src/sys/compile/GENERIC > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (863.93-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x683 Stepping =3D 3 > Features=3D0x383f9ff > real memory =3D 402636800 (393200K bytes) > avail memory =3D 387260416 (378184K bytes) > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pci0: (vendor=3D0x0e11, dev=3D0xa0f0) at 3.0 > pci0: at 5.0 > fxp0: port 0x2400-0x243f mem 0xc6800000= -0xc68fffff,0xc69fd000-0xc69fdfff irq 5 at device 8.0 on pci0 > fxp0: Ethernet address 00:50:8b:ae:c5:38 > isab0: at device 15.0 o= n pci0 > isa0: on isab0 > atapci0: port 0x2440-0x244f at device 15.1 o= n pci0 > ata0: at 0x1f0 irq 14 on atapci0 > pcib2: on motherboard > pci2: on pcib2 > pci2: (vendor=3D0x1148, dev=3D0x4300) at 6.0 irq 10 > pcib255: on motherboard > pci255: on pcib255 > pcib5: on motherboard > pci5: on pcib5 > sym0: <896> port 0x4000-0x40ff mem 0xc6bfc000-0xc6bfdfff,0xc6bffc00-0xc6b= fffff irq 11 at device 4.0 on pci5 > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking > sym1: <896> port 0x4400-0x44ff mem 0xc6bf8000-0xc6bf9fff,0xc6bfbc00-0xc6b= fbfff irq 15 at device 4.1 on pci5 > sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking > pcib1: at device 7.0 on pci5 > pci6: on pcib1 > sf0: port 0x5000-0x50ff mem 0xc6d80000-0= xc6dfffff irq 5 at device 4.0 on pci6 > sf0: Ethernet address: 00:00:d1:ed:c0:e5 > miibus0: on sf0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf1: port 0x5400-0x54ff mem 0xc6d00000-0= xc6d7ffff irq 5 at device 5.0 on pci6 > sf1: Ethernet address: 00:00:d1:ed:c0:e6 > miibus1: on sf1 > ukphy1: on miibus1 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf2: port 0x5800-0x58ff mem 0xc6c80000-0= xc6cfffff irq 5 at device 6.0 on pci6 > sf2: Ethernet address: 00:00:d1:ed:c0:e7 > miibus2: on sf2 > ukphy2: on miibus2 > ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf3: port 0x5c00-0x5cff mem 0xc6c00000-0= xc6c7ffff irq 5 at device 7.0 on pci6 > sf3: Ethernet address: 00:00:d1:ed:c0:e8 > miibus3: on sf3 > ukphy3: on miibus3 > ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pcib3: at device 9.0 on pci5 > pci7: on pcib3 > sf4: port 0x6000-0x60ff mem 0xc6f80000-0= xc6ffffff irq 5 at device 4.0 on pci7 > sf4: Ethernet address: 00:00:d1:ed:c0:7d > miibus4: on sf4 > ukphy4: on miibus4 > ukphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf5: port 0x6400-0x64ff mem 0xc6f00000-0= xc6f7ffff irq 5 at device 5.0 on pci7 > sf5: Ethernet address: 00:00:d1:ed:c0:7e > miibus5: on sf5 > ukphy5: on miibus5 > ukphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf6: port 0x6800-0x68ff mem 0xc6e80000-0= xc6efffff irq 5 at device 6.0 on pci7 > sf6: Ethernet address: 00:00:d1:ed:c0:7f > miibus6: on sf6 > ukphy6: on miibus6 > ukphy6: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf7: port 0x6c00-0x6cff mem 0xc6e00000-0= xc6e7ffff irq 5 at device 7.0 on pci7 > sf7: Ethernet address: 00:00:d1:ed:c0:80 > miibus7: on sf7 > ukphy7: on miibus7 > ukphy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > eisa0: on motherboard > mainboard0: on eisa0 slot 0 > eisa0: unknown card @@@0000 (0x00000000) at slot 5 > eisa0: unknown card @@@0000 (0x00000000) at slot 6 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: cannot reserve I/O port range > ata0-slave: identify retries exceeded > acd0: CDROM at ata0-master using PIO4 > Waiting 15 seconds for SCSI devices to settle > Mounting root from ufs:da0s1a > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device=20 > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da1: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) > da2 at sym0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device=20 > da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da2: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device=20 > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da0: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) > vinum: loaded > vinum: reading configuration from /dev/da2s1b > vinum: updating configuration from /dev/da1s1b >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 30 7:32: 3 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from Mail6.Carolina.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id A23FC37B400 for ; Thu, 30 Nov 2000 07:31:59 -0800 (PST) Received: from 0020194323 ([24.163.75.224]) by Mail6.Carolina.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 30 Nov 2000 10:31:34 -0500 Message-ID: <000a01c05afb$c9ab1ee0$e04ba318@carolina.rr.com> From: "James c Hamrick" To: Subject: capture tv Date: Thu, 30 Nov 2000 10:31:41 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C05AB8.BACF3D40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C05AB8.BACF3D40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SIR=20 I HAVE CAPTURE TV M205 JUST GOT WINDOWS ME I NEED TO REINSTALL=20 YOUR HELP PLEASE jhamrick@carolina.rr.com ------=_NextPart_000_0007_01C05AB8.BACF3D40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
SIR
I HAVE CAPTURE TV M205
JUST GOT WINDOWS ME
I NEED TO REINSTALL
YOUR HELP PLEASE
 
jhamrick@carolina.rr.com
------=_NextPart_000_0007_01C05AB8.BACF3D40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 30 9:28:50 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D69437B401 for ; Thu, 30 Nov 2000 09:28:48 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id LAA18122; Thu, 30 Nov 2000 11:28:36 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 30 Nov 2000 11:28:36 -0600 (CST) From: Chris Dillon To: Kevin Day Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym driver in 4.1.1+ on Proliant In-Reply-To: <200011291950.NAA54487@temphost.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 29 Nov 2000, Kevin Day wrote: > I've got several Compaq Proliant ML530's with the internal '896 > SCSI controller. Everything works great on 4.1-RELEASE. Going to > 4.1.1 or 4.2 causes sym0 to say "Cannot allocate IRQ resource", > followed by a kernel trap inside the sym driver. Has anyone > experienced this, or know what I can try? I had this problem long before 4.1.1, several months ago, but I'm not exactly sure what caused it. I assume that your on-board SCSI controller is trying to use IRQ15. Go into the Compaq System Setup and make sure no devices are using IRQ15 except for possibly the on-board IDE controller (which is what is _supposed_ to be using it). That solved it for me. I've got a PR open on this, but I haven't yet had time to figure out exactly what caused it since it is on a production system. It might be a BIOS problem, but it definately works with some previous kernels and not with newer ones. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64 and PowerPC under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 30 12:11:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from boat.mail.pipex.net (our.mail.pipex.net [158.43.128.75]) by hub.freebsd.org (Postfix) with SMTP id CFB0237B400 for ; Thu, 30 Nov 2000 12:11:05 -0800 (PST) Received: (qmail 11430 invoked from network); 30 Nov 2000 20:11:04 -0000 Received: from mailhost.puck.pipex.net (HELO mailhost.uk.internal) (194.130.147.54) by our.mail.pipex.net with SMTP; 30 Nov 2000 20:11:04 -0000 Received: (qmail 14899 invoked from network); 30 Nov 2000 20:11:04 -0000 Received: from yukon.cam.uk.internal (172.31.3.155) by mailhost.uk.internal with SMTP; 30 Nov 2000 20:11:04 -0000 Date: Thu, 30 Nov 2000 20:04:52 +0000 (GMT) From: Darren Joy X-Sender: darrenj@yukon.cam.uk.internal To: freebsd-scsi@freebsd.org Subject: Problems with SYM and DC390W in 4.2 Release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some Background : I had a machine, running 3.2 Release, quite happily, without problem since that release came out. For reasons which I won't go into and which aren't relevant IMHO, it stayed as plain 3.2 until this week, when I decided to purge that and install 4.2 Release, using the same hardware. Some Kit : Intel PII Abit BH6 mb Tekram DC390W ( running from 50 pin interface ) Seagate 4GB Barracuda Conner CFP2105S 2GB and later a Fujitsu 9GB SUN disc Some Story : I removed the Barracuda to use in another machine, as this one would now be a workstation only. I tried to install 4.2, first via CD, and later via FTP. The install got so far, then totally hung the machine, always when installing the ports or the src distributions. The second VTY revealed some interesting error messages along the lines of : sym0:0: message d sent on bad reselection. sym0:0: message d sent on bad reselection. sym0:0: message d sent on bad reselection. sym0:0: message d sent on bad reselection. sym0:0:control msgout: 80 20 27 d. sym0:0:control msgout: 80 20 1d d. sym0:0:control msgout: 80 20 51 d. sym0:0:control msgout: 80 20 33 d. sym0:0:control msgout: 80 22 59 d. sym0:0:control msgout: 80 22 25 d. And I see this problem every time. If I omit the ports and source distributions, I can get it to install before I see the problem, but when I try to add them afterwards, same problem, same errors. I have formatted and verified the disc from the SCSI BIOS, and can find no errors on it. I have also tried disabling tagged-commands for this drive, no change. I offer this disc as doorstop #1. The Barracuda is dead too, won't report any drive statistics, although it will spin up. This though I am willing to entertain could have been damaged through a dodgy PSU ( in an altogether different machine from the one in discussion ), but it certainly won't work in this machine at the moment. I offer this disc as doorstep #2. Then I plugged in a Sun multi-pack containing the Fujitsu, to see if the install went ok on that, my thinking being that if the install succeeded, the culprit was a dodgy Conner disc ( which is old now ). The install completed without hitch, all distibutions went on fine. Then the reboot, and the SCSI controller gets no response from the Fujitsu. If I go into the SCSI BIOS, I can see it and read the stats on it, but on booting, nothing, just hangs the machine, never gets past that SCSI ID. So whatever FreeBSD did to that disc during the install, the DC390W couldn't see it afterwards... A low level format of the Fujitsu made it show up again in the scan, however, doesn't solve my problem, and low level formatting of the Conner did not help either. My question I guess is, are there known issues in 4.2 with the SYM driver and the DC390W? Should I risk another drive becoming a doorstop? This combination worked fine on Tuesday when it was happily running 3.2, so I am not keen to believe this is chance.. If it's a dodgy Conner disc, I am happy with that, but using a different disc rendered that disc inopperable as well, so I am suspicious of the controller/driver. Can anyone offer any information to end my torment? ( I have had a bad week for hard-discs.... ) Regards Darren Joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 30 14:18:50 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id C345437B402 for ; Thu, 30 Nov 2000 14:18:45 -0800 (PST) Received: from nas2-54.mea.club-internet.fr (nas2-54.mea.club-internet.fr [195.36.200.54]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA03333; Thu, 30 Nov 2000 23:18:40 +0100 (MET) Date: Thu, 30 Nov 2000 22:18:47 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Darren Joy Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problems with SYM and DC390W in 4.2 Release In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 30 Nov 2000, Darren Joy wrote: > Some Background : >=20 > I had a machine, running 3.2 Release, quite happily, without problem sinc= e > that release came out. For reasons which I won't go into and which aren't > relevant IMHO, it stayed as plain 3.2 until this week, when I decided to > purge that and install 4.2 Release, using the same hardware. >=20 > Some Kit : >=20 > Intel PII > Abit BH6 mb > Tekram DC390W ( running from 50 pin interface ) > Seagate 4GB Barracuda > Conner CFP2105S 2GB >=20 > and later a >=20 > Fujitsu 9GB SUN disc >=20 > Some Story : >=20 > I removed the Barracuda to use in another machine, as this one would now > be a workstation only. I tried to install 4.2, first via CD, and later vi= a > FTP. The install got so far, then totally hung the machine, always when > installing the ports or the src distributions. The second VTY revealed > some interesting error messages along the lines of : >=20 > sym0:0: message d sent on bad reselection. > sym0:0: message d sent on bad reselection. > sym0:0: message d sent on bad reselection. > sym0:0: message d sent on bad reselection. > The driver is reselected by TARGET #0 for a IO that does not exist in the= =20 task list as seen by the driver. > sym0:0:control msgout: 80 20 27 d. > sym0:0:control msgout: 80 20 1d d. > sym0:0:control msgout: 80 20 51 d. > sym0:0:control msgout: 80 20 33 d. > sym0:0:control msgout: 80 22 59 d. > sym0:0:control msgout: 80 22 25 d. The driver is aborting (under behalf of CAM) tasks that had been queued to TARGET #0. > And I see this problem every time. If I omit the ports and source > distributions, I can get it to install before I see the problem, but when > I try to add them afterwards, same problem, same errors. I have formatted > and verified the disc from the SCSI BIOS, and can find no errors on it. I > have also tried disabling tagged-commands for this drive, no change. >=20 > I offer this disc as doorstop #1. >=20 > The Barracuda is dead too, won't report any drive statistics, although it > will spin up. This though I am willing to entertain could have been > damaged through a dodgy PSU ( in an altogether different machine from the > one in discussion ), but it certainly won't work in this machine at the > moment. >=20 > I offer this disc as doorstep #2. >=20 > Then I plugged in a Sun multi-pack containing the Fujitsu, to see if the > install went ok on that, my thinking being that if the install succeeded, > the culprit was a dodgy Conner disc ( which is old now ). >=20 > The install completed without hitch, all distibutions went on fine. Then > the reboot, and the SCSI controller gets no response from the Fujitsu. If > I go into the SCSI BIOS, I can see it and read the stats on it, but on > booting, nothing, just hangs the machine, never gets past that SCSI ID. S= o > whatever FreeBSD did to that disc during the install, the DC390W couldn't > see it afterwards... The software killing drives is very unlikely, unless they were close to die naturally. Btw, can you retrieve at least some kernel boot messages that succeeds. Such info is far more useful than long literature. > A low level format of the Fujitsu made it show up again in the scan, > however, doesn't solve my problem, and low level formatting of the Conner > did not help either. >=20 > My question I guess is, are there known issues in 4.2 with the SYM driver > and the DC390W? Should I risk another drive becoming a doorstop? This > combination worked fine on Tuesday when it was happily running 3.2, so I > am not keen to believe this is chance.. Depends on how many doors you need to stop using dead hard disks. :o) If you really think it is the driver that killed your disks, then you can simply edit your kernel config and replace it by `ncr' that was the driver= =20 you probably were using under FreeBSD-3.2. > If it's a dodgy Conner disc, I am happy with that, but using a different > disc rendered that disc inopperable as well, so I am suspicious of the > controller/driver. > > Can anyone offer any information to end my torment?=20 > ( I have had a bad week for hard-discs.... ) I understand. But actual causes may well be quite unrelated to the driver/hba pair, but have been just bad luck or unlikely bad things that happened at the time. Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 30 17:19:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id ECDCD37B401 for ; Thu, 30 Nov 2000 17:19:21 -0800 (PST) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id RAA18534; Thu, 30 Nov 2000 17:18:55 -0800 (PST) Message-Id: <200012010118.RAA18534@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.4 #1[UCI] To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 29160 and 4.1/4.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Nov 2000 17:18:50 -0800 From: Dave Hayes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T Gibbs wrote a while back: > It really sounds like there is some kind of BIOS incompatibility with > that card, your motherboard, and FreeBSD. As soon as I get back > to work, I'll forward your problem to Adaptec's functional test > lab and see if we can find out what is going wrong. It's been a while, and I have more data, but no solution to my original problem (included below my .signature). So, I went on this presumption. I've tested three motherboards, with different BIOS, from different manufacturers. Asus P3V4X (Via Apollo chipset) FIC FB11 (BX440 chipset) Spacewalker AV61 (Via Apollo chipset) All three show the same problems with an Adaptec 29160, namely hanging right at bootmgr. I installed each time from a 4.1 CDROM, using just the minimal installation. It appeared to install cleanly each time. Each time I reinstalled, it was interesting to note that the "set bootable" flag in the partition editor was never actually set, but all the rest of the partition information was found just fine. I am using Adaptec BIOS version 2.57.2. There is no upgrade to that BIOS listed on the adaptec website. The card was taken from a running system and put back into a running system, so the card works. These motherboards booted cleanly with an adaptec 2940UW, so the motherboards are not the issue. At the moment, there are resources in place that could be of assistance in debugging this problem. Unfortunately I have no clue how to begin, since I know very little of low-level details and drivers. Is it possible you have found a fix yet, or know of a fix, or understand what is going on better than I do so that you can suggest a fix? Since adaptec is discontinuing 2940s, I feel it imperative to get this working or at least find out why it does not work. I am even quite willing to entertain that this may be user error, even though I have been installing FreeBSD since the 2.0 days, am fairly familiar with the install process, and can easily claim over 100 boxes out there which have been installed by my hand. Thanks in advance for any assistance. ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< A wise man listens to the words unsaid. ---Original plea for help follows--- I have spent a fair amount of time trying to use this card. I am still experiencing problems and I thought I would relay my experiences in the possible hope of getting someone more knowledgable than me to tell me how to proceed with this card. The motherboard I used was a ASUS P3V4X (using the VIA APOLLO 133 4X chipset I believe). On the adaptec 29160 was a 9GB 10K IBM LVD drive. I tried to initially boot using 4.1.1 floppies. Everything appeared to install ok, but when I tried to boot off the freshly installed disk it came back with: F1 FreeBSD Default: F1 and then proceeded to beep everytime I hit (or if it times out to boot anyway). I rebooted using floppy and checked the FDISK screen. The slice was tagged as bootable even though I had tagged it this way earlier upon initial install. I retagged it as bootable and attempted to reboot. Same result as above. Next, I tried the install process from the 4.1 CD. Same result as above. I popped in a trusty old adaptec 2940UW, and retried the install. This time it worked flawlessly. So, armed with a bootable SCSI disk, I then placed the drive on a 29160 and tried to boot it. This did not work, same symptoms as before. I scanned the archives for some time reading up on what others had experienced. I tried: -Every sensical combination of configuration options on the card -Turning off the BIOS of the 29160 -Using the slower SCSI bus -Slowing down the disk transfer rate. None of these worked. Does anyone here recognize any of these symptoms and know of a fix or something else to try? I really hate being told "29160s are the best you can get and they don't make 2940s anymore" and then not being able to get it to work with my favorite OS. Thanks in advance for any assistance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 1 13:33:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from red.gradwell.net (red.gradwell.net [195.149.39.8]) by hub.freebsd.org (Postfix) with SMTP id 8023337B400 for ; Fri, 1 Dec 2000 13:33:07 -0800 (PST) Received: (qmail 17729 invoked from network); 1 Dec 2000 21:32:56 -0000 Received: from ystwyth.demon.co.uk (HELO vaio.gradwell.com) (158.152.144.35) by pop3.gradwell.net with SMTP; 1 Dec 2000 21:32:56 -0000 Message-Id: <5.0.0.25.0.20001201212649.03798548@pop3.gradwell.net> X-Sender: postmaster%pop3.peterg.org.uk@pop3.gradwell.net X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 01 Dec 2000 21:32:54 +0000 To: freebsd-scsi@freebsd.org From: Peter Gradwell Subject: Mylex DAC960 Driver "online/offline" Cc: hirez@bratcave.org, cliff@onsea.com In-Reply-To: <20001129080234.A82620@demon.ildm.com> References: <3A24D2E4.27016268@nasby.net> <20001128145946.A80230@demon.ildm.com> <3A24D2E4.27016268@nasby.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a Mylex acceleraid 250 card in a FreeBSD 4.1 machine and when it boots it tells me that: ====== DAC960 BIOS Version 4.10-41 (Feb 02, 1999) Mylex Corporation DAC960PTL1 Firmware Version 4.07-0-29 DAC960 PCI Address: F4102000 Bus=0 Dev/Slot=13 Function=1 IRQ=11 DAC960 Memory = 8 MB (EDO/ECC) WARNING: 1 system drive offline WARNING: Dead SCSI device (Channel:Target) : 0:3 Press for BIOS options Press for RAID Configuration options 2 system drives installed Press any key to continue ====== - the off line disk is in a RAID 1 disk array is a RAID 1 disk array. The kernel then boots from this RAID 1 disk array. However, when FSCKing the / partition, (/dev/mlxd0s1a) it fails, because it thinks that mlxd0 is off line. I then get a fairly continuous stream of messages to the console saying: ====== mlxd0: drive online mlxd0: drive offline ====== I have contacted Mylex Tech Support and they say that this is a message given out by the kernel, and more properly, the FreeBSD driver in the kernel. However, they have no clue as to what or why that message is occurring, and more importantly, why it is occurring so much. Does anyone know why the kernel driver is reporting this. It doesn't seem sensible that the controller should be marking a drive off line and then online again, in a loop, ad infinitum. Mylex Tech Support agree. What does this message really mean? Many thanks peter -- peter gradwell; online @ http://www.gradwell.com/peter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 1 14:27: 3 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id C253437B400 for ; Fri, 1 Dec 2000 14:26:51 -0800 (PST) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA28122 for ; Fri, 1 Dec 2000 17:26:50 -0500 (EST) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA16679 for ; Fri, 1 Dec 2000 17:26:50 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA16674 for ; Fri, 1 Dec 2000 17:26:49 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Fri, 1 Dec 2000 17:26:49 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-scsi@freebsd.org Subject: kernel panics in 4.2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I sent this message to -questions,-current, and -stable earlier, but nobody seems to know about my problem: I just recently tried putting an adaptec 2940w SCSI controller into my FreeBSD machine (running -STABLE cvsupped and recompiled every night at 1:30AM) and since including the driver in my kernel I've noticed some random panics. Most of the time they occur during heavy disk activity, and usually only when I'm running X (hence the reason I couldn't tell you the panic message). Even wierder still, I don't even have any SCSI devices connected yet; I'm using only IDE disks connected via the motherboard's builtin ATA66. I have also searched the various FreeBSD mailinglist archives and found some people with the same problems I was having, but no solutions. Crashes do not occur in Windows with this configuration (at least not any more than usual :-) ) and when I take the ahc driver out of the kernel, the panics stop. I've included my dmesg -v output and my kernel config file, please let me know if anything else is needed. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Fri Dec 1 11:55:01 EST 2000 culverk@culverk.student.umd.edu:/usr/src/sys/compile/MYKERNEL Calibrating clock(s) ... TSC clock: 800028138 Hz, i8254 clock: 1193181 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x0035d000 - 0x07fe7fff, 130592768 bytes (31883 pages) avail memory = 127324160 (124340K bytes) bios32: Found BIOS32 Service Directory header at 0xc00faf90 bios32: Entry = 0xfb400 (c00fb400) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb430 pnpbios: Found PnP BIOS data at 0xc00fbf00 pnpbios: Entry = f0000:bf30 Rev = 1.0 Other BIOS signatures found: ACPI: 000f7ad0 Preloaded elf kernel "kernel" at 0xc0337000. Preloaded elf module "if_xl.ko" at 0xc03370a8. Preloaded elf module "miibus.ko" at 0xc0337148. Preloaded elf module "usb.ko" at 0xc03371e8. Preloaded elf module "ums.ko" at 0xc0337284. Preloaded elf module "bktr_mem.ko" at 0xc0337320. Preloaded elf module "bktr.ko" at 0xc03373c0. Preloaded elf module "agp.ko" at 0xc033745c. bktr_mem: memory holder loaded Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x80003840 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=03051106) pcib-: pcib0 exists, using next available unit number apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=03051106) pcib0: on motherboard found-> vendor=0x1106, dev=0x0305, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base d8000000, size 26 found-> vendor=0x1106, dev=0x8305, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1106, dev=0x0686, revid=0x22 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x0571, revid=0x10 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000d000, size 4 found-> vendor=0x1106, dev=0x3038, revid=0x10 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=10 map[20]: type 1, range 32, base 0000d400, size 5 found-> vendor=0x1106, dev=0x3038, revid=0x10 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=10 map[20]: type 1, range 32, base 0000d800, size 5 found-> vendor=0x1106, dev=0x3057, revid=0x30 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x109e, dev=0x036e, revid=0x02 class=04-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base df002000, size 12 found-> vendor=0x109e, dev=0x0878, revid=0x02 class=04-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base df000000, size 12 found-> vendor=0x9004, dev=0x7178, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 0000dc00, size 8 map[14]: type 1, range 32, base df001000, size 12 found-> vendor=0x10b7, dev=0x9200, revid=0x78 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 0000e000, size 7 map[14]: type 1, range 32, base df003000, size 7 found-> vendor=0x1011, dev=0x0009, revid=0x22 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base 0000e400, size 7 map[14]: type 1, range 32, base df004000, size 7 found-> vendor=0x1274, dev=0x5880, revid=0x02 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base 0000e800, size 6 pci0: on pcib0 agp0: mem 0xd8000000-0xdbffffff at device 0.0 on pci0 agp0: allocating GATT for aperture of size 256M pcib2: at device 1.0 on pci0 found-> vendor=0x10de, dev=0x0110, revid=0xa1 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base dc000000, size 24 map[14]: type 1, range 32, base d0000000, size 27 pci1: on pcib2 pci1: (vendor=0x10de, dev=0x0110) at 0.0 irq 5 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=14 b=eb ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=09 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd008 ata1: mask=03 status0=50 status1=50 ata1: mask=03 ostat0=50 ostat2=50 ata1-master: ATAPI probe a=00 b=00 ata1-slave: ATAPI probe a=00 b=00 ata1: mask=03 status0=50 status1=50 ata1-master: ATA probe a=01 b=a5 ata1-slave: ATA probe a=01 b=a5 ata1: devices=03 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB Mouse, rev 1.10/6.10, addr 2, iclass 3/1 ums0: 4 buttons and Z dir. uhci1: port 0xd800-0xd81f irq 10 at device 7.3 on pci0 using shared irq10. usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered bktr0: mem 0xdf002000-0xdf002fff irq 10 at device 8.0 on pci0 brooktree0: PCI bus latency is 32. bktr0: buffer size 3555328, addr 0x5000000 bktr0: GPIO is 0x00fffffb bktr0: subsystem 0x0070 0x13eb bktr0: Hauppauge Model 61291 D110 bktr0: Hauppauge WinCast/TV, Philips NTSC tuner, remote control. pci0: (vendor=0x109e, dev=0x0878) at 8.1 irq 10 ahc0: port 0xdc00-0xdcff mem 0xdf001000-0xdf001fff irq 11 at device 9.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: Downloading Sequencer Program... 429 instructions downloaded aic7870: Wide Channel A, SCSI Id=7, 16/255 SCBs xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe000-0xe07f mem 0xdf003000-0xdf00307f irq 10 at device 11.0 on pci0 xl0: Ethernet address: 00:01:02:3e:18:41 xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: xl0 attached de0: port 0xe400-0xe47f mem 0xdf004000-0xdf00407f irq 12 at device 13.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 bpf: de0 attached pcm0: port 0xe800-0xe83f irq 12 at device 15.0 on pci0 pcm0: ac97 codec id 0x83847609 (SigmaTel STAC9721) pcm0: ac97 codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, SigmaTel 3D Enhancement pcm0: ac97 primary codec extended features AMAP using shared irq12. pcm: setmap 7ded000, 1000; 0xc0bd9000 -> 7ded000 pcm: setmap 7e12000, 1000; 0xc0bde000 -> 7e12000 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=03051106) pci-: pci1 exists, using next available unit number pcib1: on motherboard pci2: on pcib1 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 54 80 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 54 80 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 54 80 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices BIOS Geometries: 0:03ff0f3f 0..1023=1024 cylinders, 0..15=16 heads, 1..63=63 sectors 1:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 2:03ff0f3f 0..1023=1024 cylinders, 0..15=16 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging disabled ata0-master: success setting UDMA2 on VIA chip Creating DISK ad0 Creating DISK wd0 ad0: ATA-4 disk at ata0-master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad0: 8063MB [16383/16/63] at ata0-master UDMA33 ata1-master: success setting UDMA4 on VIA chip Creating DISK ad1 Creating DISK wd1 ad1: ATA-5 disk at ata1-master ad1: 13029MB (26684784 sectors), 26473 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA66 ad1: piomode=4 dmamode=2 udmamode=4 cblid=1 ad1: 13029MB [26473/16/63] at ata1-master UDMA66 ata1-slave: success setting UDMA4 on VIA chip Creating DISK ad2 Creating DISK wd2 ad2: ATA-6 disk at ata1-slave ad2: 14655MB (30015216 sectors), 29777 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA66 ad2: piomode=4 dmamode=2 udmamode=5 cblid=1 ad2: 14655MB [29777/16/63] at ata1-slave UDMA66 ata0-slave: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata0-slave: success setting UDMA2 on VIA chip acd0: DVD-ROM drive at ata0 as slave acd0: read 5512KB/s (5512KB/s), 256KB buffer, UDMA33 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 10 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. de0: enabling 10baseT port Mounting root from ufs:/dev/ad1s1a ad1s1: type 0xa5, start 63, end = 26683964, size 26683902 : OK start_init: trying /sbin/init ad2s1: type 0xa5, start 63, end = 30015215, size 30015153 : OK Linux-ELF exec handler installed splash: image decoder found: blank_saver Here is my custom kernel config file. machine i386 cpu I686_CPU ident "MYKERNEL" maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? # Advanced Power Management # Serial (COM) ports device sio # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter options IPFIREWALL options IPDIVERT options SC_DISABLE_REBOOT device pcm device ahc device scbus device da device cd options SCSI_DELAY=10000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 2 6:47:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 284E137B400 for ; Sat, 2 Dec 2000 06:47:18 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eB2ElF487377; Sat, 2 Dec 2000 07:47:15 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012021447.eB2ElF487377@aslan.scsiguy.com> To: Kenneth Wayne Culver Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panics in 4.2 In-Reply-To: Your message of "Fri, 01 Dec 2000 17:26:49 EST." Date: Sat, 02 Dec 2000 07:47:15 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I sent this message to -questions,-current, and -stable earlier, but >nobody seems to know about my problem: > >I just recently tried putting an adaptec 2940w SCSI controller into my >FreeBSD machine (running -STABLE cvsupped and recompiled every night at >1:30AM) and since including the driver in my kernel I've noticed some >random panics. It may be code displacement that has caused some uninilialized data to be hit. The SCSI driver will never be touched after the initial bus scan, so it is hard to believe that this is directly caused by the SCSI subsystem. You really need to capture the panic message in order for this to be debugged. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 2 8:51:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id D85EB37B400 for ; Sat, 2 Dec 2000 08:51:41 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA28181; Sat, 2 Dec 2000 11:51:38 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id LAA03782; Sat, 2 Dec 2000 11:51:38 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA03778; Sat, 2 Dec 2000 11:51:37 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Sat, 2 Dec 2000 11:51:37 -0500 (EST) From: Kenneth Wayne Culver To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panics in 4.2 In-Reply-To: <200012021447.eB2ElF487377@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >I sent this message to -questions,-current, and -stable earlier, but > >nobody seems to know about my problem: > > > >I just recently tried putting an adaptec 2940w SCSI controller into my > >FreeBSD machine (running -STABLE cvsupped and recompiled every night at > >1:30AM) and since including the driver in my kernel I've noticed some > >random panics. > > It may be code displacement that has caused some uninilialized data to > be hit. The SCSI driver will never be touched after the initial bus > scan, so it is hard to believe that this is directly caused by the > SCSI subsystem. You really need to capture the panic message in order > for this to be debugged. > Well, it's caused somehow by the SCSI system... I took out the driver, and I havn't had a panic since... I'll put it back, however, and try to make it crash sometime today or tomorrow. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 2 15:31: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-34.dsl.snfc21.pacbell.net [63.202.178.34]) by hub.freebsd.org (Postfix) with ESMTP id 4E30D37B400 for ; Sat, 2 Dec 2000 15:31:06 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB2NdWF21371; Sat, 2 Dec 2000 15:39:32 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012022339.eB2NdWF21371@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Gradwell Cc: freebsd-scsi@freebsd.org, hirez@bratcave.org, cliff@onsea.com Subject: Re: Mylex DAC960 Driver "online/offline" In-reply-to: Your message of "Fri, 01 Dec 2000 21:32:54 GMT." <5.0.0.25.0.20001201212649.03798548@pop3.gradwell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Dec 2000 15:39:31 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Hi, > > I have a Mylex acceleraid 250 card in a FreeBSD 4.1 machine and > when it boots it tells me that: > > ====== > DAC960 BIOS Version 4.10-41 (Feb 02, 1999) > Mylex Corporation > > DAC960PTL1 Firmware Version 4.07-0-29 > DAC960 PCI Address: F4102000 Bus=0 Dev/Slot=13 Function=1 IRQ=11 > DAC960 Memory = 8 MB (EDO/ECC) > WARNING: 1 system drive offline > WARNING: Dead SCSI device (Channel:Target) : > 0:3 > Press for BIOS options > > Press for RAID Configuration options > 2 system drives installed > Press any key to continue > ====== > > - the off line disk is in a RAID 1 disk array is a RAID 1 disk array. The > kernel then boots from this RAID 1 disk array. If the system drive is offline, you shouldn't really actually be able to boot from it at all. Of course, a single dead disk in a mirror shouldn't cause it to be marked "offline", just "degraded". I think the Mylex firmware is very confused here. > However, when FSCKing the / partition, (/dev/mlxd0s1a) it fails, > because it thinks that mlxd0 is off line. I then get a fairly continuous > stream of messages to the console saying: > > ====== > mlxd0: drive online > mlxd0: drive offline > ====== > > I have contacted Mylex Tech Support and they say that this is a message > given out by the kernel, and more properly, the FreeBSD driver in the kernel. That's correct. The controller is, however, I think to blame here; it can't make up its mind whether the drive is offline or not, and it keeps telling the driver conflicting things. > Does anyone know why the kernel driver is reporting this. It doesn't seem > sensible that the controller should be marking a drive off line and then online > again, in a loop, ad infinitum. Mylex Tech Support agree. > > What does this message really mean? It means that the controller is telling us that the drive is offline. Then that it's online. Then that it's offline again. You don't say what the time intervals between these messages are; you can get the 'drive offline' message from either the status poll (once per second) or if an I/O operation is sent to a drive that the controller reports as offline. The 'drive online' message only comes from the status poll though. Can you describe your configuration? I can try to reproduce the situation here and see if it's not possible that there's a bug in the driver confusing the status between your two drives. I have to say, though, that the fact that the controller thinks that one of your system drives is offline when you claim it's a mirror is a bit troubling. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 2 15:49:33 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from red.gradwell.net (red.gradwell.net [195.149.39.8]) by hub.freebsd.org (Postfix) with SMTP id 00D5F37B400 for ; Sat, 2 Dec 2000 15:49:30 -0800 (PST) Received: (qmail 21294 invoked from network); 2 Dec 2000 23:49:26 -0000 Received: from ystwyth.demon.co.uk (HELO vaio.gradwell.com) (158.152.144.35) by pop3.gradwell.net with SMTP; 2 Dec 2000 23:49:26 -0000 Message-Id: <5.0.0.25.0.20001202233356.0366b2d8@pop3.gradwell.net> X-Sender: postmaster%pop3.peterg.org.uk@pop3.gradwell.net X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 02 Dec 2000 23:49:24 +0000 To: Mike Smith From: Peter Gradwell Subject: Re: Mylex DAC960 Driver "online/offline" Cc: freebsd-scsi@freebsd.org In-Reply-To: <200012022339.eB2NdWF21371@mass.osd.bsdi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Mike, At 15:39 02/12/2000 -0800, Mike Smith wrote: > > What does this message really mean? > >It means that the controller is telling us that the drive is offline. >Then that it's online. Then that it's offline again. > >You don't say what the time intervals between these messages are; you can >get the 'drive offline' message from either the status poll (once per >second) or if an I/O operation is sent to a drive that the controller >reports as offline. The 'drive online' message only comes from the >status poll though. It was occuring without any apparent activity, about once per second, so I would guess it was from the status poll. >Can you describe your configuration? I can try to reproduce the >situation here and see if it's not possible that there's a bug in the >driver confusing the status between your two drives. I have to say, >though, that the fact that the controller thinks that one of your system >drives is offline when you claim it's a mirror is a bit troubling. Ok, on an update to the situation though, I was able to get too the mylex bios (there is 250 miles between me and the machine you see!) via a serial console and discovered that it had marked two drives offline. We have: 3 x 18 gig disks, of which two are bonded in a raid 1 pack and one is a hot spare 2 x 36 gig disks, bonded in a raid 0 pack. Everything apart from /var/spool/news is on the raid 1 pack. (Yeah, it's a news server.) One of the 18 gig disks and one of the 36 gig disks were marked offline. I belive that when the 18 gig disk was marked off line the RAID card rebuilt it's redundancy data onto the hot spare disk and carried on. - cos the 18 gig which is off line was part of the raid 1 pack and there is now not hot spare. *So, that's good.* So, we hard reset the machine and it booted. However, the symptoms described previously prevailed. We couldn't login via ssh or on the console as it was unresponsive. * This worries me. I would hope the machine would take the loss of /v/s/news gracefully, and carry on. So, when I accessed the bios this morning, I tried, as an "experiment" to put the 36 gig disk back online and rebooted. After running fsck a bit (is there a journaling file system for freebsd?!) the machine is now running ok. I have yet to schedule a reboot to mark the currently off line 18 gig disk as the hot spare. I think I will be able to do this. I am worried that the controller randomly marks the drives off line. Mylex tell me this happens when it looses contact with the drives. They are internal drives, well screwed into a big case, nicely racked into a locked cabinet in Telehouse Europe. From what I can gather, no one accessed the rack. It appears they aren't disconnected anyway because I can mark them online and we're go again. I'd be happy to help with more information if it helps. Directed questions work best! thanks peter -- peter gradwell; online @ http://www.gradwell.com/peter/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 2 20:20:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-34.dsl.snfc21.pacbell.net [63.202.178.34]) by hub.freebsd.org (Postfix) with ESMTP id 7D15037B400 for ; Sat, 2 Dec 2000 20:20:49 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB34TMF33893; Sat, 2 Dec 2000 20:29:22 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012030429.eB34TMF33893@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Gradwell Cc: freebsd-scsi@freebsd.org Subject: Re: Mylex DAC960 Driver "online/offline" In-reply-to: Your message of "Sat, 02 Dec 2000 23:49:24 GMT." <5.0.0.25.0.20001202233356.0366b2d8@pop3.gradwell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Dec 2000 20:29:22 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi Mike, > > At 15:39 02/12/2000 -0800, Mike Smith wrote: > > > What does this message really mean? > > > >It means that the controller is telling us that the drive is offline. > >Then that it's online. Then that it's offline again. > > > >You don't say what the time intervals between these messages are; you can > >get the 'drive offline' message from either the status poll (once per > >second) or if an I/O operation is sent to a drive that the controller > >reports as offline. The 'drive online' message only comes from the > >status poll though. > > It was occuring without any apparent activity, about once per second, > so I would guess it was from the status poll. Did you get one message each second, or two? (two would be more confusing) > >Can you describe your configuration? I can try to reproduce the > >situation here and see if it's not possible that there's a bug in the > >driver confusing the status between your two drives. I have to say, > >though, that the fact that the controller thinks that one of your system > >drives is offline when you claim it's a mirror is a bit troubling. > > Ok, on an update to the situation though, I was able to get too the > mylex bios (there is 250 miles between me and the machine you see!) > via a serial console and discovered that it had marked two drives offline. > > We have: > 3 x 18 gig disks, of which two are bonded in a raid 1 pack > and one is a hot spare > 2 x 36 gig disks, bonded in a raid 0 pack. > > Everything apart from /var/spool/news is on the raid 1 pack. (Yeah, it's > a news server.) > > One of the 18 gig disks and one of the 36 gig disks were marked offline. > > I belive that when the 18 gig disk was marked off line the RAID card > rebuilt it's redundancy data onto the hot spare disk and carried on. > - cos the 18 gig which is off line was part of the raid 1 pack and there > is now not hot spare. *So, that's good.* That sounds about right. The failure rate is terrible though. Heat issues? > So, we hard reset the machine and it booted. However, the symptoms > described previously prevailed. We couldn't login via ssh or on the console > as it was unresponsive. > > * This worries me. I would hope the machine would take the loss of > /v/s/news gracefully, and carry on. If a filesystem listed in /etc/fstab can't be mounted, the system won't boot. If you want resiliency against filesystems that won't mount, don't list them there; mount them manually as part of eg. the news subsystem startup instead. > So, when I accessed the bios this morning, I tried, as an "experiment" > to put the 36 gig disk back online and rebooted. After running fsck > a bit (is there a journaling file system for freebsd?!) the machine is > now running ok. You can use snapshots with softupdates, but that's still a work in progress, so I wouldn't count on it yet. > I have yet to schedule a reboot to mark the currently off line 18 gig > disk as the hot spare. I think I will be able to do this. > > I am worried that the controller randomly marks the drives off line. Mylex > tell me this happens when it looses contact with the drives. > They are internal drives, well screwed into a big case, nicely racked > into a locked cabinet in Telehouse Europe. From what I can gather, no > one accessed the rack. It appears they aren't disconnected anyway > because I can mark them online and we're go again. "loses contact" doesn't necessarily mean that they're disconnected; it can be caused by the drive failing to behave (eg. SCSI error -> drive reset -> repeated SCSI error(s)). If this is the case, you should have a lot more log messages from the controller. > I'd be happy to help with more information if it helps. Directed questions > work best! I'd start by checking your system logs for more verbosity from the controller. At the very least, there should be some indication that the drives died, and reporting on the rebuild that seems to have occurred. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 2 22:21:22 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from temphost.dragondata.com (temphost.dragondata.com [63.167.131.128]) by hub.freebsd.org (Postfix) with ESMTP id 52A3A37B400 for ; Sat, 2 Dec 2000 22:21:20 -0800 (PST) Received: (from toasty@localhost) by temphost.dragondata.com (8.9.3/8.9.3) id AAA04803; Sun, 3 Dec 2000 00:25:47 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200012030625.AAA04803@temphost.dragondata.com> Subject: Re: sym driver in 4.1.1+ on Proliant To: cdillon@wolves.k12.mo.us (Chris Dillon) Date: Sun, 3 Dec 2000 00:25:47 -0600 (CST) Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: from "Chris Dillon" at Nov 30, 2000 11:28:36 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Wed, 29 Nov 2000, Kevin Day wrote: > > > I've got several Compaq Proliant ML530's with the internal '896 > > SCSI controller. Everything works great on 4.1-RELEASE. Going to > > 4.1.1 or 4.2 causes sym0 to say "Cannot allocate IRQ resource", > > followed by a kernel trap inside the sym driver. Has anyone > > experienced this, or know what I can try? > > I had this problem long before 4.1.1, several months ago, but I'm not > exactly sure what caused it. I assume that your on-board SCSI > controller is trying to use IRQ15. Go into the Compaq System Setup > and make sure no devices are using IRQ15 except for possibly the > on-board IDE controller (which is what is _supposed_ to be using it). > That solved it for me. I've got a PR open on this, but I haven't yet > had time to figure out exactly what caused it since it is on a > production system. It might be a BIOS problem, but it definately > works with some previous kernels and not with newer ones. The servers are about 1000 miles from me, and dispatching a tech costs about $100/hr... Anything I can do to avoid having someone there go play in the setup, I"ll do. :) interrupt total rate ata0 irq14 4 0 sym0 irq10 100198 113 sym1 irq11 47 0 fxp0 irq5 418750 475 fdc0 irq6 2 0 atkbd0 irq1 2 0 clk irq0 87859 99 rtc irq8 112457 127 Total 719319 817 Everything seems happy on its own IRQ... I just don't get it. :) -- Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message