From: Larry Finger <Larry.Finger@lwfinger.net>
To: Mario Vietri <m.vietri@sns.it>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Linksys AE3000
Date: Mon, 18 Feb 2013 13:20:18 -0600 [thread overview]
Message-ID: <51227EF2.6040706@lwfinger.net> (raw)
In-Reply-To: <web-120409979@sns.it>
On 02/18/2013 12:03 PM, Mario Vietri wrote:
> Dear Sirs,
>
> I run an up-to-date ArchLinux system on a Toshiba Portege R600. I own a Linksys
> AE3000 (0x13b1:0x003b) usb wifi adapter, with driver downloaded from WikiDevi as
> per their AE3000 page, with the usual modifications.
> The driver compiles, installs and runs correctly, until I begin watching a
> Youtube video, when it causes a kernel panic. I can easily reproduce this crash
> at will, and thus I could submit a kernel panic picture.
>
> I have seen that this behaviour is hardly discussed on Google, and, though not
> completely unknown, it seems to me to be under-reported. I am thus wondering
> whether this has been done already, or if you think might be useful
> to you (and to me, of course). Should it be of any interest to you, could you
> please point me to a page where a list of all required info for proper reporting
> is displayed?
The usual way to report a kernel panic would be to post that photograph.
That said, I'm not aware of anyone here that debugs vendor drivers, i.e. the
ones that are not in the kernel. You will need to look at the cause of the
panic, trace it back to the driver, and try to fix it yourself.
Because the chip in that device is an RT3573, perhaps the rt2x00 developers
might help you, but most of us have other things to do.
Larry
next prev parent reply other threads:[~2013-02-18 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:03 Linksys AE3000 Mario Vietri
2013-02-18 19:20 ` Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-18 19:14 Xose Vazquez Perez
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=51227EF2.6040706@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m.vietri@sns.it \
/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;
as well as URLs for NNTP newsgroup(s).