|Summary:||2.6.25-rc7/8: Another resume regression|
|Product:||Power Management||Reporter:||Rafael J. Wysocki (rjw)|
|Severity:||normal||CC:||hjh, mlord, pavel, rui.zhang|
|Bug Depends on:|
|Bug Blocks:||7216, 9832|
Description Rafael J. Wysocki 2008-04-03 13:50:20 UTC
Subject : 2.6.25-rc7/8: Another resume regression Submitter : Mark Lord <firstname.lastname@example.org> Date : 2008-04-03 15:06 References : http://lkml.org/lkml/2008/4/3/283 This entry is being used for tracking a regression from 2.6.24. Please don't close it until the problem is fixed in the mainline.
Comment 1 Pavel Machek 2008-04-06 05:56:19 UTC
...hard to trigger, absolutely no debug data.... I'm not sure how to debug this one, or even verify that it is fixed....
Comment 2 Rafael J. Wysocki 2008-04-09 13:49:23 UTC
At http://lkml.org/lkml/2008/4/9/3 Mark said: It happened again, once, today. That's three times over a week of heavy use. Worth tracking, I suppose, but not enough information to resolve it.
Comment 3 Mark Lord 2008-04-14 16:23:46 UTC
I have had several instances of the system locking up solid during kernel initialization at boot, rather than just at resume time. Dunno if it's the same bug or not. The boot failures began back when the hi-rez timer rework was done in 2.6.21 (or 2.6.20? when was NO_HZ introduced?). Anyway, while bisecting a different kernel issue last week, this same machine locked up at boot in that fashion. Once, not repeatable. And another box here, which has been generally well-behaved for the past year, just today locked up at boot, again around the point where the high resolution timer messages normally appear on the console. That machine is running 184.108.40.206, and had to be reset immediately on discovery of the lockup. Not much useful, I know. Cheers
Comment 4 Zhang Rui 2008-09-27 01:00:16 UTC
can you reproduce the problem in the latest kernel? if yes, it would be great if you can attach the screenshot of the boot failure.
Comment 5 Zhang Rui 2008-11-20 21:41:34 UTC
mark, please re-open this bug if you can reproduce the bug in the latest kernel release.