Table 'FACP' at 0x7fff0200 Table 'APIC' at 0x7fff0390 MADT: Found table at 0x7fff0390 MP Configuration Table version 1.4 found at 0xc00f8d50 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 2: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 130 ACPI ID 3: disabled MADT: Found CPU APIC ID 131 ACPI ID 4: disabled ACPI APIC Table: <A M I OEMAPIC > APIC ID: physical 0, logical 0:0 APIC ID: physical 1, logical 0:1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 bios32: Found BIOS32 Service Directory header at 0xc00f0000 bios32: Entry = 0xf0010 (c00f0010) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0x31 pnpbios: Found PnP BIOS data at 0xc00f3130 pnpbios: Entry = f0000:3e8a Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 2 MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 0166root▲ ★NGNG で、>>165 を見ると、BIOS 的に disabled にされているような気がするですね。
> MADT: Found CPU APIC ID 130 ACPI ID 3: disabled > MADT: Found CPU APIC ID 131 ACPI ID 4: disabled
In prior FreeBSD releases, the disc1 CD-ROM (or ISO image) was a bootable installation disk containing the base system, ports tree, and common packages. The disc2 CD-ROM (or ISO image) was a bootable ``fix it'' disk with a live filesystem, to be used for making emergency repairs. This layout has now changed.
For all architectures except ia64, the disc1 image now contains the base system distribution files, ports tree, and the live filesystem, making it suitable for both an initial installation and repair purposes. (On the ia64, the live filesystem is on a separate disk due to its size.) Packages appear on separate disks; in particular, the disc2 image contains commonly packages such as desktop environments. Documents from the FreeBSD Documentation Project also appear on disc2. 0194動け動けウゴウゴ２ちゃんねる2005/05/10(火) 12:25:32ID:W+1rsMTp0 >185 それはジムはジムでもgymの方だろ！ 0195動け動けウゴウゴ２ちゃんねる2005/05/10(火) 13:20:56ID:CiGJMRY00 掃除機かけようとしてスイッチ入れたら（以下略 0196root▲ ★NGNG XOロケーションに移動したサーバ落ちすぎハングアップしすぎ、 なんとかしてちょ、とりあえず電源のチェックしてみて、 っていうメールを、私からも出しておきました。
Yes you are correct we just did an inspection of those, and are ordering the additional processor for them. Your friend, Jim
servers were shutdown for inspection, there is a problem with the Tigers configuration, they do only have 1 processor. We are resolving the problem, it was an ordering error. There is no problem with the power in XO. -Sean
ということで、
・状況はわかった ・携帯ユーザ、特にauのユーザが首を長くして待っているから、いつCPUが来るかの目安を教えて ・まだtiny tigersは実運用していないから、CPUはこちらに断らないで追加していいよ でも追加できたらメールで教えてね ・このところのhobby7落ち、BBQとc-docomo2リブート繰り返しとかがやや気になるけど、 これも含めてしばらくは注意深く様子を見ることにするよ ・また不安定になったらメールするから、do your bestで安定運用してね
Thank you for your quick reply. I understand the current situation.
Would you tell me the estimation of CPU arrival date? Japanese 2ch mobile phone users, especially au users waiting for this.
All 6 tiny tigers are still not in 2ch service now due to the CPU issue. So, if CPUs are arrived, you may install them in tiny tigers without any notices, and after CPUs are installed, please email to me.
And I encountered other servers' down which located in XO in several days. For example, cobra2244, 2245, tiger510. I think that they are unrelated to inspection. Anyway, I will watch XO servers' status carefully, and if they are unstable, I will email to you again.
Please do your best, all 2ch users are watching us in their 'lukewarm' eyes.
しかし、 May 7 13:00:25 <0.2> banana307 kernel: ad1: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=108401471 May 9 13:00:24 <0.2> banana307 kernel: ad1: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=8668191 May 10 13:00:16 <0.2> banana307 kernel: ad1: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=136239551
Loop 12: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : ok Checkerboard : ok Bit Spread : ok Bit Flip : ok Walking Ones : ok Walking Zeroes : ok 0216root▲ ★NGNG というわけで、初物は例によって ex10 から。
%uname -a FreeBSD oyster901.maido3.com 5.4-RELEASE FreeBSD 5.4-RELEASE #2: Wed May 11 07:32:34 PDT 2005 root@oyster901.maido3.com:/usr/obj/usr/src/sys/AMD64_COBRA_54 amd64 0217root▲ ★NGNG とりあえず、メモ。
Administrative Contact, Technical Contact: Watkins, Jim Sun dns@NTTSUPPORT.COM N.T.Technology inc. 2707 Colby ave suite 1110 EVERETT, WA 98201 US 425-259-3201 fax: 425-259-4183
Record expires on 22-Jul-2006. Record created on 22-Jul-1999. Database last updated on 13-May-2005 02:32:46 EDT.
%uname -a FreeBSD oyster901.maido3.com 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #3: Fri May 13 12:42:42 PDT 2005 root@oyster901.maido3.com:/usr/obj/usr/src/sys/AMD64_COBRA_54 amd64 0244root▲ ★NGNG で、パッチの中身を呼んで見ましたが、amd64も同じパッチあたってはいるけど、 HTT問題なので、AMDなCPUには関係なさげ。
で、パッチ内にこんな記述が。
+ /* + * Work out if hyperthreading is *really* enabled. This + * is made really ugly by the fact that processors lie: Dual + * core processors claim to be hyperthreaded even when they're + * not, presumably because they want to be treated the same + * way as HTT with respect to per-cpu software licensing. + * At the time of writing (May 12, 2005) the only hyperthreaded + * cpus are from Intel, and Intel's dual-core processors can be + * identified via the "deterministic cache parameters" cpuid + * calls. + */ 0245動け動けウゴウゴ２ちゃんねるNGNG>>242のリンクに
> Use of this workaround is not recommended on "dual-core" systems, as > this workaround will also disable one of the processor cores.
