1 |
Hi all, |
2 |
|
3 |
I just rebooted with the old kernel and here "hibernate-ram" still |
4 |
works, the laptop also wakes up succcessfully. The Old Kernel is |
5 |
2.6.25-x something. The new one is 2.6.26 and here it doesnt work, also |
6 |
not if I switch to tty1 before. I have the latest bios update and i have |
7 |
all the latest updates. |
8 |
So I conclude that the Problem is a bug in the Kernel. I will try and |
9 |
nail down the Problem a bit more clearly and then report back. |
10 |
|
11 |
Best Regards |
12 |
Sebastian |
13 |
|
14 |
Duncan wrote: |
15 |
> "Avuton Olrich" <avuton@×××××.com> posted |
16 |
> 3aa654a40808271947v183adf76lc84264f945588171@××××××××××.com, excerpted |
17 |
> below, on Wed, 27 Aug 2008 19:47:45 -0700: |
18 |
> |
19 |
> |
20 |
>> On Wed, Aug 27, 2008 at 4:56 PM, Sebastian Geiger <sbastig@×××.net> |
21 |
>> wrote: |
22 |
>> |
23 |
>>> I just upgraded to 2.6.26 and if I enter hibernate-ram the system |
24 |
>>> suspends but never wakes up again untill I do a cold reboot. Are there |
25 |
>>> any known issues currently with this Kernel version? I am using the |
26 |
>>> 2.6.26 tuxonice-sources and the latest hibernate script on amd64. |
27 |
>>> |
28 |
>> ACPI on linux is probably the most undependable things about the system. |
29 |
>> That being said, I've had much luck getting 'suspend to disk', aka |
30 |
>> hibernate, to work over 'suspend to ram', also known as sleep. |
31 |
>> |
32 |
>> Best of luck, but suspend to ram working is like expecting all the |
33 |
>> planets to align with the sun. Each driver for each chip in your |
34 |
>> computer must be ready for it, or it's not happening. |
35 |
>> |
36 |
> |
37 |
> ... And the kernel devs will say the same thing. They /are/ trying, and |
38 |
> things /are/ generally improving gradually in that area, but it's well |
39 |
> known that suspend to disk is /much/ more likely to work than suspend to |
40 |
> RAM. |
41 |
> |
42 |
> One thing you might try if you haven't already... X and video drivers |
43 |
> throw in a /lot/ more complexity. Many people find that suspend (of |
44 |
> either form) works MUCH better if they switch to a console before |
45 |
> suspending (leaving X running). If that works fine returning you to a |
46 |
> console but switching back to X afterward does /not/ work, try shutting X |
47 |
> down entirely before suspending. That may work. |
48 |
> |
49 |
> Beyond that, you can try unloading all non-critical modules and reloading |
50 |
> them after you resume. |
51 |
> |
52 |
> After you find a combination that works, you can of course script it, so |
53 |
> it all happens automatically. |
54 |
> |
55 |
> That said, if it was working with older kernels it'll be considered a |
56 |
> regression and the kernel folks are likely to be very interested in it, |
57 |
> particularly if you have time to file a kernel bug and do some follow-up |
58 |
> for them as they ask you to. I've had several bugs that I filed fixed, |
59 |
> but then I usually start running the -rcs (or trying to run them, anyway) |
60 |
> around -rc3 or so, and if I see a problem and it's not fixed by -rc4 or - |
61 |
> rc5, I'll bug it, and so far, they've always had it fixed before the full |
62 |
> release version. But it /can/ take rebuilding the kernel a few times, |
63 |
> often with debug-logging patches applied so they can find out what's |
64 |
> going on. Another common techique is "bisecting", that is, taking the |
65 |
> last known working version and the first known trouble version and |
66 |
> testing an rc about in the middle, thus cutting the problem space in |
67 |
> half, then one in the middle of that, etc, until you nail the bad rc, |
68 |
> then doing the same thing with the daily snapshots between the last good |
69 |
> rc and the first bad one, until you get the culprit day. Often given the |
70 |
> problem they can nail it once they know the day, but you can go farther |
71 |
> if you want to using git to bisect the day's patches until you find the |
72 |
> exact patch. (Or, do as I sometimes do and bisect the kernel sources |
73 |
> directory by directory and file by file until I find the file, then diff |
74 |
> the files and narrow it down to a specific changed line or set of lines, |
75 |
> tho that doesn't always work once you get beyond the file level since |
76 |
> often the changes are dependent on one another.) |
77 |
> |
78 |
> I may not be a coder, and I'm DEFINITELY not a kernel hacker, but I can |
79 |
> file and help trace down bugs as I see 'em, thereby contributing my |
80 |
> little bit to an improved Linux! =8^) |
81 |
> |
82 |
> |