Data unavailable

I have requirement as follows:
User generates a report by running a pl/sql procedure. Report is based on DB table which is deleted completely every day and data will not be available for 1 hour.
Requirement is, during this 1 hr period also user should get the report. We do not have to rewrite/alter procedure which is in production.
- Flash back option is disabled in DB
Any idea is appreciated.
Thanks in advance
Sateesh

Hi,
One solution i can think is ...
For an example you table name is LIVE_TABLE.
1. CREATE another table NON_LIVE_TABLE
2. CREATE VIEW which will be pointing to LIVE_TABLE and use View name in the procedure instead of table name.
SQL> create table LIVE_TABLE AS SELECT * FROM DUAL;
Table created.
SQL> create table NON_LIVE_TABLE AS SELECT * FROM DUAL;
Table created.
SQL>
SQL> CREATE VIEW FINAL_TABLE AS SELECT * FROM LIVE_TABLE;
View created.
Table TRUNCation and Data Loading:_
1. Before Loading the data Query the ALL_DEPENDENCIES view to get the dependent table name.
SQL> SELECT referenced_name from ALL_DEPENDENCIES WHERE NAME='FINAL_TABLE';
REFERENCED_NAME
LIVE_TABLE
SQL>2. Now TRUNC and LOAD data into NON_LIVE_TABLE if depenecy is on LIVE_TABLE else vice versa.
3. RECREATE the view so that it starts pointing NON_LIVE_DATA ( next day it should point LIVE_DATA).
4. Next day repeat STEP 1 to 4.
Recreation of view will take hardly few miliseconds and your reports will be available all the time.
Regards,
Avinash
Edited by: Avinash Tripathi on Dec 14, 2010 11:54 AM

