Re: linux-wlan-ng 0.2.5 and linux 2.4.34 panic on disconnect

--===============1376781114==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx"
Content-Disposition: inline


--dDRMvlgZJXvWKvBx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 11, 2007 at 09:30:13PM +0000, Tim Southerwood wrote:
> Yes - really 2.4.34 :) I have a good reason - it's a black box device
> and a key device driver is only available on 2.4.

=2E. is it binary-only?=20
=20
> Now, I have a little problem - a Dlink USB 802.11b device I have works
> fine with linux_wlan_ng 0.2.5, compiled on linux 2.4.34 with gcc 3.4.3,
> (as is the rest of the kernel) all on Redhat 7.3...

0.2.7 is available, with a few additional fixes, but I don't think any of t=
hem=20
would affect you.
=20
> ... until I unplug the device that is. Depending on the motherboard (I
> have 3 systems), either 1 in 2 times, 1 in 6-8 times or apparently never
> on the 3rd system, when the device is unplugged, a few seconds later the
> kernel panics in an interrupt handler, usually with the current task
> being the swapper. I have insufficient debugging enabled and I haven't
> yet identified which interrupt handler.

> Now, I apologise, but I haven't yet re-tested with a vanilla kernel
> (mine is patched in few key areas) nor have I gone to town enabling
> debugging... These are things I plan to attack tomorrow. I'm a bit green
> at device driver programming, though I've made a little progress with
> fixing another driver this week... I'm certainly in a good position to
> chuck some printk's in to aid debugging...

Unfortunately, there's not much we can do unless you (at the very least) ge=
t a=20
crash dump with resolved symbols; the possible presence of a binary driver =
and=20
patched-in-unknown-ways kernel also make things a lot more difficult.

Adding printk's in the driver might make things a lot worse; it may even ma=
ke the=20
problem go away.  You're better odd doing a debug build, adding '-g' to=20
EXTRA_CFLAGS, and then enabling serial console or take a photo of the crash=
 dump so=20
we can figure out where things are barfing.

> I've had this device working fine under 2.4.29 (also moderately patched)
> so I don't believe the hardware is dodgey... Or perhaps I should be
> looking at the USB host driver instead as it seems system dependant?

What USB host driver is in use?  usb-ohci, uhci, usb-uhci?

 - Solomon
--=20
Solomon Peachy                        [email protected]
AbsoluteValue Systems                 http://www.linux-wlan.com
721-D North Drive                     +1 (321) 259-0737  (office)
Melbourne, FL 32934                   +1 (321) 259-0286  (fax)

--dDRMvlgZJXvWKvBx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFFuOqzhinxHf95MjYRAtxOAJwPgbKgPyRYunPt2eBRlqGW58/e0wCgp3VV
fAqwZs9eOyDl0f/ktJDcTLs=
=9uu/
-----END PGP SIGNATURE-----

--dDRMvlgZJXvWKvBx--

--===============1376781114==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Linux-wlan-user mailing list
[email protected]
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
--===============1376781114==--