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

Bug#696662: marked as done (base: rt2800pci_mcu_status no hardware response due to radio enabled to early)

Your message dated Sat, 24 Apr 2021 16:33:29 +0200
with message-id <YIQsOa3Buy7cUgda@eldamar.lan>
and subject line Re: Bug#696662: rt2800pci_mcu_status no hardware response due to radio enabled to early
has caused the Debian Bug report #696662,
regarding base: rt2800pci_mcu_status no hardware response due to radio enabled to early
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.)


-- 
696662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696662
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: base
Severity: important
Tags: upstream

Dear Maintainer,

Wheezy with firmware-ralink packagesinstalled for network controller RT2790
Wireless 802.11n 1T/2R PCIe network controller results in a [ 26.104901] phy0
-> rt2800pci_mcu_status: error - MCU request failed no response from hardware

This is probably due to the radio being enables to early when the network
controller did not yet wake up as it ralink network controller is confirmed
working in the end. See also my issue described in more detail on the Debian
forum including dmesg and lspci logs and a potential patch from an other distro
which tackles similar issue.

http://forums.debian.net/viewtopic.php?f=30&t=90523

This warning/error only occurs during a cold boot. Rebooting does not result in
same error message as network controller is already woken up.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Source: linux
Source-Version: 3.4.4-1~experimental.1

On Sat, Dec 29, 2012 at 03:04:39PM +0100, Ben Hutchings wrote:
> Control: severity -1 normal
> Control: tag -1 patch
> 
> I'm downgrading this because the error seems to be easily recoverable.
> 
> The upstream commits that should fix this are:
> 
> commit 09a3311c1a061bda809ff78c512855f3b71dcd6b
> Author: Jakub Kicinski <kubakici@wp.pl>
> Date:   Wed Feb 22 21:58:57 2012 +0100
> 
>     rt2800: Add documentation on MCU requests
> 
> commit e8b461c37717d6b5c071c4924845884a86c20752
> Author: Jakub Kicinski <kubakici@wp.pl>
> Date:   Wed Feb 22 21:58:58 2012 +0100
> 
>     rt2800pci: Fix 'Error - MCU request failed' during initialization
> 
> However there have been several other changes to hardware initialisation
> and it may be necessary to pick more of them to avoid a regression.  I'm
> not intending to work on this.

Still closing the bug with 3.4.4-1~experimental.1 (the first after
3.4~rc1) assuming any further problem is resolved as well. If this is
not the case please feel free to reopen the bug.

Regards,
Salvatore

--- End Message ---
Reply to: