|
»
»
[FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
|
View:
New views
19 Messages
—
Rating Filter:
Alert me
|
 |
[FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Fernan Aguero
::
Rate this Message:
Hi,
I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have not seen other more recent posts about this issue ... is it because it's already fixed and working fine for everyone? http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081429.html http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html Thanks in advance for any update on this, -- fernan _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Jeremy Chadwick-3
::
Rate this Message:
On Tue, Sep 30, 2008 at 06:34:04PM -0300, Fernan Aguero wrote:
> I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which > I'd like to try installing FreeBSD. I've already failed to make 7.0 > work on this box and was wondering if you have information about the > behavior of the upcoming 7.1 on this hardware. Why don't you try a 7.1-PRERELEASE ISO and see if it works for you? ftp://ftp4.freebsd.org/pub/FreeBSD/snapshots/200809/ > I've been following the "HT1000 chipset errata saga" thread, and the > commits by sos@ to CVS (around Jan 2008), but have not seen other more > recent posts about this issue ... is it because it's already fixed and > working fine for everyone? > > http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081429.html > http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html Wow; the 2nd URL there is major/huge. I feel sorry for anyone having to deal with this problem. I'll update my Wiki page to reflect this data; thanks for bringing it (indirectly) to my attention. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
|
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by John Baldwin
::
Rate this Message:
On Tuesday 30 September 2008 05:34:04 pm Fernan Aguero wrote:
> Hi, > > I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which > I'd like to try installing FreeBSD. I've already failed to make 7.0 > work on this box and was wondering if you have information about the > behavior of the upcoming 7.1 on this hardware. > > I've been following the "HT1000 chipset errata saga" thread, and the > commits by sos@ to CVS (around Jan 2008), but have not seen other more > recent posts about this issue ... is it because it's already fixed and > working fine for everyone? > > http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081429.html > http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html > > Thanks in advance for any update on this, Try http://www.freebsd.org/~jhb/patches/ata_ht1000.patch -- John Baldwin _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Fernan Aguero
::
Rate this Message:
> At 05:34 PM 9/30/2008, Fernan Aguero wrote:
> >> I've been following the "HT1000 chipset errata saga" thread, and the >> commits by sos@ to CVS (around Jan 2008), but have not seen other more >> recent posts about this issue ... is it because it's already fixed and >> working fine for everyone? >> >> http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html > > Yes, we ran into this yesterday on a fresh install using the 7.1 beta CD as > it was set to PATA mode by accident. Also, on some earlier BIOS revs, we > had to turn off "enable USB legacy mode" as well as "EHCI handoff". By > default we set those to disabled as it seems to sometimes create a high > interrupt load on the USB bus if its enabled. Thanks for the tip. Unfortunately, the PowerEdge SC1435 BIOS does not allow much options here ... I can set the embedded SATA to 'ATA mode' (corruption hell, tested with 7.1 BETA) or just turn it 'OFF' in which case the FreeBSD installer sees no disk present. This is on BIOS v1.1.2. A newer v1.4.4 is available and I'm now researching how to update the BIOS to see if that helps. > If you forget to set the mode to SATA, the dmesg will look like > > Sep 30 13:37:08 dev2 kernel: ad4: DMA limited to UDMA33, device found > non-ATA66 cable > Sep 30 13:37:08 dev2 kernel: ad4: 152627MB <Seagate ST3160815AS 3.AAD> at > ata2-master UDMA33 > > and you will indeed get corruption > > Turning onto normal SATA mode in the BIOS, you should see > > Sep 30 16:14:15 dev2 kernel: ad4: 152627MB <Seagate ST3160815AS 3.AAD> at > ata2-master SATA150 > > ... And everything works great. > > Start with > ftp://ftp.freebsd.org//pub/FreeBSD/releases/i386/ISO-IMAGES/7.1/7.1-BETA-i386-disc1.iso I've used the amd64 version ... don't know if that makes any difference, though. Fernan _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Mike Tancsa
::
Rate this Message:
At 12:40 PM 10/1/2008, Fernan Aguero wrote:
>Thanks for the tip. > >Unfortunately, the PowerEdge SC1435 BIOS does not allow much >options here ... I can set the embedded SATA to 'ATA mode' >(corruption hell, tested with 7.1 BETA) or just turn it >'OFF' in which case the FreeBSD installer sees no disk >present. >This is on BIOS v1.1.2. A newer v1.4.4 is available and I'm >now researching how to update the BIOS to see if that helps. Wow, thats too bad. Hopefully a newer BIOS will let you put the controller in SATA mode. > > > > Start with > > > ftp://ftp.freebsd.org//pub/FreeBSD/releases/i386/ISO-IMAGES/7.1/7.1-BETA-i386-disc1.iso > >I've used the amd64 version ... don't know if that makes any >difference, though. It wont make a difference in terms of the SATA/PATA issue. However, once you get that fixes, you should be able to install the AMD64 image just fine. I would check the USB settings as well to make sure the "hand off mode" is disabled. ---Mike _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Xin LI-2
::
Rate this Message:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Did anyone who can trigger the data corruption has tried John's patch and let us know if it worked? Cheers, - -- Xin LI <delphij@...> http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjr3mkACgkQi+vbBBjt66CW2gCcC6VaWPA7HE3Pd6CLfa3lkNUz r0MAnAsQI54d28MdeSOYZCQmFguT9EFV =xM/C -----END PGP SIGNATURE----- _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Fernan Aguero
::
Rate this Message:
> Did anyone who can trigger the data corruption has tried John's patch
> and let us know if it worked? Not yet. My problem is that it's not that easy ... (at least for me, but maybe I'm missing something). The main issue for me is that I don't have a spare box running 7.x. All my FreeBSD boxes are running 6.x I've tried to make a new 7.1-BETA bootable ISO from the patched sources (make release), but failed ... this is the first time I've ever attempted this, and it seems that you cannot do that from a 6.x box (I have a full CVS mirror of FreeBSD, and a fresh checkout of RELENG_7). The next thing to do (which I already tried once, and that was also not an painless path) is to boot the box with FreeBSD-6.1 (amd64, no data corruption here) and upgrade to 7.x patching the sources along the way. I need to find a free afternoon in my agenda to fit this ... I will get back with info as soon as I have done it. Fernan _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by John Baldwin
::
Rate this Message:
On Wednesday 08 October 2008 06:15:15 am Fernan Aguero wrote:
> > Did anyone who can trigger the data corruption has tried John's patch > > and let us know if it worked? > > Not yet. My problem is that it's not that easy ... (at least > for me, but maybe I'm missing something). > > The main issue for me is that I don't have a spare box > running 7.x. All my FreeBSD boxes are running 6.x > > I've tried to make a new 7.1-BETA bootable ISO from the > patched sources (make release), but failed ... this is the > first time I've ever attempted this, and it seems that you > cannot do that from a 6.x box (I have a full CVS mirror of > FreeBSD, and a fresh checkout of RELENG_7). You can just grab the existing iso, untar it into a directory, build your own GENERIC kernel and replace the /boot/kernel/kernel in the iso tree, then use mkisofs to build a new ISO. Just be sure that once you've installed the box, you copy the updated kernel onto the box somehow before you reboot from the installer (you can use the fixit shell to help with this). -- John Baldwin _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Fernan Aguero
::
Rate this Message:
> On Wednesday 08 October 2008 06:15:15 am Fernan Aguero wrote:
> > > Did anyone who can trigger the data corruption has tried John's patch > > > and let us know if it worked? > > > > Not yet. My problem is that it's not that easy ... (at least > > for me, but maybe I'm missing something). > > > > The main issue for me is that I don't have a spare box > > running 7.x. All my FreeBSD boxes are running 6.x > > > > I've tried to make a new 7.1-BETA bootable ISO from the > > patched sources (make release), but failed ... this is the > > first time I've ever attempted this, and it seems that you > > cannot do that from a 6.x box (I have a full CVS mirror of > > FreeBSD, and a fresh checkout of RELENG_7). > You can just grab the existing iso, OK > untar it into a directory, OK > build your own GENERIC kernel and replace the > /boot/kernel/kernel in the iso tree, Will I be able to do this using a 7.x checkout on a 6.x box? > then use mkisofs to build a new ISO. Just be sure that > once you've installed the box, you copy the updated kernel > onto the box somehow before you reboot from the installer > (you can use the fixit shell to help with this). Gotcha. > -- > John Baldwin Fernan _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by John Baldwin
::
Rate this Message:
On Wednesday 08 October 2008 04:33:25 pm Fernan Aguero wrote:
> > On Wednesday 08 October 2008 06:15:15 am Fernan Aguero wrote: > > > > Did anyone who can trigger the data corruption has tried John's patch > > > > and let us know if it worked? > > > > > > Not yet. My problem is that it's not that easy ... (at least > > > for me, but maybe I'm missing something). > > > > > > The main issue for me is that I don't have a spare box > > > running 7.x. All my FreeBSD boxes are running 6.x > > > > > > I've tried to make a new 7.1-BETA bootable ISO from the > > > patched sources (make release), but failed ... this is the > > > first time I've ever attempted this, and it seems that you > > > cannot do that from a 6.x box (I have a full CVS mirror of > > > FreeBSD, and a fresh checkout of RELENG_7). > > > You can just grab the existing iso, > > OK > > > untar it into a directory, > > OK > > > build your own GENERIC kernel and replace the > > /boot/kernel/kernel in the iso tree, > > Will I be able to do this using a 7.x checkout on a 6.x box? You can use 'make kernel-toolchain' followed by 'make buildkernel' on a 6.x box to build a 7.x kernel though. -- John Baldwin _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Fernan Aguero
::
Rate this Message:
> On Wednesday 08 October 2008 04:33:25 pm Fernan Aguero wrote:
> > > On Wednesday 08 October 2008 06:15:15 am Fernan Aguero wrote: > > > > > Did anyone who can trigger the data corruption has tried John's patch > > > > > and let us know if it worked? > > > > > > > > Not yet. My problem is that it's not that easy ... (at least > > > > for me, but maybe I'm missing something). > > > > > > > > The main issue for me is that I don't have a spare box > > > > running 7.x. All my FreeBSD boxes are running 6.x > > > > > > > > I've tried to make a new 7.1-BETA bootable ISO from the > > > > patched sources (make release), but failed ... this is the > > > > first time I've ever attempted this, and it seems that you > > > > cannot do that from a 6.x box (I have a full CVS mirror of > > > > FreeBSD, and a fresh checkout of RELENG_7). > > > > > You can just grab the existing iso, > > > > OK > > > > > untar it into a directory, > > > > OK > > > > > build your own GENERIC kernel and replace the > > > /boot/kernel/kernel in the iso tree, > > > > Will I be able to do this using a 7.x checkout on a 6.x box? > > You can use 'make kernel-toolchain' followed by 'make buildkernel' on a 6.x > box to build a 7.x kernel though. > -- > John Baldwin John, thanks for the tip. I have now successfully gone through the process of making a new bootable CD using the ATA_HT1000 patched kernel. I have already done a minimal installation of FreeBSD-7.1-BETA onto the SC1435 PowerEdge box using this CD (BTW dmesg now shows the ad4 disk being recognized as SATA150 instead of giving a warning about a bad cable and recognizing it as an ATA drive). But I'm stuck at the last step ... > Just be sure that once you've installed the box, > you copy the updated kernel onto the box somehow before you > reboot from the > installer (you can use the fixit shell to help with this). I'm at the holographic emergency shell, and df(1) shows all the partitions in ad4s1 mounted under /mnt. So my idea is to cp boot/kernel/kernel /mnt/boot/kernel/ but when I do an ls(1) the /mnt directory appears to be empty ... However I'm unable to umount it! My recollection: $ df -h /dev/ad4s1a => /mnt /dev/ad4s1d => /mnt/tmp /dev/ad4s1e => /mnt/usr ... $ ls /mnt/boot boot: no such file or directory $ ls /mnt/ . .. $ umount /mnt device is busy I'm now downloading a 7.1-BETA-livefs ISO and I'll try next to boot the box with this CD to see if I can scp the kernel from another box ... but any other tip or suggestion is welcome. Fernan _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by John Baldwin
::
Rate this Message:
On Friday 10 October 2008 01:11:17 pm Fernan Aguero wrote:
> John, > > thanks for the tip. I have now successfully gone through > the process of making a new bootable CD using the ATA_HT1000 > patched kernel. > > I have already done a minimal installation of > FreeBSD-7.1-BETA onto the SC1435 PowerEdge box using this CD > (BTW dmesg now shows the ad4 disk being recognized as > SATA150 instead of giving a warning about a bad cable and > recognizing it as an ATA drive). > > But I'm stuck at the last step ... > > > Just be sure that once you've installed the box, > > you copy the updated kernel onto the box somehow before you > > reboot from the > > installer (you can use the fixit shell to help with this). > > I'm at the holographic emergency shell, and df(1) shows all > the partitions in ad4s1 mounted under /mnt. So my idea is to > cp boot/kernel/kernel /mnt/boot/kernel/ > but when I do an ls(1) the /mnt directory appears to be empty ... > > However I'm unable to umount it! > > My recollection: > $ df -h > /dev/ad4s1a => /mnt > /dev/ad4s1d => /mnt/tmp > /dev/ad4s1e => /mnt/usr > ... > $ ls /mnt/boot > boot: no such file or directory > $ ls /mnt/ > . .. > $ umount /mnt > device is busy > > I'm now downloading a 7.1-BETA-livefs ISO and I'll try next to boot > the box with this CD to see if I can scp the kernel from > another box ... but any other tip or suggestion is welcome. Hmmm, that is odd. I wonder if you are chroot'd into the drive somehow? That really shouldn't be though. -- John Baldwin _______________________________________________ freebsd-stable@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@..." |
|
|
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
by Fernan Aguero
::
Rate this Message:
> On Friday 10 October 2008 01:11:17 pm Fernan Aguero wrote:
> > John, > > > > thanks for the tip. I have now successfully gone through > > the process of making a new bootable CD using the ATA_HT1000 > > patched kernel. > > > > I have already done a minimal installation of > > FreeBSD-7.1-BETA onto the SC1435 PowerEdge box using this CD > > (BTW dmesg now shows the ad4 disk being recognized as > > SATA150 instead of giving a warning about a bad cable and > > recognizing it as an ATA drive). > > > > But I'm stuck at the last step ... > > > > > Just be sure that once you've installed the box, > > > you copy the updated kernel onto the box somehow before you > > > reboot from the > > > installer (you can use the fixit shell to help with this). > > > > I'm at the holographic emergency shell, and df(1) shows all > > the partitions in ad4s1 mounted under /mnt. So my idea is to > > cp boot/kernel/kernel /mnt/boot/kernel/ > > but when I do an ls(1) the /mnt directory appears to be empty ... > > > > However I'm unable to umount it! > > > > My recollection: > > $ df -h > > /dev/ad4s1a => /mnt > > /dev/ad4s1d => /mnt/tmp > > /dev/ad4s1e => /mnt/usr > > ... > > $ ls /mnt/boot > > boot: no such file or directory > > $ ls /mnt/ > > . .. > > $ umount /mnt > > device is busy > > > > I'm now downloading a 7.1-BETA-livefs ISO and I'll try next to boot > > the box with this CD to see if I can scp the kernel from > > another box ... but any other tip or suggestion is welcome. > > Hmmm, that is odd. I wonder if you are chroot'd into the drive somehow? That > really shouldn't be though. > > -- > John Baldwin John Sorry for the delay in replying, I had no access to this box for the whole weekend. I finally managed to replace the stock kernel with the patched one before booting with the OS installed on disk. For some reason, the emergency shell launched from the install session had ad4s1 partitions mounted under /mnt and would not give up on them ... I just rebooted the box with the same patched CD, and using the livefs CD managed to bring up the bge0 interface, and replace the stock kernel with the patched one from an nfs-mounted partition. So far everything seems to be working OK ... compiled and installed a couple of ports (vim, screen, apache, portupgrade), and everything looks fine. I can run more thourough tests if you want. Just let me know what those are and guide me through them ... are we still on time for including this patch in the upcoming 7.1? Will there be a new beta or RC? Fernan PS: Output of dmesg (7.1-BETA w/ata_ht1000.patch) ===================================================================== Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-BETA #0: Fri Oct 10 09:53:34 ART 2008 fernan@...:/usr/obj/raid10/freebsd/freebsd-7.1-beta/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2210 (1795.51-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f13 Stepping = 3 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x2001<SSE3,CX16> AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8> Cores per package: 2 usable memory = 8575381504 (8178 MB) avail memory = 8295841792 (7911 MB) ACPI APIC Table: <DELL PE_SC3 > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic1: Changing APIC ID to 5 ioapic2: Changing APIC ID to 6 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 <Version 1.1> irqs 0-15 on motherboard ioapic1 <Version 1.1> irqs 32-47 on motherboard ioapic2 <Version 1.1> irqs 64-79 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: <DELL PE_SC3> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0 pci3: <ACPI PCI bus> on pcib1 pcib2: <ACPI PCI-PCI bridge> at device 13.0 on pci3 pci4: <ACPI PCI bus> on pcib2 atapci0: <ServerWorks HT1000 SATA150 controller> port 0xecb0-0xecb7,0xeca0-0xeca3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdfffff irq 6 at device 14.0 on pci3 atapci0: [ITHREAD] ata2: <ATA channel 0> on atapci0 ata2: [ITHREAD] ata3: <ATA channel 1> on atapci0 ata3: [ITHREAD] ata4: <ATA channel 2> on atapci0 ata4: [ITHREAD] ata5: <ATA channel 3> on atapci0 ata5: [ITHREAD] atapci1: <ServerWorks HT1000 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8c0-0x8cf at device 2.1 on pci0 ata0: <ATA channel 0> on atapci1 ata0: [ITHREAD] ata1: <ATA channel 1> on atapci1 ata1: [ITHREAD] isab0: <PCI-ISA bridge> at device 2.2 on pci0 isa0: <ISA bus> on isab0 ohci0: <OHCI (generic) USB controller> port 0xd000-0xd0ff mem 0xefbed000-0xefbedfff irq 11 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: <OHCI (generic) USB controller> on ohci0 usb0: USB revision 1.0 uhub0: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: <OHCI (generic) USB controller> port 0xd400-0xd4ff mem 0xefbee000-0xefbeefff irq 11 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: <OHCI (generic) USB controller> on ohci1 usb1: USB revision 1.0 uhub1: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: <EHCI (generic) USB 2.0 controller> port 0xd800-0xd8ff mem 0xefbef000-0xefbeffff irq 11 at device 3.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: <EHCI (generic) USB 2.0 controller> on ehci0 usb2: USB revision 2.0 uhub2: <(0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2 uhub2: 4 ports with 4 removable, self powered uhub3: <vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2> on uhub2 uhub3: multiple transaction translators uhub3: 2 ports with 2 removable, self powered ums0: <Genius Optical Mouse, class 0/0, rev 1.10/1.07, addr 3> on uhub3 ums0: 3 buttons and Z dir. ukbd0: <vendor 0x1241 USB Keyboard, class 0/0, rev 1.10/2.80, addr 4> on uhub3 kbd2 at ukbd0 uhid0: <vendor 0x1241 USB Keyboard, class 0/0, rev 1.10/2.80, addr 4> on uhub3 vgapci0: <VGA-compatible display> port 0xdc00-0xdcff mem 0xe0000000-0xe7ffffff,0xefbf0000-0xefbfffff irq 44 at device 4.0 on pci0 pcib3: <ACPI PCI-PCI bridge> irq 32 at device 7.0 on pci0 pci5: <ACPI PCI bus> on pcib3 pcib4: <ACPI PCI-PCI bridge> irq 33 at device 8.0 on pci0 pci1: <ACPI PCI bus> on pcib4 bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201> mem 0xefef0000-0xefefffff irq 33 at device 0.0 on pci1 miibus0: <MII bus> on bge0 brgphy0: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:1a:a0:1e:3c:3b bge0: [ITHREAD] pcib5: <ACPI PCI-PCI bridge> irq 37 at device 9.0 on pci0 pci2: <ACPI PCI bus> on pcib5 bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201> mem 0xefff0000-0xefffffff irq 37 at device 0.0 on pci2 miibus1: <MII bus> on bge1 brgphy1: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:1a:a0:1e:3c:3c bge1: [ITHREAD] pcib6: <ACPI PCI-PCI bridge> irq 35 at device 10.0 on pci0 pci6: <ACPI PCI bus> on pcib6 pcib7: <ACPI PCI-PCI bridge> irq 36 at device 11.0 on pci0 pci7: <ACPI PCI bus> on pcib7 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] cpu0: <ACPI CPU> on acpi0 powernow0: <PowerNow! K8> on cpu0 device_attach: powernow0 attach returned 6 cpu1: <ACPI CPU> on acpi0 powernow1: <PowerNow! K8> on cpu1 device_attach: powernow1 attach returned 6 cpu2: <ACPI CPU> on acpi0 powernow2: <PowerNow! K8> on cpu2 device_attach: powernow2 attach returned 6 cpu3: <ACPI CPU> on acpi0 powernow3: <PowerNow! K8> on cpu3 device_attach: powernow3 attach returned 6 orm0: <ISA Option ROMs> at iomem 0xc0000-0xc8fff,0xc9000-0xc9fff,0xca000-0xcb7ff,0xec000-0xeffff on isa0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: cannot reserve I/O port range sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDRW <TSSTcorpCD-RW/DVD-ROM TSL462D/DE04> at ata0-master UDMA33 ad4: 152587MB <WDC WD1600JS-75NCB3 10.02E04> at ata2-master SATA150 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/ad4s1a bge0: link state changed to UP Output of dmesg (7.0-RELEASE, corruption hell) ===================================================================== Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 root@...:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2210 (1800.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f13 Stepping = 3 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x2001<SSE3,CX16> AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8> Cores per package: 2 usable memory = 8571883520 (8174 MB) avail memory = 8292429824 (7908 MB) ACPI APIC Table: <DELL PE_SC3 > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic1: Changing APIC ID to 5 ioapic2: Changing APIC ID to 6 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 <Version 1.1> irqs 0-15 on motherboard ioapic1 <Version 1.1> irqs 32-47 on motherboard ioapic2 <Version 1.1> irqs 64-79 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18) acpi0: <DELL PE_SC3> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: <ACPI CPU> on acpi0 powernow0: <PowerNow! K8> on cpu0 device_attach: powernow0 attach returned 6 cpu1: <ACPI CPU> on acpi0 powernow1: <PowerNow! K8> on cpu1 device_attach: powernow1 attach returned 6 cpu2: <ACPI CPU> on acpi0 powernow2: <PowerNow! K8> on cpu2 device_attach: powernow2 attach returned 6 cpu3: <ACPI CPU> on acpi0 powernow3: <PowerNow! K8> on cpu3 device_attach: powernow3 attach returned 6 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0 pci3: <ACPI PCI bus> on pcib1 pcib2: <ACPI PCI-PCI bridge> at device 13.0 on pci3 pci4: <ACPI PCI bus> on pcib2 atapci0: <ServerWorks HT1000 SATA150 controller> port 0xecb0-0xecb7,0xeca0-0xeca3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdfffff irq 6 at device 14.0 on pci3 atapci0: [ITHREAD] ata2: <ATA channel 0> on atapci0 ata2: [ITHREAD] ata3: <ATA channel 1> on atapci0 ata3: [ITHREAD] atapci1: <ServerWorks HT1000 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8c0-0x8cf at device 2.1 on pci0 ata0: <ATA channel 0> on atapci1 ata0: [ITHREAD] ata1: <ATA channel 1> on atapci1 ata1: [ITHREAD] isab0: <PCI-ISA bridge> at device 2.2 on pci0 isa0: <ISA bus> on isab0 ohci0: <OHCI (generic) USB controller> port 0xd000-0xd0ff mem 0xefbed000-0xefbedfff irq 11 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: <OHCI (generic) USB controller> on ohci0 usb0: USB revision 1.0 uhub0: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: <OHCI (generic) USB controller> port 0xd400-0xd4ff mem 0xefbee000-0xefbeefff irq 11 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: <OHCI (generic) USB controller> on ohci1 usb1: USB revision 1.0 uhub1: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: <EHCI (generic) USB 2.0 controller> port 0xd800-0xd8ff mem 0xefbef000-0xefbeffff irq 11 at device 3.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: <EHCI (generic) USB 2.0 controller> on ehci0 usb2: USB revision 2.0 uhub2: <(0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2 uhub2: 4 ports with 4 removable, self powered uhub3: <vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2> on uhub2 uhub3: multiple transaction translators uhub3: 2 ports with 2 removable, self powered ums0: <Logitech Optical USB Mouse, class 0/0, rev 2.00/3.40, addr 3> on uhub3 ums0: 3 buttons and Z dir. ukbd0: <Dell Dell USB Keyboard, class 0/0, rev 1.10/3.01, addr 4> on uhub3 kbd2 at ukbd0 vgapci0: <VGA-compatible display> port 0xdc00-0xdcff mem 0xe0000000-0xe7ffffff,0xefbf0000-0xefbfffff irq 44 at device 4.0 on pci0 pcib3: <ACPI PCI-PCI bridge> irq 32 at device 7.0 on pci0 pci5: <ACPI PCI bus> on pcib3 pcib4: <ACPI PCI-PCI bridge> irq 33 at device 8.0 on pci0 pci1: <ACPI PCI bus> on pcib4 bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201> mem 0xefef0000-0xefefffff irq 33 at device 0.0 on pci1 miibus0: <MII bus> on bge0 brgphy0: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:1a:a0:1e:3c:3b bge0: [ITHREAD] pcib5: <ACPI PCI-PCI bridge> irq 37 at device 9.0 on pci0 pci2: <ACPI PCI bus> on pcib5 bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4201> mem 0xefff0000-0xefffffff irq 37 at device 0.0 on pci2 miibus1: <MII bus> on bge1 brgphy1: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:1a:a0:1e:3c:3c bge1: [ITHREAD] pcib6: <ACPI PCI-PCI bridge> irq 35 at device 10.0 on pci0 pci6: <ACPI PCI bus> on pcib6 pcib7: <ACPI PCI-PCI bridge> irq 36 at device 11.0 on pci0 pci7: <ACPI PCI bus> on pcib7 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] orm0: <ISA Option ROMs> at iomem 0xc0000-0xc8fff,0xc9000-0xc9fff,0xec000-0xeffff on isa0 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: <AT Keyboard> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: cannot reserve I/O port range sc0: <System console> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec hptrr: no controller detected. md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xffffffff80bc6c08 acd0: CDRW <TSSTcorpCD-RW/DVD-ROM TSL462D/DE04> at ata0-master UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 152587MB <WDC WD1600JS-75NCB3 10.02E04> at ata2-master UDMA33 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install. GEOM_LABEL: Label for provider ad4s1 is msdosfs/DellUtility. Trying to mount root from ufs:/dev/md0 GEOM_LABEL: Label msdosfs/DellUtility removed. Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...1 0 0 done All buffers synced. Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 root@...:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2210 (1800.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f13 Stepping = 3 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x2001<SSE3,CX16> AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x1f<LAHF,CMP,SVM,ExtAPIC,CR8> Cores per package: 2 usable memory = 8576077824 (8178 MB) avail memory = 8296632320 (7912 MB) ACPI APIC Table: <DELL PE_SC3 > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic1: Changing APIC ID to 5 ioapic2: Changing APIC ID to 6 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 <Version 1.1> irqs 0-15 on motherboard ioapic1 <Version 1.1> irqs 32-47 on motherboard ioapic2 <Version 1.1> irqs 64-79 on |
