On Sat, 28 Mar 2009, Zack Weinberg wrote: > On Sat, Mar 28, 2009 at 2:08 AM, maximilian attems <m...@stro.at> wrote: > > could you please retry with a recent kernel aka 2.6.29? > > I have seen the bug with both .27 and .28, but only intermittently, > and not at all since I switched from network-manager to wicd. I have > now installed 2.6.29 on the machine, but it'll be some time before I > can be sure it's not happening, assuming the bug is fixed.
ok cool, thanks for letting us know. as 2.6.29 had quite some suspend path fixes. > > thanks for feedback > > I have to say I really don't appreciate the style of bug management > where I file a bug, there is no response for months on end, and then I > get a request to try a newer version. It gives the impression that > you're not actually doing anything about the bugs. ath5k was quite young on 2.6.26 so it was somehow expected to fail there. also you didn't seem to provide any updates nor did you go upstream. it's not that we have too many guys working on those bugs, so be happy at all to get asked. kind regards. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
