11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread Sevan / Venture37 

OpenBSD 5.4-current (GENERIC.MP) #50: Mon Sep  2 13:43:54 MDT 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error b1clock_battery,config_unit,memory_size
real mem = 8475713536 (8083MB)
avail mem = 8242003968 (7860MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (54 entries)
bios0: vendor Apple Inc. version MBA51.88Z.00EF.B02.1211271028 date 
11/27/2012

bios0: Apple Inc. MacBookAir5,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT SSDT SSDT DMAR MCFG
acpi0: wakeup devices P0P2(S4) PEG2(S4) EC__(S4) HDEF(S4) RP02(S4) 
ARPT(S4) RP05(S4) EHC1(S4) EHC2(S4) XHC1(S4) ADP1(S4) LID0(S4)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1896.01 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
cpu0: apic clock running at 99MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1895.70 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1895.70 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1895.70 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-153
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P2)
acpiprt2 at acpi0: bus -1 (PEG2)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP05)
acpicpu0 at acpi0: C3, C1, PSS
acpicpu1 at acpi0: C3, C1, PSS
acpicpu2 at acpi0: C3, C1, PSS
acpicpu3 at acpi0: C3, C1, PSS
acpibat0 at acpi0: BAT0 model 3545797981023400290 type 
3545797981528607052 oem 3545797981528673619

acpiac0 at acpi0: AC unit offline
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: IGPU
acpivout0 at acpivideo0: DD02
cpu0: Enhanced SpeedStep 1896 MHz: speeds: 2001, 2000, 1900, 1800, 1700, 
1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz

memory map conflict 0xe00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xffe7/0x3
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Core 3G Host rev 0x09
vga1 at pci0 dev 2 function 0 Intel HD Graphics 4000 rev 0x09
intagp0 at vga1
agp0 at intagp0: aperture at 0x9000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
inteldrm0: 1366x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
Intel 7 Series xHCI rev 0x04 at pci0 dev 20 function 0 not configured
Intel 7 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 Intel 7 Series USB rev 0x04: apic 2 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 Intel 7 Series HD Audio rev 0x04: msi
azalia0: codecs: Cirrus Logic CS4206, Intel/0x2806, using Cirrus Logic 
CS4206

audio0 at azalia0
ppb0 at pci0 dev 28 function 0 Intel 7 Series PCIE rev 0xc4: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 1 Intel 7 Series PCIE rev 0xc4: msi
pci2 at ppb1 bus 2
Broadcom BCM43224 rev 0x01 at pci2 dev 0 function 0 not configured
ppb2 at pci0 dev 28 function 4 Intel 7 Series PCIE rev 0xc4: msi
pci3 at ppb2 bus 3
ppb3 at pci3 dev 0

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread Kenneth R Westerback 
Geez, not much changed in the 89 years between now and 2102. :-)

 Ken

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread Sevan / Venture37 
On 5 Sep 2013, at 18:42, Kenneth R Westerback kwesterb...@rogers.com wrote:

 Geez, not much changed in the 89 years between now and 2102. :-)
 
  Ken

Im the idiot from the future, 2 days ago, I thought I was running 5.4-RELEASE 
on there

https://twitter.com/sevanjaniyan/status/374949733615562752

Sevan

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread Miod Vallat 
  Geez, not much changed in the 89 years between now and 2102. :-)
  
   Ken
 
 Im the idiot from the future, 2 days ago, I thought I was running 5.4-RELEASE 
 on there

5.4-RELEASE will have time issues in 2102. However, 5.4-CURRENT as of
now ought to run without any particular problems (assuming the hardware
is still in working condition and you can still get electricity in year
2102).

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread Ryan Freeman 
On Thu, Sep 05, 2013 at 07:32:38PM +, Miod Vallat wrote:
   Geez, not much changed in the 89 years between now and 2102. :-)
   
    Ken
  
  Im the idiot from the future, 2 days ago, I thought I was running 
  5.4-RELEASE on there
 
 5.4-RELEASE will have time issues in 2102. However, 5.4-CURRENT as of
 now ought to run without any particular problems (assuming the hardware
 is still in working condition and you can still get electricity in year
 2102).


Confirmation of this will have to go in his Will as a task for future
generations ;)  less of course, that human brain uploading technology
is done by then, and i better be able read about it in brain(4) ;)

-ryan

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread Chess Griffin 

On 05.09.2013 15:20, Sevan / Venture37 wrote:
On 5 Sep 2013, at 18:42, Kenneth R Westerback kwesterb...@rogers.com 
wrote:



Geez, not much changed in the 89 years between now and 2102. :-)

 Ken


Im the idiot from the future, 2 days ago, I thought I was running
5.4-RELEASE on there

https://twitter.com/sevanjaniyan/status/374949733615562752

Sevan


I had no idea OSX's Time Machine actually worked.

--
Chess Griffin

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread Sevan / Venture37 

On 05/09/2013 23:32, Miod Vallat wrote:

Geez, not much changed in the 89 years between now and 2102. :-)

 Ken


Im the idiot from the future, 2 days ago, I thought I was running 5.4-RELEASE 
on there


5.4-RELEASE will have time issues in 2102. However, 5.4-CURRENT as of
now ought to run without any particular problems (assuming the hardware
is still in working condition and you can still get electricity in year
2102).


The question is, will Theo still be remapping keys on peoples keyboards, 
I could've sworn I typed 2012 on my keyboard.



Sevan

Re: 11 mid-2102 i7 MacBook Air 5,1 dmesg

2013-09-05 Thread patrick keshishian 
On 9/5/13, Miod Vallat m...@online.fr wrote:
  Geez, not much changed in the 89 years between now and 2102. :-)
 
   Ken

 Im the idiot from the future, 2 days ago, I thought I was running
 5.4-RELEASE on there

 5.4-RELEASE will have time issues in 2102. However, 5.4-CURRENT as of
 now ought to run without any particular problems (assuming the hardware
 is still in working condition and you can still get electricity in year
 2102).

holy time-flux batman! he was zapped back in time running a
pre-64bit time_t OS in the future! The hardware's holographic
chip must've induced unforeseeable feedback, causing excess
thermal stress fields on the laptop's fuel-cell, causing temporal
shifts with discontinuities ...

... where is Doc Brown? I think you guys might have accidentally
invented time-travel!

--patrick