[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#779084: marked as done (firmware-ralink: ralink wifi is very unstable)

Your message dated Tue, 20 Oct 2015 23:14:38 +0100
with message-id <1445379278.10397.17.camel@decadent.org.uk>
and subject line Re: Bug#779084: firmware-ralink: ralink wifi is very unstable
has caused the Debian Bug report #779084,
regarding firmware-ralink: ralink wifi is very unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
779084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779084
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-ralink
Version: 0.43
Severity: important

Hello Ben and Team,


I've been using this wifi for around 6 months now and I have definite
patter to share, on what triggers the bug. But once the bug is
triggered, association with an AP is impossible without a system reboot.

Following is the message spat on the kernel log.


[ 3326.041150] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3326.245315] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3326.449482] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3344.112116] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3344.127822] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3344.331876] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3344.536092] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3344.740208] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3358.931865] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3359.213949] r8169 0000:0f:00.0 eth0: link down
[ 3359.214006] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3504.645334] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3504.705372] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3504.967489] r8169 0000:0f:00.0 eth0: link down
[ 3504.967552] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3505.181733] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3520.534406] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3520.554042] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3520.758148] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3520.962331] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3521.166399] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3525.586524] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3525.594060] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3525.798167] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3526.002323] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3526.206483] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3543.869292] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3543.884805] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3544.088890] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3544.293069] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3544.497255] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3546.338940] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3546.338971] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3546.346841] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3546.403205] wlan0: aborting authentication with 08:86:3b:8d:df:1d by
local choice (Reason: 3=DEAUTH_LEAVING)
[ 3546.410844] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3546.426904] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3546.426938] wlan0: aborting authentication with 08:86:3b:8d:df:1d by
local choice (Reason: 3=DEAUTH_LEAVING)
[ 3546.614964] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue
0 failed to flush
[ 3546.837225] r8169 0000:0f:00.0 eth0: link down
[ 3546.837286] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3547.039550] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3548.044368] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3548.342499] r8169 0000:0f:00.0 eth0: link down
[ 3548.342566] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3549.149524] ieee80211 phy0: rt2800mmio_txdone: Warning - Got TX
status for an empty queue 0, dropping
[ 3549.261077] ieee80211 phy0: rt2x00queue_write_tx_frame: Error -
Arrived at non-free entry in the non-full queue 0
Please file bug report to http://rt2x00.serialmonkey.com
[ 3561.743353] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3561.911333] ieee80211 phy0: rt2x00queue_write_tx_frame: Error -
Arrived at non-free entry in the non-full queue 0
Please file bug report to http://rt2x00.serialmonkey.com
[ 3569.013263] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3569.283366] r8169 0000:0f:00.0 eth0: link down
[ 3569.283433] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3569.493608] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3571.695255] ieee80211 phy0: rt2x00queue_write_tx_frame: Error -
Arrived at non-free entry in the non-full queue 0
Please file bug report to http://rt2x00.serialmonkey.com
16:06 ♒♒♒   ☺    



The only possible workaround I know so far is to reboot the machine and
hope that on next reboot, it can associate with an AP.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

firmware-ralink depends on no packages.

firmware-ralink recommends no packages.

Versions of packages firmware-ralink suggests:
ii  initramfs-tools  0.116

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tue, 24 Feb 2015 16:46:50 +0530 Ritesh Raj Sarraf <rrs@researchut.co
m> wrote:
> On 02/24/2015 04:17 PM, Ritesh Raj Sarraf wrote:
> > The only possible workaround I know so far is to reboot the machine and
> > hope that on next reboot, it can associate with an AP.
> 
> And on reboots, most of the times, the wifi will not work.
> 
> The way it works is to:
> 1) Reboot into Windows
> 2) Let Windows connect to the same WiFi AP
> 3) Now, reboot into Linux
> 4) WiFi connects.

So this looks like a driver bug, not a firmware bug.  Please open a new
bug report.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: