From owner-freebsd-stable Sun Jan 20 7:28:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id B750237B402 for ; Sun, 20 Jan 2002 07:28:35 -0800 (PST) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id g0KFSWq01387 for ; Sun, 20 Jan 2002 16:28:32 +0100 (MET) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.194.33]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/6) with ESMTP id g0KFSVv01380 for ; Sun, 20 Jan 2002 16:28:31 +0100 (MET) Received: from margaux.informatik.rwth-aachen.de (margaux.Informatik.RWTH-Aachen.DE [137.226.194.72]) by hyperion.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1) with ESMTP id QAA07306 for ; Sun, 20 Jan 2002 16:27:07 +0100 (MET) Received: (from stolz@localhost) by margaux.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id QAA11152 for stable@freebsd.org; Sun, 20 Jan 2002 16:28:27 +0100 (MET) Date: Sun, 20 Jan 2002 16:28:27 +0100 From: Volker Stolz To: stable@freebsd.org Subject: Promise TX2/UDMA133 errors Message-ID: <20020120162827.A11147@i2.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG After updating from 4.5-PRELEASE to 4.5-RC1 the following errors turned up: ... ad4s2f: UDMA ICRC error reading fsbn 27561419 of 3308872-3308935 (ad4s2 bn 27561419; cn 1715 tn 157 sn 53) retrying ad4s2a: UDMA ICRC error reading fsbn 20758395 of 137760-137839 (ad4s2 bn 20758395; cn 1292 tn 38 sn 21) retrying ... The machine build world without any of these signs running the previous kernel. Unluckily, the kernel backup got wiped out, so I cannot downgrade. atapci1: port 0xb400-0xb40f,0xb000-0xb003,0xac00-0xac07,0xa800-0xa803,0xa400-0xa407 mem 0xe0800000-0xe0803fff irq 11 at device 8.0 on pci0 ata2: at 0xa400 on atapci1 ata3: at 0xac00 on atapci1 ad4: 32253MB [69899/15/63] at ata2-master UDMA133 The PCI irq is shared by 3 devices, if that's got anything to do with it: vs@monster [16:19:20]> dmesg | grep "irq 11" pci1: <3Dfx Voodoo 3 graphics accelerator> at 0.0 irq 11 atapci1: port 0xb400-0xb40f,0xb000-0xb003,0xac00-0xac07,0xa800-0xa803,0xa400-0xa407 mem 0xe0800000-0xe0803fff irq 11 at device 8.0 on pci0 sym0: <810a> port 0xc400-0xc4ff mem 0xe0807000-0xe08070ff irq 11 at device 12.0 on pci0 drm0: <3Dfx Voodoo 3 graphics accelerator> port 0x9000-0x90ff mem 0xdc000000-0xddffffff,0xd8000000-0xd9ffffff irq 11 at device 0.0 on pci1 I know there have been changes in the ata-stuff because of VIA borkedness, but this is a Gigabyte 6BXD running a single CPU. I'll get a different board (Tyan Tiger 230T) in about a week, I do not trust this board any longer. Could any of the recent changes be responsible for this? -- Wonderful \hbox (0.80312pt too nice) in paragraph at lines 16--18 Volker Stolz * stolz@i2.informatik.rwth-aachen.de Please use PGP or S/MIME for correspondence! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message