From: lkcl . <luke.leighton@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Fwd: Re: EOMA68-A20 (allwinner sunxi a20) 4.7.0-rc2 ath9k_htc "ath9k_htc: Unable to allocate URBs" issue
Date: Mon, 25 Jul 2016 06:37:23 +0100 [thread overview]
Message-ID: <CAPweEDyONoRPLHs0EGoOtsrMqSR4jKDiqCpNg8Wtx-WPLx1_zg@mail.gmail.com> (raw)
In-Reply-To: <57959E9D.5010205@de.bosch.com>
On Mon, Jul 25, 2016 at 6:07 AM, fixed-term.Oleksij.Rempel
<fixed-term.Oleksij.Rempel@de.bosch.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> hm... take my words back
>
> i reviewed the code, "ath9k_htc: Unable to allocate URBs" may come if
> there is not enough RAM or it is too fragmented. Some other reasons
> can be too, but current code is not verbose enough to provide mode
> information.
eenterestiiing... and this is on a system with 1gb RAM, embedded
system, where i'd started up a full desktop environment.
okay so i should put in a few more printk's at various points, stop
xfce4, and generally try narrowing things down a bit.
l.
prev parent reply other threads:[~2016-07-25 5:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 14:51 [ath9k-devel] EOMA68-A20 (allwinner sunxi a20) 4.7.0-rc2 ath9k_htc "ath9k_htc: Unable to allocate URBs" issue lkcl .
2016-07-24 15:01 ` lkcl .
2016-07-24 15:14 ` lkcl .
2016-07-24 16:16 ` Oleksij Rempel
2016-07-24 18:24 ` lkcl .
2016-07-24 19:18 ` Oleksij Rempel
2016-07-24 19:38 ` lkcl .
2016-07-24 19:40 ` Oleksij Rempel
2016-07-24 19:58 ` lkcl .
[not found] ` <01d3ea7b-6fe3-a77a-1351-6a40d88f061a@rempel-privat.de>
2016-07-25 5:07 ` [ath9k-devel] Fwd: " fixed-term.Oleksij.Rempel
2016-07-25 5:37 ` lkcl . [this message]
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=CAPweEDyONoRPLHs0EGoOtsrMqSR4jKDiqCpNg8Wtx-WPLx1_zg@mail.gmail.com \
--to=luke.leighton@gmail.com \
--cc=ath9k-devel@lists.ath9k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).