Red Hat Bugzilla – Bug 240530
When suspending to RAM, hangs with "Suspending consoles"
Last modified: 2007-11-30 17:12:04 EST
2.6.21-1.3167.fc7 on a Dell Latitude D420
Trying to suspend to RAM leaves me waiting for "Suspending consoles" to finish,
which it never does.
Nigel C mentioned that this could be related to tick timers, and that pressing a
key should let it go through, but that doesn't work.
The stock F7 test 4 worked (kernel from ~1 ago, ie. it worked on Tuesday).
that, ~1 week ago. I'm using DaveJ's kernels, the regression is recent.
From my /var/log/messages, I believe it worked fine using:
and broke after the update to:
Can't test though, as the older kernels have disappeared.
IIRC it'd only be tick timers if you're running i386 and not x86_64 - what arch
is the machine? (I'm not immediately familiar with that system model number.)
You can get kernels from the build system here:
Could you also look at the Sleep Quirk Debugger, here:
and see if any of the advice there helps?
(In reply to comment #2)
> IIRC it'd only be tick timers if you're running i386 and not x86_64 - what arch
> is the machine? (I'm not immediately familiar with that system model number.)
It's i686 (it's a laptop, don't know any x86-64 laptops).
> You can get kernels from the build system here:
I'll double-check, if that's interesting.
> Could you also look at the Sleep Quirk Debugger, here:
I know about it, but read the bug description again, it won't help. The laptop
hangs while suspending, not when resuming.
> and see if any of the advice there helps?
I don't see any advices for the problem I'm seeing. It's definitely a kernel
problem, and a regression. It worked with earlier F7 test kernels.
and none of them seem to work, although I'm certain 2.6.21-1.3149.fc7 used to
work (that's the kernel I used to do suspend testing last Tuesday).
Tested with 2.6.21-1.3174.fc7, same problem.
Doing "echo mem > /sys/power/state" from run-level 3 (rather than using g-p-m)
shows the same hang. I can still type, and switch VTs though, but not run
anything (trying to log in to a console doesn't work).
Pressing Alt+SysRq+Fn+T (the Fn is necessary to get to the SysRq, this is a
laptop...) doesn't bring me any output (despite /proc/sys/kernel/sysrq being set
I also tested with the nmi_watchdog, and I'm not seeing anything appearing. I
also used the builtin Dell diagnostics, and all the tests pass (just in case it
might just be a hardware problem).
Any hints on debugging that?
That would make sense - if the console is suspended, any printks won't make it
to the screen until the console is resumed. This, of course, makes it a bit hard
to diagnose. Any chance of using something like KDB to dig deeper?
After Nigel mentioned it could be a driver issue, I tested and saw that the
iwl3495 driver is to blame.
Richard Hughes tested on his X60 with the same result (mine is a Dell Latitude
kernel-2.6.21-1.3180.fc7 still has the problem, and kernel-2.6.21-1.3186.fc7
isn't bootable (bug 240850).
*** This bug has been marked as a duplicate of 238938 ***