LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: ipw3945-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org, "Zhu, Yi" <yi.zhu@intel.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ipw3945: not only it periodically dies, it also BUG()s
Date: Wed, 6 Feb 2008 22:00:26 +0100	[thread overview]
Message-ID: <20080206210026.GA32641@elf.ucw.cz> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892003982E4C@orsmsx416.amr.corp.intel.com>

Hi!

> >>> ...I've reported this before, with full debugging. Not sure if
> >>> anything happened.
> >> 
> >> Could you please point me to where you have reported it before?
> > 
> > From pavel@ucw.cz Wed Oct 31 01:52:02 2007
> > From: Pavel Machek <pavel@ucw.cz>
> > To: linux-wireless@vger.kernel.org,
> >        kernel list <linux-kernel@vger.kernel.org>,
> >        ipw3945-devel@lists.sourceforge.net, yi.zhu@intel.com
> > Subject: iwl3945 in 2.6.24-rc1 dies under load
> > X-Warning: Reading this can be dangerous to your mental health.
> > 
> > ...and thread that resulted.
> 
> Could you please create a new bug in our bug tracking system
> (www.bughost.org) to enable us to track this problem? Please include the
> relevant information from the thread as well as the information you
> doscovered recently.

Hmmm... bugzilla says:

    * Exact steps to reproduce
    * Reproducability of bug (e.g. intermittent or 100% reproducable)
    * Did this problem not exist in previous version of the driver?
    * kernel version
    * AP brand/model
    * dmesg output at debug level 0x43fff
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		it would be nice to specify how to do this. It is
insmod parameter, right?

    * Type of security (if any) you are using (e.g. WEP64, WEP128, WPA, WPA2, 802.1x, etc)
    * Version of firmware
    * Version of the ieee80211 module
    * Proximity to the AP

    * Before reporting any firmware errors, please be sure to read Ben
Cahill's mailing list post on how to most effectively report such
bugs. 
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		unfortunately the link here does not work.

BTW, why not use kernel.org bugzilla? Having to create another account
is nasty...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-02-06 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 21:44 Pavel Machek
2008-02-05 22:59 ` Pavel Machek
2008-02-06  2:20 ` Chatre, Reinette
2008-02-06 14:32   ` Pavel Machek
2008-02-06 17:13     ` Chatre, Reinette
2008-02-06 21:00       ` Pavel Machek [this message]
2008-02-06 23:08         ` Chatre, Reinette
2008-02-15 22:41         ` Chatre, Reinette
2008-02-19 23:48           ` Pavel Machek
2008-02-07 22:04       ` iwl3945: not only it periodically dies, it also BUG()s, and oopses 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=20080206210026.GA32641@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@intel.com \
    --subject='Re: ipw3945: not only it periodically dies, it also BUG()s' \
    /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

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).