linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Berg, Johannes" <johannes.berg@intel.com>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: 3.18-rc0: iwlegacy failed after a while
Date: Sun, 26 Oct 2014 12:05:54 +0100	[thread overview]
Message-ID: <20141026110554.GA1634@amd> (raw)
In-Reply-To: <20141026103314.GB2588@redhat.com>

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

  reply	other threads:[~2014-10-26 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 13:02 3.18-rc0: iwlegacy failed after a while Grumbach, Emmanuel
2014-10-24 12:12 ` Stanislaw Gruszka
2014-10-25 11:42   ` Pavel Machek
2014-10-26 10:33     ` Stanislaw Gruszka
2014-10-26 11:05       ` Pavel Machek [this message]
2014-10-28 22:20         ` Pavel Machek
2014-11-02 12:25           ` Stanislaw Gruszka
2014-11-10  8:55             ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141026110554.GA1634@amd \
    --to=pavel@ucw.cz \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).