Bug 3964 - S3 suspend fails with mdnsresponder running
Summary: S3 suspend fails with mdnsresponder running
Status: CLOSED CODE_FIX
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Shaohua
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-29 08:46 UTC by Pedro C
Modified: 2007-04-28 12:49 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.9-ac13
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Pedro C 2004-12-29 08:46:58 UTC
Distribution: Debian Sid
Hardware Environment: Asus M2400N Centrino laptop
Software Environment:
Problem Description: Linux won't go into S3 suspend if mdnsresponder is running.

Steps to reproduce:

1. Start mdnsresponder
2. Try to suspend
3. Suspend fails with:

PM: Preparing system for suspend
Stopping tasks:
===============================================================================================================================================
 stopping tasks failed (1 tasks remaining)
Restarting tasks...<6> Strange, mDNSResponder not stopped
 done
Comment 1 Pedro C 2005-03-13 16:43:13 UTC
This seams to be fixed in 2.6.11
Comment 2 Pedro C 2005-03-13 17:36:35 UTC
This still happens in 2.6.11 after all. It may have something to do with the
ipw2100 driver.
Comment 3 Shaohua 2005-03-14 23:31:18 UTC
I got a similar issue: syslogd can't be stopped. My investigation is syslogd 
is waiting for kjournald to flush some work, but kjournald is stopped, so 
syslogd can't be stopped. The refrigerator mechanism can't handle process 
relationship.
Comment 4 Rafael J. Wysocki 2006-09-28 16:10:28 UTC
Please close this bug if the problem doesn't occur for recent kernels (2.6.18
and later).
Comment 5 Pedro C 2006-09-28 17:18:31 UTC
I have no idea if this still applies. I don't think my current distro runs
mdnsresponder and I haven't seem similar bugs since. It should probably be
closed if no one can reproduce it.

Note You need to log in before you can comment on or make changes to this bug.