Hi. Sorry for coming late to the party. I've only just seen this thread, and have had reports of it too. My concern is, shouldn't we be dealing with the cause rather than just one symptom (and as Pavel rightly wondered, assuming there aren't more)? I'm not sure that I have a solution, but I think the point is worth raising again. Do we want something like adding the process's task struct to timer data, and get the timer code to delay firing timers for frozen processes? Regards, Nigel -- Nigel, Michelle and Alisdair Cunningham 5 Mitchell Street Cobden 3266 Victoria, Australia
Attachment:
pgpoemshsRgML.pgp
Description: PGP signature
- References:
- [PATCH] Page writeback broken after resume: wb_timer lost
- From: Peter Lundkvist <[email protected]>
- Re: [PATCH] Page writeback broken after resume: wb_timer lost
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Page writeback broken after resume: wb_timer lost
- From: Johannes Stezenbach <[email protected]>
- [PATCH] Page writeback broken after resume: wb_timer lost
- Prev by Date: Re: 2.6.17-rc6-mm2
- Next by Date: [RFC][PATCH 02/20] r/o bind mount prepwork: move open_namei()'s vfs_create()
- Previous by thread: Re: [PATCH] Page writeback broken after resume: wb_timer lost
- Next by thread: Re: [PATCH] Page writeback broken after resume: wb_timer lost
- Index(es):