Similar Messages

  • Mobile data unavailable

    Hello world,
    my name is Luca, from Rome, Italy.
    I bought a Xperia Z3 Compact in September, I found it to be an awesome device, but since the first day I got a strange behaviour on mobile networking.
    Often even if the device shows a very strong signal like HSDPA+ at full strength ( 4/4 bars ) still my mobile internet connection doesn't work at all, and the only way to reenable its functionality is to turn on "airplane mode" and off again..
    Because of the issue I contacted the Sony assistance service that guided me to the closest repair center, and in less than 2 weeks they gave me the device back, unfortunately with the very same issue still there, attached is the repair recepit that claims that the issue was not found at all, the translation of the note field is:
    "Issue not found, software updated, touch parameters calibration ok, recharge and power consumption verified.
    Data connection - Wi-Fi ok, if the issue will show again, proceed to configure internet/MSS setting.
    Back cover broken, fixable out of warranty." https://www.dropbox.com/s/7ttaixyqp1xqx59/recepit.jpg?dl=0
    There was also a minor issue about strange "noisy" behaviour / hyper sensitivity of the touch screen that was actually fixed by the software update ( the Lollipop update was rolling out those 2 weeks here in Italy ).
    The network issue itself is not 100% reproducible because some lucky times the issue doesn't show, but I managed to get a couple of screen recordings showing the issue, in both recordings I'm trying to access some internet service ( googling things or accessing some youtube clip ) but the browser and the YouTube client simply get stuck on loading. Note also that no "Network not available" alert is shown and that the signal icon in the top bar shows a full power HSDPA+ connection available. https://www.dropbox.com/s/149fflg1ayxwcyk/record.1.mp4?dl=0https://www.dropbox.com/s/yjpzwgkzbj4y29y/record.2.mp4?dl=0
    For sake of completeness my carrier is TIM, with a LTE enabled plan.
    The device is now configured to use 3G/2G networks only but the issue arise in 4G mode too.
    Also the "stamina mode" and the "background data queue" are set but I spent various days trying the different permutations of these and other settings looking for a combination that would solve this thing, with no success.
    I also already tried disabling bluetooth, again with no result.
    The device has "developer options" enabled but is not rooted nor the boot loader unlocked.
    I understand the people at the repair center cannot deeply investigate every single device they receive but I hope you will understand my disappointment in having a 500€ device that simply has its most powerful feature broken.
    If you cold put me in the right direction to solve this issue it would be great.
    Thank you very much for your attention and in advance for your help.
    Luca Castoro

    @uliwooly This is the screen recording I captured yesterday evening, forgive me, because the software repair moved the icons in the notification bar to their original location I was missing the "airplane mode" icon even if it was in the very center of the screen ( I was looking for it where I placed it in my previous configuration in the lower right corner ) so the video is slighlty longer than necessary.Also i forgot to change the capturing mode from landscape to portrait so there are black bands on the screen sides. https://www.dropbox.com/s/ye9a687jrncoja5/record.3.mp4?dl=0 Tomorrow I'll ask a friend to swap for a couple of days our devices so I should be able to investigate if it's a SIM related question or a device fault.I really don't think it will show itself as a SIM related problem as I can always make/reveive voice calls or SMS, but at least I'll remove any doubt about this thing.

  • ICal data unavailable after volume restore

    I recently used ASR to create an image of a data partition of a server. The data partition in question also held the iCal Server data store. After installing new drives, I restored this partition with ASR, and all the ACLs were gone from all the files (that may be normal, but it was annoying). But the real problem: nobody on the client machines can see their calendars - they don't show up in the list under their account descriptions.
    I've run proxyclean, but nothing needed cleaning. It's clearly a permissions problem, I just cant figure out where.
    Data store location in ical reads "/Volumes/Data/iCalData/CalendarServer/Documents"
    *Perms for those folders:*
    drwxrwxrwx@ 4 diradmin staff 136 Jun 8 15:25 iCalData
    drwxrwxrwx 4 root admin 136 Jun 9 13:40 CalendarServer
    drwxrwx---@ 4 _calendar _calendar 136 Mar 22 2008 Documents
    and everything below that is drwxr-xrwx
    Logs:
    127.0.0.1)] CCAE19E2-F45F-4212-B004-04AB35AB3284(admin) 'Open Directory Administrators'>
    2010-06-09 15:31:28-0400 [-] [caldav-8011] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[groups@058167af-ace8-519a-ac3d-e166498db024(/Search->/Loca l/Default)] ABCDEFAB-CDEF-ABCD-EFAB-CDEF00000014(staff) 'Users'>
    2010-06-09 15:31:28-0400 [-] [caldav-8011] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[groups@058167af-ace8-519a-ac3d-e166498db024(/Search->/LDAP v3/127.0.0.1)] 6BE5B502-4563-4E0B-9E0D-C555AAA29F07(staff) 'Open Directory Users'>
    2010-06-09 15:31:37-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/3939D86C-40D8-4425-AF4E-6ED5FA07CDC8/inbox/ HTTP/1.1
    2010-06-09 15:31:40-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/3939D86C-40D8-4425-AF4E-6ED5FA07CDC8/inbox/ HTTP/1.1
    2010-06-09 15:38:54-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/3939D86C-40D8-4425-AF4E-6ED5FA07CDC8/ HTTP/1.1
    2010-06-09 15:38:54-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/3939D86C-40D8-4425-AF4E-6ED5FA07CDC8/inbox/ HTTP/1.1
    2010-06-09 15:42:23-0400 [-] [caldav-8011] [AMP,client] Unauthenticated users not enabled with the 'calendar' SACL
    2010-06-09 15:42:23-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:42:24-0400 [-] [caldav-8011] [AMP,client] Unauthenticated users not enabled with the 'calendar' SACL
    2010-06-09 15:42:24-0400 [-] [caldav-8012] [OpenDirectoryService] Reloading users record cache
    2010-06-09 15:42:24-0400 [-] [caldav-8012] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[users@058167af-ace8-519a-ac3d-e166498db024(/Search->/Local /Default)] FFFFEEEE-DDDD-CCCC-BBBB-AAAA00000000(root) 'System Administrator'>
    2010-06-09 15:42:24-0400 [-] [caldav-8012] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[users@058167af-ace8-519a-ac3d-e166498db024(/Search->/LDAPv 3/127.0.0.1)] B3684481-FD2F-45F2-89C1-2A115FAF06EC(root) 'System Administrator'>
    2010-06-09 15:42:24-0400 [-] [caldav-8012] [AMP,client] PROPFIND /principals/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:42:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:42:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/inbox/ HTTP/1.1
    2010-06-09 15:42:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:42:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:42:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/8DBE094F-6644-4E0A-ADF7-C5AD24310F7E/ HTTP/1.1
    2010-06-09 15:42:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/EB286993-F127-4B53-BB2E-03DE86CAD2A4/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/4829AE18-D669-4B5C-84FF-F8F6F3E5A7A9/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/214C3A11-4B68-4CAA-9014-2124B93D7F3C/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/506FF654-3911-4ECD-8BF5-B387CB5B5F0E/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/71798596-8336-4B04-A9E0-B4D6B7E92482/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/3939D86C-40D8-4425-AF4E-6ED5FA07CDC8/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/BB970578-CCA9-446B-AF36-7A53376485C3/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/3939D86C-40D8-4425-AF4E-6ED5FA07CDC8/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/BB970578-CCA9-446B-AF36-7A53376485C3/ HTTP/1.1
    2010-06-09 15:42:25-0400 [-] [caldav-8012] [AMP,client] Unauthenticated users not enabled with the 'calendar' SACL
    2010-06-09 15:42:25-0400 [-] [caldav-8012] [AMP,client] Unauthenticated users not enabled with the 'calendar' SACL
    2010-06-09 15:42:25-0400 [-] [caldav-8011] [AMP,client] Unauthenticated users not enabled with the 'calendar' SACL
    2010-06-09 15:42:38-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/DA66656C-2475-4E35-AB40-6007177135FB/ HTTP/1.1
    2010-06-09 15:42:38-0400 [-] [caldav-8012] [AMP,client] PROPFIND /calendars/users/atpstaff/calendar/ HTTP/1.1
    2010-06-09 15:42:38-0400 [-] [caldav-8012] [AMP,client] PROPFIND /calendars/users/atpstaff/07779C9F-B3E5-4060-9E27-71A2BDB0D276/ HTTP/1.1
    2010-06-09 15:50:09-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/inbox/ HTTP/1.1
    2010-06-09 15:50:10-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:50:10-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/EB286993-F127-4B53-BB2E-03DE86CAD2A4/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [AMP,client] PROPFIND /principals/_uids_/214C3A11-4B68-4CAA-9014-2124B93D7F3C/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [OpenDirectoryService] Reloading groups record cache
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [OpenDirectoryService] Reloading resources record cache
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [OpenDirectoryService] Reloading locations record cache
    2010-06-09 15:50:11-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/71798596-8336-4B04-A9E0-B4D6B7E92482/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[groups@058167af-ace8-519a-ac3d-e166498db024(/Search->/Loca l/Default)] ABCDEFAB-CDEF-ABCD-EFAB-CDEF00000050(admin) 'Administrators'>
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[groups@058167af-ace8-519a-ac3d-e166498db024(/Search->/LDAP v3/127.0.0.1)] CCAE19E2-F45F-4212-B004-04AB35AB3284(admin) 'Open Directory Administrators'>
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[groups@058167af-ace8-519a-ac3d-e166498db024(/Search->/Loca l/Default)] ABCDEFAB-CDEF-ABCD-EFAB-CDEF00000014(staff) 'Users'>
    2010-06-09 15:50:11-0400 [-] [caldav-8012] [OpenDirectoryService] Record disabled due to conflict: <OpenDirectoryRecord[groups@058167af-ace8-519a-ac3d-e166498db024(/Search->/LDAP v3/127.0.0.1)] 6BE5B502-4563-4E0B-9E0D-C555AAA29F07(staff) 'Open Directory Users'>
    2010-06-09 15:50:11-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/506FF654-3911-4ECD-8BF5-B387CB5B5F0E/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/8DBE094F-6644-4E0A-ADF7-C5AD24310F7E/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/4829AE18-D669-4B5C-84FF-F8F6F3E5A7A9/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/3939D86C-40D8-4425-AF4E-6ED5FA07CDC8/ HTTP/1.1
    2010-06-09 15:50:11-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/BB970578-CCA9-446B-AF36-7A53376485C3/ HTTP/1.1
    2010-06-09 15:57:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 15:57:24-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/inbox/ HTTP/1.1
    2010-06-09 15:58:26-0400 [-] [caldav-8011] [AMP,client] Unauthenticated users not enabled with the 'calendar' SACL
    2010-06-09 15:58:26-0400 [-] [caldav-8011] [AMP,client] Unauthenticated users not enabled with the 'calendar' SACL
    2010-06-09 15:58:27-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/3C7994F4-5674-45DD-822A-60B4110D96E0/ HTTP/1.1
    2010-06-09 15:58:27-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/BB970578-CCA9-446B-AF36-7A53376485C3/ HTTP/1.1
    2010-06-09 15:58:29-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/BB970578-CCA9-446B-AF36-7A53376485C3/ HTTP/1.1
    2010-06-09 15:58:30-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/3C7994F4-5674-45DD-822A-60B4110D96E0/ HTTP/1.1
    2010-06-09 15:58:31-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/BB970578-CCA9-446B-AF36-7A53376485C3/inbox/ HTTP/1.1
    2010-06-09 15:58:32-0400 [-] [caldav-8011] [AMP,client] PROPFIND /calendars/_uids_/3C7994F4-5674-45DD-822A-60B4110D96E0/inbox/ HTTP/1.1
    2010-06-09 15:58:32-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/BB970578-CCA9-446B-AF36-7A53376485C3/ HTTP/1.1
    2010-06-09 15:58:32-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/3C7994F4-5674-45DD-822A-60B4110D96E0/ HTTP/1.1
    2010-06-09 15:58:32-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/EB286993-F127-4B53-BB2E-03DE86CAD2A4/ HTTP/1.1
    2010-06-09 15:58:32-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/EB286993-F127-4B53-BB2E-03DE86CAD2A4/ HTTP/1.1
    2010-06-09 15:58:33-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/71798596-8336-4B04-A9E0-B4D6B7E92482/ HTTP/1.1
    2010-06-09 15:58:33-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/71798596-8336-4B04-A9E0-B4D6B7E92482/ HTTP/1.1
    2010-06-09 15:58:33-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/5D3B2677-1D34-40F8-8CAA-D0686D641236/ HTTP/1.1
    2010-06-09 15:58:33-0400 [-] [caldav-8011] [AMP,client] PROPFIND /principals/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/ HTTP/1.1
    2010-06-09 16:00:27-0400 [-] [caldav-8011] [AMP,client] PROPPATCH /calendars/_uids_/85EFE8EE-519B-4578-8641-98F49E183226/inbox/ HTTP/1.1

    I have also seen this problem.
    My fix for it was to get the iCal package off the install CD.
    To do this, download a program called Pacifist. What it does is it reads the install disc, and finds all the packages that the programs are in.
    It is really handy for installing individual apps.
    Once you have extracted the package, install it as usual. Then you should see all you data back in iCal, until it breaks again.
    Note: This is not really a fix, rather a way to get iCal working again.
    I have also seen this problem happen when there was no update done, or rather the update was done a month before the problem occurred. This was a real fail update by apple and i hope they make a fix for it in the next update, although now that Snow Leopard is out, your probably won't wee any more fixes, as they will be too busy patching up 10.6, already up to 10.6.2

  • Packet data unavailable

    i have this problem. I cant browse . The message is always packet data unavailbale. I have gprs/mms settings configuration.My phone is nokia N95. Network : globe. thank you

    removing the sim and going to connectivity settings , go to destinations and remove all access points , then put sim back in and phone should re-establish access points automatically , if not contact your service provider and they should be able to send the correct settings via txt message ! Good Luck
    If I have helped at all, a click on the White Star is always appreciated :
    you can also help others by marking 'accept as solution' 

  • IMessage Fallback if data unavailable?

    When I sent a message to my iPhone from another iPhone it uses IMessage, but when I disable wifi (to simulate I am out of reach of an Internet connection) it doesn't sent the message as an SMS.... The sender doesn't necessarily know if I do or don't have a data connection so iMessage should see this and fall back, isn't it?!

    For the record, I mean disabling Internet on the receiving side, so the sender should not sent an iMessage but a SMS instead, which it currently doesn't.

  • IPhone 6+ 128gb Gold now says ship date unavailable

    I am getting frustrated along with the rest of you.  I ordered an iPhone 6+ 128GB Gold within 30 minutes after orders opened online.  My email confirmation listed Sept 19th as ship date.  The order status page said the same thing until late yesterday afternoon.  Now it says "not available at this time"  The availability for my husband's iPhone 6 64GB which was on the same order says the same thing.  Within 15 minutes of placing that order I placed orders for my kids' iPhones.  Those confirmations listed Oct 7 as the ship date.  Now the order status says "not available at this time"
    What is going on?  I have called customer service last evening and a rep spent over 30 minutes telling me I will get my phones when Verizon gets the phones, how many orders they had, Apple is never prepared, I will get an email when it ships, and on and on she went.  It was like I was being lectured about "This is what happens when I try to order along with millions of other crazy people."
    It seems like no one at Verizon knows or can figure out what is going on with our orders.  I ordered from them 2 years ago at iPhone 5 launch.  It look less than 5 minutes.  Order status was always updated.  Phones arrived on schedule. 
    I just want an honest update on the status of my orders.  Customer Service, are you listening?

    ordered 6 plus 128gb space gray on 10/13/2014. (10-31-2014 ship by) Have not heard anything but the e-mail of it now being by 11/21/2014 ship by, which I received after 7:00pm on 10/31/2014. (order status still shows 10/31/2014 ship by)
    I would love to know if anyone else has ordered the same model and color and actually received it?

  • No data to display on ADF mobile application

    Hello all,
    I have followed and tested Sherman's tutorial: http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/adfmobile/ShermanNewFeatiure-ADFMobileBrowser.html
    This is a great tutorial, simple and straightforward, so I easily put to work, in my machine (localhost), successfully. The application displays all data and behaves correctly.
    My problem is after I shut down jdeveloper, when I open the project again and run it, the application starts but don't display any data. Only shows the message: No data to display.
    I have checked and the data exists in the AppModule, all connections with the database server are OK.
    This error is so strange, I have tested several times and I get the same behaviour, restart of jdeveloper after a successfull deploy, makes the data unavailable.
    Does anyone have some clue to this strange behaviour?
    Regards,
    Pedro

    Thanks for reply Shay,
    I'm using Google Chrome 15.0.874.106 m and also IE 8.
    No error message appears on Weblogic log window only the following message:
    04:48:31 PM] Deploying 2 profiles...
    [04:48:34 PM] Wrote Web Application Module to C:\Users\jose.gouveia\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\o.j2ee\drs\Funcionarios\FuncLstWebApp.war
    [04:48:35 PM] Wrote Enterprise Application Module to C:\Users\jose.gouveia\AppData\Roaming\JDeveloper\system11.1.2.1.38.60.81\o.j2ee\drs\Funcionarios
    [04:48:35 PM] Deploying Application...
    [04:48:49 PM] Application Deployed Successfully.
    [04:48:49 PM] The following URL context root(s) were defined and can be used as a starting point to test your application:
    [04:48:49 PM] http://192.168.56.1:7101/Func
    [04:48:49 PM] Elapsed time for deployment: 20 seconds
    [04:48:49 PM] ---- Deployment finished. ----
    Run startup time: 19860 ms.
    [Application Funcionarios deployed to Server Instance IntegratedWebLogicServer]
    Target URL -- http://127.0.0.1:7101/Func/faces/browse.jspx
    <AdfFacesContext> <<clinit>> A implementação do AdfFacesContext não foi encontrada. Se se tratar de uma aplicação de rich client, não funcionará. Isto é esperado para as aplicações do Trinidad.
    Does this information give more insight about this issue?
    Regards,
    Pedro.

  • "Business" data unavailible?

    I just updated to Tiger.. Why is that the "Business" on Dashboard gives me "data unavailable" message for everything?
    what do you have to do to have it work?
    or the area I am in is not on the network?
    or any other reasons?
    thanks.

    You should be able to choose the "i' at the lower right (when it is open so you must enter something first) of the business pages widget then it will flip around so you can enter your zip code and search parameters.
    -mj
    [email protected]

  • When I install a host agent on my OEM 12c the status of the agent and host target in the OEM is stuck in pending. The agent is up and can ping the OMS. I haven't been able to locate any relevant errors in the logs

    Sum
    General
    Upload Metric Data
    Status
    Status Pending
    Availability (%)
    Unavailable
    Host
    Version
    Platform
    Operating System
    Operating System Agent Username
    Unavailable
    Interaction with Management Service
    Upload to
    Unavailable
    Last Successful Upload
    Unavailable
    Agent to Management Service Response Time (ms)
    Unavailable
    Agent Upload Interval (minutes)
    15
    Detailed Status
    Restarts (last 24 hours)
    0
    Secure
    Unavailable
    Agent Collecting
    Unavailable
    Agent Backed Off
    No
    Agent Purging Data
    Unavailable
    Above is the display from the agent page on the OEM console.
    I have also checked the agents page and confirmed that the agent is not Blacked Out.

    Hi Krishnan,
    emctl unsecure agent fails with the error:
    [15-04-2015 16:28:19] USERINFO ::Checking Agent for HTTP...
    [15-04-2015 16:28:19] USERINFO ::   Done.
    [15-04-2015 16:28:24] USERINFO ::Agent is already stopped...   Done.
    [15-04-2015 16:28:24] USERINFO ::Unsecuring agent...   Started.
    -115-04-15 16:28:25,294 [main] INFO  agent.SecureAgentCmd openPage.871 - Opening: https://usatl-w-cmcloud.americas.abb.com:1159/empbs/genwallet
    2015-04-15 16:28:29,521 [main] INFO  agent.SecureAgentCmd openPage.897 - Response Status Code: 200
    2015-04-15 16:28:29,523 [main] INFO  agent.SecureAgentCmd openPage.905 - RESPONSE_STATUS header: OK
    2015-04-15 16:28:29,525 [main] INFO  agent.SecureAgentCmd openPage.906 - Response body: -1
    2015-04-15 16:28:30,311 [main] INFO  agent.SecureAgentCmd openPage.871 - Opening: https://usatl-w-cmcloud.americas.abb.com:1159/empbs/genwallet
    2015-04-15 16:28:32,258 [main] INFO  agent.SecureAgentCmd openPage.897 - Response Status Code: 200
    2015-04-15 16:28:32,261 [main] INFO  agent.SecureAgentCmd openPage.905 - RESPONSE_STATUS header: OK
    2015-04-15 16:28:32,262 [main] INFO  agent.SecureAgentCmd openPage.906 - Response body: -1
    [15-04-2015 16:28:32] USERINFO ::OMS is locked. Cannot unsecure the Agent.
    [15-04-2015 16:28:32] USERINFO ::Unsecuring Agent...  Failed.
    The OMS is on a Windows 7 VM. Do you know the command to unlock the OMS?
    Thanks,
    Jerald

  • 4s with ios8 - battery drain issue - possible clue?

    I am one of the 4s users who is experiencing significantly accelerated battery drain since upgrading to ios 8.0 the first day it was released.  My battery will drain from %100 to less than %50 in less than two hours with typical light use.  Previously on ios 7.x I could go all day and be only down to %70 or so.  The way it's working now I won't make it through a day at work without having to recharge.
    I have tried optimizing in all the ways suggested in other threads (like turning off background apps etc.) and as far as I can tell my battery usage should be no worse (and presumably better since attention was given in ios 8.0 to making battery use better) than it was in ios 7.x.
    However, I'm wondering if this is causing my battery drain:
    In Settings->Privacy->Diagnostics & Usage->Diagnostic & Usage Data:
    There is a long list of "stacks+backboardd-2014-09-22-1..." files.  Yesterday (22nd) there were eight (8) of these rather large files created.  Today, on the 23rd, I'm up to three, when I looked this morning, there was just one.  Each file is rather massive, so something is burning a fair bit of energy triggering the debugging diagnostics tool to create and store these files.  (I'm guessing).
    Here's an example of the contents of one of them (just the head of the file, as I say, they are massive):
    {"os_version":"iPhone OS 8.0 (12A365)","bug_type":"188"}
      Incident Identifier: BDD2D474-CDCF-4409-8A16-732C2D22EF06
      CrashReporter Key:   f14750a09f7499f2bd4c6b15297406f27dc09a69
      Hardware Model:      iPhone4,1
      OS Version:          iPhone OS 8.0 (12A365)
      Kernel version:      Darwin Kernel Version 14.0.0: Tue Aug 19 15:08:02 PDT 2014; root:xnu-2783.1.72~8/RELEASE_ARM_S5L8940X
      Date:                2014-09-23 13:08:17 -0500
      Exception Code:      0xfaded322
      Reason:              Watchdog: Thermal not updating, backboardd 20.002234s last successful ping: 270b50 269f9fd0ce63 269r1d77000 200m0/1 200nffffffff 0m10004003/1 0u0 0n1
      Thermal data unavailable
      Frontmost process PID:    43
      Stackshot trace buffer size too small, trying again with 524288 bytes.
      Jetsam Level:              0
      Free Pages:              797
      Active Pages:          41652
      Inactive Pages:        18292
      Purgeable Pages:          71
      Wired Pages:           23313
      Speculative Pages:     20591
      Throttled Pages:       24377
      File-backed Pages:     67840
      Compressions:              0
      Decompressions:            0
      Compressor Size:           0
      Busy Buffer Count:         0
      Pages Wanted:            533
      Pages Reclaimed:           0
      Process 0 info:
              resident memory bytes:  64299008
              page faults:                3789
              page-ins:                      0
              copy-on-write faults:          0
              times throttled:               0
              times did throttle:            0
              user   time in task:          25.616464 seconds
              system time in task:           0.000000 seconds
      Process 0 kernel_task threads:
      thread 0x65 TH_WAIT|TH_UNINT 0x803e35a8
              thread priority:               92
              Base thread priority:          92
              thread sched flags:     none
              kernel cont: 0x8007ea05
              user   time in thread:     1.234561 seconds
              system time in thread:     0.000000 seconds
      thread 0x66 TH_RUN|TH_IDLE 0
              thread priority:                0
              Base thread priority:           0
              thread sched flags:     none
              kernel cont: 0x800294e5
              user   time in thread:     6.564943 seconds
              system time in thread:     0.000000 seconds
      thread 0x67 TH_WAIT|TH_UNINT 0x8002574d
              thread priority:               95
              Base thread priority:          95
              thread sched flags:     none
              kernel cont: 0x8002574d
              user   time in thread:     0.027250 seconds
              system time in thread:     0.000000 seconds
    ...etc...
    Anyway, just wondering if this might be related to why my phone's batter life has plummeted.  Also, does anyone have any insight as to what this file is actually telling us?  I'm happy to send diagnostics to Apple if it will help them get to the bottom of this issue that seems to be plaguing other 4s users.
    Thanks!
    James Rowell.

    I just wanted to post a small follow up. During my recent attempts to debug my battery issues, I rebooted the iPhone.  I don't think my phone had been rebooted since I did the upgrade and started experiencing these battery issues.  At any rate, since rebooting I have seen my battery use return to much more acceptable and expected rates of idle/usage times.
    Try rebooting your phone to see if it helps!  I wonder if it's just this simple for the folks who have been experiencing similar problems?!
    Good luck all.

  • SAP Support for Classic G/L in ECC 6.0 and above

    Hello,
    Running an SAP upgrade project from 4.6C to ECC 6.0 (EHP6). The customer is running the existing release since the past 8 years with FI/CO, MM,SD,PM and HCM modules.
    We are exploring the possibilities and repercussions of moving on to new G/L from the legacy classic G/L. Please have a look at the mentioned points for replies accordingly.
    1. As far as I understand, if need to seamlessly transit in the ECC 6.0 with New G/L in a way that the old transactional data, and all balances are retained with historical records, then we need to purchase the SAP New G/L Migration Services, and this would be lead and done by SAP. There is no alternate way of doing it solely by our ownself, Is this correct ?. If we engage SAP for this migration exercise and consulting then does it ensure that all historical data and balances are moved intact in the new G/L environment and from an end user perspective all transactional done to date before moving in ECC 6.0 are retained.
    2. I guess we still need to review the integration impact of the new G/L for all other modules, is there a substantial rework to be done or with minimal effort, new account assignments and related configuration can be altered .
    3. If we don't opt for SAP G/L Migration service but still want to activate and use the new G/L and profit center accounting, then as far as myself and my team assess, we need to decide a cutover date and gather the balances/open items from the legacy G/L and upload them to the new G/L in ECC 6.0, just as it would be the case for a fresh new implementation for a customer coming from non-SAP environment. If this is correct then :    
    The customer will lose all historical, detailed transactional data with respect to the legacy G/L and relevant originating entries. In such case for any business reporting requirement, the customer has to keep a separate PRD server alive in a dormant state for fetching the data before the transition in ECC 6.0 environment. Is this the correct understanding and the only possible approach, can there be a better way of ensuring the availability of historical data.
    In such a case of doing a cutover data migration from old G/L to new G/L, do we have to upload the rest of the master/transactional data for all other modules as well, enacting a situation that all of them started as fresh new modules in ECC.6.0,  or the legacy master / transactional data for all other modules can be kept intact for historical purposes. (examples, all vendors and PO / sales order and customer master / employee master and all payroll historical records for past 8 years).
    4. Any indication or official SAP note, that for how long SAP intends to support the legacy G/L in the upcoming ECC versions. It is necessary to know in case the customer currently opts for still continuing with the classic G/L in ECC 6.0 , but we have a lurking danger that SAP would stop the support and availability of legacy classic G/L in the near future. So to a have a long term sustainable benefit, we might deliberate with the customer to take a bitter sip now , and move on to the new G/L with all its bells/whistles and the nuisances it might bring in terms of historical transaction data unavailability.
    I hope i was able to make my scenario clearly understandable for having some valuable input from the forum members.
    Thanks a lot for reading and replying.

    Hi Syed,
    From Technical basis perspective there is not much work in newGL migration apart from application and database tuning.
    Time taken for migrating to newGL will depend upon number of open items available in the system at the time of migration.
    Most of your queries are functional and suggestion would be to move this thread to ERP Financials.
    For your information you may go through below links
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/ae/b3569044974c6985c4e711e20435d6/content.htm
    http://wiki.scn.sap.com/wiki/display/ERPFI/NewGL+Migration+Scenarios
    Hope this helps.
    Regards,
    Deepak Kori

  • How can I tell if my iPhone 5 is being monitored

    Like what the heavens is this
    Incident Identifier: C64D68EF-4FEA-45AF-BD2B-970B048D6204
    CrashReporter Key:   dd5f10720916bf17d853d6fb30dbe43eae04c5ad
    Hardware Model:      iPhone5,1
    OS Version:          iPhone OS 7.0.2 (11A501)
    Kernel version:      Darwin Kernel Version 14.0.0: Mon Sep  9 20:49:01 PDT 2013; root:xnu-2423.1.74~2/RELEASE_ARM_S5L8950X
    Date:                2013-10-05 15:33:57 -0800
    Exception Code:      0xbaaaaaad
    Reason:              Manually triggered stackshot via backboardd
    Thermal data unavailable
    Frontmost process PID:    33
    Jetsam Level:              0
    Free Pages:            86813
    Active Pages:          48555
    Inactive Pages:        24440
    Purgeable Pages:        8464
    Wired Pages:           22412
    Speculative Pages:     31266
    Throttled Pages:       46241
    File-backed Pages:     81947
    Compressions:              0
    Decompressions:            0
    Compressor Size:           0
    Busy Buffer Count:         0
    Pages Wanted:              0
    Pages Reclaimed:           0
    Process 0 info:
         resident memory bytes:  73293824
         page faults:                2436
         page-ins:                      0
         copy-on-write faults:          0
         times throttled:               0
         times did throttle:            1
         user   time in task:        3033.585391 seconds
         system time in task:           0.000000 seconds
    Process 0 kernel_task threads:
    thread 0x1 TH_WAIT|TH_UNINT 0x8037cb3c
         thread priority:               92
         Base thread priority:          92
         thread sched flags:     none
         kernel cont: 0x800ff5d5
         user   time in thread:     0.284941 seconds
         system time in thread:     0.000000 seconds
    thread 0x2 TH_RUN|TH_IDLE 0
         thread priority:                0
         Base thread priority:           0
         thread sched flags:     none
         kernel cont: 0x800c146d
         user   time in thread:  1426.733573 seconds
         system time in thread:     0.000000 seconds
    thread 0x3 TH_WAIT|TH_UNINT 0x800bde21
         thread priority:               95
         Base thread priority:          95
         thread sched flags:     none
         kernel cont: 0x800bde21
         user   time in thread:     0.288740 seconds
         system time in thread:     0.000000 seconds
    thread 0x4 TH_WAIT|TH_UNINT 0x8037e3b0
         thread priority:               80
         Base thread priority:          80
         thread sched flags:     none
         kernel cont: 0x800cd389
         user   time in thread:     0.158330 seconds
         system time in thread:     0.000000 seconds
    thread 0x5 TH_WAIT|TH_UNINT 0x8037e3b8
         thread priority:               93
         Base thread priority:          93
         thread sched flags:     none
         kernel cont: 0x800cd591
         user   time in thread:     0.000010 seconds
         system time in thread:     0.000000 seconds
    thread 0x6 TH_WAIT|TH_UNINT 0xca2e3cb8
         thread priority:               95
         Base thread priority:          95
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800d2bbd 0x8001e61c
         user   time in thread:     0.000402 seconds
         system time in thread:     0.000000 seconds
    thread 0x7 TH_WAIT|TH_UNINT 0
         thread priority:               94
         Base thread priority:          94
         thread sched flags:     none
         kernel cont: 0x800cfcad
         user   time in thread:     0.007175 seconds
         system time in thread:     0.000000 seconds
    thread 0x8 TH_WAIT|TH_UNINT 0x8037cca4
         thread priority:               95
         Base thread priority:          95
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x80112e4b 0x8001e61c
         user   time in thread:     0.001290 seconds
         system time in thread:     0.000000 seconds
    thread 0x9 TH_WAIT|TH_UNINT 0x8bcfb65c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0xc TH_WAIT|TH_UNINT 0x8bd23abc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.788015 seconds
         system time in thread:     0.000000 seconds
    thread 0x1e TH_WAIT|TH_UNINT 0x8044ea1c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000014 seconds
         system time in thread:     0.000000 seconds
    thread 0x22 TH_WAIT|TH_UNINT 0x8044e8b4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000013 seconds
         system time in thread:     0.000000 seconds
    thread 0x27 TH_WAIT|TH_UNINT 0x8037f62c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8026c2bd
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0x28 TH_WAIT|TH_UNINT 0x8bedae54
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.004976 seconds
         system time in thread:     0.000000 seconds
    thread 0x29 TH_WAIT|TH_UNINT 0x8bedaabc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000861 seconds
         system time in thread:     0.000000 seconds
    thread 0x2a TH_WAIT|TH_UNINT 0x8beda5bc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000010 seconds
         system time in thread:     0.000000 seconds
    thread 0x2b TH_WAIT|TH_UNINT 0x8beda314
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000010 seconds
         system time in thread:     0.000000 seconds
    thread 0x33 TH_WAIT|TH_UNINT 0x8beeabac
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000145 seconds
         system time in thread:     0.000000 seconds
    thread 0x68 TH_WAIT|TH_UNINT 0x8beec724
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     1.381468 seconds
         system time in thread:     0.000000 seconds
    thread 0x6a TH_WAIT|TH_UNINT 0x8bf9ed3c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000015 seconds
         system time in thread:     0.000000 seconds
    thread 0x6b TH_WAIT|TH_UNINT 0x8bf9ecc4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x8008abff 0x8001e61c
         user   time in thread:     0.949146 seconds
         system time in thread:     0.000000 seconds
    thread 0x6c TH_WAIT|TH_UNINT 0x8bf9ea6c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     1.267516 seconds
         system time in thread:     0.000000 seconds
    thread 0x6d TH_WAIT|TH_UNINT 0x8bf9e8b4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.030421 seconds
         system time in thread:     0.000000 seconds
    thread 0x6e TH_WAIT|TH_UNINT 0x8bf9e65c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.002393 seconds
         system time in thread:     0.000000 seconds
    thread 0x6f TH_WAIT|TH_UNINT 0x8bf9e4a4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0x70 TH_WAIT|TH_UNINT 0x8bf9e33c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.037684 seconds
         system time in thread:     0.000000 seconds
    thread 0x71 TH_WAIT|TH_UNINT 0x8bf9e15c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000011 seconds
         system time in thread:     0.000000 seconds
    thread 0x72 TH_WAIT|TH_UNINT 0x8bf84fbc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000011 seconds
         system time in thread:     0.000000 seconds
    thread 0x73 TH_WAIT|TH_UNINT 0x8bf84e7c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0x74 TH_WAIT|TH_UNINT 0x8bf84c4c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0x76 TH_WAIT|TH_UNINT 0x8bf84904
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.767722 seconds
         system time in thread:     0.000000 seconds
    thread 0x77 TH_WAIT|TH_UNINT 0x8bf84684
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     1.435439 seconds
         system time in thread:     0.000000 seconds
    thread 0x78 TH_WAIT|TH_UNINT 0x8bf84404
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.741600 seconds
         system time in thread:     0.000000 seconds
    thread 0x7a TH_WAIT|TH_UNINT 0x8bfb1f94
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000013 seconds
         system time in thread:     0.000000 seconds
    thread 0x7c TH_WAIT|TH_UNINT 0x8bfb1ea4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000013 seconds
         system time in thread:     0.000000 seconds
    thread 0x7e TH_WAIT|TH_UNINT 0x8bfb19f4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.007323 seconds
         system time in thread:     0.000000 seconds
    thread 0x7f TH_WAIT|TH_UNINT 0x8bf83cec
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0x81 TH_WAIT|TH_UNINT 0x8bf83774
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000014 seconds
         system time in thread:     0.000000 seconds
    thread 0x82 TH_WAIT|TH_UNINT 0x8bf834cc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0x83 TH_WAIT|TH_UNINT 0x8bf83224
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000011 seconds
         system time in thread:     0.000000 seconds
    thread 0x84 TH_WAIT|TH_UNINT 0x8bf82f6c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.047931 seconds
         system time in thread:     0.000000 seconds
    thread 0x85 TH_WAIT|TH_UNINT 0x8bf82cc4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000011 seconds
         system time in thread:     0.000000 seconds
    thread 0x86 TH_WAIT|TH_UNINT 0x8bf82724
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.001153 seconds
         system time in thread:     0.000000 seconds
    thread 0x87 TH_WAIT|TH_UNINT 0x8bf82224
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000016 seconds
         system time in thread:     0.000000 seconds
    thread 0x88 TH_WAIT|TH_UNINT 0x8c068814
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000010 seconds
         system time in thread:     0.000000 seconds
    thread 0x8d TH_WAIT|TH_UNINT 0x8c068274
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0x92 TH_WAIT|TH_UNINT 0x8c059c74
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x8008abff 0x8001e61c
         user   time in thread:     0.050050 seconds
         system time in thread:     0.000000 seconds
    thread 0x98 TH_RUN|TH_IDLE 0
         thread priority:                0
         Base thread priority:           0
         thread sched flags:     none
         kernel: 0x800c1553 0x8001e61c
         user   time in thread:  1524.633018 seconds
         system time in thread:     0.000000 seconds
    thread 0x9a TH_WAIT|TH_UNINT 0x8c05910c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000012 seconds
         system time in thread:     0.000000 seconds
    thread 0xa0 TH_WAIT|TH_UNINT 0x8c0c4f94
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0xa1 TH_WAIT|TH_UNINT 0x8c0c4ef4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0xaa TH_WAIT|TH_UNINT 0x8c0c48dc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x8008abff 0x8001e61c
         user   time in thread:     0.002161 seconds
         system time in thread:     0.000000 seconds
    thread 0xba TH_WAIT|TH_UNINT 0x809ddbd4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x8008abff 0x8001e61c
         user   time in thread:     0.007530 seconds
         system time in thread:     0.000000 seconds
    thread 0xbb TH_WAIT|TH_UNINT 0x809dd954
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.238435 seconds
         system time in thread:     0.000000 seconds
    thread 0xc1 TH_WAIT|TH_UNINT 0x8c06cf1c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     2.040494 seconds
         system time in thread:     0.000000 seconds
    thread 0xc3 TH_WAIT|TH_UNINT 0x8c06ca1c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0xc4 TH_WAIT|TH_UNINT 0x8c06c9a4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.001540 seconds
         system time in thread:     0.000000 seconds
    thread 0xc9 TH_WAIT|TH_UNINT 0x8c0eee2c
         thread priority:               97
         Base thread priority:          97
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.005496 seconds
         system time in thread:     0.000000 seconds
    thread 0xcb TH_WAIT|TH_UNINT 0x8c0eed8c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000008 seconds
         system time in thread:     0.000000 seconds
    thread 0xcc TH_WAIT|TH_UNINT 0x8c0ee01c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0xd3 TH_WAIT|TH_UNINT 0x806f8594
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000011 seconds
         system time in thread:     0.000000 seconds
    thread 0xd4 TH_WAIT|TH_UNINT 0x806f8634
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     1.267741 seconds
         system time in thread:     0.000000 seconds
    thread 0xde TH_WAIT|TH_UNINT 0x8037e4b0
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8012f01d
         user   time in thread:     0.000008 seconds
         system time in thread:     0.000000 seconds
    thread 0xe0 TH_WAIT|TH_UNINT 0x8037de8c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x80281a4d
         user   time in thread:     0.001036 seconds
         system time in thread:     0.000000 seconds
    thread 0xe1 TH_WAIT|TH_UNINT 0x8037f5b8
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8024df65
         user   time in thread:     0.000019 seconds
         system time in thread:     0.000000 seconds
    thread 0xe2 TH_WAIT|TH_UNINT 0x8037f5b8
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8024df65
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0xe3 TH_WAIT|TH_UNINT 0x8003dc99
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8026c2bd
         user   time in thread:     0.000008 seconds
         system time in thread:     0.000000 seconds
    thread 0xe4 TH_WAIT|TH_UNINT 0x8037e510
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8026c2bd
         user   time in thread:     0.000007 seconds
         system time in thread:     0.000000 seconds
    thread 0xe5 TH_WAIT|TH_UNINT 0x80383fb0
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015cf6f 0x8001e61c
         user   time in thread:     0.017170 seconds
         system time in thread:     0.000000 seconds
    thread 0xe6 TH_WAIT|TH_UNINT 0x8037d250
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8026c2bd
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0xe7 TH_WAIT|TH_UNINT 0x8037dc84
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x80270f11
         user   time in thread:     0.000180 seconds
         system time in thread:     0.000000 seconds
    thread 0xe8 TH_WAIT|TH_UNINT 0x8037dc70
         thread priority:               95
         Base thread priority:          95
         thread sched flags:     none
         kernel cont: 0x8026ff59
         user   time in thread:     0.000110 seconds
         system time in thread:     0.000000 seconds
    thread 0xeb TH_WAIT|TH_UNINT 0x809ddc9c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000172 seconds
         system time in thread:     0.000000 seconds
    thread 0xec TH_WAIT|TH_UNINT 0x8c0c2ef4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000243 seconds
         system time in thread:     0.000000 seconds
    thread 0xf8 TH_WAIT|TH_UNINT 0x8c47b724
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0x101 TH_WAIT|TH_UNINT 0x80a9d3e0
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8005736f 0x80a989a7 0x8001e61c
         user   time in thread:     0.000009 seconds
         system time in thread:     0.000000 seconds
    thread 0x109 TH_WAIT|TH_UNINT 0x80004869
         thread priority:               81
         Base thread priority:          81
         thread sched flags: TH_SFLAG_PROMOTED
         kernel: 0x800c0e35 0x800c0249 0x80d58c3d 0x80d58911 0x80422609 0x80e5fd4d 0x8098a007 0x809872e1 0x8008b4f1 0x8008ab45 0x8008ab95 0x8001e61c
         user   time in thread:     4.010159 seconds
         system time in thread:     0.000000 seconds
    thread 0x10c TH_WAIT|TH_UNINT 0x80aa3270
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x80005a35 0x8026c05d 0x8005736f 0x80aa0119 0x8001e61c
         user   time in thread:     0.079481 seconds
         system time in thread:     0.000000 seconds
    thread 0x10d TH_WAIT|TH_UNINT 0x8c12a15c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     8.487605 seconds
         system time in thread:     0.000000 seconds
    thread 0x10f TH_WAIT|TH_UNINT 0x80cad230
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x80005a35 0x8026c05d 0x8005736f 0x80cab355 0x8001e61c
         user   time in thread:     0.069662 seconds
         system time in thread:     0.000000 seconds
    thread 0x110 TH_WAIT|TH_UNINT 0x8c686c4c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:    15.977407 seconds
         system time in thread:     0.000000 seconds
    thread 0x119 TH_WAIT|TH_UNINT 0x8c8972c4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:    14.469932 seconds
         system time in thread:     0.000000 seconds
    thread 0x12b TH_WAIT|TH_UNINT 0x8d041c9c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0x12f TH_WAIT 0x8aef9d14
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x806dc401 0x806da4d5 0x8008b8e9 0x806da311 0x806ed031 0x8001e61c
         user   time in thread:     0.000022 seconds
         system time in thread:     0.000000 seconds
    thread 0x154 TH_WAIT|TH_UNINT 0x8cf6047c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.335668 seconds
         system time in thread:     0.000000 seconds
    thread 0x156 TH_WAIT|TH_UNINT 0x80004869
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x8007a2cb 0x8068cd95 0x807278e9 0x806720ff 0x8008b8e9 0x8068ccfb 0x8068d763 0x8072776d 0x8008b4f1 0x806709f9 0x8008b8e9 0x8067099d 0x8008ab45 0x8008ab95 0x8001e61c
         user   time in thread:     0.539602 seconds
         system time in thread:     0.000000 seconds
    thread 0x159 TH_WAIT|TH_UNINT 0x80004869
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x8007a2cb 0x8068cd95 0x807278e9 0x806720ff 0x8008b8e9 0x8068ccfb 0x8068d763 0x8072776d 0x8008b4f1 0x806709f9 0x8008b8e9 0x8067099d 0x8008ab45 0x8008ab95 0x8001e61c
         user   time in thread:     0.252653 seconds
         system time in thread:     0.000000 seconds
    thread 0x15c TH_WAIT|TH_UNINT 0x8cf6b8b4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000477 seconds
         system time in thread:     0.000000 seconds
    thread 0x164 TH_WAIT|TH_UNINT 0x8c3e2678
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.222261 seconds
         system time in thread:     0.000000 seconds
    thread 0x165 TH_WAIT|TH_UNINT 0x8c3e21a4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8005736f 0x8015b5a7 0x8001e61c
         user   time in thread:     0.215994 seconds
         system time in thread:     0.000000 seconds
    thread 0x170 TH_WAIT|TH_UNINT 0x80751e68
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.000008 seconds
         system time in thread:     0.000000 seconds
    thread 0x171 TH_WAIT|TH_UNINT 0x80751994
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015b531 0x8001e61c
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0x174 TH_WAIT|TH_UNINT 0x80751678
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.000007 seconds
         system time in thread:     0.000000 seconds
    thread 0x175 TH_WAIT|TH_UNINT 0x807511a4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015b531 0x8001e61c
         user   time in thread:     0.000007 seconds
         system time in thread:     0.000000 seconds
    thread 0x178 TH_WAIT|TH_UNINT 0x808b5e68
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.000007 seconds
         system time in thread:     0.000000 seconds
    thread 0x179 TH_WAIT|TH_UNINT 0x808b5994
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015b531 0x8001e61c
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0x17c TH_WAIT|TH_UNINT 0x80754e04
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.960959 seconds
         system time in thread:     0.000000 seconds
    thread 0x182 TH_WAIT|TH_UNINT 0x8d058ddc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.053237 seconds
         system time in thread:     0.000000 seconds
    thread 0x194 TH_WAIT|TH_UNINT 0x8c421c80
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8008acf7 0x8008b9c3 0x80a1983f 0x8008b8e9 0x80a1a3f1 0x80a19ac1 0x8001e61c
         user   time in thread:     3.540672 seconds
         system time in thread:     0.000000 seconds
    thread 0x1a2 TH_WAIT|TH_UNINT 0x8d13b5bc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000005 seconds
         system time in thread:     0.000000 seconds
    thread 0x1b0 TH_WAIT 0
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800b0715 0x8029b1cd 0x8001e61c
         user   time in thread:     0.000050 seconds
         system time in thread:     0.000000 seconds
    thread 0x1b1 TH_WAIT|TH_UNINT 0x8037f1d8
         thread priority:               92
         Base thread priority:          92
         thread sched flags:     none
         kernel cont: 0x8010329d
         user   time in thread:     0.000009 seconds
         system time in thread:     0.000000 seconds
    thread 0x1b2 TH_WAIT|TH_UNINT 0x800ff211
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800ff211
         user   time in thread:     0.000005 seconds
         system time in thread:     0.000000 seconds
    thread 0x1b3 TH_WAIT|TH_UNINT 0x800ff62d
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800ff62d
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0x1b4 TH_WAIT|TH_UNINT 0x8037e400
         thread priority:               92
         Base thread priority:          92
         thread sched flags:     none
         kernel cont: 0x800fbf21
         user   time in thread:     0.000005 seconds
         system time in thread:     0.000000 seconds
    thread 0x1be TH_WAIT|TH_UNINT 0x8d1b99cc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     7.980376 seconds
         system time in thread:     0.000000 seconds
    thread 0x1c4 TH_WAIT|TH_UNINT 0x8a3d5f94
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000046 seconds
         system time in thread:     0.000000 seconds
    thread 0x1c6 TH_WAIT|TH_UNINT 0x8a3d579c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0x1c9 TH_WAIT|TH_UNINT 0x8a3d5364
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000710 seconds
         system time in thread:     0.000000 seconds
    thread 0x1cd TH_WAIT|TH_UNINT 0x8d2649cc
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000244 seconds
         system time in thread:     0.000000 seconds
    thread 0x320 TH_WAIT|TH_UNINT 0x808b5678
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.000009 seconds
         system time in thread:     0.000000 seconds
    thread 0x321 TH_WAIT|TH_UNINT 0x808b51a4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015b531 0x8001e61c
         user   time in thread:     0.000008 seconds
         system time in thread:     0.000000 seconds
    thread 0x329 TH_WAIT|TH_UNINT 0x9aa6ee68
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.022045 seconds
         system time in thread:     0.000000 seconds
    thread 0x32a TH_WAIT|TH_UNINT 0x9aa6e994
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8005736f 0x8015b5a7 0x8001e61c
         user   time in thread:     0.015240 seconds
         system time in thread:     0.000000 seconds
    thread 0x36c TH_WAIT|TH_UNINT 0x9becee04
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel cont: 0x8008ab81
         user   time in thread:     0.000006 seconds
         system time in thread:     0.000000 seconds
    thread 0x372 TH_WAIT|TH_UNINT 0x9aa6e678
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.000013 seconds
         system time in thread:     0.000000 seconds
    thread 0x373 TH_WAIT|TH_UNINT 0x9aa6e1a4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015b531 0x8001e61c
         user   time in thread:     0.000009 seconds
         system time in thread:     0.000000 seconds
    thread 0x37a TH_WAIT|TH_UNINT 0x9c1ece68
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8015d987 0x8001e61c
         user   time in thread:     0.000014 seconds
         system time in thread:     0.000000 seconds
    thread 0x37b TH_WAIT|TH_UNINT 0x9c1ec994
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8026c06b 0x8005736f 0x8015b5a7 0x8001e61c
         user   time in thread:     0.002279 seconds
         system time in thread:     0.000000 seconds
    thread 0x4f4 TH_WAIT 0x8bd357a4
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x806dc401 0x806d79f9 0x8008b8e9 0x806db2db 0x806cd483 0x806cd77f 0x8001e61c
         user   time in thread:     0.087166 seconds
         system time in thread:     0.000000 seconds
    thread 0x4f5 TH_WAIT 0x805d147c
         thread priority:               81
         Base thread priority:          81
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8008acf7 0x8008b9c3 0x806d85ff 0x806d733f 0x8008b8e9 0x806d8dfd 0x806cdb3b 0x8001e61c
         user   time in thread:     0.071081 seconds
         system time in thread:     0.000000 seconds
    thread 0x1e3a TH_WAIT|TH_UNINT 0
         thread priority:               93
         Base thread priority:          93
         thread sched flags:     none
         kernel cont: 0x800cfe61
         user   time in thread:     0.001266 seconds
         system time in thread:     0.000000 seconds
    thread 0x1e48 TH_WAIT|TH_UNINT 0x8d121900
         thread priority:               93
         Base thread priority:          93
         thread sched flags:     none
         kernel: 0x800c0e35 0x800c0249 0x800059c1 0x8008acf7 0x8008b9c3 0x8085388d 0x808501f9 0x807d6d29 0x807f6673 0x807f63a3 0x8008b8e9 0x807f6483 0x802b5893 0x800cff9b 0x8001e61c
         user   time in thread:     0.000247 seconds
         system time in thread:     0.000000 seconds
    thread 0x1e49 TH_WAIT|TH_UNINT 0
         thread priority:               93
         Base thread priority:          93
         thread sched flags:     none
         kernel cont: 0x800cfe61
         user   time in thread:     0.002454 seconds
         system time in thread:     0.000000 seconds
    thread 0x1e4b TH_WAIT|TH_UNINT 0
         thread priority:               93
         Base thread priority:          93
         thread sched flags:     none
         kernel cont: 0x800cfe61
         user   time in thread:     0.002745 seconds
         system time in thread:     0.000000 seconds
    thread 0x1e4f TH_WAIT|TH_UNINT 0
         thread priority:               93
         Base thread priority:          93
         thread sched flags:     none
         kernel cont: 0x800cfe61
         user   time in thread:     0.000616 seconds
         system time in thread:     0.000000 seconds
    Process 1 info:
         resident memory bytes:  1245184
         page faults:                8008
         page-ins:                   1074
         copy-on-write faults:       3781
         times throttled:               0
         times did throttle:            0
         user   time in task:           1.685523 seconds
         system time in task:           0.000000 seconds
    Process 1 binary images:
    0x2be45000 <f15a81a9454d33b1b0db274777ecf386>
    0x15000 <3c91c465efa632c7a677dd0b5fdee0dc>
    Process 1 launchd threads:
    thread 0x1af TH_WAIT 0
         thread priority:               30
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800b0655
         user: 0x3bbc8a84 0x3bbc8881 0x3bc5b211 0x3bc5b347 0x1a145 0x1875b 0x3bb24ab7
         user   time in thread:     1.356240 seconds
         system time in thread:     0.000000 seconds
    thread 0x1d9 TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x8026c2bd
         user: 0x3bbdb440 0x1923f 0x3bc41c5d 0x3bc41bcf 0x3bc3fcd0
         user   time in thread:     0.031975 seconds
         system time in thread:     0.000000 seconds
    thread 0x1da TH_WAIT 0x8037c6ac
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800c7811
         user: 0x3bbdb550 0x3bb4c4ed 0x3bb9a5dd 0x18857 0x3bc41c5d 0x3bc41bcf 0x3bc3fcd0
         user   time in thread:     0.297308 seconds
         system time in thread:     0.000000 seconds
    Process 14 info:
         resident memory bytes:  5316608
         page faults:               14033
         page-ins:                    535
         copy-on-write faults:        175
         times throttled:               0
         times did throttle:            0
         user   time in task:           8.172742 seconds
         system time in task:           0.000000 seconds
    Process 14 binary images:
    0x2be76000 <f15a81a9454d33b1b0db274777ecf386>
    0x23000 <4fe3311b8b7037d49beecfa0fdcc36a0>
    0x49000 <78fda66b07d238cb9b3a82821dcacff7>
    0x58000 <4fe73958847f3e6c9e648edcbb17b96a>
    0x61000 <3b0f9eee68933363a319711480e01e71>
    0x204000 <59763b4d9bc432d1bbbb433bb5648f97>
    0x1bb7000 <0828c56b23003f1bb7fd002ee90ab917>
    0x1bbe000 <92eb48a6becb3e3bb6570f0197106532>
    0x1bc6000 <b9c4df88e87c36e88d46ff462b32ba70>
    0x1bcd000 <2c1937163ebe3a76a157ff5b995a35e0>
    0x1c55000 <00207af4fb373169a8b53260eec70ee7>
    0x1cdc000 <84606a61285131ba92ebad9450fe3960>
    0x1cdf000 <4bc8fe6feebc350f9d59acbc0ddaadca>
    0x1ce8000 <f1c1d601cac0320da99f85d656ce6ab9>
    0x1cfb000 <1a4db7ce0aee37749d41ac26d5810394>
    0x1d00000 <695239f0346139689fcadcde33295cff>
    0x1d07000 <6eae01c6fed83d1585b43da5ff13b4b0>
    0x1d0c000 <73d7dc51b99d3706a4d6d647cc6579ef>
    0x1d11000 <56152e87c8ce33d2be34b77ae1097452>
    0x1d18000 <e71219df91843af087a50dd564defa5b>
    0x1d1c000 <8cf7091e9ad93992b59785cf263e0bdf>
    0x1d21000 <501eb880e4c93a0a80bd8e673dcab5d7>
    0x1d26000 <8782802e862e3b36a1e4a605021da148>
    0x1d2b000 <fb73be1380c534dcad408cf998f53d20>
    0x1e3b000 <a6eb150cd6a83f82a7a915a6c61da403>
    0x1e40000 <6fbd1508e9a13a768237a8a4424b4343>
    0x1ece000 <56e74d3681403500bfeb14be5236cce7>
    0x1ed5000 <30335f65b2d63a099bb707c43058b578>
    Process 14 UserEventAgent threads:
    thread 0x1e8 TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800b0655
         user: 0x3bbc8a84 0x3bbc8881 0x312fb561 0x312f9cc7 0x31264541 0x31264323 0x31c52827 0x31ca3669 0x23f2d 0x3bb24ab7
         user   time in thread:     0.300891 seconds
         system time in thread:     0.000000 seconds
    thread 0x226 TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800b0655
         user: 0x3bbc8a84 0x3bbc8881 0x312fb561 0x312f9c81 0x31264541 0x312a81ab 0x62469 0x3bc41c5d 0x3bc41bcf 0x3bc3fcd0
         user   time in thread:     0.003178 seconds
         system time in thread:     0.000000 seconds
    thread 0x227 TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x8026c2bd
         user: 0x3bbdb440 0x312ff463 0x3bc41c5d 0x3bc41bcf 0x3bc3fcd0
         user   time in thread:     0.000113 seconds
         system time in thread:     0.000000 seconds
    thread 0x22f TH_WAIT 0
         thread priority:               33
         Base thread priority:          33
         thread sched flags:     none
         kernel cont: 0x8025660d
         user: 0x3bbc8838 0x3bb170d5 0x3bb11643 0
         user   time in thread:     0.721651 seconds
         system time in thread:     0.000000 seconds
    thread 0x276 TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800b0655
         user: 0x3bbc8a84 0x3bbc8881 0x312fb561 0x312f9c81 0x31264541 0x312a81ab 0x20a80f 0x3bc41c5d 0x3bc41bcf 0x3bc3fcd0
         user   time in thread:     1.620126 seconds
         system time in thread:     0.000000 seconds
    thread 0x28a TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800b0655
         user: 0x3bbc8a84 0x3bbc8881 0x312fb561 0x312f9c81 0x31264541 0x31264323 0x3a284993 0x3bc41c5d 0x3bc41bcf 0x3bc3fcd0
         user   time in thread:     2.280643 seconds
         system time in thread:     0.000000 seconds
    thread 0x2d3 TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800b0655
         user: 0x3bbc8a84 0x3bbc8881 0x312fb561 0x312f9c81 0x31264541 0x312a81ab 0x1d2eb11 0x3bc41c5d 0x3bc41bcf 0x3bc3fcd0
         user   time in thread:     0.002442 seconds
         system time in thread:     0.000000 seconds
    thread 0x1673 TH_WAIT 0xacbf8140
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x80ae22e5
         user: 0x3bbdbc7c 0x3bc3fe0b 0x3bc3fcc4
         user   time in thread:     0.302431 seconds
         system time in thread:     0.000000 seconds
    thread 0x1db8 TH_WAIT 0x940b4a40
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x80ae22e5
         user: 0x3bbdbc7c 0x3bc3fe0b 0x3bc3fcc4
         user   time in thread:     0.005145 seconds
         system time in thread:     0.000000 seconds
    thread 0x1dc2 TH_WAIT 0xa5bc8f40
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x80ae22e5
         user: 0x3bbdbc7c 0x3bc3fe0b 0x3bc3fcc4
         user   time in thread:     0.009007 seconds
         system time in thread:     0.000000 seconds
    Process 15 info:
         resident memory bytes:  4517888
         page faults:                3141
         page-ins:                    494
         copy-on-write faults:        150
         times throttled:               0
         times did throttle:            4
         user   time in task:           1.144801 seconds
         system time in task:           0.000000 seconds
    Process 15 binary images:
    0x2be95000 <f15a81a9454d33b1b0db274777ecf386>
    0xee000 <23927f275eb33de4a048eaa3103459e2>
    Process 15 wifid threads:
    thread 0x1e9 TH_WAIT 0
         thread priority:               31
         Base thread priority:          31
         thread sched flags:     none
         kernel cont: 0x800b0655
         user: 0x3bbc8a84 0x3bbc8881 0x312fb561 0x312f9cc7 0x31264541 0x312a81ab 0x142251 0x3bb24ab7
         user   time in thread:     0.057682 seconds
         system time in thread:     0.000000 seconds
    thread 0x298 TH_WAIT 0
         thread priority:               33
         Base thread priority:          33
         thread sched flags:     none
         kernel cont: 0x8025660d
         user: 0x3bbc8838 0x3bb170d5 0x3bb11643 0
         user   time in thread:     0.020125 seconds

    It is normal debugging information that is sent to Apple. It does not mean your phone is being monitored, other than for problems that Apple might like to solve. No personal information is sent, as you can see from the information you posted.
    If you don't want to send diagnostic information to Apple you can turn that off completely:
    Settings > General > About > Diagnostics & Usage > choose Don't Send.
    More information: http://www.apple.com/pr/library/2011/04/27Apple-Q-A-on-Location-Data.html

  • Error message 0xc000021a - every day after a boot of notebook W8

    Hi,
    I have the following issue. I have a Windows 8 notebook from MSI. Since the last couple of days, I'm facing an issue when I try to boot the notenbook. It returns with a 0c000021A error. When I open SrtTrail.txt, I see the following message:
    Test Performed:
    Name: Check for updates
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms
    Test Performed:
    Name: System disk test
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms
    Test Performed:
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 172 ms
    Test Performed:
    Name: Disk metadata test
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms
    Test Performed:
    Name: Target OS test
    Result: Completed successfully. Error code =  0x0
    Time taken = 641 ms
    Test Performed:
    Name: Volume content check
    Result: Completed successfully. Error code =  0x0
    Time taken = 281 ms
    Test Performed:
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms
    Test Performed:
    Name: System boot log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms
    Test Performed:
    Name: Event log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 47 ms
    Test Performed:
    Name: Internal state check
    Result: Completed successfully. Error code =  0x0
    Time taken = 15 ms
    Test Performed:
    Name: Boot status test
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms
    Test Performed:
    Name: Setup state check
    Result: Completed successfully. Error code =  0x0
    Time taken = 188 ms
    Test Performed:
    Name: Registry hives test
    Result: Completed successfully. Error code =  0x0
    Time taken = 1828 ms
    Test Performed:
    Name: Windows boot log diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms
    Test Performed:
    Name: Bugcheck analysis
    Result: Completed successfully. Error code =  0x0
    Time taken = 516 ms
    Root cause found:
    Bugcheck c000021a. Parameters = 0xfffff8a003f9b850, 0xffffffffc0000428, 0xfffff8a0003bb610, 0x0.
    Boot critical file  is corrupt.
    I have been looking for a long time to find a proper solution, but from what I found on the internet, there are so many different approaches and I don't know whether the provided solutions have worked or not. I did a disk clean up, I have no other log files
    present. If you need more details for further analysis, please let me know. Currently, I'm using the DISM utility to get the notebook booted, but I prefer a proper start up from my notebook.
    Any help is really appreciated.

    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck C000021A, {fffff8a003e1cda0, ffffffffc0000428, fffff8a00017dbb0, 0}
    ----- ETW minidump data unavailable-----
    Probably caused by : ntkrnlmp.exe ( nt!NtSetSystemPowerState+878 )
    Followup: MachineOwner
    6: kd> !analyze -v
    * Bugcheck Analysis *
    WINLOGON_FATAL_ERROR (c000021a)
    The Winlogon process terminated unexpectedly.
    Arguments:
    Arg1: fffff8a003e1cda0, String that identifies the problem.
    Arg2: ffffffffc0000428, Error Code.
    Arg3: fffff8a00017dbb0
    Arg4: 0000000000000000
    Debugging Details:
    ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
    EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
    EXCEPTION_PARAMETER1: fffff8a003e1cda0
    EXCEPTION_PARAMETER2: ffffffffc0000428
    EXCEPTION_PARAMETER3: fffff8a00017dbb0
    EXCEPTION_PARAMETER4: 0
    ADDITIONAL_DEBUG_TEXT: Verification of a KnownDLL failed.
    BUGCHECK_STR: 0xc000021a_c0000428_user32.dll_HASH_INVALID
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: smss.exe
    CURRENT_IRQL: 0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER: from fffff8030a39048e to fffff8030a079540
    STACK_TEXT:
    fffff880`039436e8 fffff803`0a39048e : 00000000`0000004c 00000000`c000021a fffff880`0120d400 fffffa80`0dd1d130 : nt!KeBugCheckEx
    fffff880`039436f0 fffff803`0a381aec : 00000000`00000001 00000000`00000002 ffffffff`80000110 00000000`00000002 : nt!PopGracefulShutdown+0x29a
    fffff880`03943730 fffff803`0a078553 : fffffa80`06bf5900 00000000`00000000 00000000`c0000004 fffff880`03943901 : nt!NtSetSystemPowerState+0x878
    fffff880`03943870 fffff803`0a07d730 : fffff803`0a626fcf 00000000`00000001 00000000`00000000 fffffa80`00000004 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`03943a08 fffff803`0a626fcf : 00000000`00000001 00000000`00000000 fffffa80`00000004 fffffa80`0bf07ce0 : nt!KiServiceLinkage
    fffff880`03943a10 fffff803`0a4fb833 : fffff8a0`00027010 fffff803`0a45f2bc 00000000`00000000 fffff8a0`000604a8 : nt! ?? ::NNGAKEGL::`string'+0x41aa9
    fffff880`03943ad0 fffff803`0a04e860 : fffffa80`06bf5900 00000000`00000000 00000000`00000002 fffff803`0a082dbc : nt!PopPolicyWorkerAction+0x63
    fffff880`03943b40 fffff803`0a0b7411 : fffff803`00000002 fffff803`0a04e7a0 fffff803`0a2b8620 fffff803`0a082d00 : nt!PopPolicyWorkerThread+0xc0
    fffff880`03943b80 fffff803`0a04c075 : 00000000`10000000 00000000`00000080 fffff803`0a0b72d0 fffffa80`06bf5900 : nt!ExpWorkerThread+0x142
    fffff880`03943c10 fffff803`0a1003b6 : fffff803`0a317180 fffffa80`06bf5900 fffff803`0a371880 fffffa80`06996040 : nt!PspSystemThreadStartup+0x59
    fffff880`03943c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!NtSetSystemPowerState+878
    fffff803`0a381aec cc int 3
    SYMBOL_STACK_INDEX: 2
    SYMBOL_NAME: nt!NtSetSystemPowerState+878
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 536464f4
    IMAGE_VERSION: 6.2.9200.16912
    BUCKET_ID_FUNC_OFFSET: 878
    FAILURE_BUCKET_ID: 0xc000021a_c0000428_user32.dll_HASH_INVALID_nt!NtSetSystemPowerState
    BUCKET_ID: 0xc000021a_c0000428_user32.dll_HASH_INVALID_nt!NtSetSystemPowerState
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:0xc000021a_c0000428_user32.dll_hash_invalid_nt!ntsetsystempowerstate
    FAILURE_ID_HASH: {4c1cb833-8749-f823-0b1e-7f7a668864ad}
    Followup: MachineOwner
    adn this shows 6: kd> db fffff8a003e1cda0
    fffff8a0`03e1cda0 56 65 72 69 66 69 63 61-74 69 6f 6e 20 6f 66 20 Verification of
    fffff8a0`03e1cdb0 61 20 4b 6e 6f 77 6e 44-4c 4c 20 66 61 69 6c 65 a KnownDLL faile
    fffff8a0`03e1cdc0 64 2e 00 00 20 02 00 00-01 01 00 00 00 00 00 05 d... ...........
    fffff8a0`03e1cdd0 04 01 04 03 4e 74 46 73-02 00 00 00 00 00 14 00 ....NtFs........
    fffff8a0`03e1cde0 20 ea d1 03 a0 f8 ff ff-00 00 00 00 00 00 00 00 ...............
    fffff8a0`03e1cdf0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
    fffff8a0`03e1ce00 38 ce 00 00 00 00 02 00-20 9b e3 03 a0 f8 ff ff 8....... .......
    fffff8a0`03e1ce10 04 01 0c 03 46 49 63 73-30 00 43 00 30 00 34 00 ....FIcs0.C.0.4.
    6: kd> da fffff8a00017dbb0
    fffff8a0`0017dbb0 "user32.dll"
    Hi, the dump analysis indicates that this issue is probably caused by ntkrnlmp.exe a NT Kernel & System file, and deep analysis shows that the error is related with user32.dll file, invalid hash, this file must be corrupted, or might be placed with
    other files due to some 3 rd part software installation, or even virus infection, I suggest you refer to this link to fix the dll file, replace the file with a right copy (this is an old link, but some solutions are also useful in Windows 8.1)
    http://support.microsoft.com/kb/142676
    Yolanda Zhu
    TechNet Community Support

  • Regarding generic delta.

    does any sap bw gurus know the answer to my doubt.
    i have created 3 views from mm tables (EBAN,MSEG,MKPF,GLPCA) AND FROM THESE 3 views i have created 3 generic data sorses in r/3 dev server and transported to r/3 quality server and loaded from r/3 qlty server to ods with full update mode in infopackage.
    now i want to load delta records for those geeric data sorses, what is the procedure. i have not selected the delta option while creation of data sorses but loaded into ODS with full update.now i want to get delta records, what is the process?
    Suppose i have selected generic delta and given some field to get delta records in r/3 dev server, does it effect in r/3 qualty server or do i need to transport same recquest or new recquest for delta from dev to quality server?
    this is very very urgent pls. points assigned.

    Hi,
    ODS may not let you load deltas if there are Full loads already loaded. So either you have to delete them or make them into Full repair using FM RSSM_SET_REPAIR_FULL_FLAG.
    This you can decide after talking to users, if they are ok with the data unavailability during the reload, you can delete these data.
    Then perform the changes (delta DS) in the DEV and transport it to QUAL.
    Then the usual procedure, replicate in BW, perform init load and start deltas.
    Hope this helps.
    Thanks,
    JituK

  • [SOLVED]Installing it87 driver for lm_sensors support

    Hello,
    I've done much research on how to properly install an update it87 driver that could make 0x8620 work.
    I ran sensors-detect and ran into this:
    # sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
    # System: Gigabyte Technology Co., Ltd. Z97X-Gaming 7
    This program will help you determine which kernel modules you need
    to load to use lm_sensors most effectively. It is generally safe
    and recommended to accept the default answers to all questions,
    unless you know what you're doing.
    Some south bridges, CPUs or memory controllers contain embedded sensors.
    Do you want to scan for them? This is totally safe. (YES/no): y
    Module cpuid loaded successfully.
    Silicon Integrated Systems SIS5595... No
    VIA VT82C686 Integrated Sensors... No
    VIA VT8231 Integrated Sensors... No
    AMD K8 thermal sensors... No
    AMD Family 10h thermal sensors... No
    AMD Family 11h thermal sensors... No
    AMD Family 12h and 14h thermal sensors... No
    AMD Family 15h thermal sensors... No
    AMD Family 15h power sensors... No
    AMD Family 16h power sensors... No
    Intel digital thermal sensor... Success!
    (driver `coretemp')
    Intel AMB FB-DIMM thermal sensor... No
    VIA C7 thermal sensor... No
    VIA Nano thermal sensor... No
    Some Super I/O chips contain embedded sensors. We have to write to
    standard I/O ports to probe them. This is usually safe.
    Do you want to scan for Super I/O sensors? (YES/no): y
    Probing for Super-I/O at 0x2e/0x2f
    Trying family `National Semiconductor/ITE'... No
    Trying family `SMSC'... No
    Trying family `VIA/Winbond/Nuvoton/Fintek'... No
    Trying family `ITE'... Yes
    Found unknown chip with ID 0x8620
    Probing for Super-I/O at 0x4e/0x4f
    Trying family `National Semiconductor/ITE'... No
    Trying family `SMSC'... No
    Trying family `VIA/Winbond/Nuvoton/Fintek'... No
    Trying family `ITE'... No
    Some systems (mainly servers) implement IPMI, a set of common interfaces
    through which system health data may be retrieved, amongst other things.
    We first try to get the information from SMBIOS. If we don't find it
    there, we have to read from arbitrary I/O ports to probe for such
    interfaces. This is normally safe. Do you want to scan for IPMI
    interfaces? (YES/no): y
    # DMI data unavailable, please consider installing dmidecode 2.7
    # or later for better results.
    Probing for `IPMI BMC KCS' at 0xca0... No
    Probing for `IPMI BMC SMIC' at 0xca8... No
    Some hardware monitoring chips are accessible through the ISA I/O ports.
    We have to write to arbitrary I/O ports to probe them. This is usually
    safe though. Yes, you do have ISA I/O ports even if you do not have any
    ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
    Probing for `National Semiconductor LM78' at 0x290... No
    Probing for `National Semiconductor LM79' at 0x290... No
    Probing for `Winbond W83781D' at 0x290... No
    Probing for `Winbond W83782D' at 0x290... No
    Lastly, we can probe the I2C/SMBus adapters for connected hardware
    monitoring devices. This is the most risky part, and while it works
    reasonably well on most systems, it has been reported to cause trouble
    on some systems.
    Do you want to probe the I2C/SMBus adapters now? (YES/no): y
    Found unknown SMBus adapter 8086:8ca2 at 0000:00:1f.3.
    Sorry, no supported PCI bus adapters found.
    Module i2c-dev loaded successfully.
    Next adapter: i915 gmbus ssc (i2c-0)
    Do you want to scan it? (yes/NO/selectively): y
    Next adapter: i915 gmbus vga (i2c-1)
    Do you want to scan it? (yes/NO/selectively): y
    Next adapter: i915 gmbus panel (i2c-2)
    Do you want to scan it? (yes/NO/selectively): y
    Next adapter: i915 gmbus dpc (i2c-3)
    Do you want to scan it? (yes/NO/selectively): y
    Next adapter: i915 gmbus dpb (i2c-4)
    Do you want to scan it? (yes/NO/selectively): y
    Next adapter: i915 gmbus dpd (i2c-5)
    Do you want to scan it? (yes/NO/selectively): y
    Now follows a summary of the probes I have just done.
    Just press ENTER to continue:
    Driver `coretemp':
    * Chip `Intel digital thermal sensor' (confidence: 9)
    Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
    Created symlink from /etc/systemd/system/multi-user.target.wants/lm_sensors.service to /usr/lib/systemd/system/lm_sensors.service.
    Unloading i2c-dev... OK
    Unloading cpuid... OK
    So I did some research and found that this was updated and available as a potential driver for my MOBO:
    http://www.lm-sensors.org/wiki/Devices
    You will see the IT8620E which covers the unknown chip lm_sensors found.
    I downloaded the file, extracted it and tried to do a
    sudo make
    but I ran into an error because it was looking for
    KERNEL_BUILD := /usr/src/linux-headers-$(TARGET)
    which is NOT in that directory. I installed the linux-headers and saw that it adds files to
    /lib/modules/3.19.3-3-ARCH
    . I modified the Makefile and it got past that part but it ran into another error during
    make install
    After much frustration I looked and saw 
    usr/lib/modules/3.19.3-3-ARCH/kernel/drivers/hwmon/it87.ko.gz
    so now I'm questioning if I even need to install this driver or if I need to update it. Is there a way to learn more about these drivers that come in the linux package?
    I can't find anything concrete on how to make this work. I'm just trying to add my fan speeds and other junk to my conky!
    Edit:
    modinfo it87 gave me this result:
    filename: /lib/modules/3.19.3-3-ARCH/kernel/drivers/hwmon/it87.ko.gz
    license: GPL
    description: IT8705F/IT871xF/IT872xF hardware monitoring driver
    author: Chris Gauthron, Jean Delvare <[email protected]>
    depends: hwmon-vid,hwmon
    intree: Y
    vermagic: 3.19.3-3-ARCH SMP preempt mod_unload modversions
    parm: force_id:Override the detected device ID (ushort)
    parm: update_vbat:Update vbat if set else return powerup value (bool)
    parm: fix_pwm_polarity:Force PWM polarity to active high (DANGEROUS) (bool)
    So, this tells me that this driver does not cover 8620.
    Last edited by SirMyztiq (2015-04-10 06:23:31)

    Update:
    I believe after some researching and actually going for it that I managed to install the it87 test driver.
    I modified the Makefile on this line:
    KERNEL_BUILD := /lib/modules/$(TARGET)/build
    And when it failed on this line:
    SYSTEM_MAP := /boot/System.map-$(TARGET)
    I did:
    sudo cp /proc/kallsyms /boot/System.map-`uname -r`
    Because Arch doesn't put this file there because it isn't needed to boot...I think.
    Either way it finished and I was able to use the lm_sensors.

Maybe you are looking for