Problem with journalizing
Hi all,
I was trying to use the 'Change data capture' feature in ODI. I was able to start the journal for 1 of my models. In the operator the process failed giving the error :
java.sql.SQLException: ORA-00439: feature not enabled: Streams Capture
Then, I thought the problem might have been because the db user did not have privileges. So i executed the following pl sql block in the sql prompt :
BEGIN
DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE(GRANTEE => 'DATA2');
END;
/ as per the instructions in the designer(DATA2 is the name of the db user, from where the model takes the data ). Still the same error came. Then I figured that in the V$OPTION view the value of the parameter 'Streams Capture' was false. Now I am trying to set this 'Streams Capture' parameter to 'TRUE'. The 'update' command didnt seem to work. The error I got was :
ORA-02030: can only select from fixed tables/views
How do I set the 'Streams Capture' parameter to 'TRUE'?
And am I on the right track?Please help.
P.S : I am using the Oracle 10g Express Edition.
Regards,
Divya
I'm not sure that Express has the LogMiner fiunctionality available. I think this may be an Enterprise feature.
Similar Messages
-
Add a dimension - Problems with journal
Hi,
We need to add to a dimension to an existing application that has journal defined.
We have done the following steps:
1) We add and assign the new dimension to the application succesfully.
2) We try to create within the journal wizard, the new journal template adding the new dimension and we receive the following error "The system cannot create journal template".
We wanted to know, if is posible to generate manually the template or what is the best practice to add a new dimension in an application that has journals.
Thanks in advance.
Regards,
JuanHi,
try one of these:
Solution1:
This error will occur if the query files folder is missing from each of the
problem applications. To resolve, simply copy the query file folder or
create one under each application and run through the journal wizard again.
Solution 2:
Reason:That issue may arise if native Excel is configured to open less than three
sheets by default on the client machine used to build the template.
Solution:
You can modify the Excel settings:
- In Excel 2003, select Tools, Options and click General in the Options
dialog box. Then change the setting for "Sheets in new workbook".
- In Excel 2007, click on the Office button and then on the Excel Options
button. In the Popular tab, "When creating new workbooks", please change
the "Include this many sheets" setting.
If it is different than 3, please set it back to 3 and test to build your
journal template again.
Solution 3:
Reason:The journal template couldn`t be created if the application
have more than 7 dimensions which are set for secure.
Soln: recommend setting dimension for secure as less than 7.
thnks. -
Problem with journal Periods Review Button
Hi All,
Go to Journals Post Form -->
Find Journal Batches -->
enter Period -->
click on Find -->
Select Any period -->
---> Click on "Review Batch" Button
I am expecting a window/form (I am not sure but some thing should come) at tis time. But, Nothing is shown/different on the screen. Before raising an SR, do I have to check for anything?
Or can I raise an SR with Oracle?
Oracle apps Version R12 - 12.0.4Hi;
Please check below notes which could be helpful on your issue:
In GLXJEPST The Button "Review Batch" Returns Error FRM-40815 [ID 309634.1]
Why is the Approve Batch button disabled in the Enter Journals Form when Reviewing a Journal From the Notifications Screen? [ID 270422.1]
If its not help i suggest enable trace:
How to enable and retrieve debug log messages [ID 433199.1]
Running a Trace on a Form [ID 148143.1]
Running a Trace on a Process [ID 148145.1]
FAQ: Common Tracing Techniques within the Oracle Applications 11i/R12 [ID 296559.1]
Regard
Helios -
Problem with Legal Consolidation for Journal
Hi BPC Friends
I have the application icmatching with data and I have written other values with Journal.
I have run the package legal consolidation.
I have this problem:
for the value that I have loaded into the application, the logic consolidation works correctly, indeed it writes a new record with different datasource
but for the value that I have written into the application using the Journal the logic doesn't work correctly, indeed it writes into the database a new record like the original but with contrary value so I lose also the value that I wrote with the journal
Could you please help me?
thanks
regards
Michele MedagliaHello Michele,
Basically what ever data that you input in journal as long as the selection on xdim is fulfilled the script will run normally.
If its write in reverse and deleted your original data, it must be something wrong in your script, you can check at first.
If the problem still you can't found, can you share us a little about the script?
hope helps -
Problem with creation of journal receivers
I have a problem.
Journal receivers are getting created for example in library R3T02DATA instead of R3T02JRN.
How do I fix this.
Any help would be appreciated
Thanks
JoeHi Joe,
you should create a JRNRCV in r3sidJRN and then you can usew CHGJRN r3siddata/qsqjrn with the new receiver
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de -
[SOLVED] Problems with systemd's journal when using syslog() in C
Hi,
I have a problem with journalctl and syslog output within a C program:
When I use journalctl in follow mode:
$ journalctl -f
and I run the folowing program in another terminal
#include <stdio.h>
#include <syslog.h>
int main()
FILE *pf;
int i;
/* logging made in file /var/log/syslog */
openlog("martins",LOG_CONS,LOG_USER);
pf = fopen("not_here","r");
if (!pf)
syslog(LOG_ERR | LOG_USER,"oops -- %m\n");
return 0;
no syslog error message appears in the journal.
But, when I modify the programm by adding a 'sleep(1);' right before 'return 0;'
there is a correct error message shown in the journal.
Is this a bug in systemd? Or do I understand something wrong with systemd's journal?
I'm actually running
linux-3.10-12-1-lts
systemd 207
with a 32Bit installation
Thanks for any hints,
Martin
Last edited by thesofty (2013-10-01 19:10:13)Now, I understand what's going on:
1) There is an known issue about a race condition in journald when the logging process exits. In this case the message isn't assigned to the user whose process generated the message.
2) Apparently the group of the journal files have been changed from 'adm' to 'systemd-journal' in Arch Linux around April 2013.
But still I only have been member of 'adm' as described in the journal tutorial on http://0pointer.de/blog/projects/journalctl.html. So I can only see syslog messages, which are correctly assigned to my own user account. The messages with the race condition, as mentioned above, have been invisible to me.
After joining to the new right group again:
$ sudo usermod -d G martin systemd-journal
I also see the syslog messaes just before exiting the process again :-). -
Slow in start-up + problems with Entourage
Since I have installed Mac OS X Lion I do have some problems.
My Macbook Pro doesn't start up as fast as he used with previous Mac version, how come? I unchoose the box to re-open programs at start-up.
Another thinhg, from time to time my Entourage (2008) needs to be closed to sent a problem report to Microsoft, before Mac OS X Lion I had no problems with this.
Will there be soon an update which fixes all these bugs?I doubt you will like this suggestion, but since you installed a new drive I would recommend doing this:
Extended Hard Drive Preparation
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Reinstall Snow. If you continue to have problems it could be got a slightly defective DVD or you may have marginal RAM. -
[SOLVED] Problem with second SATA drive
My laptop has two hard drive bays, and just recently I added a second SATA drive (moved it from my old laptop) to the extra bay.
Now, anytime the second hard drive /dev/sdb has any heavy disk activity, it appears to cause a shutdown of the SATA port for the first drive (/dev/sda)! Though the second drive is still fine, and I can still write to it until the system crashes from the root drive (on /dev/sda) being shutdown.
If I don't mount and use the second drive, the first drive works just fine, and I can pound it with traffic without issue.
I can reproduce this problem by copying large amounts of data to drive 2.
This is when I get in my dmesg when the first SATA drive shuts down:
[ 3013.249525] ata1.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x6 frozen
[ 3013.249532] ata1.00: failed command: READ FPDMA QUEUED
[ 3013.249539] ata1.00: cmd 60/08:00:78:b8:ba/00:00:24:00:00/40 tag 0 ncq 4096 in
[ 3013.249539] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3013.249543] ata1.00: status: { DRDY }
[ 3013.249545] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249559] ata1.00: cmd 61/08:08:b8:60:7b/00:00:29:00:00/40 tag 1 ncq 4096 out
[ 3013.249559] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249562] ata1.00: status: { DRDY }
[ 3013.249564] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249568] ata1.00: cmd 61/08:10:c0:60:7b/00:00:29:00:00/40 tag 2 ncq 4096 out
[ 3013.249568] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249570] ata1.00: status: { DRDY }
[ 3013.249572] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249576] ata1.00: cmd 61/08:18:c8:60:7b/00:00:29:00:00/40 tag 3 ncq 4096 out
[ 3013.249576] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249578] ata1.00: status: { DRDY }
[ 3013.249580] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249585] ata1.00: cmd 61/08:20:48:12:d7/00:00:18:00:00/40 tag 4 ncq 4096 out
[ 3013.249585] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249587] ata1.00: status: { DRDY }
[ 3013.249589] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249593] ata1.00: cmd 61/08:28:28:63:38/00:00:19:00:00/40 tag 5 ncq 4096 out
[ 3013.249593] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249595] ata1.00: status: { DRDY }
[ 3013.249597] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249601] ata1.00: cmd 61/08:30:28:6f:38/00:00:19:00:00/40 tag 6 ncq 4096 out
[ 3013.249601] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249603] ata1.00: status: { DRDY }
[ 3013.249605] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249609] ata1.00: cmd 61/08:38:28:98:ae/00:00:25:00:00/40 tag 7 ncq 4096 out
[ 3013.249609] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249611] ata1.00: status: { DRDY }
[ 3013.249613] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249617] ata1.00: cmd 61/08:40:d8:79:3b/00:00:25:00:00/40 tag 8 ncq 4096 out
[ 3013.249617] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249619] ata1.00: status: { DRDY }
[ 3013.249621] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249625] ata1.00: cmd 61/08:48:08:98:b6/00:00:18:00:00/40 tag 9 ncq 4096 out
[ 3013.249625] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249627] ata1.00: status: { DRDY }
[ 3013.249629] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249633] ata1.00: cmd 61/08:50:10:98:36/00:00:19:00:00/40 tag 10 ncq 4096 out
[ 3013.249633] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249636] ata1.00: status: { DRDY }
[ 3013.249640] ata1: hard resetting link
[ 3013.575549] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3013.576784] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3013.578334] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3013.578588] ata1.00: configured for UDMA/133
[ 3013.592223] ata1.00: device reported invalid CHS sector 0
[ 3013.592233] ata1.00: device reported invalid CHS sector 0
[ 3013.592238] ata1.00: device reported invalid CHS sector 0
[ 3013.592242] ata1.00: device reported invalid CHS sector 0
[ 3013.592246] ata1.00: device reported invalid CHS sector 0
[ 3013.592250] ata1.00: device reported invalid CHS sector 0
[ 3013.592254] ata1.00: device reported invalid CHS sector 0
[ 3013.592258] ata1.00: device reported invalid CHS sector 0
[ 3013.592263] ata1.00: device reported invalid CHS sector 0
[ 3013.592267] ata1.00: device reported invalid CHS sector 0
[ 3013.592271] ata1.00: device reported invalid CHS sector 0
[ 3013.592302] sd 0:0:0:0: [sda]
[ 3013.592306] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592310] sd 0:0:0:0: [sda]
[ 3013.592313] Sense Key : 0xb [current] [descriptor]
[ 3013.592320] Descriptor sense data with sense descriptors (in hex):
[ 3013.592323] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592342] 00 00 00 00
[ 3013.592351] sd 0:0:0:0: [sda]
[ 3013.592353] ASC=0x0 ASCQ=0x0
[ 3013.592358] sd 0:0:0:0: [sda] CDB:
[ 3013.592361] cdb[0]=0x28: 28 00 24 ba b8 78 00 00 08 00
[ 3013.592376] end_request: I/O error, dev sda, sector 616216696
[ 3013.592414] sd 0:0:0:0: [sda]
[ 3013.592417] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592421] sd 0:0:0:0: [sda]
[ 3013.592423] Sense Key : 0xb [current] [descriptor]
[ 3013.592428] Descriptor sense data with sense descriptors (in hex):
[ 3013.592431] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592449] 00 00 00 00
[ 3013.592458] sd 0:0:0:0: [sda]
[ 3013.592460] ASC=0x0 ASCQ=0x0
[ 3013.592465] sd 0:0:0:0: [sda] CDB:
[ 3013.592467] cdb[0]=0x2a: 2a 00 29 7b 60 b8 00 00 08 00
[ 3013.592482] end_request: I/O error, dev sda, sector 695951544
[ 3013.592505] sd 0:0:0:0: [sda]
[ 3013.592508] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592512] sd 0:0:0:0: [sda]
[ 3013.592514] Sense Key : 0xb [current] [descriptor]
[ 3013.592519] Descriptor sense data with sense descriptors (in hex):
[ 3013.592522] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592540] 00 00 00 00
[ 3013.592549] sd 0:0:0:0: [sda]
[ 3013.592551] ASC=0x0 ASCQ=0x0
[ 3013.592556] sd 0:0:0:0: [sda] CDB:
[ 3013.592558] cdb[0]=0x2a: 2a 00 29 7b 60 c0 00 00 08 00
[ 3013.592572] end_request: I/O error, dev sda, sector 695951552
[ 3013.592583] sd 0:0:0:0: [sda]
[ 3013.592586] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592589] sd 0:0:0:0: [sda]
[ 3013.592592] Sense Key : 0xb [current] [descriptor]
[ 3013.592597] Descriptor sense data with sense descriptors (in hex):
[ 3013.592599] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592618] 00 00 00 00
[ 3013.592626] sd 0:0:0:0: [sda]
[ 3013.592628] ASC=0x0 ASCQ=0x0
[ 3013.592632] sd 0:0:0:0: [sda] CDB:
[ 3013.592635] cdb[0]=0x2a: 2a 00 29 7b 60 c8 00 00 08 00
[ 3013.592649] end_request: I/O error, dev sda, sector 695951560
[ 3013.592665] sd 0:0:0:0: [sda]
[ 3013.592668] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592671] sd 0:0:0:0: [sda]
[ 3013.592673] Sense Key : 0xb [current] [descriptor]
[ 3013.592678] Descriptor sense data with sense descriptors (in hex):
[ 3013.592684] Aborting journal on device dm-0-8.
[ 3013.592701] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
[ 3013.592687] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592723] 00 00 00 00
[ 3013.592729] sd 0:0:0:0: [sda]
[ 3013.592730] ASC=0x0 ASCQ=0x0
[ 3013.592733] sd 0:0:0:0: [sda] CDB:
[ 3013.592735] cdb[0]=0x2a: 2a 00 18 d7 12 48 00 00 08 00
[ 3013.592744] end_request: I/O error, dev sda, sector 416748104
[ 3013.592752] Buffer I/O error on device dm-0, logical block 266057
[ 3013.592760] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902184 (offset 258048 size 4096 starting block 266057)
[ 3013.592766] sd 0:0:0:0: [sda]
[ 3013.592768] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592771] sd 0:0:0:0: [sda]
[ 3013.592772] Sense Key : 0xb [current] [descriptor]
[ 3013.592776] Descriptor sense data with sense descriptors (in hex):
[ 3013.592778] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592790] 00 00 00 00
[ 3013.592795] sd 0:0:0:0: [sda]
[ 3013.592797] ASC=0x0 ASCQ=0x0
[ 3013.592800] sd 0:0:0:0: [sda] CDB:
[ 3013.592801] cdb[0]=0x2a: 2a 00 19 38 63 28 00 00 08 00
[ 3013.592811] end_request: I/O error, dev sda, sector 423125800
[ 3013.592817] Buffer I/O error on device dm-0, logical block 1063269
[ 3013.592822] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5898577 (offset 970752 size 4096 starting block 1063269)
[ 3013.592842] sd 0:0:0:0: [sda]
[ 3013.592845] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592849] sd 0:0:0:0: [sda]
[ 3013.592851] Sense Key : 0xb [current] [descriptor]
[ 3013.592856] Descriptor sense data with sense descriptors (in hex):
[ 3013.592859] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592877] 00 00 00 00
[ 3013.592885] sd 0:0:0:0: [sda]
[ 3013.592887] ASC=0x0 ASCQ=0x0
[ 3013.592892] sd 0:0:0:0: [sda] CDB:
[ 3013.592894] cdb[0]=0x2a: 2a 00 19 38 6f 28 00 00 08 00
[ 3013.592908] end_request: I/O error, dev sda, sector 423128872
[ 3013.592915] Buffer I/O error on device dm-0, logical block 1063653
[ 3013.592922] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902187 (offset 1171456 size 4096 starting block 1063653)
[ 3013.592931] sd 0:0:0:0: [sda]
[ 3013.592934] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592937] sd 0:0:0:0: [sda]
[ 3013.592940] Sense Key : 0xb [current] [descriptor]
[ 3013.592945] Descriptor sense data with sense descriptors (in hex):
[ 3013.592947] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592966] 00 00 00 00
[ 3013.592974] sd 0:0:0:0: [sda]
[ 3013.592976] ASC=0x0 ASCQ=0x0
[ 3013.592980] sd 0:0:0:0: [sda] CDB:
[ 3013.592983] cdb[0]=0x2a: 2a 00 25 ae 98 28 00 00 08 00
[ 3013.592997] end_request: I/O error, dev sda, sector 632199208
[ 3013.593006] Buffer I/O error on device dm-0, logical block 27197445
[ 3013.593018] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 6425165 (offset 151552 size 4096 starting block 27197445)
[ 3013.593028] sd 0:0:0:0: [sda]
[ 3013.593031] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593034] sd 0:0:0:0: [sda]
[ 3013.593037] Sense Key : 0xb [current] [descriptor]
[ 3013.593042] Descriptor sense data with sense descriptors (in hex):
[ 3013.593045] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593063] 00 00 00 00
[ 3013.593071] sd 0:0:0:0: [sda]
[ 3013.593073] ASC=0x0 ASCQ=0x0
[ 3013.593078] sd 0:0:0:0: [sda] CDB:
[ 3013.593085] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
[ 3013.593089] cdb[0]=0x2a: 2a 00 25 3b 79 d8 00 00 08 00
[ 3013.593104] end_request: I/O error, dev sda, sector 624654808
[ 3013.593111] Buffer I/O error on device dm-0, logical block 26254395
[ 3013.593115] lost page write due to I/O error on dm-0
[ 3013.593126] sd 0:0:0:0: [sda]
[ 3013.593129] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593132] sd 0:0:0:0: [sda]
[ 3013.593135] Sense Key : 0xb [current] [descriptor]
[ 3013.593140] Descriptor sense data with sense descriptors (in hex):
[ 3013.593142] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593161] 00 00 00 00
[ 3013.593169] sd 0:0:0:0: [sda]
[ 3013.593171] ASC=0x0 ASCQ=0x0
[ 3013.593175] sd 0:0:0:0: [sda] CDB:
[ 3013.593178] cdb[0]=0x2a: 2a 00 18 b6 98 08 00 00 08 00
[ 3013.593192] end_request: I/O error, dev sda, sector 414619656
[ 3013.593198] Buffer I/O error on device dm-0, logical block 1
[ 3013.593201] lost page write due to I/O error on dm-0
[ 3013.593211] sd 0:0:0:0: [sda]
[ 3013.593213] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593217] sd 0:0:0:0: [sda]
[ 3013.593219] Sense Key : 0xb [current] [descriptor]
[ 3013.593224] Descriptor sense data with sense descriptors (in hex):
[ 3013.593227] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593245] 00 00 00 00
[ 3013.593253] sd 0:0:0:0: [sda]
[ 3013.593256] ASC=0x0 ASCQ=0x0
[ 3013.593260] sd 0:0:0:0: [sda] CDB:
[ 3013.593262] cdb[0]=0x2a: 2a 00 19 36 98 10 00 00 08 00
[ 3013.593277] end_request: I/O error, dev sda, sector 423008272
[ 3013.593283] Buffer I/O error on device dm-0, logical block 1048578
[ 3013.593286] lost page write due to I/O error on dm-0
[ 3013.593298] ata1: EH complete
[ 3013.595707] EXT4-fs error (device dm-0) in ext4_dirty_inode:4603: Journal has aborted
[ 3013.596581] EXT4-fs error (device dm-0): ext4_journal_start_sb:370: Detected aborted journal
[ 3013.596591] EXT4-fs (dm-0): Remounting filesystem read-only
[ 3020.421558] journal commit I/O error
[ 3020.421570] journal commit I/O error
[ 3020.421574] journal commit I/O error
[ 3020.421578] journal commit I/O error
[ 3020.421581] journal commit I/O error
[ 3147.052191] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
[ 3147.052197] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052209] ata1.00: cmd 60/50:00:d0:48:99/00:00:1c:00:00/40 tag 0 ncq 40960 in
[ 3147.052209] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3147.052212] ata1.00: status: { DRDY }
[ 3147.052213] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052218] ata1.00: cmd 60/18:08:28:49:99/00:00:1c:00:00/40 tag 1 ncq 12288 in
[ 3147.052218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052220] ata1.00: status: { DRDY }
[ 3147.052221] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052226] ata1.00: cmd 60/88:10:48:49:99/00:00:1c:00:00/40 tag 2 ncq 69632 in
[ 3147.052226] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052228] ata1.00: status: { DRDY }
[ 3147.052229] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052234] ata1.00: cmd 60/20:18:00:a4:ba/00:00:24:00:00/40 tag 3 ncq 16384 in
[ 3147.052234] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052236] ata1.00: status: { DRDY }
[ 3147.052239] ata1: hard resetting link
[ 3147.378368] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3148.066853] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3148.069139] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3148.069393] ata1.00: configured for UDMA/133
[ 3148.080059] ata1.00: device reported invalid CHS sector 0
[ 3148.080066] ata1.00: device reported invalid CHS sector 0
[ 3148.080071] ata1.00: device reported invalid CHS sector 0
[ 3148.080075] ata1.00: device reported invalid CHS sector 0
[ 3148.080112] sd 0:0:0:0: [sda]
[ 3148.080114] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080117] sd 0:0:0:0: [sda]
[ 3148.080118] Sense Key : 0xb [current] [descriptor]
[ 3148.080123] Descriptor sense data with sense descriptors (in hex):
[ 3148.080125] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080136] 00 00 00 00
[ 3148.080140] sd 0:0:0:0: [sda]
[ 3148.080142] ASC=0x0 ASCQ=0x0
[ 3148.080145] sd 0:0:0:0: [sda] CDB:
[ 3148.080146] cdb[0]=0x28: 28 00 1c 99 48 d0 00 00 50 00
[ 3148.080156] end_request: I/O error, dev sda, sector 479807696
[ 3148.080170] sd 0:0:0:0: [sda]
[ 3148.080171] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080173] sd 0:0:0:0: [sda]
[ 3148.080175] Sense Key : 0xb [current] [descriptor]
[ 3148.080178] Descriptor sense data with sense descriptors (in hex):
[ 3148.080180] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080190] 00 00 00 00
[ 3148.080195] sd 0:0:0:0: [sda]
[ 3148.080196] ASC=0x0 ASCQ=0x0
[ 3148.080199] sd 0:0:0:0: [sda] CDB:
[ 3148.080200] cdb[0]=0x28: 28 00 1c 99 49 28 00 00 18 00
[ 3148.080209] end_request: I/O error, dev sda, sector 479807784
[ 3148.080216] sd 0:0:0:0: [sda]
[ 3148.080218] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080220] sd 0:0:0:0: [sda]
[ 3148.080221] Sense Key : 0xb [current] [descriptor]
[ 3148.080224] Descriptor sense data with sense descriptors (in hex):
[ 3148.080225] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080236] 00 00 00 00
[ 3148.080241] sd 0:0:0:0: [sda]
[ 3148.080242] ASC=0x0 ASCQ=0x0
[ 3148.080245] sd 0:0:0:0: [sda] CDB:
[ 3148.080246] cdb[0]=0x28: 28 00 1c 99 49 48 00 00 88 00
[ 3148.080254] end_request: I/O error, dev sda, sector 479807816
[ 3148.080267] sd 0:0:0:0: [sda]
[ 3148.080268] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080270] sd 0:0:0:0: [sda]
[ 3148.080272] Sense Key : 0xb [current] [descriptor]
[ 3148.080274] Descriptor sense data with sense descriptors (in hex):
[ 3148.080276] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080287] 00 00 00 00
[ 3148.080291] sd 0:0:0:0: [sda]
[ 3148.080293] ASC=0x0 ASCQ=0x0
[ 3148.080295] sd 0:0:0:0: [sda] CDB:
[ 3148.080296] cdb[0]=0x28: 28 00 24 ba a4 00 00 00 20 00
[ 3148.080305] end_request: I/O error, dev sda, sector 616211456
[ 3148.080315] ata1: EH complete
I have experimented, and found that if I turn off NCQ on the kernel command line in my bootloader (libata.force=noncq), that it takes longer before the problem occurs. Though, if I write enough to the second drive, it does still happen after a while, just greatly reduced its chances of happening.
Is it possible that the old drive (sdb) is causing the problem? I noticed that it is much noisier than I remember when the drive head moves around.
Another curiosity while I was trying to duplicate the problem:
- I start a large file copy from sda -> sdb
- At the same time in another terminal, I do "find / -print"
- When I hear the drive 2 head moving, it pauses the output of the "find" command.
Every time I hear the head move, I see the find output pause. Its almost like the drive seek on drive 2 causes the whole Sata controller to pause while the head moves. Very odd!
Anyone have any ideas? I think the next thing I will try is borrow a drive from another machine, and do the big write to it to see if I get the same results.
If it is of any help, here is some more info on the laptop:
lspci:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1)
07:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)
0d:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 (rev 5e)
13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
13:00.1 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
19:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
cat /proc/interrupts:
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
0: 50 0 0 0 0 0 0 0 IO-APIC-edge timer
1: 958 0 0 0 0 0 0 0 IO-APIC-edge i8042
8: 1 0 0 0 0 0 0 0 IO-APIC-edge rtc0
9: 1675 0 0 0 0 0 0 0 IO-APIC-fasteoi acpi
12: 12257 0 0 0 0 0 0 0 IO-APIC-edge i8042
16: 24769 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1, mmc0, nvidia
17: 142 0 0 0 0 0 0 0 IO-APIC-fasteoi snd_hda_intel
19: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi rts_pstor
23: 1937 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb4
41: 1 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
42: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
43: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
44: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
45: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
46: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
47: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
48: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
49: 19406 0 0 0 0 0 0 0 PCI-MSI-edge iwlwifi
50: 36099 0 0 0 0 0 0 0 PCI-MSI-edge ahci
51: 14 0 0 0 0 0 0 0 PCI-MSI-edge mei
52: 386378 0 0 0 0 0 0 0 PCI-MSI-edge snd_hda_intel
53: 56803 0 0 0 0 0 0 0 PCI-MSI-edge eth0
NMI: 34 5 19 5 18 4 13 4 Non-maskable interrupts
LOC: 77964 17705 161241 14302 187823 16150 56845 12750 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 34 5 19 5 18 4 13 4 Performance monitoring interrupts
IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts
RTR: 7 0 0 0 0 0 0 0 APIC ICR read retries
RES: 13721 7023 304 110 175 110 213 123 Rescheduling interrupts
CAL: 6941 7677 2774 7670 5804 7568 7655 7673 Function call interrupts
TLB: 366 545 268 179 310 272 212 166 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 29 29 29 29 29 29 29 29 Machine check polls
ERR: 0
MIS: 0
smartctl --all /dev/sda
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: ST9500423AS
Serial Number: 5WS354LM
LU WWN Device Id: 5 000c50 044bb741b
Firmware Version: 0005DEM1
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu Sep 13 15:26:14 2012 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 105) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 113 099 006 Pre-fail Always - 54715920
3 Spin_Up_Time 0x0003 098 098 085 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1114
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 069 060 030 Pre-fail Always - 10214892
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2030
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 559
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 098 000 Old_age Always - 8590065667
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 053 049 045 Old_age Always - 47 (Min/Max 47/51)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 17
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 871
193 Load_Cycle_Count 0x0032 039 039 000 Old_age Always - 122293
194 Temperature_Celsius 0x0022 047 051 000 Old_age Always - 47 (0 17 0 0 0)
195 Hardware_ECC_Recovered 0x001a 113 099 000 Old_age Always - 54715920
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 67229123085518
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1947733828
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2798982459
254 Free_Fall_Sensor 0x0032 001 001 000 Old_age Always - 899
SMART Error Log Version: 1
ATA Error Count: 8 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 8 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
Error 7 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
Error 6 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
Error 5 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
Error 4 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 6 -
# 2 Short offline Aborted by host 90% 1 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
smartctl --all /dev/sdb
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M6
Device Model: SAMSUNG HM320JI
Serial Number: S16LJF0QB02815
LU WWN Device Id: 5 0f0000 001202815
Firmware Version: 2SS00_01
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Thu Sep 13 15:27:10 2012 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 110) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 110) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2562
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 810
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 4842
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 440
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 154
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 71
194 Temperature_Celsius 0x0022 073 073 000 Old_age Always - 55 (Min/Max 17/55)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 252 252 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 534
225 Load_Cycle_Count 0x0032 077 077 000 Old_age Always - 236803
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Last edited by johni (2012-09-16 00:46:54)It appears my drive one really is failing. It was the first drive and not the second making the loud head seek sound. I borrowed another drive from a friend, and copied my drive one to it. No problems with the new drive in place.
-
Samsung hard drive problems with mid 2009 Macbook Pro
Arghh, this is driving me mad.
I'd like to know if anyone has installed a Samsung HM641JI SATA II hard drive into a mid 2009 Macbook Pro (mine is a 2.8Ghz) and, if so, how they managed it. The drive is 640GB. These are the steps I've taken:
1. Swap out the stock drive for the Samsung
2. Boot from a USB drive which contains a mirror of my system
3. When the system identified the new disk, I formatted it with 2 partitions (GUID table, HFS journaled)
4. Reboot
5. System is very slow. Boots from USB but can't use keyboard to login
6. Switch off and try again
7. Remove Samsung drive
8. Reboot from USB (works perfectly)
9. Downgrade firmware to 1.6
10. Replace samsung drive and try again
11. System boots from USB
12. Verify that drive is running at 1.5Ghz
13. Disk utility and system profiler both crash
14. Disk unmounts by itself and other random weirdness
15. Remove Samsung drive
I've read endless reports about the firmware in this model of Macbook Pro and its issues with SATA II but struggling to find anything current and specific. Two questions:
a. Is there anythign I can do to get this drive to play nicely?
b. What drive should I get if the answer to a is no?
As a bit of background.. my system began playing up last week with lots of spinning beach balls resulting in forced switch offs. Booting from a mirror on a USB drive works perfectly so I concluded that the drive was on its way out. A drive test utility confirmed this. I'm now wondering if it really was the drive or the cable or the logic board.
Any advice appreciated.
Cheers
//AI'm coming around to the idea that this might be a problem with the SATA cable rather than the drive.
I currently have the stock drive (Hitachi) back in the macbook. It mounted for a while and was then ejected when I tried writing data to it. System profiler reports that "There was an error while scanning for Serial-ATA devices."
I was able to mount the same drive in a USB enclosure this afternoon without any problems. Right now, I seem to be having issues with both the Samsung drive and the Hitachi drive - I wasn't suspicious of thr latter because I thought it was failing.
I found one or two accounts of other people having similar problems that were resolved with a new sata cable.
How does a cable fail? Could this be my problem?
Cheers
//A -
Problems with Time Machine backup for two machines to one external drive
I have a brand new WD 500GB USB My Book external drive plugged into my Intel Mac Mini running 10.5.1 to use as a TM backup drive (TM reformatted it to HFS+ journaled). The Mini's connected by ethernet to the Airport Extreme. It works great. I setup my wife's MacBook Pro 17" Dual Core 2 w. 10.5.1 for TM using the Mac Mini's TM backup drive and it works fine (a little slower at 811.n wi-fi speeds, but OK). I have the Mac Mini setup in Energy Saver to shut down at night and restart in the morning. The morning after I setup my wife's MacBook Pro for TM I found a big black & white message (in half a dozen languages) on the Mac Mini saying start up failed and I need to reboot using the power button. I did and everything was cool. Now comes the problem, it's done it three days in a row so it looks like there is a problem with the TM setup. It didn't do this before I setup my wife's computer for TM.
Any thoughts on what is causing this? We've had minimal problems with Leopard setup (short of a brief hunt for an Airport Extreme Drive and a couple of network printers during initial setup).1 mistake @ a time wrote:
I works fine over a network if the TM drive is attached to another Mac running Leopard. It won't work with an Airport drive (Apple deep sixed that feature in the final release).
We have an Airport Extreme base station, and we plan to add an Airport Express to boost the power to reach the second floor. We are ordering 4 iMacs, 20", plus I have the Macbook 13" that I have had for a few months.
We thought we could connect one large external drive via firewire cable to one of the iMacs and use it to back up all five computers via Time Machine.
Is that possible, or does everybody need their own external drive?
Thanks!
susan -
My wife has been having problems with Safari, and many third party software and malware programs infecting her Mac Book Pro. I have tried to reset Safari but it keeps coming back, taking over Safari, changing defaults, start pages, and search engines, Etc.
Is it safe to use programs like MacKeeper, who keeps send my wife's computer message and alerts, or should I just wipe the drive and start over?
SkipI am having lot's of lag time with Safari, etc..
I'll type in a website.. and it will take 15-20 seconds to start..
Start time: 17:51:37 12/02/14
Model Identifier: MacBookPro11,3
System Version: OS X 10.10.1 (14B25)
Kernel Version: Darwin 14.0.0
Time since boot: 14 days 3:02
USB
My Passport 07B8 (Western Digital Technologies, Inc.)
Diagnostic reports
2014-11-13 QuickLookSatellite crash x2
2014-11-21 com.apple.WebKit.Plugin.64 crash
Log
Nov 30 21:32:39 PM notification timeout (pid 345, Adobe CEF Helper)
Nov 30 21:32:39 PM notification timeout (pid 99018, CEPHtmlEngine)
Nov 30 21:32:39 PM notification timeout (pid 99019, CEPHtmlEngine He)
Dec 1 09:09:03 [[0xffffff802bfa4000] OpCode 0x0C01 (Set Event Mask) from: kernel_task (0) Synchronous status: 0x00 (kIOReturnSuccess) state: 2 (BUSY) timeout: 5000] Bluetooth warning: An HCI Req timeout occurred.
Dec 1 09:52:03 PM notification timeout (pid 266, Creative Cloud)
Dec 1 09:52:03 PM notification timeout (pid 346, Adobe CEF Helper)
Dec 1 09:52:03 PM notification timeout (pid 345, Adobe CEF Helper)
Dec 1 10:04:37 process WindowServer[114] caught causing excessive wakeups. Observed wakeups rate (per sec): 170; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 12755007
Dec 1 10:31:08 ALF: ifnet_get_address_list_family error 12
Dec 1 10:59:17 process Meeting Center[2921] caught causing excessive wakeups. Observed wakeups rate (per sec): 647; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45104
Dec 1 12:24:35 process com.apple.WebKit[4567] caught causing excessive wakeups. Observed wakeups rate (per sec): 297; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 76962
Dec 1 14:31:01 process com.apple.WebKit[7400] caught causing excessive wakeups. Observed wakeups rate (per sec): 397; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 53188
Dec 1 14:43:52 process com.apple.WebKit[7400] caught causing excessive wakeups. Observed wakeups rate (per sec): 224; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 150084
Dec 1 14:47:34 process com.apple.WebKit[7400] caught causing excessive wakeups. Observed wakeups rate (per sec): 332; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 222103
Dec 1 15:03:29 process com.apple.WebKit[7400] caught causing excessive wakeups. Observed wakeups rate (per sec): 214; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 370572
Dec 1 16:38:03 SIOCPROTODETACH_IN6: utun2 error=6
Dec 1 16:38:08 SIOCPROTODETACH_IN6: utun2 error=6
Dec 1 20:08:30 jnl: disk3s2: replay_journal: from: 112328704 to: 113115136 (joffset 0x3a38000)
Dec 1 20:08:30 jnl: disk3s2: journal replay done.
Dec 1 20:27:11 com.adobe.acc.AdobeCreativeCloud.75292.UUID: Service exited with abnormal code: 5
Dec 2 08:23:00 process com.apple.WebKit[11891] caught causing excessive wakeups. Observed wakeups rate (per sec): 161; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 527508
Dec 2 09:29:37 firefox (map: 0xffffff80317c5960) triggered DYLD shared region unnest for map: 0xffffff80317c5960, region 0x7fff9ae00000->0x7fff9b000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
Dec 2 10:04:39 SIOCPROTODETACH_IN6: utun2 error=6
Dec 2 10:04:44 SIOCPROTODETACH_IN6: utun2 error=6
Dec 2 16:42:24 process com.apple.WebKit[26151] caught causing excessive wakeups. Observed wakeups rate (per sec): 153; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45002
Swap (MiB): 41556
Activity
Net: 210 in, 20 out (KiB/s)
Memory: kernel_task (UID 0) is using 1632 MB
kexts
com.cisco.kext.acsock (1.1.0)
com.wdc.driver.USB.64.10.9 (1.0.1)
Daemons
com.cisco.anyconnect.vpnagentd
com.oracle.java.JavaUpdateHelper
com.apple.installer.osmessagetracing
com.microsoft.office.licensing.helper
com.google.keystone.daemon
com.wdc.WDSmartWareService
com.oracle.java.Helper-Tool
com.adobe.fpsaud
com.wdc.SmartwareDriveService
Agents
com.adobe.AdobeCreativeCloud
com.zimbra.desktop
com.citrix.ServiceRecords
com.google.keystone.system.agent
com.apple.photostream-agent
com.genieo.completer.download
com.genieo.completer.update
com.cisco.anyconnect.gui
com.citrix.ReceiverHelper
com.citrix.AuthManager_Mac
com.citrix.FMDAgent.14800.UUID
com.oracle.java.Java-Updater
com.fiplab.MailTabProHelper
com.adobe.PDApp.AAMUpdatesNotifier.74724.UUID
com.citrixonline.GoToMeeting.G2MUpdate
com.apple.AirPortBaseStationAgent
com.microsoft.SyncServicesAgent
Startup items
/System/Library/StartupItems/ciscod/ciscod
/System/Library/StartupItems/ciscod/StartupParameters.plist
Bundles
/System/Library/Extensions/hp_fax_io.kext
- com.hp.kext.hp-fax-io
/System/Library/Extensions/hp_Inkjet1_io_enabler.kext
- com.hp.print.hpio.Inkjet1.kext
/System/Library/Extensions/hp_Inkjet4_io_enabler.kext
- com.hp.print.hpio.Inkjet4.kext
/System/Library/Extensions/hp_Inkjet8_io_enabler.kext
- com.hp.print.hpio.inkjet8.kext
/System/Library/Extensions/JMicronATA.kext
- com.jmicron.JMicronATA
/System/Library/Extensions/WD1394_64_109HPDriver.kext
- com.wdc.driver.1394.64.10.9
/System/Library/Extensions/WDUSB_64_109HPDriver.kext
- com.wdc.driver.USB.64.10.9
/Library/Extensions/hp_io_printerclassdriver_enabler.kext
- com.hp.hpio.hp-io-printerclassdriver-enabler
/Library/Internet Plug-Ins/AdobeAAMDetect.plugin
- com.AdobeAAMDetectLib.AdobeAAMDetect
/Library/Internet Plug-Ins/CitrixICAClientPlugIn.plugin
- com.citrix.citrixicaclientplugIn
/Library/Internet Plug-Ins/Flash Player.plugin
- N/A
/Library/Internet Plug-Ins/googletalkbrowserplugin.plugin
- com.google.googletalkbrowserplugin
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin
- com.oracle.java.JavaAppletPlugin
/Library/Internet Plug-Ins/npg.plugin
- npg.graphon.com
/Library/Internet Plug-Ins/o1dbrowserplugin.plugin
- com.google.o1dbrowserplugin
/Library/Internet Plug-Ins/SharePointBrowserPlugin.plugin
- com.microsoft.sharepoint.browserplugin
/Library/Internet Plug-Ins/SharePointWebKitPlugin.webplugin
- com.microsoft.sharepoint.webkitplugin
/Library/Internet Plug-Ins/Silverlight.plugin
- com.microsoft.SilverlightPlugin
/Library/Internet Plug-Ins/SlingPlayer.plugin
- com.slingmedia.slingplayer.plugin.nspapi
/Library/PreferencePanes/Flash Player.prefPane
- com.adobe.flashplayerpreferences
/Library/PreferencePanes/FMDSysPrefPane.prefPane
- Citrix.FMDSysPrefPane
/Library/PreferencePanes/JavaControlPanel.prefPane
- com.oracle.java.JavaControlPanel
/Library/PreferencePanes/WDQuickViewPrefsPane.prefPane
- com.westerndigital.quickview.prefpanel
/Library/PreferencePanes/Zimbra.prefPane
- com.zimbra.prefpanel
/Library/ScriptingAdditions/Adobe Unit Types.osax
- N/A
Library/Address Book Plug-Ins/SkypeABDialer.bundle
- com.skype.skypeabdialer
Library/Address Book Plug-Ins/SkypeABSMS.bundle
- com.skype.skypeabsms
Library/Internet Plug-Ins/CitrixOnlineWebDeploymentPlugin.plugin
- com.citrixonline.mac.WebDeploymentPlugin
Library/Internet Plug-Ins/Google Earth Web Plug-in.plugin
- com.Google.GoogleEarthPlugin.plugin
Library/Internet Plug-Ins/WebEx.plugin
- com.webex.WebEx
Library/Internet Plug-Ins/WebEx.plugin/Contents/Resources
- com.webex.WebEx
Library/Internet Plug-Ins/WebEx64.plugin
- com.cisco_webex.plugin.gpc64
dylibs
/usr/lib/libaudioc.dylib
/usr/lib/libclipc.dylib
/usr/lib/libcs.dylib
/usr/lib/libdc.dylib
/usr/lib/libfilec.dylib
/usr/lib/libMonoPosixHelper.dylib
/usr/lib/libpbr.dylib
/usr/lib/libprintc.dylib
/usr/lib/libsc.dylib
/usr/lib/libSFFileMonitor.32.dylib
/usr/lib/libSFIPC.32.dylib
/usr/lib/libSFIPC.I.dylib
/usr/lib/libSFsqlite3.7.4.dylib
/usr/lib/libSFSyncEngine.I.dylib
/usr/lib/libupc.dylib
App extensions
it.bloop.airmail.beta10.Airmail-Today-Beta
it.bloop.airmail.beta10.Airmail-Composer-Beta
com.wunderkinder.wunderlistdesktop.sharingextension
com.wunderkinder.wunderlistdesktop.todayextension
com.readitlater.PocketMac.AddToPocketShareExtension
com.stylemac.instadesk.Photodesk-Feed
it.bloop.airmail.beta10.Airmail-Share-Beta
Apps
/Applications/Uninstall IM Completer.app
Contents of /Library/LaunchAgents/com.cisco.anyconnect.gui.plist (checksum 1087717482)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key>
<dict>
<key>PathState</key>
<dict>
<key>/opt/cisco/anyconnect/gui_keepalive</key>
<true/>
</dict>
</dict>
<key>Label</key>
<string>com.cisco.anyconnect.gui</string>
<key>LimitLoadToSessionType</key>
<string>Aqua</string>
<key>ProgramArguments</key>
<array>
<string>open</string>
<string>--wait-apps</string>
<string>/Applications/Cisco/Cisco AnyConnect Secure Mobility Client.app</string>
</array>
</dict>
</plist>
Contents of /Library/LaunchAgents/com.citrix.AuthManager_Mac.plist (checksum 1591517921)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ServiceIPC</key>
<true/>
<key>MachServices</key>
<dict>
<key>com.citrix.AuthManager_Mac</key>
<true/>
</dict>
<key>Label</key>
<string>com.citrix.AuthManager_Mac</string>
<key>WaitForDebugger</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/usr/local/libexec/AuthManager_Mac.app/Contents/MacOS/AuthManager_Mac</ string>
</array>
<key>LimitLoadToSessionType</key>
<string>Aqua</string>
<key>Disabled</key>
<false/>
</dict>
</plist>
Contents of /Library/LaunchAgents/com.citrix.ReceiverHelper.plist (checksum 676087606)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.citrix.ReceiverHelper</string>
<key>RunAtLoad</key>
<true/>
<key>KeepAlive</key>
<dict>
<key>SuccessfulExit</key>
<false/>
</dict>
<key>WaitForDebugger</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/usr/local/libexec/ReceiverHelper.app/Contents/MacOS/ReceiverHelper</st ring>
</array>
<key>LimitLoadToSessionType</key>
<string>Aqua</string>
<key>Disabled</key>
<false/>
</dict>
</plist>
Contents of /Library/LaunchAgents/com.citrix.ServiceRecords.plist (checksum 1445213025)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ServiceIPC</key>
<true/>
<key>MachServices</key>
<dict>
<key>com.citrix.Beacons</key>
<true/>
<key>com.citrix.ServiceRecords</key>
<true/>
</dict>
<key>Label</key>
<string>com.citrix.ServiceRecords</string>
<key>RunAtLoad</key>
<true/>
<key>KeepAlive</key>
<true/>
<key>WaitForDebugger</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/usr/local/libexec/ServiceRecords.app/Contents/MacOS/ServiceRecords</st ring>
</array>
...and 8 more line(s)
Contents of /Library/LaunchAgents/com.oracle.java.Java-Updater.plist (checksum 3453356730)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.oracle.java.Java-Updater</string>
<key>ProgramArguments</key>
<array>
<string>/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Resources/Java Updater.app/Contents/MacOS/Java Updater</string>
<string>-bgcheck</string>
</array>
<key>StandardErrorPath</key>
<string>/dev/null</string>
<key>StandardOutPath</key>
<string>/dev/null</string>
<key>StartCalendarInterval</key>
<dict>
<key>Hour</key>
<integer>9</integer>
<key>Minute</key>
<integer>57</integer>
<key>Weekday</key>
<integer>3</integer>
</dict>
</dict>
...and 1 more line(s)
Contents of /Library/LaunchDaemons/com.cisco.anyconnect.vpnagentd.plist (checksum 2630047092)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC -//Apple Computer//DTD PLIST 1.0//EN
http://www.apple.com/DTDs/PropertyList-1.0.dtd >
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.cisco.anyconnect.vpnagentd</string>
<key>ProgramArguments</key>
<array>
<string>/opt/cisco/anyconnect/bin/vpnagentd</string>
<string>-execv_instance</string>
</array>
<key>KeepAlive</key>
<true/>
<key>RunAtLoad</key>
<true/>
<key>AbandonProcessGroup</key>
<true/>
<key>EnableTransactions</key>
<false/>
</dict>
</plist>
Contents of /Library/LaunchDaemons/com.wdc.SmartwareDriveService.plist (checksum 2733252498)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.wdc.SmartwareDriveService</string>
<key>Program</key>
<string>/Library/Application Support/WD SmartWare Services/SmartwareDriveService</string>
<key>RunAtLoad</key>
<true/>
<key>StandardErrorPath</key>
<string>/dev/null</string>
</dict>
</plist>
Contents of /Library/LaunchDaemons/com.wdc.WDSmartWareService.plist (checksum 1153517838)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.wdc.WDSmartWareService</string>
<!-- <key>Program</key>
<string>/Library/Application Support/WD SmartWare Services/SmartwareServerApp.app/Contents/MacOS/SmartwareServiceApp</string> -->
<key>ProgramArguments</key>
<array>
<string>/Library/Application Support/WD SmartWare Services/SmartwareServiceApp.app/Contents/MacOS/SmartwareServiceApp</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StandardErrorPath</key>
<string>/dev/null</string>
</dict>
</plist>
Contents of Library/LaunchAgents/com.genieo.completer.download.plist (checksum 1894818845)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.genieo.completer.download</string>
<key>ProgramArguments</key>
<array>
<string>/Users/USER/Library/Application Support/com.genieoinnovation.Installer/Completer.app/Contents/MacOS/Installer</ string>
<string>-trigger</string>
<string>download</string>
<string>-isDev</string>
<string>0</string>
<string>-installVersion</string>
<string>15886</string>
<string>-firstAppId</string>
<string>19340001</string>
</array>
<key>WatchPaths</key>
<array>
<string>/Users/USER/Downloads</string>
</array>
</dict>
</plist>
Contents of Library/LaunchAgents/com.genieo.completer.update.plist (checksum 2339121592)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.genieo.completer.update</string>
<key>ProgramArguments</key>
<array>
<string>/Users/USER/Library/Application Support/com.genieoinnovation.Installer/Completer.app/Contents/MacOS/Installer</ string>
<string>-trigger</string>
<string>update</string>
<string>-isDev</string>
<string>0</string>
<string>-installVersion</string>
<string>15886</string>
<string>-firstAppId</string>
<string>19340001</string>
</array>
<key>StartInterval</key>
<integer>86400</integer>
</dict>
</plist>
Contents of Library/LaunchAgents/com.microsoft.LaunchAgent.SyncServicesAgent.plist (checksum 3051698494)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>KeepAlive</key>
<false/>
<key>Label</key>
<string>com.microsoft.SyncServicesAgent</string>
<key>OnDemand</key>
<false/>
<key>ProgramArguments</key>
<array>
<string>/Applications/Microsoft Office 2011/Office/SyncServicesAgent.app/Contents/MacOS/SyncServicesAgent</string>
</array>
</dict>
</plist>
Contents of Library/LaunchAgents/com.zimbra.desktop.plist (checksum 3676173668)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.zimbra.desktop</string>
<key>ProgramArguments</key>
<array>
<string>/Users/USER/Library/Zimbra Desktop/bin/zdesktop</string>
<string>start</string>
<string>-w</string>
</array>
-
hi guys,
i have a problem with my usb devices.
the dmesg:
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
Command line: root=/dev/sda5 vga=0x0361 ro
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ce000 - 00000000000d0000 (reserved)
BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fed0000 (usable)
BIOS-e820: 000000007fed0000 - 000000007fee3000 (ACPI NVS)
BIOS-e820: 000000007fee3000 - 0000000080000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
DMI present.
Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
last_pfn = 0x7fed0 max_arch_pfn = 0x100000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask F80000000 write-back
1 base 07FF00000 mask FFFF00000 uncachable
2 disabled
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009f800 (usable)
modified: 000000000009f800 - 00000000000a0000 (reserved)
modified: 00000000000ce000 - 00000000000d0000 (reserved)
modified: 00000000000dc000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000007fed0000 (usable)
modified: 000000007fed0000 - 000000007fee3000 (ACPI NVS)
modified: 000000007fee3000 - 0000000080000000 (reserved)
modified: 00000000e0000000 - 00000000f0000000 (reserved)
modified: 00000000fec00000 - 00000000fec10000 (reserved)
modified: 00000000fed00000 - 00000000fed00400 (reserved)
modified: 00000000fed14000 - 00000000fed1a000 (reserved)
modified: 00000000fed1c000 - 00000000fed90000 (reserved)
modified: 00000000fee00000 - 00000000fee01000 (reserved)
modified: 00000000ff000000 - 0000000100000000 (reserved)
init_memory_mapping: 0000000000000000-000000007fed0000
0000000000 - 007fe00000 page 2M
007fe00000 - 007fed0000 page 4k
kernel direct mapping tables up to 7fed0000 @ 10000-14000
RAMDISK: 37d42000 - 37fefc39
ACPI: RSDP 00000000000f7fe0 00024 (v02 PTLTD )
ACPI: XSDT 000000007fedab41 0008C (v01 Sony VAIO 20070418 PTL 00000000)
ACPI: FACP 000000007fee1bd2 000F4 (v03 Sony VAIO 20070418 PTL 00000001)
ACPI: DSDT 000000007fedbeeb 05C73 (v02 Sony VAIO 20070418 PTL 20050624)
ACPI: FACS 000000007fee2fc0 00040
ACPI: APIC 000000007fee1cc6 00068 (v01 Sony VAIO 20070418 PTL 0000005A)
ACPI: HPET 000000007fee1d2e 00038 (v01 Sony VAIO 20070418 PTL 0000005A)
ACPI: MCFG 000000007fee1d66 0003C (v01 Sony VAIO 20070418 PTL 0000005A)
ACPI: TCPA 000000007fee1da2 00032 (v01 Sony VAIO 20070418 PTL 00005A52)
ACPI: SLIC 000000007fee1dd4 00176 (v01 Sony VAIO 20070418 PTL 01000000)
ACPI: TMOR 000000007fee1f4a 00026 (v01 Sony VAIO 20070418 PTL 00000003)
ACPI: APIC 000000007fee1f70 00068 (v01 Sony VAIO 20070418 PTL 00000000)
ACPI: BOOT 000000007fee1fd8 00028 (v01 Sony VAIO 20070418 PTL 00000001)
ACPI: SSDT 000000007fedbc29 002C2 (v01 Sony VAIO 20070418 PTL 20050624)
ACPI: SSDT 000000007fedb159 0025F (v01 Sony VAIO 20070418 PTL 20050624)
ACPI: SSDT 000000007fedb0b3 000A6 (v01 Sony VAIO 20070418 PTL 20050624)
ACPI: SSDT 000000007fedabcd 004E6 (v01 Sony VAIO 20070418 PTL 20050624)
ACPI: BIOS bug: multiple APIC/MADT found, using 0
ACPI: If "acpi_apic_instance=2" works better, notify [email protected]
ACPI: Local APIC address 0xfee00000
(7 early reservations) ==> bootmem [0000000000 - 007fed0000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
#2 [0000200000 - 000082d0d0] TEXT DATA BSS ==> [0000200000 - 000082d0d0]
#3 [0037d42000 - 0037fefc39] RAMDISK ==> [0037d42000 - 0037fefc39]
#4 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000]
#5 [000082e000 - 000082e204] BRK ==> [000082e000 - 000082e204]
#6 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000]
found SMP MP-table at [ffff8800000f8010] f8010
[ffffe20000000000-ffffe20001bfffff] PMD -> [ffff880001200000-ffff880002dfffff] on node 0
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0007fed0
On node 0 totalpages: 523871
DMA zone: 56 pages used for memmap
DMA zone: 1682 pages reserved
DMA zone: 2245 pages, LIFO batch:0
DMA32 zone: 7108 pages used for memmap
DMA32 zone: 512780 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 0, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
SMP: Allowing 2 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000ce000
PM: Registered nosave memory: 00000000000ce000 - 00000000000d0000
PM: Registered nosave memory: 00000000000d0000 - 00000000000dc000
PM: Registered nosave memory: 00000000000dc000 - 0000000000100000
Allocating PCI resources starting at 88000000 (gap: 80000000:60000000)
NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Embedded 25 pages at ffff880001010000, static data 72352 bytes
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 515025
Kernel command line: root=/dev/sda5 vga=0x0361 ro
Initializing CPU#0
NR_IRQS:768
PID hash table entries: 4096 (order: 12, 32768 bytes)
Extended CMOS year: 2000
Fast TSC calibration using PIT
Detected 1994.610 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Checking aperture...
No AGP bridge found
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Memory: 2053736k/2095936k available (3409k kernel code, 452k absent, 41160k reserved, 1239k data, 464k init)
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
hpet clockevent registered
HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Calibrating delay loop (skipped), value calculated using timer frequency.. 3990.43 BogoMIPS (lpj=6648700)
Security Framework initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
ACPI: Core revision 20090320
Setting APIC routing to flat
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0a
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3991.23 BogoMIPS (lpj=6649976)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU1: Thermal monitoring enabled (TM2)
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0a
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
Total of 2 processors activated (7982.67 BogoMIPS).
CPU0 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 0 1
CPU1 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 1 0
net_namespace: 1888 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: BIOS _OSI(Linux) query ignored
ACPI: EC: non-query interrupt received, switching to interrupt mode
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE storm detected, transactions will use polling mode
ACPI: EC: missing confirmations, switch off interrupt mode.
[Firmware Bug]: ACPI: ACPI brightness control misses _BQC function
ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
ACPI: EC: driver started in poll mode
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:1a.0: reg 20 io port: [0x1800-0x181f]
pci 0000:00:1a.1: reg 20 io port: [0x1820-0x183f]
pci 0000:00:1a.7: reg 10 32bit mmio: [0xfc404800-0xfc404bff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10 64bit mmio: [0xfc400000-0xfc403fff]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.4: PME# disabled
pci 0000:00:1d.0: reg 20 io port: [0x1840-0x185f]
pci 0000:00:1d.1: reg 20 io port: [0x1860-0x187f]
pci 0000:00:1d.2: reg 20 io port: [0x1880-0x189f]
pci 0000:00:1d.7: reg 10 32bit mmio: [0xfc404c00-0xfc404fff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 1180-11bf claimed by ICH6 GPIO
pci 0000:00:1f.1: reg 10 io port: [0x00-0x07]
pci 0000:00:1f.1: reg 14 io port: [0x00-0x03]
pci 0000:00:1f.1: reg 18 io port: [0x00-0x07]
pci 0000:00:1f.1: reg 1c io port: [0x00-0x03]
pci 0000:00:1f.1: reg 20 io port: [0x18a0-0x18af]
pci 0000:00:1f.2: reg 10 io port: [0x18d8-0x18df]
pci 0000:00:1f.2: reg 14 io port: [0x18cc-0x18cf]
pci 0000:00:1f.2: reg 18 io port: [0x18d0-0x18d7]
pci 0000:00:1f.2: reg 1c io port: [0x18c8-0x18cb]
pci 0000:00:1f.2: reg 20 io port: [0x18e0-0x18ff]
pci 0000:00:1f.2: reg 24 32bit mmio: [0xfc404000-0xfc4047ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 10 32bit mmio: [0x000000-0x0000ff]
pci 0000:00:1f.3: reg 20 io port: [0x1c00-0x1c1f]
pci 0000:01:00.0: reg 10 32bit mmio: [0xce000000-0xceffffff]
pci 0000:01:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff]
pci 0000:01:00.0: reg 1c 64bit mmio: [0xcc000000-0xcdffffff]
pci 0000:01:00.0: reg 24 io port: [0x2000-0x207f]
pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
pci 0000:00:01.0: bridge io port: [0x2000-0x2fff]
pci 0000:00:01.0: bridge 32bit mmio: [0xcc000000-0xceffffff]
pci 0000:00:01.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
pci 0000:00:1c.0: bridge io port: [0x3000-0x3fff]
pci 0000:00:1c.0: bridge 32bit mmio: [0xf6000000-0xf7ffffff]
pci 0000:00:1c.0: bridge 64bit mmio pref: [0xf0000000-0xf1ffffff]
pci 0000:00:1c.1: bridge io port: [0x4000-0x4fff]
pci 0000:00:1c.1: bridge 32bit mmio: [0xf8000000-0xf9ffffff]
pci 0000:00:1c.1: bridge 64bit mmio pref: [0xf2000000-0xf3ffffff]
pci 0000:06:00.0: reg 10 32bit mmio: [0xfa000000-0xfa000fff]
pci 0000:06:00.0: PME# supported from D0 D3hot D3cold
pci 0000:06:00.0: PME# disabled
pci 0000:00:1c.2: bridge io port: [0x5000-0x5fff]
pci 0000:00:1c.2: bridge 32bit mmio: [0xfa000000-0xfbffffff]
pci 0000:00:1c.2: bridge 64bit mmio pref: [0xf4000000-0xf5ffffff]
pci 0000:08:00.0: reg 10 64bit mmio: [0xfc000000-0xfc003fff]
pci 0000:08:00.0: reg 18 io port: [0x6000-0x60ff]
pci 0000:08:00.0: supports D1 D2
pci 0000:08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:08:00.0: PME# disabled
pci 0000:00:1c.4: bridge io port: [0x6000-0x6fff]
pci 0000:00:1c.4: bridge 32bit mmio: [0xfc000000-0xfc0fffff]
pci 0000:09:03.0: reg 10 32bit mmio: [0xfc100000-0xfc100fff]
pci 0000:09:03.0: supports D1 D2
pci 0000:09:03.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:09:03.0: PME# disabled
pci 0000:09:03.1: reg 10 32bit mmio: [0xfc102000-0xfc1027ff]
pci 0000:09:03.1: reg 14 32bit mmio: [0xfc104000-0xfc107fff]
pci 0000:09:03.1: supports D1 D2
pci 0000:09:03.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:09:03.1: PME# disabled
pci 0000:09:03.2: reg 10 32bit mmio: [0xfc101000-0xfc101fff]
pci 0000:09:03.2: supports D1 D2
pci 0000:09:03.2: PME# supported from D0 D1 D2 D3hot
pci 0000:09:03.2: PME# disabled
pci 0000:00:1e.0: transparent bridge
pci 0000:00:1e.0: bridge 32bit mmio: [0xfc100000-0xfc1fffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 *5 6 7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 *7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
PCI: Using ACPI for IRQ routing
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 10 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved
system 00:01: iomem range 0xfed14000-0xfed17fff has been reserved
system 00:01: iomem range 0xfed18000-0xfed18fff has been reserved
system 00:01: iomem range 0xfed19000-0xfed19fff has been reserved
system 00:01: iomem range 0xe0000000-0xefffffff has been reserved
system 00:01: iomem range 0xfed20000-0xfed3ffff has been reserved
system 00:01: iomem range 0xfed40000-0xfed44fff has been reserved
system 00:01: iomem range 0xfed45000-0xfed8ffff has been reserved
system 00:04: iomem range 0xfed00000-0xfed003ff has been reserved
system 00:06: ioport range 0x680-0x69f has been reserved
system 00:06: ioport range 0x800-0x80f has been reserved
system 00:06: ioport range 0x1000-0x107f has been reserved
system 00:06: ioport range 0x1180-0x11bf has been reserved
system 00:06: ioport range 0x1640-0x164f has been reserved
system 00:06: ioport range 0xfe00-0xfe7f has been reserved
system 00:06: ioport range 0xfe80-0xfeff has been reserved
pci 0000:01:00.0: BAR 6: can't allocate mem resource [0xe0000000-0xdfffffff]
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0: IO window: 0x2000-0x2fff
pci 0000:00:01.0: MEM window: 0xcc000000-0xceffffff
pci 0000:00:01.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
pci 0000:00:1c.0: IO window: 0x3000-0x3fff
pci 0000:00:1c.0: MEM window: 0xf6000000-0xf7ffffff
pci 0000:00:1c.0: PREFETCH window: 0x000000f0000000-0x000000f1ffffff
pci 0000:00:1c.1: PCI bridge, secondary bus 0000:04
pci 0000:00:1c.1: IO window: 0x4000-0x4fff
pci 0000:00:1c.1: MEM window: 0xf8000000-0xf9ffffff
pci 0000:00:1c.1: PREFETCH window: 0x000000f2000000-0x000000f3ffffff
pci 0000:00:1c.2: PCI bridge, secondary bus 0000:06
pci 0000:00:1c.2: IO window: 0x5000-0x5fff
pci 0000:00:1c.2: MEM window: 0xfa000000-0xfbffffff
pci 0000:00:1c.2: PREFETCH window: 0x000000f4000000-0x000000f5ffffff
pci 0000:00:1c.4: PCI bridge, secondary bus 0000:08
pci 0000:00:1c.4: IO window: 0x6000-0x6fff
pci 0000:00:1c.4: MEM window: 0xfc000000-0xfc0fffff
pci 0000:00:1c.4: PREFETCH window: disabled
pci 0000:09:03.0: CardBus bridge, secondary bus 0000:0a
pci 0000:09:03.0: IO window: 0x007000-0x0070ff
pci 0000:09:03.0: IO window: 0x007400-0x0074ff
pci 0000:09:03.0: PREFETCH window: 0x88000000-0x8bffffff
pci 0000:09:03.0: MEM window: 0x90000000-0x93ffffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:09
pci 0000:00:1e.0: IO window: 0x7000-0x7fff
pci 0000:00:1e.0: MEM window: 0xfc100000-0xfc1fffff
pci 0000:00:1e.0: PREFETCH window: 0x00000088000000-0x0000008bffffff
pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:01.0: setting latency timer to 64
pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.4: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci 0000:09:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci_bus 0000:00: resource 0 io: [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff]
pci_bus 0000:01: resource 0 io: [0x2000-0x2fff]
pci_bus 0000:01: resource 1 mem: [0xcc000000-0xceffffff]
pci_bus 0000:01: resource 2 pref mem [0xd0000000-0xdfffffff]
pci_bus 0000:02: resource 0 io: [0x3000-0x3fff]
pci_bus 0000:02: resource 1 mem: [0xf6000000-0xf7ffffff]
pci_bus 0000:02: resource 2 pref mem [0xf0000000-0xf1ffffff]
pci_bus 0000:04: resource 0 io: [0x4000-0x4fff]
pci_bus 0000:04: resource 1 mem: [0xf8000000-0xf9ffffff]
pci_bus 0000:04: resource 2 pref mem [0xf2000000-0xf3ffffff]
pci_bus 0000:06: resource 0 io: [0x5000-0x5fff]
pci_bus 0000:06: resource 1 mem: [0xfa000000-0xfbffffff]
pci_bus 0000:06: resource 2 pref mem [0xf4000000-0xf5ffffff]
pci_bus 0000:08: resource 0 io: [0x6000-0x6fff]
pci_bus 0000:08: resource 1 mem: [0xfc000000-0xfc0fffff]
pci_bus 0000:09: resource 0 io: [0x7000-0x7fff]
pci_bus 0000:09: resource 1 mem: [0xfc100000-0xfc1fffff]
pci_bus 0000:09: resource 2 pref mem [0x88000000-0x8bffffff]
pci_bus 0000:09: resource 3 io: [0x00-0xffff]
pci_bus 0000:09: resource 4 mem: [0x000000-0xffffffffffffffff]
pci_bus 0000:0a: resource 0 io: [0x7000-0x70ff]
pci_bus 0000:0a: resource 1 io: [0x7400-0x74ff]
pci_bus 0000:0a: resource 2 pref mem [0x88000000-0x8bffffff]
pci_bus 0000:0a: resource 3 mem: [0x90000000-0x93ffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 2743k freed
Simple Boot Flag at 0x36 set to 0x1
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1249997463.944:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 4017
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:01:00.0: Boot video device
pcieport-driver 0000:00:01.0: irq 24 for MSI/MSI-X
pcieport-driver 0000:00:01.0: setting latency timer to 64
pcieport-driver 0000:00:1c.0: irq 25 for MSI/MSI-X
pcieport-driver 0000:00:1c.0: setting latency timer to 64
pcieport-driver 0000:00:1c.1: irq 26 for MSI/MSI-X
pcieport-driver 0000:00:1c.1: setting latency timer to 64
pcieport-driver 0000:00:1c.2: irq 27 for MSI/MSI-X
pcieport-driver 0000:00:1c.2: setting latency timer to 64
pcieport-driver 0000:00:1c.4: irq 28 for MSI/MSI-X
pcieport-driver 0000:00:1c.4: setting latency timer to 64
vesafb: framebuffer at 0xcd000000, mapped to 0xffffc20010100000, using 8000k, total 14336k
vesafb: mode is 1280x800x32, linelength=5120, pages=1
vesafb: scrolling: redraw
vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Console: switching to colour frame buffer device 160x50
fb0: VESA VGA frame buffer device
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 464k freed
SCSI subsystem initialized
libata version 3.00 loaded.
pata_acpi 0000:00:1f.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
pata_acpi 0000:00:1f.1: setting latency timer to 64
pata_acpi 0000:00:1f.1: PCI INT A disabled
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: irq 29 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 3 ports 3 Gbps 0x7 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
ata1: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404100 irq 29
ata2: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404180 irq 29
ata3: SATA max UDMA/133 abar m2048@0xfc404000 port 0xfc404200 irq 29
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata1.00: ACPI cmd ef/90:03:00:00:00:a0 succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
ata1.00: ATA-7: FUJITSU MHV2200BT, 0000004F, max UDMA/100
ata1.00: 390721968 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: ACPI cmd ef/90:03:00:00:00:a0 succeeded
ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access ATA FUJITSU MHV2200B 0000 PQ: 0 ANSI: 5
ata_piix 0000:00:1f.1: version 2.13
ata_piix 0000:00:1f.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.1: setting latency timer to 64
scsi3 : ata_piix
scsi4 : ata_piix
ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x18a0 irq 14
ata5: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18a8 irq 15
ata4.00: ATAPI: MATSHITABD-MLT UJ-220V, 1.00, max UDMA/33
ata4.00: configured for UDMA/33
scsi 3:0:0:0: CD-ROM MATSHITA BD-MLT UJ-220V 1.00 PQ: 0 ANSI: 5
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors: (200 GB/186 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
sd 0:0:0:0: [sda] Attached SCSI disk
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: [email protected]
Intel AES-NI instructions are not detected.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with writeback data mode.
rtc_cmos 00:07: RTC can wake from S4
rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
udev: starting version 141
sky2 driver version 1.22
sky2 0000:08:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
sky2 0000:08:00.0: setting latency timer to 64
sky2 0000:08:00.0: Yukon-2 FE chip revision 1
sky2 0000:08:00.0: irq 30 for MSI/MSI-X
sky2 eth0: addr 00:13:a9:c1:09:33
cfg80211: Calling CRDA to update world regulatory domain
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 3:0:0:0: Attached scsi generic sg1 type 5
ACPI: AC Adapter [ADP1] (on-line)
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
ACPI: Lid Switch [LID0]
input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
ACPI: Power Button [PWRB]
ACPI: SSDT 000000007fedb8e7 0027A (v01 Sony VAIO 20070418 PTL 20050624)
ACPI: SSDT 000000007fedb3b8 004AA (v01 Sony VAIO 20070418 PTL 20050624)
ACPI Warning (processor_throttling-0843): Invalid throttling state, reset [20090320]
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Monitor-Mwait will be used to enter C-3 state
Marking TSC unstable due to TSC halts in idle
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
processor ACPI_CPU:00: registered as cooling_device0
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: SSDT 000000007fedbb61 000C8 (v01 Sony VAIO 20070418 PTL 20050624)
ACPI: SSDT 000000007fedb862 00085 (v01 Sony VAIO 20070418 PTL 20050624)
ACPI Warning (processor_throttling-0843): Invalid throttling state, reset [20090320]
ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
processor ACPI_CPU:01: registered as cooling_device1
ACPI: Processor [CPU1] (supports 8 throttling states)
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [TZ00] (58 C)
input: PC Speaker as /devices/platform/pcspkr/input/input4
sony-laptop: Sony Notebook Control Driver v0.6.
input: Sony Vaio Keys as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:29/SNY5001:00/input/input5
input: Sony Vaio Jogdial as /devices/virtual/input/input6
ACPI: Invalid active0 threshold
iTCO_vendor_support: vendor-support=0
thermal LNXTHERM:02: registered as thermal_zone1
ACPI: Thermal Zone [TZ01] (58 C)
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ACPI: Battery Slot [BAT0] (battery present)
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 19 (level, low) -> IRQ 19
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfc404800
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfc404c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 21, io base 0x00001820
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001840
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001860
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001880
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
input: PS/2 Mouse as /devices/platform/i8042/serio4/input/input7
input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio4/input/input8
usb 1-2: new high speed USB device using ehci_hcd and address 2
usb 1-2: configuration #1 chosen from 1 choice
usb 2-3: new high speed USB device using ehci_hcd and address 3
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
yenta_cardbus 0000:09:03.0: CardBus bridge found [104d:9005]
yenta_cardbus 0000:09:03.0: Using CSCINT to route CSC interrupts to PCI
yenta_cardbus 0000:09:03.0: Routing CardBus interrupts to PCI
yenta_cardbus 0000:09:03.0: TI: mfunc 0x01121b22, devctl 0x64
usb 2-3: configuration #1 chosen from 1 choice
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 185.18.31 Tue Jul 28 17:52:27 PDT 2009
yenta_cardbus 0000:09:03.0: ISA IRQ mask 0x0cf8, PCI irq 16
yenta_cardbus 0000:09:03.0: Socket status: 30000006
pci_bus 0000:09: Raising subordinate bus# of parent bus (#09) from #0a to #0d
yenta_cardbus 0000:09:03.0: pcmcia: parent PCI bridge I/O window: 0x7000 - 0x7fff
yenta_cardbus 0000:09:03.0: pcmcia: parent PCI bridge Memory window: 0xfc100000 - 0xfc1fffff
yenta_cardbus 0000:09:03.0: pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x8bffffff
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2009 Intel Corporation
iwl3945 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
iwl3945 0000:06:00.0: setting latency timer to 64
ohci1394 0000:09:03.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 3:0:0:0: Attached scsi CD-ROM sr0
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[17] MMIO=[fc102000-fc1027ff] Max Packet=[2048] IR/IT contexts=[4/8]
tifm_7xx1 0000:09:03.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
hub 2-0:1.0: unable to enumerate USB device on port 5
iwl3945 0000:06:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945 0000:06:00.0: Detected Intel Wireless WiFi Link 3945ABG
iwl3945 0000:06:00.0: irq 31 for MSI/MSI-X
Initializing USB Mass Storage driver...
scsi5 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
input: HDA Intel Mic at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/input/input9
input: HDA Intel HP Out at Ext Left Jack as /devices/pci0000:00/0000:00:1b.0/input/input10
usb 5-1: new low speed USB device using uhci_hcd and address 2
usbcore: registered new interface driver hiddev
Linux video capture interface: v2.00
input: Western Digital My Book as /devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3:1.1/input/input11
generic-usb 0003:1058:1102.0001: input,hidraw0: USB HID v1.11 Device [Western Digital My Book] on usb-0000:00:1d.7-3/input1
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
uvcvideo: Found UVC 1.00 device <unnamed> (05ca:1837)
uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
uvcvideo: Failed to query (129) UVC probe control : -32 (exp. 26).
uvcvideo: Failed to initialize the device (-5).
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
phy0: Selected rate control algorithm 'iwl-3945-rs'
usb 5-1: configuration #1 chosen from 1 choice
input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input12
generic-usb 0003:046D:C518.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1/input0
input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input13
generic-usb 0003:046D:C518.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1/input1
fuse init (API version 7.11)
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 2 processor cores.
VBoxDrv: dbg - g_abExecMemory=ffffffffa0f05760
vboxdrv: fAsync=0 offMin=0x1ae offMax=0x125c
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 3.0.4 (interface 0x000e0000).
VBoxNetFlt: dbg - g_abExecMemory=ffffffffa10a9f00
hub 2-0:1.0: unable to enumerate USB device on port 5
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0800460302564f69]
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
Clocksource tsc unstable (delta = -435934901 ns)
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
EXT3 FS on dm-0, internal journal
scsi 5:0:0:0: Direct-Access WD My Book 1028 PQ: 0 ANSI: 4
sd 5:0:0:0: Attached scsi generic sg2 type 0
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
sd 5:0:0:0: [sdb] 625142448 512-byte hardware sectors: (320 GB/298 GiB)
sd 5:0:0:0: [sdb] Write Protect is off
sd 5:0:0:0: [sdb] Mode Sense: 10 00 00 00
sd 5:0:0:0: [sdb] Assuming drive cache: write through
usb-storage: device scan complete
sd 5:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 5:0:0:0: [sdb] Attached SCSI disk
EXT4-fs: barriers enabled
kjournald2 starting: pid 1929, dev dm-1:8, commit interval 5 seconds
EXT4 FS on dm-1, internal journal on dm-1:8
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
EXT4-fs: mounted filesystem dm-1 with ordered data mode
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
Adding 2449872k swap on /dev/sda6. Priority:-1 extents:1 across:2449872k
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
iwl3945 0000:06:00.0: firmware: requesting iwlwifi-3945-2.ucode
hub 2-0:1.0: unable to enumerate USB device on port 5
iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
wlan0: authenticate with AP 00:11:6b:10:2f:bc
wlan0: authenticated
wlan0: associate with AP 00:11:6b:10:2f:bc
wlan0: RX AssocResp from 00:11:6b:10:2f:bc (capab=0x471 status=0 aid=1)
wlan0: associated
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
hub 2-0:1.0: unable to enumerate USB device on port 5
i think the result is, that my bluetooth and webcam isn't working...
can you help me pls.
regards nigg
Last edited by nigg (2009-08-11 14:14:57)I'm also having this problem. It's happening with my USB flash disk. I was almost buying another one when I tried it with Windows Vista on the same machine and it worked ok, then I tried Arch Linux (with kernel 2.6.30.5) on another machine and got the same error. After that I tried Ubuntu and it worked ok. Seems that Arch's kernel doesn't like my USB flash disk.
Last edited by esdrasbeleza (2009-09-02 01:16:09) -
Disk Utility 13 problem with USB drives
There appears to be a problem with Disk Utility 13 (part of OS X 10.9). At least, so far as I can tell, everything traces back to this app, or possibly OS X 10.9 itself.
I recently upgraded my MacBook Air to OS X 10.9 (reformatted hard drive, installed system from scratch, updated with all the latest Apple updates). I pre-checked all my third party software to make sure it was 10.9 compatible before installing it after the system cleanup, so everything I’m running supposedly has been approved as safe for 10.9. But I’m seeing a problem formatting USB drives that I do not encounter when running under 10.8.
I have a Seagate STAA500101 (“FreeAgent GoFlex”) drive connected via Seagate’s USB3 adapter that I’ve used for some time as a Time Machine backup. Post-overhaul, I decided to erase the backup and start fresh. When I attempt to format it (single GUID partition) with Disk Utility, I see the following messages go by:
Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled 1
Could not mount disk1s2 with name (null) after erase
Then there’s a pause, and the format appears to conclude fine. But if I run a “Verify Disk” immediately, I get this:
Verifying partition map for “Seagate FreeAgent GoFlex Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Volume on disk1s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
Problems were found with the partition map which might prevent booting
Error: Partition map needs repair because a data partition needs loader space.
As the drive has just been formatted, that seemed odd. I took it over to another Mac still running 10.8.5 and formatted it there — it worked just fine. Verified just fine. Took the drive back to my MacBook Air and tried to verify the disk — same failure.
I wanted to rule out bad media, so I took a Lexar 16GB USB flash drive and tried to format it with Disk Utility 13 — got the same problem.
The only success I’ve had formatting USB drives under 10.9 is to boot up into OS X Recovery. Disk Utility there formatted my Seagate drive without an error. But once I booted back into normal 10.9 operating mode, the drive once again fails to verify; it makes me leery about using it as a Time Machine backup.
I suppose it’s possible there could be some background component like Sophos causing problems when formatting drives, but if I format a drive via OS X Recovery or another Mac under 10.8, that wouldn’t explain why the drives fail to verify.
Anyone got any other observations on this issue?Problem resolved. I'm posting this note for anyone else who might run into this situation and come across this discussion.
It actually did turn out to be Sophos -- Cloud, that is. I'd been using Sophos' free Mac antivirus software on a variety of systems but forgot that I was now testing out Sophos Cloud on my own MacBook, which is their new endpoint solution, and supposed to be compatible with OS X 10.9 (although the Mac version is listed as "beta") Sophos Cloud includes a new feature called Device Control which allows you to create a company-wide policy to control access to hardware such as USB drives, optical drives, etc. But apparently it's still pretty buggy. I had my Device Control configured with the default setting of "monitor but do not block" but it was most definitely gumming up the system. With Sophos Cloud installed, here's what happens if I try to run "Verify Disk" on any attached drive. Note on the left side how "disk2s2" shows as a sub-volume for each hard drive.
So if I uninstall Sophos Cloud, reboot and rescan, here's what I get:
Works fine. Note that the "disk2s2" subvolumes are also gone. This is the way Disk Utility also appears on a 10.8 or 10.9 system, even if you have the standard free Sophos for Mac software installed. It's only Sophos Cloud that's not playing nice. It also appears to have stopped me from being able to play DVDs from an attached Apple USB SuperDrive -- that problem was likewise solved by removing Sophos Cloud. -
Using an external drive for OS, problems with install
Hi
My iMac, 1.8 GHz, OS 10.5.8, PPC's internal hard drive is failing. Rather than replace the internal drive, I had hoped to use an external USB drive to run the OS.
When using the OS 10.5.x install, I am repeatedly told the OS cannot be installed onto my external drive.
I cannot narrow down the isse.
Is it because it is a USB drive?
Is it the format of the drive? It is currently formatted as "Mac OS X Extended Journaled."
Is it indicative of some other problem with the computer?You need an external Firewire drive to boot a PowerPC Mac computer.
I recommend you do a google search on any external harddrive you are looking at.
I bought a low cost external drive enclosure. When I started having trouble with it, I did a google search and found a lot of complaints about the drive enclosure. I ended up buying a new drive enclosure. On my second go around, I decided to buy a drive enclosure with a good history of working with Macs. The chip set seems to be the key ingredient. The Oxford line of chips seems to be good. I got the Oxford 911.
Has everything interface:
FireWire 800/400 + USB2, + eSATA 'Quad Interface'
save a little money interface:
FireWire 400 + USB 2.0
This web page lists both external harddrive types. You may need to scroll to the right to see both.
http://eshop.macsales.com/shop/firewire/1394/USB/EliteAL/eSATA_FW800_FW400_USB
The latest the hard drive enclosures support the newer serial ata drives. The drive and closure that I list supports only older parallel ata.
Here is an external hd enclosure.
http://eshop.macsales.com/item/Other%20World%20Computing/MEFW91UAL1K/
Here is what one contributor recommended:
http://discussions.apple.com/message.jspa?messageID=10452917#10452917
Folks in these Mac forums recommend LaCie, OWC or G-Tech.
Here is a list of recommended drives:
http://discussions.apple.com/thread.jspa?messageID=5564509#5564509 -
Mac Pro (First Generation) problem with 1TB Seagate Barracuda
Hi Macianer,
I have a first generation Mac Pro which was sold with max. 750GB Hard drives for each bay. At this time I am grabbing for straws and maybe someone has any info on this problem.
I purchased 4 x 1TB Seagate Barracuda hard drives ( Model: ST31000340AS / Firmware: SD15 ), did a regular format after I purchased them ( GUID Partition Table, Journaled HFS+ File System). I am using 2 of them internally (they get quite hot and i didn't want to put all 4 of them in there) and two of them externally (backup purposes). The other two internal bays are covered by 2x 500GB Barracuda drives.
I put all four 1 TB hard drived through a 1 week stress test to make sure I am not dealing with bad apples. So far this practice served me well.
Now 2 weeks later one completely crashed (internal boot drive). It sounded to spin up alright but was not accessible at all. I went to BestBuy and GeekSquad said this drive is crashed and I returned it.
Since I had a backup I didn't worry too much. I put the back up hard drive in as the new boot drive (since it was a SuperDuper duplicat) it worked like a charm. Now the second hard drive starts temporarily freezing the system for 2-4 minutes and seems to get stuck showing the great colored ball of doom. After the freeze it continues to operate normal again and I am able to continue my work.
I ran the Disk Utility and I got the following message:
INVALID KEY LENGTH
VOLUME CHECK FAILED.
ERROR: FILESYSTEM VERIFY OR REPAIR FAILED.
It just seems weird, I never had problems with hard drives and now I get these problems with 3-4 week old hard drives.
I was in a chat with seagate support. First question to trouble shoot: Do you have access to a PC. My answer was no since Microsoft Vista I donated all of them to the Salvation Army. He asked if I formatted the hard drives low level and MBR with HFS+. I said since I do not have access to PC nor do I plan on using my hard drives for PC I formatted it regular with GUID and HFS+. I asked if there is any history of these drives that would help explain my experience. I was hoping for a recall or something of that sort or something that a firmware upgrade would remedy.
I guess my question is, is the first generation Mac Pro, even though it seems to format and run them fine, not able to handle 1TB hard drives on a daily basis. Or am I dealing with hard drive problems? The Seagate guy didn't seem to be of any help.
Any help is appreciated or even pointers that would help me in finding the problem.
Cheers,
PixelGrinch
Message was edited by: PixelGrinchExcellent questions, I too am looking at SSD.
Some things I know about SSD:
1. Intel recently released new firmware for their SSD drives to improve long term performance including Trim/Garbage collection.
2. SSD drives can be setup as SLC or MLC - SLC is faster read 2X, write 4X over MLC, however SLC is smaller capacity. SLC also has a longer life span.
3. Intel plans to have an 320GB X25-M (MLC) and a 128GB X25-E (SLC) out soon.
OSX does not fully support Trim and I'm not aware of any 3rd party software for OSX that helps in the garbage collection area. Diskeeper 2010 for Windows 7 provides full support for all variants of SSD, but nothing on the Mac side.
I'm probably going to wait for 2010 to see what comes out, SSD appears to be good news, but it still also seems to have issues. Given the cost of these drivers and the frequent firmware updates, a wait and see is my choice.
I've thought about going with a SAS RAID controller and 15K RAID drivers, but the cost/performance ratio comes out about the same and the 15K drives are noisey and power hungry but they're a "known" entity.
Rob
Maybe you are looking for
-
Quicktime always opens up..........
hello, when safari or firefox is running and a page is displayed which shows a video which show run on that page, quicktime opens up and displays it box and then a error message which says "url is not valid". thanks. lee
-
Acrobat 10. Can't print to file
Hi! When I try to print to file from any application (Word, Excel, Notepad, ....) with Adobe PDF printer, it creates an empty PS file. Can anyone help? I'm using Acrobat Standard X on Windows XP SP3. Thanks
-
Applying Path on Oracle 9i (9.2.0.4.0)
Hi all, I am planning to apply a upgrade path on my current Oracle Database server. I have not done this activity in past so I need to know some things before I start off. Issue 1 Does the patch applucation is self-explanatory? i.e. Does it have the
-
How and when does Berkeley free the memory of key and data ?
Hi, even though i just have posted a question several days ago, i couldnt find an answere to these questions in the Berkeley docs or on the internet: Does Berkleley Db free the data that is handeled to it with the key or the data objekt ? When is it
-
Transporting holiday calendar gives export error
I have changed settings for a holiday calendar and I am trying to transport the calendars to my test system. But in the process I get an export error saying "scrap char in NUMC field found in TFAIT.VON." Does anybody know what the issue might be and