Hi On Fri, Sep 27, 2013 at 5:37 PM, Pavel Roskin <[email protected]> wrote: > On Fri, 27 Sep 2013 10:33:26 +0100 > Emil Velikov <[email protected]> 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 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. Thanks David > 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 [email protected], it's clearly not an nvidia issue. > > -- > Regards, > Pavel Roskin _______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
