On Wed, Mar 23, 2005 at 02:33:44AM -0800, Andrew Morton wrote:
> Seems that there's a `struct work_struct' which is still registered but its
> memory has been freed. It's likely that CONFIG_DEBUG_PAGEALLOC caught this.
>
> Either that, or some module got unloaded without flushing its workqueue.
>
> Are you using any modules which do schedule_work()?
No.
> Have you added any code which does schedule_work()?
Hm, I don't think so. But of course I have some nfsv4 patches, and the
nfsv4 nfsd code does use schedule_delayed_work(). It's possible the
cleanup is wrong, and that bringing nfsd up and down could get nfsv4
into some bad state. I'll take a look. Would that explain this?
I'm not claiming this is a recent regression, by the way; apm resume has
always had intermittent problems on this laptop. It's only recently
that I've actually tried to pay attention to those problems. (Bad me!)
--b.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
