LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Chatre, Reinette" <reinette.chatre@intel.com>
To: "Pavel Machek" <pavel@ucw.cz>
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 15:08:57 -0800	[thread overview]
Message-ID: <D936D925018D154694D8A362EEB0892003983522@orsmsx416.amr.corp.intel.com> (raw)
In-Reply-To: <20080206210026.GA32641@elf.ucw.cz>

On Wednesday, February 06, 2008 1:00 PM, Pavel Machek  wrote:

>    * dmesg output at debug level 0x43fff
>      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 		it would be nice to specify how to do this. It is
> insmod parameter, right?

correct. you can do this as follows:
$ insmod iwl3945 debug=0x43fff
or
$ modprobe iwl3945 debug=0x43fff

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

We'll try to dig out the instructions from another location and update
that link. Thanks for letting us know.

> 
> BTW, why not use kernel.org bugzilla? Having to create another
> account is nasty... 

Users can report iwlwifi bugs in many locations ... their OSV's bug
tracker (which could end up being many) as well as the kernel.org
bugzilla. We focus on bugs in the bughost.org system.

Reinette

  reply	other threads:[~2008-02-06 23:14 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
2008-02-06 23:08         ` Chatre, Reinette [this message]
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=D936D925018D154694D8A362EEB0892003983522@orsmsx416.amr.corp.intel.com \
    --to=reinette.chatre@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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).