Jump to content

ASRock Pro4-M

kenrel panic

  • Please log in to reply
20 replies to this topic

#21
adrian95

adrian95

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 135 posts
  • Gender:Male
  • Location:Illinois
8/15/12 11:40:47.506 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:47.509 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:48.041 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:48.128 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:48.537 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.052 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.054 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.520 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.624 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:26.111 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 10:02:37.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700
8/16/12 10:13:48.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700
8/16/12 10:15:45.501 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:15:45.503 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:15:46.154 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:17:58.477 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:17:58.479 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:17:59.663 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:29:50.480 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:29:50.482 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 12:27:30.000 PM kernel[0]: RTC: Maintenance 2012/8/16 15:26:14, sleep 2012/8/16 14:53:08
8/16/12 2:16:51.000 PM kernel[0]: RTC: Maintenance 2012/8/16 17:15:35, sleep 2012/8/16 15:27:53
8/16/12 4:06:13.000 PM kernel[0]: RTC: Maintenance 2012/8/16 19:04:57, sleep 2012/8/16 17:17:49
8/16/12 5:55:34.000 PM kernel[0]: RTC: Maintenance 2012/8/16 20:54:18, sleep 2012/8/16 19:06:36
8/16/12 7:44:55.000 PM kernel[0]: RTC: Maintenance 2012/8/16 22:43:39, sleep 2012/8/16 20:55:57
8/16/12 9:34:16.000 PM kernel[0]: RTC: Maintenance 2012/8/17 00:33:00, sleep 2012/8/16 22:45:17
8/16/12 10:34:25.638 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:34:25.639 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:34:26.285 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1

Here is some more from logs (I've been monitoring them):
8/15/12 11:40:47.506 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:47.509 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:48.041 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:48.128 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/15/12 11:40:48.537 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.052 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.054 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.520 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:25.624 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 8:41:26.111 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data
8/16/12 10:02:37.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700
8/16/12 10:13:48.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700
8/16/12 10:15:45.501 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:15:45.503 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:15:46.154 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:17:58.477 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:17:58.479 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:17:59.663 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:29:50.480 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:29:50.482 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 12:27:30.000 PM kernel[0]: RTC: Maintenance 2012/8/16 15:26:14, sleep 2012/8/16 14:53:08
8/16/12 2:16:51.000 PM kernel[0]: RTC: Maintenance 2012/8/16 17:15:35, sleep 2012/8/16 15:27:53
8/16/12 4:06:13.000 PM kernel[0]: RTC: Maintenance 2012/8/16 19:04:57, sleep 2012/8/16 17:17:49
8/16/12 5:55:34.000 PM kernel[0]: RTC: Maintenance 2012/8/16 20:54:18, sleep 2012/8/16 19:06:36
8/16/12 7:44:55.000 PM kernel[0]: RTC: Maintenance 2012/8/16 22:43:39, sleep 2012/8/16 20:55:57
8/16/12 9:34:16.000 PM kernel[0]: RTC: Maintenance 2012/8/17 00:33:00, sleep 2012/8/16 22:45:17
8/16/12 10:34:25.638 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:34:25.639 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
8/16/12 10:34:26.285 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1

8/16/12 8:52:51.842 AM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fbdc490f1e0> Thu Aug 16 09:25:26 2012 ART (approx)
8/16/12 8:52:51.842 AM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fbdc490f1e0> Thu Aug 16 09:25:26 2012 ART (approx)
8/16/12 10:10:33.201 AM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fadaa43bc30> Thu Aug 16 11:02:39 2012 ART (approx)
8/16/12 10:10:33.201 AM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fadaa43bc30> Thu Aug 16 11:02:39 2012 ART (approx)
8/16/12 10:14:15.590 AM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fbfec90c960> Thu Aug 16 11:13:50 2012 ART (approx)
8/16/12 10:14:15.590 AM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fbfec90c960> Thu Aug 16 11:13:50 2012 ART (approx)
8/16/12 10:14:23.689 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:15:45.000 AM kernel[0]: Wake reason: GLAN XHC
8/16/12 10:15:45.000 AM kernel[0]: The USB device iMate, USB To ADB Adaptor (Port 1 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
8/16/12 10:15:45.074 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:15:49.095 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:15:50.304 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:16:31.165 AM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fbfec910a30> Thu Aug 16 11:13:50 2012 ART (approx)
8/16/12 10:16:31.165 AM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fbfec910a30> Thu Aug 16 11:13:50 2012 ART (approx)
8/16/12 10:17:58.000 AM kernel[0]: Wake reason: power-button XHC (User)
8/16/12 10:17:58.000 AM kernel[0]: The USB device iMate, USB To ADB Adaptor (Port 1 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
8/16/12 10:17:58.136 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:17:58.160 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:18:02.120 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:28:20.344 AM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7f9c20602c00> Thu Aug 16 11:27:20 2012 ART (approx)
8/16/12 10:28:20.344 AM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7f9c20602c00> Thu Aug 16 11:27:20 2012 ART (approx)
8/16/12 10:28:26.469 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:29:50.027 AM com.apple.backupd-helper[302]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.
8/16/12 10:29:50.000 AM kernel[0]: Wake reason: GLAN XHC
8/16/12 10:29:50.000 AM kernel[0]: The USB device iMate, USB To ADB Adaptor (Port 1 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)
8/16/12 11:53:03.498 AM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7f9c20608d30> Thu Aug 16 12:27:21 2012 ART (approx)
8/16/12 11:53:03.498 AM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7f9c20608d30> Thu Aug 16 12:27:21 2012 ART (approx)
8/16/12 11:53:05.965 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 12:27:30.000 PM kernel[0]: Wake reason: RTC (Alarm)
8/16/12 12:27:50.328 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 2:16:51.000 PM kernel[0]: Wake reason: RTC (Alarm)
8/16/12 2:17:45.855 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 4:06:13.000 PM kernel[0]: Wake reason: RTC (Alarm)
8/16/12 4:06:33.174 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 5:55:34.000 PM kernel[0]: Wake reason: RTC (Alarm)
8/16/12 5:55:55.218 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 7:44:55.000 PM kernel[0]: Wake reason: RTC (Alarm)
8/16/12 7:45:15.281 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 9:34:16.000 PM kernel[0]: Wake reason: RTC (Alarm)
8/16/12 9:34:37.321 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com.
8/16/12 10:34:25.000 PM kernel[0]: Wake reason: GLAN EHC1
8/16/12 10:34:25.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2)
8/16/12 10:34:25.000 PM kernel[0]: The USB device USB Optical Mouse (Port 6 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   Web hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy