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: <20141025114246.GA16230@amd>
Date:	Sat, 25 Oct 2014 13:42:46 +0200
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 Fri 2014-10-24 14:12:40, Stanislaw Gruszka wrote:
> On Thu, Oct 23, 2014 at 01:02:37PM +0000, Grumbach, Emmanuel wrote:
> > [Changed subject]
> > This is really iwlegacy and not iwlwifi.
> > 
> > 
> > > 
> > > Hi!
> > > 
> > > Full dmesg is in the attachment, I guess the troubles started with:
> > > 
> > > iwl3945 0000:03:00.0: Queue 4 stuck for 2004 ms.
> > > iwl3945 0000:03:00.0: On demand firmware reload
> > > iwl3945 0000:03:00.0: Master Disable Timed Out, 100 usec
> > > ieee80211 phy0: Hardware restart was requested
> > > iwl3945 0000:03:00.0: BSM uCode verification failed at addr
> > > 0x00003800+0 (of 900), is 0xa5\
> > > a5a5a2, s/b 0xf802020
> > > iwl3945 0000:03:00.0: Unable to set up bootstrap uCode: -5
> > > 
> > 
> > Huh - I don't remember any change there, but you should ask the right person - iwlegacy maintainer :)
> 
> 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.
									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/