Server mit 192 GB RAM bootet nicht

H

handwerker

Well-Known Member
Hi !

Ich habe in der Firma gerade einen neuen Server als Virtualisierungs Host geliefert bekommen und wollte zu Testzwecken mal FreeBSD 9.1 von USB booten.

Der Server ist ein Dell Poweredge R720 mit 2 6-Kern CPUs und 192 GB RAM.

Booten wollte ich
FreeBSD-9.1-RELEASE-amd64-memstick.img

Bootloader klappt noch, beim Boot des Kernels hängt er sich auf.

Muss ich irgendwelche Kernel Optionen angeben damit das klappt ?
 
Warte einfach mal ein paar Sekunden länger. Habe ich bei einem Server mit 144GB auch. Das dauert eben länger, bis der Bildschirm weiter scrollt... :)
 
Ich habe hier nicht die Hardware das zu reproduzieren, aber das klingt jetzt nicht so prickelnd. Würde ich auf jeden Fall mal auf stable@ posten, wenn der Kernel für eine Weile hängt. Da läuft dann ja wohl offensichtlich etwas aus dem Ruder. Ich würde vermuten irgendein Integritätstest skaliert nicht linear.
 
Es ist völlig normal, dass der Kernel bei sehr großen RAM-Mengen mehrere Minuten(!) brauchen kann, bevor er auch nur die erste Zeile ausgibt. Das liegt an FreeBSDs paranoiden RAM-Check, der sicherstellt dass RAM auch wirklich RAM ist. Man kann (und sollte) den auf wirklich dicken Kisten allerdings abschalten: hw.memtest.tests=0 (ins Loader-Prompt hauen oder in die loader.conf tippen)

Allerdings ist das FreeBSD-Team sehr an Erfahrungsberichten mit Kisten mit extrem viel RAM interessiert. Die sind einfach selten, aber aus Entwicklersicht höchst interessant. Daher, egal ob es geht oder nicht; Schreibe eine kurze Mail mit dmesg und wie zufrieden du bist an freebsd-current@ :)
 
Mal so aus Neugier, was soll es sonst sein? Gibt es ein BIOS, dass dem System eine Festplatte per memory mapped IO als RAM unterjubeln kann? Oder Hardware die SATA auf DDR abbildet?
 
Zuletzt bearbeitet:
Früher, vor langer Zeit, gab es tatsächlich Maschinen, die irgendwelche Mappings und ähnliches als RAM deklarierten. (Free)BSD wäre darüber gestolpert, daher versucht er sie zu erkennen und anschließend zu ignorieren. Da Windows und Linux sowas schon ewig nicht mehr machen, ist es auch unter FreeBSD unnötig. Warum man den Mist unter FreeBSD nicht einfach abschafft? Ich fasse die wirklich extrem lange Diskussion dazu mal so zusammen: Ich finde, dass der Fahrradschuppen lila gestrichen werden sollte!
 
ich nehme einfach mal an dass die lila fahrradschuppenmenschen dieses problem einfach noch nicht erkannt haben, weil ihre kisten wohl noch mit maximal 4gb laufen.

ein mehrerer minuten langer boot ist in meinen augen aber auch nicht hinnehmbar. zumindest ein prozessbalken oder eine meldung "this might take several minutes" waeren doch schoen, oder?

frage an den threadersteller: lief es denn nachher?
 
