search for: sysfb_simplefb

Hello! I have spent some time on the issue. I'm not sure it's a nouveau bug. I have a fix that changes arch/x86/kernel/sysfb_simplefb.c only. GRUB actually uses graphic mode 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...

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

On 26/09/13 23:37, Pavel Roskin wrote: > Hello! > > I have spent some time on the issue. I'm not sure it's a nouveau bug. > I have a fix that changes arch/x86/kernel/sysfb_simplefb.c only. > > GRUB actually uses graphic mode 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...

...E_BUSY? Or is it related to >> CONFIG_X86_SYSFB? > > CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would > compile without it. create_simplefb() is used in > arch/x86/kernel/sysfb.c that is compiled unconditionally and that > function is defined in arch/x86/kernel/sysfb_simplefb.c that is only > compiled if CONFIG_X86_SYSFB is defined. You can set CONFIG_X86_SYSFB=n and everything works fine. It's the default and is what pre-3.12 kernels always did. > I tried four combinations: with and without IORESOURCE_BUSY and with > and without the PCI resource adjustme...

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

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

...this is related to IORESOURCE_BUSY? Or is it related to > CONFIG_X86_SYSFB? CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would compile without it. create_simplefb() is used in arch/x86/kernel/sysfb.c that is compiled unconditionally and that function is defined in arch/x86/kernel/sysfb_simplefb.c that is only compiled if CONFIG_X86_SYSFB is defined. I tried four combinations: with and without IORESOURCE_BUSY and with and without the PCI resource adjustment. The only combination when nvidiafb probes the hardware is when IORESOURCE_BUSY is not used and the BOOTFP resource is adjusted to m...

...lt;dh.herrmann at gmail.com> wrote: > > CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would > > compile without it. create_simplefb() is used in > > arch/x86/kernel/sysfb.c that is compiled unconditionally and that > > function is defined in arch/x86/kernel/sysfb_simplefb.c that is only > > compiled if CONFIG_X86_SYSFB is defined. > > You can set CONFIG_X86_SYSFB=n and everything works fine. It's the > default and is what pre-3.12 kernels always did. Of course, you are right, I missed sysfb.h. > > I tried four combinations: with and witho...