Nouveau - Oct 2013 - Resource map sanity check fails after GRUB "keeps" the gfx mode

Hi Pavel

On Fri, Sep 27, 2013 at 9:40 PM, Pavel Roskin <proski at gnu.org>
wrote:
> Quoting David Herrmann <dh.herrmann at gmail.com>:
>
>> I am aware of this and there is already a fix pending from 2 weeks
>> ago. Unfortunately, I have been in the US for the last 2 weeks and
>> haven't really been able to push on that. Anyhow, it should really
be
>> just a cosmetic issue. We need to mark the sysfb FB as busy to avoid
>> the nasty warnings. Other than that, this shouldn't cause any
issues.
>
>
> OK, you are the one who must be better aware of the whole picture, so if
the
> intention is to make the resource busy, that's my first patch and
whatever
> you are trying to push.
>
> You still may want to have a look at my second patch that widens the
> resource to match an appropriate PCI BAR.
>
> I'm too puzzled why the resource conflict warning causes a GPU lockup
for
> another user.  Maybe it's an unrelated issue.  Also, I don't use
UEFI.  I
> plan to test it eventually if I figure out how to migrate to it without
> reinstalling everything.
Thanks for your investigations. I finally sent my patch and put you on
CC. Sorry for the delay, but I have mostly catched up with all emails
now.

This really just suppresses the warning and nothing else. It does not
fix any lockup/crash/... And your PCI-BAR adjustment doesn't change
anything either, sorry. There is no reason to size the resource
according to PCI tables as it is totally fine to remap partial
segments. resource management is only used for sanity checks and
bookkeeping. If there are real bugs (other than just "Your kernel is
fine." warnings) then we need to bisect them.

Let me know if there are still related issues. I will gladly try to
resolve them.
Thanks!
David

On Wed, 2 Oct 2013 16:47:29 +0200
David Herrmann <dh.herrmann at gmail.com> wrote:
> Thanks for your investigations. I finally sent my patch and put you on
> CC. Sorry for the delay, but I have mostly catched up with all emails
> now.
> 
> This really just suppresses the warning and nothing else.
Thank you for your detailed explanation in the patch.
> It does not
> fix any lockup/crash/...
I know.  I was surprised that my patch fixed something else, but now we
know that it didn't.  It's better when patches don't have unexpected
effects even if the effects are positive :)
> And your PCI-BAR adjustment doesn't change
> anything either, sorry.
I simply tried another approach to pacify the resource checker.

However, there is some difference.  nvidiafb cannot access the
resources if IORESOURCE_BUSY is used.

It's not that it matters for me.  nvidiafb fails on my hardware anyway
and I don't need it when I already have simplefb and nouveau.  But I
think we should have a closer look why it fails and what other drivers
may fail.

-- 
Regards,
Pavel Roskin

Hi Pavel

On Wed, Oct 2, 2013 at 11:46 PM, Pavel Roskin <proski at gnu.org>
wrote:
> On Wed, 2 Oct 2013 16:47:29 +0200
> David Herrmann <dh.herrmann at gmail.com> wrote:
>
>> Thanks for your investigations. I finally sent my patch and put you on
>> CC. Sorry for the delay, but I have mostly catched up with all emails
>> now.
>>
>> This really just suppresses the warning and nothing else.
>
> Thank you for your detailed explanation in the patch.
>
>> It does not
>> fix any lockup/crash/...
>
> I know.  I was surprised that my patch fixed something else, but now we
> know that it didn't.  It's better when patches don't have
unexpected
> effects even if the effects are positive :)
Indeed. And I appreciate your help a lot.
>> And your PCI-BAR adjustment doesn't change
>> anything either, sorry.
>
> I simply tried another approach to pacify the resource checker.
>
> However, there is some difference.  nvidiafb cannot access the
> resources if IORESOURCE_BUSY is used.
Are you sure this is related to IORESOURCE_BUSY? Or is it related to
CONFIG_X86_SYSFB?

Thanks
David
> It's not that it matters for me.  nvidiafb fails on my hardware anyway
> and I don't need it when I already have simplefb and nouveau.  But I
> think we should have a closer look why it fails and what other drivers
> may fail.
>
> --
> Regards,
> Pavel Roskin