From: Lauri Hintsala <lauri.hintsala@bluegiga.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [BUGFIX PATCH] video: mxsfb: fix crash when unblanking the display
Date: Fri, 04 Jan 2013 07:08:12 +0000 [thread overview]
Message-ID: <50E67FDC.3000905@bluegiga.com> (raw)
In-Reply-To: <20663.19785.221750.909491@ipc1.ka-ro>
On 11/29/2012 01:55 PM, Lothar Waßmann wrote:
> Hi,
>
> adding Juergen Beisert as the driver's author to the recipient list.
>
> Lothar Waßmann writes:
>> The VDCTRL4 register does not provide the MXS SET/CLR/TOGGLE feature.
>> The write in mxsfb_disable_controller() sets the data_cnt for the LCD
>> DMA to 0 which obviously means the max. count for the LCD DMA and
>> leads to overwriting arbitrary memory when the display is unblanked.
>>
>> Note: I already sent this patch in December 2011 but noone picked it up obviously.
>>
>> Signed-off-by: Lothar Waßmann <LW@KARO-electronics.de>
Tested-by: Lauri Hintsala <lauri.hintsala@bluegiga.net>
This fixes the CPU freezing. I really recommend to apply this patch into
mainline soon because unblanking freezes the whole system!!!
Default value of consoleblank parameter is 600 seconds and the whole
system crashes every time when framebuffer console is activated after
that timeout. I wonder why this issue is still open in mainline kernel.
Should this patch be added into stable versions too?
Best Regards,
Lauri Hintsala
next prev parent reply other threads:[~2013-01-04 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 12:49 [BUGFIX PATCH] video: mxsfb: fix crash when unblanking the display Lothar Waßmann
2012-11-22 12:49 ` [PATCH] video: mxsfb: fix typo: 'FAILING' instead of 'FALLING' Lothar Waßmann
2012-11-29 11:59 ` Lothar Waßmann
2012-11-29 13:42 ` Juergen Beisert
2012-11-29 11:55 ` [BUGFIX PATCH] video: mxsfb: fix crash when unblanking the display Lothar Waßmann
2012-11-29 13:50 ` Juergen Beisert
2013-01-04 7:08 ` Lauri Hintsala [this message]
2013-01-04 7:42 ` Shawn Guo
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=50E67FDC.3000905@bluegiga.com \
--to=lauri.hintsala@bluegiga.com \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).