severity 404316 important thanks On Sat, 24 Feb 2007 11:33:28 +0100 Michael Meskes <[EMAIL PROTECTED]> wrote:
> I'm experiencing the same problem as mentioned in this bug for a few > weeks. Originally I thought I had a kernel problem, but I finally found > some time to test different kernels just to find that all share the same > problem. Now I got myself the old source of version 0.5-1 recompiled and > installed it and now everything is fine. This seems to be problem with > the up-to-date version. I doubt it, the original reporter opened this bug against 0.3. I still don't have a clue what is triggering this, also because the error message doesn't come from uswsusp. Could you add some printf's to see how far resume comes? Or do you want me to create a patch for you so you can test? > I set the severity of this bug back to grave to make sure it does not > migrate to etch. I don't feel like playing BTS ping-pong, but the severity for this bug is important IMHO. There is no security hole, lots of people are using it so it is usable. To reassure you this won't go into etch; this is a new upstream version and etch is *frozen*. grts Tim
signature.asc
Description: PGP signature