From: Andrew Wasielewski <andrew@wasielewski.co.uk>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WARNING: at drivers/net/wireless/p54/main.c:443 p54_work+0x66/0x80 [p54common]() (Not tainted)
Date: Wed, 06 Feb 2013 23:51:38 +0000 [thread overview]
Message-ID: <2167973.tjlmlbBDaE@localhost.localdomain> (raw)
In-Reply-To: <201301300106.52229.chunkeey@googlemail.com>
Thanks for getting back Christian,
On Wednesday 30 January 2013 01:06:52 Christian Lamparter wrote:
> Hello,
>
> On Wednesday, January 30, 2013 12:04:38 AM Andrew Wasielewski wrote:
> > I just had the following crash in p54common.
> Yeah, the driver has run out of memory (memory on the device). This
> is most likely caused when the firmware "ceased operations". Sadly,
> the last available firmware from Conexant for the isl3886 is
> 2.13.1.0.lm86.arm (and you probably are using it already :-/ )
Yes, that is my version... :-(
> What's even worse is that neither Conexant nor STE have not and won't
> be providing any new images and the freemac project has stalled as well.
> The Islsm project had a firmware terminal which could be used to debug
> firmware stuff, but it is was never ported.
>
> > The "failed to update LEDs" messages continued until I rebooted - couldn't find
> > a way to reload the stack. O/S is ClearOS Community release 6.3.0 (kernel 2.6.32-279.19.1.v6.i686).
> > Hardware is LinkSys WUSB54G running in AP mode using hostapd, firmware isl3886usb.
> Reloading the driver (modprobe -r p54usb && modprobe p54usb) or replugging the
> device should have helped. Anyway, the clean "reset" procedure for these devices
> is known but to Conexant. If you have sysfs, you can reset a dead usb device
> by toggling (writing 0 and then 1 into) /sys/bus/usb/devices/x-y-z/authorized.
The "authorized" file doesn't exist in my sysfs
> If this helps, we can at least let the driver reset the device automatically
> once it bails out. What do you think?
modprobing p54usb works with the driver, but I still have to restart hostapd for it to pick up the now-working driver. Good news is it hasn't happened again. Unplugging is tricky as I have slightly hacked the WUSB54G to fit inside the case (an old Shuttle mini-PC) with a SMA-RP connector and a decent antenna. In fact the main reason I went for the WUSB54G is because this conversion seemed quite easy. I am open to any suggestions for USB devices with b/g/n(?) support that could be internally mounted in this way, + has AP mode support of course.
>
> Regards,
> Chr
Thanks,
Andrew
next prev parent reply other threads:[~2013-02-06 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 23:04 WARNING: at drivers/net/wireless/p54/main.c:443 p54_work+0x66/0x80 [p54common]() (Not tainted) Andrew Wasielewski
2013-01-30 0:06 ` Christian Lamparter
2013-02-06 23:51 ` Andrew Wasielewski [this message]
2013-02-07 15:57 ` Christian Lamparter
2013-02-12 0:04 ` Andrew Wasielewski
2013-02-13 9:39 ` Christian Lamparter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2167973.tjlmlbBDaE@localhost.localdomain \
--to=andrew@wasielewski.co.uk \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox