From owner-freebsd-current Fri Jul 9 16:46:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id D8F9D15053 for ; Fri, 9 Jul 1999 16:46:21 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id XAA01977 for ; Fri, 9 Jul 1999 23:46:18 GMT Message-ID: <3786890E.2F6CCE34@tdx.co.uk> Date: Sat, 10 Jul 1999 00:43:10 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Latest currents 'hang' on biord? [ Appears only on my system? :( ] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Any current's more recent than about a month ago on my main system seem to 'hang' on biord whenever they access the IDE drives... The system boots of SCSI, has a number of SCSI drives - but as soon as it either tries to mount, or fsck an IDE drive it just hangs... Breaking into DDB at the time and running PS shows either fsck, or mount in "biord" - even a simple DD results in the same hang... Hitting CTRL-C will quit the mount/fsck/dd command - but the system just doesn't seem to be able to access it's IDE drives? Has anyone got any suggestions? - I noticed this a while ago, and posted accordingly - but no one responded... If I boot an old kernel (like a month old) the system comes up OK, but any newer kernels and they just hang... I've tried rebuilding the kernel config from GENERIC, but it does the same :( System is an SMP dual P-Pro200, running on a SuperMicro P6DNF w/256Mb RAM, 3 x 2940's, and 4xIDE drives... Kernel config just says: controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 dmesg for the above drives is below (I'd post the whole -v dmesg, but it's very long :( wdc0 at 0x1f0-0x1f7 irq 14 flags 0xff00ff on isa wdc0: unit 0 (wd0): , multi-block-16 wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc0: unit 1 (wd1): , multi-block-16 wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1 at 0x170-0x177 irq 15 flags 0xff00ff on isa wdc1: unit 0 (wd2): , multi-block-16 wd2: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1: unit 1 (wd3): , multi-block-8 wd3: 2445MB (5008752 sectors), 4969 cyls, 16 heads, 63 S/T, 512 B/S wd3: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 Any suggestions? - I'd guess it's not a very prolific problem, as no one else seems to have the same symptoms? :( -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message