linux-mips
[Top] [All Lists]

Re: Patch for the "ug" bug

To: Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: Patch for the "ug" bug
From: Jean-Yves Avenard <jyavenard@gmail.com>
Date: Tue, 7 Jan 2014 22:25:03 +0100
Cc: linux-mips@linux-mips.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/mWy0F0qcJCUBab5WLzOeuo+3Mh1rdqlbeaPtY+lXvk=; b=kvzNtZle1BTJjaHujXvUI1KjjpIiWMDsiFgyjFTymEhFeYlH1hIH3QHBPkbiQB6PLE jnt7xvz4F+OJcPLQ2fbKFlSuX/cXKmiiCz8lo1G+Rx0xLxR936UV/29BioQEsvsBWisG wQGesS+ycBo0DcqvNGBLTnVy+YKYu7JpGSlAuPXh8ak9MH5qJqFB8IThdkOs52Qf+Jb2 55uwvTBi7AiUjAoWf9pwOI9jIamLSAlVeXppbNvg1lThqfw1ObWpi5iiHK0yxKPwJ9oG fYHbq+PTrguuOo4QS9/A14SFxOtEQK5Pve32xy7qv7xBMHA5tTIYr3SOsrM7PDMEYSOr R/dw==
In-reply-to: <52CC5B12.8090305@hauke-m.de>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <CANpj82+h1a0qBfaaYpqmuL69JpbB+T_z0pg0iL=5JPBvDE9A2w@mail.gmail.com> <52CC5B12.8090305@hauke-m.de>
Sender: linux-mips-bounce@linux-mips.org
On 7 January 2014 20:52, Hauke Mehrtens <hauke@hauke-m.de> wrote:

>
> Hi,
>
> this is a little late but I haven't seen this earlier. I just tried your
> script and had no problems on my Asus RT-N66U running OpenWrt with
> kernel 3.10.24. This problem was either cause by some other non upstream
> Broadcom modification or was already fixed in mainline kernel.
>

As you wrote, you're a little late.... about 18 months late...

The issue was in the mips memory management in 2.6.x kernel....
FWIW; all tomato and dd-wrt firmware include this fix.

Now the question is more about weither the fix is in your kernel or not...

<Prev in Thread] Current Thread [Next in Thread>