VOD down every night

I work nights and come home hoping to watch a little TV and then go to bed. Unfortunately when I get home it's mostly infomercials so I rely heavily on VOD. 5 nights out of 7 VOD is not working. I reset everything and still not working. When I go online I always get the message that VOD is down in my area and will be returned usually in the morning. Fat lot of good that does me...I'm sleeping then. I am seriously considering returning to Comcast (I hate Comcast) even tho the $$ is more but if I'm not getting VOD what the hell am I paying for? Please, please fix this Verizon. I've been singing your praises to everyone and I work in a casino....I talk to a LOT of people. Please don't make me go back to Comcast (did I mention I hate Comcast??).

I hate Comcast too - one of the happiest days of my life was calling them to terminate service because I switched to FiOS.
I don't do a lot of VOD myself (especially late night) but haven't seen this problem. I'm curious where you are located and if you have tried unplugging the STB when the problem is happening and the plugging it back in. That can solve some problems... not that you should have to do this, but I am just curious if you tried and that did or did not fix it. That's often my first step at troubleshooting.
Good luck.

Similar Messages

My imac (intel core i5, OS 10.10.1) shuts down every night and will not "wake up" next morning -- it never used to do that -- if I hold down the start button more than twice for many seconds, then it will finally boot up and works fine all day – I've

my imac (intel core i5, OS 10.10.1) shuts down every night and will not "wake up" next morning -- it never used to do that -- if I hold down the start button more than twice for many seconds, then it will finally boot up and works fine all day – I’ve tried shutting it down and unplugging it, and that does not work -- I’ve run disk utilities checked permissions, and run anti-virus and get no adverse results – I cannot figure out what is different that causes this problem

From previous experience 3 indicates a shutdown initiated by the SMC (System Management Controller) — hardware responsible for many low-level functions including power, sleep, lights, and fan activity.
Try resetting it:
Power or other problems related to unexpected system sleep, shutdown, lights or fans call for an SMC reset. Read all the steps.
Before Resetting the SMC
Try each of the following steps in this order before you reset the SMC. Test the issue after completing each troubleshooting step to determine if the issue still occurs.
Press Command + Option + Escape to force quit any application that is not responding.
Put your Mac to sleep by choosing the Apple () menu from the upper-left menu bar and then choosing Sleep. Wake the computer after it has gone to sleep.
Restart your Mac by choosing the Apple () menu from the upper-left menu bar and then choosing Restart.
Shut down your Mac by choosing the Apple () menu from the upper-left menu bar and then choosing Shut Down.
Resetting the SMC for Mac Pro, Intel-based iMac, Intel-based Mac mini, or Intel-based Xserve
Shut down the computer.
Unplug the computer's power cord.
Wait fifteen seconds.
Attach the computer's power cord.
Wait five seconds, then press the power button to turn on the computer.

SHOULD MACINTOSH COMPUTERS BE SHUT DOWN EVERY NIGHT?

Should I shut down my iMac every night?

My Mac's sleep 24-7 and I only shut them down when I'm gone for more than a day or two.
Mac's can easily go beyond 45 days without being shutdown or restarted.

Should I shut down my iPhone every night? Sleep vs shut-down.

Hi, If I never use my phone during the night, should I shut it right down every night? How much energy is used when the iPhone "sleeps" for 8 hours?
Thanks for your thoughts on this!

My battery will loose about 10% (polling email every hour, and push IM left on) over 7.5 hours.
You can leave it on and I think Apple intend people do, because otherwise alarms will not go off, I use the alarms to wake me up The best option is to leave it on and plugged in.

Should I shut down my mac pro every night

Just purchase a Macbook Pro, should I shut it down every night?

leroydouglas wrote:
Never heard that advice before. The kb certainly does not say that.
Big difference from your statement compare ""Apple does not recommend leaving your portable plugged in all the time."
I think using the battery regularly is a better interpretation.
I would submit that is the way most people use their Portables, close the lid.
You absolutely misunderstood I referred to BOTH "on power AND in sleep mode"
     not to: "closing the lid ,... sleep mode"
Using the battery regularly can mean anything as a generalization.
That advice on parasitic charging is correct.   Which referres to BOTH in sleep AND on power...   not however to merely "in sleep mode"
There is no etrecheck for parasitic battery charging,   ..... NOR is there any such check for both:
1. fast discharges
3. low discharges
As such that battery information you provided above doesnt report bad abuse / misuse of a battery.
Nor does / can Etrecheck report on physical abuse of any macbook, logically.
Battery abuse / misuse is a type of physical abuse, chemistry of the battery abuse, however its internal.
I did not say the KB article said that,    what it says:
http://www.apple.com/batteries/notebooks.html
"Apple does not recommend leaving your portable plugged in all the time."
So, you misunderstood.
Apples recommendation refers to micro-cycling the battery and to parasitic charging in the above quote, that it doesnt elaborate on the specifics of same
is irrelevant.
The implication from same is exactly this
*If you don’t plan on using it for a few hours, turn it OFF (plugged in or otherwise) ..*You don’t want your Macbook both always plugged in AND in sleep mode       (When portable devices are charging and in the on or sleep position, the current that is drawn through the device is called the parasitic load and will alter the dynamics of charge cycle. Battery manufacturers advise against parasitic loading because it induces mini-cycles.)
Keeping batteries connected to a charger ensures that periodic "top-ups" do very minor but continuous damage to individual cells, hence Apples recommendation above:   “Apple does not recommend leaving your portable plugged in all the time”, …this is because “Li-ion degrades fastest at high state-of-charge”.
                    This is also the same reason new Apple notebooks are packaged with 50% charges and not 100%.
