All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	David Herrmann
	<dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Resource map sanity check fails after GRUB "keeps" the gfx mode
Date: Fri, 27 Sep 2013 11:37:43 -0400	[thread overview]
Message-ID: <20130927113743.1383f9b5@IRBT4585> (raw)
In-Reply-To: <524550E6.6040909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri, 27 Sep 2013 10:33:26 +0100
Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> FWIW another nvc0 user is experiencing the same/similar issue and the
> patch seems to resolve the problem in his case.
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=69488

Good to hear that my patch actually makes more than cosmetic difference
for somebody.  My system doesn't hang even with the stack trace.  

I posted another patch on the bug page.  It widens the BOOTFB resource
to match the PCI BAR instead of making it busy. With the new patch,
nvidiafb doesn't report that the resource is busy, it reports
unsupported hardware, which is true.

Old patch:
nvidiafb 0000:01:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff
64bit pref]
nvidiafb: cannot request PCI regions

New patch:
nvidiafb: Device ID: 10de0ffc
nvidiafb: unknown NV_ARCH

I'll send the patch to x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, it's clearly not an nvidia issue.

-- 
Regards,
Pavel Roskin

  parent reply	other threads:[~2013-09-27 15:37 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 [this message]
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
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=20130927113743.1383f9b5@IRBT4585 \
    --to=proski-mxxj517/zsq@public.gmane.org \
    --cc=dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=emil.l.velikov-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.