Hoi,
wir könnten alle Farben oifach in oin Topf werfen, rumrühren und dann mit dem streichen wo da bei rum kümmts :) - dat wär doch was oda ?
D.h. abschalten per default aktiv - wer`s trotzdem ham will solls einschalten.

Gruß Bummibär
 
Wahrscheinlich handelt es sich dabei um irgendwelche Uraltkisten und es würde reichen den Test für 64Bit Architekturen auszuschalten. Die sollten rundum neu genug sein um nicht mit solchem Firlefanz konfrontiert zu werden.
 
Yamagi schrieb:
Es ist völlig normal, dass der Kernel bei sehr großen RAM-Mengen mehrere Minuten(!) brauchen kann, bevor er auch nur die erste Zeile ausgibt. Das liegt an FreeBSDs paranoiden RAM-Check, der sicherstellt dass RAM auch wirklich RAM ist. Man kann (und sollte) den auf wirklich dicken Kisten allerdings abschalten: hw.memtest.tests=0 (ins Loader-Prompt hauen oder in die loader.conf tippen)

Allerdings ist das FreeBSD-Team sehr an Erfahrungsberichten mit Kisten mit extrem viel RAM interessiert. Die sind einfach selten, aber aus Entwicklersicht höchst interessant. Daher, egal ob es geht oder nicht; Schreibe eine kurze Mail mit dmesg und wie zufrieden du bist an freebsd-current@ :)
Zum Vergrößern anklicken....

Also ein dual Hexacore mit 96GiB RAM bootet zwar langsam funktioniert anschließend aber wunderbar.
 
Kamikaze schrieb:
Mal so aus Neugier, was soll es sonst sein? Gibt es ein BIOS, dass dem System eine Festplatte per memory mapped IO als RAM unterjubeln kann? Oder Hardware die SATA auf DDR abbildet?
Zum Vergrößern anklicken....

Ein Memory hole oder memory mapped I/O von PCI Devices. Zum krönenden Abschluss kann ein Puffer auf einem PCI Device durchaus als (langsames) RAM funktionieren. Solange bis das PCI Device diesen Speicher mit etwas anderem überschreibt.
 
Ich dachte immer das Betriebssystem weißt die Adressen für Memory-Mapped IO zu (Grafikspeicher etwa). Dass das einfach so hochkommen kann klingt relativ unangenehm.
 
Kamikaze schrieb:
Ich dachte immer das Betriebssystem weißt die Adressen für Memory-Mapped IO zu (Grafikspeicher etwa). Dass das einfach so hochkommen kann klingt relativ unangenehm.
Zum Vergrößern anklicken....

Nach meinem Verständnis sollte das auch nicht passieren. Ich hatte so etwas nur beim Versuch FreeBSD auf meinem früheren MacBook zu booten. Apples BIOS Kompatibilitätsmodus hat die Hardware so verstellt hinterlassen, dass der zweite Core eine widersprüchliche Ansicht über das RAM hatte. Dem Zweiten Core fehlte die ersten 2GiB RAM. Der alte FreeBSD 7 Kernel kam damit klar, weil er die Zweite Kopie der Daten nicht nie las. Also habe ich den Kernel misshandelt und das ganze durch ein paar Konstanten ersetzt. Danach bootet der Kernel allerdings nur noch auf genau diesem Rechner.
 
Ich bin auch schon oefters drauf reingefallen und warum das fuer amd64 nicht deaktiviert wurde, kann ich auch nicht verstehen. Habe eben mal in den Code geguckt, um zu sehen, was der da eigentlich treibt und dabei gesehen, das es zB fuer VMs abgeschaltet ist (in 9.1 zumindest). Das erklaert warum meine 256 GB RAM VM schnell bootete, aber eine Kiste mit 512 GB >15 Minuten gebraucht hat um hoch zu kommen.
Jedenfalls ist es auch interessant wie er das checkt: Er schreibt einfach verschiedene Muster auf die Speicheradressen wie 010..., 101..., nur Nullen und Einsen und liest die Gruetze dann wieder zurueck. Wie das einem klar machen soll, das sich dahinter RAM verbirgt ist mir allerdings nicht klar. Das koennte auch sonst was fuer Speicher sein, warum auch immer man das tun sollte sei mal dahingestellt. Zumindest alles was nur lesbar, oder schreibbar ist kriegt man so gefiltert.

Edit:
Man koennte natuerlich auch hingehen und gucken, was sich mit, sagen wir mal mehr als 8 Gb Speicher meldet, braucht diesen Check sicher nicht.
 
Wie gesagt, dieser Check ist ein Relikt aus einer anderen Zeit. Heute ist er schon aus dem Grund nicht notwendig, da Windows und Linux keine vergleichbare Funktionalität bieten. Oder anders gesagt: Wenn Hardware diesen Check benötigt, werden Windows und Linux nicht auf ihr laufen. Und ich glaube viel, aber nicht, dass jemand zu Windows und Linux inkompatible Systeme baut. :)

In VMs ist er abgeschaltet, weil ein stumpfes Überschreiben des RAMs die verschiedenen Speicheroptimierungsmechanismen einer VM sehr erfolgreich aus dem Tritt bringt. In normalen Systemen ist er nicht abgeschaltet, weil die zugehörige Diskussion lang und fruchtlos war. Wer mag, kann mal versuchen, ob er sie in den Archiven der Listen noch findet.
 
Hi !
Ich habe es nochmal versucht:
Ergebnis: Es funktioniert
Nach dem Boot-Splash Bildschirm dauert es 3 Minuten in denen sich nichts am Bildschirm tut,
dann kommen die Kernel Meldungen wie üblich...
 
Okay. Dann setzte das oben schon erwähnte hw.memtest.tests=0 in der /boot/loader.conf und in Zukunft wird er sofort starten. :)
 
So schaut der dmesg aus ...

Für die Spielkinder: So schaut der dmesg der Kiste aus:

Code: 
Copyright (c) 1992-2012 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 9.1-RELEASE #0 r243825: Tue Dec  4 09:23:10 UTC 2012
    root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
CPU: Intel(R) Xeon(R) CPU E5-2667 0 @ 2.90GHz (2900.06-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x206d7  Family = 6  Model = 2d  Stepping = 7
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x1fbee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant, performance statistics
real memory  = 206158430208 (196608 MB)
avail memory = 198729396224 (189523 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <DELL   PE_SC3  >
FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 SMT threads
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
 cpu8 (AP): APIC ID:  8
 cpu9 (AP): APIC ID:  9
 cpu10 (AP): APIC ID: 10
 cpu11 (AP): APIC ID: 11
 cpu12 (AP): APIC ID: 32
 cpu13 (AP): APIC ID: 33
 cpu14 (AP): APIC ID: 34
 cpu15 (AP): APIC ID: 35
 cpu16 (AP): APIC ID: 36
 cpu17 (AP): APIC ID: 37
 cpu18 (AP): APIC ID: 38
 cpu19 (AP): APIC ID: 39
 cpu20 (AP): APIC ID: 40
 cpu21 (AP): APIC ID: 41
 cpu22 (AP): APIC ID: 42
 cpu23 (AP): APIC ID: 43
ioapic1: Changing APIC ID to 1
ioapic2: Changing APIC ID to 2
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 32-55 on motherboard
ioapic2 <Version 2.0> irqs 64-87 on motherboard
kbd1 at kbdmux0
acpi0: <DELL PE_SC3> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
cpu8: <ACPI CPU> on acpi0
cpu9: <ACPI CPU> on acpi0
cpu10: <ACPI CPU> on acpi0
cpu11: <ACPI CPU> on acpi0
cpu12: <ACPI CPU> on acpi0
cpu13: <ACPI CPU> on acpi0
cpu14: <ACPI CPU> on acpi0
cpu15: <ACPI CPU> on acpi0
cpu16: <ACPI CPU> on acpi0
cpu17: <ACPI CPU> on acpi0
cpu18: <ACPI CPU> on acpi0
cpu19: <ACPI CPU> on acpi0
cpu20: <ACPI CPU> on acpi0
cpu21: <ACPI CPU> on acpi0
cpu22: <ACPI CPU> on acpi0
cpu23: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x7f irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x5f irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 450
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
Event timer "HPET5" frequency 14318180 Hz quality 440
Event timer "HPET6" frequency 14318180 Hz quality 440
Event timer "HPET7" frequency 14318180 Hz quality 440
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 53 at device 1.0 on pci0
pci2: <ACPI PCI bus> on pcib1
bge0: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd50a0000-0xd50affff,0xd50b0000-0xd50bffff,0xd50c0000-0xd50cffff irq 34 at device 0.0 on pci2
bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus0: <MII bus> on bge0
brgphy0: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Ethernet address: 90:b1:1c:31:f6:88
bge1: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd50d0000-0xd50dffff,0xd50e0000-0xd50effff,0xd50f0000-0xd50fffff irq 36 at device 0.1 on pci2
bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus1: <MII bus> on bge1
brgphy1: <BCM5720C 1000BASE-T media interface> PHY 2 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge1: Ethernet address: 90:b1:1c:31:f6:89
pcib2: <ACPI PCI-PCI bridge> irq 53 at device 1.1 on pci0
pci1: <ACPI PCI bus> on pcib2
bge2: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd51a0000-0xd51affff,0xd51b0000-0xd51bffff,0xd51c0000-0xd51cffff irq 35 at device 0.0 on pci1
bge2: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
bge2: Try again
miibus2: <MII bus> on bge2
brgphy2: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus2
brgphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge2: Ethernet address: 90:b1:1c:31:f6:86
bge3: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd51d0000-0xd51dffff,0xd51e0000-0xd51effff,0xd51f0000-0xd51fffff irq 38 at device 0.1 on pci1
bge3: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus3: <MII bus> on bge3
brgphy3: <BCM5720C 1000BASE-T media interface> PHY 2 on miibus3
brgphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge3: Ethernet address: 90:b1:1c:31:f6:87
pcib3: <ACPI PCI-PCI bridge> irq 53 at device 2.0 on pci0
pci4: <ACPI PCI bus> on pcib3
isp0: <Qlogic ISP 2532 PCI FC-AL Adapter> port 0xe800-0xe8ff mem 0xd9ff8000-0xd9ffbfff irq 40 at device 0.0 on pci4
isp1: <Qlogic ISP 2532 PCI FC-AL Adapter> port 0xec00-0xecff mem 0xd9ffc000-0xd9ffffff irq 44 at device 0.1 on pci4
pcib4: <ACPI PCI-PCI bridge> irq 53 at device 2.2 on pci0
pci3: <ACPI PCI bus> on pcib4
mfi0: <Drake Skinny> port 0xfc00-0xfcff mem 0xdaffc000-0xdaffffff,0xdaf80000-0xdafbffff irq 42 at device 0.0 on pci3
mfi0: Using MSI
mfi0: Megaraid SAS driver Ver 4.23 
pcib5: <ACPI PCI-PCI bridge> irq 53 at device 3.0 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> irq 53 at device 3.2 on pci0
pci6: <ACPI PCI bus> on pcib6
bge4: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd52a0000-0xd52affff,0xd52b0000-0xd52bffff,0xd52c0000-0xd52cffff irq 50 at device 0.0 on pci6
bge4: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus4: <MII bus> on bge4
brgphy4: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus4
brgphy4:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge4: Ethernet address: 00:10:18:f6:b6:d4
bge5: <Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000> mem 0xd52d0000-0xd52dffff,0xd52e0000-0xd52effff,0xd52f0000-0xd52fffff irq 53 at device 0.1 on pci6
bge5: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus5: <MII bus> on bge5
brgphy5: <BCM5720C 1000BASE-T media interface> PHY 2 on miibus5
brgphy5:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge5: Ethernet address: 00:10:18:f6:b6:d5
pci0: <base peripheral> at device 5.0 (no driver attached)
pci0: <base peripheral> at device 5.2 (no driver attached)
pcib7: <PCI-PCI bridge> irq 16 at device 17.0 on pci0
pci7: <PCI bus> on pcib7
pci0: <simple comms> at device 22.0 (no driver attached)
pci0: <simple comms> at device 22.1 (no driver attached)
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdd0fd000-0xdd0fd3ff irq 23 at device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
pcib8: <ACPI PCI-PCI bridge> at device 28.0 on pci0
device_attach: pcib8 attach returned 6
pcib8: <ACPI PCI-PCI bridge> irq 19 at device 28.7 on pci0
pci9: <ACPI PCI bus> on pcib8
pcib9: <PCI-PCI bridge> at device 0.0 on pci9
pci10: <PCI bus> on pcib9
pcib10: <PCI-PCI bridge> at device 0.0 on pci10
pci11: <PCI bus> on pcib10
pcib11: <PCI-PCI bridge> at device 0.0 on pci11
pci12: <PCI bus> on pcib11
vgapci0: <VGA-compatible display> mem 0xd4000000-0xd4ffffff,0xdc7fc000-0xdc7fffff,0xdb800000-0xdbffffff irq 19 at device 0.0 on pci12
pcib12: <PCI-PCI bridge> at device 1.0 on pci10
pci13: <PCI bus> on pcib12
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xdd0fe000-0xdd0fe3ff irq 22 at device 29.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci1
pcib13: <PCI-PCI bridge> at device 30.0 on pci0
pci14: <PCI bus> on pcib13
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci0: <Intel Patsburg AHCI SATA controller> port 0xdce8-0xdcef,0xdcf8-0xdcfb,0xdcf0-0xdcf7,0xdcfc-0xdcff,0xdcc0-0xdcdf mem 0xdd0ff000-0xdd0ff7ff irq 20 at device 31.2 on pci0
ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
pcib14: <ACPI Host-PCI bridge> on acpi0
pci64: <ACPI PCI bus> on pcib14
pcib15: <ACPI PCI-PCI bridge> irq 85 at device 1.0 on pci64
pci65: <ACPI PCI bus> on pcib15
pcib16: <ACPI PCI-PCI bridge> irq 85 at device 2.0 on pci64
pci66: <ACPI PCI bus> on pcib16
pcib17: <ACPI PCI-PCI bridge> irq 85 at device 3.0 on pci64
pci67: <ACPI PCI bus> on pcib17
pcib18: <ACPI PCI-PCI bridge> irq 85 at device 3.2 on pci64
pci68: <ACPI PCI bus> on pcib18
pci64: <base peripheral> at device 5.0 (no driver attached)
pci64: <base peripheral> at device 5.2 (no driver attached)
pcib19: <ACPI Host-PCI bridge> on acpi0
pci63: <ACPI PCI bus> on pcib19
pci63: <base peripheral> at device 8.0 (no driver attached)
pci63: <base peripheral> at device 9.0 (no driver attached)
pci63: <base peripheral> at device 10.0 (no driver attached)
pci63: <base peripheral> at device 10.1 (no driver attached)
pci63: <base peripheral> at device 10.2 (no driver attached)
pci63: <base peripheral> at device 10.3 (no driver attached)
pci63: <base peripheral> at device 11.0 (no driver attached)
pci63: <base peripheral> at device 11.3 (no driver attached)
pci63: <base peripheral> at device 12.0 (no driver attached)
pci63: <base peripheral> at device 12.1 (no driver attached)
pci63: <base peripheral> at device 12.2 (no driver attached)
pci63: <base peripheral> at device 12.6 (no driver attached)
pci63: <base peripheral> at device 12.7 (no driver attached)
pci63: <base peripheral> at device 13.0 (no driver attached)
pci63: <base peripheral> at device 13.1 (no driver attached)
pci63: <base peripheral> at device 13.2 (no driver attached)
pci63: <base peripheral> at device 13.6 (no driver attached)
pci63: <base peripheral> at device 14.0 (no driver attached)
pci63: <dasp> at device 14.1 (no driver attached)
pci63: <base peripheral> at device 15.0 (no driver attached)
pci63: <base peripheral> at device 15.1 (no driver attached)
pci63: <base peripheral> at device 15.2 (no driver attached)
pci63: <base peripheral> at device 15.3 (no driver attached)
pci63: <base peripheral> at device 15.4 (no driver attached)
pci63: <base peripheral> at device 15.5 (no driver attached)
pci63: <base peripheral> at device 15.6 (no driver attached)
pci63: <base peripheral> at device 16.0 (no driver attached)
pci63: <base peripheral> at device 16.1 (no driver attached)
pci63: <base peripheral> at device 16.2 (no driver attached)
pci63: <base peripheral> at device 16.3 (no driver attached)
pci63: <base peripheral> at device 16.4 (no driver attached)
pci63: <base peripheral> at device 16.5 (no driver attached)
pci63: <base peripheral> at device 16.6 (no driver attached)
pci63: <base peripheral> at device 16.7 (no driver attached)
pci63: <base peripheral> at device 17.0 (no driver attached)
pci63: <base peripheral> at device 19.0 (no driver attached)
pci63: <dasp> at device 19.1 (no driver attached)
pci63: <dasp> at device 19.4 (no driver attached)
pci63: <dasp> at device 19.5 (no driver attached)
pci63: <base peripheral> at device 19.6 (no driver attached)
pcib20: <ACPI Host-PCI bridge> on acpi0
pci127: <ACPI PCI bus> on pcib20
pci127: <base peripheral> at device 8.0 (no driver attached)
pci127: <base peripheral> at device 9.0 (no driver attached)
pci127: <base peripheral> at device 10.0 (no driver attached)
pci127: <base peripheral> at device 10.1 (no driver attached)
pci127: <base peripheral> at device 10.2 (no driver attached)
pci127: <base peripheral> at device 10.3 (no driver attached)
pci127: <base peripheral> at device 11.0 (no driver attached)
pci127: <base peripheral> at device 11.3 (no driver attached)
pci127: <base peripheral> at device 12.0 (no driver attached)
pci127: <base peripheral> at device 12.1 (no driver attached)
pci127: <base peripheral> at device 12.2 (no driver attached)
pci127: <base peripheral> at device 12.6 (no driver attached)
pci127: <base peripheral> at device 12.7 (no driver attached)
pci127: <base peripheral> at device 13.0 (no driver attached)
pci127: <base peripheral> at device 13.1 (no driver attached)
pci127: <base peripheral> at device 13.2 (no driver attached)
pci127: <base peripheral> at device 13.6 (no driver attached)
pci127: <base peripheral> at device 14.0 (no driver attached)
pci127: <dasp> at device 14.1 (no driver attached)
pci127: <base peripheral> at device 15.0 (no driver attached)
pci127: <base peripheral> at device 15.1 (no driver attached)
pci127: <base peripheral> at device 15.2 (no driver attached)
pci127: <base peripheral> at device 15.3 (no driver attached)
pci127: <base peripheral> at device 15.4 (no driver attached)
pci127: <base peripheral> at device 15.5 (no driver attached)
pci127: <base peripheral> at device 15.6 (no driver attached)
pci127: <base peripheral> at device 16.0 (no driver attached)
pci127: <base peripheral> at device 16.1 (no driver attached)
pci127: <base peripheral> at device 16.2 (no driver attached)
pci127: <base peripheral> at device 16.3 (no driver attached)
pci127: <base peripheral> at device 16.4 (no driver attached)
pci127: <base peripheral> at device 16.5 (no driver attached)
pci127: <base peripheral> at device 16.6 (no driver attached)
pci127: <base peripheral> at device 16.7 (no driver attached)
pci127: <base peripheral> at device 17.0 (no driver attached)
pci127: <base peripheral> at device 19.0 (no driver attached)
pci127: <dasp> at device 19.1 (no driver attached)
pci127: <dasp> at device 19.4 (no driver attached)
pci127: <dasp> at device 19.5 (no driver attached)
pci127: <base peripheral> at device 19.6 (no driver attached)
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xec000-0xeffff on isa0
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
ppc0: cannot reserve I/O port range
ctl: CAM Target Layer loaded
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est2 attach returned 6
p4tcc2: <CPU Frequency Thermal Control> on cpu2
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est3 attach returned 6
p4tcc3: <CPU Frequency Thermal Control> on cpu3
est4: <Enhanced SpeedStep Frequency Control> on cpu4
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est4 attach returned 6
p4tcc4: <CPU Frequency Thermal Control> on cpu4
est5: <Enhanced SpeedStep Frequency Control> on cpu5
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est5 attach returned 6
p4tcc5: <CPU Frequency Thermal Control> on cpu5
est6: <Enhanced SpeedStep Frequency Control> on cpu6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est6 attach returned 6
p4tcc6: <CPU Frequency Thermal Control> on cpu6
est7: <Enhanced SpeedStep Frequency Control> on cpu7
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est7 attach returned 6
p4tcc7: <CPU Frequency Thermal Control> on cpu7
est8: <Enhanced SpeedStep Frequency Control> on cpu8
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est8 attach returned 6
p4tcc8: <CPU Frequency Thermal Control> on cpu8
est9: <Enhanced SpeedStep Frequency Control> on cpu9
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est9 attach returned 6
p4tcc9: <CPU Frequency Thermal Control> on cpu9
est10: <Enhanced SpeedStep Frequency Control> on cpu10
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est10 attach returned 6
p4tcc10: <CPU Frequency Thermal Control> on cpu10
est11: <Enhanced SpeedStep Frequency Control> on cpu11
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est11 attach returned 6
p4tcc11: <CPU Frequency Thermal Control> on cpu11
est12: <Enhanced SpeedStep Frequency Control> on cpu12
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est12 attach returned 6
p4tcc12: <CPU Frequency Thermal Control> on cpu12
est13: <Enhanced SpeedStep Frequency Control> on cpu13
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est13 attach returned 6
p4tcc13: <CPU Frequency Thermal Control> on cpu13
est14: <Enhanced SpeedStep Frequency Control> on cpu14
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est14 attach returned 6
p4tcc14: <CPU Frequency Thermal Control> on cpu14
est15: <Enhanced SpeedStep Frequency Control> on cpu15
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est15 attach returned 6
p4tcc15: <CPU Frequency Thermal Control> on cpu15
est16: <Enhanced SpeedStep Frequency Control> on cpu16
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est16 attach returned 6
p4tcc16: <CPU Frequency Thermal Control> on cpu16
est17: <Enhanced SpeedStep Frequency Control> on cpu17
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est17 attach returned 6
p4tcc17: <CPU Frequency Thermal Control> on cpu17
est18: <Enhanced SpeedStep Frequency Control> on cpu18
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est18 attach returned 6
p4tcc18: <CPU Frequency Thermal Control> on cpu18
est19: <Enhanced SpeedStep Frequency Control> on cpu19
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est19 attach returned 6
p4tcc19: <CPU Frequency Thermal Control> on cpu19
est20: <Enhanced SpeedStep Frequency Control> on cpu20
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est20 attach returned 6
p4tcc20: <CPU Frequency Thermal Control> on cpu20
est21: <Enhanced SpeedStep Frequency Control> on cpu21
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est21 attach returned 6
p4tcc21: <CPU Frequency Thermal Control> on cpu21
est22: <Enhanced SpeedStep Frequency Control> on cpu22
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est22 attach returned 6
p4tcc22: <CPU Frequency Thermal Control> on cpu22
est23: <Enhanced SpeedStep Frequency Control> on cpu23
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 245900002000
device_attach: est23 attach returned 6
p4tcc23: <CPU Frequency Thermal Control> on cpu23
mfi0: 972 (414857171s/0x0020/info) - Shutdown command received from host
mfi0: 973 (boot + 4s/0x0020/info) - Firmware initialization started (PCI ID 0073/1000/1f51/1028)
mfi0: 974 (boot + 4s/0x0020/info) - Firmware version 2.120.14-1730
mfi0: 975 (boot + 5s/0x0020/info) - Package version 20.11.0-0002
mfi0: 976 (boot + 5s/0x0020/info) - Board Revision A01
mfi0: 977 (boot + 31s/0x0004/info) - Enclosure PD 20(c None/p1) communication restored
mfi0: 978 (boot + 31s/0x0002/info) - Inserted: Encl PD 20
mfi0: 979 (boot + 31s/0x0002/info) - Inserted: PD 20(c None/p1) Info: enclPd=20, scsiType=d, portMap=00, sasAddr=5948f090eb548f00,0000000000000000
mfi0: 980 (boot + 31s/0x0002/info) - Inserted: PD 00(e0x20/s0)
mfi0: 981 (boot + 31s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=5000c5005ef16071,0000000000000000
mfi0: 982 (boot + 31s/0x0002/info) - Inserted: PD 01(e0x20/s1)
mfi0: 983 (boot + 31s/0x0002/info) - Inserted: PD 01(e0x20/s1) Info: enclPd=20, scsiType=0, portMap=01, sasAddr=5000c5005ef77b99,0000000000000000
mfi0: 984 (boot + 31s/0x0002/info) - Inserted: PD 02(e0x20/s2)
mfi0: 985 (boot + 31s/0x0002/info) - Inserted: PD 02(e0x20/s2) Info: enclPd=20, scsiType=0, portMap=02, sasAddr=5000c5005eef626d,0000000000000000
mfi0: 986 (414857261s/0x0020/info) - Time established as 02/22/13 14:07:41; (72 seconds since power on)
mfi0: 987 (414857787s/0x0020/info) - Host driver is loaded and operational
Timecounters tick every 1.000 msec
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
mfid0 on mfi0
mfid0: 571136MB (1169686528 sectors) RAID volume (no label) is optimal
ugen1.2: <vendor 0x8087> at usbus1
uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus1
ugen0.2: <vendor 0x8087> at usbus0
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus0
uhub3: 6 ports with 6 removable, self powered
uhub2: 8 ports with 8 removable, self powered
ugen0.3: <General> at usbus0
umass0: <General USB Flash Disk, class 0/0, rev 2.00/1.00, addr 3> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0x4100
umass0:9:0:-1: Attached to scbus9
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <General USB Flash Disk 1.0> Removable Direct Access SCSI-2 device 
da0: 40.000MB/s transfers
da0: 1801MB (3688448 512 byte sectors: 255H 63S/T 229C)
SMP: AP CPU #22 Launched!
cd0 at ahcich4 bus 0 scbus6 target 0 lun 0
cd0: <PLDS DVD+-RW DS-8A8SH KD51> Removable CD-ROM SCSI-0 device 
cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
SMP: AP CPU #5 Launched!
SMP: AP CPU #13 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #15 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #12 Launched!
SMP: AP CPU #11 Launched!
SMP: AP CPU #14 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #17 Launched!
SMP: AP CPU #10 Launched!
SMP: AP CPU #20 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #23 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #18 Launched!
SMP: AP CPU #8 Launched!
SMP: AP CPU #21 Launched!
SMP: AP CPU #9 Launched!
SMP: AP CPU #16 Launched!
SMP: AP CPU #4 Launched!
SMP: AP CPU #19 Launched!
Timecounter "TSC-low" frequency 11328352 Hz quality 1000
ugen0.4: <CHESEN> at usbus0
ukbd0: <CHESEN PS2 to USB Converter, class 0/0, rev 1.10/0.10, addr 4> on usbus0
kbd0 at ukbd0
ums0: <CHESEN PS2 to USB Converter, class 0/0, rev 1.10/0.10, addr 4> on usbus0
ums0: 5 buttons and [XYZ] coordinates ID=1
GEOM: da0: geometry does not match label (64h,33s != 255h,63s).
GEOM: da0: media size does not match label.
Root mount waiting for: usbus0
Root mount waiting for: usbus0
ugen0.5: <General> at usbus0
umass1: <General USB Flash Disk, class 0/0, rev 2.00/1.00, addr 5> on usbus0
umass1:  SCSI over Bulk-Only; quirks = 0x4100
umass1:10:1:-1: Attached to scbus10
da1 at umass-sim1 bus 1 scbus10 target 0 lun 0
da1: <General USB Flash Disk 1.0> Removable Direct Access SCSI-2 device 
da1: 40.000MB/s transfers
da1: 1801MB (3688448 512 byte sectors: 255H 63S/T 229C)
ugen0.6: <no manufacturer> at usbus0
uhub4: <no manufacturer Gadget USB HUB, class 9/0, rev 2.00/0.00, addr 6> on usbus0
Root mount waiting for: usbus0
uhub4: 6 ports with 6 removable, self powered
Root mount waiting for: usbus0
ugen0.7: <Avocent> at usbus0
ukbd1: <Keyboard> on usbus0
kbd2 at ukbd1
ums1: <Mouse> on usbus0
ums1: 3 buttons and [Z] coordinates ID=0
ums2: <Mouse REL> on usbus0
ums2: 3 buttons and [XYZ] coordinates ID=0
Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]...
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Zurück
Oben