Re: select with timeout across S3
From: Andreas Mohr <hidden>
Date: 2008-08-28 20:57:36
Possibly related (same subject, not in this thread)
- 2009-01-27 · Re: FW: select with timeout across S3 · Pavel Machek <hidden>
- 2008-09-12 · Re: FW: select with timeout across S3 · marty <hidden>
- 2008-09-11 · Re: FW: select with timeout across S3 · Pavel Machek <hidden>
- 2008-09-11 · Re: FW: select with timeout across S3 · Leisner, Martin <hidden>
- 2008-09-01 · Re: FW: select with timeout across S3 · Pavel Machek <hidden>
Hi, dito. This also happened to me a couple (4?) months ago, likely on 2.6.24 or 2.6.25. And for me it had the "very nice" effect of not obeying DHCP lease time, with a red-faced IT guy appearing in my door the next morning thusly... ;)
From examining it more closely, it was rather obvious that select timeout
happened maybe 10 hours later than it should have (with 12h lease time), due to hitting nightly S2R about two hours into the lease time. Annoying, to say the least. I think I then privately asked some timer guy about it, but I didn't get a reply. The DHCP client to hit this was pump, IIRC (can re-check). Andreas Mohr