linux-kernel - Re: 3.18-rc0: iwlegacy failed after a while

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]

Message-ID: <20141026110554.GA1634@amd>
Date:	Sun, 26 Oct 2014 12:05:54 +0100
From:	Pavel Machek <pavel@....cz>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	"Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"Berg, Johannes" <johannes.berg@...el.com>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>
Subject: Re: 3.18-rc0: iwlegacy failed after a while

On Sun 2014-10-26 11:33:15, Stanislaw Gruszka wrote:
> On Sat, Oct 25, 2014 at 01:42:46PM +0200, Pavel Machek wrote:
> > > Since 3.17 we have only 2 minor iwlegacy changes on current linus tree.
> > > If this is a regression it's probably caused by different subsystem
> > > changes, most likely by PCI changes. If this is not regression, such
> > > errors could be caused by enabling PS, but that has to be done
> > > explicitly, Pavel did you enable power_save ? 
> > 
> > This is running pretty standart MATE desktop, and no, I don't think I
> > enabled that.
> 
> It can be checked by "iw dev wlan0 get power_save" .
> 
> More important quiestions: Is this regression, did you see this error
> before? How reproducible is this problem?

I've never seen it before, and it only happened once after update to
3.18-rc.

> There is this message in the dmesg:
> 
> iwl3945 0000:03:00.0: BSM uCode verification failed at addr 0x00003800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
> 
> 0xa5a5a5a2 value suggest that we disconnect from the PCI bus, hence
> this could be also a H/W problem.

That machine is 10 years old and will work for another 10. It does not
have h/w problems ;-).

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/