[Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206112

Andriy Voskoboinyk  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

--- Comment #4 from Andriy Voskoboinyk  ---
Should be fixed in r302035.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206112

Andriy Voskoboinyk  changed:

   What|Removed |Added

 CC||a...@freebsd.org

--- Comment #3 from Andriy Voskoboinyk  ---
Hi,

Is it still reproducible after r302035?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206112

Felix Palmen  changed:

   What|Removed |Added

 CC||fe...@palmen-it.de

--- Comment #2 from Felix Palmen  ---
Hi Simone,
as I'm experiencing the exact same issue here, are there any news? And, could
you please show the patch making it work for you?

TIA, Felix

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206112

--- Comment #1 from Simone Mario Lombardo  ---
A little strange news.

The issue seems arises when the laptop is booted after few hours of being shut
down and it's related to the performance issue I cited; I need to reboot the
machine twice (!) to get nice performance and not getting the error.

I have put three firmware reset in a row in the if_rtwn.c and doubled the wait
time before accessing to the registry after the reset and now the card is
usable after a fresh boot.

I'll test if it is sufficient to keep the wait state longer in the next days or
it needs a "triple" firmware reset.

Simone

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

[Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206112

Bug ID: 206112
   Summary: [rtwn] Under heavy load, "can't map mbuf (error 12)"
arises
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: wireless
  Assignee: freebsd-wireless@FreeBSD.org
  Reporter: evil.lo...@gmail.com
CC: freebsd-am...@freebsd.org
CC: freebsd-am...@freebsd.org

Hi,

I'm testing the rtwn module and under heavy usage (e.g. video streaming) or a
high number of active connections (e.g. multiple browser tabs or P2P), the
interface stops responding in a few minutes and the following message spams
multiple times on the system message buffer.

rtwn0: can't map mbuf (error: 12) 

where 12 I assume it's the error number of ENOMEM.

ifconfig wlan0 down and ifconfig wlan0 up does not reset the interface and the
card still not respond. A full reboot of the machine fixes it.

When those messages appear, trying to resume the stream from the application
issues a kernel panic while trying to unload the module results in a machine
freeze.

I'll take the crash dump, if it's necessary.

With light usage, I can't get the issue.

(I don't know if this relates to the performance issue I have with the module.
The speed seems capped to around 1/3 rather than the full 54mbps rate I got
using the ndis wrapper. I'm opening a separate bug report for that.)

Which information are needed?

Thanks,

Simone

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"