From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: vexpress: Check master site in daughterboard's sysctl operations
Date: Tue, 12 Jun 2012 14:02:37 +0100 [thread overview]
Message-ID: <1339506157.3063.37.camel@linaro1.home> (raw)
In-Reply-To: <1339491487.3063.23.camel@linaro1.home>
On Tue, 2012-06-12 at 09:58 +0100, Jon Medhurst (Tixy) wrote:
> On Fri, 2012-06-08 at 13:50 +0100, Pawel Moll wrote:
> > With recent enough motherboard firmware, core tile can be fitted
> > in either of the two daughterboard sites. The non-DT tile code for
> > V2P-CA9 did not check that when configuring DVI output nor setting
> > CLCD pixel clock.
> >
> > Fixed now, providing "get master site" API in motherboard's code.
> >
> > Signed-off-by: Pawel Moll <pawel.moll@arm.com>
>
> This patch makes an Ubuntu boot always hang for me, about the time it
> would switch to GUI mode, it's not very consistent unfortunately.
I've found the cause of the problem, v2m_get_master_site() is marked
__init but is used by the non __init function ct_ca9x4_clcd_enable(). So
when Ubuntu GUI startup messes with the display it ends up calling into
freed memory.
Dropping __init from ct_ca9x4_clcd_enable() fixes my boot failures.
--
Tixy
prev parent reply other threads:[~2012-06-12 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 12:50 [PATCH 1/2] ARM: vexpress: Check master site in daughterboard's sysctl operations Pawel Moll
2012-06-08 12:50 ` [PATCH 2/2] ARM: vexpress: Initial common clock support Pawel Moll
2012-06-13 10:07 ` Jon Medhurst (Tixy)
2012-06-12 8:58 ` [PATCH 1/2] ARM: vexpress: Check master site in daughterboard's sysctl operations Jon Medhurst (Tixy)
2012-06-12 9:08 ` Pawel Moll
2012-06-12 13:02 ` Jon Medhurst (Tixy) [this message]
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=1339506157.3063.37.camel@linaro1.home \
--to=tixy@linaro.org \
--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).