From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ilia Mirkin <imirkin@alum.mit.edu>,
LKML <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>,
jeyu@kernel.org
Subject: Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
Date: Fri, 14 Jul 2017 18:33:01 +0200 [thread overview]
Message-ID: <1500049981.5248.2.camel@gmx.de> (raw)
In-Reply-To: <20170714161027.5htn5jlswvfgphzw@hirez.programming.kicks-ass.net>
On Fri, 2017-07-14 at 18:10 +0200, Peter Zijlstra wrote:
> On Fri, Jul 14, 2017 at 05:58:18PM +0200, Mike Galbraith wrote:
> > On Fri, 2017-07-14 at 17:50 +0200, Peter Zijlstra wrote:
>
> > > Urgh, is for some mysterious reason the __bug_table section of modules
> > > ending up in RO memory?
> > >
> > > I forever get lost in that link magic :/
> >
> > +1
> >
> > drm.ko
> > 20 __bug_table 00000630 0000000000000000 0000000000000000 0004bff3 2**0
> > CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA
> > vmlinux
> > 15 __bug_table 0000ba84 ffffffff81af26c0 0000000001af26c0 00cf26c0 2**0
> > CONTENTS, ALLOC, LOAD, READONLY, DATA
> >
> > Danged if I know... um um RELOC business mucks things up?
>
> Argh, it shouldn't be READONLY for vmlinux either, but apparently that
> is working for mysterious reasons.
>
> Some architectures were in fact complaining that I broke that, and hence
> patch:
>
> b5effd3815cc ("debug: Fix __bug_table[] in arch linker scripts")
>
> I think we need professional help with this linking stuff, but who to
> ask?
Andy Lutomirski?
next prev parent reply other threads:[~2017-07-14 16:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 17:32 [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith
2017-07-11 17:51 ` Ilia Mirkin
2017-07-11 18:08 ` Mike Galbraith
2017-07-11 18:22 ` Ilia Mirkin
2017-07-11 18:53 ` Mike Galbraith
2017-07-12 7:45 ` Mike Galbraith
2017-07-12 9:55 ` Mike Galbraith
2017-07-12 11:25 ` Mike Galbraith
2017-07-12 11:37 ` Ilia Mirkin
2017-07-12 17:19 ` Mike Galbraith
2017-07-12 19:33 ` Tobias Klausmann
2017-07-14 13:36 ` Mike Galbraith
2017-07-14 13:41 ` Mike Galbraith
2017-07-14 15:05 ` Tobias Klausmann
2017-07-14 15:10 ` [Nouveau] " Karol Herbst
2017-07-14 15:15 ` Mike Galbraith
2017-07-14 15:16 ` Ilia Mirkin
2017-07-14 15:19 ` Tobias Klausmann
2017-07-14 15:20 ` Ilia Mirkin
2017-07-14 15:55 ` Peter Zijlstra
2017-07-14 15:11 ` Mike Galbraith
2017-07-14 15:50 ` Peter Zijlstra
2017-07-14 15:58 ` Mike Galbraith
2017-07-14 16:10 ` Peter Zijlstra
2017-07-14 16:33 ` Mike Galbraith [this message]
2017-07-14 19:42 ` Josh Poimboeuf
2017-07-15 2:45 ` Mike Galbraith
2017-07-17 17:20 ` Jessica Yu
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=1500049981.5248.2.camel@gmx.de \
--to=efault@gmx.de \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=peterz@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