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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 6 Feb 2008 22:00:26 +0100
From:	Pavel Machek <pavel@....cz>
To:	"Chatre, Reinette" <reinette.chatre@...el.com>
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

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@....cz Wed Oct 31 01:52:02 2007
> > From: Pavel Machek <pavel@....cz>
> > To: linux-wireless@...r.kernel.org,
> >        kernel list <linux-kernel@...r.kernel.org>,
> >        ipw3945-devel@...ts.sourceforge.net, yi.zhu@...el.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
--
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/