From owner-freebsd-stable Tue Apr 2 20:30:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from lynx.syix.com (lynx.syix.com [205.171.72.20]) by hub.freebsd.org (Postfix) with ESMTP id 2004737B43A for ; Tue, 2 Apr 2002 20:30:28 -0800 (PST) Received: from cat (cat.npqr.net [63.147.19.40]) by lynx.syix.com (8.11.6/8.11.6) with SMTP id g334UOe97744 for ; Tue, 2 Apr 2002 20:30:24 -0800 (PST) (envelope-from pan@syix.com) Message-ID: <01f201c1dac8$45cd95a0$2813933f@cat> From: "pan" To: Subject: ata still breaks raid Date: Tue, 2 Apr 2002 20:30:18 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 tried cvsup again today [04/02/2002 14:00 PST] after noticing new code in repository relative to via northbridges ... same results as reported before ... 4.5-STABLE breaks the raid array and panics to an awkward halt. I am positive that if the ata system worked at least as well as it does in 4.5-RELEASE I wouldn't be plaguing the list with these frequent reports on attemtps to get 4.5-STABLE installed. I mean - 4.5-RELEASE manages to create and use ar0 with no trouble on the same equipment 4.5-STABLE fails on with relentless consistency. Therefore, it seems as though the differenc between having a working sever and a broken one is whatever difference there is between 4.5-RELEASE and 4.5-STABLE. A little more data is offered here (I'd still like someone to give me feedback on what other data or tests I can provide - haven't got any replies yet that moves this break in STABLE along) ... I noticed that the 4.5-RELEASE install on the same box that works(does it really?) shows some other errors in the ata sub-system as noted before the mb in question is an Abit KR7A-RAID with the KT266 chipset (VIA VT8366A /VT8233), yet look at this line from dmesg atapci0: port 0xc400-0xc40f at device 17.1 on pci0 as far as this humble correspondent believes, there isn't a 686 chip on the mb - so, what's up with that? Is that a symptom that the ata code has a break in it that goes back to 4.5r or before? 4.5r misidentifies a hpt372 as an udma 5 device and when 4.5r boots it resets udma 6 drives to udma 5. That I understand to be a matter of developing code and that 4.5s does udma 6. 4.5-RELEASE dmesg appended in hopes there might be some demi-clueful data for anyone who cares about the ata sub-system. I am willing to provide any other data from the machine 4.5-STABLE breaks and there is a window of time still available for whatever tests might produce useful info, if only I knew what any maintainer might need to know. Pan * 4.5r dmesg KR&A-R/hpt372 boot_verbose & verbose_loading* 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.5-RELEASE #0: Mon Mar 25 14:07:06 PST 2002 xxxxxxx Calibrating clock(s) ... TSC clock: 1600825917 Hz, i8254 clock: 1193289 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 1600690919 Hz CPU: AMD Athlon(tm) XP 1900+ (1600.69-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480000<,AMIE,DSP,3DNow!> Data TLB: 32 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 1073676288 (1048512K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00312000 - 0x3ffe7fff, 1070424064 bytes (261334 pages) avail memory = 1042759680 (1018320K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fb030 bios32: Entry = 0xfb4a0 (c00fb4a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb4d0 pnpbios: Found PnP BIOS data at 0xc00fbfa0 pnpbios: Entry = f0000:bfd0 Rev = 1.0 Other BIOS signatures found: ACPI: 000f6e00 Preloaded elf kernel "kernel" at 0xc02eb000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02eb09c. VESA: information block 56 45 53 41 00 02 b0 0e 00 c0 00 00 00 00 f6 0e 00 c0 20 00 01 01 cf 0e 00 c0 e0 0e 00 c0 ee 0e 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 45 mode(s) found VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc00c0ef6 (c0000ef6) VESA: S3 Incorporated. ViRGE /DX /GX VESA: S3 Incorporated. ViRGE /DX /GX Rev B Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 pci_open(1): mode 1 addr port (0x0cf8) is 0x80008840 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=30991106) Using $PIR table, 8 entries at 0xc00fdef0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x1106, dev=0x3099, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e0000000, size 26 found-> vendor=0x1106, dev=0xb099, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x11ad, dev=0x0002, revid=0x11 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base 0000c000, size 8 map[14]: type 1, range 32, base e9000000, size 8 found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e4000000, size 26 found-> vendor=0x1106, dev=0x3074, revid=0x00 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x0571, revid=0x06 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[20]: type 1, range 32, base 0000c400, size 4 found-> vendor=0x1103, dev=0x0004, revid=0x05 class=01-04-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 0000d400, size 3 map[14]: type 1, range 32, base 0000d800, size 2 map[18]: type 1, range 32, base 0000dc00, size 3 map[1c]: type 1, range 32, base 0000e000, size 2 map[20]: type 1, range 32, base 0000e400, size 8 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 dc0: <82c168 PNIC 10/100BaseTX> port 0xc000-0xc0ff mem 0xe9000000-0xe90000ff irq 12 at device 13.0 on pci0 dc0: Ethernet address: 00:a0:cc:30:ec:71 miibus0: on dc0 pnphy0: on miibus0 pnphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX bpf: dc0 attached pci0: (vendor=0x5333, dev=0x8a01) at 16.0 irq 11 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xc400-0xc40f at device 17.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xc400 ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=14 b=eb ata0-slave: ATAPI probe a=7f b=7f ata0: mask=03 status0=00 status1=00 ata0: devices=04 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xc408 ata1: mask=03 status0=20 status1=30 ata1: mask=03 ostat0=20 ostat2=30 ata1-master: ATAPI probe a=20 b=20 ata1-slave: ATAPI probe a=30 b=30 ata1: mask=03 status0=20 status1=30 ata1-master: ATA probe a=25 b=25 ata1-slave: ATA probe a=25 b=25 ata1: devices=00 ata1: at 0x170 irq 15 on atapci0 atapci1: port 0xe400-0xe4ff,0xe000-0xe003,0xdc00-0xdc07,0xd800-0xd803,0xd400-0xd407 irq 10 at device 19.0 on pci0 ata-: ata2 exists, using next available unit number ata2: iobase=0xd400 altiobase=0xd802 bmaddr=0xe400 ata2: mask=03 status0=50 status1=00 ata2: mask=03 ostat0=50 ostat2=00 ata2-master: ATAPI probe a=00 b=00 ata2-slave: ATAPI probe a=00 b=00 ata2: mask=03 status0=50 status1=00 ata2-master: ATA probe a=01 b=a5 ata2: devices=01 ata2: at 0xd400 on atapci1 ata3: iobase=0xdc00 altiobase=0xe002 bmaddr=0xe408 ata3: mask=03 status0=50 status1=00 ata3: mask=03 ostat0=50 ostat2=00 ata3-master: ATAPI probe a=00 b=00 ata3-slave: ATAPI probe a=00 b=00 ata3: mask=03 status0=50 status1=00 ata3-master: ATA probe a=01 b=a5 ata3: devices=01 ata3: at 0xdc00 on atapci1 using shared irq10. ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: