> Mind sharing your hostname.ral0 and the tools you use to trigger this
> situation? I've tried hping, tcpbench, ping -f, rsync, etc to no avail.
>
> max ~8000 intr/s with hping
> 2.5MB/s with scp
hostname.ral0 is:
inet 10.2.0.1 255.255.0.0 NONE \
mode 11g \
medi
On Sun, Nov 22, 2009 at 08:31:07PM -0800, Roland Dreier wrote:
> The interrupt handling in ral(4) for RT2661 has a couple of problems,
> which causes the interface to get stuck under heavy load with OACTIVE
> set (the problems are likely especially severe on slow systems such as
> my 600MHz VIA sys
> Does it do anything for 2860? I have that as an AP now and every once in
> a while it stops working, I need to restart the interface.
No, the driver code is a completely different C file. It's possible
there are analogous bugs for 2860 though, since the hardware and
driver are both closely re
On 2009/11/30 20:33, viq wrote:
> On Mon, Nov 30, 2009 at 10:56:29AM -0800, Roland Dreier wrote:
> > Hi Damien / OpenBSD devs,
> >
> > Did anyone get a chance to look at this diff? These fixes are the
> > difference for me between ral being usable as an AP and getting stuck
> > almost immediately
On Mon, Nov 30, 2009 at 10:56:29AM -0800, Roland Dreier wrote:
> Hi Damien / OpenBSD devs,
>
> Did anyone get a chance to look at this diff? These fixes are the
> difference for me between ral being usable as an AP and getting stuck
> almost immediately under heavy load. Is there anything I need
Hi Damien / OpenBSD devs,
Did anyone get a chance to look at this diff? These fixes are the
difference for me between ral being usable as an AP and getting stuck
almost immediately under heavy load. Is there anything I need to do
to get this committed?
Thanks,
Roland
The interrupt handling in ral(4) for RT2661 has a couple of problems,
which causes the interface to get stuck under heavy load with OACTIVE
set (the problems are likely especially severe on slow systems such as
my 600MHz VIA system); bouncing the interface down and back up fixes
things. As I descr
By the way, I forgot to mention that even with this patch applied, I
do have one odd problem with ral on my system -- after some time
(hours it appears), the ral interface stops being able to send
multicasts/broadcasts. All other traffic works fine, including
receiving multicasts, but no multicast
