From: Julian Margetson <runaway@candw.ms>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Dave Hansen <dave@sr71.net>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Alex Perez <aperez@alexperez.com>,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: [BUG/REGRESSION] Kernel 4.5-rc1 on Acube Sam460ex AMCC 460ex Power PC motherboards
Date: Thu, 28 Jan 2016 14:21:48 -0400 [thread overview]
Message-ID: <56AA5C3C.1060001@candw.ms> (raw)
In-Reply-To: <CAPcyv4jaHy0R+ZT2h_O94b-eeceeezLP=yTfGguJ+PiB+9g9Ew@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3775 bytes --]
On 1/28/2016 11:47 AM, Dan Williams wrote:
> On Thu, Jan 28, 2016 at 2:41 AM, Julian Margetson <runaway@candw.ms> wrote:
>> On 1/27/2016 3:34 PM, Dan Williams wrote:
>>> On Wed, Jan 27, 2016 at 2:18 AM, Julian Margetson <runaway@candw.ms>
>>> wrote:
>>>> On 1/26/2016 9:43 PM, Dan Williams wrote:
>>>> diff --git a/mm/memory.c b/mm/memory.c
>>>> index 30991f83d0bf..c44e387130b2 100644
>>>> --- a/mm/memory.c
>>>> +++ b/mm/memory.c
>>>> @@ -1521,6 +1521,8 @@ static int insert_pfn(struct vm_area_struct
>>>> *vma, unsigned long addr,
>>>> entry = pte_mkdevmap(pfn_t_pte(pfn, prot));
>>>> else
>>>> entry = pte_mkspecial(pfn_t_pte(pfn, prot));
>>>> + pr_info("%s: entry: %#llx pfn: %#lx\n", __func__,
>>>> + (unsigned long long) entry, pfn_t_to_pfn(pfn));
>>>> set_pte_at(mm, addr, pte, entry);
>>>> update_mmu_cache(vma, addr, pte); /* XXX: why not for
>>>> insert_page? */
>>>>
>>>> ...of course for the passing case you'll need to drop the call to
>>>> pfn_t_to_pfn() and just print the pfn directly.
>>>>
>>>> Thank you for the help tracking this down, it's much appreciated.
>>>>
>>>> Happy to help out. Just need some guidance sometimes as I am relatively
>>>> new
>>>> at this.
>>> No worries.
>>>
>>> So, below is the failing case, what does insert_pfn print in the
>>> passing case? No need for the full log just the first few lines after
>>> starting X when running the commit before this failing one... (commit
>>> 69660fd797c3 "x86, mm: introduce _PAGE_DEVMAP").
>>>
>>> I'm still stumped given that PTE_RPN_SHIFT==PAGE_SHIFT in this
>>> configuration, so there's no 64-bit to 32-bit truncation to worry
>>> about...
>> Having a problem building .
>>
>> CALL scripts/checksyscalls.sh
>> <stdin>:1307:2: warning: #warning syscall copy_file_range not implemented
>> [-Wcpp]
>> CHK include/generated/compile.h
>> CALL arch/powerpc/kernel/systbl_chk.sh
>> CC mm/memory.o
>> CHK kernel/config_data.h
>> mm/memory.c: In function ‘insert_pfn’:
>> mm/memory.c:1520:9: error: implicit declaration of function
>> ‘pfn_t_to_pfn’ [-Werror=implicit-function-declaration]
>> pr_info("%s: entry: %#llx pfn: %#lx\n", __func__,
>> ^
>> mm/memory.c:1520:9: warning: format ‘%lx’ expects argument of type
>> ‘long unsigned int’, but argument 4 has type ‘int’ [-Wformat=]
> Yes, when you go to the preceding commit pfn_t_to_pfn() no longer
> exists. You'll need to change the debug statement to:
>
> pr_info("%s: entry: %#llx pfn: %#lx\n", __func__,
> (unsigned long long) entry, pfn);
>
>
Thank you .
Not getting any debug output .
============================================================================================
/* Ok, finally just insert the thing.. */
entry = pte_mkspecial(pfn_pte(pfn, prot));
pr_info("%s: entry: %#llx pfn: %#lx\n", __func__,
(unsigned long long) entry, pfn);
set_pte_at(mm, addr, pte, entry);
update_mmu_cache(vma, addr, pte); /* XXX: why not for insert_page? */
=============================================================================================
[ 15.622581] systemd[1]: Mounted POSIX Message Queue File System.
[ 15.785050] systemd[1]: Mounting Configuration File System...
[ 15.888907] systemd[1]: Starting Apply Kernel Variables...
[ 15.994762] systemd[1]: Mounting FUSE Control File System...
[ 16.153688] systemd[1]: Mounted FUSE Control File System.
Ubuntu Xenial Xerus (development branch) Sam460ex ttyS0
Sam460ex login:
[-- Attachment #1.2: Type: text/html, Size: 4818 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-28 18:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 23:20 [BUG/REGRESSION] Radeon HDMI casuses oops on Acube Sam460ex amcc 460ex power board Julian Margetson
2015-05-18 16:08 ` Alex Deucher
2015-05-18 17:48 ` Julian Margetson
2015-05-18 20:59 ` Alex Deucher
2015-05-18 22:41 ` Julian Margetson
2015-05-18 23:00 ` Alex Deucher
2015-05-19 0:43 ` Julian Margetson
2015-05-22 11:57 ` Julian Margetson
2015-05-31 11:48 ` Julian Margetson
2015-12-28 15:58 ` [BUG] Radeon TAHITI_vce.bin firmware " Julian Margetson
2016-01-22 0:12 ` [BUG] Radeon TAHITI_vce.bin firmware casuses oops on Acube Sam460ex amcc 460ex and other Power PC motherboards Julian Margetson
2016-01-22 5:15 ` Alex Deucher
2016-01-22 8:17 ` Christian König
2016-01-22 11:06 ` Julian Margetson
2016-01-25 12:46 ` [BUG/REGRESSION] Kernel 4.5-rc1 on Acube Sam460ex AMCC 460ex " Julian Margetson
2016-01-25 19:20 ` Dan Williams
2016-01-25 20:35 ` Julian Margetson
2016-01-27 1:43 ` Dan Williams
2016-01-27 10:18 ` Julian Margetson
2016-01-27 19:34 ` Dan Williams
2016-01-28 10:41 ` Julian Margetson
2016-01-28 15:47 ` Dan Williams
2016-01-28 18:21 ` Julian Margetson [this message]
2016-01-28 18:42 ` Dan Williams
[not found] ` <56A173FA.2090405-zqC88Q5qmK4@public.gmane.org>
2019-01-01 15:03 ` ATI FirePro 2260 doesn't work after the update 'drm-next-2018-12-14' Christian Zigotzky
[not found] ` <845b2222-7014-0211-3246-55d1acc7686b-KCoaydhb8eAb1SvskN2V4Q@public.gmane.org>
2019-01-03 11:03 ` Michel Dänzer
[not found] ` <d62eb7a9-5dd7-8052-6010-63898c51fd05-otUistvHUpPR7s880joybQ@public.gmane.org>
2019-01-03 19:30 ` Christian Zigotzky
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=56AA5C3C.1060001@candw.ms \
--to=runaway@candw.ms \
--cc=aperez@alexperez.com \
--cc=chzigotzky@xenosoft.de \
--cc=dan.j.williams@intel.com \
--cc=dave@sr71.net \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.