From owner-freebsd-hardware Wed Jan 1 7: 8:50 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B879937B401 for ; Wed, 1 Jan 2003 07:08:49 -0800 (PST) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F062443E4A for ; Wed, 1 Jan 2003 07:08:48 -0800 (PST) (envelope-from mike@sentex.net) Received: from house.sentex.net (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.12.6/8.12.6) with ESMTP id h01F8fCv023907; Wed, 1 Jan 2003 10:08:41 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030101100748.06da5d00@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 01 Jan 2003 10:08:42 -0500 To: Bruce Campbell From: Mike Tancsa Subject: Re: ata "fallback to PIO mode" on dual processor AMD systems Cc: freebsd-hardware@freebsd.org In-Reply-To: <1041390091.3e125a0b19c58@www.nexusmail.uwaterloo.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 10:01 PM 12/31/2002 -0500, Bruce Campbell wrote: > > show ? Do you have tags enabled ? > >hw.ata.tags: 0 > >are tags a good thing ? In theory yes, in practice... I would strongly avoid them on ATA devices. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 1 7:25:49 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DF4837B401 for ; Wed, 1 Jan 2003 07:25:48 -0800 (PST) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B2BC43EB2 for ; Wed, 1 Jan 2003 07:25:47 -0800 (PST) (envelope-from mike@sentex.net) Received: from house.sentex.net (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.12.6/8.12.6) with ESMTP id h01FPiCv025914; Wed, 1 Jan 2003 10:25:45 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030101100848.024838f0@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 01 Jan 2003 10:25:46 -0500 To: Bruce Campbell From: Mike Tancsa Subject: Re: ata "fallback to PIO mode" on dual processor AMD systems Cc: freebsd-hardware@freebsd.org In-Reply-To: <1041390502.3e125ba66487e@www.nexusmail.uwaterloo.ca> References: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> <025701c2b112$ddfbf580$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 10:08 PM 12/31/2002 -0500, Bruce Campbell wrote: >atapci0: port 0xb800-0xb80f at device 7.1 on pci0 > >The removeable drive bays use a short piece of 80 conductor cable to go >from a large centronics type connector to the drive. Maybe it is >a stub matching problem. The boxes that these enclosures came in >had a sticker which said "UDMA33/66/100" but under the sticker it >just said "UDMA33/66". Maybe I was ripped off. It could be the problem although I am not sure if there are any cabling differences between 66 and 100. Its quite possible the manufacturer just updated the sticker on the boxes to reflect that the drives "now work with ATA100" where as in fact they always did. Should be easy enough to verify if you run the drives without the trays. I buy trays locally from CCC (180 Columbia). They (Startech branded) are not high end by any stretch of the imagination, but they will work at UDMA100 and we use quite a few. BTW, I have been running the same MB with great results so far. Two 2000MPs. The primary drives are off a 3ware card, but there is one IDE drive that holds all the logging from a rather busy web server. CPU: AMD Athlon(TM) MP 2000+ (1666.74-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480000<,AMIE,DSP,3DNow!> real memory = 1073741824 (1048576K bytes) config> q avail memory = 1041698816 (1017284K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 atapci0: port 0xb800-0xb80f at device 7.1 on pci0 During busy times the drive gets brutalized as it gets a nightly dump of /home which pushes the all out drive. Like I said, no problems since we commissioned the machine back in October. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 4: 7:56 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0450837B405 for ; Thu, 2 Jan 2003 04:07:56 -0800 (PST) Received: from hal-4.inet.it (hal-4.inet.it [213.92.5.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C339843EC2 for ; Thu, 2 Jan 2003 04:07:54 -0800 (PST) (envelope-from kim@ngi.it) Received: from [::ffff:80.206.34.157] by hal-4.inet.it via I-SMTP-4.3.4-430 id ::ffff:80.206.34.157+i09BCcKuph0; Thu, 02 Jan 2003 13:07:53 +0100 Message-ID: <3E142BAB.9010105@ngi.it> Date: Thu, 02 Jan 2003 13:08:11 +0100 From: Mirko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20030101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: audigy support? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all. Is there a possibility to use audigy sound card with freebsd 5.0? Emu10k1.c fully support sound blaster live series but audigy support has been disabled (commented out). Can anyone help me? Thanks in advance Mirko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 8:38:27 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A781237B401 for ; Thu, 2 Jan 2003 08:38:22 -0800 (PST) Received: from mail.tiscali.it (mail-8.tiscali.it [195.130.225.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2059543EC5 for ; Thu, 2 Jan 2003 08:38:21 -0800 (PST) (envelope-from fcasadei@inwind.it) Received: from goku.kasby (217.133.211.64) by mail.tiscali.it (6.5.032) id 3E00A1FE008805BA for freebsd-hardware@freebsd.org; Thu, 2 Jan 2003 17:38:19 +0100 Received: (qmail 2870 invoked by uid 1000); 2 Jan 2003 16:38:12 -0000 Date: Thu, 2 Jan 2003 17:38:12 +0100 From: Francesco Casadei To: Bruce Campbell Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ata "fallback to PIO mode" on dual processor AMD systems Message-ID: <20030102163812.GA2350@goku.kasby> Mail-Followup-To: Bruce Campbell , freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org References: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.7-STABLE i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 31, 2002 at 03:57:16PM -0500, Bruce Campbell wrote: >=20 > I am seeing a problem with ata disks on 4 new systems, which > I believe is either a bug in the ata driver, or a problem with > the onboard IDE controller, or something else. Systems are as follows: >=20 > Motherboard: ASUS A7M266-D > CPUs : 2 x 2000+ AMD MP > Memory : 2 x 512MB Crucial part: CT6472Y265 >=20 > Disks (all UDMA100): >=20 > Master Slave > System 1: WDC WD400BB WDC WD1000BB > System 2: WDC WD400BB WDC WD1000BB > System 3: WDC WD400BB WDC WD800BB > System 4: WDC WD400BB Maxtor 98196H8 >=20 > Kernel : 4.7-RELEASE, custom kernel (compared to GENERIC): >=20 > commented out: >=20 > cpu I386_CPU > cpu I486_CPU >=20 > enabled=20 >=20 > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O >=20 >=20 > I am running a test with "dbench" (/usr/ports/benchmarks/dbench) > with a script which runs: >=20 > dbench 1 > sleep for 5 minutes > dbench 2 > sleep for 5 minutes > dbench 3 > ... >=20 > to simulate 1,2,3... clients. >=20 > The following has happened on systems 2,3 and 4, after about 15 hours > of running the test: >=20 > Dec 30 23:26:59 ecserv13 /kernel: ad0: WRITE command timeout tag=3D0 serv= =3D0 - > resetting > Dec 30 23:26:59 ecserv13 /kernel: ata0: resetting devices .. done > Dec 30 23:26:59 ecserv13 /kernel: ad0: WRITE command timeout tag=3D0 serv= =3D0=20 > resetting > Dec 30 23:27:00 ecserv13 /kernel: ata0: resetting devices .. done > Dec 30 23:27:00 ecserv13 /kernel: ad0: WRITE command timeout tag=3D0 serv= =3D0=20 > resetting > Dec 30 23:27:00 ecserv13 /kernel: ata0: resetting devices .. done > Dec 30 23:27:00 ecserv13 /kernel: ad0: WRITE command timeout tag=3D0 serv= =3D0=20 > resetting > Dec 30 23:27:00 ecserv13 /kernel: ad0: timeout waiting for cmd=3Def s=3Dd= 0 e=3D00 > Dec 30 23:27:00 ecserv13 /kernel: ad0: trying fallback to PIO mode > Dec 30 23:27:00 ecserv13 /kernel: ata0: resetting devices .. done >=20 > The test continues to run with the ata controller in PIO mode, with > slower performance, and higher load average. >=20 > Once the master drops to PIO, attempts to access the slave then cause > it to drop to PIO. >=20 > If I run: >=20 > atacontrol mode 0 UDMA100 UDMA100 >=20 > attempts to access either drive result in a delay until the controller > drops to PIO, and then operations resume. A soft reboot and things > work in UDMA mode again. Also tried UDMA33 and UDMA66 with no change. > I also tried "atacontrol reinit 0" with no help. >=20 > Theories when I search the web for "fallback to PIO mode" include: >=20 > - bad disks > - something to do with thermal recalibration >=20 > I don't believe the problems are bad disks, as the slave drops to PIO > after the master does, and I can't get in back to UDMA, other than by > soft reboot. Plus I see the problem on 6 of 8 disks. >=20 > The problem is very repeatable. >=20 > Can anyone offer any ideas, or suggest investigative steps ? I have a sy= stem > in PIO mode right now. >=20 > Thanks, >=20 > --=20 > Bruce Campbell > Engineering Computing > CPH-2374B > University of Waterloo > (519)888-4567 ext 5889 >=20 > ---------------------------------------- > This mail sent through www.mywaterloo.ca >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message >=20 > end of the original message Same problem here, but slightly different configuration: # atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI rev 0 Slave: no device present ATA channel 2: Master: ad4 ATA/ATAPI rev 5 Slave: no device present ATA channel 3: Master: ad6 ATA/ATAPI rev 5 Slave: no device present ad4 and ad6 are attached to a Promise FastTrak 100 TX2 ATA RAID controller. # atacontrol mode 0 Master =3D UDMA100=20 Slave =3D ??? # atacontrol mode 1 Master =3D PIO4=20 Slave =3D ??? # atacontrol mode 2 Master =3D UDMA100=20 Slave =3D ??? # atacontrol mode 3 Master =3D PIO4=20 Slave =3D ??? ad6 falls back to PIO mode on heavy I/O activity, i.e. when the system does= a level 0 file systems dump from the RAID 1 array (ad4,ad6) to the backup disk ad0. Rebooting and rebuilding the array with the Promise BIOS utility temporarily solve the problem. The system may be up and running for 1-4 weeks doing a level 0 dump every morning at 5:30am and then one day the drive ad6 falls b= ack to PIO mode again (little before the completion of fs dump). Do the hard drives you are using support the ATA tagged queuing? And if so,= do you have TQ enbled? Francesco Casadei --=20 You can download my public key from http://digilander.libero.it/fcasadei/ or retrieve it from a keyserver (pgpkeys.mit.edu, wwwkeys.pgp.net, ...) Key fingerprint is: 1671 9A23 ACB4 520A E7EE 00B0 7EC3 375F 164E B17B --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+FGr0fsM3XxZOsXsRAlInAKDb4DiO9vSpMBJnmfRnS3v+qtTs+ACg0EZG BvkLn2Sdg7cpD6KSWoxsYRA= =sE+F -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 8:54:30 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4D9837B401; Thu, 2 Jan 2003 08:54:28 -0800 (PST) Received: from level.uwaterloo.ca (level.uwaterloo.ca [129.97.50.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id D25DF43EC2; Thu, 2 Jan 2003 08:54:27 -0800 (PST) (envelope-from bruce@engmail.uwaterloo.ca) Received: from level.uwaterloo.ca (localhost [127.0.0.1]) by level.uwaterloo.ca (8.12.3/8.12.3) with ESMTP id h02Gr45n068856; Thu, 2 Jan 2003 11:53:04 -0500 (EST) (envelope-from bruce@engmail.uwaterloo.ca) Received: (from www@localhost) by level.uwaterloo.ca (8.12.3/8.12.3/Submit) id h02Gr4U4068855; Thu, 2 Jan 2003 11:53:04 -0500 (EST) X-Authentication-Warning: level.uwaterloo.ca: www set sender to bruce@engmail.uwaterloo.ca using -f Received: from 129.97.50.50 ( [129.97.50.50]) as user bruce@engmail.uwaterloo.ca by www.nexusmail.uwaterloo.ca with HTTP; Thu, 2 Jan 2003 11:53:04 -0500 Message-ID: <1041526384.3e146e708b8e4@www.nexusmail.uwaterloo.ca> Date: Thu, 2 Jan 2003 11:53:04 -0500 From: Bruce Campbell To: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Followup to "fallback to PIO mode" on dual processor AMD systems References: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> <025701c2b112$ddfbf580$1200a8c0@gsicomp.on.ca> <5.2.0.9.0.20030101100848.024838f0@192.168.0.12> In-Reply-To: <5.2.0.9.0.20030101100848.024838f0@192.168.0.12> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 / FreeBSD-4.6.2 X-Originating-IP: 129.97.50.50 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org By the way, I've determined our removable IDE disk trays are manufactured by SNT (http://www.snt.com.tw/metal.htm) and are part number SNT-129. It looks like these are the same ones startech sells. I've placed my hardware configuration here: http://www.freebsd.uwaterloo.ca/twiki/bin/view/Freebsd/DualAmd2000 Out of my 4 AMD systems, my test results are now: - 1 refuses to die - 1 panic'ed and died, after not being able to drop to PIO. Many fsck errors upon reboot. The console error was "ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device" - 2 dropped to PIO after about 15 hours of tests, and ran fine (but slowly) with PIO As for the the 2 that dropped to PIO and worked, I rebooted and manually ran atacontrol mode 0 UDMA33 UDMA33 and restarted the tests. No problems in 36 hours so far. My 4 Intel systems (which only have a UDMA33 controller on the motherboard) have also been running 48 hours no problems. The test I run is... dbench 1 sleep 300 dbench 2 sleep 300 dbench 3 ... up to about "dbench 80" and then I kill and restart. With UDMA100, "dbench 10" gave 43 MB/Sec With UDMA33, "dbench 10" gives 37 MB/Sec I still plan to: - try UDMA100 with the drives directly attached (ie. no removable tray) - maybe try a non onboard IDE controller - shuffle the disks to see if the problems follow the disks or not At present, I don't suspect bad media because the error message is "WRITE command timeout tag=0 serv=0" which doesn't suggest a specific sector/track etc, and running with UDMA33 instead of UDMA100 makes the problem appear to vanish. ---------------------------------------- This mail sent through www.mywaterloo.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 10:43:31 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 985BC37B47C; Thu, 2 Jan 2003 10:43:27 -0800 (PST) Received: from level.uwaterloo.ca (level.uwaterloo.ca [129.97.50.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB1943EA9; Thu, 2 Jan 2003 10:43:26 -0800 (PST) (envelope-from bruce@engmail.uwaterloo.ca) Received: from level.uwaterloo.ca (localhost [127.0.0.1]) by level.uwaterloo.ca (8.12.3/8.12.3) with ESMTP id h02Ig35n071399; Thu, 2 Jan 2003 13:42:03 -0500 (EST) (envelope-from bruce@engmail.uwaterloo.ca) Received: (from www@localhost) by level.uwaterloo.ca (8.12.3/8.12.3/Submit) id h02Ig3ka071398; Thu, 2 Jan 2003 13:42:03 -0500 (EST) X-Authentication-Warning: level.uwaterloo.ca: www set sender to bruce@engmail.uwaterloo.ca using -f Received: from 129.97.50.50 ( [129.97.50.50]) as user bruce@engmail.uwaterloo.ca by www.nexusmail.uwaterloo.ca with HTTP; Thu, 2 Jan 2003 13:42:03 -0500 Message-ID: <1041532923.3e1487fb50a0e@www.nexusmail.uwaterloo.ca> Date: Thu, 2 Jan 2003 13:42:03 -0500 From: Bruce Campbell To: Francesco Casadei Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ata "fallback to PIO mode" on dual processor AMD systems References: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> <20030102163812.GA2350@goku.kasby> In-Reply-To: <20030102163812.GA2350@goku.kasby> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 / FreeBSD-4.6.2 X-Originating-IP: 129.97.50.50 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Quoting Francesco Casadei : > On Tue, Dec 31, 2002 at 03:57:16PM -0500, Bruce Campbell wrote: > > > > I am seeing a problem with ata disks on 4 new systems, which > > I believe is either a bug in the ata driver, or a problem with > > the onboard IDE controller, or something else. Systems are as follows: > > ... > > Motherboard: ASUS A7M266-D > > CPUs : 2 x 2000+ AMD MP > > Memory : 2 x 512MB Crucial part: CT6472Y265 > > Dec 30 23:26:59 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > - > > resetting > > Dec 30 23:26:59 ecserv13 /kernel: ata0: resetting devices .. done > > Dec 30 23:26:59 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > > resetting > > Dec 30 23:27:00 ecserv13 /kernel: ata0: resetting devices .. done > > Dec 30 23:27:00 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > > resetting > > Dec 30 23:27:00 ecserv13 /kernel: ata0: resetting devices .. done > > Dec 30 23:27:00 ecserv13 /kernel: ad0: WRITE command timeout tag=0 serv=0 > > resetting > > Dec 30 23:27:00 ecserv13 /kernel: ad0: timeout waiting for cmd=ef s=d0 > e=00 > > Dec 30 23:27:00 ecserv13 /kernel: ad0: trying fallback to PIO mode > > Same problem here, but slightly different configuration: > > # atacontrol list > ATA channel 0: > Master: ad0 ATA/ATAPI rev 5 > Slave: no device present > ATA channel 1: > Master: acd0 ATA/ATAPI rev 0 > Slave: no device present > ATA channel 2: > Master: ad4 ATA/ATAPI rev 5 > Slave: no device present > ATA channel 3: > Master: ad6 ATA/ATAPI rev 5 > Slave: no device present > > ad4 and ad6 are attached to a Promise FastTrak 100 TX2 ATA RAID controller. > > # atacontrol mode 0 > Master = UDMA100 > Slave = ??? > > # atacontrol mode 1 > Master = PIO4 > Slave = ??? > > # atacontrol mode 2 > Master = UDMA100 > Slave = ??? > > # atacontrol mode 3 > Master = PIO4 > Slave = ??? > > ad6 falls back to PIO mode on heavy I/O activity, i.e. when the system does > a > level 0 file systems dump from the RAID 1 array (ad4,ad6) to the backup disk > ad0. > Rebooting and rebuilding the array with the Promise BIOS utility temporarily > solve the problem. The system may be up and running for 1-4 weeks doing a > level 0 dump every morning at 5:30am and then one day the drive ad6 falls > back > to PIO mode again (little before the completion of fs dump). > > Do the hard drives you are using support the ATA tagged queuing? And if so, > do > you have TQ enbled? I don't have it enabled: hw.ata.tags: 0 I've manually set: atacontrol mode 0 UDMA33 UDMA33 and the problem has not recurred. -- Bruce Campbell Engineering Computing CPH-2374B University of Waterloo (519)888-4567 ext 5889 ---------------------------------------- This mail sent through www.mywaterloo.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 11:36:34 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4655637B401; Thu, 2 Jan 2003 11:36:31 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id D29E443EB2; Thu, 2 Jan 2003 11:36:29 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id GAA06502; Fri, 3 Jan 2003 06:36:23 +1100 Date: Fri, 3 Jan 2003 06:36:29 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Bruce Campbell Cc: freebsd-hardware@FreeBSD.ORG, Subject: Re: Followup to "fallback to PIO mode" on dual processor AMD systems In-Reply-To: <1041526384.3e146e708b8e4@www.nexusmail.uwaterloo.ca> Message-ID: <20030103062516.F755-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 2 Jan 2003, Bruce Campbell wrote: > At present, I don't suspect bad media because the error message is > "WRITE command timeout tag=0 serv=0" which doesn't suggest a specific > sector/track etc, and running with UDMA33 instead of UDMA100 makes the problem > appear to vanish. The fallback is clearly wrong because it turns isolated media errors into pessimized i/o for the whole disk at best, system hangs during resets next best, and system crashes at worst. I keep a disk with bad media on line for testing some of this, and zap the fallback using the following patch (hope this is complete; it was edited from a larger patch). %%% Index: ata-disk.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.139 diff -u -2 -r1.139 ata-disk.c --- ata-disk.c 17 Dec 2002 16:26:22 -0000 1.139 +++ ata-disk.c 18 Dec 2002 01:03:37 -0000 @@ -597,5 +606,5 @@ else { ata_dmainit(adp->device, ata_pmode(adp->device->param), -1, -1); - printf(" falling back to PIO mode\n"); + printf(" NOT falling back to PIO mode\n"); } TAILQ_INSERT_HEAD(&adp->device->channel->ata_queue, request, chain); @@ -603,4 +612,5 @@ } +#if 0 /* if using DMA, try once again in PIO mode */ if (request->flags & ADR_F_DMA_USED) { @@ -613,4 +623,5 @@ return ATA_OP_FINISHED; } +#endif request->flags |= ADR_F_ERROR; %%% Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 13:31:20 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78AB337B401; Thu, 2 Jan 2003 13:31:17 -0800 (PST) Received: from level.uwaterloo.ca (level.uwaterloo.ca [129.97.50.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB1D443EA9; Thu, 2 Jan 2003 13:31:16 -0800 (PST) (envelope-from bruce@engmail.uwaterloo.ca) Received: from level.uwaterloo.ca (localhost [127.0.0.1]) by level.uwaterloo.ca (8.12.3/8.12.3) with ESMTP id h02LTq5n075524; Thu, 2 Jan 2003 16:29:52 -0500 (EST) (envelope-from bruce@engmail.uwaterloo.ca) Received: (from www@localhost) by level.uwaterloo.ca (8.12.3/8.12.3/Submit) id h02LTppi075523; Thu, 2 Jan 2003 16:29:51 -0500 (EST) X-Authentication-Warning: level.uwaterloo.ca: www set sender to bruce@engmail.uwaterloo.ca using -f Received: from 129.97.50.50 ( [129.97.50.50]) as user bruce@engmail.uwaterloo.ca by www.nexusmail.uwaterloo.ca with HTTP; Thu, 2 Jan 2003 16:29:51 -0500 Message-ID: <1041542991.3e14af4fc3d65@www.nexusmail.uwaterloo.ca> Date: Thu, 2 Jan 2003 16:29:51 -0500 From: Bruce Campbell To: Bruce Evans Cc: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Followup to "fallback to PIO mode" on dual processor AMD systems References: <20030103062516.F755-100000@gamplex.bde.org> In-Reply-To: <20030103062516.F755-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 / FreeBSD-4.6.2 X-Originating-IP: 129.97.50.50 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Quoting Bruce Evans : > On Thu, 2 Jan 2003, Bruce Campbell wrote: > > > At present, I don't suspect bad media because the error message is > > "WRITE command timeout tag=0 serv=0" which doesn't suggest a specific > > sector/track etc, and running with UDMA33 instead of UDMA100 makes the > problem > > appear to vanish. > > The fallback is clearly wrong because it turns isolated media errors > into pessimized i/o for the whole disk at best, system hangs during > resets next best, and system crashes at worst. I keep a disk with bad > media on line for testing some of this, and zap the fallback using the > following patch (hope this is complete; it was edited from a larger > patch). Thanks for the patch. Under moderate load, I am seeing occasional instances of: /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting /kernel: ata0: resetting devices .. done and everything keeps on working normally via DMA. ie it does not drop to PIO. The more manacing case is this: Dec 30 23:26:59 /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Dec 30 23:26:59 /kernel: ata0: resetting devices .. done Dec 30 23:26:59 /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Dec 30 23:27:00 /kernel: ata0: resetting devices .. done Dec 30 23:27:00 /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Dec 30 23:27:00 /kernel: ata0: resetting devices .. done Dec 30 23:27:00 /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Dec 30 23:27:00 /kernel: ad0: timeout waiting for cmd=ef s=d0 e=00 Dec 30 23:27:00 /kernel: ad0: trying fallback to PIO mode Dec 30 23:27:00 /kernel: ata0: resetting devices .. done So it appears it would no longer with DMA, but it would work with PIO. If it is manually set back to UDMA with the atacontrol command, it times out again, and falls back to PIO. However, a soft reboot, and all is well again. > > %%% > Index: ata-disk.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v > retrieving revision 1.139 > diff -u -2 -r1.139 ata-disk.c > --- ata-disk.c 17 Dec 2002 16:26:22 -0000 1.139 > +++ ata-disk.c 18 Dec 2002 01:03:37 -0000 > @@ -597,5 +606,5 @@ > else { > ata_dmainit(adp->device, ata_pmode(adp->device->param), -1, -1); > - printf(" falling back to PIO mode\n"); > + printf(" NOT falling back to PIO mode\n"); > } > TAILQ_INSERT_HEAD(&adp->device->channel->ata_queue, request, chain); > @@ -603,4 +612,5 @@ > } > > +#if 0 > /* if using DMA, try once again in PIO mode */ > if (request->flags & ADR_F_DMA_USED) { > @@ -613,4 +623,5 @@ > return ATA_OP_FINISHED; > } > +#endif > > request->flags |= ADR_F_ERROR; > %%% > > Bruce > -- Bruce Campbell Engineering Computing CPH-2374B University of Waterloo (519)888-4567 ext 5889 ---------------------------------------- This mail sent through www.mywaterloo.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 13:39:29 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21CA537B405 for ; Thu, 2 Jan 2003 13:39:27 -0800 (PST) Received: from mail.tiscali.it (mail-1.tiscali.it [195.130.225.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3923743EA9 for ; Thu, 2 Jan 2003 13:39:25 -0800 (PST) (envelope-from fcasadei@inwind.it) Received: from goku.kasby (217.133.211.64) by mail.tiscali.it (6.5.032) id 3E0C9704002016C7 for freebsd-hardware@freebsd.org; Thu, 2 Jan 2003 22:39:23 +0100 Received: (qmail 29595 invoked by uid 1000); 2 Jan 2003 21:39:11 -0000 Date: Thu, 2 Jan 2003 22:39:11 +0100 From: Francesco Casadei To: Bruce Campbell Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Re: ata "fallback to PIO mode" on dual processor AMD systems Message-ID: <20030102213911.GA13458@goku.kasby> Mail-Followup-To: Bruce Campbell , freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org References: <1041368236.3e1204ac45da5@www.nexusmail.uwaterloo.ca> <20030102163812.GA2350@goku.kasby> <1041532923.3e1487fb50a0e@www.nexusmail.uwaterloo.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <1041532923.3e1487fb50a0e@www.nexusmail.uwaterloo.ca> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.7-STABLE i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 02, 2003 at 01:42:03PM -0500, Bruce Campbell wrote: >=20 [snip] > I don't have it enabled: >=20 > hw.ata.tags: 0 >=20 > I've manually set: >=20 > atacontrol mode 0 UDMA33 UDMA33 >=20 > and the problem has not recurred. >=20 > --=20 > Bruce Campbell > Engineering Computing > CPH-2374B > University of Waterloo > (519)888-4567 ext 5889 >=20 > ---------------------------------------- > This mail sent through www.mywaterloo.ca >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message >=20 > end of the original message # atacontrol mode 3 Master =3D PIO4=20 Slave =3D ??? # atacontrol mode 3 udma33 xxx Master =3D UDMA33=20 Slave =3D ??? # atacontrol mode 3 Master =3D UDMA33=20 Slave =3D ??? # find / -name nonexistent -print # atacontrol mode 3 Master =3D PIO4=20 Slave =3D ??? After little disk activity, like searching a file throughout the entire filesystem, the second disk of the RAID array falls back to PIO4 mode. I booted the system from the live system cd (2nd disk of the freebsd distribution set) then ran dd to read from and write to ad6: no errors were found. Francesco Casadei --=20 You can download my public key from http://digilander.libero.it/fcasadei/ or retrieve it from a keyserver (pgpkeys.mit.edu, wwwkeys.pgp.net, ...) Key fingerprint is: 1671 9A23 ACB4 520A E7EE 00B0 7EC3 375F 164E B17B --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE+FLF+fsM3XxZOsXsRAveBAJ9ZG5yIZDlVBs2F8UslyyT8rzYtmACfdYHK KrLDpkI+OejwC8Cb3E3Nuu0= =v0C8 -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 2 13:50:27 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9D6437B401; Thu, 2 Jan 2003 13:50:26 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C65D043EC2; Thu, 2 Jan 2003 13:50:25 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.6/8.12.6) with ESMTP id h02LoI1N052364; Thu, 2 Jan 2003 16:50:18 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.6/8.12.6/Submit) id h02LoILU052363; Thu, 2 Jan 2003 16:50:18 -0500 (EST) (envelope-from barney) Date: Thu, 2 Jan 2003 16:50:18 -0500 From: Barney Wolff To: Bruce Evans Cc: Bruce Campbell , freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Followup to "fallback to PIO mode" on dual processor AMD systems Message-ID: <20030102215018.GA52185@pit.databus.com> References: <1041526384.3e146e708b8e4@www.nexusmail.uwaterloo.ca> <20030103062516.F755-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030103062516.F755-100000@gamplex.bde.org> User-Agent: Mutt/1.4i X-Scanned-By: MIMEDefang 2.26 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Jan 03, 2003 at 06:36:29AM +1100, Bruce Evans wrote: > > The fallback is clearly wrong because it turns isolated media errors > into pessimized i/o for the whole disk at best, system hangs during > resets next best, and system crashes at worst. I keep a disk with bad > media on line for testing some of this, and zap the fallback using the > following patch (hope this is complete; it was edited from a larger > patch). Perhaps the right answer is to test uptime and do the fallback if the error happens in the first minute, at least for permanently-mounted disks. In any case, retries in the current mode should be exhausted first. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 3 1:16:48 2003 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0767437B401 for ; Fri, 3 Jan 2003 01:16:46 -0800 (PST) Received: from smtp.netcologne.de (smtp.netcologne.de [194.8.194.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 441FE43EB2 for ; Fri, 3 Jan 2003 01:16:45 -0800 (PST) (envelope-from jeffrey.crawford@netcologne.de) Received: from lissi.crawford.int (xdsl-213-168-105-92.netcologne.de [213.168.105.92]) by smtp.netcologne.de (Postfix) with ESMTP id 2B6F68675C for ; Fri, 3 Jan 2003 10:16:40 +0100 (MET) Received: by lissi.crawford.int (Postfix, from userid 1000) id 7C6114B12; Fri, 3 Jan 2003 10:16:41 +0100 (CET) Date: Fri, 3 Jan 2003 10:16:41 +0100 From: Jeffrey Eugene Crawford To: freebsd-hardware@freebsd.org Cc: jeffrey.crawford@netcologne.de Subject: Problem with USB Kodak DX4900 Message-ID: <20030103091641.GA1034@lissi.crawford.int> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello everyone, I've been looking around the newsgroups, and mail archives the past couple of days, but I still can't get the thing to work. When I try to connect the Kodak DX4900 digital camera to my USB port, I get (After a slight delay) the following message appears on the console: uhub0: device problem, disabling port 1 After that my Mustek 1200UB scanner stops woking with a similar message identifying port 2 this time. Only a reboot with the Camera not attached will reenable the Mustek Scanner again. the output of "usbdev -v" will print a message on the port where the camera is installed "this can't happen!" (Or something simmilar). My VIA chipset seems to show up often when I'm searching for USB problems in the newsgroup and freebsd archives. I'm starting to assume that the VIA USB chipset is not all that its cracked up to be. Please note that I'm not subscribed to this mailing list so please remember to include me in the CC when responding to this mail. Here is the output from dmesg when camera and scanner were attached: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-RELEASE-p2 #0: Thu Dec 12 00:08:52 CET 2002 root@lissi.crawford.int:/usr/obj/usr/src/sys/LISSI Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 751709439 Hz CPU: AMD Athlon(tm) Processor (751.71-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x622 Stepping = 2 Features=0x183f9ff AMD Features=0xc0400000 real memory = 805240832 (786368K bytes) avail memory = 778235904 (759996K bytes) Preloaded elf kernel "kernel" at 0xc04a5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04a509c. Preloaded elf module "linux.ko" at 0xc04a50ec. Preloaded elf module "agp.ko" at 0xc04a518c. Preloaded elf module "nvidia.ko" at 0xc04a5228. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00fde40 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xd8000000-0xdbffffff at device 0.0 on pci0 pcib2: at device 1.0 on pci0 pci1: on pcib2 nvidia0: mem 0xd0000000-0xd7ffffff,0xdc000000-0xdcffffff irq 5 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xc000-0xc00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xc400-0xc41f irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: device problem, disabling port 1 uhub0: device problem, disabling port 2 pci0: (vendor=0x1106, dev=0x3057) at 7.4 pcm0: port 0xd400-0xd403,0xd000-0xd003,0xcc00-0xccff irq 10 at device 7.5 on pci0 atapci1: port 0xe800-0xe80f,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd807 mem 0xdf000000-0xdf003fff irq 11 at device 9.0 on pci0 ata2: at 0xd800 on atapci1 ata3: at 0xe000 on atapci1 rl0: port 0xec00-0xecff mem 0xdf004000-0xdf0040ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:30:84:40:ff:fa miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: on motherboard pci2: on pcib1 orm0: