netdev - RE: iwlwifi worse than ever in current git.

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Jan 2012 20:40:32 +0000
From:	"Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>
To:	Dan Williams <dcbw@...hat.com>, Dave Jones <davej@...hat.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Guy, Wey-Yi W" <wey-yi.w.guy@...el.com>,
	Linux Wireless <linux-wireless@...r.kernel.org>
Subject: RE: iwlwifi worse than ever in current git.

Hi,

Is that series I added a debug flag that tells us what happens with the queues: please enable the 31st bit: 0x80000000

Just debug=0x80000000 as a module parameter.

> 
> On Tue, 2012-01-10 at 13:49 -0500, Dave Jones wrote:
> > For the last few releases, iwlwifi has been getting consistently worse
> > wrt reliability for me.  The failure mode has varied, from the chip just
> > locking up with no tx/rx of packets with nothing being logged, to
> > microcode warnings, and spewing 'Tx aggregation enabled' messages over and
> over.
> 
> You might want to CC linux-wireless@...r too...
> 
> > The merge post 3.2 has made these problems a lot worse.  Before, these
> > lock-ups were happening once or twice a day. Now they happen several times
> an hour
> > (and after the first one, they seem more frequent). When they happen,
> > unloading and reloading the module is the only way for me to get working
> wireless again.
> > They may happen more frequently when the laptop is not idle.
> >
> > I did a bisect of the changes since 3.2, which pointed at
> 76bc10fcd128ad028cf77c62e179cd20dc2ffecf
> > as being the culprit, but to be honest I'm not 100% convinced.
> >
> > Because every step of the way during the bisect, I saw different failure
> modes,
> > so when I marked something as 'good', it meant "doesn't lock up in the same
> way",
> > even though it may be symptomatic of the same problem.
> >
> > The specific chip I'm using is a 5300 in a Dell Adamo, connecting to
> > an Apple airport extreme (current model) in N mode.
> >
> > 	Dave
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe netdev" in
> > the body of a message to majordomo@...r.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.