Subject: Re: trap in ipw(4)
To: john heasley <heas@shrubbery.net>
From: Luke Mewburn <lukem@NetBSD.org>
List: tech-net
Date: 12/16/2004 16:18:31
--yuedfix5hmtMJRO4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Dec 15, 2004 at 03:25:38PM -0800, john heasley wrote:
| I've hit a trap in the ipw driver several times on an ibm t41p w/ a
| 2100 3B mini-pci. I can almost reliably trigger it by booting, logging
| in from a remote, and running dmesg. It always occurs at the same place
| each time; IIRC, from the two occasions where it wasnt stuck in X, it
| complained about the value of %ebx, which appears to be m (the mbuf *).
|=20
| It seems as if the values of ifp and m (in ipw_start) get swapped
| somehow. I looked through the code and do not see any place where these
| could get swapped.
|=20
| The firmware is the most recent with -current of ~12/4. It is not doing
| WEP.
|=20
| Has anyone seen this before? Clues on how to debug?
I've had hangs on my system that I've suspected were ipw(4) related;
I couldn't get to the console because I was in X at the time.
Please submit a PR about this.
--yuedfix5hmtMJRO4
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)
iD8DBQFBwRqnpBhtmn8zJHIRAjrqAJ0Y5tHWpPAMjAA8a3fsEf6nZo/nzgCgu1VP
dTO6mDOAzFCQhR/kKiGkRMo=
=bppE
-----END PGP SIGNATURE-----
--yuedfix5hmtMJRO4--