linux-kernel - RE: ipw3945: not only it periodically dies, it also BUG()s

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 Feb 2008 14:41:08 -0800
From:	"Chatre, Reinette" <reinette.chatre@...el.com>
To:	"Pavel Machek" <pavel@....cz>
Cc:	<ipw3945-devel@...ts.sourceforge.net>,
	<linux-wireless@...r.kernel.org>, "Zhu, Yi" <yi.zhu@...el.com>,
	"kernel list" <linux-kernel@...r.kernel.org>
Subject: RE: ipw3945: not only it periodically dies, it also BUG()s

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

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

The instructions on how to report a bug have been updated to address the
above issues. Thank you very much for helping us to make it better.

Reinette
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/