Bug#404316: AW: Re: Bug#404316: Found in actual sid version
Gesendet mit dem BlackBerry Handheld von T-Mobile -Original Message- From: Tim Dijkstra [EMAIL PROTECTED] Date: Mon, 5 Mar 2007 17:31:38 To:Michael Meskes [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#404316: Found in actual sid version 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
Bug#404316: Found in actual sid version
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. I agree that this is strange. 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? It's already on my todo list, but I haven't found the time yet. 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. Well, if people are really using it you're right. I'm not really sure about this. Keep in mind that people might or might not update their initrd images. At least on my system the images weren't updated automatically all the time. But if you know that it works for others I'm fine with important. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404316: Found in actual sid version
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
Bug#404316: Found in actual sid version
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 set the severity of this bug back to grave to make sure it does not migrate to etch. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
