Bug#562981: rt2860-source: connection drops - debian kernel 2.6.32
Hey Jonathan,
Thanks for following up on this. I haven't seen this happening on 3.x
kernels since I switched a few weeks back. I haven't been using the
system for gaming/voip or with synergy though, so it's possible my usage
patterns have changed .. but generally speaking I feel this is gone now.
TTimo
On 11/14/2011 5:17 AM, Jonathan Nieder wrote:
> Hi,
>
> Timothee Besset wrote:
>
>> Linux plageis 2.6.32-trunk-amd64 #1 SMP Thu Dec 17 06:29:18 UTC 2009
>> x86_64 GNU/Linux
>>
>> My wireless connection suddenly drops after 20 to 30 minutes of usage,
>> especially when I run the program synergy between my machines (if I am
>> not running synergy it can take many hours between every drops).
>>
>> In the syslog I see:
>> ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
> Sorry for the slow response. As Ben mentioned, after you reported
> this, the driver was merged into the main kernel package. Can you
> still reproduce the bug? If so, please try the following:
>
> 1. Attach output from "reportbug --template linux-image-$(uname -r)"
> right after experiencing it. This will give us some logs and
> tell us a little about your hardware.
>
> 2. Try to reproduce with a 3.x kernel from unstable or experimental
> (the corresponding driver there is rt2800pci). The only packages
> from outside of squeeze needed for this aside from the
> linux-image-* packages themselves are linux-base and
> initramfs-tools.
>
> If it exhibits similar problems, please report this upstream at
> linux-wireless@vger.kernel.org, cc-ing users@rt2x00.serialmonkey.com
> and either me or this bug log so we can track the resulting
> discussion.
>
> If it does not exhibit similar problems and the latest squeeze
> kernel does, we have an interesting task ahead of us. Maybe we
> could take inspiration from the new driver when fixing the old
> driver, or maybe it would be worth just backporting rt2800pci
> altogether.
>
> 3. Any new, weird symptoms in the meantime? Was this a regression,
> or was the driver always broken? Etc.
>
> Thanks for reporting, and I hope we can find a fix.
>
> Regards,
> Jonathan
Reply to: