Return-path: Received: from mga02.intel.com ([134.134.136.20]:44177 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760358AbYBFXJQ convert rfc822-to-8bit (ORCPT ); Wed, 6 Feb 2008 18:09:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: ipw3945: not only it periodically dies, it also BUG()s Date: Wed, 6 Feb 2008 15:08:57 -0800 Message-ID: (sfid-20080206_230924_690102_B5C6C5A9) In-Reply-To: <20080206210026.GA32641@elf.ucw.cz> References: <20080205214441.GA1518@elf.ucw.cz> <20080206143218.GA16188@elf.ucw.cz> <20080206210026.GA32641@elf.ucw.cz> From: "Chatre, Reinette" To: "Pavel Machek" Cc: , , "Zhu, Yi" , "kernel list" Sender: linux-wireless-owner@vger.kernel.org List-ID: 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