All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: David Herrmann <dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Resource map sanity check fails after GRUB "keeps" the gfx mode
Date: Wed, 2 Oct 2013 17:46:52 -0400	[thread overview]
Message-ID: <20131002174652.5907a2d0@IRBT4585> (raw)
In-Reply-To: <CANq1E4T6Wa5ReKqBd=-3fDKGs8frMCQ5RQxAOM19C4dnwL_sOA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, 2 Oct 2013 16:47:29 +0200
David Herrmann <dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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

  parent reply	other threads:[~2013-10-02 21:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26  0:07 Resource map sanity check fails after GRUB "keeps" the gfx mode Pavel Roskin
2013-09-26 22:37 ` Pavel Roskin
2013-09-27  9:33   ` Emil Velikov
     [not found]     ` <524550E6.6040909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-27 15:37       ` Pavel Roskin
2013-09-27 18:08         ` David Herrmann
     [not found]           ` <CANq1E4STGCp8X+i-OOd1KYCZQEoUeYuEw8=tkWuXY8_8wcieuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-27 19:40             ` Pavel Roskin
     [not found]               ` <20130927154031.khkhbl17s0ow4sgc-cebfxv-2RFepEojUI3Rd1RZctBqVdHuzzzSOjJt@public.gmane.org>
2013-10-02 14:47                 ` David Herrmann
     [not found]                   ` <CANq1E4T6Wa5ReKqBd=-3fDKGs8frMCQ5RQxAOM19C4dnwL_sOA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-02 21:46                     ` Pavel Roskin [this message]
2013-10-02 22:19                       ` David Herrmann
     [not found]                         ` <CANq1E4TxPg5ZM6WxDZiqi_ZFsY-qqhh8C56aBgSDVKzqt0m2pg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-03 22:10                           ` Pavel Roskin
2013-10-03 23:08                             ` David Herrmann
     [not found]                               ` <CANq1E4Sib6+Z4H3B-DnsB_Eqk4X7ni2Ttj6AgW9gBKcaBf=z6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-04 22:11                                 ` Pavel Roskin
2013-12-18 14:14                                   ` David Herrmann

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=20131002174652.5907a2d0@IRBT4585 \
    --to=proski-mxxj517/zsq@public.gmane.org \
    --cc=dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.