[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#409011: When booting: 38 sec. delay at "Attempting manual resume"



On Mon, Jan 29, 2007 at 04:16:24PM -0800, David Lawyer wrote:
> Package: linux-image-2.6.17-2-486
> Version: 2.6.17-9_i386
> 
> Please merge my bug report 365266 into this as they are at least
> partially the same bug.  When I submitted the 365266 bug report I
> thought that the delay in booting was due to probing ide0 which
> is broken on my PC.  But now it doesn't seem to probe ide0 anymore but
> the delay still exists.
> 
> Here's from dmesg at the point of delay.  Note that I've put "debug" and
> "time" on the kernel command line (using lilo).
> 
> [   46.324557] hdd: cache flushes not supported
> [   46.325131]  hdd: hdd1 hdd2 hdd3
> [   84.007425] Attempting manual resume
> [   84.353163] kjournald starting.  Commit interval 5 seconds
> 
> What is going on?  "resume" must mean resume from a suspend, but there
> is no suspend in dmesg.  The "Attempting manual resume" message is
> found in /linux-2.6.x/kernel/power/disk.c in the function
> resume_store().  I don't have source code on my PC but found it on the
> Internet at:
> http://www.gelato.unsw.edu.au/lxr/source/kernel/power/disk.c#L12
> 
> According to this site, the function name that issues this message
> (resume_store) only appears in the definition of this function,  In
> other words the function is defined but never used (if this site
> indexing is correct).
> 
> cat /sys/power/resume results in 22:67 which is hdd3, the swap
> partition on my "backup" drive.  Apparently the image being restored
> comes from there and it happens just after hdd3 prints in the dmesg
> output.  Yet I don't see S1SUSPEND on hdd3 which is the SWSUSP_SIG
> (sinature).
> 
> There is a document, swsusp, in the power directory of the kernel
> documentation and it says that it's not good to use suspend if the ide
> driver is a module (as it is with this package).  But is suspend being
> used at all? 
> 			David Lawyer

Does this error still occur with more recent kernel versions?

Cheers,
        Moritz



Reply to: