Toshiba 8100 Fix (was Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 - 5.4 breaks ATA (Intel ICH2))
I have a Toshiba 8100 notebook which runs 5.4-STABLE. Kernels compiled after some time in September 2005 fail to boot; the machine locks up right after the ata controller is called in the boot messages. I have traced the problem to a change to /usr/src/sys/dev/pci.c, (see below from my cvsup log). I found the problem by cvsup'ing /usr/src for dates starting with my last working kernel and once I had the date of problem code tied down to a couple of days adding in each update to see if it caused the failure to boot. I then added the fix to the latest 5.4 sources to make sure that the fix still worked. The problem (really the Toshiba 8100 BIOS problem) was triggered by: Edit src/sys/dev/pci/pci.c Add delta 1.264.2.12 2005.09.05.18.09.20 imp which changes line 835 of pci.c from if (base == 0) to if (base == 0 || map == testval) The sysctl parameter hw.pci.enable_io_modes is supposed to allow PCs with lazy BIOSes to boot, but in the case of the 8100 setting hw.pci.enable_io_modes: 0 doesn't allow the system to boot. This is obviously a problem with the Toshiba BIOS, which I know from other times has other problems; I am putting this here in case someone else has the same problem and wants to boot FreeBSD 5.4-STABLE with a kernel revision after 9/5/2005. Mike Squires ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
On Sat, 24 Sep 2005, Billy Newsom wrote: Okay, Tim, I just reported the same bug in a previous post. So did Julian C. Dunn. I think this is an issue with some recent code changes in CVS... See these threads: critical BOOT failure updating to latest 5-Stable (5.4) 9/23/2005 12:07 AM ATA lockup with 5.4-STABLE 9/21/2005 10:19 PM I have a similar problem (previously posted to this mailing list) with a Toshiba 8100 which locks up when atapci0 is called during the boot using recent kernels. I can boot off an old 5.4-RELEASE kernel (May 2005) and can boot off the more recent kernels if I copy the old version of acpi.ko over the new version, which leads me to believe that it is changes in the ACPI code which are the source of the problem. I've posted to the ACPI mailing list (I'm not aware of any responses). Mike Squires ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
On Sun, Sep 25, 2005 at 01:10:20PM -0400, Tim Howe wrote: Billy Newsom [EMAIL PROTECTED] writes: Anyway, I count three systems that are normally boting with 5.3 or 5.4, and then the upgrade to the latest 5-Stable breaks the boot. If I may make a small correction, I would like to point out that it's not 5-STABLE that breaks mine but 5.4-RELEASE. Even booting from the 5.4 mini-CD can't find the drive, but booting from the 5.3 installer can. I don't know if this helps, but I had some nasty tries installing 5.(3?4?)-release from scratch on some SuperMicro SATA-based systems, and while it seemed to be choking on SATA, what I did was install in safe mode from the CD-ROM, compile an SMP kernel, and reboot. With the SMP kernel, the systems ran fine, without, choking on SATA errors ... -danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
On Tue, Oct 04, 2005 at 04:30:19PM -0700, Danny Howard wrote: On Sun, Sep 25, 2005 at 01:10:20PM -0400, Tim Howe wrote: Billy Newsom [EMAIL PROTECTED] writes: Anyway, I count three systems that are normally boting with 5.3 or 5.4, and then the upgrade to the latest 5-Stable breaks the boot. If I may make a small correction, I would like to point out that it's not 5-STABLE that breaks mine but 5.4-RELEASE. Even booting from the 5.4 mini-CD can't find the drive, but booting from the 5.3 installer can. I don't know if this helps, but I had some nasty tries installing 5.(3?4?)-release from scratch on some SuperMicro SATA-based systems, and while it seemed to be choking on SATA, what I did was install in safe mode from the CD-ROM, compile an SMP kernel, and reboot. With the SMP kernel, the systems ran fine, without, choking on SATA errors ... AErrr, pardon my stupidity ... this was actually on some motherboards with SCSI disks attached that were barfing on 5.3 ... my SATA machines have been just fine in this respect. :) Thanks, -danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 - 5.4 breaks ATA (Intel ICH2))
On Thu, 29 Sep 2005, Michael L. Squires wrote: A new kernel based on sources of 9/28/2005 still fails to boot on a Toshiba 8100 with a UDMA33 IDE onboard controller. The parameters passed to atapci0 are different from those passed by the earlier kernel, and the system locks up this point. Following suggestions elswhere I replaced acpi.ko in the new kernel directory with the acpi.ko from the last working kernel and the new kernel now boots. I'll run the usual ACPI debugging info and post to the freebsd-acpi mailing list. Mike Squires Toshiba 8100 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 - 5.4 breaks ATA (Intel ICH2))
A new kernel based on sources of 9/28/2005 still fails to boot on a Toshiba 8100 with a UDMA33 IDE onboard controller. The parameters passed to atapci0 are different from those passed by the earlier kernel, and the system locks up this point. I'm not including the dmesg, etc., since that's the same as I posted earlier. Mike Squires ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[PATCH] option to re-enable aggressive ATA probing (was: 5.3 - 5.4 breaks ATA (Intel ICH2))
Tim Howe [EMAIL PROTECTED] writes:
ata0-master: stat=0xd0 err=0xd0 lsb=0xd0 msb=0xd0
This turned out to be the key.
Version 1.51 of ata-lowlevel.c added a check for stat0/1, err, lsb, and
msb being identical. If they are, it aborts the probe. The attached
patch creates an option ATA_AGGRESSIVE_PROBE which disables this for the
old aggressive behavior (which may wait up to the full 31 seconds).
I also took the liberty of reworking the still-busy check from 3
equality tests to 2 bitmask tests. It seems simpler to my eye with
identical results, but if I missed something or the other style was
preferred please let me know.
The patch is against 5-STABLE because that's what I have.
--
Tim Howe
Software Engineer
Celebrity Resorts, Inc.
--- sys/conf/options.stock Tue Sep 27 00:28:50 2005
+++ sys/conf/options Tue Sep 27 00:55:53 2005
@@ -301,6 +301,7 @@
# Options used in the 'ata' ATA/ATAPI driver
ATA_STATIC_ID opt_ata.h
ATA_NOPCI opt_ata.h
+ATA_AGGRESSIVE_PROBE opt_ata.h
DEV_ATADISK opt_ata.h
DEV_ATAPICD opt_ata.h
DEV_ATAPIST opt_ata.h
--- sys/conf/NOTES.stock Tue Sep 27 00:30:28 2005
+++ sys/conf/NOTES Tue Sep 27 00:56:39 2005
@@ -1501,8 +1501,11 @@
#
# ATA_STATIC_ID: controller numbering is static ie depends on location
# else the device numbers are dynamically allocated.
+# ATA_AGGRESSIVE_PROBE: Does not give up on probing when all err, lsb, and
+ msb are identical.
options ATA_STATIC_ID
+#options ATA_AGGRESSIVE_PROBE
#
# Standard floppy disk controllers and floppy tapes, supports
--- sys/dev/ata/ata-lowlevel.c.stock Tue Sep 27 00:31:10 2005
+++ sys/dev/ata/ata-lowlevel.c Tue Sep 27 00:59:19 2005
@@ -604,24 +604,21 @@
}
}
}
- if (mask == 0x01) /* wait for master only */
- if (!(stat0 ATA_S_BUSY) || (stat0 == 0xff timeout 5) ||
- (stat0 == err lsb == err msb == err timeout 5))
- break;
- if (mask == 0x02) /* wait for slave only */
- if (!(stat1 ATA_S_BUSY) || (stat1 == 0xff timeout 5) ||
- (stat1 == err lsb == err msb == err timeout 5))
- break;
- if (mask == 0x03) { /* wait for both master slave */
- if (!(stat0 ATA_S_BUSY) !(stat1 ATA_S_BUSY))
- break;
- if ((stat0 == 0xff timeout 5) ||
- (stat0 == err lsb == err msb == err timeout 5))
- mask = ~0x01;
- if ((stat1 == 0xff timeout 5) ||
- (stat1 == err lsb == err msb == err timeout 5))
- mask = ~0x02;
- }
+
+if (mask 0x01)/* waiting for master */
+if (!(stat0 ATA_S_BUSY) || (stat0 == 0xff timeout 5)
+#ifndef ATA_AGGRESSIVE_PROBE
+|| (stat0 == err lsb == err msb == err timeout 5)
+#endif
+)
+mask = ~0x01;
+if (mask 0x02)/* waiting for slave */
+if (!(stat1 ATA_S_BUSY) || (stat1 = 0xff timeout 5)
+#ifndef ATA_AGGRESSIVE_PROBE
+|| (stat1 == err lsb == err msb == err timeout 5)
+#endif
+)
+mask = ~0x02;
if (mask == 0 !(stat0 ATA_S_BUSY) !(stat1 ATA_S_BUSY))
break;
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 - 5.4 breaks ATA (Intel ICH2))
On Sun, 2005-09-25 at 15:36 -0500, Billy Newsom wrote: I would like to concur with this sighting. I will repeat it to emphasize this for whoever can decipher this for bug fixes: 1. In recent 5-Stable 2. The IDE controller, atapci0, 3. seems to be detectected, but without a certain memory allocation 4. namely, 0xfff0-0x 5. while the other memory and I/O segments are detected fine. Furthermore, 6. It won't boot on the affected machines. 7. More than one controller is affected (ICH2, PIIX3, and possibly PIIX4) 8. Mine, at least, boots fine to a July 4th 5-Stable. Here is an example I found from someone reporting a similar issue (Julian Dunn) Look at this from his dmesg: *First* his good booting dmesg line: atapci0: Intel PIIX4 UDMA33 controller port 0xfff0-0x,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.1 on pci0 *Second* his non-booting dmesg line: atapci0: Intel PIIX4 UDMA33 controller port 0x376,0x170-0x177,0x3f6,0x1f0-0x1f atapci0: Lazy allocation of 0x10 bytes rid 0x20 type 4 at 0 7 at device 2.1 on pci0 Can I point out the fact that these two lines (first from the good, second from the bad dmesg) seem to say that atapci0 is not getting its memory segment detected -- the segment at 0xfff0-0x. Here's a bit more information about the defect. I discovered this accidentally while testing out a -STABLE kernel built today. When I booted the -STABLE kernel, it went and autoloaded the old /boot/kernel/acpi.ko from the -RELEASE kernel, and the system would boot as normal. However, if I broke to the loader prompt and loaded the -STABLE kernel and its corresponding acpi.ko, the machine would fail to boot (as above, with the memory segment not being detected). Would this help anyone in filing a PR about the issue? - Julian -- [ Julian C. Dunn [EMAIL PROTECTED] * You can throw confetti, ] [ WWW: www.aquezada.com/staff/julian * but you're still going ] [ PGP: 91B3 7A9D 683C 7C16 715F* through the motions, baby ] [ 442C 6065 D533 FDC2 05B9*- Aimee Mann ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
Billy Newsom [EMAIL PROTECTED] writes: See these threads: critical BOOT failure updating to latest 5-Stable (5.4) 9/23/2005 12:07 AM ATA lockup with 5.4-STABLE 9/21/2005 10:19 PM Thanks for the references; I'll definiteluy take a look at them (only reason I haven't before replying is that I'm mobile currently and don't feel like digging through archives on the itty bitty screen. Anyway, I count three systems that are normally boting with 5.3 or 5.4, and then the upgrade to the latest 5-Stable breaks the boot. If I may make a small correction, I would like to point out that it's not 5-STABLE that breaks mine but 5.4-RELEASE. Even booting from the 5.4 mini-CD can't find the drive, but booting from the 5.3 installer can. Perhaps you could test one of those identical machines with a simple hard disk swap? Just put the bad booting drive in a working system and see if the error is still there? I can do this either today or tomorrow. Has anyone checked the CVS repository for a possible change to the ATA detection or boot code? Since you mentioned that 5.4-RELEASE worked for you but -STABLE didn't, I've got a build of RELENG_5 (is this still active in comparison to RELENG_6?) going now. Perhaps what broke yours fixed mine. In any case it will be helpful for patching against and testing. Can you post your dmesg for 5.3 perhaps? Yes. BTW, you can boot that machine to the old kernel using the procedure If you think it will be helpful I can. Will this produce a different result than booting from the 5.3 installer? -- Tim Howe Software Engineer Celebrity Resorts, Inc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.4-STABLE changes breaks IDE boot (was Re: 5.3 - 5.4 breaks ATA (Intel ICH2))
This may be a similar problem to the one discussed in the Intel ICH2 thread. System is a Toshiba 8100. System boots from a 5.4-STABLE kernel compiled 5/3/2005 but locks up on boot with kernels compiled in the past few days. I re-cvsup'd after the first lockup and build a GENERIC kernel, same results. The atapci0 lines were divided by the mailer to fit into an 80 col line, I've added the \. The only difference I can see is that the working kernel allocates port 0xfff0-0x to atapci0, and both the non-working kernels don't allocate those ports. This is the only difference I can see between the working and non-working output from the boot process. The complete old dmesg is attached. Mike Squires --hopefully relevant parts of old dmesg-- FreeBSD 5.4-STABLE #0: Tue May 3 21:29:44 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/PORT Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (697.42-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 402522112 (383 MB) avail memory = 384188416 (366 MB) npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xfe08-0xfe0b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xdfff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 3.0 on pci0 isa0: ISA bus on isab0 isab1: PCI-ISA bridge at device 5.0 on pci0 device_attach: isab1 attach returned 6 atapci0: Intel PIIX4 UDMA33 controller port \ 0xfff0-0x,0x376,0x170-0x177,0x3f6,D0x1f0-0x1f7 at device 5.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ---nonworking atapci0 command, hand copied-- atapci0: Intel PIIX4 UDMA33 controller port \ 0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 5.1 on pci0 Copyright (c) 1992-2005 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 5.4-STABLE #0: Tue May 3 21:29:44 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/PORT Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (697.42-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 402522112 (383 MB) avail memory = 384188416 (366 MB) npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xfe08-0xfe0b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xdfff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 3.0 on pci0 isa0: ISA bus on isab0 isab1: PCI-ISA bridge at device 5.0 on pci0 device_attach: isab1 attach returned 6 atapci0: Intel PIIX4 UDMA33 controller port 0xfff0-0x,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 5.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xff80-0xff9f irq 11 at device 5.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge at device 5.3 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 6.0 on pci0 pci2: ACPI PCI bus on pcib2 sym0: 875 port 0xce00-0xceff mem 0xefefe000-0xefefefff,0xefefff00-0xefef irq 11 at device 1.0 on pci2 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. atapci1: CMD 648 UDMA66 controller port 0xcdd0-0xcddf,0xcde4-0xcde7,0xcde8-0xcdef,0xcdf4-0xcdf7,0xcdf8-0xcdff irq 11 at device 3.0 on pci2 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pci0: simple comms at device 7.0 (no driver attached) pci0: wireless controller, iRDA at device 9.0 (no driver attached) cbb0: ToPIC100 PCI-CardBus Bridge at device 11.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: ToPIC100 PCI-CardBus Bridge at device 11.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit
Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 - 5.4 breaks ATA (Intel ICH2))
Michael L. Squires wrote: This may be a similar problem to the one discussed in the Intel ICH2 thread. System is a Toshiba 8100. System boots from a 5.4-STABLE kernel compiled 5/3/2005 but locks up on boot with kernels compiled in the past few days. I re-cvsup'd after the first lockup and build a GENERIC kernel, same results. The atapci0 lines were divided by the mailer to fit into an 80 col line, I've added the \. The only difference I can see is that the working kernel allocates port 0xfff0-0x to atapci0, and both the non-working kernels don't allocate those ports. This is the only difference I can see between the working and non-working output from the boot process. I would like to concur with this sighting. I will repeat it to emphasize this for whoever can decipher this for bug fixes: 1. In recent 5-Stable 2. The IDE controller, atapci0, 3. seems to be detectected, but without a certain memory allocation 4. namely, 0xfff0-0x 5. while the other memory and I/O segments are detected fine. Furthermore, 6. It won't boot on the affected machines. 7. More than one controller is affected (ICH2, PIIX3, and possibly PIIX4) 8. Mine, at least, boots fine to a July 4th 5-Stable. Here is an example I found from someone reporting a similar issue (Julian Dunn) Look at this from his dmesg: *First* his good booting dmesg line: atapci0: Intel PIIX4 UDMA33 controller port 0xfff0-0x,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.1 on pci0 *Second* his non-booting dmesg line: atapci0: Intel PIIX4 UDMA33 controller port 0x376,0x170-0x177,0x3f6,0x1f0-0x1f atapci0: Lazy allocation of 0x10 bytes rid 0x20 type 4 at 0 7 at device 2.1 on pci0 Can I point out the fact that these two lines (first from the good, second from the bad dmesg) seem to say that atapci0 is not getting its memory segment detected -- the segment at 0xfff0-0x. I found this out prior to the post by Mr. Squires, independently. I'm starting to smell a PR, and perhaps some attention by the maintainer of the pci-ata code, which I think is [EMAIL PROTECTED] Billy The complete old dmesg is attached. Mike Squires --hopefully relevant parts of old dmesg-- FreeBSD 5.4-STABLE #0: Tue May 3 21:29:44 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/PORT Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (697.42-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 402522112 (383 MB) avail memory = 384188416 (366 MB) npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xfe08-0xfe0b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xdfff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 3.0 on pci0 isa0: ISA bus on isab0 isab1: PCI-ISA bridge at device 5.0 on pci0 device_attach: isab1 attach returned 6 atapci0: Intel PIIX4 UDMA33 controller port \ 0xfff0-0x,0x376,0x170-0x177,0x3f6,D0x1f0-0x1f7 at device 5.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ---nonworking atapci0 command, hand copied-- atapci0: Intel PIIX4 UDMA33 controller port \ 0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 5.1 on pci0 Copyright (c) 1992-2005 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 5.4-STABLE #0: Tue May 3 21:29:44 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/PORT Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (697.42-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 402522112 (383 MB) avail memory = 384188416 (366 MB) npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xfe08-0xfe0b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xdfff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
On Fri, 2005-Sep-23 22:52:09 -0400, Tim Howe wrote: I've got several other Pentium 3-based machines running 5.4-RELEASE-p3 with a GENERIC kernel, and I have a 5.3 installer disk, so my strategy was to do a minimal install of 5.3, then NFS mount /usr/src and /usr/obj from my organizational build server and upgrade to 5.4 from there. Did you reboot after the 5.3 install or do the upgrade whilst booted from that install disk? root filesystem. Further investigation found that it wasn't able to find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM drive (master on ata0). You shouldn't have two masters on ata0. I hope that's a typo. How far through the boot process do you get? I gather the loader runs successfully and loads the kernel but the kernel can't find ad0. Does it find the controller (ata0 or whatever)? -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
I'm no expert on this, but I'd let that machine have it's own build environment instead of NFS importing it from a server. It _does_ require more disk space, but in the long run, it might be for the better. If you _must_ export from server, then export only /usr/src and not /usr/obj Owe Jørgensen On Fri, 23 Sep 2005 22:52:09 -0400, Tim Howe [EMAIL PROTECTED] wrote: I've got a machine here that I'm trying to install FreeBSD 5.4 on. It's identical (except for the hard drive) to another machine that I ran the 4.x series on for some time with no issues. I've got several other Pentium 3-based machines running 5.4-RELEASE-p3 with a GENERIC kernel, and I have a 5.3 installer disk, so my strategy was to do a minimal install of 5.3, then NFS mount /usr/src and /usr/obj from my organizational build server and upgrade to 5.4 from there. The 5.3 install went smoothly, make installkernel went smoothly, but when I tried to reboot I got an error saying that it couldn't find the root filesystem. Further investigation found that it wasn't able to find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM drive (master on ata0). I verified that the drive had not gone bad by again booting off the 5.3 installer disk, which found ad0 with no difficulty. I then downloaded the 5.4 mini-CD, which was unable to find ad0. Finally, I swapped in another hard drive with identical results. Neither booting with ACPI disabled (didn't bother to check whether this machine even has it) nor booting in safe mode helped at all. I did happen to notice that when the 5.3 CD boots, there is a delay of several seconds when probing ata0. Could this be a timing issue with regard to the controller? The machine is a Gateway ATXSTF FED Pro M1000 with a 1GHz Pentium III and 256MB of RAM. It has an onboard Intel ICH2 UDMA100 controller. The first HDD I tried was a Western Digital Caviar 32500 2559.8MB drive, and the second was a Caviar 24300 4311.9MB drive. If necessary, I'm willing to build custom kernels for testing purposes or to add debugging statements etc, if anyone can give me pointers in the right direction. Thanks in advance. -- mvh, Owe André Jørgensen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
Peter Jeremy [EMAIL PROTECTED] writes: Did you reboot after the 5.3 install or do the upgrade whilst booted from that install disk? I rebooted into the freshly installed 5.3 system and it worked perfectly. The upgrade went fine also. It was only upon booting into the 5.4 kernel that I had problems. Further investigation found that it wasn't able to find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM drive (master on ata0). You shouldn't have two masters on ata0. I hope that's a typo. It is. That should read CDROM drive (master on ata1). How far through the boot process do you get? I gather the loader runs successfully and loads the kernel but the kernel can't find ad0. That's correct. Does it find the controller (ata0 or whatever)? I believe so. I'm not near that machine presently, but I know it found the ATA PCI controller because it was able to find the CDROM drive. I know it displayed a message saying ata0: something or other. If it displayed anything (not an error) does that mean that ata0 was found then? - Tim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
Owe Jørgensen [EMAIL PROTECTED] writes: I'm no expert on this, but I'd let that machine have it's own build environment instead of NFS importing it from a server. I'm not doing a separate build, just installing a prebuilt system. The machines are all Pentium IIIs and I'm using GENERIC kernels on all of them. It _does_ require more disk space, but in the long run, it might be for the better. If you _must_ export from server, then export only /usr/src and not /usr/obj I was following these instructions in the handbook: Secondly, it allows you to use NFS mounts to upgrade multiple machines on your network. If you have three machines, A, B and C that you want to upgrade, run make buildworld and make installworld on A. B and C should then NFS mount /usr/src and /usr/obj from A, and you can then run make installworld to install the results of the build on B and C. -- Tim Howe Software Engineer Celebrity Resorts, Inc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 - 5.4 breaks ATA (Intel ICH2)
Okay, Tim, I just reported the same bug in a previous post. So did Julian C. Dunn. I think this is an issue with some recent code changes in CVS... See these threads: critical BOOT failure updating to latest 5-Stable (5.4) 9/23/2005 12:07 AM ATA lockup with 5.4-STABLE 9/21/2005 10:19 PM I have privately emailed Mr. Dunn, and his problem seems a little different perhaps, but I see some similarities. His system is an IBM (so is mine) and his uses the Intel PIIX4 ata chipset. Mine uses the PIIX3. Mine is by far the oldest, and yours is the newest system. Of note maybe is that I was also using an older drive as you are, in my case an 8 or 9 GB Quantum Fireball. Anyway, I count three systems that are normally boting with 5.3 or 5.4, and then the upgrade to the latest 5-Stable breaks the boot. Perhaps you could test one of those identical machines with a simple hard disk swap? Just put the bad booting drive in a working system and see if the error is still there? Has anyone checked the CVS repository for a possible change to the ATA detection or boot code? Can you post your dmesg for 5.3 perhaps? BTW, you can boot that machine to the old kernel using the procedure unload load /boot/kernel.old/kernel boot (or boot -v) Do all of that with option 6 on the Boot Loader menu. Thanks, Billy Tim Howe wrote: I've got a machine here that I'm trying to install FreeBSD 5.4 on. It's identical (except for the hard drive) to another machine that I ran the 4.x series on for some time with no issues. I've got several other Pentium 3-based machines running 5.4-RELEASE-p3 with a GENERIC kernel, and I have a 5.3 installer disk, so my strategy was to do a minimal install of 5.3, then NFS mount /usr/src and /usr/obj from my organizational build server and upgrade to 5.4 from there. The 5.3 install went smoothly, make installkernel went smoothly, but when I tried to reboot I got an error saying that it couldn't find the root filesystem. Further investigation found that it wasn't able to find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM drive (master on ata0). I verified that the drive had not gone bad by again booting off the 5.3 installer disk, which found ad0 with no difficulty. I then downloaded the 5.4 mini-CD, which was unable to find ad0. Finally, I swapped in another hard drive with identical results. Neither booting with ACPI disabled (didn't bother to check whether this machine even has it) nor booting in safe mode helped at all. I did happen to notice that when the 5.3 CD boots, there is a delay of several seconds when probing ata0. Could this be a timing issue with regard to the controller? The machine is a Gateway ATXSTF FED Pro M1000 with a 1GHz Pentium III and 256MB of RAM. It has an onboard Intel ICH2 UDMA100 controller. The first HDD I tried was a Western Digital Caviar 32500 2559.8MB drive, and the second was a Caviar 24300 4311.9MB drive. If necessary, I'm willing to build custom kernels for testing purposes or to add debugging statements etc, if anyone can give me pointers in the right direction. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 - 5.4 breaks ATA (Intel ICH2)
I've got a machine here that I'm trying to install FreeBSD 5.4 on. It's identical (except for the hard drive) to another machine that I ran the 4.x series on for some time with no issues. I've got several other Pentium 3-based machines running 5.4-RELEASE-p3 with a GENERIC kernel, and I have a 5.3 installer disk, so my strategy was to do a minimal install of 5.3, then NFS mount /usr/src and /usr/obj from my organizational build server and upgrade to 5.4 from there. The 5.3 install went smoothly, make installkernel went smoothly, but when I tried to reboot I got an error saying that it couldn't find the root filesystem. Further investigation found that it wasn't able to find the ATA HDD (master on ata0) at all, but could find the ATAPI CDROM drive (master on ata0). I verified that the drive had not gone bad by again booting off the 5.3 installer disk, which found ad0 with no difficulty. I then downloaded the 5.4 mini-CD, which was unable to find ad0. Finally, I swapped in another hard drive with identical results. Neither booting with ACPI disabled (didn't bother to check whether this machine even has it) nor booting in safe mode helped at all. I did happen to notice that when the 5.3 CD boots, there is a delay of several seconds when probing ata0. Could this be a timing issue with regard to the controller? The machine is a Gateway ATXSTF FED Pro M1000 with a 1GHz Pentium III and 256MB of RAM. It has an onboard Intel ICH2 UDMA100 controller. The first HDD I tried was a Western Digital Caviar 32500 2559.8MB drive, and the second was a Caviar 24300 4311.9MB drive. If necessary, I'm willing to build custom kernels for testing purposes or to add debugging statements etc, if anyone can give me pointers in the right direction. Thanks in advance. -- Tim Howe Software Engineer Celebrity Resorts, Inc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
