Your message dated Tue, 17 Dec 2013 14:10:52 +0100
with message-id <[email protected]>
and subject line failed to provide moreinfo
has caused the Debian Bug report #725780,
regarding base: kernel stuck after any kind of boot unless noresume parameter
is provided
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.)
--
725780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725780
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: base
Severity: normal
When I boot (either after halt or hibernate) the kernel stuck when it attempt
to check if there is any data to resume from (probably after hibernation) but
even if I didn't hibernate. This doesn't seem to me like a kernel problem
(3.11.2) because I am using very same kernel on another machine I use and
everything works just fine there. If I don't provide noresume option, the
system can't boot, not even to recovery. I am using debian testing (sid). I
suspect this is something related to encryption, because last message I see on
screen say something about libcrypt or something similar. I will eventually
update this bug when I reboot my computer again (which may happen in few days)
in order to give you exact name of that library, but I created a default
installation without configuring anything like encryption, so I guess this
should work. BTW s2disk does successfuly hibernate
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.11.2-lite (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Hi,
closing this bug as the submitter failed to provide more info as promised, so
I assume this very strange problem (which doesnt seem like a Debian bug to me
in the first place) "magically" went away.
Feel free to shout, reopening bugs is easy.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
