Your message dated Fri, 25 Jul 2008 22:54:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Re (2): Bug#488541: uswsusp: hangs system at startup
has caused the Debian Bug report #488541,
regarding uswsusp: hangs system at startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
488541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488541
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: uswsusp
Version: 0.7-1.2
Severity: critical
Justification: breaks the whole system
*** Please type your report below this line ***
I installed uswsusp inadvertently because it is a recommendation of pmutils.
The machine runs unattended 4 days of the week. During unattended
operation a power failure forced a reboot. Startup paused at the prompt
from uswsusp and waited for three days until I was able to intervene.
Normal email retrieval and other services were unavailable during this time.
This is unacceptable behaviour.
In the "default case" or "installed case" startup should resume if
there is no intervention after a minute or two.
Thanks, Peter Easthope
[EMAIL PROTECTED]
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
--
http://carnot.yi.org/
= http://carnot.pathology.ubc.ca/
Desktops.OpenDoc http://members.shaw.ca/peasthope/
--- End Message ---
--- Begin Message ---
Op Fri, 25 Jul 2008 09:50:42 -0700
schreef PETER EASTHOPE <[EMAIL PROTECTED]>:
> I removed uswsusp immediately after reading
> a tip from Andrew Sackville-West in debian-user.
> The console message is "resume: ..." although
> the program is uswsusp.
Well the package is called uswsusp, but the program resuming is called
resume:)
> t> ... or pm-utils for that matter on a server,
> that's desktop software.
>
> I've removed pm-utils, and by dependency hal,
> from my server at work. Yet from reading
> http://en.wikipedia.org/wiki/Hardware_abstraction_layer
> I would have thought hal would be useful on a
> server as well as a desktop and even on a laptop
> and a pda.
Well these technologies, hal, dbus and programs that were build around
it, come from the linux-desktop world, with a graphical interface and
such. So, yes they are also useful on PDAs and laptops, but I'm
not running it on my servers.
Looking at the rdepends of hal I see lots of desktop software.
Also, I wouldn't know a usecase for hibernating a server.
But anyway, I was defending my decision not to timeout. If I would
timeout, that could lead to dataloss (not resuming from a suspended
system with unsaved data). While waiting indefinitely is a mere
inconvenience. Unless it is a server system you can't access of
course... But people running uswsusp on a server should be a
minority.
> t> ... shouldn't happen if you didn't suspend before the
> powerfailure.
So, you weren't suspending, the problem was indeed:
> >
> The uswsusp code was in the initrd. Finally I had to
> "update-initramfs -u".
>
> "Could not stat the resume device file." was because
> I had changed the partitioning of the drive.
Ah, ok, that is nasty. But that's not a bug in uswsusp. Although it
is true that the average person repartitioning their harddisk wouldn't
think about uswsusp. It would be nice if we could automatize the
regeneration of the initramfs it, but there is not an easy way for
uswsusp to check if the initrd is still up-to-date...
grts Tim
--- End Message ---