Contrary to popular myths about notebook batteries, there is protection circuitry in your Macbook and therefore you cannot ‘overcharge’ your notebook when plugged in and already fully charged.
However if you do not plan on using your notebook for several hours, turn it off (plugged in or otherwise), since you do not want your Macbook ‘both always plugged in and in sleep mode’.
A lot of battery experts call the use of Lithium-Ion cells the "80% Rule", meaning use 80% of the full charge or so, then recharge them for longer overall life. The only quantified damage done in the use of Lithium Ion batteries are instances where the internal notebook battery is “often drained very low”, this is bad general use of your notebook battery.
A person who has, for example, 300 charge cycles on their battery and is recharging at say 40% remaining of a 100% charge has a better battery condition state than, say, another person who has 300 charge cycles on their battery and is recharging at say 10-15% remaining on a 100% charge. DoD (depth of discharge) is much more important on the wear and tear on your Macbook’s battery than the count of charge cycles. There is no set “mile” or wear from a charge cycle in specific. Frequent high depth of discharge rates (draining the battery very low) on a Lithium battery will hasten the lowering of maximum battery capacity.
All batteries in any device are a consumable meant to be replaced eventually after much time, even under perfect use conditions.
If the massive amount of data that exists on lithium batteries were to be condensed into a simplex, helpful, and memorable bit of information it would be:
1. While realistically a bit impractical during normal everyday use, a lithium battery's longevity and its chemistry's health is most happy swinging back and forth between 20% and 85% charge roughly.
2. Do not purposefully drain your battery very low (10% and less), and do not keep them charged often or always high (100%).
3. Lithium batteries do not like the following:
A: Deep discharges, as meaning roughly 10% or less on a frequent basis.
B: Rapid discharges as referring to energy intensive gaming on battery on a frequent basis (in which case while gaming, if possible, do same on power rather than battery). This is a minor consideration.
C: Constant inflation, as meaning always or most often on charge, and certainly not both in sleep mode and on charge always or often.
From Apple on batteries:
http://www.apple.com/batteries/notebooks.html
http://support.apple.com/kb/HT1446
Bad discharging or battery use conditions:
Heat (due to environmental conditions or due to rapid discharges from heavy use = gaming / video editing)
Rapid discharging of the battery frequently causes chemical changes over time in the battery leading to decreased capacity and resistance of current flow.
The very worst use of your battery is often draining the battery very low, and worse still letting it remain in such a state.
*Most long-term rapid damage to the battery occurs from discharging it with high loading (gaming) conditions but paramount is avoiding deep and frequent low DOD (depths of discharge) in use.
Undesirable charging or charged conditions:
High perpetual SOC (state of charge), where the battery is always or very often connected to charge
Parasitic loading where the battery is both usually on and charging or worse both always charging and in sleep mode, since this induces mini-cycling of the battery.
Bad general handling conditions:
Temperature use conditions when either too hot (95F and above) or too cold (50F and below)
Storing your battery away with a low charge (40% and less) long-term.
Considerations:
Your battery is subject to chemical aging even if not in use. A Lithium battery is aging as soon as its made, regardless.
In a perfect (although impractical) situation, your lithium battery is best idealized swinging back and forth between 20 and 85% SOC (state of charge) roughly.
Further still how you discharge the battery is far more important than how it is either charged or stored short term.
Ultimately counting charge cycles is of little to no importance. Abuse in discharging (foremost), charging, and storing the battery and how it affects battery chemistry is important and not the ‘odometer’ reading, or cycle counts on the battery.
Everything boils down to battery chemistry long term, and not an arbitrary number, or cycle count.
Keep your macbook plugged in when near a socket since in the near end of long-term life, this is beneficial to the battery.

Does it "hurt" the timecapsule if i cut the power every night?

i use my timecapsule as a wlan rooter and do not want to have the wlan active over night. since there is no on/off i simply cut the power in the evening. do you think this will hurt the timecapsule over a longer period?
thanks

+1 ^^^
Wireless does not continuously transmit.. when you don't actually pass packets over wireless, the signal is just a short poll, every few seconds.. a burst to tell wireless devices I am here. The actual level of signal is extremely low..
If you are concerned about security.. WPA2 Personal with 20 character key.. full combo of upper, lower and digit alphanumeric.. will not be broken.
If you are concerned for safety.. the power rf output of the dect phone is 10x greater than wifi. The radio and communications signals in your house from mobile phone towers for instance could be greater.
If you are concerned for power and environment.. the actual standby power demand of the TC is around 8W. The problem is shutting it down every night produces expansion and contraction issues. Replacement of the TC faster than normal counteracts any benefit gained for power saved. But that is the point we don't know.. will it break or how fast. Hard to know.

I shut down my IPad 2 every night. So that sleep/ wake button has not corrected the touch screen problem. Any other suggestions? Thanks

I shut Down my IPad 2 every night, so that has not fixed the problem with the touch screen feature. Is their anything else that I can try? Thanks

You have already posted this morning and I assume that you are responding to someone elses's suggestion but from where .... I have no clue.
Go back to here and follow along. GrumpyGator made a couple of suggestions for you to try.
https://discussions.apple.com/message/20137619#20137619

HP LaserJet Pro 100 functioned printer M175nw cleaning every night

I have a
HP LaserJet Pro 100 multifunctionele kleurenprinter M175nw. Runs fine in a wireless network.
The printer is used some times but also a week not at all. After 15 min the printer goes into sleep mode and after two hours or so the device switches off except the green standby light for receiving new wireless jobs.
Problem i have is that nearby every night the printer runs with a lot of noise, in the middle of the night. It looks like he is cleaning the drums or turning the cartridges or the drum. It SOUNDS like he is prepairing for printing but there is no job at all. After a few minutes the device stops and goes back to sleep. I am doiing it also than.
Is this a service property of this machine and can i switch it off? It takes energy and wakes me up!

Hi @jeroegro,
I see that the printer is going into a cleaning mode in the evening and you would like to be able to turn this service off.
I can help you today.
I couldn't find any settings through the printers control panel to turn this service off.
Either turn the printer off manually or you can set the printer to power off after so many hours, through the menus.
Go to Setup, System Setup menu, (wrench button) Energy Settings, Auto Power Down, set the time.
Have a nice day!
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

Mac Mini/Mountain Lion sleeps but won't wake up (or crashes) every night.

