On Fri, Apr 17, 2009 at 1:30 PM, maximilian attems m...@stro.at wrote:
please as already told several times report upstream on
bugzilla.kernel.org so that the guys working on it can fix it.
let us know the bug number.
I have done this now (upstream bug 13199, this bug should be marked
On Fri, Apr 17, 2009 at 01:14:46PM -0400, Zack Weinberg wrote:
On Tue, Apr 7, 2009 at 6:50 PM, Moritz Muehlenhoff j...@inutil.org wrote:
I don't have the slightest idea how to report a bug to the kernel
upstream.
It's a standard Bugzilla installation: http://bugzilla.kernel.org
Do they
This is just to say that after an interval of working well, my ath5k
is now completely nonfunctional in both 2.6.28 and 2.6.29. (I'm going
to try backing all the way down to 2.6.27 next.) Cold boot doesn't
help. Rebooting into Windows doesn't help (it used to). This isn't
a hardware failure,
On Tue, Apr 7, 2009 at 6:50 PM, Moritz Muehlenhoff j...@inutil.org wrote:
I don't have the slightest idea how to report a bug to the kernel
upstream.
It's a standard Bugzilla installation: http://bugzilla.kernel.org
Do they mind receiving bug reports for distribution-modified kernels?
(i.e.
On Fri, Apr 17, 2009 at 12:57:09PM -0400, Zack Weinberg wrote:
This is just to say that after an interval of working well, my ath5k
is now completely nonfunctional in both 2.6.28 and 2.6.29. (I'm going
to try backing all the way down to 2.6.27 next.) Cold boot doesn't
help. Rebooting into
On Mon, 06 Apr 2009, Zack Weinberg wrote:
[..snipp..]
so can we please have an update on 2.6.29-2, that would be really great
for more information on the debian kernel, read
- http://wiki.debian.org/DebianKernel
- http://wiki.debian.org/DebianKernelReportingBugs
kind regards
--
maks
--
On Tue, Apr 7, 2009 at 3:40 AM, maximilian attems m...@stro.at wrote:
On Mon, 06 Apr 2009, Zack Weinberg wrote:
[..snipp..]
so can we please have an update on 2.6.29-2, that would be really great
It is still too early to say whether the problem has gone away.
zw
--
To UNSUBSCRIBE, email
In gmane.linux.debian.devel.kernel, you wrote:
On Sun, Mar 29, 2009 at 9:21 AM, maximilian attems m...@stro.at wrote:
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.
On Sun, Mar 29, 2009 at 9:21 AM, maximilian attems m...@stro.at wrote:
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
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
could you please retry with a recent kernel aka 2.6.29?
thanks for feedback
--
maks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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
12 matches
Mail list logo
