linux-kernel - Re: [BUG 4.1.0-rc6] iwlwifi: "Error sending REPLY_TXFIFO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1433446982.22937.4.camel@intel.com>
Date:	Thu, 4 Jun 2015 19:43:02 +0000
From:	"Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>
To:	"kirill@...temov.name" <kirill@...temov.name>
CC:	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"Berg, Johannes" <johannes.berg@...el.com>
Subject: Re: [BUG 4.1.0-rc6] iwlwifi: "Error sending REPLY_TXFIFO_FLUSH:
 time out after 2000ms"

On Thu, 2015-06-04 at 22:32 +0300, Kirill A. Shutemov wrote:
> On Thu, Jun 04, 2015 at 06:13:22PM +0000, Grumbach, Emmanuel wrote:
> > On Thu, 2015-06-04 at 20:37 +0300, Kirill A. Shutemov wrote:
> > > Hi,
> > > 
> > > I've trigered the bug few times after several suspend/resume cycles.
> > > Hardware is Thinkpad X1 2013 with Intel Corporation Centrino Advanced-N
> > > 6205 (8086:0085) (rev 96).
> > > 
> > 
> > This really looks like the platform problem people have been hitting.
> > The device is no longer accessible.
> > Unfortunately, I really don't know what we can do in that case.
> 
> Is there anything I can do to provide info you need?
> 
Thing is that I have already talked to the relevant people internally.
The problem here is that the PCI bus is not doing its work anymore. This
can happen when one of the sides does a violation that the other side
isn't ready to cope with. The proper way to cope with this is to take
the machine and to plug it in a PCI analyzer. This is an equipment that
monitors all the PCI transactions on the bus. You are not the first to
complain, I have had a lot of complaints about this recently. Someone
even tried to bisect because he thought this was a regression. This
didn't bring any conclusion since the commit that served as the 'good'
baseline wasn't working anymore after he finished the bisection.
In short, unless you are ready to send the actual system that is giving
you trouble, there isn't much I can do.
You can try the step in
https://bugzilla.kernel.org/show_bug.cgi?id=91171#c42 to see if it can
help recovering.