FW 800 speed disappointing: controller to blame?
I had many of my images backed up on a 1TB external HDD with a FW 400 port. Running out of space, I copied all the images to a new 2TB external HDD with a FW 800 port.
Then I duplicated those files from the 2TB external HDD with a FW 800 port to a 2nd 2TB external HDD with a FW 800 port via the Finder (the two 2TB external HDDs with FW 800 ports were daisy chained together). The transfer of files from the FW 800 to the 2nd FW 800 external HDD was slower than the transfer of files from the FW 400 to the FW 800 external HDD.
This indicated to me that the FW 800 controller in the iMac was perhaps very busy communicating with both drives for every bit moved instead of the the two FW 800 HDDs communicating between themselves with the iMac's controller providing oversight. Is this the case because if it is, I'll be sure to not to dasiy chain FW 800 HDD together and instead connect one to the FW 400 port of my iMac. I miss SCSI (but not SCSI voodoo).
Also, the HDDs involved were:
The FW800 HDDs were both Seagate FreeAgent GoFlex with a FireWire 800/USB 2.0 adapter. The specifications according to Best Buy are 7200 RPM with a 32MB cache.
The FW400 HDD was a Western Digital My Book Home Edition. WD doesn't have specifications for it but I've read that the speed can vary "from 5400 to 7200 RPM" and the cache can vary "8 MBytes to 32 MBytes".
Similar Messages
-
I recently purchased a four bay RAID array to replace the multitude of external drives that I've collected over the years. I installed four 1TB drives in a RAID 5 configuration to make up a 3TB array. The RAID model is the DM4 from Sabio (Sabio DAS DM4).
I connected it to my iMac via Firewire 800 (it has 2x FW800 ports, 1x FW400, 1x USB 2.0, 1x eSATA), and after hours of copying from the external USB drives I finally got everything migrated over to the new monster drive. However, I am seeing some weirdness in transfer speeds.
My iMac specs are as follows:
Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.21f4
I was testing copy speeds to the array by using the cp command in the terminal and watching the disk activity in iStat Menus (but you can get the same information out of Activity Monitor on the Disk Activity tab). Using cp, I was only able to push about 45MiB/s, which I found strange since this is near the maximum of FW400 (50MiB/s).
The truly weird thing, though, was using the same file, copying to the array in the Finder pushed the transfer up to 65MiB/s. The main question I have is why would that be? I've tried alternates on the command line as well, such as rsync but nothing moves as fast as the finder.
Now I get that writing to the array is going to be slower considering that I'm writing parity to all the drives, but I don't get the speed difference between the command line tools and the GUI Finder. Maybe it's a caching issue?
I'm also seeing a hit between the command line and the Finder with reads from the array. Unsurprisingly the reads are better than the writes, since I'm pulling from four drives. With the Finder, I'm able to pull at an average rate of 75MiB/s. The command line I read around 63MiB/s to 66MiB/s.
All these tests are the same file. The drive in the iMac is actually brand new (1TB Seagate), and it has barely anything on it so it's not some type of fragmentation issue. The only external drive on the iMac is this Sabio array.
So, does anyone have any ideas why I'm seeing such a speed difference between the command line and the GUI? Also, is there a way to work around this slow down on the command line? Hopefully someone knows more than I've found thus far.
Thanks for your time,
Adam.You're right, I could use the Finder to do all my copies, but I typically don't use my systems at that level. I know that sounds weird, but I'm a Linux admin and systems engineer by trade and I live in the command-line/terminal all day long. I am a lot faster at manipulating the system via the command-line than I am with point and click. There are a lot of times that I just quit the Finder outright so I don't have to look at my Desktop icons (though I have the desktop turned off right now so I don't see any icons at all).
I generally use my iMac as a media center, where it serves media to my PS3 and what not. I also use it for some development work. My wife will use the machine for graphic design when she is working form home thus she's in the Adobe Creative Suite a lot of the time. With that said, the machine is mutli-user, and I typically use command-line programs to ensure that what I copy is copied correctly via rsync, or the cp -Rp commands.
Now, my observations were not really a concern, but more of a why-on-earth-is-this-happening type of thing. In the past, it used to be a lot faster and more efficient CPU wise to copy via the command-line than it was in the Finder. Now with Snow Leopard they seem to have gone the other way around. To me, it just seems that the command-line equivalent, which doesn't have any glitz or glamour at all, should be natively faster than the Finder, which has progress bars, drag-and-drop, etc.
So yeah, I can use the Finder, but it's not what I use normally. -
Minimum connection speeds 5508 controller and 2602E APs
We have an applicaiton that is sensitive to network speeds. Is there a way to guarantee a minimum wireless network speed such as 100 MBs utilizing a 5508 controller and 2602e APs?
We have an applicaiton that is sensitive to network speeds. Is there a way to guarantee a minimum wireless network speed such as 100 MBs utilizing a 5508 controller and 2602e APs?
Not easy. Wireless is a shared medium. This means if one client talks, everyone else has to stop and wait for their turn.
It's like doing video. Video is time-sensitive. If you put a single AP in a room (granted you've got full 1Gbps ethernet access all the way), and you get 25 people continuously streaming videos, then you'll see some impact. Bring the number down to say, 8 to 10 and you'll see improvements.
What kind of application are we talking about here? -
Slow firewire 800 speeds on early 2008 macbook pro 17"
I've got an early 2008 macbook pro 17". I'm transferring files between a WD mybook studio II (2TB) configured as raid-1 to a sata dock with a seagate 1TB drive daisy-chained over firewire 800. both 1TB drives in the WD mybook and the 1TB seagate in the sata dock are 7.2k rpm. I'm running a block-level clone FROM the mybook TO the seagate using Carbon Copy Cloner which i would think would be the fastest real-world test i could do. I'm getting pegged speeds of 40MB/s. This is on par with other regular read/write speeds i've noticed in the past. this seems way off. to remove variables i unplugged my two firewire 400 drives (as i've heard that may slow things down, even though they're not doing anything during the clone) and it SLOWED DOWN the fw800 clone to 38MB/s ! plugging the two firewire 400 drives back in during the clone brought the speeds back up to 40MB/s. i don't have a unibody 2009 mbp that had the firewire issues.
1) HDD's should read at 70-80MB/s and at least write at 59 MB/s, why am i not getting that using firewire 800 and two 7200 rpm drives ?? (i know the wd mybook is raid-1 but i'm reading from it...shouldn't effect read performance)
2) (less important) why on earth would having two firewire 400 drives plugged in and inactive make the firewire 800 transfer speeds go up/down 2MB/s
i'm willing to experiment with anyone's suggestions. huge thanks in advance.i have a similar problem.
i have a new seagate freeagent 1tb drive w/FW800, FW400 and USB2.0 ports, and its connected via the FW800 port/cable to my macbook pro, and read/write speeds are really slow, particularly read speeds.
i'm currently working on an audio project with around 15 audio tracks running at once, and it chokes the drive ('HD overload' errors), so i've done some benchmark testing using Drive Genius and Xbench. the results show that the drive is averaging around 12mb/s read speed, and around 26mb/s write speed. grim.
i tried the drive with the FW400 connection on my missus' old imac g5, and its much faster than my mbp's FW800 connection, so i decided to try the drive back on my machine with OSX booted in Safe mode, and benchmark it again. the results are massively different; the FW800 connection is very fast (as you'd expect).
both the tests were done with all my peripherals attached (usb hub, ethernet cable, usb2 ext. drive) so i don't think the problem is with those.
what i'm wondering is if there are any known system extensions that can screw with the FW bus speeds? if not, any pointers as to where i should start troubleshooting?
many thanks! -
I have an iphone 4S and a Lumia 800. I was wondering why my iphone is sooooooooo much faster at web browsing and rendering and in general tasks. Surely my Lumia should be quicker? Lumia is slow to browse the web and internet inc wifi. My 4S is lightning quick.
Dear Wizard of Oz, there are alot of factors affecting browsing speed and i would invite you to read the various reviews that puts the iPhone 4S and the Lumia 800 on test.
Further, if you didn't already notice, the iPhone 4s has dual core processors while the Lumia 800 is only a 1.4GHz single core.
Thank you. -
BLDC Motor Speed from Controller
In the tester I am building, I am having troubles acquiring a stable motor speed. I need a stable speed so that I can control the motor speed to 1100 +/- 50 RPM.
We have a compressor connected to a Dart 700BDC controller, and a cFP-CTR-502 counter input connected to one of the hall sensor inputs on the controller. The counter is set up just to continually counting the number of pulses (counter overflow is handled within the test application). The test application gets the counter value and timestamp from the Fieldpoint VI's approximately every 500 milliseconds. It compares these two items to the data from the previous iteration to generate an RPM. I've attached a VI that has the routine that I am currently using.
When I run the motor, I have RPM values that fluctuates beyond my 50 RPM window. Do I need to tweak my routines to display a more stable reading? Or is a different solution required?
Attachments:
Monitor Motor Speed.vi 13 KBHi OlderJohn,
The first you should try is lowering your sample time and perhaps even your proportional gain. Are you familiar with PID control. I recommend reading a great article on it here
Joe Daily
National Instruments
Applications Engineer
may the G be with you .... -
Asus N71JQ Suspend/Resume Issues, USB3 Controller to blame??
Alright so I've never gotten Suspend to work on this laptop since like 2.6.35 or so, no idea what they did in 2.6.36 or 2.6.37 (skipped those kernels) but it broke my suspend...which makes me sad. Been jumping between Arch and Fedora lately, neither of them works so its not a default configuration screw up. Arch has the nice bonus of having a LOT more packages available, specifically uswsusp so I've been giving that try to make it work. Graphics drivers are Gallium3D Radeon (with KMS) so its not an FGLRX issue; just to get that out of the way.
Here's what happens: I tell it to sleep / suspend, screen blacks out, my Disk-activity LED turns active (and stays active until I shutdown), doesn't take any keyboard input, including the SysReq keys. Try toggling caps lock to see if the kernel is locked... nothing happens; LED doesnt change its status at all. Only option is to hold down the power button and reboot.
The Arch wiki on Asus Laptops mentioned, for a diff modal of the N-series that Suspend didnt work correctly because of bugs in the USB3 Controller; I have a single USB3 port on this laptop. So there is any kernel parameter, module, etc that I could toggle for USB3?
pm-suspend.log:
[eric@eric-laptop ~]$ cat /var/log/pm-suspend.log
Initial commandline parameters:
Thu Sep 1 20:12:21 EDT 2011: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux eric-laptop 3.0-ARCH #1 SMP PREEMPT Wed Aug 17 20:24:07 UTC 2011 i686 Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz GenuineIntel GNU/Linux
Module Size Used by
ipv6 250073 22
cryptd 6893 0
aes_i586 6940 2
aes_generic 25670 1 aes_i586
snd_hda_codec_hdmi 20068 1
snd_hda_codec_realtek 222124 1
snd_hda_intel 19101 6
snd_hda_codec 66954 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 4942 1 snd_hda_codec
snd_pcm 60015 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
sg 20982 0
uvcvideo 57363 0
joydev 7439 0
arc4 1086 2
usb_storage 35279 0
uas 6440 0
videodev 70542 1 uvcvideo
keucr 74634 0
usbhid 31199 0
evdev 7278 10
hid 65215 1 usbhid
media 8545 2 uvcvideo,videodev
snd_timer 15374 2 snd_pcm
ath9k 75832 0
radeon 910898 3
mac80211 191541 1 ath9k
snd 43593 17 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
ttm 45269 1 radeon
soundcore 4986 1 snd
drm_kms_helper 21997 1 radeon
iTCO_wdt 10293 0
iTCO_vendor_support 1545 1 iTCO_wdt
ath9k_common 1390 1 ath9k
ath9k_hw 262580 2 ath9k,ath9k_common
ath 11959 2 ath9k,ath9k_hw
cfg80211 138620 3 ath9k,mac80211,ath
atl1c 28528 0
snd_page_alloc 5869 2 snd_hda_intel,snd_pcm
drm 147782 5 radeon,ttm,drm_kms_helper
cpufreq_ondemand 5056 8
mei 27104 0
agpgart 22096 2 ttm,drm
i7core_edac 13707 0
edac_core 30220 3 i7core_edac
acpi_cpufreq 5113 1
asus_laptop 11994 0
i2c_algo_bit 4423 1 radeon
freq_table 2047 2 cpufreq_ondemand,acpi_cpufreq
i2c_core 16625 5 videodev,radeon,drm_kms_helper,drm,i2c_algo_bit
pcspkr 1375 0
serio_raw 3390 0
video 9780 0
thermal 6595 0
processor 21876 1 acpi_cpufreq
psmouse 56431 0
sparse_keymap 2628 1 asus_laptop
mperf 1027 1 acpi_cpufreq
battery 8865 0
ac 2505 0
button 3646 0
rfkill 12406 2 cfg80211,asus_laptop
ext4 337724 3
mbcache 4249 1 ext4
jbd2 59488 1 ext4
crc16 1069 1 ext4
sr_mod 13244 0
cdrom 31277 1 sr_mod
sd_mod 26147 6
ahci 18085 4
libahci 16573 1 ahci
libata 154449 2 ahci,libahci
xhci_hcd 61332 0
scsi_mod 111801 7 sg,usb_storage,uas,keucr,sr_mod,sd_mod,libata
ehci_hcd 34935 0
usbcore 119644 8 uvcvideo,usb_storage,uas,keucr,usbhid,xhci_hcd,ehci_hcd
total used free shared buffers cached
Mem: 3025356 578420 2446936 0 28596 250580
-/+ buffers/cache: 299244 2726112
Swap: 8388604 0 8388604
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend:
/usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Sep 1 20:12:22 EDT 2011: performing suspend
Initial commandline parameters:
Thu Sep 1 20:19:18 EDT 2011: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux eric-laptop 3.0-ARCH #1 SMP PREEMPT Wed Aug 17 20:24:07 UTC 2011 i686 Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz GenuineIntel GNU/Linux
Module Size Used by
ipv6 250073 22
cryptd 6893 0
aes_i586 6940 2
aes_generic 25670 1 aes_i586
snd_hda_codec_hdmi 20068 1
snd_hda_codec_realtek 222124 1
radeon 910898 3
snd_hda_intel 19101 6
snd_hda_codec 66954 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
ttm 45269 1 radeon
drm_kms_helper 21997 1 radeon
snd_hwdep 4942 1 snd_hda_codec
snd_pcm 60015 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 15374 2 snd_pcm
snd 43593 17 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
uvcvideo 57363 0
serio_raw 3390 0
soundcore 4986 1 snd
videodev 70542 1 uvcvideo
drm 147782 5 radeon,ttm,drm_kms_helper
cpufreq_ondemand 5056 8
arc4 1086 2
joydev 7439 0
usbhid 31199 0
hid 65215 1 usbhid
ath9k 75832 0
mac80211 191541 1 ath9k
ath9k_common 1390 1 ath9k
i7core_edac 13707 0
ath9k_hw 262580 2 ath9k,ath9k_common
edac_core 30220 3 i7core_edac
usb_storage 35279 0
uas 6440 0
iTCO_wdt 10293 0
keucr 74634 0
ath 11959 2 ath9k,ath9k_hw
media 8545 2 uvcvideo,videodev
iTCO_vendor_support 1545 1 iTCO_wdt
atl1c 28528 0
mei 27104 0
cfg80211 138620 3 ath9k,mac80211,ath
evdev 7278 10
snd_page_alloc 5869 2 snd_hda_intel,snd_pcm
psmouse 56431 0
acpi_cpufreq 5113 1
freq_table 2047 2 cpufreq_ondemand,acpi_cpufreq
agpgart 22096 2 ttm,drm
i2c_algo_bit 4423 1 radeon
i2c_core 16625 5 radeon,drm_kms_helper,videodev,drm,i2c_algo_bit
mperf 1027 1 acpi_cpufreq
pcspkr 1375 0
asus_laptop 11994 0
sparse_keymap 2628 1 asus_laptop
battery 8865 0
video 9780 0
processor 21876 1 acpi_cpufreq
ac 2505 0
thermal 6595 0
button 3646 0
rfkill 12406 2 cfg80211,asus_laptop
ext4 337724 3
mbcache 4249 1 ext4
jbd2 59488 1 ext4
crc16 1069 1 ext4
sr_mod 13244 0
sg 20982 0
cdrom 31277 1 sr_mod
sd_mod 26147 6
ahci 18085 4
libahci 16573 1 ahci
libata 154449 2 ahci,libahci
xhci_hcd 61332 0
scsi_mod 111801 7 usb_storage,uas,keucr,sr_mod,sg,sd_mod,libata
ehci_hcd 34935 0
usbcore 119644 8 uvcvideo,usbhid,usb_storage,uas,keucr,xhci_hcd,ehci_hcd
total used free shared buffers cached
Mem: 3025356 627068 2398288 0 29004 255828
-/+ buffers/cache: 342236 2683120
Swap: 8388604 0 8388604
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend:
/usr/lib/pm-utils/sleep.d/01laptop-mode suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /etc/pm/sleep.d/90alsa suspend suspend:
/etc/pm/sleep.d/90alsa suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Sep 1 20:19:19 EDT 2011: performing suspend
dmesg:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.0-ARCH (tobias@T-POWA-LX) (gcc version 4.6.1 (GCC) ) #1 SMP PREEMPT Wed Aug 17 20:24:07 UTC 2011
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009bc00 (usable)
[ 0.000000] BIOS-e820: 000000000009bc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000bb4ec000 (usable)
[ 0.000000] BIOS-e820: 00000000bb4ec000 - 00000000bb531000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb531000 - 00000000bb542000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb542000 - 00000000bb554000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb554000 - 00000000bb55d000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb55d000 - 00000000bb565000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb565000 - 00000000bb57f000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb57f000 - 00000000bb580000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb580000 - 00000000bb595000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb595000 - 00000000bb599000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb599000 - 00000000bb59c000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb59c000 - 00000000bb59d000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb59d000 - 00000000bb5a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb5a0000 - 00000000bb5a3000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000bb5a3000 - 00000000bb5a8000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb5a8000 - 00000000bb5b6000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb5b6000 - 00000000bb5cc000 (reserved)
[ 0.000000] BIOS-e820: 00000000bb5cc000 - 00000000bb5ce000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bb5ce000 - 00000000c0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1b000 - 00000000fed20000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffa00000 - 00000000ffc00000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
[ 0.000000] PAT support disabled.
[ 0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
[ 0.000000] DMI 2.6 present.
[ 0.000000] DMI: ASUSTeK Computer Inc. N71Jq/N71Jq, BIOS N71Jq.207 05/14/2010
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] last_pfn = 0xbb4ec max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DFFFF uncachable
[ 0.000000] E0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 080000000 mask FC0000000 write-back
[ 0.000000] 2 base 0BC000000 mask FFC000000 uncachable
[ 0.000000] 3 base 100000000 mask FC0000000 write-back
[ 0.000000] 4 base 0FFE00000 mask FFFE00000 write-protect
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] found SMP MP-table at [c00fcb70] fcb70
[ 0.000000] initial memory mapped : 0 - 00c00000
[ 0.000000] Base memory trampoline at [c0097000] 97000 size 16384
[ 0.000000] init_memory_mapping: 0000000000000000-00000000377fe000
[ 0.000000] 0000000000 - 0000400000 page 4k
[ 0.000000] 0000400000 - 0037400000 page 2M
[ 0.000000] 0037400000 - 00377fe000 page 4k
[ 0.000000] kernel direct mapping tables up to 377fe000 @ bfb000-c00000
[ 0.000000] RAMDISK: 7f66a000 - 7fff0000
[ 0.000000] Allocated new RAMDISK: 36e78000 - 377fdc71
[ 0.000000] Move RAMDISK from 000000007f66a000 - 000000007ffefc70 to 36e78000 - 377fdc70
[ 0.000000] ACPI: RSDP 000f0410 00024 (v02 _ASUS_)
[ 0.000000] ACPI: XSDT bb5a1e18 0006C (v01 _ASUS_ Notebook 06222004 MSFT 00010013)
[ 0.000000] ACPI: FACP bb57fc18 000F4 (v04 _ASUS_ Notebook 06222004 MSFT 00010013)
[ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20110413/tbfadt-369)
[ 0.000000] ACPI Warning: 32/64X FACS address mismatch in FADT - 0xBB5B3F40/0x00000000BB5CDD40, using 32 (20110413/tbfadt-489)
[ 0.000000] ACPI: DSDT bb542018 119EF (v01 _ASUS_ Notebook 00000000 INTL 20051117)
[ 0.000000] ACPI: FACS bb5b3f40 00040
[ 0.000000] ACPI: APIC bb5a0f18 0008C (v02 _ASUS_ Notebook 06222004 MSFT 00010013)
[ 0.000000] ACPI: DBGP bb5a2f18 00034 (v01 _ASUS_ Notebook 06222004 MSFT 00010013)
[ 0.000000] ACPI: ECDT bb5cda18 000C1 (v01 _ASUS_ Notebook 06222004 AMI. 00000003)
[ 0.000000] ACPI: SLIC bb5aec18 00176 (v01 _ASUS_ Notebook 06222004 ASUS 00000001)
[ 0.000000] ACPI: MCFG bb5ccd18 0003C (v01 _ASUS_ Notebook 06222004 MSFT 00000097)
[ 0.000000] ACPI: HPET bb5ccc98 00038 (v01 _ASUS_ Notebook 06222004 AMI. 00000003)
[ 0.000000] ACPI: SSDT bb59c018 009F1 (v01 PmRef CpuPm 00003000 INTL 20051117)
[ 0.000000] ACPI: DMAR bb5cdb18 00068 (v01 INTEL CP_FIELD 00000001 INTL 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 2108MB HIGHMEM available.
[ 0.000000] 887MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 377fe000
[ 0.000000] low ram: 0 - 377fe000
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x000377fe
[ 0.000000] HighMem 0x000377fe -> 0x000bb4ec
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009b
[ 0.000000] 0: 0x00000100 -> 0x000bb4ec
[ 0.000000] On node 0 totalpages: 767095
[ 0.000000] free_area_init_node: node 0, pgdat c05adc80, node_mem_map f5707200
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3947 pages, LIFO batch:0
[ 0.000000] Normal zone: 1744 pages used for memmap
[ 0.000000] Normal zone: 221486 pages, LIFO batch:31
[ 0.000000] HighMem zone: 4218 pages used for memmap
[ 0.000000] HighMem zone: 535668 pages, LIFO batch:31
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] SMP: Allowing 8 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: 000000000009b000 - 000000000009c000
[ 0.000000] PM: Registered nosave memory: 000000000009c000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
[ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:20000000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 12 pages/cpu @f5000000 s25472 r0 d23680 u524288
[ 0.000000] pcpu-alloc: s25472 r0 d23680 u524288 alloc=1*4194304
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 761101
[ 0.000000] Kernel command line: root=/dev/sda2 ro pcie_aspm=force nopat acpi_sleep=s3_bios
[ 0.000000] PCIe ASPM is forcedly enabled
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Initializing CPU#0
[ 0.000000] allocated 12275136 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Initializing HighMem for node 0 (000377fe:000bb4ec)
[ 0.000000] Memory: 3015104k/3068848k available (3415k kernel code, 53276k reserved, 1406k data, 500k init, 2159544k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xfff16000 - 0xfffff000 ( 932 kB)
[ 0.000000] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
[ 0.000000] vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
[ 0.000000] .init : 0xc05b6000 - 0xc0633000 ( 500 kB)
[ 0.000000] .data : 0xc0455f95 - 0xc05b5980 (1406 kB)
[ 0.000000] .text : 0xc0100000 - 0xc0455f95 (3415 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Verbose stalled-CPUs detection is disabled.
[ 0.000000] NR_IRQS:512
[ 0.000000] CPU 0 irqstacks, hard=f400a000 soft=f400c000
[ 0.000000] Extended CMOS year: 2000
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.003333] spurious 8259A interrupt: IRQ7.
[ 0.003333] Detected 1596.063 MHz processor.
[ 0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 3193.13 BogoMIPS (lpj=5320210)
[ 0.000013] pid_max: default: 32768 minimum: 301
[ 0.000105] Security Framework initialized
[ 0.000111] AppArmor: AppArmor disabled by boot time parameter
[ 0.000158] Mount-cache hash table entries: 512
[ 0.000652] Initializing cgroup subsys cpuacct
[ 0.000683] Initializing cgroup subsys memory
[ 0.000703] Initializing cgroup subsys devices
[ 0.000707] Initializing cgroup subsys freezer
[ 0.000711] Initializing cgroup subsys net_cls
[ 0.000715] Initializing cgroup subsys blkio
[ 0.000782] CPU: Physical Processor ID: 0
[ 0.000785] CPU: Processor Core ID: 0
[ 0.000794] mce: CPU supports 9 MCE banks
[ 0.000813] CPU0: Thermal monitoring enabled (TM1)
[ 0.000825] using mwait in idle threads.
[ 0.002305] ACPI: Core revision 20110413
[ 0.050618] ftrace: allocating 15363 entries in 31 pages
[ 0.061914] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.062303] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
[ 0.095282] CPU0: Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz stepping 05
[ 0.200338] Performance Events: PEBS fmt1+, erratum AAJ80 worked around, Nehalem events, Intel PMU driver.
[ 0.200351] ... version: 3
[ 0.200355] ... bit width: 48
[ 0.200358] ... generic registers: 4
[ 0.200361] ... value mask: 0000ffffffffffff
[ 0.200365] ... max period: 000000007fffffff
[ 0.200368] ... fixed-purpose events: 3
[ 0.200371] ... event mask: 000000070000000f
[ 0.220475] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.246983] CPU 1 irqstacks, hard=f4160000 soft=f4162000
[ 0.246988] Booting Node 0, Processors #1
[ 0.246993] smpboot cpu 1: start_ip = 97000
[ 0.257483] Initializing CPU#1
[ 0.360354] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.380199] CPU 2 irqstacks, hard=f416e000 soft=f4170000
[ 0.380203] #2
[ 0.380206] smpboot cpu 2: start_ip = 97000
[ 0.390683] Initializing CPU#2
[ 0.493563] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.513403] CPU 3 irqstacks, hard=f4180000 soft=f4182000
[ 0.513408] #3
[ 0.513410] smpboot cpu 3: start_ip = 97000
[ 0.523888] Initializing CPU#3
[ 0.626767] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.646605] CPU 4 irqstacks, hard=f41ba000 soft=f41bc000
[ 0.646609] #4
[ 0.646612] smpboot cpu 4: start_ip = 97000
[ 0.657093] Initializing CPU#4
[ 0.759933] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.779805] CPU 5 irqstacks, hard=f41d8000 soft=f41da000
[ 0.779810] #5
[ 0.779813] smpboot cpu 5: start_ip = 97000
[ 0.790187] Initializing CPU#5
[ 0.893097] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.913005] CPU 6 irqstacks, hard=f41e6000 soft=f41e8000
[ 0.913010] #6
[ 0.913012] smpboot cpu 6: start_ip = 97000
[ 0.923489] Initializing CPU#6
[ 1.026297] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.046206] CPU 7 irqstacks, hard=f41f4000 soft=f41f6000
[ 1.046210] #7 Ok.
[ 1.046213] smpboot cpu 7: start_ip = 97000
[ 1.056691] Initializing CPU#7
[ 1.159495] NMI watchdog enabled, takes one hw-pmu counter.
[ 1.166058] Brought up 8 CPUs
[ 1.166063] Total of 8 processors activated (25545.34 BogoMIPS).
[ 1.173501] devtmpfs: initialized
[ 1.173795] PM: Registering ACPI NVS region at bb4ec000 (282624 bytes)
[ 1.173815] PM: Registering ACPI NVS region at bb542000 (73728 bytes)
[ 1.173822] PM: Registering ACPI NVS region at bb55d000 (32768 bytes)
[ 1.173827] PM: Registering ACPI NVS region at bb57f000 (4096 bytes)
[ 1.173832] PM: Registering ACPI NVS region at bb595000 (16384 bytes)
[ 1.173836] PM: Registering ACPI NVS region at bb59c000 (4096 bytes)
[ 1.173840] PM: Registering ACPI NVS region at bb5a8000 (57344 bytes)
[ 1.173847] PM: Registering ACPI NVS region at bb5cc000 (8192 bytes)
[ 1.176054] print_constraints: dummy:
[ 1.176174] NET: Registered protocol family 16
[ 1.176365] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 1.176370] ACPI: bus type pci registered
[ 1.176555] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 1.176562] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[ 1.176566] PCI: Using MMCONFIG for extended config space
[ 1.176569] PCI: Using configuration type 1 for base access
[ 1.177664] bio: create slab <bio-0> at 0
[ 1.183082] ACPI: EC: EC description table is found, configuring boot EC
[ 1.183093] ACPI: EC: Look up EC in DSDT
[ 1.188672] ACPI: Executed 2 blocks of module-level executable AML code
[ 1.206049] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.244444] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.245155] ACPI: SSDT bb59fa98 002E1 (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
[ 1.246430] ACPI: Dynamic OEM Table Load:
[ 1.246437] ACPI: SSDT (null) 002E1 (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
[ 1.246751] ACPI: SSDT bb59e698 005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
[ 1.247976] ACPI: Dynamic OEM Table Load:
[ 1.247981] ACPI: SSDT (null) 005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
[ 1.266525] ACPI: SSDT bb59f718 00303 (v01 PmRef ApIst 00003000 INTL 20051117)
[ 1.267915] ACPI: Dynamic OEM Table Load:
[ 1.267920] ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20051117)
[ 1.276164] ACPI: SSDT bb59dd98 00119 (v01 PmRef ApCst 00003000 INTL 20051117)
[ 1.277458] ACPI: Dynamic OEM Table Load:
[ 1.277464] ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20051117)
[ 1.289022] ACPI: Interpreter enabled
[ 1.289041] ACPI: (supports S0 S3 S4 S5)
[ 1.289092] ACPI: Using IOAPIC for interrupt routing
[ 1.296566] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.296722] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.296877] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.297377] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.297532] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.297686] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.298171] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.298326] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.298481] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.298971] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.299126] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.299292] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.300744] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.300896] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.301051] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.301542] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.301697] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.301852] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.302348] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.302504] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.302670] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.321563] ACPI: EC: GPE = 0x1b, I/O: command/status = 0x66, data = 0x62
[ 1.322237] ACPI: No dock devices found.
[ 1.322241] HEST: Table not found.
[ 1.322248] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 1.323477] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
[ 1.324853] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
[ 1.324860] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
[ 1.324866] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
[ 1.324872] pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000d3fff]
[ 1.324878] pci_root PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff]
[ 1.324883] pci_root PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff]
[ 1.324888] pci_root PNP0A08:00: host bridge window [mem 0x000dc000-0x000dffff]
[ 1.324895] pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xfeafffff]
[ 1.324920] pci 0000:00:00.0: [8086:d132] type 0 class 0x000600
[ 1.325011] pci 0000:00:03.0: [8086:d138] type 1 class 0x000604
[ 1.325080] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 1.325087] pci 0000:00:03.0: PME# disabled
[ 1.325138] pci 0000:00:08.0: [8086:d155] type 0 class 0x000880
[ 1.325228] pci 0000:00:08.1: [8086:d156] type 0 class 0x000880
[ 1.325317] pci 0000:00:08.2: [8086:d157] type 0 class 0x000880
[ 1.325403] pci 0000:00:08.3: [8086:d158] type 0 class 0x000880
[ 1.325511] pci 0000:00:10.0: [8086:d150] type 0 class 0x000880
[ 1.325584] pci 0000:00:10.1: [8086:d151] type 0 class 0x000880
[ 1.325748] pci 0000:00:16.0: [8086:3b64] type 0 class 0x000780
[ 1.325846] pci 0000:00:16.0: reg 10: [mem 0xd660a000-0xd660a00f 64bit]
[ 1.326129] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 1.326145] pci 0000:00:16.0: PME# disabled
[ 1.326285] pci 0000:00:1a.0: [8086:3b3c] type 0 class 0x000c03
[ 1.326365] pci 0000:00:1a.0: reg 10: [mem 0xd6608000-0xd66083ff]
[ 1.326676] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 1.326692] pci 0000:00:1a.0: PME# disabled
[ 1.326802] pci 0000:00:1b.0: [8086:3b56] type 0 class 0x000403
[ 1.326882] pci 0000:00:1b.0: reg 10: [mem 0xd6600000-0xd6603fff 64bit]
[ 1.327163] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 1.327174] pci 0000:00:1b.0: PME# disabled
[ 1.327267] pci 0000:00:1c.0: [8086:3b42] type 1 class 0x000604
[ 1.327550] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 1.327566] pci 0000:00:1c.0: PME# disabled
[ 1.327670] pci 0000:00:1c.1: [8086:3b44] type 1 class 0x000604
[ 1.327957] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 1.327973] pci 0000:00:1c.1: PME# disabled
[ 1.328060] pci 0000:00:1c.2: [8086:3b46] type 1 class 0x000604
[ 1.328351] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 1.328367] pci 0000:00:1c.2: PME# disabled
[ 1.328462] pci 0000:00:1c.3: [8086:3b48] type 1 class 0x000604
[ 1.328749] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[ 1.328765] pci 0000:00:1c.3: PME# disabled
[ 1.328853] pci 0000:00:1c.5: [8086:3b4c] type 1 class 0x000604
[ 1.329148] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 1.329163] pci 0000:00:1c.5: PME# disabled
[ 1.329291] pci 0000:00:1d.0: [8086:3b34] type 0 class 0x000c03
[ 1.329375] pci 0000:00:1d.0: reg 10: [mem 0xd6607000-0xd66073ff]
[ 1.329691] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 1.329707] pci 0000:00:1d.0: PME# disabled
[ 1.329799] pci 0000:00:1e.0: [8086:2448] type 1 class 0x000604
[ 1.330072] pci 0000:00:1f.0: [8086:3b09] type 0 class 0x000601
[ 1.330516] pci 0000:00:1f.2: [8086:3b29] type 0 class 0x000106
[ 1.330610] pci 0000:00:1f.2: reg 10: [io 0xe070-0xe077]
[ 1.330654] pci 0000:00:1f.2: reg 14: [io 0xe060-0xe063]
[ 1.330685] pci 0000:00:1f.2: reg 18: [io 0xe050-0xe057]
[ 1.330724] pci 0000:00:1f.2: reg 1c: [io 0xe040-0xe043]
[ 1.330768] pci 0000:00:1f.2: reg 20: [io 0xe020-0xe03f]
[ 1.330799] pci 0000:00:1f.2: reg 24: [mem 0xd6606000-0xd66067ff]
[ 1.330977] pci 0000:00:1f.2: PME# supported from D3hot
[ 1.330993] pci 0000:00:1f.2: PME# disabled
[ 1.331134] pci 0000:01:00.0: [1002:68c0] type 0 class 0x000300
[ 1.331157] pci 0000:01:00.0: reg 10: [mem 0xc0000000-0xcfffffff 64bit pref]
[ 1.331176] pci 0000:01:00.0: reg 18: [mem 0xd0020000-0xd003ffff 64bit]
[ 1.331190] pci 0000:01:00.0: reg 20: [io 0xd000-0xd0ff]
[ 1.331212] pci 0000:01:00.0: reg 30: [mem 0xd0000000-0xd001ffff pref]
[ 1.331241] pci 0000:01:00.0: supports D1 D2
[ 1.331273] pci 0000:01:00.1: [1002:aa60] type 0 class 0x000403
[ 1.331295] pci 0000:01:00.1: reg 10: [mem 0xd0040000-0xd0043fff 64bit]
[ 1.331365] pci 0000:01:00.1: supports D1 D2
[ 1.335902] pci 0000:00:03.0: PCI bridge to [bus 01-01]
[ 1.335910] pci 0000:00:03.0: bridge window [io 0xd000-0xdfff]
[ 1.335917] pci 0000:00:03.0: bridge window [mem 0xc0000000-0xd00fffff]
[ 1.335926] pci 0000:00:03.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 1.336144] pci 0000:00:1c.0: PCI bridge to [bus 02-02]
[ 1.336161] pci 0000:00:1c.0: bridge window [io 0xc000-0xcfff]
[ 1.336169] pci 0000:00:1c.0: bridge window [mem 0xd5200000-0xd65fffff]
[ 1.336196] pci 0000:00:1c.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 1.336455] pci 0000:03:00.0: [168c:002b] type 0 class 0x000280
[ 1.336540] pci 0000:03:00.0: reg 10: [mem 0xd3e00000-0xd3e0ffff 64bit]
[ 1.336838] pci 0000:03:00.0: supports D1
[ 1.336842] pci 0000:03:00.0: PME# supported from D0 D1 D3hot D3cold
[ 1.336858] pci 0000:03:00.0: PME# disabled
[ 1.337005] pci 0000:00:1c.1: PCI bridge to [bus 03-03]
[ 1.337021] pci 0000:00:1c.1: bridge window [io 0xb000-0xbfff]
[ 1.337038] pci 0000:00:1c.1: bridge window [mem 0xd3e00000-0xd51fffff]
[ 1.337065] pci 0000:00:1c.1: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 1.337276] pci 0000:00:1c.2: PCI bridge to [bus 04-06]
[ 1.337288] pci 0000:00:1c.2: bridge window [io 0xa000-0xafff]
[ 1.337304] pci 0000:00:1c.2: bridge window [mem 0xd2a00000-0xd3dfffff]
[ 1.337332] pci 0000:00:1c.2: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 1.337613] pci 0000:07:00.0: [1033:0194] type 0 class 0x000c03
[ 1.337696] pci 0000:07:00.0: reg 10: [mem 0xd1600000-0xd1601fff 64bit]
[ 1.338015] pci 0000:07:00.0: PME# supported from D0 D3hot D3cold
[ 1.338031] pci 0000:07:00.0: PME# disabled
[ 1.338172] pci 0000:00:1c.3: PCI bridge to [bus 07-07]
[ 1.338183] pci 0000:00:1c.3: bridge window [io 0x9000-0x9fff]
[ 1.338199] pci 0000:00:1c.3: bridge window [mem 0xd1600000-0xd29fffff]
[ 1.338227] pci 0000:00:1c.3: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 1.338479] pci 0000:08:00.0: [1969:1063] type 0 class 0x000200
[ 1.338545] pci 0000:08:00.0: reg 10: [mem 0xd0200000-0xd023ffff 64bit]
[ 1.338585] pci 0000:08:00.0: reg 18: [io 0x8000-0x807f]
[ 1.338855] pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 1.338871] pci 0000:08:00.0: PME# disabled
[ 1.339007] pci 0000:00:1c.5: PCI bridge to [bus 08-08]
[ 1.339024] pci 0000:00:1c.5: bridge window [io 0x8000-0x8fff]
[ 1.339035] pci 0000:00:1c.5: bridge window [mem 0xd0200000-0xd15fffff]
[ 1.339063] pci 0000:00:1c.5: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 1.339340] pci 0000:00:1e.0: PCI bridge to [bus 09-09] (subtractive decode)
[ 1.339358] pci 0000:00:1e.0: bridge window [io 0xf000-0x0000] (disabled)
[ 1.339377] pci 0000:00:1e.0: bridge window [mem 0xfff00000-0x000fffff] (disabled)
[ 1.339405] pci 0000:00:1e.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 1.339411] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 1.339417] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 1.339422] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 1.339428] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
[ 1.339434] pci 0000:00:1e.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
[ 1.339439] pci 0000:00:1e.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
[ 1.339445] pci 0000:00:1e.0: bridge window [mem 0x000dc000-0x000dffff] (subtractive decode)
[ 1.339451] pci 0000:00:1e.0: bridge window [mem 0xc0000000-0xfeafffff] (subtractive decode)
[ 1.339579] pci_bus 0000:00: on NUMA node 0
[ 1.339586] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 1.340288] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEG3._PRT]
[ 1.340443] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
[ 1.340582] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
[ 1.340730] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
[ 1.340919] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
[ 1.341071] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
[ 1.341175] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 1.341817] pci0000:00: Requesting ACPI _OSC control (0x1d)
[ 1.342419] pci0000:00: ACPI _OSC control (0x1d) granted
[ 1.342762] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.342916] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.343071] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.343255] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.343408] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.343562] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.343745] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.343898] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.344051] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.344234] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.344386] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.344539] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.344738] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.344891] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.345046] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.345229] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.345381] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.345534] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.345717] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.345878] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.346039] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.346812] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.346963] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.347117] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.347301] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.347453] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.347606] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.347790] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.347943] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.348097] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.348280] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.348431] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.348586] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.348784] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.348936] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.349089] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.349283] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.349441] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.349595] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.349778] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.349930] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.350084] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.350866] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.351021] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.351178] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.351364] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.351519] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.351675] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.351862] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.352016] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.352171] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.352357] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.352512] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.352682] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.352885] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.353040] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.353196] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.353382] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.353535] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.353690] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.353876] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.354029] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.354185] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.354962] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.355115] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.355268] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.355453] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.355605] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.355759] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.355953] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.356108] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.356260] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.356444] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.356594] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.356747] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.356947] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.357099] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.357253] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.357436] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.357589] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.357743] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.357926] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.358078] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.358232] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.359003] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.359156] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.359320] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.359511] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.359660] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.359814] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.359997] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.360148] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.360299] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.360483] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.360634] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.360788] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.360987] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.361139] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.361292] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.361476] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.361627] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.361781] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.361964] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.362116] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.362270] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.363057] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.363217] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.363375] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.363559] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.363711] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.363865] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.364048] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.364200] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.364354] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.364538] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.364690] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.364843] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.365043] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.365194] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.365349] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.365533] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.365684] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.365837] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.366036] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.366190] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.366345] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.367110] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.367263] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.367419] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.367602] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.367754] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.367909] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.368092] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.368244] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.368397] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.368581] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.368734] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.368888] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.369087] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.369250] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.369409] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.369593] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.369745] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.369898] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.370082] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.370235] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.370389] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.371154] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.371307] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.371462] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.371647] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.371799] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.371952] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.372136] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.372290] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.372446] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.372639] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.372796] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.372950] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.373151] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.373302] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.373453] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.373637] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.373789] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.373943] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.374126] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.374275] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.374428] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.375199] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.375353] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.375506] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.375691] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.375852] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.376013] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.376197] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.376351] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.376506] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.376690] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.376842] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.376995] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.377194] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.377346] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.377500] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.377683] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.377836] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.377991] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.378175] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.378327] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.378481] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.379268] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.379425] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.379581] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.379765] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.379916] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.380067] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.380251] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.380403] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.380557] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.380740] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.380892] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.381046] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.381246] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.381398] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.381552] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.381736] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.381889] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.382042] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.382225] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.382377] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.382540] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.383344] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.383499] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.383653] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.383839] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.383991] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.384143] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.384325] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.384477] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.384630] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.384814] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.384966] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.385120] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.385320] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.385473] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.385628] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.385812] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.385975] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.386133] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.386319] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.386471] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.386624] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.387403] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.387555] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.387708] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.387890] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.388041] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.388193] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.388376] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.388527] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.388680] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.388863] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.389014] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.389176] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.389381] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.389532] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.389686] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.389869] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.390020] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.390175] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.390359] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.390512] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.390667] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.391452] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.391605] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.391759] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.391944] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.392098] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.392252] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.392435] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.392598] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.392755] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.392938] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.393089] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.393241] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.393440] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.393592] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.393746] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.393930] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.394082] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.394235] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.394419] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.394571] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.394724] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.395505] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.395658] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.395812] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.396010] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.396163] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.396316] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.396500] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.396652] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.396805] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.396988] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.397140] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.397293] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.397491] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.397642] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.397795] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.397978] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.398130] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.398282] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.398465] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.398618] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.398770] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.399573] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.399729] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.399884] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.400068] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.400221] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.400374] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.400559] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.400712] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.400867] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.401050] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.401203] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.401358] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.401557] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.401710] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.401864] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.402047] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.402201] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.402355] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.402548] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.402706] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.402858] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.403639] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.403792] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.403947] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.404130] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.404284] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.404439] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.404623] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.404775] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.404930] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.405113] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.405266] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.405421] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.405619] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.405773] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.405934] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.406124] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.406275] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.406428] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.406611] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.406761] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.406913] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.407705] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.407859] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.408013] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.408198] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.408349] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.408502] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.408686] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.408838] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.408991] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.409184] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.409342] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.409497] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.409696] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.409849] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.410004] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.410187] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.410339] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.410495] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.410678] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.410830] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.410984] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.411765] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.411917] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.412069] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.412252] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.412401] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.412562] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.412752] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.412903] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.413058] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.413241] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.413392] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.413544] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.413743] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.413894] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.414047] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.414231] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.414384] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.414538] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.414721] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.414872] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 1.415024] [Firmware Bug]: ACPI: BIOS _Dwight I followed the wiki; that was the one I was thinking of in my original post. And thanks for explaining why it didnt do anything (had to had _hcd to the xhci). I have SINCE moved to Fedora to test out their new PM and virtualization support, but I do want to continue this thread as... im having the same issues.
Interestingly, thanks to Fedora Automatic Bug Reporting Tool, the freezes I was experiencing with the fixes from the wiki explain some things. When I suspend with those fixes and come back, NetworkManager is "unmanaged" and I start experiencing Soft Kernel Locks from "Tee", Not the first time I've had Soft Kernel Locks, though they were typically from Kworker, so this brings 2 questions.
What could make NetworkManager suddenly become worthless and list my eth0 and wlan0 be "Unmanaged" and what does "Tee" do in the kernel?
Also, whats the difference between ehci_hcd and xhci_hcd? I know xhci_hcd is for the experimental USB3 support, but I couldnt find any information on ehci -
I talked my sister into getting a iMac 24" 2.16GHz. (Her first Mac)
After showing her how to use it, I decided to do a test to see how much speed I would gain if I got one.
I brought along a copy of an iMovie/iDVD project on a FW disk and copied the whole thing to the HD on her new Mac.
I then tested the speed of rendering a 2 hour video (36 gig iMovie project) which my Mac takes around 6 hours to compress and encode before it begins to burn the DVD.
I was looking for a HUGE speed boost that would convince me to shell out the $2000.00 to get one for myself.
Using her computer, I would only save about 30 minutes.
I guess for $500.00 more I could get a MacPro which has Two 2.66GHz Dual-Core Intel Xeon “Woodcrest” processors, but would I see any REAL increase in speed?.. Can't,,, my projects are usually HUGE and require "Best Quality" setting which does not 'pre-render' unless I am not understanding what you mean. ..
QT/Full Quality, yepp, that's what I meant.. though, iDVD allows only a max. of 120min, the file couldn't be larger than 26GB... usual advice for video makers: more harddrive space, much more hdd space, moooooore...
as said. if you hand-over a complex iM project with lots of different files and formats, you increase the encoding time; and on my German board, I read the advice to avoid mp3 in iM projects, cause those could slow down iDVD dramatically... (one guy converts every audio import into aiff... before usage...) ...
but....
PC-guys LOVE to discuss 'speed', I never ever had any concerns about speed on my Mac..
as long as you don't render a CGI hairy KingKong or calculate the weather in the year 2020, speed is - imho - no criteria... as you said: a Mac product looks better, more professional, 'feels' better...
those 'nerds', watching their activity meters, are faster, so what - but what do they CREATE faster...? benchmarks... ??
give'em a break with those:
http://movies.apple.com/movies/us/apple/getamacads2/work480x376.mov
http://movies.apple.com/movies/us/apple/getamac/betterresults_480x376.mov
aaand 'Mac'/Justin Long is partner of Bruce Willis in http://www.imdb.com/title/tt0337978/ , Yippee Ki Yay M.. ;)) -
Very Slow Time Capsule WiFi Speeds - Disappointing
Hi,
I've read a lot about this in the TC posts, but have yet to see a solution. The wireless speeds on my 1TB TC is solidly slower than my old Linksys router. Whereas my Linksys can manage speeds greater than 12,000kb/s, the TC can only manage around 6 max. Most of the time, it's much slower. I've disabled backups, and nothing is different other than removing the Linksys, and replacing it with the TC. Needless to say, this is very troubling. And yes, I've applied the recent airport update to my mac, and the system update to the TC.
Has anyone found a solution for this, and if not, has Apple confirmed this as an issue.
Help!OK, I'm not sure about this, it's just speculation, but I have an idea. The problem with AEBS, and why it couldn't be used to backup to USB drives reliably, is that the data being sent there was not acknowledged, i.e. there was no receipt from Airport saying, "I successfully received that data." I would imagine lots of wireless routers don't bother acknowledging - if the data gets lost, another request will surely get sent again. ACKs tend to slow things down - satellite cable modems even pre-acknowledge packets due to TCP's problem with ACK latency. TCP requires decent timing and ACKs to perform well. But you can't have that on a backup solution. You need to ACK the data. So the TC (and now with the firmware upgrade, AirDisk) have to ACK the data, which slows things down, which makes your wireless seem slower. Again, this is all just speculation, but I think it's a reasonable theory.
-
NitroAV FireWire 800/1394b Express Card (34)
After some foot dragging by FireWire direct, today I finally received the NitroAV FireWire 800/1394b Express Card ordered almost a month ago.
First Impressions: Unimpressive at best.
According to the FireWire direct rep, it is supposed to work using the Mac OS built in drivers and require no additional driver....
Upon first insertion, my MacBook Pro promptly went into a kernel panic.
NOT a good introductory performance!
Upon restart, I did get the thing to work, "sort of".
First, it requires AC power even with a 2.5" external drive meant for bus power. Bummer, but so be it. However, less acceptable: it is VERY fussy about sequence, reminding me of evil SCSI voodoo rituals from the past century. Seems it only likes to work once- if I remove the card, it requires a reboot to recognize anything attached to it subsequently.
Functionality is intermittent. Sometimes I can mount and unmount a drive several times in a row, sometimes just once before it fails to recognize the drive and requires another reboot. One drive it took a long time to recognize but eventually it did- only to freeze up rock solid soon thereafter requiring an uncomfortable long push on the power button to shut down- nothing else worked. That drive was a known to be working Lacie, the first a known to be working WiebeTech and both are totally reliable on my G5 and previously completely reliable on the MacBook Pro using the integrated FireWire 400 port.
Unscientific results so far show a modest speed increase transferring a few large files, nothing like double the FireWire 800 speed hoped for. In any case if it ain't reliable it ain't gettin' used. Hoping for a driver solution in 10.4.7? (Wishful thinking)
No one likes a fussy device, much less one doomed to corrupting directories with that kind of behavior. I'm disappointed with Apple for omitting the FireWire 800 port on the 15 inch model and leaving us with this cheesy "solution".
I am not a big fan of dongles, or things like Express cards which are just asking for trouble by introducing intermediary third party connectivity issues exactly like these...
Oh yeh, and the little metal door on the Express Card slot tends to hang open and not snap closed- just to add insult to the whole process.Well, after two days of use I have a bit of data regarding the NitroAV (and Apple's implementation of ExpressCard/34).
First some general observations: like bigwheel, there are a few too many rough edges to be fully pleased. After inserting the card, a menu bar icon appears next to the Airport icon. On mouse over, the drop down shows "Unknown Vendor" and "Firewire Controller" are greyed out, while the 3rd "Power off Card" is selectable but does NOT power down the card. Looks like I have to shut down the MBP, then eject the Nitro card.
I also can confirm intermittent unmounting and remounting. My latest experiment is to leave the drive mounted and then have it wake up after sleep. So far it's worked once, but will post if it continues to find my FW 800 drive over time.
One major design flaw of the ExpressCard implementation - to engage the card you push in until it clicks, while to disengage the card you merely push in a second time. But how are you supposed to ATTACH FW800 cables?? I find I have to try to hold the ExpressCard firmly so it doesn't go in while fumbling with the FW800 connector. WAY too fussy...
OK, here's some actual test data, involving transfers of 1,000 MB of files (147 Canon RAW files, approx 7 MB each).
I used three hard drives for various transfers -
1. Internal stock 100 GB - 5400 rpm (TOSHIBA MK1032GSX)
2. FW 800 / 400 500 GB - 7200 rpm (Seagate 3500841A in OWC Mercury Elite case)
3. FW 800 / 400 250 GB - La Cie 7200 rpm drive
All test are transfer of 1 GB of files from HD to HD-
Test 1: Internal to FW 400 - 68 seconds
Test 2: Internal to FW 800 - 65 seconds
Test 3: MBP built in FW 400 daisy-chained - 54 seconds
Test 4: Nitro FW 800 daisy chained - 43 seconds
Test 5: Nitro FW 800 port A to Nitro FW 800 port B - 43 seconds
Test 6: MBP built in FW 400 to Nitro FW 800 - 35 seconds
So it looks like there is some speed increase, but I was surprised that mixing the FW 400 and FW 800 ports gave the fastest transfer speeds! The Nitro card is dependent on Apple's implementation of buses, and this seems to be the winning combo. Not that intuitive that shifting one of the FW 800 devices down to FW 400 will speed things up, but that's what my simple test seemed to imply.
I didn't test read times only, but it would seem that these should speed up (and hopefully speed up my primary application of Aperture).
MBP 2.0, 2GB Mac OS X (10.4.6) -
Here's the deal. Currently running SL 10.6.8 on a MAC Mini. Planning for eventual upgrade to ML. Have a 1TB external hard drive partitioned into two volumes, one volume for Time Machine and one volume for SL which I periodically update using Superduper. Thus I always have a point-in-time bootable backup on the external hard drive.
The MAC Mini supports Firewire 800. However, booting from my current external hard disk is pretty slow, since it only supports Firewire 400. I am considering buying an Iomega MiniMax which supports Firewire 800. Then, I would use the MiniMax as my bootable backup volume, and relegate the older hard drive to Time Machine.
So, question #1 is, can I daisychain the new MiniMax between the MAC Mini and my existing external hard drive? My expectation is that the new Mini Max would run using Firewire 800 and that the existing hard drive would run at Firewire 400 speed as it does today. If it doesn't (e.g., daisychaining in the Firewire 400 external disk with the MiniMax Firewire 800 external disk ends up running the whole leg at 400), my resolution will be to run the existing hard disk off an available USB port and have just the MiniMax running at Firewire 800.
Why am I going to all this trouble? That's question #2. I don't trust upgrades; they always break something. When I upgraded from 10.5.x to 10.6.x, the web directories got renamed, and all of my web apps 403'd until I figured out what happened. Plus, I have accounts for other family members, and in order to ensure their ability to use the computer during my upgrade process, I need to have the ability to fall-back quickly to a known-stable version of OSX. So what I'm trying to do is insulate myself from problems by partitioning the MiniMax into two volumes, taking a Superduper image of my current installation on the Mac Mini to MiniMax external drive volume 1, then upgrading to ML on the MAC Mini, and take a SuperDuper image of that to MiniMax external drive volume 2. Then, if the upgrade results in problems I can't resolve immediately, I can simply reimage the MAC Mini from MiniMax volume 1. BUT ...
... I've read that the ML installation creates a "service and support" partition that is different than the startup disk. I'm concerned that I won't be able to reimage the hard disk in the MAC Mini once I upgrade it to ML because of the partitioning changes it introduces on the startup disk. Theoretically, I +should+ be able to use the disk utility on my SL system to repartition the disk in the MAC Mini prior to reimaging it from my backup, but I'm considering the possibility that the new partition may be of a type that the SL disk utility cannot identify, and might therefore be unable to delete or even detect. So I'm hoping someone else has been down this road and can advise me. Even at Firewire 800 speeds, booting from an external disk is still going to be slow, so I want to be able to restore my SL image to the MAC Mini hard disk.
A little background on me. I work for a major disaster recovery provider. I used to have a Mac PRO G5, which I got used, and the first thing I did with it was install a second hard disk, SuperDupe an image from the first disk to the second, and made sure I could boot from the second. THEN I started using and customizing the MAC. I really feel vulnerable with the MAC Mini, since it only has the single internal hard drive - sort of like going out in public dressed only in a long T-shirt. So my whole thing is, I ABSOLUTELY MUST BE ABLE TO PUT THINGS BACK THE WAY THEY WERE before I do the migration to ML.
Obsessive-cumpulsive? Yep. Anal? You got it. That's why I'm in the DR business.You may have overloaded the port, following the instructions below it should reset:
+1. Shut down the computer.+
+2. Disconnect all devices and all other cables, except the keyboard and mouse cable(s).+
+3. Disconnect the computer from the power outlet and wait for 3 to 5 minutes.+
+4. Plug the computer back in and turn it on.+
+5. Reconnect the device(s) (one at a time if there is more than one) and test. Test with each port if you have more than one.+
http://support.apple.com/kb/HT1317?viewlocale=en_US -
Fire wire 800 and the 24" imac
I'm strongly considering purchasing a 24" iMac. I see that a lot of people are having problems using their 800 port with external hard drives. I was wondering if anyone out there has had any success using it? The main reason that i'm buying the 24" instead of a smaller one is the 800 port. What do you guys thing...hold off until they fix it?
Message was edited by: Big CBTom,
Have you verified that using both the FW 400 and 800 ports at the same time really gives you full speed on both ports on your imac? (Check the FW speed in "About this Mac" with both connected). The reason I ask is that when I have a FW800(only) drive plugged into my Powerbook G4,, I get FW 800 speed. However, when I plug in a FW device of any kind to the FW 400 port, both ports drop to FW 400 speed. I have a FW 400 cardbus adapter also, and even if I plug all FW 400 devices into the cardbus adapter, I still only get FW 400 speed out of the FW 800 port.
So I am curious if the ports on the new imac are actually independent (like they are on a Mac Pro), or if they continue to share one FW chip. I wish to have a Firewire audio interface connected to the FW 400 port and a fast hard drive connected to the FW 800 port and still get maximum performance out of each. Any further info 2ould be appreciated.
Bob -
Mixing FireWire 400 with FireWire 800
How do I connect FireWire 400 Peripherals and FireWire 800 Peripherals to the single FireWire 800 port and preserve the FireWire 800 speed to the computer for the Firewire 800 Peripherals? (Obviously, the 400 speed peripherals cona only send and receive at 400 speed.)
My guess is that connecting the FireWire 800 peripherals to the computer and adding the 400 peripherals at the end of the 800 daisy chain may work. However, recalling the mixing things in other contexts (USB 1.x vs. 2.x and WiFi 802.11g vs. 802.11n) drags every device down to the slowest speed. Will that happen on a FireWire 800 and 400 daisy chain?
Anyone know of a FireWire 800 hub?jnsail wrote:
How do I connect FireWire 400 Peripherals and FireWire 800 Peripherals to the single FireWire 800 port and preserve the FireWire 800 speed to the computer for the Firewire 800 Peripherals?
You cannot. If devices of different speeds are daisy-chained, the speed of the entire chain will drop to the speed of the slowest device, in this case FW400. A hub won't help.
The workaround is to get an ExpressCard FireWire adapter, and connect one set of devices to that, and the other set to the MBP's FW800 port. -
I have an older iMac (3.06 GHz Intel Core i3). I currently have 3 external firewire 400 drives daisy-chained to it. I use a 800 to 400 adapter on the back of the iMac to convert from 800 down for my drives. I was just looking at OWC and considering a new external. Just wondering if it would be worth my while to pay extra to get a USB3/firewire 800 enclosure instead of a 400. If I hook up the 800 directly to the iMac, then use the 800/400 adapter off the extra port on the back of the first drive to run the other 4 400 drives, will I be getting the 800 speed from the first drive, or will it be downgraded to 400 (speed of the older drives). If I was starting from scratch, it wouldn't be an issue, but since I don't want to loose the other 4TBs+ on my other drives. Hope someone knows the answer. I've heard conflicting stories on how this actually works.
ThanksJust wondering if it would be worth my while to pay extra to get a USB3/firewire 800 enclosure instead of a 400.
If you think you'll ever upgrade you Mac I'd get the FW800/USB3.0 model so it will be usable at it's intended speed with the new Mac.
OT -
Firewire 800 intentionally limited to 400
With nothing but a FW800 drive plugged into any fw port, the drive is listed as capable of 800 speed, but communicating at 400. The system profiler shows a "phantom" unknown/unknown device, with a top speed of 400.
I dug out the IORegistryTools from the developers kit, and found the "unknown device" to be an IORegistryEntry, in the IOFirewireLocalNote with a listed max speed of "Ox2" (400) instead of "0x3" (800).
In short, the OS is intentionally limiting the max fw speed to 400, instead of its rated 800.
Why? How do I change that registry entry?
PPC G5 Quad running 10.5.1.Tracy, et al.,
While disconcerting, it does seem that this may be a "non-issue"...
I ran 3 benchmarking applications (AJA's Kona Test, Blackmagic's Disk Test, and the QuickBench from Intech's Speedtools) on two different FW800 enclosures. All three apps gave nearly identical results...
Single drive inside of a WiebeTech ToughTech: Average 50.3 MB/s read and 48.0 MB/s write.
(500 GB drive formatted with HFS+ Journaled)
Dual drives in a OWC Mercury Elite Pro-AL 800: Average 77 MB/s read and 54 MB/s write.
(2-400 GB drives formatted with HFS+ Journaled, in a RAID-0 Striped configuration)
The tests were done using 100+ MB test file sizes where available.
So, it seems that the speeds on my multiple-drive enclosure are reflective of those faster than FW400...
Well, at least maybe you can get Apple to consider changing the description of the "repeater device"...
Message was edited by: davemcc
Maybe you are looking for
-
How do i open a secured document,need to prin out the contents?
How do I open a secured document? I need to print out the contents.
-
Open file dialogue hangs with extension panels
Hi. I have PS CS5 64 bit running on a PC, Win 7. Everything has been working fine but I have recently installed two new extension panels - Fundy Image Brander and Tych Panel. When either of these scripts require you to input a file to open via the Op
-
HT5278 How to update my iPhone to ios5
How to update my iPhone 3gs to ios 5
-
I'm trying to make a small program that displays some text in a frame, but the frame should be transparent so the user can see the text, and whats behind the frame on the desktop. I've looked for a way to set the color of the current frame, or just t
-
Need to Download Need to Download Adobe Photoshop Elements 10
Hey guys. I've moved to a new system and need to download Adobe Photoshop Elements 10. I can find the serial number details in my account, but no download link. The product/trials page only takes me to version 12. Any and all help in finding this elu