search for: sysfb

...tem 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...

...another approach to pacify the resource checker. >> > >> > However, there is some difference. nvidiafb cannot access the >> > resources if IORESOURCE_BUSY is used. >> >> Are you sure 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...

On Fri, 4 Oct 2013 01:08:34 +0200 David Herrmann <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_SYS...

...finds > the dri device but then bails out with "no devices detected". > > Note: When vga_default_device() is set boot_vga PCI sysfs attribute > reflects its state. When unset this attribute is 1 whenever > IORESOURCE_ROM_SHADOW flag is set. > > With introduction of sysfb/simplefb/simpledrm efifb is getting obsolete > while having native drivers for the GPU also makes selecting > sysfb/efifb optional. > > Remove the efifb implementation of vga_default_device() and initialize > vgaarb's vga_default_device() with the PCI GPU that matches boot >...

...> 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. Are you sure this is related to IORESOURCE_BUSY? Or is it related to CONFIG_X86_SYSFB? Thanks David > 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, > Pa...

...54 49 89 fc 53 48 83 ec 08 <48> 8b 87 88 00 00 00 4c 8b 2f 48 85 c0 74 1b 48 8b b8 90 00 00 [ 657.802514] RIP [<ffffffff813d2af0>] device_del+0x10/0x1b0 [ 657.802520] RSP <ffff88007deff9f8> [ 657.802524] ---[ end trace 11e780c61d88afaf ]--- I'm booting with efi stub and SYSFB=y, FB_SIMPLE=y, DRM_NOUVEAU=m Same config did boot properly with 3.12. Above output contains complete output from the time of calling modprobe nouveau. lspci -nn: 00:00.0 Host bridge [0600]: NVIDIA Corporation MCP79 Host Bridge [10de:0a82] (rev b1) 00:00.1 RAM memory [0500]: NVIDIA Corporation MCP...

....herrmann at gmail.com>: > 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. OK, you are the one who must be better aware of the whole picture, so if the intention is to make the resource busy, that's my first patch and whatever you are trying to push. You still may...

...gt; > 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. > > Are you sure 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 tri...

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 k...

...om>: > >> 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. > > > OK, you are the one who must be better aware of the whole picture, so if the > intention is to make the resource busy, that's my first patch and whatever > you are trying...

...08 <48> 8b 87 88 00 00 00 4c 8b 2f 48 85 c0 74 1b 48 8b b8 90 00 00 > [ 657.802514] RIP [<ffffffff813d2af0>] device_del+0x10/0x1b0 > [ 657.802520] RSP <ffff88007deff9f8> > [ 657.802524] ---[ end trace 11e780c61d88afaf ]--- > > I'm booting with efi stub and SYSFB=y, FB_SIMPLE=y, DRM_NOUVEAU=m > Same config did boot properly with 3.12. Above output contains complete > output from the time of calling modprobe nouveau. Hrm.... that is a separate bug that we should probably figure out. Looks like some use-after-free when nouveau fails to come up (note th...

https://bugs.freedesktop.org/show_bug.cgi?id=77361 Priority: medium Bug ID: 77361 Assignee: nouveau at lists.freedesktop.org Summary: nouveau not working on 3.13 linux kernel QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: sam.halliday at gmail.com