All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Pecio" <michal.pecio@gmail.com>
To: rtl8821cerfe2@gmail.com
Cc: linux-wireless@vger.kernel.org, pkshih@realtek.com,
	sha@pengutronix.de, Kalle Valo <kvalo@kernel.org>
Subject: Re: rtw88: alloc_skb(32768, GFP_ATOMIC) fails, driver gets stuck
Date: Sun, 6 Oct 2024 17:43:31 +0200	[thread overview]
Message-ID: <20241006174331.1c4e6640@foxbook> (raw)
In-Reply-To: <baca0d5d-072e-4003-ab4a-ecc524d6b89b@gmail.com>

Hi,

> I have this problem with RTL8811CU, RTL8723DU, RTL8811AU, RTL8812AU.

Does it mean there are working patches for 8811AU somewhere?
I have this damn thing, lying unused because unsupported.

> The host controller died when I unplugged another device

xhci not responding, assume dead?
Yuck. Maybe linux-usb should hear about it if it's reproducible.

> alloc_skb fails (silently) therefore the RX URB is not submitted
> ever again. There are only 4 RX URBs.

drivers/net/usb/usbnet.c::rx_submit() deals with it by queuing a work
to resubmit the URB later using blocking allocations.

Failure of usb_submit_urb() is handled same way. This too can return
-ENOMEM, on xhci for example.

Regards,
Michal

  parent reply	other threads:[~2024-10-06 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 11:46 rtw88: USB devices randomly stop receiving anything Bitterblue Smith
2024-09-26 13:04 ` petter
2024-09-26 16:51   ` Bitterblue Smith
2024-09-27  6:44     ` petter
2024-09-29 11:43 ` Bitterblue Smith
2024-09-30 20:56 ` rtw88: alloc_skb(32768, GFP_ATOMIC) fails, driver gets stuck Bitterblue Smith
2024-10-01  1:25   ` Ping-Ke Shih
2024-10-07 22:03     ` Bitterblue Smith
2024-10-02 10:58   ` Kalle Valo
2024-10-03  4:26     ` Ping-Ke Shih
2024-10-06 15:43   ` Michał Pecio [this message]
2024-10-07 22:04     ` Bitterblue Smith

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=20241006174331.1c4e6640@foxbook \
    --to=michal.pecio@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=rtl8821cerfe2@gmail.com \
    --cc=sha@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.