Hi everybody,
I have a mid-2010 mac mini server on which I recently installed Mountain Lion 10.8.2 (without server stuff).
Every night, it stops responding. The led is on but the display is off and it does not respond to mouse/keyboard. I even tried remote desktop.
The only solution is the power button...
What I already did :
- Reset Pram/Nvram
- Reset SMC
I also took a look at the console and I found a message that is fired just before the machine stops responding.
---- DAY 1 ----
24/09/12 02:03:00,000 kernel[0]: Wake reason: GIGE (Network)
24/09/12 02:03:00,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
24/09/12 02:03:00,000 kernel[0]: Previous Sleep Cause: 5
24/09/12 02:03:01,004 hidd[54]: MultitouchHID: device bootloaded
24/09/12 02:03:01,000 kernel[0]: AppleBCM5701::selectMedium - autoselect, any duplex, flow control allowed
24/09/12 02:03:01,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0
24/09/12 02:03:01,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Wake reason GIGE - bonjour - service connect
24/09/12 02:03:01,141 configd[18]: network changed: v4(en0-:192.168.0.100) v6(en0-:fe80::224:d4ff:feb4:22f1) DNS- Proxy- SMB
24/09/12 02:03:01,146 mDNSResponder[46]: DeregisterInterface: Frequent transitions for interface en0 (192.168.0.100)
24/09/12 02:03:02,000 kernel[0]: Graphics suppressed 1944 ms
24/09/12 02:03:02,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug [79ed,2301,0de1,0300,41e1,0000]
24/09/12 02:03:02,599 configd[18]: network changed: v4(en0+:192.168.0.100) DNS+ Proxy+ SMB
24/09/12 02:03:02,607 mDNSResponder[46]: mDNS_RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:C62C:03FF:FE0C:F227)
24/09/12 02:03:02,608 mDNSResponder[46]: mDNS_RegisterInterface: Frequent transitions for interface en0 (192.168.0.100)
24/09/12 02:03:02,617 configd[18]: network changed: v4(en0:192.168.0.100) v6(en0+:fe80::224:d4ff:feb4:22f1) DNS! Proxy SMB
24/09/12 02:03:32,209 com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fe119e220d0> Mon Sep 24 02:07:26 2012 CEST (approx)
24/09/12 02:03:32,210 com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fe119e220d0> Mon Sep 24 02:07:26 2012 CEST (approx)
24/09/12 20:13:29,000 bootlog[0]: BOOT_TIME 1348510409 0
---- DAY 2 ----
24/09/12 23:24:09,000 kernel[0]: Wake reason: GIGE (Network)
24/09/12 23:24:09,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
24/09/12 23:24:09,000 kernel[0]: AirPort_Brcm43xx::checkInterfacePowerState: Check _pwrOffThreadCall!
24/09/12 23:24:09,000 kernel[0]: Previous Sleep Cause: 5
24/09/12 23:24:09,994 hidd[45]: MultitouchHID: device bootloaded
24/09/12 23:24:10,000 kernel[0]: AppleBCM5701::selectMedium - autoselect, any duplex, flow control allowed
24/09/12 23:24:10,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0
24/09/12 23:24:10,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Wake reason GIGE - bonjour - service connect
24/09/12 23:24:10,000 kernel[0]: Graphics suppressed 1135 ms
24/09/12 23:24:10,154 configd[17]: network changed: v4(en0-:192.168.0.100) v6(en0-:fe80::224:d4ff:feb4:22f1) DNS- Proxy- SMB
24/09/12 23:24:10,166 mDNSResponder[37]: DeregisterInterface: Frequent transitions for interface en0 (192.168.0.100)
24/09/12 23:24:11,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug [79ed,2301,0de1,0300,41e1,0000]
24/09/12 23:24:11,520 configd[17]: network changed: v4(en0+:192.168.0.100) DNS+ Proxy+ SMB
24/09/12 23:24:11,532 mDNSResponder[37]: mDNS_RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:C62C:03FF:FE0C:F227)
24/09/12 23:24:11,533 mDNSResponder[37]: mDNS_RegisterInterface: Frequent transitions for interface en0 (192.168.0.100)
24/09/12 23:24:11,543 configd[17]: network changed: v4(en0:192.168.0.100) v6(en0+:fe80::224:d4ff:feb4:22f1) DNS! Proxy SMB
24/09/12 23:24:40,684 com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fb5d1e11910> Mon Sep 24 21:41:51 2012 CEST (approx)
24/09/12 23:24:40,684 com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fb5d1e11910> Mon Sep 24 21:41:51 2012 CEST (approx)
25/09/12 19:03:47,000 bootlog[0]: BOOT_TIME 1348592627 0
---- DAY 3 ----
26/09/12 05:33:54,000 kernel[0]: Wake reason: RTC (Alarm)
26/09/12 05:33:54,000 kernel[0]: RTC: Maintenance 2012/9/26 03:33:53, sleep 2012/9/26 01:34:04
26/09/12 05:33:54,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
26/09/12 05:33:54,000 kernel[0]: AirPort_Brcm43xx::checkInterfacePowerState: Check _pwrOffThreadCall!
26/09/12 05:33:54,000 kernel[0]: Previous Sleep Cause: 5
26/09/12 05:33:54,000 kernel[0]: AppleBCM5701::selectMedium - autoselect, any duplex, flow control allowed
26/09/12 05:33:55,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0
26/09/12 05:33:55,175 hidd[46]: MultitouchHID: device bootloaded
26/09/12 05:33:56,000 kernel[0]: Graphics suppressed 2444 ms
26/09/12 05:33:56,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug [79ed,2301,0de1,0300,41e1,0000]
26/09/12 05:33:56,534 configd[17]: network changed: v4(en0-:192.168.0.100) v6(en0-:fe80::224:d4ff:feb4:22f1) DNS- Proxy- SMB
26/09/12 05:33:56,645 com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fafe2e16a80> Tue Sep 25 20:31:50 2012 CEST (approx)
26/09/12 05:33:56,646 com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fafe2e16a80> Tue Sep 25 20:31:50 2012 CEST (approx)
26/09/12 05:33:56,686 configd[17]: network changed: v4(en0+:192.168.0.100) v6(en0+:fe80::224:d4ff:feb4:22f1) DNS+ Proxy+ SMB
26/09/12 05:34:01,000 kernel[0]: Sandbox: sandboxd(671) deny mach-lookup com.apple.coresymbolicationd
26/09/12 19:04:50,000 bootlog[0]: BOOT_TIME 1348679090 0
Any clue ?

