Bugzilla – Bug 10804
Fab4 won't let windows server sleep, continuously waking up windows server
Last modified: 2009-10-05 14:36:58 UTC
Bit of a show-stopper for me this one, as i am having to pull the power cord out when not in use to prevent it from bringing my beastly vista box out of sleep (s3) straight after it goes to sleep. It does not seem to mater what 'state' the fab4 is left in, i.e - 'off', 'on', home menu etc. I have seen this with the Controller from time to time, but usually power cycling that and making sure it was left a the home menu when docked would sort it out.
Are you sure this are WOL packets and not just regular network traffic?
Yes, i have been using WOL for a while now with my SB3, SBr, SBc and laptop - nothing else wake the server unless it 'needs' to and send a magic packet. My fab4 did not until r3895, now it constantly wakes the server until i pull the plug. What else could it be? if it was normal network traffic my other players would be bringing it out of standby. The only thing thats changed on my network is the fab4. (In reply to comment #1) > Are you sure this are WOL packets and not just regular network traffic? >
Hmm, I do not see that when testing against a Mac running OSX. As long as Fab4 stays in the home menu or off screensaver, my Mac goes to sleep and stays there. Only if I chose something that requires the server my Mac gets woken up. Is your Fab4 using wired or wireless? Could you check the wake on lan settings of the ethernet card in your PC? I know there are some cards out there which allow different levels of wake on lan and I am wondering if you have one of these and if maybe that the difference. Thanks Felix
Wireless. And my NIC is set to "Only allow management stations to wake this computer..." (if that not set, any traffic will wake it). Worked perfectly for months until this weeks fab4 firmware. Just to reiterate; i have absolutely isolated this to my fab4, nothing else on my network wakes the server. The fab4 did not until this week, and the problem goes away when i physically pull the fab4s power cord. Does not have tried leaving it on the home menu and 'off', but that does not elp. This is not an intermittent fault, it is constant; when the gab4 is powered the server wont be asleep for more than 3 seconds before it woken again. Was in a non-stop sleep/wake cycle for the last couple of days. My partner called me at work to tell me and i got her to pull the fab4's power - bingo, problem goes away. I dont know what else i can say really. I also have a little app on my laptop which i sometime use to wake the server, it's called 'WOL magic packet sender'. It also has a 'receive' test function that listens for 'magic' wake request packets - any idea which port it needs to listen to if i run it on my server? I would like to look deeper into this if you need me to, it would help we work out under what conditions and how frequently they are being sent. Or is that another way to monitor this (other than waiting for my PSU and HDD to fail, lol)? (In reply to comment #3) > Hmm, I do not see that when testing against a Mac running OSX. As long as Fab4 > stays in the home menu or off screensaver, my Mac goes to sleep and stays > there. Only if I chose something that requires the server my Mac gets woken up. > > Is your Fab4 using wired or wireless? > > Could you check the wake on lan settings of the ethernet card in your PC? I > know there are some cards out there which allow different levels of wake on lan > and I am wondering if you have one of these and if maybe that the difference. > > Thanks > Felix >
Thanks for the extended information. However I've double checked with my Fab4 using wireless and am still unable to see what you describe. :( Have you tried to do a factory reset on your Fab4?
Yes, two factory resets this morning. Still happening, even straight after a FR without ever having played anything and staying at the home menu and connected to itself and turned 'off'. (In reply to comment #5) > Thanks for the extended information. However I've double checked with my Fab4 > using wireless and am still unable to see what you describe. :( > > Have you tried to do a factory reset on your Fab4? >
Ok, I have no further idea at this point. I suggest QA checks this out.
Dominic: Do you have the means to capture a network trace? TCPDUMP or WireShark would probably do the trick.
If the next FW release does not improve matters, i will try and provide you with a trace. I have had a quick look at using wireshark, and TBH it is pushing the envelope of my networking knowledge, so i may have to seek further advice in the forum. (In reply to comment #8) > Dominic: Do you have the means to capture a network trace? > > TCPDUMP or WireShark would probably do the trick. >
bug 10810 and/or bug 10740 related at all? I've seen this in QA since 7.3.2 but could not pin down how/why it was happening Any device attached to my windows system, when the system tries to go to S3/S4 it will get re-woken immediately. moving the the player to SN or disconnecting it will allow the system to go to S3/S4
I have seen this with SB2/3, Boom, Duet, Fab4
Dominic, did you have a look at the bugs James references in comment 10 to see if they match your symptoms as well? Information note: there's info about how to correctly set up windows for WOL on the Wikipedia Wake on Lan page.
I'm not sure if it is related or not - but i am not seeing this with my SB3, SBr or SB Controller - its only the fab4. Also, i would be very surprised to see the same bug simultaneously appear in the fab4 and SB3's firmware given how different they are - right? And as said in that other bug report, just 'pinging' the server should not wake the server, only a special wake/magic packet should wake the server. Remember i am not saying that the server wont enter S3 mode - its does that fine - but it gets woken up immediately by the fab4 (which is now sitting there unplugged). I repeat - i know how to set up WOL - i have been using it for about a year perfectly fine with my SB3, SBr, SBc, fab4 and my laptop. It is configured 100% correctly, this has only happened since the fab4 was updated to r3895. This is NOT a windows config issue. (In reply to comment #12) > Dominic, did you have a look at the bugs James references in comment 10 to see > if they match your symptoms as well? > > Information note: there's info about how to correctly set up windows for WOL on > the Wikipedia Wake on Lan page. >
Dominic: Which build of SC are you running? Are all of your players connecting to the same system/build or different systems? Does the same thing happen if you shut down SC?
I have tried several nighties, including last nights. I dont think this is a server issue though. All players are connected to the same SC. SC is running on my Vista64 box, which is connected (wired) to my 2wire router. My SB3, SBr, SBc and fab4 are all connected wirelessly. Yes, i have tried this with SC running and SC disabled. It also makes no difference if i put the PC to sleep or leave it to do a scheduled sleep. I will try and provide a trace over the next couple of days when i am less busy. (In reply to comment #14) > Dominic: Which build of SC are you running? > > Are all of your players connecting to the same system/build or different > systems? > > Does the same thing happen if you shut down SC? >
Ok, could of quick questions re capturing the trace with wireshark - Should i run it on my laptop, and let the server go through its sleep/wake - or install wireshark on the PC SC is running on? How long do you want the trace to run for? Any other instructions that might help?
Created attachment 4711 [details] Network trace (wireshark) - showing idle/OFF fab4 preventing server sleep
Here is the network trace you requested. --------------------------------------- The following are the IP address's of all devices on my network; SC - 192.168.1.65 Laptop - 192.168.1.80 SB3 - 192.168.1.68 SBr - 192.168.1.70 SBc - 192.168.1.69 fab4 - 192.168.1.81 NOTES: Wirehsark was running on my laptop. SC is wired to the router, everything else is wireless. WOL is configured correctly and the server is set to sleep (S3) after 5 minutes. I have tried manually shutting down SC, but it still gets woken you striaght away by the fab4. As soon as the fab4 is physically unplugged, the server will go to sleep and stay asleep with all other devices still connected. During this trace, everything on the network was idle - that is to say, none of the devices where being used or playing music (other than the laptop). I did not touch them at all, they all just sat the at the home menu with their clock screen savers up. I have also noticed that sometimes the server is actually prevented from going to sleep when it should. In order to show that it does sleep then get woken up, i pressed the servers case power button which puts it to sleep - it got woken striaght up again. Toward the end of the trace i pulled the fab4's power cord. The server then went to sleep when it was supposed to and stayed asleep. (In reply to comment #17) > Created an attachment (id=4711) [details] > Network trace (wireshark) - showing idle/OFF fab4 preventing server sleep >
Just to add, i updated the fab4 to r3945 today and i am still seeing the exact same symptom.
Thanks for the attached log file. If I searched correctly I see one single WOL magic packet (no. 1606) which is sent from 192.168.1.69 (SBC) and none other. The packet is listed with protocol ECHO (7) because we are sending the WOL magic packets to port 7. My guess it that something different than WOL magic packets immediately wake your PC or do prevent it from sleeping. Why this is only an issue for Fab4 but not SBC I don't know, maybe we are sending different / more traffic between Fab4 and SC than SBC and SC?
UPDATE: After Felix say the trace i provided showed a WOL packet from the SBc's IP, i decided to try something... and i have had a bit of a breakthrough; If i turn the SBc off (completely powered down) i dont see the problem any more and i can have the fab4 permanently on. So i can have either the fab4 on, or the SBC on - but not both. However, as soon as the SBc is back on the server is getting woken up - even just sat in the dock not being used it wakes the server when the fab4 is also on. Does not seem to matter if the SBc is connected to any player or not connected to a player. So basically SBc+Fab4 wake the server constantly, but SBc or Fab4 on thier own and the server sleeps fine. So there seems to be some kind of interaction between the SBc and Fab4 thats causing this. Might also explain why no one else has seen this and thinks i am mad :). Hope this helps.
Adjusting summary with updated info
Steven will investigate further
Since updating to SBC r4154 and FAB4 r4474, the problem seems to have gone.
It's planned to change when WOL packets are sent, so this will only be after a press (touch/button) by the user. Re-assigning to myself for this change.
Yikes, its back in r5823. http://forums.slimdevices.com/showthread.php?p=425527
Reset priority before triage.
Using this as the master bug for WOL improvements for 7.4
*** Bug 5378 has been marked as a duplicate of this bug. ***
We need to at least understand the cause of this for 7.4.
This should be fixed now that wol should only be called based on direct user input.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.