From: "Michel Dänzer" <michel@daenzer.net>
To: Meelis Roos <mroos@linux.ee>
Cc: sparclinux@vger.kernel.org, oftedal@gmail.com,
David Miller <davem@davemloft.net>,
dri-devel@lists.freedesktop.org
Subject: Re: PCI Radeon RV100 detection hang on sparc64
Date: Wed, 27 Aug 2014 11:24:44 +0900 [thread overview]
Message-ID: <53FD416C.3060005@daenzer.net> (raw)
In-Reply-To: <alpine.LRH.2.11.1408260954250.4606@siim2.ut.ee>
On 26.08.2014 16:07, Meelis Roos wrote:
>>>> r100 init hangs in a different place. Original dmesg first, then my
>>>> instrumented dmesg (seems to get further):
>>>
>>> The instrumented dmesg had a couple of my local test changes and was
>>> bad now that I had ROM. Reverted them exept my readb changes (instead
>>> of direct dereferences of iomapped space) and redid
>>> logging to be more precise.
>>>
>>>> [drm] radeon kernel modesetting enabled.
>>>> PCI: Enabling device: (0000:02:02.0), cmd 82
>>>> [drm] initializing kernel modesetting (RV100 0x1002:0x5159 0x1002:0x0908).
>>>> [drm] register mmio base: 0x10000000
>>>> [drm] register mmio size: 32768
>>>> [drm:radeon_device_init] *ERROR* Unable to find PCI I/O BAR
>>>
>>> This was still the unchanged kernel hanging.
>>>
>>> Below is a new debug log to pinpoint the hang. It seems to hang in
>>> r100_gfx_get_rptr but not on first try.
>>
>> It's most likely hanging in readl() in r100_mm_rreg() then.
>
> Yes, it is doing direct readl() there. But what does this hang mean?
I'm not sure if the read can hang because of the GPU, or if indicates a
more fundamental PCI issue. Dave?
> By the way, I get these warnings from r100. Seem to be unrelated but
> still worth reporting IMHO:
Looks unrelated indeed.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-27 2:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 14:41 PCI Radeon RV100 detection hang on sparc64 Meelis Roos
2012-09-06 16:51 ` Adam Jackson
2012-09-06 18:15 ` David Miller
2012-09-06 16:55 ` Michel Dänzer
2012-09-06 18:18 ` David Miller
2012-09-07 7:18 ` Dave Airlie
2012-09-19 7:51 ` mroos
2013-09-23 13:48 ` mroos
2013-09-23 19:06 ` Kjetil Oftedal
2013-09-23 20:36 ` David Miller
2013-09-23 21:14 ` mroos
2013-09-23 21:33 ` David Miller
2013-09-24 11:06 ` Meelis Roos
2013-09-25 23:26 ` Meelis Roos
2013-10-01 8:43 ` Meelis Roos
2014-04-04 20:52 ` David Miller
2014-08-13 6:30 ` David Miller
2014-08-19 11:17 ` Meelis Roos
2014-08-25 14:48 ` Meelis Roos
2014-08-26 2:46 ` Michel Dänzer
2014-08-26 7:07 ` Meelis Roos
2014-08-27 2:24 ` Michel Dänzer [this message]
2014-08-30 19:20 ` Kjetil Oftedal
2014-08-31 5:59 ` Meelis Roos
2013-09-23 21:18 ` Meelis Roos
2013-10-10 11:51 ` [PATCH] only try to find radeon IGP ROM on X86 Meelis Roos
2013-10-10 14:38 ` Alex Deucher
2013-10-10 15:26 ` Meelis Roos
2013-10-10 17:02 ` David Miller
2013-10-10 17:10 ` Alex Deucher
2012-09-06 18:08 ` PCI Radeon RV100 detection hang on sparc64 David Miller
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=53FD416C.3060005@daenzer.net \
--to=michel@daenzer.net \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=mroos@linux.ee \
--cc=oftedal@gmail.com \
--cc=sparclinux@vger.kernel.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