From: pwalmsley@nvidia.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: "drm: Add reference counting to blob properties" breaks Tegra124 Jetson TK1 in linux-next
Date: Tue, 12 May 2015 09:25:48 -0600 [thread overview]
Message-ID: <55521B7C.3030708@nvidia.com> (raw)
In-Reply-To: <CAPj87rOwzD7-g+GRkGpPXi+ayafmr8E=mbTK3j7cgCAkXCFt2g@mail.gmail.com>
Hi Daniel,
On 05/12/2015 03:06 AM, Daniel Stone wrote:
> Hi Paul,
>
> On 12 May 2015 at 05:00, Paul Walmsley <pwalmsley@nvidia.com> wrote:
>> Tegra124 Jetson TK1 hangs during boot in next-20150508 and beyond:
>>
>> http://nvt.pwsan.com/experimental/linux-next/testlogs/test_next-20150508/20150508101018/boot/tegra124-jetson-tk1/tegra124-jetson-tk1/tegra_defconfig_log.txt
>> http://nvt.pwsan.com/experimental/linux-next/testlogs/test_next-20150511/20150511004533/boot/tegra124-jetson-tk1/tegra124-jetson-tk1/tegra_defconfig_log.txt
>>
>> Reverting commit 672cb1d6aec7da2799afd1b529d5136d84ed2561 ("drm: Add
>> reference counting to blob properties") gets it booting again:
>>
>> http://nvt.pwsan.com/pub/pwalmsley-tester/testlogs/test_20150511204703_3838232431c2636ff539f2354c630c0ca3d4b7ad/20150511204703/boot/tegra124-jetson-tk1/tegra124-jetson-tk1/tegra_defconfig_log.txt
>>
>> I'm not a DRM expert but maybe one of you knows what's going on here?
> Thierry found and fixed the rather stupid bug: not using the cached
> 'dev' variable in the one place it would've been useful!
>
> http://paste.debian.net/175522/ is the fix, which has been squashed in
> to the branch and should appear in -next from today.
>
> Thanks for the report.
Great! Thanks everyone for the very fast fix.
- Paul
prev parent reply other threads:[~2015-05-12 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 4:00 "drm: Add reference counting to blob properties" breaks Tegra124 Jetson TK1 in linux-next Paul Walmsley
2015-05-12 6:33 ` Daniel Stone
2015-05-12 6:37 ` Daniel Vetter
2015-05-12 9:06 ` Daniel Stone
2015-05-12 15:25 ` Paul Walmsley [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=55521B7C.3030708@nvidia.com \
--to=pwalmsley@nvidia.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).