All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "Łukasz Walewski" <ljw@icm.edu.pl>
Cc: linux-wireless@vger.kernel.org, ilw@linux.intel.com, sgruszka@redhat.com
Subject: Re: iwl3945 randomly crashes
Date: Tue, 20 Dec 2016 11:19:38 -0600	[thread overview]
Message-ID: <1482254378.30160.16.camel@redhat.com> (raw)
In-Reply-To: <20161220181145.f92ef40322426f7911300885@icm.edu.pl>

On Tue, 2016-12-20 at 18:11 +0100, Łukasz Walewski wrote:
> On Tue, 20 Dec 2016 10:49:52 -0600
> Dan Williams <dcbw@redhat.com> wrote:
> 
> > 
> > On Tue, 2016-12-20 at 17:24 +0100, Łukasz Walewski wrote:
> > > 
> > > Hi,
> > > 
> > > I am using the latest Lubuntu 16.10 with fairly recent kernel
> > > 
> > > ljw@hideo:~$ uname -a
> > > Linux hideo 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:33
> > > UTC
> > > 2016 i686 i686 i686 GNU/Linux
> > > 
> > > on an old Toshiba laptop (Satellite Pro U200) equipped with an
> > > Intel
> > > PRO/Wireless 3945ABG adapter
> > > 
> > > ljw@hideo:~$ lspci | grep ireless
> > > 02:00.0 Network controller: Intel Corporation PRO/Wireless
> > > 3945ABG
> > > [Golan] Network Connection (rev 02)
> > > 
> > > The wireless network crashes once in a while with no apparent
> > > reason
> > > with the following log entries:
> > > 
> > > Dec 18 17:23:42 hideo kernel: [94900.863133] iwl3945
> > > 0000:02:00.0:
> > > loaded firmware version 15.32.2.9
> > > Dec 18 17:23:42 hideo kernel: [94900.913626] iwl3945
> > > 0000:02:00.0:
> > > BSM uCode verification failed at addr 0x00003800+0 (of 900), is
> > > 0xa5a5a5a2, s/b 0xf802020
> > > Dec 18 17:23:42 hideo kernel: [94900.913633] iwl3945
> > > 0000:02:00.0:
> > > Unable to set up bootstrap uCode: -5
> > > 
> > > This problem has been reported several times on different mailing
> > > lists and community portals all over the Internet, nevertheless I
> > > was
> > > not able to locate the right fix for it.
> > > 
> > > The workaround suggested elswhere (restarting the network-manager
> > > when the problem occurs) works with my setup.
> > 
> > Instead of restarting NM, you can "pkill -TERM wpa_supplicant" or
> > something, which will do the same thing but just bounce the wifi
> > rather
> > than everything.  Or 'rmmod iwl3945; modprobe iwl3945'.
> 
> Thanks, but that is just another workaround. I am interested in
> fixing the problem, i.e. getting the driver not to crash at all,
> rather than playing around with it crashing every now and then.

Yeah, I know.  Just pointing out that people often use a huge hammer,
when a much smaller hammer will do.

Dan

      reply	other threads:[~2016-12-20 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 16:24 iwl3945 randomly crashes Łukasz Walewski
2016-12-20 16:49 ` Dan Williams
2016-12-20 17:11   ` Łukasz Walewski
2016-12-20 17:19     ` Dan Williams [this message]

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=1482254378.30160.16.camel@redhat.com \
    --to=dcbw@redhat.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ljw@icm.edu.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.