Hi, I'm quite interested by your issue, because i get the exact same one.
On my mini (late 2012), system doesn t wake up from sleep if it has slept for more than 1 hour.
In fact I get the exact same message as you get in your console.
When I try and wake up system before the programmed maintenance wakeup, it wakes up fine.
But as soon as this programmed time has passed, it just won t wake up, I have to force switch it off via the power button and restart it.
I have nothing plugged on my mini except : AC - Thunderbolt display, and LAN connected to my freebox.
Do you still have the issue or is it ok now for you ?
I'll try in the upcoming days to plug the freebox in the thunderbolt display's adapter instead of the macmini's rj45.

Re: Slow broadband every night 10pm-Midnight

I am experiencing very slow broadband every night from 10pm. I searched the forum and saw this post and notied it was marked as 'solved' Can you tell me what the problem is here and how to solve it? I
magnamundian wrote:
Subject says it all really, switched to BT around 1 month ago and every night between 10pm and Midnight my broadband slows to a speed that would make dial-up blush. After midnight things ramp back up to normal. I don't P2P and this situation is consistent regardless of whether I have used the broadband heavily during the day (Netflix) or not used the broadband at all (until I tried to use at 10pm), so I'm discounting any ideas of traffic shaping or limits.
BT Line/Speed Checker results (http://diagnostics.bt.com/speedtest/)
After a good 10 minutes wait (not the 45 seconds advertised) the Exchange > HomeHub test came back with... well nothing really, the nifty Exchange > House graphic disappeared (after 10 minutes) and I suppose the results page was due to appear but after another 10 minutes I was still looking at "transferring data from BT.com" in the bottom of my browser... If I manage to get it to complete the cycle later I'll post the result.
At all other times of day the broadband lives up to expectations. Any advise appreciated, we previous had no problems with BE Broadband except for dire connections to US/Japan Servers (Sony/Square Enix etc), which was pretty much a problem of insufficient bandwidth on their backbone network.
Additional information from BTHomeHub.home:
ADSL Line Status
Connection information
Line state:
Connected
Connection time:
9 days, 18:20:04
Downstream:
20,609 Kbps
Upstream:
1,276 Kbps
ADSL settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
2.1 dB / 6.8 dB
Line attenuation (Down/Up):
27.5 dB / 16.6 dB
Output power (Down/Up):
0.0 dBm / 12.6 dBm
FEC Events (Down/Up):
1086302352 / 0
CRC Events (Down/Up):
3453520 / 1589
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
Loss of Link (Remote):
0
HEC Errors (Down/Up):
65406711 / 1420
Error Seconds (Local/Remote):
0 / 364
t is not clear to me what to do from the contents of this thread. Thanks.
magnamundian wrote:
Subject says it all really, switched to BT around 1 month ago and every night between 10pm and Midnight my broadband slows to a speed that would make dial-up blush. After midnight things ramp back up to normal. I don't P2P and this situation is consistent regardless of whether I have used the broadband heavily during the day (Netflix) or not used the broadband at all (until I tried to use at 10pm), so I'm discounting any ideas of traffic shaping or limits.
BT Line/Speed Checker results (http://diagnostics.bt.com/speedtest/)
After a good 10 minutes wait (not the 45 seconds advertised) the Exchange > HomeHub test came back with... well nothing really, the nifty Exchange > House graphic disappeared (after 10 minutes) and I suppose the results page was due to appear but after another 10 minutes I was still looking at "transferring data from BT.com" in the bottom of my browser... If I manage to get it to complete the cycle later I'll post the result.
At all other times of day the broadband lives up to expectations. Any advise appreciated, we previous had no problems with BE Broadband except for dire connections to US/Japan Servers (Sony/Square Enix etc), which was pretty much a problem of insufficient bandwidth on their backbone network.
Additional information from BTHomeHub.home:
ADSL Line Status
Connection information
Line state:
Connected
Connection time:
9 days, 18:20:04
Downstream:
20,609 Kbps
Upstream:
1,276 Kbps
ADSL settings
VPI/VCI:
0/38
Type:
PPPoA
Modulation:
G.992.5 Annex A
Latency type:
Interleaved
Noise margin (Down/Up):
2.1 dB / 6.8 dB
Line attenuation (Down/Up):
27.5 dB / 16.6 dB
Output power (Down/Up):
0.0 dBm / 12.6 dBm
FEC Events (Down/Up):
1086302352 / 0
CRC Events (Down/Up):
3453520 / 1589
Loss of Framing (Local/Remote):
0 / 0
Loss of Signal (Local/Remote):
0 / 0
Loss of Power (Local/Remote):
0 / 0
Loss of Link (Remote):
0
HEC Errors (Down/Up):
65406711 / 1420
Error Seconds (Local/Remote):
0 / 364

A "lay" explanation is this.
As IMJ has stated, at night the noise margin is dropping to a level whereby it becomes difficult for the DSL to bitload the data into the ADSL spectrum without undue error correction and bitswapping, and often increased error rate.
This situation tends to throttle down throughput .... and if it got worse, which clearly it isn't doing, it's just staying at a poor level .... the modem would drop the connection, and renegotiate .... and come back with target margin, at which juncture it would bitload and throughput would return to normal.
So what IMJ is saying is ... if it doesn;t drop and continues to hobble along .... force a drop, or reset it, and it will come back as if it had dropped by the modem forcing a drop.
In the end DLM will hopefully get hold of the situation and set the line parameters in a fashion which will sustain a connection and bitload properly 24 hours a day .... but sometimes it needs help, and especially if it didn't linetrain properly.
If it continues manual intervention is useful to set the noise margin accordingly until the line has re-trained.
Resetting the hub or modem is not a good idea with DSL, however in this instance if an automatic cure is not forthcoming, it is the ONLY time I would advocate a router reset, especially at night, when margin is depleted.

Skype 7.3 crashing around same time every night

Skype has been crashing every night, right before I go to bed Skype.exe ends up consuming almost 2GB of memory for some reason, at around the same time every night, and there are constant errors that Skype is out of memory, and it eventually stops responding completely until I end the process.
Running Windows 7 64bit with the latest updates installed, and Skype 7.3 latest build. Screenshot attached.
Attachments:
2015-04-14 02-13-29.jpg ‏23 KB

It really can't be any other software or hardware changes, as no changes have been made at all since the Skype update which caused this issue to start occuring.
As this particular system and user account are locked down and used almost exclusively just for Skype by an elderly retired person who runs no other applications, and has made no other changes to the system within that time that Skype has been updated and this issue has started occuring.
The Skype window remains open after they launch it in the morning, without minimizing it or using any other applications which could potentially interfere.
Considering the user is an elderly person with limited computer knowledge, when this issue occurs they are unable to recover the system themselves from its non responsive state, requiring intervention by us fix it on a nightly basis which is less than ideal for us, and them.

My Imac 24" Leopard wake me up every night at 01h00 AM!

Hi to all of you
my new Imac 24" (dec07 and 10.5.1) wake up or start by itself every night at 01h00 AM. As my desk is in my bedroom, it drives me crazy. The only solution found is to change the time setting (3h earlier) to perform this at 10h00pm.
No clue trough activity monitor. Just a guess about maintenance scripts.
Never had that on a Imac G5 1.8 Ghz, even with Leopard.
Have you seen same behaviour and got any idea?

Hi
Mac did again without any setting. Console log:
Feb 3 00:14:31 iMac24 loginwindow[7473]: Login Window Started Security Agent
Feb 3 00:14:43 iMac24 kernel[0]: AFPSleepWakeHandler: going to sleep
Feb 3 00:14:43 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 00:14:45: --- last message repeated 1 time ---
Feb 3 00:14:45 iMac24 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Feb 3 01:00:08 iMac24 kernel[0]: vmmon: powerStateDidChange flags=0x4 (state 2)
Feb 3 01:00:00 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 00:14:45 iMac24 kernel[0]: System Sleep
Feb 3 01:00:00 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 01:00:09 iMac24 kernel[0]: System Wake
Feb 3 01:00:09 iMac24 kernel[0]: vmmon: powerStateDidChange flags=0x82 (state 4)
Feb 3 01:00:01 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet8(7) Flags 8863 Family 2 172.16.241.1 has different family: 0
Feb 3 01:00:09 iMac24 kernel[0]: vmnet: VMNetDisconnect called for port 0x76f5000
Feb 3 01:00:01 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet1(8) Flags 8863 Family 2 172.16.92.1 has different family: 0
Feb 3 01:00:09 iMac24 kernel[0]: vmnet: bridge-en1: filter detached
Feb 3 01:00:01 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 01:00:09 iMac24 kernel[0]: vmnet: bridge-en1: down
Feb 3 01:00:01 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 01:00:09 iMac24 kernel[0]: vmnet: bridge-en1: detached
Feb 3 01:00:09 iMac24 kernel[0]: vmnet: Freeing hub at 0x7b8c800.
Feb 3 01:00:08 iMac24 configd[33]: rtmsg: error writing to routing socket
Feb 3 01:00:09 iMac24 kernel[0]: AppleYukon2: 00000000,00000000 sk98osx_dnet - recovering from missed interrupt
Feb 3 01:00:08 iMac24 configd[33]: rtmsg: error writing to routing socket
Feb 3 01:00:09 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet8(7) Flags 8863 Family 2 172.16.241.1 has different family: 0
Feb 3 01:00:09 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet1(8) Flags 8863 Family 2 172.16.92.1 has different family: 0
Feb 3 01:00:09 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 01:00:10: --- last message repeated 1 time ---
Feb 3 01:00:10 iMac24 kernel[0]: AppleUSBHub::setPowerState(0x5abf600, 2 -> 4) timed out after 10395 ms
Feb 3 01:00:10 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet8(7) Flags 8863 Family 2 172.16.241.1 has different family: 0
Feb 3 01:00:10 iMac24 kernel[0]: EIR is not supported.
Feb 3 01:00:10 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet1(8) Flags 8863 Family 2 172.16.92.1 has different family: 0
Feb 3 01:00:10 iMac24 kernel[0]: AFPSleepWakeHandler: waking up
Feb 3 01:00:10 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 01:00:12 iMac24 kernel[0]: SetCryptoKey T: len 16, idx 0
Feb 3 01:00:12 iMac24 kernel[0]: SetCryptoKey R: len 32, idx 1
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x7e4ca00.
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: VMNetConnect: returning port 0x7e4ca00
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: Allocated hub 0x622a000 for hubNum 0.
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f4:76:14
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: Hub 0
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: Port 0
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: bridge-en1: got dev 0x5cf4204
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: bridge-en1: wireless interface detected.
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: bridge-en1: up
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: bridge-en1: attached
Feb 3 01:00:12 iMac24 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x7e4ca00.
Feb 3 01:00:13 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet8(7) Flags 8863 Family 2 172.16.241.1 has different family: 0
Feb 3 01:00:13 iMac24 mDNSResponder[22]: getifaddrs ifa_netmask for vmnet1(8) Flags 8863 Family 2 172.16.92.1 has different family: 0
Feb 3 01:00:13 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 01:00:14: --- last message repeated 1 time ---
Feb 3 01:00:14 iMac24 kernel[0]: AppleYukon2: 00000000,00000000 sk98osx_dnet - recovering from missed interrupt
Feb 3 01:00:33 iMac24 kernel[0]: AFPSleepWakeHandler: going to sleep
Feb 3 01:00:33 iMac24 mDNSResponder[22]: SetupAddr invalid sa_family 0
Feb 3 01:00:55: --- last message repeated 1 time ---
Feb 3 01:00:55 iMac24 kernel[0]: BT_USB Controller: SuspendDevice(0) failed with error e0004051
Feb 3 01:00:55 iMac24 kernel[0]: BT_USB Controller: SuspendDevice(0) we are still connected to our hub so .. plain reset 0x5b1ff00
Feb 3 01:01:25 iMac24 kernel[0]: CSRUSBBluetoothHCIController::setPowerState(0x5b7b000, 1 -> 2) timed out after 50292 ms
Feb 3 09:08:48 localhost kernel[0]: npvhash=4095
Feb 3 09:08:45 localhost com.apple.launchctl.System[2]: fsck_hfs: Volume is journaled. No checking performed.
VMNET is very present. Perhaps, you will see at 01h00 something , thanks for help
JY

Sleep or shut down at night?

Hi, it just occurred to me that in summer with frequent lightning storms especially during the night, might it be a good idea to shut the computer down and disconnect the power adapter at night?
I tend to use the computer plugged in during the day, with short periods of battery use, and then at night I leave it plugged in and just close the lid. Even with old PC's I did this without a problem, but with my new MBP I don't want to take any chances!
Thanks,
Karen

karenr wrote:
Thanks.. re. shutting down at night, I thought there was an issue of wear and tear from starting up so often.. otherwise it would certainly be simpler to shut down and not worry about nighttime power surges.
I don't worry about wear and tear, because although technically it might be better to run your computer at full power 24/7 to avoid premature wear from thermal and power cycling, realistically nearly every Mac user either sleeps or shuts down their laptop at least once a day whether that's at night or merely to transport it (since it is a laptop after all) and therefore powering off is the norm, and it is not causing mass early laptop deaths.
We are also weighing leaving the computer plugged in versus the potential damage from a lightning strike, and we're saying the potential damage from sleeping or shutting down at night is assumed to be less severe than that of a direct lightning hit.
Re. sleeping the computer all night and draining the battery, I do that once a month to calibrate the battery, but isn't it recommended to not drain deeply too often?
You are right that is is recommended to not do deep discharges too often. But an overnight sleep does not drain the battery that far, maybe a few percent. What I didn't mention is that if your battery is new and fully charged, it will probably last around a week in sleep mode. One night off the charger isn't going to drain the battery unless, as I mentioned, it's an old battery with a fraction of its original capacity.

2012 Mac Mini shuts down at night on its own.

Every night for the last week my Mac mini shuts all the way down at night. I have not made any changes to this machine it just started doing this on its own. When I reboot in the morning it tells me that the computer has shut down and then gives the following for the error report:
Anonymous UUID: E6A1AB4A-69C1-7F0F-E205-C4588CCB015A
Thu Jul 3 11:51:44 2014
panic(cpu 0 caller 0xffffff8027ed1066): trying to interlock destroyed mutex (0xffffff80715265f0)
Backtrace (CPU 0), Frame : Return Address
0xffffff8211f33680 : 0xffffff8027e22fa9
0xffffff8211f33700 : 0xffffff8027ed1066
0xffffff8211f33710 : 0xffffff802816017c
0xffffff8211f33730 : 0xffffff802816140e
0xffffff8211f33770 : 0xffffff8027fffbd0
0xffffff8211f337c0 : 0xffffff8027fdc148
0xffffff8211f33810 : 0xffffff8027fdb710
0xffffff8211f33850 : 0xffffff8027fe27d0
0xffffff8211f33880 : 0xffffff8027fda63f
0xffffff8211f33940 : 0xffffff8028010c6b
0xffffff8211f339f0 : 0xffffff8028012888
0xffffff8211f33a60 : 0xffffff8027ffd23b
0xffffff8211f33ac0 : 0xffffff8027fd5bfb
0xffffff8211f33b40 : 0xffffff8027fd5554
0xffffff8211f33c00 : 0xffffff8027ff1422
0xffffff8211f33d80 : 0xffffff8027fe96dc
0xffffff8211f33f50 : 0xffffff8028240653
0xffffff8211f33fb0 : 0xffffff8027ef3c56
BSD process name corresponding to current thread: automount
Mac OS version:
13D65
Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide: 0x0000000027c00000
Kernel text base: 0xffffff8027e00000
System model name: Macmini6,1 (Mac-031AEE4D24BFF0B1)
System uptime in nanoseconds: 137393932698714
last loaded kext at 118189293439107: com.apple.driver.AppleUSBCDC 4.2.1b5 (addr 0xffffff7fa9ed3000, size 20480)
last unloaded kext at 116233964408599: com.apple.driver.AppleUSBCDC 4.2.1b5 (addr 0xffffff7fa9ed3000, size 16384)
loaded kexts:
com.symantec.kext.SymAPComm 12.6.1f9
com.symantec.kext.fw 5.3.1f9
com.symantec.kext.filesecurity 12.6.1f9
com.steelseries.BoardListener 8.28
com.logmein.driver.LogMeInSoundDriver 1.0.3
com.seagate.driver.PowSecLeafDriver_10_5 5.2.4
at.obdev.nke.LittleSnitch 4202
com.symantec.kext.ips 3.9.2f1
com.symantec.kext.pf 5.6.1f9
com.symantec.kext.internetSecurity 5.3.1f8
com.seagate.driver.PowSecDriverCore 5.2.4
com.apple.driver.AppleUSBCDC 4.2.1b5
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.4f1
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.AGPM 100.14.15
com.apple.driver.ApplePlatformEnabler 2.0.9d1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 2.6.1f2
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.driver.AppleMikeyDriver 2.6.1f2
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.driver.AppleIntelHD4000Graphics 8.2.6
com.apple.driver.AppleIntelFramebufferCapri 8.2.6
com.apple.iokit.IOUSBAttachedSCSI 1.0.5
com.apple.iokit.SCSITaskUserClient 3.6.6
com.apple.driver.AppleIRController 325.7
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.5.1
com.apple.driver.AppleFWOHCI 5.0.2
com.apple.driver.AppleSDXC 1.5.2
com.apple.driver.AppleUSBHub 666.4.0
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.driver.AppleAHCIPort 3.0.0
com.apple.driver.AppleUSBEHCI 660.4.0
com.apple.driver.AppleUSBXHCI 677.4.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
com.apple.driver.AppleBluetoothHIDKeyboard 170.15
com.apple.driver.AppleHIDKeyboard 170.15
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.6.1f2
com.apple.vecLib.kext 1.0.0
com.apple.driver.AppleHDAController 2.6.1f2
com.apple.iokit.IOHDAFamily 2.6.1f2
com.apple.driver.IOBluetoothHIDDriver 4.2.4f1
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOBluetoothFamily 4.2.4f1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.IOPlatformPluginFamily 5.7.0d11
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.4f1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOSurface 91.1
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOAcceleratorFamily2 98.20
com.apple.AppleGraphicsDeviceControl 3.5.26
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.iokit.IOUSBMassStorageClass 3.6.0
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.CoreStorage 380
com.apple.iokit.IOFireWireSBP2 4.2.6
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.6
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.2.7
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IO80211Family 630.35
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 677.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Unable to gather system configuration information.Model: Macmini6,1, BootROM MM61.0106.B03, 2 processors, Intel Core i5, 2.5 GHz, 16 GB, SMC 2.7f0
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x31364B544631473634485A2D314736443120
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x31364B544631473634485A2D314736443120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.4f1 13674, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE HDD HTS545050A7E362, 500.11 GB
USB Device: USB3.0 Hub
USB Device: USB3.0 Hub
USB Device: Backup+ Desk
USB Device: Hub
USB Device: Hub
USB Device: Diablo III Gaming Mouse
USB Device: Hub
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB2.0 Hub
USB Device: USB2.0 Hub
USB Device: Hub
USB Device: My Passport 070A
Thunderbolt Bus: Mac mini, Apple Inc., 23.4

Remove the Norton/Symantec product by following the instructions on either of these pages:
Uninstalling your Norton product for Mac
Removing Symantec programs for Macintosh
If you have a different version of the product, the procedure may be different. Back up all data before making any changes.

OS X tries to reboot every night

In the past week I've started keeping my mac on at night to download bit torrent files. For some reason, it reboots itself every night. This is incredibly annoying, and I have my mac secured, so it doesn't automatically log in. I've checked the console log to try and determine what's causing it to reboot, but I didn't find anything. Where can I find what is requesting the reboot so I can shut it off?
Thanks,
Todd

Ok,
I've looked at my system log and I don't see anything out of the ordinary. I fired my macbook up after I got home from work at 19:08, when I came home at 21:57 from dinner, it had tried to shut down. I've included the entire console log, there's nothing between 19:16 and 21:57. Can I turn on more verbose logging?
Oct 5 19:08:13 todd kernel[0]: System SafeSleep
Oct 5 19:08:13 todd kernel[0]: hibernate_page_list_setall start
Oct 5 19:08:13 todd kernel[0]: hibernate_page_list_setall time: 252 ms
Oct 5 19:08:13 todd kernel[0]: pages 356787, wire 51685, act 35092, inact 53149, zf 31701, could discard act 80113 inact 105047
Oct 5 19:08:13 todd kernel[0]: hibernate_page_list_setall found pageCount 356787
Oct 5 19:08:13 todd kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
Oct 5 19:08:13 todd kernel[0]: IOHibernatePollerOpen(0)
Oct 5 19:08:13 todd kernel[0]: writing 356279 pages
Oct 5 19:08:13 todd kernel[0]: image1Size 91656704
Oct 5 19:08:13 todd kernel[0]: all time: 8063 ms, comp time: 1702 ms, deco time: 0 ms,
Oct 5 19:08:13 todd kernel[0]: image 315595264, uncompressed 700903424 (171119), compressed 314348784 (44%), sum1 878c6d06, sum2 aefe5823
Oct 5 19:08:13 todd kernel[0]: hibernate_write_image done(0)
Oct 5 19:08:13 todd kernel[0]: sleep
Oct 5 19:08:13 todd kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Oct 5 19:08:13 todd kernel[0]: Started CPU 01
Oct 5 19:08:13 todd kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep
Oct 5 19:08:13 todd kernel[0]: System Wake
Oct 5 19:08:13 todd kernel[0]: Previous Sleep Cause: 2
Oct 5 19:08:14 todd BatteryUpdater[510]: Battery does not need the BatteryUpdate v 1.2 (0x2)
Oct 5 19:08:15 todd mDNSResponder: getifaddrs ifa_netmask for vmnet8(8) Flags 8863 Family 2 172.16.93.1 has different family: 0
Oct 5 19:08:15 todd mDNSResponder: getifaddrs ifa_netmask for vmnet1(9) Flags 8863 Family 2 172.16.199.1 has different family: 0
Oct 5 19:08:15 todd BatteryUpdater[511]: Battery does not need the BatteryUpdate v 1.2 (0x2)
Oct 5 19:08:29 todd kernel[0]: IOAudioStream[0x451aa00]::clipIfNecessary() - Error: attempting to clip to a position more than one buffer ahead of last clip position (25,19ec)->(27,2fe9).
Oct 5 19:08:29 todd kernel[0]: IOAudioStream[0x451aa00]::clipIfNecessary() - adjusting clipped position to (27,19ec)
Oct 5 19:08:49 todd kernel[0]: hibernate image path: /var/vm/sleepimage
Oct 5 19:08:49 todd kernel[0]: sizeof(IOHibernateImageHeader) == 512
Oct 5 19:08:49 todd kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0xc805000, maxio 400000
Oct 5 19:08:49 todd kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 3
Oct 5 19:08:49 todd kernel[0]: hibernate_alloc_pages flags 00000000, gobbling 0 pages
Oct 5 19:14:46 todd kernel[0]: System SafeSleep
Oct 5 19:14:46 todd kernel[0]: hibernate_page_list_setall start
Oct 5 19:14:46 todd kernel[0]: hibernate_page_list_setall time: 245 ms
Oct 5 19:14:46 todd kernel[0]: pages 327653, wire 49701, act 27891, inact 35102, zf 29268, could discard act 80467 inact 105224
Oct 5 19:14:46 todd kernel[0]: hibernate_page_list_setall found pageCount 327653
Oct 5 19:14:46 todd kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
Oct 5 19:14:46 todd kernel[0]: IOHibernatePollerOpen(0)
Oct 5 19:14:46 todd kernel[0]: writing 327132 pages
Oct 5 19:14:46 todd kernel[0]: image1Size 85210112
Oct 5 19:14:46 todd kernel[0]: all time: 6638 ms, comp time: 1407 ms, deco time: 0 ms,
Oct 5 19:14:46 todd kernel[0]: image 262421504, uncompressed 579342336 (141441), compressed 261273980 (45%), sum1 9319bd47, sum2 57c4a76c
Oct 5 19:14:46 todd kernel[0]: hibernate_write_image done(0)
Oct 5 19:14:46 todd kernel[0]: sleep
Oct 5 19:14:46 todd kernel[0]: IOUSBWorkLoop::closeGate - interrupt Thread being held offEnabling XMM register save/restore and SSE/SSE2 opcodes
Oct 5 19:14:46 todd kernel[0]: Started CPU 01
Oct 5 19:14:46 todd kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep
Oct 5 19:14:46 todd kernel[0]: System Wake
Oct 5 19:14:48 todd mDNSResponder: getifaddrs ifa_netmask for vmnet8(8) Flags 8863 Family 2 172.16.93.1 has different family: 0
Oct 5 19:14:48 todd mDNSResponder: getifaddrs ifa_netmask for vmnet1(9) Flags 8863 Family 2 172.16.199.1 has different family: 0
Oct 5 19:14:48 todd BatteryUpdater[517]: Battery does not need the BatteryUpdate v 1.2 (0x2)
Oct 5 19:15:46 todd configd[37]: Error: Failed to join most recent network "cafenet", err=88001006 (will search for any others)
Oct 5 19:15:47 todd /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Could not find "cafenet" on channel(s) 6
Oct 5 19:15:48 todd /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: No networks found on channel(s) 6 11
Oct 5 19:15:48 todd /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Could not find "Telecom wireless hotspot" on channel(s) 6 11
Oct 5 19:15:48 todd mDNSResponder: getifaddrs ifa_netmask for vmnet8(8) Flags 8863 Family 2 172.16.93.1 has different family: 0
Oct 5 19:15:48 todd mDNSResponder: getifaddrs ifa_netmask for vmnet1(9) Flags 8863 Family 2 172.16.199.1 has different family: 0
Oct 5 19:15:48 todd configd[37]: AppleTalk startup
Oct 5 19:15:51 todd configd[37]: posting notification com.apple.system.config.network_change
Oct 5 19:15:51 todd kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x4a31480.
Oct 5 19:15:51 todd lookupd[525]: lookupd (version 369.6) starting - Fri Oct 5 19:15:51 2007
Oct 5 19:15:51 todd kernel[0]: vmnet: VMNetConnect: returning port 0x4a31480
Oct 5 19:15:51 todd kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Oct 5 19:15:51 todd kernel[0]: vmnet: Allocated hub 0x54ec000 for hubNum 0.
Oct 5 19:15:51 todd kernel[0]: vmnet: VMNET_SO_BINDTOHUB: port: paddr 00:50:56:fb:c8:3a
Oct 5 19:15:51 todd kernel[0]: vmnet: Hub 0
Oct 5 19:15:51 todd kernel[0]: vmnet: Port 0
Oct 5 19:15:51 todd kernel[0]: vmnet: bridge-en1: got dev 0x4677404
Oct 5 19:15:51 todd kernel[0]: vmnet: bridge-en1: wireless interface detected.
Oct 5 19:15:51 todd kernel[0]: vmnet: bridge-en1: up
Oct 5 19:15:51 todd kernel[0]: vmnet: bridge-en1: attached
Oct 5 19:15:51 todd kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x4a31480.
Oct 5 19:15:53 todd configd[37]: AppleTalk startup complete
Oct 5 19:15:53 todd mDNSResponder: getifaddrs ifa_netmask for vmnet8(8) Flags 8863 Family 2 172.16.93.1 has different family: 0
Oct 5 19:15:53 todd mDNSResponder: getifaddrs ifa_netmask for vmnet1(9) Flags 8863 Family 2 172.16.199.1 has different family: 0
Oct 5 19:15:56 todd mDNSResponder: NOTE: Wide-Area Service Discovery disabled to avoid crashing defective DNS relay 10.1.1.1.
Oct 5 19:16:35 todd kernel[0]: CiscoVPN : shutting down VPN driver.
Oct 5 19:16:35 todd kernel[0]: CiscoVPN : waking up VPN driver.
Oct 5 19:16:47 todd lookupd[531]: lookupd (version 369.6) starting - Fri Oct 5 19:16:47 2007
Oct 5 19:16:47 todd configd[37]: posting notification com.apple.system.config.network_change
Oct 5 19:16:47 todd lookupd[532]: lookupd (version 369.6) starting - Fri Oct 5 19:16:47 2007
Oct 5 19:16:49 todd mDNSResponder: getifaddrs ifa_netmask for vmnet8(8) Flags 8863 Family 2 172.16.93.1 has different family: 0
Oct 5 19:16:49 todd mDNSResponder: getifaddrs ifa_netmask for vmnet1(9) Flags 8863 Family 2 172.16.199.1 has different family: 0
Oct 5 21:57:42 todd mDNSResponder: getifaddrs ifa_netmask for vmnet8(8) Flags 8863 Family 2 172.16.93.1 has different family: 0
Oct 5 21:57:42 todd mDNSResponder: getifaddrs ifa_netmask for vmnet1(9) Flags 8863 Family 2 172.16.199.1 has different family: 0
Oct 5 21:57:51 todd mDNSResponder: getifaddrs ifa_netmask for vmnet8(8) Flags 8863 Family 2 172.16.93.1 has different family: 0
Oct 5 21:57:51 todd mDNSResponder: getifaddrs ifa_netmask for vmnet1(9) Flags 8863 Family 2 172.16.199.1 has different family: 0

VOD down every night

Similar Messages

Maybe you are looking for