search for: bootfb

Hello! I'm getting this backtrace every time I boot: resource map sanity check conflict: 0xf0000000 0xf1ffffff 0xf1000000 0xf112bfff BOOTFB ------------[ cut here ]------------ WARNING: CPU: 6 PID: 1 at /home/proskin/src/linux/arch/x86/mm/ioremap.c:171 __ioremap_caller+0x372/0x380() Info: mapping multiple BARs. Your kernel is fine. Modules linked in: CPU: 6 PID: 1 Comm: swapper/0 Not tainted 3.12.0-rc1-00021-g8f98ef7 #28 Hardware name:...

...e on my card. That mode is supported by simplefb. However, the resource conflict happens regardless of whether simplefb is enabled. It's sysfb_simplefb that causes it, a completely different driver. If GRUB keeps the graphic mode, I have this entry in /proc/iomem: f1000000-f112bfff : BOOTFB It is reserved by sysfb_simplefb. Nouveau tries to map an area at 0xf0000000-0xf1ffffff, so it includes the existing resource without being equivalent to it. Nouveau correctly calls remove_conflicting_framebuffers() before trying to map that resource. However, sysfb_simplefb is not a real frame...

...ed by > simplefb. However, the resource conflict happens regardless of whether > simplefb is enabled. It's sysfb_simplefb that causes it, a completely > different driver. > > If GRUB keeps the graphic mode, I have this entry in /proc/iomem: > > f1000000-f112bfff : BOOTFB > > It is reserved by sysfb_simplefb. Nouveau tries to map an area at > 0xf0000000-0xf1ffffff, so it includes the existing resource without > being equivalent to it. > > Nouveau correctly calls remove_conflicting_framebuffers() before trying > to map that resource. However,...

...s 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 req...

...eks 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 &gt...

https://bugs.freedesktop.org/show_bug.cgi?id=69488 Priority: medium Bug ID: 69488 Assignee: nouveau at lists.freedesktop.org Summary: GF108 (NVC1) GPU lockup QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: vekinn at gmail.com Hardware: Other