From owner-freebsd-scsi Sun Dec 13 17:13:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06675 for freebsd-scsi-outgoing; Sun, 13 Dec 1998 17:13:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06670 for ; Sun, 13 Dec 1998 17:13:55 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA18517; Mon, 14 Dec 1998 11:41:44 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981212120158.09620@uriah.heep.sax.de> Date: Mon, 14 Dec 1998 11:41:35 +1030 (CST) From: "Daniel O'Connor" To: J Wunsch Subject: Re: cdrecord and caching issue Cc: larry@marso.com, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12-Dec-98 J Wunsch wrote: > Just as an additional datapoint: reloading the medium is the only > documented way to get rid of the cached TOC for my old Plasmon burner. And cdrecord often reloads the media (ahh, the joys of a tray CD-R :) to get the correct information about the drive. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 13 17:54:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11475 for freebsd-scsi-outgoing; Sun, 13 Dec 1998 17:54:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11427 for ; Sun, 13 Dec 1998 17:54:13 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id UAA07735 for freebsd-scsi@freebsd.org; Sun, 13 Dec 1998 20:49:35 -0500 (EST) (envelope-from larry) Date: Sun, 13 Dec 1998 20:48:58 -0500 From: "Larry S. Marso" To: "Daniel O'Connor" Subject: Re: cdrecord and caching issue Message-ID: <19981213204857.A7656@marso.com> References: <19981212120158.09620@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i In-Reply-To: ; from Daniel O'Connor on Mon, Dec 14, 1998 at 11:41:35AM +1030 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org With my yamaha cdr 4x2x6 it is possible also to power down and power back up and achieve the same result. Best regards -- Larry S. Marso larry@marso.com On Mon, Dec 14, 1998 at 11:41:35AM +1030, Daniel O'Connor wrote: > > On 12-Dec-98 J Wunsch wrote: > > Just as an additional datapoint: reloading the medium is the only > > documented way to get rid of the cached TOC for my old Plasmon burner. > And cdrecord often reloads the media (ahh, the joys of a tray CD-R :) to get the correct > information about the drive. > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 13 18:35:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15179 for freebsd-scsi-outgoing; Sun, 13 Dec 1998 18:35:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15174 for ; Sun, 13 Dec 1998 18:35:12 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id SAA02550; Sun, 13 Dec 1998 18:35:09 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id SAA13289; Sun, 13 Dec 1998 18:35:09 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id SAA20727; Sun, 13 Dec 1998 18:35:08 -0800 (PST) Date: Sun, 13 Dec 1998 18:35:08 -0800 (PST) From: Tom Wadlow To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: <199812121704.KAA05364@pluto.plutotech.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 Just FYI, I've loaded the 3.0-19981211-SNAP and thus far (a bit more than a day), things seem to be stable. The RELEASE version wouldn't stay up for more than a few hours. This one hasn't crashed yet, but time will tell.... --Tom On Sat, 12 Dec 1998, Justin T. Gibbs wrote: > Date: Sat, 12 Dec 1998 09:57:14 -0700 > From: Justin T. Gibbs > To: Tom Wadlow > Cc: Justin T. Gibbs , scsi@FreeBSD.org > Subject: Re: A problem with SCSI > > >I've built out several systems from 3.0-RELEASE that all seeem to manifest thi > >s problem. > >Two die on a regular basis. The third gets strange messsages but seems to sta > >y up. > > > >Machines dying with "Invalidating pack" > > A) Pentium 100MHz > > 64MB RAM > > BusLogic 496 SCSI controller > > 4GB Connor SCSI (only device on the SCSI chain) > > Ethernet > > Floppy > > This is most likely a bad interaction between your buslogic 946 and the > Connor drives. Can you mail me the dmesg output from your machine just > after boot? > > There have been several bug fixes to the Buslogic driver since 3.0R. Your > problem may be solved by running a more recent SNAPSHOT or using CVSup > to pull -current. > > -- > Justin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 13 22:21:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04649 for freebsd-scsi-outgoing; Sun, 13 Dec 1998 22:21:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04638 for ; Sun, 13 Dec 1998 22:21:51 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id HAA21365; Mon, 14 Dec 1998 07:21:41 +0100 (MET) Received: from cicely.cicely.de (cicely.cicely.de [10.1.3.3]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id HAA14089; Mon, 14 Dec 1998 07:21:43 +0100 (CET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.5.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id HAA08361; Mon, 14 Dec 1998 07:21:41 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id HAA01313; Mon, 14 Dec 1998 07:21:36 +0100 (CET) Message-ID: <19981214072135.00864@cicely.de> Date: Mon, 14 Dec 1998 07:21:35 +0100 From: Bernd Walter To: "Kenneth D. Merry" , "Larry S. Marso" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cd write failure References: <19981211115604.C21942@marso.com> <199812111957.MAA17481@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199812111957.MAA17481@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Dec 11, 1998 at 12:57:29PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 11, 1998 at 12:57:29PM -0700, Kenneth D. Merry wrote: > Larry S. Marso wrote... > > I get the following cd write failures writing at speeds above 1x on a > > Yamaha 4260 with max 4x write speed: > > > > After such an error, the cdr is ruined. > > > > This outcome does *not* occur immediately after rebooting the system. But Sounds like a thermical problem to me. Most writers need a minimal air-flow, which is usualy not garantied in typical computercases. > > after writing just one time, it begins (and seems to get worse). > > Eventually, even 1x has created this error. > > > > I'm using CAM 3.0-R aout. > > Well, here's your problem: > > > Device seems to be: Generic mmc CD-RW. > > Using generic SCSI-3/mmc CD-R driver (mmc_cdr). > > Driver flags : SWABAUDIO > > cdrecord: Undefined error: 0. WARNING: RR-scheduler not available, > > disabling. > > Starting to write CD/DVD at speed 4 in write mode for multi session. > > Last chance to quit, starting real write in 1 seconds. > > cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error > > CDB: 2A 00 00 00 00 00 00 00 1F 00 > > status: 0x2 (CHECK CONDITION) > > Sense Bytes: 70 00 04 D1 D9 00 00 0A 00 00 00 00 09 01 00 00 00 00 00 00 00 > > 08 00 00 00 00 00 00 08 00 01 06 > > Sense Key: 0x4 Hardware Error, Segment 0 > > Sense Code: 0x09 Qual 0x01 (tracking servo failure) Fru 0x0 > > Sense flags: Blk -774307840 (not valid) > > resid: 63488 > > cmd finished after 14.068s timeout 40s > > write track data: error after 0 bytes > > You got a hardware error. Specifically, it's a "Tracking servo failure". > > This is probably not a CAM problem, but most likely a problem with your > drive. I suggest that you: > > 1. Contact Joerg Schilling , the author of > cdrecord. He may know of specific issues with that drive that would > cause it to spit out the above error. > > 2. Contact Yamaha tech support, and see what they say about it. > > Ken > -- > Kenneth Merry > ken@plutotech.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 14 07:29:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02938 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 07:29:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02920; Mon, 14 Dec 1998 07:29:12 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id KAA25933; Mon, 14 Dec 1998 10:29:08 -0500 (EST) Date: Mon, 14 Dec 1998 10:29:08 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@FreeBSD.ORG cc: freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable 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 Hi, FWIW, I got the same message today, but the machine didn't lock up. Any ideas? Anyone? I'm cc-ing stable this time in hopes of finding someone running cam under -stable... Here's the messages: Dec 12 03:44:18 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 31 Dec 13 02:01:04 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 2 Dec 14 02:01:21 shell /kernel: (da0:ahc0:0:0:0): tagged openings now 30 Dec 14 10:07:42 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 14 10:07:45 shell /kernel: SEQADDR == 0x8 Dec 14 10:07:45 shell /kernel: SSTAT1 == 0xa Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b Dec 14 10:07:45 shell /kernel: ahc0: Bus Device Reset Sent. 1 SCBs aborted Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." On Fri, 11 Dec 1998, spork wrote: > Hi, > > I'm about to put two new machines in production, and they're both "core" > machines; main dns/auth/mail and a shell machine. Currently the machines > we use in this capacity are 2.1.7.1, and it's been very stable. > > Now the new machines share a RAID array hung off of a CMD CRD-5440. I > patched our usual build (980825 -stable) with the July CAM patchkit, as > the existing AHC driver couldn't detect any LUNs beyond the first one. > > All has been well so far, I've tried to stress the machines as much as > possible by running some disk benchmarks over and over, but yesterday one > locked up (console frozen) with the following messages being the last > thing on the console: > > Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa > Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b > Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted > > I had to give it a hard reset at this point. > > So my questions are: Is this a known issue? Does it point to a possible > hardware problem? Will there be a newer cam patchkit for -stable? > > I don't think it's a cabling issue, as this is the first I've seen of any > anomolies with the scsi subsystem, and the only cabling in question here > is a high quality 2' external UW scsi cable from the back of this machine > to the RAID array. The other machine that uses the other host port on the > RAID array remained functional during this glitch... > > Any ideas? I was very comfortable with CAM before, but now I'm a little > nervous about moving this into production. Would it be better to try and > back out of the patches and use the ahc driver? Let me know if there's > any other info needed. > > Following are the boot messages... > > Thanks, > > Charles > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. > Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. > Dec 10 19:27:32 shell /kernel: > Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 > Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL > Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) > Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 > Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> > Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) > Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: > Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 > Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 > Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 > Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 > Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 > Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 > Dec 10 19:27:32 shell /kernel: fxp0 Dec 10 19:27:32 shell /kernel: ro 10/100B Ethernet> rev 5 int a irq 10 on pci0:7:0 > Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d > Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 > Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 > Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d > Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: > Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: > Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > Dec 10 19:27:32 shell /kernel: sio0: type 16550A > Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > Dec 10 19:27:32 shell /kernel: sio1: type 16550A > Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port > Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface > Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold > Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in > Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard > Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface > Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry > Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device > Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) > Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 > Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device > Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) > Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. > Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding > Dec 10 19:27:32 shell savecore: no core dump > > --- > Charles Sprickman > spork@super-g.com > --- > "...there's no idea that's so good you can't > ruin it with a few well-placed idiots." > > > 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 Mon Dec 14 08:39:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09662 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 08:39:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09655 for ; Mon, 14 Dec 1998 08:39:52 -0800 (PST) (envelope-from richard@jezebel.demon.co.uk) Received: from jezebel.demon.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id QAA17834 for ; Mon, 14 Dec 1998 16:39:49 GMT (envelope-from richard@jezebel.demon.co.uk) Message-ID: <36753F8E.D2A105FE@jezebel.demon.co.uk> Date: Mon, 14 Dec 1998 16:40:46 +0000 From: Richard Smith Organization: http://www.trltech.co.uk X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Update: ncr0: timeout problem Content-Type: multipart/mixed; boundary="------------DB215F9E1F9AF6CD294F2EFB" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------DB215F9E1F9AF6CD294F2EFB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Over a month ago, I posted a timeout problem I was having with my symbios controller and fujitsu drive, on 2.2.7R I have now upgraded to 3.0R and the problem although different, still remains. I was advised at the time that the problem would be easier to diagnose under 3.0, so here goes... I can force the problem by performing a "tar -cf /dev/null /usr". After a short while disk activity stops. Then after a further 70s-80s the following messages appear: ncr0: timeout nccb=0xf09a4400 ncr0: timeout nccb=0xf09a4800 ncr0: timeout nccb=0xf09a4c00 ncr0: timeout nccb=0xf09a3000 ncr0: timeout nccb=0xf09a3400 ncr0: timeout nccb=0xf09a3800 A couple more appear later, then the whole lot repeats every 60s-70s. The last time I tried this, it took four attempts before it would pass fschk without hanging again. On the second attempt the following messages were generated: ncr0:0 ERROR (0:5) (8-0-0) (f/9d) @ (script 7ec:190003fa). ncr0: script cmd = 89030000 ncr0: regdump: da 00 80 9d 47 0f 00 0f 03 08 80 00 80 00 01 02. ncr0: have to clear fifos. ncr0: restert (fatal error). (da0:ncr0:0:0:0): COMMAND FAILED (9 ff) @0xf0857400 Dmesg.boot is attached in case it may be of use. ncr0 is a symbios logic v4.0 pci scsi bios pci rev 2.0,2.1 pci-4.11.00 53c875 fast20 wide scsi, and da0 is a fujitsu M2949E-512 HDD (about 8.5 Gbytes). The disk is divided into almost two equal slices, with FBSD in the top 4G. I understand that in future I should use Adaptec scsi cards and Seagate or IBM disks. Meanwhile, however, any help with which bit needs fixing or throwing away would be much appreciated. Thanks, _______________________________________________________________________ Richard Smith Assistant Chief Engineer TRL Technology Limited --------------DB215F9E1F9AF6CD294F2EFB Content-Type: text/plain; charset=us-ascii; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #0: Sat Oct 17 17:45:06 GMT 1998 jkh@kickme.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz cost 2808 ns Timecounter "TSC" frequency 119752905 Hz cost 189 ns CPU: Pentium/P54C (119.75-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62484480 (61020K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x02 on pci0.7.1 ed1: rev 0x00 int a irq 9 on pci0.13.0 ed1: address 00:00:b4:55:0e:b3, type NE2000 (16 bit) vga0: rev 0x08 on pci0.14.0 ncr0: rev 0x03 int a irq 11 on pci0.15.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, intr, iordis wcd0: 689Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked wdc1 not found at 0x170 wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround Waiting 15 seconds for SCSI devices to settle changing root device to da0s3a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8682MB (17781964 512 byte sectors: 255H 63S/T 1106C) --------------DB215F9E1F9AF6CD294F2EFB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 14 08:57:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11717 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 08:57:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11698; Mon, 14 Dec 1998 08:57:44 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id JAA54340; Mon, 14 Dec 1998 09:57:27 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812141657.JAA54340@panzer.plutotech.com> Subject: Re: CAM and -stable In-Reply-To: from spork at "Dec 14, 98 10:29:08 am" To: spork@super-g.com (spork) Date: Mon, 14 Dec 1998 09:57:27 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 spork wrote... [ sorry for not responding to your previous message. I thought Justin would respond, but evidently he never got around to it. ] > FWIW, I got the same message today, but the machine didn't lock up. Any > ideas? Anyone? I'm cc-ing stable this time in hopes of finding someone > running cam under -stable... > > Here's the messages: > > Dec 12 03:44:18 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 31 > Dec 13 02:01:04 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 2 > Dec 14 02:01:21 shell /kernel: (da0:ahc0:0:0:0): tagged openings now 30 > Dec 14 10:07:42 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out > while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Dec 14 10:07:45 shell /kernel: SEQADDR == 0x8 > Dec 14 10:07:45 shell /kernel: SSTAT1 == 0xa > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message > Sent > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, > status = 34b > Dec 14 10:07:45 shell /kernel: ahc0: Bus Device Reset Sent. 1 SCBs aborted The 'timed out while idle' messages basically mean that a command timed out while we were waiting for it to complete, and there was nothing else going on at the time. I think it generally takes around 10 seconds for that to happen. (It may actually be 60 now...) Generally, it's a sign that the device has gone "out to lunch", and we have to whap it over the head with a BDR to get it to wake up. Another example of a device with that sort of problem is the Quantum Atlas II. (especially firmware revisions earlier than LYK8) Earlier firmware revisions of that drive will go "out to lunch" when there is a lot of bus traffic, You also have another problem, which wasn't evident in your earlier mail. The tagged openings on one of your RAID partitions have gone down to 2. This is a prime example of why it's a good idea to print out the number of tagged openings by default. (Take note all you whiners out there who've been complaining about it.) That indicates that the device keeps sending queue full until we reduce the number of tagged openings to the lowest possible value (2). I would suggest looking in the CMD docs, and try to figure out if they say how many simultaneous transactions the device can handle. Take that number, divide it by 2 (you've got two partitions on the device), and make that the maximum number of tags in a quirk entry in the transport layer. Make the minimum number of tags something slightly less than that. If they don't say how many tags the thing can handle, a good measurement is something in the neighborhood of the first 'reduced tags' number you get. I'm not sure whether the above messages are all of the tagged openings messages, but if they are, you might assume that the thing can handle around 32 tags total. Divided by 2, that's 16. So you could try setting the maximum for each lun to 16, and the minimum to 10 or so. Generally, the system will recover all right from the 'timed out while idle' problem. After we hit the device with a BDR, all the CCBs that have already been sent to the device are aborted, and we requeue them all. > On Fri, 11 Dec 1998, spork wrote: > > > Hi, > > > > I'm about to put two new machines in production, and they're both "core" > > machines; main dns/auth/mail and a shell machine. Currently the machines > > we use in this capacity are 2.1.7.1, and it's been very stable. > > > > Now the new machines share a RAID array hung off of a CMD CRD-5440. I > > patched our usual build (980825 -stable) with the July CAM patchkit, as > > the existing AHC driver couldn't detect any LUNs beyond the first one. > > > > All has been well so far, I've tried to stress the machines as much as > > possible by running some disk benchmarks over and over, but yesterday one > > locked up (console frozen) with the following messages being the last > > thing on the console: > > > > Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > > Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa > > Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted > > > > I had to give it a hard reset at this point. > > > > So my questions are: Is this a known issue? Does it point to a possible > > hardware problem? Will there be a newer cam patchkit for -stable? > > > > I don't think it's a cabling issue, as this is the first I've seen of any > > anomolies with the scsi subsystem, and the only cabling in question here > > is a high quality 2' external UW scsi cable from the back of this machine > > to the RAID array. The other machine that uses the other host port on the > > RAID array remained functional during this glitch... > > > > Any ideas? I was very comfortable with CAM before, but now I'm a little > > nervous about moving this into production. Would it be better to try and > > back out of the patches and use the ahc driver? Let me know if there's > > any other info needed. > > > > Following are the boot messages... > > > > Thanks, > > > > Charles > > > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > > Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. > > Dec 10 19:27:32 shell /kernel: > > Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 > > Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL > > Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) > > Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 > > Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> > > Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) > > Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: > > Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 > > Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 > > Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 > > Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 > > Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 > > Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 > > Dec 10 19:27:32 shell /kernel: fxp0 > Dec 10 19:27:32 shell /kernel: ro 10/100B Ethernet> rev 5 int a irq 10 on pci0:7:0 > > Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d > > Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 > > Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 > > Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d > > Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: > > Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: > > Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > > Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > > Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > > Dec 10 19:27:32 shell /kernel: sio0: type 16550A > > Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > > Dec 10 19:27:32 shell /kernel: sio1: type 16550A > > Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > > Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port > > Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface > > Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold > > Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in > > Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard > > Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface > > Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry > > Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 > > Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device > > Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) > > Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 > > Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device > > Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) > > Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. > > Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding > > Dec 10 19:27:32 shell savecore: no core dump > > > > --- > > Charles Sprickman > > spork@super-g.com > > --- > > "...there's no idea that's so good you can't > > ruin it with a few well-placed idiots." > > > > > > 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 > Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 14 09:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16644 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 09:43:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16625; Mon, 14 Dec 1998 09:43:51 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id MAA10160; Mon, 14 Dec 1998 12:43:11 -0500 (EST) Date: Mon, 14 Dec 1998 12:43:11 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: <199812141657.JAA54340@panzer.plutotech.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 Mon, 14 Dec 1998, Kenneth D. Merry wrote: > spork wrote... > > [ sorry for not responding to your previous message. I thought Justin > would respond, but evidently he never got around to it. ] No problem, I was a little nervous, that's all... > Generally, it's a sign that the device has gone "out to lunch", and we have > to whap it over the head with a BDR to get it to wake up. Are you aware of anyone else running a CMD controller? I know wcarchive is using the Mylex box. I hope I've made a good choice... > You also have another problem, which wasn't evident in your earlier mail. > The tagged openings on one of your RAID partitions have gone down to 2. > That indicates that the device keeps sending queue full until we reduce the > number of tagged openings to the lowest possible value (2). I would > suggest looking in the CMD docs, and try to figure out if they say how many > simultaneous transactions the device can handle. Take that number, divide > it by 2 (you've got two partitions on the device), and make that the > maximum number of tags in a quirk entry in the transport layer. Make the > minimum number of tags something slightly less than that. How and where do I set the number of tags? The docs (http://www.cmd.com/storage/products/docs/datasheet/crd5440.cfm) say that the unit can queue 64 commands. There are two hosts on this controller in our installation. I'm no scsi genius, are 'tags' and 'queued commands' the same thing? > Generally, the system will recover all right from the 'timed out while > idle' problem. After we hit the device with a BDR, all the CCBs that have > already been sent to the device are aborted, and we requeue them all. Yep, it's only froze up completely once. Is your feeling that if I adjust it to use less tags this should go away? I checked the CMD website, and there is one more firmware update, but it doesn't address any serious issues. And one last thing, will there ever be a newer patchkit for CAM under stable? My timing is horrible, I need to put these machines in production in the next week or so, so I can't really go to 3.x right now... In 6 months or so, sure, but these will probably remain at 2.2 for quite some time. Are there major changes from what I'm running in the 3.x tree? Thanks very much, Charles ps- if anyone feels the crosspost to -stable and -scsi is unneeded, feel free to remove the less appropriate list... > > > On Fri, 11 Dec 1998, spork wrote: > > > > > Hi, > > > > > > I'm about to put two new machines in production, and they're both "core" > > > machines; main dns/auth/mail and a shell machine. Currently the machines > > > we use in this capacity are 2.1.7.1, and it's been very stable. > > > > > > Now the new machines share a RAID array hung off of a CMD CRD-5440. I > > > patched our usual build (980825 -stable) with the July CAM patchkit, as > > > the existing AHC driver couldn't detect any LUNs beyond the first one. > > > > > > All has been well so far, I've tried to stress the machines as much as > > > possible by running some disk benchmarks over and over, but yesterday one > > > locked up (console frozen) with the following messages being the last > > > thing on the console: > > > > > > Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > > > Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa > > > Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb > > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > > Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted > > > > > > I had to give it a hard reset at this point. > > > > > > So my questions are: Is this a known issue? Does it point to a possible > > > hardware problem? Will there be a newer cam patchkit for -stable? > > > > > > I don't think it's a cabling issue, as this is the first I've seen of any > > > anomolies with the scsi subsystem, and the only cabling in question here > > > is a high quality 2' external UW scsi cable from the back of this machine > > > to the RAID array. The other machine that uses the other host port on the > > > RAID array remained functional during this glitch... > > > > > > Any ideas? I was very comfortable with CAM before, but now I'm a little > > > nervous about moving this into production. Would it be better to try and > > > back out of the patches and use the ahc driver? Let me know if there's > > > any other info needed. > > > > > > Following are the boot messages... > > > > > > Thanks, > > > > > > Charles > > > > > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. > > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > > > Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. > > > Dec 10 19:27:32 shell /kernel: > > > Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 > > > Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL > > > Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) > > > Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 > > > Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> > > > Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) > > > Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) > > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: > > > Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 > > > Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 > > > Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 > > > Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 > > > Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 > > > Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 > > > Dec 10 19:27:32 shell /kernel: fxp0 > > Dec 10 19:27:32 shell /kernel: ro 10/100B Ethernet> rev 5 int a irq 10 on pci0:7:0 > > > Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d > > > Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 > > > Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > > Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 > > > Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d > > > Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 > > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: > > > Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: > > > Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > > > Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > > > Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > > > Dec 10 19:27:32 shell /kernel: sio0: type 16550A > > > Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > > > Dec 10 19:27:32 shell /kernel: sio1: type 16550A > > > Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > > > Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port > > > Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface > > > Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > > Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold > > > Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in > > > Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard > > > Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface > > > Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry > > > Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 > > > Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device > > > Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > > Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) > > > Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 > > > Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device > > > Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > > Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) > > > Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. > > > Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding > > > Dec 10 19:27:32 shell savecore: no core dump > > > > > > --- > > > Charles Sprickman > > > spork@super-g.com > > > --- > > > "...there's no idea that's so good you can't > > > ruin it with a few well-placed idiots." > > > > > > > > > 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 > > > > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 14 09:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17856 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 09:53:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17837; Mon, 14 Dec 1998 09:53:34 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA54713; Mon, 14 Dec 1998 10:53:10 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812141753.KAA54713@panzer.plutotech.com> Subject: Re: CAM and -stable In-Reply-To: from spork at "Dec 14, 98 12:43:11 pm" To: spork@super-g.com (spork) Date: Mon, 14 Dec 1998 10:53:10 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 spork wrote... > On Mon, 14 Dec 1998, Kenneth D. Merry wrote: > > > spork wrote... > > > > [ sorry for not responding to your previous message. I thought Justin > > would respond, but evidently he never got around to it. ] > > No problem, I was a little nervous, that's all... > > > Generally, it's a sign that the device has gone "out to lunch", and we have > > to whap it over the head with a BDR to get it to wake up. > > Are you aware of anyone else running a CMD controller? I know wcarchive > is using the Mylex box. I hope I've made a good choice... I believe Karl Denninger is using a CMD controller on one of his machines, with CAM. You'd have to ask him for details, though. > > You also have another problem, which wasn't evident in your earlier mail. > > The tagged openings on one of your RAID partitions have gone down to 2. > > That indicates that the device keeps sending queue full until we reduce the > > number of tagged openings to the lowest possible value (2). I would > > suggest looking in the CMD docs, and try to figure out if they say how many > > simultaneous transactions the device can handle. Take that number, divide > > it by 2 (you've got two partitions on the device), and make that the > > maximum number of tags in a quirk entry in the transport layer. Make the > > minimum number of tags something slightly less than that. > > How and where do I set the number of tags? The docs > (http://www.cmd.com/storage/products/docs/datasheet/crd5440.cfm) say that > the unit can queue 64 commands. There are two hosts on this controller in > our installation. I'm no scsi genius, are 'tags' and 'queued commands' > the same thing? Yes, they are. > > Generally, the system will recover all right from the 'timed out while > > idle' problem. After we hit the device with a BDR, all the CCBs that have > > already been sent to the device are aborted, and we requeue them all. > > Yep, it's only froze up completely once. Is your feeling that if I adjust > it to use less tags this should go away? I checked the CMD website, and > there is one more firmware update, but it doesn't address any serious > issues. It might very well go away. The only way to find out is to try it. Since it can supposedly handle 64 commands, you might try setting the maximum in the quirk entry to 32, to divide the load evenly. You could set the minimum to 24 or so. > And one last thing, will there ever be a newer patchkit for CAM under > stable? My timing is horrible, I need to put these machines in production > in the next week or so, so I can't really go to 3.x right now... In 6 > months or so, sure, but these will probably remain at 2.2 for quite some > time. Are there major changes from what I'm running in the 3.x tree? Yes, there will be a new -stable patchkit. At least that's been the plan. Justin makes the snapshots, and I'm not sure what his plans are. I can tell you, however, that unless it gets made this week (unlikely), it won't happen until January. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 14 15:09:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27473 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 15:09:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns2.inch.com (oscar.inch.com [207.240.140.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27467; Mon, 14 Dec 1998 15:09:43 -0800 (PST) (envelope-from spork@super-g.com) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by ns2.inch.com (8.8.8/8.8.5) with ESMTP id SAA23466; Mon, 14 Dec 1998 18:09:39 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id SAA12259; Mon, 14 Dec 1998 18:08:33 -0500 (EST) Date: Mon, 14 Dec 1998 18:08:33 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: <199812141753.KAA54713@panzer.plutotech.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 OK, I'm just going to bug you one more time with two questions: Where can I find more docs for cam? Like cam(3) or something? How can I adjust things so that only a certain amount of tags are used (like we've been discussing)? I assume it has something to do with "quirk entries", but I'm not sure where that type of thing gets defined... Thanks again, Charles --- Charles Sprickman spork@super-g.com On Mon, 14 Dec 1998, Kenneth D. Merry wrote: > It might very well go away. The only way to find out is to try it. Since > it can supposedly handle 64 commands, you might try setting the maximum in > the quirk entry to 32, to divide the load evenly. You could set the > minimum to 24 or so. > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 14 15:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29043 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 15:21:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29024; Mon, 14 Dec 1998 15:21:36 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA56332; Mon, 14 Dec 1998 16:21:27 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812142321.QAA56332@panzer.plutotech.com> Subject: Re: CAM and -stable In-Reply-To: from spork at "Dec 14, 98 06:08:33 pm" To: spork@super-g.com (spork) Date: Mon, 14 Dec 1998 16:21:27 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 spork wrote... > OK, I'm just going to bug you one more time with two questions: > > Where can I find more docs for cam? Like cam(3) or something? There are lots of man pages. It just depends on what you want documentation on. Most of the controller drivers have man pages (like ahc(4), dpt(4)). All of the peripheral drivers have man pages (like da(4), pass(4)). If you want generic kernel configuration information, see scsi(4). (a.k.a. cam(4)) cam(3) certainly exists, but it's probably not what you're looking for. (Unless you're writing a userland SCSI pass-through program) Oops, I just realized that you're using -stable. Most of those man pages aren't available in -stable. In any case, the quirk entry stuff you want to do isn't documented anywhere, so the docs from -current wouldn't help. > How can I adjust things so that only a certain amount of tags are used > (like we've been discussing)? I assume it has something to do with > "quirk entries", but I'm not sure where that type of thing gets defined... Oh, I should have been a little more clear there. Go into sys/cam/cam_xpt.c, and look around near the top of the file. You'll see a quirk table with entries like this: { /* Reports QUEUE FULL for temporary resource shortages */ { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP39100*", "*" }, /*quirks*/0, /*mintags*/24, /*maxtags*/32 }, And, as far as numbers go, I'd suggest that you use exactly the numbers that we use for the Atlas II, above. They'll apply to both luns of your RAID controller, so the available tag openings will be evenly split between the two. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 14 15:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03514 for freebsd-scsi-outgoing; Mon, 14 Dec 1998 15:56:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03494; Mon, 14 Dec 1998 15:56:39 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id SAA17264; Mon, 14 Dec 1998 18:56:03 -0500 (EST) Date: Mon, 14 Dec 1998 18:56:03 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: <199812142321.QAA56332@panzer.plutotech.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 Hi Ken, This is your day. I'm giving the following a spin. I'm not much into C, but I think I got all the fields right: > /* Added to fix CRD-5440's lack of tags */ > { T_DIRECT, SIP_MEDIA_FIXED, "CMD TECH", "CRD-5440*", "*"}, > /*quirks*/0, /*mintags*/22, /*maxtags*/30 > }, > { Thanks again, I appreciate your help with this... Charles --- Charles Sprickman spork@super-g.com On Mon, 14 Dec 1998, Kenneth D. Merry wrote: > Oh, I should have been a little more clear there. Go into > sys/cam/cam_xpt.c, and look around near the top of the file. You'll see a > quirk table with entries like this: > > { > /* Reports QUEUE FULL for temporary resource shortages */ > { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP39100*", "*" }, > /*quirks*/0, /*mintags*/24, /*maxtags*/32 > }, > > And, as far as numbers go, I'd suggest that you use exactly the numbers > that we use for the Atlas II, above. They'll apply to both luns of your > RAID controller, so the available tag openings will be evenly split between > the two. > > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 13:32:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28725 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 13:32:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28711 for ; Tue, 15 Dec 1998 13:32:23 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id OAA59717; Tue, 15 Dec 1998 14:17:40 -0700 (MST) Date: Tue, 15 Dec 1998 14:17:40 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812152117.OAA59717@narnia.plutotech.com> To: Richard Smith cc: scsi@FreeBSD.ORG Subject: Re: Update: ncr0: timeout problem X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <36753F8E.D2A105FE@jezebel.demon.co.uk> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Over a month ago, I posted a timeout problem I was having with my > symbios controller and fujitsu drive, on 2.2.7R > > I have now upgraded to 3.0R and the problem although different, still > remains. I was advised at the time that the problem would be easier to > diagnose under 3.0, so here goes... My guess would be that the Fujitsu doesn't like getting lots of tags. CAM will actually send more transactions to the drive in parallel than the old SCSI code which could be making the problem worse than before. Unfortunately, my knowledge of the underlying NCR hardware is pretty limitted, so I can't say for sure that this is the cause of the problem. Try reducing the number of transactions that CAM sends to the drive and see if this helps. You can do this by adding a quirk entry for your drive in sys/cam/cam_xpt.c. Something like this should get you started: { /* Broken tagged queuing drive?? */ { T_DIRECT, SIP_MEDIA_FIXED, "FUJITSU", "M2949E-512", "0134" }, /*quirks*/0, /*mintags*/2, /*maxtags*/2 }, If this works, increment the maxtags value until it stops working. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 14:22:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05788 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 14:22:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from net.kitel.co.kr (net.kitel.co.kr [210.102.35.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05781 for ; Tue, 15 Dec 1998 14:22:42 -0800 (PST) (envelope-from swjeong@net.kitel.co.kr) Received: (from swjeong@localhost) by net.kitel.co.kr (8.8.8H1/8.8.8) id HAA01711 for freebsd-scsi@FreeBSD.ORG; Wed, 16 Dec 1998 07:22:35 +0900 (KST) Date: Wed, 16 Dec 1998 07:22:35 +0900 (KST) From: swjeong Message-Id: <199812152222.HAA01711@net.kitel.co.kr> To: freebsd-scsi@FreeBSD.ORG Subject: kernel panic with ufsspec_write Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have used segate ST34572W (4G ultra wide) under heavy load on RELEASE-2.2.5 . But in the same configuration with ST34371W on RELEASE-3.0, there is kernel panic. Printed message is 'ufsspec_write .....' What is the reason of the panic? I turned off tagged queue by setting DQue bit in mode page 10. But the panic still existed. System up time is a day or two. And it's heavily loaded system. And I couldn't debug on dump image. www# gdb -k /kernel.981215.debug vmcore.0 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... "/kernel.981215.debug": not in executable format: File format not recognized kgdb could not open the exec-file, please check the name you used ! (kgdb) How can I debug with aout image ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 15:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16161 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 15:53:59 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from net.kitel.co.kr (net.kitel.co.kr [210.102.35.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16150 for ; Tue, 15 Dec 1998 15:53:57 -0800 (PST) (envelope-from swjeong@net.kitel.co.kr) Received: (from swjeong@localhost) by net.kitel.co.kr (8.8.8H1/8.8.8) id IAA05913 for freebsd-scsi@FreeBSD.ORG; Wed, 16 Dec 1998 08:53:50 +0900 (KST) Date: Wed, 16 Dec 1998 08:53:50 +0900 (KST) From: swjeong Message-Id: <199812152353.IAA05913@net.kitel.co.kr> To: freebsd-scsi@FreeBSD.ORG Subject: scsi error message Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am using 3.0-RELEASE. I saw the following SCSI error message. What is the reason? I have properley terminated SCSI bus. # dmesg ... da5 at ahc0 bus 0 target 7 lun 0 da5: Fixed Direct Access SCSI2 device da5: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled da5: 8347MB (17096357 512 byte sectors: 255H 63S/T 1064C) ... (da5:ahc0:0:7:0): tagged openings now 62 (da5:ahc0:0:7:0): SCB 0x10 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x8 SSTAT1 == 0xa (da5:ahc0:0:7:0): Queuing a BDR SCB (da5:ahc0:0:7:0): Bus Device Reset Message Sent (da5:ahc0:0:7:0): no longer in timeout, status = 34b ahc0: Bus Device Reset Sent. 62 SCBs aborted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 18:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06221 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 18:20:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06216 for ; Tue, 15 Dec 1998 18:20:52 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA64842; Tue, 15 Dec 1998 19:20:32 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812160220.TAA64842@panzer.plutotech.com> Subject: Re: scsi error message In-Reply-To: <199812152353.IAA05913@net.kitel.co.kr> from swjeong at "Dec 16, 98 08:53:50 am" To: swjeong@net.kitel.co.kr (swjeong) Date: Tue, 15 Dec 1998 19:20:32 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 swjeong wrote... > > I am using 3.0-RELEASE. > I saw the following SCSI error message. > What is the reason? > I have properley terminated SCSI bus. > > # dmesg > > ... > > da5 at ahc0 bus 0 target 7 lun 0 > da5: Fixed Direct Access SCSI2 device > da5: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled > da5: 8347MB (17096357 512 byte sectors: 255H 63S/T 1064C) > > ... > > (da5:ahc0:0:7:0): tagged openings now 62 > (da5:ahc0:0:7:0): SCB 0x10 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR == 0x8 > SSTAT1 == 0xa > (da5:ahc0:0:7:0): Queuing a BDR SCB > (da5:ahc0:0:7:0): Bus Device Reset Message Sent > (da5:ahc0:0:7:0): no longer in timeout, status = 34b > ahc0: Bus Device Reset Sent. 62 SCBs aborted The "timed out while idle" message is caused by a device going "out to lunch" and not coming back on the bus. In this case, it probably means that we sent a transaction to the disk and it didn't return the transaction within 60 seconds. That drive, with the 71xx firmware revisions, is known to be more or less broken for tagged queueing. Since I see the tagged openings message, either one of two things has happened: - You have disabled the quirk entry in cam_xpt.c. - There's something wrong with the quirk entry or quirk entry mechanism, since it is reporting the number of outstanding tags. So, have you changed the quirk entry? There's one other odd, and possibly bad thing there. The above disk is on SCSI ID 7. That's generally the SCSI ID that the SCSI controller is on. What SCSI ID is your controller on? Can you send the full dmesg output from that machine? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 18:26:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07275 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 18:26:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07270 for ; Tue, 15 Dec 1998 18:26:27 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA64896; Tue, 15 Dec 1998 19:26:07 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812160226.TAA64896@panzer.plutotech.com> Subject: Re: kernel panic with ufsspec_write In-Reply-To: <199812152222.HAA01711@net.kitel.co.kr> from swjeong at "Dec 16, 98 07:22:35 am" To: swjeong@net.kitel.co.kr (swjeong) Date: Tue, 15 Dec 1998 19:26:07 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 swjeong wrote... > > I have used segate ST34572W (4G ultra wide) under heavy load on RELEASE-2.2.5 . > But in the same configuration with ST34371W on RELEASE-3.0, > there is kernel panic. > Printed message is > > 'ufsspec_write .....' > > What is the reason of the panic? It looks like a filesystem type panic. I doubt it is SCSI-related. > I turned off tagged queue by setting DQue bit in mode page 10. > But the panic still existed. Turning off tagged queueing will only help your problem if it is load-related. (i.e., if load on the filesystem causes the panic, turning off tagged queueing will have the effect of decreasing the amount of simultaneous I/O you can do to the drive, and therefore decrease the load the filesystem.) > System up time is a day or two. And it's heavily loaded system. > > And I couldn't debug on dump image. > > www# gdb -k /kernel.981215.debug vmcore.0 > GDB is free software and you are welcome to distribute copies of it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.16 (i386-unknown-freebsd), > Copyright 1996 Free Software Foundation, Inc... > > "/kernel.981215.debug": not in executable format: File format not recognized > > kgdb could not open the exec-file, please check the name you used ! > (kgdb) > > How can I debug with aout image ? I'm not sure if 3.0-RELEASE shipped with an a.out verison of gdb. If it did, you could probably do something like: gdb -aout -k /kernel.981215.debug vmcore.0 If it didn't, you can fetch an a.out verison of gdb here: ftp://ftp.lemis.com/pub/vinum/gdb-aout Hopefully that will enable you get a good stack trace from your core dump and debugging kernel. Without a stack trace, it'll be difficult to track down the problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 20:27:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19146 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 20:27:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org ([142.177.186.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19141 for ; Tue, 15 Dec 1998 20:27:21 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id AAA22374 for ; Wed, 16 Dec 1998 00:27:14 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 16 Dec 1998 00:27:14 -0400 (AST) From: The Hermit Hacker To: freebsd-scsi@FreeBSD.ORG Subject: Invalidating pack... 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 just want to confirm, but this is definitely a drive problem? I'm starting to suspect the controller itself, cause we keep losing drives on that controller *sigh* But I want to make sure it isn't a 'ghost error' from the controller, vs a drive problem: Unexpected busfree. LASTPHASE == 0x40 SEQADDR == 0x110 (da8:ahc2:0:5:0): Invalidating pack Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 21:28:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24746 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 21:28:56 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org ([142.177.186.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24741 for ; Tue, 15 Dec 1998 21:28:54 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id BAA22813 for ; Wed, 16 Dec 1998 01:28:48 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 16 Dec 1998 01:28:48 -0400 (AST) From: The Hermit Hacker To: freebsd-scsi@FreeBSD.ORG Subject: benign message, or something to worry about? 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 (da0:ahc0:0:0:0): SCB 0x4e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0xa SSTAT1 == 0xa (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:0. 31 SCBs aborted Possible drive problem, or just normal operation? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 22:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01419 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 22:47:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01407 for ; Tue, 15 Dec 1998 22:47:32 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.1/8.9.1) id WAA22578; Tue, 15 Dec 1998 22:47:12 -0800 (PST) (envelope-from mph) Message-ID: <19981215224711.A21538@wopr.caltech.edu> Date: Tue, 15 Dec 1998 22:47:11 -0800 From: Matthew Hunt To: "Kenneth D. Merry" , Oliver Fromme Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM References: <19981129142027.A9664@wopr.caltech.edu> <199812010528.WAA13755@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812010528.WAA13755@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Nov 30, 1998 at 10:28:58PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Nov 30, 1998 at 10:28:58PM -0700, Kenneth D. Merry wrote: > Matthew Hunt wrote... > > [ after non-CAM to CAM upgrade... ] > > When I try to rip CD audio, tosha emits the following error: > > > > wopr:~/tmp$ tosha -v -t 1 -o out.pcm > > Device: /dev/cd0c IBM CDRM00201 !F 0724 > > tosha: WARNING: Drive type not recognized. > > [...] > > error returned from CD-DA read command: > > (pass1:ahc0:0:3:0): Vendor Specific Command. CDB: d8 > > (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:bf,0 > > (pass1:ahc0:0:3:0): Vendor Specific ASC > It's kinda difficult to decipher vendor-specific error messages. I would > suggest contacting Oliver Fromme . He > is the author of tosha, and he may know what that error code means. He may > also want to explicitly define that particular IBM CDROM drive as a > Toshiba-like drive. As it turns out, it looks like treating my IBM branded drive as a Toshiba does fix the problem. I have no idea why it would have started appearing after changing to CAM. I've attached the trivial patch I've used, but I don't know whether it's appropriate for widespread use. I understand that my drive is really an XM-4101, but I don't know whether it's generally true that IBM drives are really Toshibae. --- /usr/home/mph/FreeBSD/ports/audio/tosha/work/tosha-0.05/tosha.c Tue Dec 15 22:45:25 1998 +++ tosha.c.new Tue Dec 15 22:44:56 1998 @@ -627,6 +627,7 @@ fprintf (stderr, "Device: %s %s %s %s\n", device, vendor, product, versid); if (!strncmp(vendor, "TOSHIBA", 7) || + !strncmp(vendor, "IBM", 3) || !strncmp(vendor, "DEC", 3)) { denschange = 0x82; } -- Matthew Hunt * Inertia is a property of matter. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 15 23:09:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03025 for freebsd-scsi-outgoing; Tue, 15 Dec 1998 23:09:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03020 for ; Tue, 15 Dec 1998 23:09:17 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id AAA66347; Wed, 16 Dec 1998 00:09:08 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812160709.AAA66347@panzer.plutotech.com> Subject: Re: benign message, or something to worry about? In-Reply-To: from The Hermit Hacker at "Dec 16, 98 01:28:48 am" To: scrappy@hub.org (The Hermit Hacker) Date: Wed, 16 Dec 1998 00:09:08 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 The Hermit Hacker wrote... > > (da0:ahc0:0:0:0): SCB 0x4e - timed out while idle, LASTPHASE == 0x1, > SCSISIGI == 0x0 > SEQADDR == 0xa > SSTAT1 == 0xa > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > ahc0: Bus Device Reset on A:0. 31 SCBs aborted > > > Possible drive problem, or just normal operation? It could be a drive problem. It means that the drive didn't complete an I/O before the timeout. The read/write timeout in the da driver is currently 60 seconds. We had to hit the drive with a BDR to get it to "wake up". We can generally recover from that sort of problem, but it generally indicates a firmware problem of some sort with the drive. The most notorious drives for that sort of problem are the Quantum Atlas II's. What sort of drive is it? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 00:32:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10864 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 00:32:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10825 for ; Wed, 16 Dec 1998 00:31:46 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id OAA06328; Wed, 16 Dec 1998 14:20:20 +0600 (NS) Date: Wed, 16 Dec 1998 14:20:20 +0600 (NS) From: Max Khon To: Matthew Hunt cc: "Kenneth D. Merry" , Oliver Fromme , freebsd-scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM In-Reply-To: <19981215224711.A21538@wopr.caltech.edu> 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 hi, there! On Tue, 15 Dec 1998, Matthew Hunt wrote: > > > [ after non-CAM to CAM upgrade... ] > > > When I try to rip CD audio, tosha emits the following error: > > > > > > wopr:~/tmp$ tosha -v -t 1 -o out.pcm > > > Device: /dev/cd0c IBM CDRM00201 !F 0724 > > > tosha: WARNING: Drive type not recognized. > > > [...] > > > error returned from CD-DA read command: > > > (pass1:ahc0:0:3:0): Vendor Specific Command. CDB: d8 > > > (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:bf,0 > > > (pass1:ahc0:0:3:0): Vendor Specific ASC I have the same problem with Sony CDU948S-RP cd-recorder After transition to CAM tosha stops grabbing after transferring about ~3M of data: === husky:~$ tosha -w -t 1 Device: /dev/cd0c SONY CD-R CDU948S 1.0e track playing start end raw size mp3 size # of number time sector sector in bytes 128 kbps frames -------------------------------------------------------------- 1 5:13'20 32 23526 55260240 5013101 11993 Reading to track01.wav ... error returned from CD-DA read command: (pass0:ncr0:0:6:0): Vendor Specific Command. CDB: d8 (pass0:ncr0:0:6:0): ILLEGAL REQUEST asc:bf,0 (pass0:ncr0:0:6:0): Vendor Specific ASC husky:~$ tosha -w -t 8 Device: /dev/cd0c SONY CD-R CDU948S 1.0e track playing start end raw size mp3 size # of number time sector sector in bytes 128 kbps frames -------------------------------------------------------------- 8 3:44'58 189692 206549 39650016 3597208 8605 Reading to track08.wav ... error returned from CD-DA read command: (pass0:ncr0:0:6:0): Vendor Specific Command. CDB: d8 (pass0:ncr0:0:6:0): ILLEGAL REQUEST asc:bf,0 (pass0:ncr0:0:6:0): Vendor Specific ASC === husky:~$ ls -l track*.wav -rw-r--r-- 1 root wheel 3010604 Dec 16 14:15 track01.wav -rw-r--r-- 1 root wheel 3010604 Dec 16 14:15 track08.wav === Dec 15 21:21:35 husky /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Dec 15 21:21:35 husky /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Dec 15 21:21:35 husky /kernel: The Regents of the University of California. All rights reserved. Dec 15 21:21:35 husky /kernel: FreeBSD 3.0-CURRENT #36: Tue Dec 15 21:20:21 NS 1998 Dec 15 21:21:35 husky /kernel: fjoe@husky.iclub.nsu.ru:/usr/src/sys/compile/husky Dec 15 21:21:35 husky /kernel: Timecounter "i8254" frequency 1193182 Hz Dec 15 21:21:35 husky /kernel: CPU: Pentium/P55C (187.11-MHz 586-class CPU) Dec 15 21:21:35 husky /kernel: Origin = "GenuineIntel" Id = 0x543 Stepping=3 Dec 15 21:21:35 husky /kernel: Features=0x8001bf Dec 15 21:21:35 husky /kernel: real memory = 33554432 (32768K bytes) Dec 15 21:21:35 husky /kernel: config> quit Dec 15 21:21:35 husky /kernel: avail memory = 29761536 (29064K bytes) Dec 15 21:21:35 husky /kernel: Probing for devices on PCI bus 0: Dec 15 21:21:35 husky /kernel: chip0: rev 0x03 on pci0.0.0 Dec 15 21:21:35 husky /kernel: chip1: rev 0x01 on pci0.7.0 Dec 15 21:21:35 husky /kernel: ide_pci0: rev 0x00 on pci0.7.1 Dec 15 21:21:35 husky /kernel: vga0: rev 0x60 int a irq 10 on pci0.10.0 Dec 15 21:21:35 husky /kernel: ncr0: rev 0x12 int a irq 10 on pci0.11.0 Dec 15 21:21:35 husky /kernel: Probing for PnP devices: Dec 15 21:21:35 husky /kernel: CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] Dec 15 21:21:35 husky /kernel: ESS1868 (rev 11 Dec 15 21:21:35 husky /kernel: , native mode) Dec 15 21:21:35 husky /kernel: pcm1 (ESS1868 sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 on isa Dec 15 21:21:35 husky /kernel: Probing for devices on the ISA bus: Dec 15 21:21:35 husky /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Dec 15 21:21:35 husky /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Dec 15 21:21:35 husky /kernel: ed0 at 0x300-0x31f irq 9 on isa Dec 15 21:21:35 husky /kernel: ed0: address 00:00:01:ff:04:1e, type NE2000 (16 bit) Dec 15 21:21:35 husky /kernel: fe0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa Dec 15 21:21:35 husky /kernel: sio0: type 16550A Dec 15 21:21:35 husky /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Dec 15 21:21:35 husky /kernel: sio1: type 16550A Dec 15 21:21:35 husky /kernel: lpt0 at 0x378-0x37f irq 7 on isa Dec 15 21:21:35 husky /kernel: lpt0: Interrupt-driven port Dec 15 21:21:35 husky /kernel: lp0: TCP/IP capable interface Dec 15 21:21:35 husky /kernel: psm0 not found at 0x60 Dec 15 21:21:35 husky /kernel: pcm0 not found Dec 15 21:21:35 husky /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Dec 15 21:21:35 husky /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 15 21:21:35 husky /kernel: fd0: 1.44MB 3.5in Dec 15 21:21:35 husky /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff on isa Dec 15 21:21:35 husky /kernel: wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 Dec 15 21:21:35 husky /kernel: wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S Dec 15 21:21:35 husky /kernel: wdc1 at 0x170-0x177 irq 15 flags 0xa0ff on isa Dec 15 21:21:35 husky /kernel: wdc1: unit 1 (atapi): , removable, accel, dma, iordis Dec 15 21:21:35 husky /kernel: wcd0: 2062KB/sec, 12 Dec 15 21:21:35 husky /kernel: 8KB cache, audio play, 256 volume levels, ejectable tray Dec 15 21:21:35 husky /kernel: wcd0: 120mm photo disc loaded, unlocked Dec 15 21:21:35 husky /kernel: wt0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: mcd0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: matcdc0 not found at 0x230 Dec 15 21:21:35 husky /kernel: scd0 not found at 0x230 Dec 15 21:21:35 husky /kernel: ie0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: ep0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: ex0 not found Dec 15 21:21:35 husky /kernel: le0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: lnc0 not found at 0x280 Dec 15 21:21:35 husky /kernel: ze0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: zp0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: cs0 not probed due to I/O address conflict with ed0 at 0x300 Dec 15 21:21:35 husky /kernel: adv0 not found at 0x330 Dec 15 21:21:35 husky /kernel: bt0 not found at 0x134 Dec 15 21:21:35 husky /kernel: aha0 not found at 0x134 Dec 15 21:21:35 husky /kernel: npx0 on motherboard Dec 15 21:21:35 husky /kernel: npx0: INT 16 interface Dec 15 21:21:35 husky /kernel: Intel Pentium F00F detected, installing workaround Dec 15 21:21:35 husky /kernel: Waiting 5 seconds for SCSI devices to settle Dec 15 21:21:35 husky /kernel: changing root device to wd0s1a Dec 15 21:21:35 husky /kernel: cd0 at ncr0 bus 0 target 6 lun 0 Dec 15 21:21:35 husky /kernel: cd0: Removable CD-ROM SCSI-2 device Dec 15 21:21:35 husky /kernel: cd0: 10.0M Dec 15 21:21:35 husky /kernel: B/s transfers (10.0MHz, offset 8) Dec 15 21:21:35 husky /kernel: cd0: cd present [340242 x 2048 byte records] /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 02:37:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21779 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 02:37:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from datasail.it ([194.177.99.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21772 for ; Wed, 16 Dec 1998 02:37:00 -0800 (PST) (envelope-from bago@datasail.it) Received: from lust (194.177.99.15) by datasail.it with SMTP (Eudora Internet Mail Server 1.1.2); Wed, 16 Dec 1998 11:39:10 +0000 Message-Id: <4.1.19981216113848.00a29210@splut.datasail.it> X-Sender: bago@splut.datasail.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 16 Dec 1998 11:42:15 +0100 To: freebsd-scsi@FreeBSD.ORG From: Bagnara Stefano Subject: DPT 2144 UWR and RAID Manager Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just bought DPT 2144 UWR and 3 x 4.5GB IBM SCSI HDD. I need to implement RAID5 on my freebsd 3. I've seen that i got the storage manager only for DOS, Windows 3.1 Windows 95/98, Windows NT, OS/2, Netware, SCO, NextStep; but no storage manager for FreeBSD. How can i do? What packages i need? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 03:34:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27316 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 03:34:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27309 for ; Wed, 16 Dec 1998 03:34:51 -0800 (PST) (envelope-from richard@jezebel.demon.co.uk) Received: from jezebel.demon.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id LAA25205; Wed, 16 Dec 1998 11:33:59 GMT (envelope-from richard@jezebel.demon.co.uk) Message-ID: <36779AE4.18B06075@jezebel.demon.co.uk> Date: Wed, 16 Dec 1998 11:35:00 +0000 From: Richard Smith Organization: http://www.trltech.co.uk X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: scsi@FreeBSD.ORG Subject: Re: Update: ncr0: timeout problem References: <199812152117.OAA59717@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > > > Over a month ago, I posted a timeout problem I was having with my > > symbios controller and fujitsu drive, on 2.2.7R > > > > I have now upgraded to 3.0R and the problem although different, still > > remains. I was advised at the time that the problem would be easier to > > diagnose under 3.0, so here goes... > > My guess would be that the Fujitsu doesn't like getting lots of tags. > CAM will actually send more transactions to the drive in parallel than > the old SCSI code which could be making the problem worse than before. > Unfortunately, my knowledge of the underlying NCR hardware is pretty > limitted, so I can't say for sure that this is the cause of the problem. > > Try reducing the number of transactions that CAM sends to the drive > and see if this helps. You can do this by adding a quirk entry > for your drive in sys/cam/cam_xpt.c. Something like this should get > you started: > > { > /* Broken tagged queuing drive?? */ > { T_DIRECT, SIP_MEDIA_FIXED, "FUJITSU", "M2949E-512", "0134" }, > /*quirks*/0, /*mintags*/2, /*maxtags*/2 > }, > > If this works, increment the maxtags value until it stops working. :-( I successfully managed to reduce the number of timeout messages to two: ncr0: timeout nccb=0xf0857400 ncr0: timeout nccb=0xf085f800 So I guess the quirk entry was correctly picked up, but did not cure the problem. Thanks for your support. -richard _______________________________________________________________________ Richard Smith Assistant Chief Engineer TRL Technology Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 05:20:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11868 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 05:20:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11826 for ; Wed, 16 Dec 1998 05:20:13 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id OAA06541; Wed, 16 Dec 1998 14:19:12 +0100 (CET) (envelope-from olli) Date: Wed, 16 Dec 1998 14:19:12 +0100 (CET) From: Oliver Fromme Message-Id: <199812161319.OAA06541@dorifer.heim3.tu-clausthal.de> To: freebsd-scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM Cc: mph@pobox.com Newsgroups: list.freebsd-scsi Organization: Administration Heim 3 Reply-To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Hunt wrote in list.freebsd-scsi: > As it turns out, it looks like treating my IBM branded drive as a > Toshiba does fix the problem. I have no idea why it would have started > appearing after changing to CAM. I changed the default handling of unrecognized drives between versions 0.04 and 0.05 of tosha -- that might be the reason. > I've attached the trivial patch I've used, but I don't know whether > it's appropriate for widespread use. I understand that my drive is > really an XM-4101, but I don't know whether it's generally true that > IBM drives are really Toshibae. This is the first time I hear about an "IBM" CD-ROM drive, so I just added that entry to tosha's config file. Thanks for letting me know. If you're familiar with CVS, you can checkout tosha-current from the public CVS repository, just set $CVSROOT to this: :pserver:cvs@dorifer.heim3.tu-clausthal.de:/home/cvs/cvs Then type "cvs login", enter "cvs" as password, and type "cvs checkout tosha". I hope to get around to release a new version soon, it will probably not be much different from what's in the repository right now. Regards Oliver PS: The "media changed" problem is known and will be fixed. :-) -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 05:32:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13163 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 05:32:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13158 for ; Wed, 16 Dec 1998 05:32:32 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id OAA06630; Wed, 16 Dec 1998 14:29:03 +0100 (CET) (envelope-from olli) Date: Wed, 16 Dec 1998 14:29:03 +0100 (CET) From: Oliver Fromme Message-Id: <199812161329.OAA06630@dorifer.heim3.tu-clausthal.de> To: freebsd-scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM Cc: fjoe@iclub.nsu.ru Newsgroups: list.freebsd-scsi Organization: Administration Heim 3 Reply-To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Max Khon wrote in list.freebsd-scsi: > I have the same problem with Sony CDU948S-RP cd-recorder > After transition to CAM tosha stops grabbing after transferring about ~3M > of data: > [...] > (pass0:ncr0:0:6:0): Vendor Specific Command. CDB: d8 > (pass0:ncr0:0:6:0): ILLEGAL REQUEST asc:bf,0 > (pass0:ncr0:0:6:0): Vendor Specific ASC > [...] > -rw-r--r-- 1 root wheel 3010604 Dec 16 14:15 track01.wav > -rw-r--r-- 1 root wheel 3010604 Dec 16 14:15 track08.wav That's really strange. That file size is neither a multiple of 512 nor of 2352 (the "red book" sector size). Do those files contain correct audio data, or are they garbage (silence, white noise or whatever)? You could try to checkout tosha-current, as I explained in the previous posting in this thread on the freebsd-scsi list, but I doubt that it has anything to do with your problem. By the way, you shouldn't call those files *.wav unless they're in WAV format. Tosha 0.05 always creates "raw" PCM files without any header, while Tosha-current supports a bunch of different audio formats, including WAV. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 06:34:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21267 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 06:34:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21250; Wed, 16 Dec 1998 06:34:15 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.103]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id KAA11222; Wed, 16 Dec 1998 10:34:04 -0400 (AST) Date: Wed, 16 Dec 1998 10:34:39 -0400 (AST) From: "Marc G. Fournier" To: freebsd-scsi@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: any way of gleaming info from these? 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 vnode_pager_putpages: residual I/O 4096 at 113 vnode_pager_putpages: I/O error 6 vnode_pager_putpages: residual I/O 4096 at 113 vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 vnode_pager_putpages: I/O error 6 vnode_pager_putpages: residual I/O 4096 at 113 maybe its totally impossible, but is there no way of detailing which drive is causing this? or is it not a drive? Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 06:48:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23222 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 06:48:01 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23193; Wed, 16 Dec 1998 06:47:58 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id GAA09727; Wed, 16 Dec 1998 06:48:06 -0800 (PST) Message-Id: <199812161448.GAA09727@root.com> To: "Marc G. Fournier" cc: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-reply-to: Your message of "Wed, 16 Dec 1998 10:34:39 -0400." From: David Greenman Reply-To: dg@root.com Date: Wed, 16 Dec 1998 06:48:06 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >vnode_pager_putpages: residual I/O 4096 at 113 >vnode_pager_putpages: I/O error 6 >vnode_pager_putpages: residual I/O 4096 at 113 >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 >vnode_pager_putpages: I/O error 6 >vnode_pager_putpages: residual I/O 4096 at 113 > >maybe its totally impossible, but is there no way of detailing which drive >is causing this? or is it not a drive? Error 6 is ENXIO - device not configured. This might happen if the device is SCSI and it loses power/goes offline. I can't think of any other reasons offhand. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 07:07:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25742 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 07:07:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from moran.grauel.com (moran.grauel.com [199.233.104.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25733 for ; Wed, 16 Dec 1998 07:07:55 -0800 (PST) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.1/8.8.7) id KAA00251; Wed, 16 Dec 1998 10:08:19 -0500 (EST) From: Richard J Kuhns MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13943.52451.453181.907266@moran.grauel.com> Date: Wed, 16 Dec 1998 10:08:19 -0500 (EST) To: freebsd-scsi@FreeBSD.ORG Subject: New problem with under -current X-Mailer: VM 6.56 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some time ago, after I switch to CAM, I reported that I could no longer write tapes, altho I could read just fine. With a new kernel (cvsuped 12/15/98), I can still read tapes just fine, but here's what happens when I try to write: moran:~$ tar -cvf /dev/rsa0 zigzag-0.61.tar.gz zigzag-0.61.tar.gz tar: can't write to /dev/rsa0 : Invalid argument Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): WRITE(06). CDB: a 0 0 28 0 0 Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): ILLEGAL REQUEST csi:0,0,80,8 asc:0,13 Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): Audio play operation successfully completed Relevant info: ahc0: rev 0x00 int a irq 10 on pci0.20.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ... Waiting 10 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers ... moran:~$ mt status Mode Density Blocksize bpi Compression Current: QIC-320 variable 16000 unsupported ---------available modes--------- 0: QIC-320 variable 16000 unsupported 1: QIC-320 variable 16000 unsupported 2: QIC-320 variable 16000 unsupported 3: QIC-320 variable 16000 unsupported Any suggestions? I intend to buy a new tape drive sometime after the holidays, but it would still be nice to have this one working. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 07:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29297 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 07:45:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29289; Wed, 16 Dec 1998 07:45:51 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id QAA13332; Wed, 16 Dec 1998 16:45:19 +0100 (CET) (envelope-from des) To: spork Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable References: From: Dag-Erling Smorgrav Date: 16 Dec 1998 16:45:18 +0100 In-Reply-To: spork's message of "Mon, 14 Dec 1998 18:56:03 -0500 (EST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org spork writes: > > /* Added to fix CRD-5440's lack of tags */ It's not lack of tags that's the problem (64 is pretty good), but the fact that the firmware (incorrectly) reports that it's out of queue slots when things get busy. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 07:51:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00572 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 07:51:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00544; Wed, 16 Dec 1998 07:50:57 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.103]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id LAA17300; Wed, 16 Dec 1998 11:49:41 -0400 (AST) Date: Wed, 16 Dec 1998 11:50:16 -0400 (AST) From: "Marc G. Fournier" To: David Greenman cc: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-Reply-To: <199812161448.GAA09727@root.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, 16 Dec 1998, David Greenman wrote: > >vnode_pager_putpages: residual I/O 4096 at 113 > >vnode_pager_putpages: I/O error 6 > >vnode_pager_putpages: residual I/O 4096 at 113 > >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 > >vnode_pager_putpages: I/O error 6 > >vnode_pager_putpages: residual I/O 4096 at 113 > > > >maybe its totally impossible, but is there no way of detailing which drive > >is causing this? or is it not a drive? > > Error 6 is ENXIO - device not configured. This might happen if the device > is SCSI and it loses power/goes offline. I can't think of any other reasons > offhand. Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? The system is locked up right now, awaiting someone to get down to the office and reboot it. Looking through /usr/src/sys, the error message is generated in vm/vnode_pager.c...which, to me, would indicate swap space? Is there no way of adding in the name of the device generating this error to the error message? Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 08:00:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01990 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 08:00:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00704 for ; Wed, 16 Dec 1998 07:51:51 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id VAA15945; Wed, 16 Dec 1998 21:49:51 +0600 (NS) Date: Wed, 16 Dec 1998 21:49:50 +0600 (NS) From: Max Khon To: Oliver Fromme cc: freebsd-scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM In-Reply-To: <199812161329.OAA06630@dorifer.heim3.tu-clausthal.de> 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 hi, there! On Wed, 16 Dec 1998, Oliver Fromme wrote: > > -rw-r--r-- 1 root wheel 3010604 Dec 16 14:15 track01.wav > > -rw-r--r-- 1 root wheel 3010604 Dec 16 14:15 track08.wav > > That's really strange. That file size is neither a multiple of > 512 nor of 2352 (the "red book" sector size). > Do those files contain correct audio data, or are they garbage > (silence, white noise or whatever)? you forgot 44 bytes of .wav header > You could try to checkout tosha-current, as I explained in the > previous posting in this thread on the freebsd-scsi list, but I > doubt that it has anything to do with your problem. where can i get it? (cvsup, ftp, anything else) > By the way, you shouldn't call those files *.wav unless they're > in WAV format. Tosha 0.05 always creates "raw" PCM files > without any header, while Tosha-current supports a bunch of > different audio formats, including WAV. those files are actually .wav files. i just patched tosha to write .wav header (and IIRC i sent you those patches about a half year ago) /fjoe PS btw do you (or anyone else) have any data sheets on Sony CD-Rs -- i ported cdrdao from linux to FreeBSD (CAM) but cannot test all the functions because my Sony CDU948S-RP CD-R is not MMC-compatible and is not supported by cdrdao in any other way (does not have driver) cdrdao is recording tool which can burn audio CDs in DAO mode. i tried to e-mail Sony tech. support but they said that their management department decided to not distribute such info to end users To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 08:43:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08147 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 08:43:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08138 for ; Wed, 16 Dec 1998 08:43:41 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id IAA11135; Wed, 16 Dec 1998 08:43:19 -0800 Date: Wed, 16 Dec 1998 08:43:19 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Richard J Kuhns cc: freebsd-scsi@FreeBSD.ORG Subject: Re: New problem with under -current In-Reply-To: <13943.52451.453181.907266@moran.grauel.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 The write is in variable mode (of all things>. It needs to be in fixed block mode. Do a mt -f /dev/rsa0 blocksize 512. Why it thinks it came up in variable is a mystery to me. This might be a good QUIRK_FIXED candidate (when I check the code in) for this f/w- I think other 525's may in fact support variable (which, IIRC, isn't really variable in that it still has to be modulo 512). On Wed, 16 Dec 1998, Richard J Kuhns wrote: > Some time ago, after I switch to CAM, I reported that I could no longer > write tapes, altho I could read just fine. With a new kernel (cvsuped > 12/15/98), I can still read tapes just fine, but here's what happens when I > try to write: > > moran:~$ tar -cvf /dev/rsa0 zigzag-0.61.tar.gz > zigzag-0.61.tar.gz > tar: can't write to /dev/rsa0 : Invalid argument > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): WRITE(06). CDB: a 0 0 28 0 0 > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): ILLEGAL REQUEST csi:0,0,80,8 asc:0,13 > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): Audio play operation successfully completed > > Relevant info: > > ahc0: rev 0x00 int a irq 10 on pci0.20.0 > ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs > ... > Waiting 10 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-CCS device > sa0: 3.300MB/s transfers > ... > moran:~$ mt status > Mode Density Blocksize bpi Compression > Current: QIC-320 variable 16000 unsupported > ---------available modes--------- > 0: QIC-320 variable 16000 unsupported > 1: QIC-320 variable 16000 unsupported > 2: QIC-320 variable 16000 unsupported > 3: QIC-320 variable 16000 unsupported > > Any suggestions? I intend to buy a new tape drive sometime after the > holidays, but it would still be nice to have this one working. > > -- > Richard Kuhns rjk@grauel.com > PO Box 6249 Tel: (765)477-6000 \ > 100 Sawmill Road x319 > Lafayette, IN 47903 (800)489-4891 / > > 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 Dec 16 09:09:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12150 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 09:09:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12141 for ; Wed, 16 Dec 1998 09:09:04 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id SAA03255; Wed, 16 Dec 1998 18:08:33 +0100 (MET) Message-ID: <3677E911.7C422D3F@we.lc.ehu.es> Date: Wed, 16 Dec 1998 18:08:33 +0100 From: "José MŞ Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG CC: olli@dorifer.heim3.tu-clausthal.de Subject: Re: tosha reports random errors after transition to CAM References: <199812161329.OAA06630@dorifer.heim3.tu-clausthal.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oliver Fromme wrote: > > You could try to checkout tosha-current, as I explained in the > previous posting in this thread on the freebsd-scsi list, but I > doubt that it has anything to do with your problem. > tosha-current? How can I get it? I would like to test it against a NEC CDR-1410 which fails under tosha-0.05. -- JM ----------------------------------------------------------------------- José MŞ Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 09:09:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12168 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 09:09:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA12159 for ; Wed, 16 Dec 1998 09:09:13 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with esmtp (Exim 1.82 #3) id 0zqJYM-0003gZ-00; Wed, 16 Dec 1998 08:11:58 -0800 Date: Wed, 16 Dec 1998 08:11:53 -0800 (PST) From: Tom To: Bagnara Stefano cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT 2144 UWR and RAID Manager In-Reply-To: <4.1.19981216113848.00a29210@splut.datasail.it> 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, 16 Dec 1998, Bagnara Stefano wrote: > I just bought DPT 2144 UWR and 3 x 4.5GB IBM SCSI HDD. > I need to implement RAID5 on my freebsd 3. > > I've seen that i got the storage manager only for DOS, Windows 3.1 > Windows 95/98, Windows NT, OS/2, Netware, SCO, NextStep; but > no storage manager for FreeBSD. > > How can i do? What packages i need? A bootable DOS floppy, and dtpmgr.exe Setup the array, then install FreeBSD. The newer DPT cards include the DPT manager in flash. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 09:27:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14193 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 09:27:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14180 for ; Wed, 16 Dec 1998 09:27:18 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id MAA15985; Wed, 16 Dec 1998 12:19:04 -0500 (EST) (envelope-from larry) Date: Wed, 16 Dec 1998 12:19:04 -0500 From: "Larry S. Marso" To: =?iso-8859-1?Q?Jos=E9_M=AA_Alcaide?= , freebsd-scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM Message-ID: <19981216121903.N15104@marso.com> References: <199812161329.OAA06630@dorifer.heim3.tu-clausthal.de> <3677E911.7C422D3F@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.94.13i In-Reply-To: =?iso-8859-1?Q?=3C3677E911=2E7C422D3F=40we=2Elc=2Eehu=2Ees=3E=3B_from_Jo?= =?iso-8859-1?Q?s=E9_M=AA_Alcaide_on_Wed=2C_Dec_16=2C_1998_at_06:08:33PM_?= =?iso-8859-1?Q?+0100?= Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had to go into the Tosha source and set it to properly identify my Yamaha 4260. (I think the latest Tosha gets it right). What I did was set it to treat the Yamaha as one after another of the different cdrom burners it recognized. Well, actually, I hit it the right one the first try. Best regards -- Larry S. Marso larry@marso.com On Wed, Dec 16, 1998 at 06:08:33PM +0100, José MŞ Alcaide wrote: > Oliver Fromme wrote: > > > > You could try to checkout tosha-current, as I explained in the > > previous posting in this thread on the freebsd-scsi list, but I > > doubt that it has anything to do with your problem. > > > > tosha-current? How can I get it? I would like to test it > against a NEC CDR-1410 which fails under tosha-0.05. > > -- JM > ----------------------------------------------------------------------- > José MŞ Alcaide | mailto:jose@we.lc.ehu.es > Universidad del País Vasco | http://www.we.lc.ehu.es/~jose > Dpto. de Electricidad y Electrónica | > Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 > 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 > ----------------------------------------------------------------------- > "Go ahead... make my day." - H. Callahan > > 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 Dec 16 11:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00823 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 11:45:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from moran.grauel.com (moran.grauel.com [199.233.104.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00810 for ; Wed, 16 Dec 1998 11:45:00 -0800 (PST) (envelope-from rjk@moran.grauel.com) Received: (from rjk@localhost) by moran.grauel.com (8.9.1/8.8.7) id OAA14218; Wed, 16 Dec 1998 14:44:31 -0500 (EST) From: Richard J Kuhns Message-ID: <13944.3487.123163.720382@moran.grauel.com> Date: Wed, 16 Dec 1998 14:44:31 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: mjacob@feral.com CC: freebsd-scsi@FreeBSD.ORG Subject: Re: New problem with under -current In-Reply-To: References: <13943.52451.453181.907266@moran.grauel.com> X-Mailer: VM 6.56 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: >> I wrote: >> ... I can't write tapes... > > The write is in variable mode (of all things>. It needs to be in fixed > block mode. Do a mt -f /dev/rsa0 blocksize 512. Why it thinks it came up > in variable is a mystery to me. This might be a good QUIRK_FIXED candidate > (when I check the code in) for this f/w- I think other 525's may in fact > support variable (which, IIRC, isn't really variable in that it still has > to be modulo 512). > Many thanks; that's all it took. I can make backups again. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 16:00:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03747 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 16:00:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from proteus.idirect.com (proteus.idirect.com [207.136.80.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03742 for ; Wed, 16 Dec 1998 16:00:29 -0800 (PST) (envelope-from fehr@idirect.com) Received: from localhost (fehr@localhost) by proteus.idirect.com (8.9.1/8.9.1) with ESMTP id TAA13349 for ; Wed, 16 Dec 1998 19:00:57 -0500 (EST) Date: Wed, 16 Dec 1998 19:00:56 -0500 (EST) From: "Eric D. Fehr" To: scsi@FreeBSD.ORG Subject: > 10 SCSI drives, 3.0-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 I'm starting to get fairly frustrated on this one, and have been tearing my hair out on it for some time. Hopefully someone knows an answer. I sure don't. For background, I have a system with 14 18.2GB Seagate drives in it. It has an Adaptec 7890 controller on the motherboard (ASUS P2B-S), and an Adaptec 2940U2W card as well. The drives are split on the channels on the two controllers. The problem is when I attempt to label the drives da10+. So, my question: Does 3.0-RELEASE support > 10 drives??? I can read the label from da9 via: disklabel -r da9 but "disklabel -r da10" gives the following: disklabel: /dev/rda10c: Undefined error: 0 and "disklabel -w da10 auto" gives: disklabel: No space left on device I had to make the nodes by hand for drives da10 and up, here are my entries: brw-r----- 1 root operator 4, 0x00010052 Dec 16 18:10 da10 brw-r----- 1 root operator 4, 80 Dec 16 18:10 da10a brw-r----- 1 root operator 4, 81 Dec 16 18:10 da10b crw-r--r-- 1 root operator 4, 82 Dec 16 18:38 da10c brw-r----- 1 root operator 4, 83 Dec 16 18:10 da10d brw-r----- 1 root operator 4, 84 Dec 16 18:10 da10e brw-r----- 1 root operator 4, 85 Dec 16 18:10 da10f brw-r----- 1 root operator 4, 86 Dec 16 18:10 da10g brw-r----- 1 root operator 4, 87 Dec 16 18:10 da10h brw-r----- 1 root operator 4, 0x00020052 Dec 16 18:10 da10s1 crw-r--r-- 1 root operator 4, 0x00020050 Dec 16 18:32 da10s1a crw-r--r-- 1 root operator 4, 0x00020051 Dec 16 18:32 da10s1b brw-r--r-- 1 root operator 4, 0x00020052 Dec 16 18:19 da10s1c crw-r--r-- 1 root operator 4, 0x00020054 Dec 16 18:32 da10s1e brw-r----- 1 root operator 4, 0x00030052 Dec 16 18:10 da10s2 brw-r----- 1 root operator 4, 0x00040052 Dec 16 18:10 da10s3 brw-r----- 1 root operator 4, 0x00050052 Dec 16 18:10 da10s4 crw-r----- 1 root operator 13, 0x00010052 Dec 16 18:10 rda10 crw-r----- 1 root operator 13, 80 Dec 16 18:10 rda10a crw-r----- 1 root operator 13, 81 Dec 16 18:10 rda10b crw-r----- 1 root operator 13, 82 Dec 16 18:10 rda10c crw-r----- 1 root operator 13, 83 Dec 16 18:10 rda10d crw-r----- 1 root operator 13, 84 Dec 16 18:10 rda10e crw-r----- 1 root operator 13, 85 Dec 16 18:10 rda10f crw-r----- 1 root operator 13, 86 Dec 16 18:10 rda10g crw-r----- 1 root operator 13, 87 Dec 16 18:10 rda10h crw-r----- 1 root operator 13, 0x00020052 Dec 16 18:10 rda10s1 crw-r--r-- 1 root operator 13, 0x00020050 Dec 16 18:37 rda10s1a crw-r--r-- 1 root operator 13, 0x00020051 Dec 16 18:37 rda10s1b brw-r--r-- 1 root operator 13, 0x00020052 Dec 16 18:22 rda10s1c crw-r--r-- 1 root operator 13, 0x00020054 Dec 16 18:37 rda10s1e crw-r----- 1 root operator 13, 0x00030052 Dec 16 18:10 rda10s2 crw-r----- 1 root operator 13, 0x00040052 Dec 16 18:10 rda10s3 crw-r----- 1 root operator 13, 0x00050052 Dec 16 18:10 rda10s4 Here is my uname info: FreeBSD momma.bigmomma.com 3.0-RELEASE FreeBSD 3.0-RELEASE #0: Wed Dec 16 17:36:46 EST 1998 root@momma.bigmomma.com:/usr/src/sys/compile/MOMMA i386 And here is my dmesg info. Note that 4 drives are on the 2940U2W controller U2 interface, 4 on the 7890 U2 interface, and 5 on the 7890 U interface: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #0: Wed Dec 16 17:36:46 EST 1998 root@momma.bigmomma.com:/usr/src/sys/compile/MOMMA Timecounter "i8254" frequency 1193182 Hz cost 3025 ns Timecounter "TSC" frequency 451024723 Hz cost 114 ns CPU: Pentium II (quarter-micron) (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 1073741824 (1048576K bytes) avail memory = 1043206144 (1018756K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x01 int d irq 255 on pci0.4.2 chip4: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 12 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x01 int a irq 12 on pci0.9.0 de0: rev 0x22 int a irq 10 on pci0.10.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:80:c8:58:96:d3 ahc1: rev 0x00 int a irq 11 on pci0.12.0 ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface Waiting 15 seconds for SCSI devices to settle de0: enabling Full Duplex 100baseTX port changing root device to da0s1a da10 at ahc1 bus 0 target 0 lun 0 da10: Fixed Direct Access SCSI2 device da10: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da10: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da13 at ahc1 bus 0 target 13 lun 0 da13: Fixed Direct Access SCSI2 device da13: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da13: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da12 at ahc1 bus 0 target 12 lun 0 da12: Fixed Direct Access SCSI2 device da12: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da12: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da11 at ahc1 bus 0 target 11 lun 0 da11: Fixed Direct Access SCSI2 device da11: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da11: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI2 device da0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da5 at ahc0 bus 0 target 6 lun 0 da5: Fixed Direct Access SCSI2 device da5: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da5: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da4 at ahc0 bus 0 target 5 lun 0 da4: Fixed Direct Access SCSI2 device da4: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da4: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI2 device da3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da2 at ahc0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI2 device da2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da9 at ahc0 bus 0 target 14 lun 0 da9: Fixed Direct Access SCSI2 device da9: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da9: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da8 at ahc0 bus 0 target 10 lun 0 da8: Fixed Direct Access SCSI2 device da8: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da8: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da7 at ahc0 bus 0 target 9 lun 0 da7: Fixed Direct Access SCSI2 device da7: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da7: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da6 at ahc0 bus 0 target 8 lun 0 da6: Fixed Direct Access SCSI2 device da6: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da6: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 16:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10790 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 16:46:59 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt1-202.HiWAAY.net [208.147.147.202]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10779 for ; Wed, 16 Dec 1998 16:46:56 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id SAA91836 for ; Wed, 16 Dec 1998 18:26:19 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199812170026.SAA91836@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Archive Anaconda problems under -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 18:26:18 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aw fiddlesticks, haven't tried my Archive Anaconda since installing 3.0. Its broke too. "mt stat" reports all modes to be 512 byte blocks (so the blocksize command itsn't needed, right? Makes no difference to "mt stat" output). This is what /var/log/messages has to say about an attempt to tar a couple of files to the drive: Dec 16 18:18:07 n4hhe /kernel: (sa1:ahc0:0:6:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 16 18:18:07 n4hhe /kernel: SEQADDR == 0xa Dec 16 18:18:07 n4hhe /kernel: SSTAT1 == 0xa Dec 16 18:18:07 n4hhe /kernel: (sa1:ahc0:0:6:0): Queuing a BDR SCB Dec 16 18:18:07 n4hhe /kernel: (sa1:ahc0:0:6:0): Bus Device Reset Message Sent Dec 16 18:18:07 n4hhe /kernel: (sa1:ahc0:0:6:0): no longer in timeout, status = 34b Dec 16 18:18:07 n4hhe /kernel: ahc0: Bus Device Reset on A:6. 1 SCBs aborted ahc0 is: ahc0: rev 0x00 int a irq 15 on pci0.9.0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs [...] sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.0MB/s transfers (5.0MHz, offset 15) sa1 at ahc0 bus 0 target 6 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 5.0MB/s transfers (5.0MHz, offset 15) only the above two tape drives are on this scsi bus. Kernel sources were fairly close to kernel build date: FreeBSD 3.0-CURRENT #3: Wed Dec 9 21:36:44 CST 1998 dkelly@n4hhe.ampr.org:/usr/src/sys/compile/PPRO213 The Python (sa0) works just fine. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 22:21:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10900 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 22:21:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10894 for ; Wed, 16 Dec 1998 22:20:59 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id HAA29231 for freebsd-scsi@FreeBSD.ORG; Thu, 17 Dec 1998 07:20:50 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id HAA02276; Thu, 17 Dec 1998 07:16:10 +0100 (MET) (envelope-from j) Message-ID: <19981217071608.34321@uriah.heep.sax.de> Date: Thu, 17 Dec 1998 07:16:08 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: New problem with under -current Reply-To: Joerg Wunsch References: <13943.52451.453181.907266@moran.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Matthew Jacob on Wed, Dec 16, 1998 at 08:43:19AM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote: > The write is in variable mode (of all things>. It needs to be in fixed > block mode. Hmm, weird. I thought everything >= QIC 320 would grok variable mode? Apparently not. > (which, IIRC, isn't really variable in that it still has > to be modulo 512). At least for the Tandbergs, it's truely variable. There even seems to be a variable-mode standard for QIC-150, but it's a waste of space (IIRC they're writing another full 512-bytes block per each 512 bytes in order to record variable-length information). Everything >= 320 is documented to allow `true variable' mode there, albeit it will be sliced in blocks of no more than 1024 bytes on the tape. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 22:26:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11584 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 22:26:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11579 for ; Wed, 16 Dec 1998 22:26:19 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id HAA29290; Thu, 17 Dec 1998 07:26:02 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id HAA02264; Thu, 17 Dec 1998 07:13:10 +0100 (MET) (envelope-from j) Message-ID: <19981217071308.02048@uriah.heep.sax.de> Date: Thu, 17 Dec 1998 07:13:08 +0100 From: J Wunsch To: Richard J Kuhns Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: New problem with under -current Reply-To: Joerg Wunsch References: <13943.52451.453181.907266@moran.grauel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <13943.52451.453181.907266@moran.grauel.com>; from Richard J Kuhns on Wed, Dec 16, 1998 at 10:08:19AM -0500 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Richard J Kuhns wrote: > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): WRITE(06). CDB: a 0 0 28 0 0 > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): ILLEGAL REQUEST csi:0,0,80,8 asc:0,13 > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): Audio play operation successfully completed Oh, i'm afraid you can't use an Archive Viper to play audio tapes, can you? :-) (scnr) > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-CCS device > sa0: 3.300MB/s transfers What's ``SCSI-CCS'' here? I've never seen that before. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 23:37:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18509 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 23:37:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18502 for ; Wed, 16 Dec 1998 23:37:26 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id AAA72322; Thu, 17 Dec 1998 00:37:14 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812170737.AAA72322@panzer.plutotech.com> Subject: Re: > 10 SCSI drives, 3.0-RELEASE??? In-Reply-To: from "Eric D. Fehr" at "Dec 16, 98 07:00:56 pm" To: fehr@idirect.com (Eric D. Fehr) Date: Thu, 17 Dec 1998 00:37:14 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 Eric D. Fehr wrote... > I'm starting to get fairly frustrated on this one, and have been tearing > my hair out on it for some time. Hopefully someone knows an answer. I > sure don't. > > For background, I have a system with 14 18.2GB Seagate drives in it. It > has an Adaptec 7890 controller on the motherboard (ASUS P2B-S), and an > Adaptec 2940U2W card as well. The drives are split on the channels on the > two controllers. The problem is when I attempt to label the drives da10+. > So, my question: > > Does 3.0-RELEASE support > 10 drives??? Yes. There's no problem with that. > I can read the label from da9 via: > > disklabel -r da9 > > but "disklabel -r da10" gives the following: > > disklabel: /dev/rda10c: Undefined error: 0 > > and "disklabel -w da10 auto" gives: > > disklabel: No space left on device You're having disklabel trouble. disklabel is such fun. It looks like you're using 'dangerously dedicated' mode. (i.e., no DOS partitions) IIRC, you may need the -r switch. i.e.: disklabel -wr da10 auto Here's a little trick that will blow away whatever is in the first part of the disk: dd if=/dev/zero of=/dev/rda10c bs=64k count=3 Note -- you'd better not have anything important on the disk, that'll blow it away. Then you'll probably want to try something like: disklabel -wr da10 auto I'm not sure that'll work for you, but at least you'll have something to try. Whenever I try to disklabel something, it usually takes a bit of fiddling before I figure out the right incantation to make disklabel work. Another strategy to try (after you've done the dd trick above) if you've got another drive of the same or smaller size is: disklabel da8 > da8.label disklabel -r -R da10 da8.label That will only work if the disk in question is the same size, or smaller than the 'da8' above. Otherwise, you'll get a "no space left on device" error. If you decide to go with a real DOS partition table, you'd just specify things like 'da10s1' instead of 'da10' above. > I had to make the nodes by hand for drives da10 and up, here are my > entries: [ ... ] > And here is my dmesg info. Note that 4 drives are on the 2940U2W > controller U2 interface, 4 on the 7890 U2 interface, and 5 on the 7890 U > interface: > [ ... ] Impressive machine. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 16 23:48:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19615 for freebsd-scsi-outgoing; Wed, 16 Dec 1998 23:48:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19598; Wed, 16 Dec 1998 23:48:05 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id XAA19152; Wed, 16 Dec 1998 23:48:07 -0800 (PST) Message-Id: <199812170748.XAA19152@root.com> To: "Marc G. Fournier" cc: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-reply-to: Your message of "Wed, 16 Dec 1998 11:50:16 -0400." From: David Greenman Reply-To: dg@root.com Date: Wed, 16 Dec 1998 23:48:06 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Wed, 16 Dec 1998, David Greenman wrote: > >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >vnode_pager_putpages: I/O error 6 >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 >> >vnode_pager_putpages: I/O error 6 >> >vnode_pager_putpages: residual I/O 4096 at 113 >> > >> >maybe its totally impossible, but is there no way of detailing which drive >> >is causing this? or is it not a drive? >> >> Error 6 is ENXIO - device not configured. This might happen if the device >> is SCSI and it loses power/goes offline. I can't think of any other reasons >> offhand. > >Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? >The system is locked up right now, awaiting someone to get down to the >office and reboot it. vnode_pager_putpages is a routine, not an error (well...:-)). I don't know what is returning ENXIO, but putpages just calls the filesystem VOP_PUTPAGES entry, so you'd have to look at that. vnode_pager_putpages isn't usually called very often in a typical system - it's used when mapped/modified file pages need to be written back to the backing file, which doesn't normally happen on a typical system (modified pages are usually backed by swap, not the file). >Looking through /usr/src/sys, the error message is generated in >vm/vnode_pager.c...which, to me, would indicate swap space? No, the swap_pager pages out to swap. The vnode_pager pages out to files. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 00:37:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24314 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 00:37:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24309 for ; Thu, 17 Dec 1998 00:37:10 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id AAA13713; Thu, 17 Dec 1998 00:36:47 -0800 Date: Thu, 17 Dec 1998 00:36:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Joerg Wunsch cc: Richard J Kuhns , freebsd-scsi@FreeBSD.ORG Subject: Re: New problem with under -current In-Reply-To: <19981217071308.02048@uriah.heep.sax.de> 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, 17 Dec 1998, J Wunsch wrote: > As Richard J Kuhns wrote: > > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): WRITE(06). CDB: a 0 0 28 0 0 > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): ILLEGAL REQUEST csi:0,0,80,8 asc:0,13 > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): Audio play operation successfully completed > > Oh, i'm afraid you can't use an Archive Viper to play audio tapes, can > you? :-) (scnr) Well, I think this has to do with attempting to interpret ASC/ASCQ on a device that's CCS. > > > sa0 at ahc0 bus 0 target 6 lun 0 > > sa0: Removable Sequential Access SCSI-CCS device > > sa0: 3.300MB/s transfers > > What's ``SCSI-CCS'' here? I've never seen that before. SCSI-1 ANSI X3T10 1986 SCSI-CCS Common Command Set SCSI-2 ANSI X3T10 1994 SCSI-3 "" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 04:15:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17225 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 04:15:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from net.kitel.co.kr (net.kitel.co.kr [210.102.35.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17220 for ; Thu, 17 Dec 1998 04:15:07 -0800 (PST) (envelope-from swjeong@net.kitel.co.kr) Received: (from swjeong@localhost) by net.kitel.co.kr (8.8.8H1/8.8.8) id VAA02458 for freebsd-scsi@FreeBSD.ORG; Thu, 17 Dec 1998 21:14:55 +0900 (KST) Date: Thu, 17 Dec 1998 21:14:55 +0900 (KST) From: swjeong Message-Id: <199812171214.VAA02458@net.kitel.co.kr> To: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panic with ufsspec_write Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here is debug output. www# gdb -aout -k /var/crash/kernel.1 /var/crash/vmcore.1 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 2846720 initial pcb at 24edcc panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor write, page not present instruction pointer = 0x8:0xf01f11dd stack pointer = 0x10:0xf60efeb0 frame pointer = 0x10:0xf60efec0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 293 (rlogin) interrupt mask = panic: from debugger panic: from debugger dumping to dev 20401, offset 393216 dump 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:268 268 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:268 #1 0xf013d930 in panic (fmt=0xf0116138 "from debugger") at ../../kern/kern_shutdown.c:430 #2 0xf0116155 in db_panic (addr=-266399267, have_addr=0, count=1, modif=0xf60efd34 "") at ../../ddb/db_command.c:432 #3 0xf0116035 in db_command (last_cmdp=0xf023a524, cmd_table=0xf023a384, aux_cmd_tablep=0xf024c024) at ../../ddb/db_command.c:332 #4 0xf01161c2 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf01188d3 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xf0207d71 in kdb_trap (type=12, code=0, regs=0xf60efe74) at ../../i386/i386/db_interface.c:157 #7 0xf0212863 in trap_fatal (frame=0xf60efe74) at ../../i386/i386/trap.c:874 #8 0xf021230c in trap_pfault (frame=0xf60efe74, usermode=0) at ../../i386/i386/trap.c:772 #9 0xf0211f5f in trap (frame={tf_es = 16, tf_ds = -65520, tf_edi = -166789380, tf_esi = 8192, tf_ebp = -166789440, tf_isp = -166789476, tf_ebx = -166789312, tf_edx = -1, tf_ecx = 32, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -266399267, tf_cs = 8, tf_eflags = 66183, tf_esp = -166789380, tf_ss = 14}) at ../../i386/i386/trap.c:396 #10 0xf01f11dd in ufsspec_write (ap=0xf60efefc) at ../../ufs/ufs/ufs_vnops.c:1842 #11 0xf01f1705 in ufs_vnoperatespec (ap=0xf60efefc) at ../../ufs/ufs/ufs_vnops.c:2309 #12 0xf0163897 in vn_write (fp=0xf1b89700, uio=0xf60eff40, cred=0xf19b7600) at vnode_if.h:331 #13 0xf0146376 in write (p=0xf603f2c0, uap=0xf60eff94) at ../../kern/sys_generic.c:270 #14 0xf0212b23 in syscall (frame={tf_es = 537395239, tf_ds = -272695257, tf_edi = 537449120, tf_esi = 537442088, tf_ebp = -272639628, tf_isp = -166789148, tf_ebx = 16964, tf_edx = 8192, tf_ecx = -272639648, tf_eax = 4, tf_trapno = 7, tf_err = 7, tf_eip = 537350513, tf_cs = 31, tf_eflags = 518, tf_esp = -272639648, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #15 0x20075171 in ?? () #16 0x1cd9 in ?? () #17 0x1bb4 in ?? () #18 0x1095 in ?? () (kgdb) up ... (kgdb) up #10 0xf01f11dd in ufsspec_write (ap=0xf60efefc) at ../../ufs/ufs/ufs_vnops.c:1842 Source file is more recent than executable. 1842 { (kgdb) l 1842,1863 1837 1838 uio = ap->a_uio; 1839 resid = uio->uio_resid; 1840 1841 if (VTOI(ap->a_vp) == NULL) /* work around */ 1842 { 1843 printf("ufsspec_write would panic at point A\n"); 1844 return EFAULT; 1845 } 1846 1847 error = VOCALL(spec_vnodeop_p, VOFFSET(vop_write), ap); 1848 1849 1850 1851 if (VTOI(ap->a_vp) == NULL) /* work around */ 1852 { 1853 printf("ufsspec_write would panic at point B\n"); 1854 return EFAULT; 1855 } 1857 1858 1859 1860 if (uio->uio_resid != resid) 1861 VTOI(ap->a_vp)->i_flag |= IN_CHANGE | IN_UPDATE; 1862 return (error); 1863 } (kgdb) p *ap->a_vp $1 = {v_flag = 8, v_usecount = 1, v_writecount = 1, v_holdcnt = 0, v_lastr = 0, v_id = 205016, v_mount = 0x0, v_op = 0xf19d4100, v_freelist = { tqe_next = 0x0, tqe_prev = 0xf6145520}, v_mntvnodes = { le_next = 0xf61a5ea0, le_prev = 0xf61a11e8}, v_cleanblkhd = { lh_first = 0x0}, v_dirtyblkhd = {lh_first = 0x0}, v_synclist = { le_next = 0x0, le_prev = 0xf19b7484}, v_numoutput = 0, v_type = VBAD, v_un = {vu_mountedhere = 0x0, vu_socket = 0x0, vu_specinfo = 0x0, vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0, v_cstart = 0, v_lasta = 0, v_clen = 0, v_maxio = 0, v_object = 0x0, v_interlock = {lock_data = 0}, v_vnlock = 0x0, v_tag = VT_NON, v_data = 0x0, v_cache_src = { lh_first = 0x0}, v_cache_dst = {tqh_first = 0x0, tqh_last = 0xf60202fc}, v_dd = 0xf6020280, v_ddid = 0, v_pollinfo = {vpi_lock = {lock_data = 0}, vpi_selinfo = {si_pid = 0, si_flags = 0}, vpi_events = 0, vpi_revents = 0}} (kgdb) Note that v_data is NULL. This caused panic at line 1861 (originaly 1842). I made work around for this panic by putting ap->a_vp->v_data checking. Always point B is excuted and, point A was never executed. During 24 hours, point B was executed 3 times. There was about thirty outgoing rlogin users. And kernel configuration contained 'pseudo-device pty 64'. and there existed corresponding pseudo terminal device. Thanks again, I appreciate your help with this... ----- Jeong Sung-Won swjeong@kitel.co.kr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 06:25:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01821 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 06:25:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01813 for ; Thu, 17 Dec 1998 06:25:13 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA27006; Fri, 18 Dec 1998 01:25:02 +1100 Date: Fri, 18 Dec 1998 01:25:02 +1100 From: Bruce Evans Message-Id: <199812171425.BAA27006@godzilla.zeta.org.au> To: freebsd-scsi@FreeBSD.ORG, swjeong@net.kitel.co.kr Subject: Re: kernel panic with ufsspec_write Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >... >(kgdb) l 1842,1863 >1837 >1838 uio = ap->a_uio; >1839 resid = uio->uio_resid; >1840 >1841 if (VTOI(ap->a_vp) == NULL) /* work around */ >1842 { >1843 printf("ufsspec_write would panic at point A\n"); >1844 return EFAULT; >1845 } >1846 >1847 error = VOCALL(spec_vnodeop_p, VOFFSET(vop_write), ap); >1848 >1849 >1850 >1851 if (VTOI(ap->a_vp) == NULL) /* work around */ >1852 { >1853 printf("ufsspec_write would panic at point B\n"); >1854 return EFAULT; >1855 } >1857 >1858 >1859 >1860 if (uio->uio_resid != resid) >1861 VTOI(ap->a_vp)->i_flag |= IN_CHANGE | IN_UPDATE; >1862 return (error); >1863 } >(kgdb) p *ap->a_vp >$1 = {v_flag = 8, v_usecount = 1, v_writecount = 1, v_holdcnt = 0, > v_lastr = 0, v_id = 205016, v_mount = 0x0, v_op = 0xf19d4100, v_freelist = { > tqe_next = 0x0, tqe_prev = 0xf6145520}, v_mntvnodes = { > le_next = 0xf61a5ea0, le_prev = 0xf61a11e8}, v_cleanblkhd = { > lh_first = 0x0}, v_dirtyblkhd = {lh_first = 0x0}, v_synclist = { > le_next = 0x0, le_prev = 0xf19b7484}, v_numoutput = 0, v_type = VBAD, > v_un = {vu_mountedhere = 0x0, vu_socket = 0x0, vu_specinfo = 0x0, > vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0, v_cstart = 0, v_lasta = 0, > v_clen = 0, v_maxio = 0, v_object = 0x0, v_interlock = {lock_data = 0}, > v_vnlock = 0x0, v_tag = VT_NON, v_data = 0x0, v_cache_src = { > lh_first = 0x0}, v_cache_dst = {tqh_first = 0x0, tqh_last = 0xf60202fc}, > v_dd = 0xf6020280, v_ddid = 0, v_pollinfo = {vpi_lock = {lock_data = 0}, > vpi_selinfo = {si_pid = 0, si_flags = 0}, vpi_events = 0, vpi_revents = 0}} >(kgdb) > >Note that v_data is NULL. This caused panic at line 1861 (originaly 1842). Also note that v_type is VBAD. >I made work around for this panic by putting ap->a_vp->v_data checking. >Always point B is excuted and, point A was never executed. >During 24 hours, point B was executed 3 times. >There was about thirty outgoing rlogin users. And kernel configuration >contained 'pseudo-device pty 64'. and there existed corresponding >pseudo terminal device. This is caused by revoke() of an active device. It is easiest to demonstrate for reads since reads are more likely to block: on ttyv0 on ttyv1 on ttyv2 $ cat /dev/ttypN [waits] $ cat >/dev/ptypN 1 1 % revoke /dev/ttypN [hangs] 2 ["2" is not read -- revoke has partially completed] ^C [panic in ufsspec_read] ddb> set $eip=$eip+4 # fix problem using ddb :-) ddb> continue $ $ $ The vnode is half gone when VOCALL() in ufsspec_READ() returns. revoke() is apparently waiting for it to be fully gone. I think revoke() should do more to attempt to terminate outstanding i/o so that it doesn't block, but your workaround is the correct fix for cases where it does block. I/o routines are apparently supposed to allow for the vnode's fs changing to deadfs underneath them! Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 11:42:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06684 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 11:42:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06669; Thu, 17 Dec 1998 11:42:27 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA03006; Thu, 17 Dec 1998 11:31:04 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdfc3003; Thu Dec 17 19:31:03 1998 Date: Thu, 17 Dec 1998 11:30:59 -0800 (PST) From: Julian Elischer To: David Greenman cc: "Marc G. Fournier" , freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-Reply-To: <199812170748.XAA19152@root.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, 16 Dec 1998, David Greenman wrote: > >On Wed, 16 Dec 1998, David Greenman wrote: > > > >> >vnode_pager_putpages: residual I/O 4096 at 113 > >> >vnode_pager_putpages: I/O error 6 > >> >vnode_pager_putpages: residual I/O 4096 at 113 > >> >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 > >> >vnode_pager_putpages: I/O error 6 > >> >vnode_pager_putpages: residual I/O 4096 at 113 > >> > > >> >maybe its totally impossible, but is there no way of detailing which drive > >> >is causing this? or is it not a drive? > >> > >> Error 6 is ENXIO - device not configured. This might happen if the device > >> is SCSI and it loses power/goes offline. I can't think of any other reasons > >> offhand. > > > >Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? > >The system is locked up right now, awaiting someone to get down to the > >office and reboot it. > > vnode_pager_putpages is a routine, not an error (well...:-)). I don't know > what is returning ENXIO, but putpages just calls the filesystem VOP_PUTPAGES > entry, so you'd have to look at that. vnode_pager_putpages isn't usually > called very often in a typical system - it's used when mapped/modified file > pages need to be written back to the backing file, which doesn't normally > happen on a typical system (modified pages are usually backed by swap, not > the file). > > >Looking through /usr/src/sys, the error message is generated in > >vm/vnode_pager.c...which, to me, would indicate swap space? > > No, the swap_pager pages out to swap. The vnode_pager pages out to files. I THINK the vnode pager is called if you are writing to a mmapped file, right? > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > 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 Thu Dec 17 11:53:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08540 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 11:53:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08510; Thu, 17 Dec 1998 11:53:17 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id LAA25533; Thu, 17 Dec 1998 11:52:59 -0800 (PST) Message-Id: <199812171952.LAA25533@root.com> To: Julian Elischer cc: "Marc G. Fournier" , freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-reply-to: Your message of "Thu, 17 Dec 1998 11:30:59 PST." From: David Greenman Reply-To: dg@root.com Date: Thu, 17 Dec 1998 11:52:59 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >> >vnode_pager_putpages: I/O error 6 >> >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >> >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 >> >> >vnode_pager_putpages: I/O error 6 >> >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >> > >> >> >maybe its totally impossible, but is there no way of detailing which drive >> >> >is causing this? or is it not a drive? >> >> >> >> Error 6 is ENXIO - device not configured. This might happen if the device >> >> is SCSI and it loses power/goes offline. I can't think of any other reasons >> >> offhand. >> > >> >Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? >> >The system is locked up right now, awaiting someone to get down to the >> >office and reboot it. >> >> vnode_pager_putpages is a routine, not an error (well...:-)). I don't know >> what is returning ENXIO, but putpages just calls the filesystem VOP_PUTPAGES >> entry, so you'd have to look at that. vnode_pager_putpages isn't usually >> called very often in a typical system - it's used when mapped/modified file >> pages need to be written back to the backing file, which doesn't normally >> happen on a typical system (modified pages are usually backed by swap, not >> the file). >> >> >Looking through /usr/src/sys, the error message is generated in >> >vm/vnode_pager.c...which, to me, would indicate swap space? >> >> No, the swap_pager pages out to swap. The vnode_pager pages out to files. > >I THINK the vnode pager is called if you are writing to a mmapped file, >right? Yes, if it is mapped shared and writable. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 20:13:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11126 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 20:13:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11121 for ; Thu, 17 Dec 1998 20:13:29 -0800 (PST) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [205.252.239.241]) by tasam.com (8.9.1/8.9.1) with SMTP id XAA25739 for ; Thu, 17 Dec 1998 23:13:18 -0500 (EST) Message-ID: <006f01be2a3c$bbd056b0$f1effccd@bug.tasam.com> From: "Joe Gleason" To: Subject: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 Date: Thu, 17 Dec 1998 23:13:12 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="x-user-defined" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently got this in my security check output log: > Direct Access SCSI3 device > (da0:ahc1:0:5:0): WRITE(06). CDB: a 0 0 7f 10 0 > (da0:ahc1:0:5:0): HARDWARE FAILURE asc:44,0 > (da0:ahc1:0:5:0): Internal target failure field replaceable unit: 1 Is is something I should worry about? Here is the relavent part of my dmesg: ahc0 rev 4 int a irq 12 on pci0:20:0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1 rev 4 int b irq 11 on pci0:20:1 ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs Sending WDTR! (probe20:ahc1:0:5:0): Sending SDTR!! da0 at ahc1 bus 0 target 5 lun 0 da0: Fixed Direct Access SCSI3 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) I just have the one scsi device. Joe Gleason Tasam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 20:38:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15086 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 20:38:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15081 for ; Thu, 17 Dec 1998 20:38:27 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id UAA21637; Thu, 17 Dec 1998 20:37:58 -0800 Date: Thu, 17 Dec 1998 20:37:58 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Joe Gleason cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 In-Reply-To: <006f01be2a3c$bbd056b0$f1effccd@bug.tasam.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 F/W crash of sorts? Does it really report itself as a SCSI-3 device? How interesting...I don't really have a good answer, but yes, I'd worry about it. Usually you only see these kinds of crocks on tape drives (SDT 5000s had them a lot). Has it happened more than once? On Thu, 17 Dec 1998, Joe Gleason wrote: > I recently got this in my security check output log: > > > Direct Access SCSI3 device > > (da0:ahc1:0:5:0): WRITE(06). CDB: a 0 0 7f 10 0 > > (da0:ahc1:0:5:0): HARDWARE FAILURE asc:44,0 > > (da0:ahc1:0:5:0): Internal target failure field replaceable unit: 1 > > Is is something I should worry about? > > Here is the relavent part of my dmesg: > > ahc0 rev 4 int a irq 12 on pci0:20:0 > ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1 rev 4 int b irq 11 on pci0:20:1 > ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs > > Sending WDTR! > (probe20:ahc1:0:5:0): Sending SDTR!! > da0 at ahc1 bus 0 target 5 lun 0 > da0: Fixed Direct Access SCSI3 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > > I just have the one scsi device. > > Joe Gleason > Tasam > > > 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 Thu Dec 17 20:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15166 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 20:38:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15159 for ; Thu, 17 Dec 1998 20:38:45 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA78249; Thu, 17 Dec 1998 21:38:22 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812180438.VAA78249@panzer.plutotech.com> Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 In-Reply-To: <006f01be2a3c$bbd056b0$f1effccd@bug.tasam.com> from Joe Gleason at "Dec 17, 98 11:13:12 pm" To: clash@tasam.com (Joe Gleason) Date: Thu, 17 Dec 1998 21:38:22 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 Joe Gleason wrote... > I recently got this in my security check output log: > > > Direct Access SCSI3 device > > (da0:ahc1:0:5:0): WRITE(06). CDB: a 0 0 7f 10 0 > > (da0:ahc1:0:5:0): HARDWARE FAILURE asc:44,0 > > (da0:ahc1:0:5:0): Internal target failure field replaceable unit: 1 > > Is is something I should worry about? In general, yes, you should worry about it. I would keep a close eye on the drive. Look for any more error messages. If you keep getting error messages, you may want to call IBM and inquire about it. They may be able to tell you what part of the drive "field replaceable unit 1" is. If they would put their manuals on their web site like Quantum and Seagate, you might be able to find out for yourself. > Here is the relavent part of my dmesg: > > ahc0 rev 4 int a irq 12 on pci0:20:0 > ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1 rev 4 int b irq 11 on pci0:20:1 > ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs > > Sending WDTR! > (probe20:ahc1:0:5:0): Sending SDTR!! > da0 at ahc1 bus 0 target 5 lun 0 > da0: Fixed Direct Access SCSI3 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > > I just have the one scsi device. You might want to check and see if it is running too hot. Here's a script that might do that, depending on whether your firmware supports it. (I've tried it on the 18G version of that drive, with firmware version 03B0, and it works fine.) ======================================== #!/bin/ksh TEMPC=`camcontrol cmd -n da -u 1 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` echo "The temperature is: $TEMPF F" ======================================== I think the default temperature threshold (before it starts spewing errors) is 60C. Ideally, though, you'll want to run a good bit cooler than that. You'll need to change the '-u 1' above to '-u 0' for your drive. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 21:17:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18880 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 21:17:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18875 for ; Thu, 17 Dec 1998 21:17:01 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA78573; Thu, 17 Dec 1998 22:16:43 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812180516.WAA78573@panzer.plutotech.com> Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 In-Reply-To: from Matthew Jacob at "Dec 17, 98 08:37:58 pm" To: mjacob@feral.com Date: Thu, 17 Dec 1998 22:16:43 -0700 (MST) Cc: clash@tasam.com, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 Matthew Jacob wrote... > On Thu, 17 Dec 1998, Joe Gleason wrote: > > (probe20:ahc1:0:5:0): Sending SDTR!! > > da0 at ahc1 bus 0 target 5 lun 0 > > da0: Fixed Direct Access SCSI3 device > > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > > > > I just have the one scsi device. > > F/W crash of sorts? Does it really report itself as a SCSI-3 device? How > interesting...I don't really have a good answer, but yes, I'd worry about > it. Usually you only see these kinds of crocks on tape drives (SDT 5000s > had them a lot). It really does report itself as a SCSI-3 device. I've got an Ultrastar 9ZX that reports itself as SCSI-3: da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI3 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8705MB (17829870 512 byte sectors: 255H 63S/T 1109C) And the 18G version of the drive he has reports itself as SCSI-3 as well. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 17 21:19:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19192 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 21:19:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19185 for ; Thu, 17 Dec 1998 21:19:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id VAA21788; Thu, 17 Dec 1998 21:19:08 -0800 Date: Thu, 17 Dec 1998 21:19:08 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: clash@tasam.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 In-Reply-To: <199812180516.WAA78573@panzer.plutotech.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 Well, if that's the case, it's time for me to get off my ass and start merging in the SES driver and start thinking about lots more SCSI-3 things.... On Thu, 17 Dec 1998, Kenneth D. Merry wrote: > Matthew Jacob wrote... > > On Thu, 17 Dec 1998, Joe Gleason wrote: > > > (probe20:ahc1:0:5:0): Sending SDTR!! > > > da0 at ahc1 bus 0 target 5 lun 0 > > > da0: Fixed Direct Access SCSI3 device > > > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > > da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > > > > > > I just have the one scsi device. > > > > F/W crash of sorts? Does it really report itself as a SCSI-3 device? How > > interesting...I don't really have a good answer, but yes, I'd worry about > > it. Usually you only see these kinds of crocks on tape drives (SDT 5000s > > had them a lot). > > It really does report itself as a SCSI-3 device. I've got an Ultrastar 9ZX > that reports itself as SCSI-3: > > da1 at ahc1 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI3 device > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 8705MB (17829870 512 byte sectors: 255H 63S/T 1109C) > > And the 18G version of the drive he has reports itself as SCSI-3 as well. > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 18 10:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12603 for freebsd-scsi-outgoing; Fri, 18 Dec 1998 10:46:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12576 for ; Fri, 18 Dec 1998 10:46:11 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id TAA18178; Fri, 18 Dec 1998 19:45:57 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA22362 (5.67b/IDA-1.5); Fri, 18 Dec 1998 19:19:06 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id SAA01874; Fri, 18 Dec 1998 18:46:00 +0100 (CET) From: Wilko Bulte Message-Id: <199812181746.SAA01874@yedi.iaf.nl> Subject: Re: New problem with under -current In-Reply-To: <19981217071308.02048@uriah.heep.sax.de> from J Wunsch at "Dec 17, 98 07:13:08 am" To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 18 Dec 1998 18:46:00 +0100 (CET) Cc: rjk@grauel.com, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] 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 As J Wunsch wrote... > As Richard J Kuhns wrote: > > sa0 at ahc0 bus 0 target 6 lun 0 > > sa0: Removable Sequential Access SCSI-CCS device Hmm. FYI: Viper 2525 have seen a considerable number of different F/W versions. I was glad to have sold mine. > > sa0: 3.300MB/s transfers > > What's ``SCSI-CCS'' here? I've never seen that before. CCS = common command set (I think) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 18 10:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12617 for freebsd-scsi-outgoing; Fri, 18 Dec 1998 10:46:22 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12598 for ; Fri, 18 Dec 1998 10:46:18 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id TAA18186; Fri, 18 Dec 1998 19:46:04 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA22356 (5.67b/IDA-1.5); Fri, 18 Dec 1998 19:19:04 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id SAA01825; Fri, 18 Dec 1998 18:41:12 +0100 (CET) From: Wilko Bulte Message-Id: <199812181741.SAA01825@yedi.iaf.nl> Subject: Re: New problem with under -current In-Reply-To: from Matthew Jacob at "Dec 17, 98 00:36:47 am" To: mjacob@feral.com Date: Fri, 18 Dec 1998 18:41:12 +0100 (CET) Cc: joerg_wunsch@uriah.heep.sax.de, rjk@grauel.com, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] 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 As Matthew Jacob wrote... > > > On Thu, 17 Dec 1998, J Wunsch wrote: > > > As Richard J Kuhns wrote: > > > > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): WRITE(06). CDB: a 0 0 28 0 0 > > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): ILLEGAL REQUEST csi:0,0,80,8 asc:0,13 > > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): Audio play operation successfully completed > > > > Oh, i'm afraid you can't use an Archive Viper to play audio tapes, can > > you? :-) (scnr) Hmm. Assuming the right data is on the tape 'dd if=/dev/rst0 of=/dev/audio" should work ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 18 10:51:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13223 for freebsd-scsi-outgoing; Fri, 18 Dec 1998 10:51:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13215 for ; Fri, 18 Dec 1998 10:51:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA24177; Fri, 18 Dec 1998 10:51:06 -0800 Date: Fri, 18 Dec 1998 10:51:06 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Wilko Bulte cc: freebsd-scsi@FreeBSD.ORG Subject: Re: New problem with under -current In-Reply-To: <199812181741.SAA01825@yedi.iaf.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 Fri, 18 Dec 1998, Wilko Bulte wrote: > As Matthew Jacob wrote... > > > > > > On Thu, 17 Dec 1998, J Wunsch wrote: > > > > > As Richard J Kuhns wrote: > > > > > > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): WRITE(06). CDB: a 0 0 28 0 0 > > > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): ILLEGAL REQUEST csi:0,0,80,8 asc:0,13 > > > > Dec 16 10:00:04 moran /kernel: (sa0:ahc0:0:6:0): Audio play operation successfully completed > > > > > > Oh, i'm afraid you can't use an Archive Viper to play audio tapes, can > > > you? :-) (scnr) > > Hmm. Assuming the right data is on the tape 'dd if=/dev/rst0 of=/dev/audio" > should work ;-) Yeah- it's too bad nobody will tell us what the magic commands to ship to the SGI f/w Python DAT drives so we can fetch DAT audio... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 18 13:15:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02762 for freebsd-scsi-outgoing; Fri, 18 Dec 1998 13:15:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02754 for ; Fri, 18 Dec 1998 13:15:41 -0800 (PST) (envelope-from searle@longacre.demon.co.uk) Received: from [158.152.156.24] (helo=longacre.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.10 #1) id 0zr7F0-0007l9-00; Fri, 18 Dec 1998 21:15:18 +0000 Date: Fri, 18 Dec 1998 21:05:41 +0000 (GMT) From: Michael Searle Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <199812180438.VAA78249@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Organization: Who, me? X-Mailer: ANT RISCOS Marcel [ver 1.46] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri 18 Dec, Kenneth D. Merry wrote: > > You might want to check and see if it is running too hot. Here's a script > that might do that, depending on whether your firmware supports it. (I've > tried it on the 18G version of that drive, with firmware version 03B0, and > it works fine.) > > ======================================== > #!/bin/ksh > > TEMPC=`camcontrol cmd -n da -u 1 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` > > TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` > > echo "The temperature is: $TEMPF F" > ======================================== > > I think the default temperature threshold (before it starts spewing errors) > is 60C. Ideally, though, you'll want to run a good bit cooler than that. > > You'll need to change the '-u 1' above to '-u 0' for your drive. > > Ken Is this a general SCSI command that could be used on anything, or specific to IBM drives / that model? Mike -- csubl@csv.warwick.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 18 14:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12270 for freebsd-scsi-outgoing; Fri, 18 Dec 1998 14:41:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12264 for ; Fri, 18 Dec 1998 14:41:34 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA81790; Fri, 18 Dec 1998 15:41:22 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812182241.PAA81790@panzer.plutotech.com> Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 In-Reply-To: from Michael Searle at "Dec 18, 98 09:05:41 pm" To: searle@longacre.demon.co.uk (Michael Searle) Date: Fri, 18 Dec 1998 15:41:22 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] 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 Michael Searle wrote... > On Fri 18 Dec, Kenneth D. Merry wrote: > > > > > You might want to check and see if it is running too hot. Here's a script > > that might do that, depending on whether your firmware supports it. (I've > > tried it on the 18G version of that drive, with firmware version 03B0, and > > it works fine.) > > > > ======================================== > > #!/bin/ksh > > > > TEMPC=`camcontrol cmd -n da -u 1 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` > > > > TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` > > > > echo "The temperature is: $TEMPF F" > > ======================================== > > > > I think the default temperature threshold (before it starts spewing errors) > > is 60C. Ideally, though, you'll want to run a good bit cooler than that. > > > > You'll need to change the '-u 1' above to '-u 0' for your drive. > > > > Ken > > Is this a general SCSI command that could be used on anything, or specific to > IBM drives / that model? It is specific to certain firmware revisions of certain IBM drives that have on-board temperature sensors. (No, I don't know which firmware revisions. You'll have to try it and find out, if your drive has a temperature sensor.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 18 15:12:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17052 for freebsd-scsi-outgoing; Fri, 18 Dec 1998 15:12:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17047 for ; Fri, 18 Dec 1998 15:12:37 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id AAA07237 for freebsd-scsi@FreeBSD.ORG; Sat, 19 Dec 1998 00:12:21 +0100 (CET) (envelope-from olli) Date: Sat, 19 Dec 1998 00:12:21 +0100 (CET) From: Oliver Fromme Message-Id: <199812182312.AAA07237@dorifer.heim3.tu-clausthal.de> To: freebsd-scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM Newsgroups: list.freebsd-scsi Organization: Administration Heim 3 Reply-To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Max Khon wrote in list.freebsd-scsi: > > That's really strange. That file size is neither a multiple of > > 512 nor of 2352 (the "red book" sector size). > > Do those files contain correct audio data, or are they garbage > > (silence, white noise or whatever)? > > you forgot 44 bytes of .wav header Well, I didn't know that you were using a "hacked" version of tosha. Of course, I can't provide support for that. I'd recommend that you try tosha-current which contains regular support for WAV (and other formats). Can you answer my question about the file contents, please? > > You could try to checkout tosha-current, as I explained in the > > previous posting in this thread on the freebsd-scsi list, but I > > doubt that it has anything to do with your problem. > > where can i get it? (cvsup, ftp, anything else) Please see http://www.fromme.com/tosha/ I have also tarred up the current source tree (as of the time of this writing; this is not guaranteed to be up-to-date): http://www.fromme.com/tosha-current.tar.gz Note that the manual page hasn't been updated yet, but "tosha -h" should get you going. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 19 22:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09545 for freebsd-scsi-outgoing; Sat, 19 Dec 1998 22:42:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09535 for ; Sat, 19 Dec 1998 22:42:55 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sun, 20 Dec 1998 01:42:52 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sat, 19 Dec 1998 22:42:50 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 20 Dec 1998 01:42:49 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG Cc: harlan@pfcs.com Subject: Problem with Amanda backups to 4mm tape X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 01:42:49 -0500 Message-ID: <29914.914136169@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (If this belongs on another list, please let me know.) I have a system that I've been using for amanda backups of my network for a couple of years. It's currently running 2.2.8-STABLE and amanda-2.4.1p1. As of a few months ago, I have been unable to get 1 local and 1 remote filesystem to back up to tape on this machine. If I do a simple "dump" of the problem local filesystem to tape, it works. I have tried backing up these two filesystems using almost all combinations of (no) holding disk / (no) compression. I've cleaned the heads and tried a number of fresh new tapes. Anyway, I get the following message upon failure: Dec 19 22:10:57 pcfb1 /kernel: st1(ahc0:5:0): Target Busy Dec 19 22:10:57 pcfb1 last message repeated 5 times dmesg for the SCSI stuff is: ahc0 rev 0 int a irq 11 on pci0:10:0 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "TOSHIBA MK537FB/ 6258" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1015MB (2079838 512 byte sectors) (ahc0:3:0): "SEAGATE SX410800N 7102" type 0 fixed SCSI 2 sd1(ahc0:3:0): Direct-Access 8347MB (17096357 512 byte sectors) (ahc0:5:0): "ARCHIVE Python 28388-XXX 4.98" type 1 removable SCSI 2 st1(ahc0:5:0): Sequential-Access density code 0x13, drive empty (ahc0:6:0): "TOSHIBA CD-ROM XM-3501TA 3384" type 5 removable SCSI 2 cd0(ahc0:6:0): CD-ROM can't get the size The tape drive is last on the chain and is internally terminated (active, as I recall). Any ideas? I'd really like to get all of my backups working cleanly again. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message