linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 16 Feb 2012 07:28:10 +1100 Benjamin Herrenschmidt wrote: > On Wed, 2012-02-15 at 08:39 +0100, Michel D?nzer wrote: > > > > > Btw, to sum up the list of Power Architecture machines with > > > > PCIE that aim to be a desktop/workstation: Apple iMac G5 > > > > (iSight), Apple PowerMac Quad G5, YDL Powerstation 2x970MP and > > > > Acube Sam460ex . And the last two, on present evidence (my > > > > attempts), aren't able to boot up if bootkernel has kms enabled. > > > > > > Which radeon card, kernel log please ? > > > > See > > http://lists.freedesktop.org/archives/dri-devel/2012-February/018792.html > > (start of this thread) and > > http://lists.freedesktop.org/archives/dri-devel/2012-February/018791.html . > > Ok, so for the 460EX, I am not surprised things aren't working with > KMS & DRI2... the 460 is not cache coherent, and this is not handled > by TTM as far as I can tell. > > The second case with no firmware is a bit more surprising, looks like > something bad happened on the PCI express bus or the kernel tried to > access something that the card rejected (target abort or PCIe > equivalent most likely), thus triggering a PLB error . That could be > investigated a bit more. > > Note that you say this is smoe kind of "SAM460EX" card... but it > claims to be a Canyonlands in the device-tree... is that expected or > do we have yet another case of a vendor claiming to be the eval board > they based their design upon and generally screwing up in a major > way ? IE. does it indeed work with an -identical- device-tree to a > canyonland and no patches added to the machine support at all ? > Guys, thank you very much for your replies, i know it's a very common (bad) scenario, thanks for your opinion i already informed the vendor to suggest a _real_ linux kernel porting and i'll do it again. Anyway after nearly ten years, due a lack in resources, i'm sadly going to suspend the CRUX PPC project and my activism pro free software thus i'm unable to follow these debug. I'll hold on to me the only YDL Powerstation then from the next weeks i'll can only follow trying to help in debug [1] on this specific machine. [1]http://lists.freedesktop.org/archives/dri-devel/2012-January/018575.html all the best and again THANKS for all your work, - --nico - -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk88VnEACgkQxq34tDeO7Lg1NQCgkcHSqVxtJ2pfw2x+fyyuTLpx llMAn1h0szhNtxusxjCsBzjj5LQ/v6VZ =Uszy -END PGP SIGNATURE-
Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 16 Feb 2012 07:28:10 +1100 Benjamin Herrenschmidt wrote: > On Wed, 2012-02-15 at 08:39 +0100, Michel Dänzer wrote: > > > > > Btw, to sum up the list of Power Architecture machines with > > > > PCIE that aim to be a desktop/workstation: Apple iMac G5 > > > > (iSight), Apple PowerMac Quad G5, YDL Powerstation 2x970MP and > > > > Acube Sam460ex . And the last two, on present evidence (my > > > > attempts), aren't able to boot up if bootkernel has kms enabled. > > > > > > Which radeon card, kernel log please ? > > > > See > > http://lists.freedesktop.org/archives/dri-devel/2012-February/018792.html > > (start of this thread) and > > http://lists.freedesktop.org/archives/dri-devel/2012-February/018791.html . > > Ok, so for the 460EX, I am not surprised things aren't working with > KMS & DRI2... the 460 is not cache coherent, and this is not handled > by TTM as far as I can tell. > > The second case with no firmware is a bit more surprising, looks like > something bad happened on the PCI express bus or the kernel tried to > access something that the card rejected (target abort or PCIe > equivalent most likely), thus triggering a PLB error . That could be > investigated a bit more. > > Note that you say this is smoe kind of "SAM460EX" card... but it > claims to be a Canyonlands in the device-tree... is that expected or > do we have yet another case of a vendor claiming to be the eval board > they based their design upon and generally screwing up in a major > way ? IE. does it indeed work with an -identical- device-tree to a > canyonland and no patches added to the machine support at all ? > Guys, thank you very much for your replies, i know it's a very common (bad) scenario, thanks for your opinion i already informed the vendor to suggest a _real_ linux kernel porting and i'll do it again. Anyway after nearly ten years, due a lack in resources, i'm sadly going to suspend the CRUX PPC project and my activism pro free software thus i'm unable to follow these debug. I'll hold on to me the only YDL Powerstation then from the next weeks i'll can only follow trying to help in debug [1] on this specific machine. [1]http://lists.freedesktop.org/archives/dri-devel/2012-January/018575.html all the best and again THANKS for all your work, - --nico - -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk88VnEACgkQxq34tDeO7Lg1NQCgkcHSqVxtJ2pfw2x+fyyuTLpx llMAn1h0szhNtxusxjCsBzjj5LQ/v6VZ =Uszy -END PGP SIGNATURE- ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
On Sun, 12 Feb 2012 11:00:43 +0100 Michel D?nzer wrote: > On Sam, 2012-02-11 at 21:00 +0100, acrux wrote: > > > > Just a curiosity, i've only two powerpc machines[1] equipped with PCIE > > videocards and both them are not able to boot with radeonkms. > > Modern PCI-E videocards are not recognized by the old linux framebuffer > > subsystem and they solely can be managed by the new KMS frame buffer > > that doesn't work properly on Power Architecture. > > That's too broad a statement, it works fine on other PowerPC machines > (PowerMacs, some embedded boards). > hi Michel, thanks a lot for your help, i really appreciate it. If you say they were tested on real Power Architecture boards with PCIE videocards thus it is reassuring... and i'm happy that you understand my previus assertion wasn't affected by malevolence or sarcasm. Indeed i'm also a bit troubled 'n frustrated thinking that next release of mesa 'll do extend use of llvm (that doesn't work properly on linuxppc and totally untested on linuxppc64) Btw, to sum up the list of Power Architecture machines with PCIE that aim to be a desktop/workstation: Apple iMac G5 (iSight), Apple PowerMac Quad G5, YDL Powerstation 2x970MP and Acube Sam460ex . And the last two, on present evidence (my attempts), aren't able to boot up if bootkernel has kms enabled. Furthermore the first tree ones can fallback to the legacy OpenFirmware framebuffer and safely get a console. > It looks like there's a problem with accessing the PCIe device memory, > and at this point it's not even 100% clear that this is due to a problem > in the driver, as opposed to e.g. in the platform code. > it could be the right problem and i've CC BenH that has a better global perspective. all the best, --nico -- acrux
Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
On Sun, 12 Feb 2012 11:00:43 +0100 Michel Dänzer wrote: > On Sam, 2012-02-11 at 21:00 +0100, acrux wrote: > > > > Just a curiosity, i've only two powerpc machines[1] equipped with PCIE > > videocards and both them are not able to boot with radeonkms. > > Modern PCI-E videocards are not recognized by the old linux framebuffer > > subsystem and they solely can be managed by the new KMS frame buffer > > that doesn't work properly on Power Architecture. > > That's too broad a statement, it works fine on other PowerPC machines > (PowerMacs, some embedded boards). > hi Michel, thanks a lot for your help, i really appreciate it. If you say they were tested on real Power Architecture boards with PCIE videocards thus it is reassuring... and i'm happy that you understand my previus assertion wasn't affected by malevolence or sarcasm. Indeed i'm also a bit troubled 'n frustrated thinking that next release of mesa 'll do extend use of llvm (that doesn't work properly on linuxppc and totally untested on linuxppc64) Btw, to sum up the list of Power Architecture machines with PCIE that aim to be a desktop/workstation: Apple iMac G5 (iSight), Apple PowerMac Quad G5, YDL Powerstation 2x970MP and Acube Sam460ex . And the last two, on present evidence (my attempts), aren't able to boot up if bootkernel has kms enabled. Furthermore the first tree ones can fallback to the legacy OpenFirmware framebuffer and safely get a console. > It looks like there's a problem with accessing the PCIe device memory, > and at this point it's not even 100% clear that this is due to a problem > in the driver, as opposed to e.g. in the platform code. > it could be the right problem and i've CC BenH that has a better global perspective. all the best, --nico -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
On Tue, 07 Feb 2012 18:32:44 +0100 Michel D?nzer wrote: > On Son, 2012-02-05 at 00:38 +0100, acrux wrote: > > > > unable to have a working radeon kms framebuffer with linux-3.3-rc2 > > on ppc video card: Radeon X1650PRO PCIE > > Is this a regression? If yes, can you bisect? > not a regression, i didn't find a working kernel release > > > [drm] GART: num cpu pages 131072, num gpu pages 131072 > > The driver detects the CPU page size as 4K, is that correct? > > it's right, 4k page size Just a curiosity, i've only two powerpc machines[1] equipped with PCIE videocards and both them are not able to boot with radeonkms. Modern PCI-E videocards are not recognized by the old linux framebuffer subsystem and they solely can be managed by the new KMS frame buffer that doesn't work properly on Power Architecture. Anyway, YDL Powerstation can fallback to use the old OpenFirmware frame buffer. KMS porting to Power Architecture machines with PCIE is it only an exercise or someone is also able to test them? Because i can understand that the userbase is non-existent and the dri-developers don't have these "rare" machines. [1] YDL Powerstation, Acube Sam460ex cheers, --nico -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/
linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon 9250 pci
On Tue, 07 Feb 2012 19:01:04 +0100 Michel D?nzer wrote: > On Son, 2012-02-05 at 00:41 +0100, acrux wrote: > > unable to have a working radeon kms framebuffer with linux-3.3-rc2 > > on ppc video card: Radeon 9250 PCI > > Is this a regression? If yes, can you bisect? > not a regression, i didn't find a working kernel release > > > Machine check in kernel mode. > > Data Write PLB Error > > Machine Check exception is imprecise > > Oops: Machine check, sig: 7 [#1] > > Canyonlands > > Modules linked in: > > NIP: c000a580 LR: c0399084 CTR: 000bfffb > > REGS: efff7f10 TRAP: 0214 Not tainted (3.3.0-rc2) > > MSR: 00029000 CR: 24714222 XER: > > TASK = ef83[1] 'swapper' THREAD: ef834000 > > GPR00: ef835c30 ef83 f550 0030 > > ef835bd8 GPR08: ef835b38 f5500014 000c0001 > > 24714284 8500682f ef8f7800 ef17c1c0 GPR16: 0020 c05f > > c06105de ef835d08 c0610351 c056a6f0 c0610600 GPR24: > > fff4 ef8ca47c ef9ffe00 ef9fff38 ef9e7c00 ef835cb8 ef8ea000 > > ef8ca400 NIP [c000a580] _memset_io+0x54/0x90 LR [c0399084] > > radeon_fb_find_or_create_single+0x234/0x42c Call Trace: > > [ef835c30] [c0399068] radeon_fb_find_or_create_single+0x218/0x42c > > (unreliable) > > Again looks like the problem occurs when first accessing VRAM, in this > case for clearing the visible framebuffer contents. > > I wonder if we're missing something to handle device memory access > properly on your machine(s)... Is ioremap_wc() working on them with > other drivers? > > i got a kernel panic also with the legacy radeon framebuffer -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/
Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
On Tue, 07 Feb 2012 18:32:44 +0100 Michel Dänzer wrote: > On Son, 2012-02-05 at 00:38 +0100, acrux wrote: > > > > unable to have a working radeon kms framebuffer with linux-3.3-rc2 > > on ppc video card: Radeon X1650PRO PCIE > > Is this a regression? If yes, can you bisect? > not a regression, i didn't find a working kernel release > > > [drm] GART: num cpu pages 131072, num gpu pages 131072 > > The driver detects the CPU page size as 4K, is that correct? > > it's right, 4k page size Just a curiosity, i've only two powerpc machines[1] equipped with PCIE videocards and both them are not able to boot with radeonkms. Modern PCI-E videocards are not recognized by the old linux framebuffer subsystem and they solely can be managed by the new KMS frame buffer that doesn't work properly on Power Architecture. Anyway, YDL Powerstation can fallback to use the old OpenFirmware frame buffer. KMS porting to Power Architecture machines with PCIE is it only an exercise or someone is also able to test them? Because i can understand that the userbase is non-existent and the dri-developers don't have these "rare" machines. [1] YDL Powerstation, Acube Sam460ex cheers, --nico -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon 9250 pci
On Tue, 07 Feb 2012 19:01:04 +0100 Michel Dänzer wrote: > On Son, 2012-02-05 at 00:41 +0100, acrux wrote: > > unable to have a working radeon kms framebuffer with linux-3.3-rc2 > > on ppc video card: Radeon 9250 PCI > > Is this a regression? If yes, can you bisect? > not a regression, i didn't find a working kernel release > > > Machine check in kernel mode. > > Data Write PLB Error > > Machine Check exception is imprecise > > Oops: Machine check, sig: 7 [#1] > > Canyonlands > > Modules linked in: > > NIP: c000a580 LR: c0399084 CTR: 000bfffb > > REGS: efff7f10 TRAP: 0214 Not tainted (3.3.0-rc2) > > MSR: 00029000 CR: 24714222 XER: > > TASK = ef83[1] 'swapper' THREAD: ef834000 > > GPR00: ef835c30 ef83 f550 0030 > > ef835bd8 GPR08: ef835b38 f5500014 000c0001 > > 24714284 8500682f ef8f7800 ef17c1c0 GPR16: 0020 c05f > > c06105de ef835d08 c0610351 c056a6f0 c0610600 GPR24: > > fff4 ef8ca47c ef9ffe00 ef9fff38 ef9e7c00 ef835cb8 ef8ea000 > > ef8ca400 NIP [c000a580] _memset_io+0x54/0x90 LR [c0399084] > > radeon_fb_find_or_create_single+0x234/0x42c Call Trace: > > [ef835c30] [c0399068] radeon_fb_find_or_create_single+0x218/0x42c > > (unreliable) > > Again looks like the problem occurs when first accessing VRAM, in this > case for clearing the visible framebuffer contents. > > I wonder if we're missing something to handle device memory access > properly on your machine(s)... Is ioremap_wc() working on them with > other drivers? > > i got a kernel panic also with the legacy radeon framebuffer -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon 9250 pci
unable to have a working radeon kms framebuffer with linux-3.3-rc2 on ppc video card: Radeon 9250 PCI here the boot log: Using Canyonlands machine description Initializing cgroup subsys cpu Linux version 3.3.0-rc2 (root at sam460) (gcc version 4.5.3 (CRUX PPC) ) #2 Sat Feb 4 20:34:21 CET 2012 Zone PFN ranges: DMA 0x -> 0x0003 Normal empty HighMem 0x0003 -> 0x0008 Movable zone start PFN for each node Early memory PFN ranges 0: 0x -> 0x0008 MMU: Allocated 1088 bytes of context maps for 255 contexts Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520192 Kernel command line: root=/dev/sda3 ro video=800x600 console=tty0 console=ttyS0,115200 udbg-immortal PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 2072736k/2097152k available (6772k kernel code, 24416k reserved, 188k data, 143k bss, 196k init) Kernel virtual memory layout: * 0xfffcf000..0xf000 : fixmap * 0xffc0..0xffe0 : highmem PTEs * 0xffa0..0xffc0 : consistent mem * 0xffa0..0xffa0 : early ioremap * 0xf100..0xffa0 : vmalloc & ioremap SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:512 nr_irqs:512 16 UIC0 (32 IRQ sources) at DCR 0xc0 UIC1 (32 IRQ sources) at DCR 0xd0 UIC2 (32 IRQ sources) at DCR 0xe0 UIC3 (32 IRQ sources) at DCR 0xf0 clocksource: timebase mult[db6db7] shift[24] registered Console: colour dummy device 80x25 console [tty0] enabled pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 devtmpfs: initialized NET: Registered protocol family 16 256k L2-cache enabled PCIE0: Port disabled via device-tree PCIE1: Checking link... PCIE1: No device detected. PCI host bridge /plb/pciex at d2000 (primary) ranges: MEM 0x000e8000..0x000e -> 0x8000 MEM 0x000f0010..0x000f001f -> 0x IO 0x000f8001..0x000f8001 -> 0x Removing ISA hole at 0x000f0010 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pciex at d2000: Legacy ISA memory support enabled PCIE1: successfully set as root-complex PCI host bridge /plb/pci at c0ec0 (primary) ranges: MEM 0x000d8000..0x000d -> 0x8000 MEM 0x000c0ee0..0x000c0eef -> 0x IO 0x000c0800..0x000c0800 -> 0x Removing ISA hole at 0x000c0ee0 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pci at c0ec0: Legacy ISA memory support enabled gpiochip_add: registered GPIOs 224 to 255 on device: /plb/opb/gpio at ef600b00 PCI: Probing PCI hardware PCI host bridge to bus :80 pci_bus :80: root bus resource [io 0xfffe-0xfffe] pci_bus :80: root bus resource [mem 0xe8000-0xe] PCI: Hiding 4xx host bridge resources :80:00.0 pci :80:00.0: PCI bridge to [bus 81-bf] PCI host bridge to bus 0001:00 pci_bus 0001:00: root bus resource [io 0x-0x] pci_bus 0001:00: root bus resource [mem 0xd8000-0xd] pci :80:00.0: PCI bridge to [bus 81-bf] pci 0001:00:04.0: BAR 0: assigned [mem 0xd8000-0xd87ff pref] pci 0001:00:04.1: BAR 0: assigned [mem 0xd8800-0xd8fff pref] pci 0001:00:06.0: BAR 0: assigned [mem 0xd9000-0xd93ff] pci 0001:00:06.0: BAR 1: assigned [mem 0xd9400-0xd941f] pci 0001:00:04.0: BAR 6: assigned [mem 0xd9420-0xd9421 pref] pci 0001:00:04.0: BAR 2: assigned [mem 0xd9422-0xd9422] pci 0001:00:04.1: BAR 1: assigned [mem 0xd9423-0xd9423] pci 0001:00:04.0: BAR 1: assigned [io 0x1000-0x10ff] bio: create slab at 0 vgaarb: device added: PCI:0001:00:04.0,decodes=io+mem,owns=io+mem,locks=none vgaarb: loaded vgaarb: bridge control possible 0001:00:04.0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Switching to clocksource timebase NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered UDP hash table entries: 512 (order: 1, 8192 bytes) UDP-Lite hash table entries: 512 (order: 1, 8192 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. Could not remap bcsr setting trigger mode 3 for irq 43 failed (uic_set_irq_type+0x0/0x164) setti
linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
On Fri, 3 Feb 2012 02:56:18 +0100 acrux wrote: unable to have a working radeon kms framebuffer with linux-3.3-rc2 on ppc video card: Radeon X1650PRO PCIE here the boot log: U-Boot 2010.06.05 (Jul 05 2011 - 17:53:34) CPU: AMCC PowerPC 460EX Rev. B at 1166.667 MHz (PLB=233 OPB=116 EBC=116) No Security/Kasumi support Bootstrap Option H - Boot ROM Location I2C (Addr 0x52) Internal PCI arbiter enabled 32 kB I-Cache 32 kB D-Cache Board: Sam460ex, PCIe 4x + SATA-2 I2C: ready DRAM: 2 GiB (ECC not enabled, 466 MHz, CL4) PCI: Bus Dev VenId DevId Class Int 00 06 126f 0501 0380 00 PCIE1: successfully set as root-complex 02 00 1002 71c1 0300 ff Net: ppc_4xx_eth0 FPGA: Revision 03 (2010-10-07) SM502: found VGA: 1 VESA: OK Using Canyonlands machine description Initializing cgroup subsys cpu Linux version 3.3.0-rc2 (root at sam460) (gcc version 4.5.3 (CRUX PPC) ) #2 Sat Feb 4 20:34:21 CET 2012 Zone PFN ranges: DMA 0x -> 0x0003 Normal empty HighMem 0x0003 -> 0x0008 Movable zone start PFN for each node Early memory PFN ranges 0: 0x -> 0x0008 MMU: Allocated 1088 bytes of context maps for 255 contexts Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520192 Kernel command line: root=/dev/sda3 ro video=800x600 console=tty0 console=ttyS0,115200 udbg-immortal PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 2072736k/2097152k available (6772k kernel code, 24416k reserved, 188k data, 143k bss, 196k init) Kernel virtual memory layout: * 0xfffcf000..0xf000 : fixmap * 0xffc0..0xffe0 : highmem PTEs * 0xffa0..0xffc0 : consistent mem * 0xffa0..0xffa0 : early ioremap * 0xf100..0xffa0 : vmalloc & ioremap SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:512 nr_irqs:512 16 UIC0 (32 IRQ sources) at DCR 0xc0 UIC1 (32 IRQ sources) at DCR 0xd0 UIC2 (32 IRQ sources) at DCR 0xe0 UIC3 (32 IRQ sources) at DCR 0xf0 clocksource: timebase mult[db6db7] shift[24] registered Console: colour dummy device 80x25 console [tty0] enabled pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 devtmpfs: initialized NET: Registered protocol family 16 256k L2-cache enabled PCIE0: Port disabled via device-tree PCIE1: Checking link... PCIE1: Device detected, waiting for link... PCIE1: link is up ! PCI host bridge /plb/pciex at d2000 (primary) ranges: MEM 0x000e8000..0x000e -> 0x8000 MEM 0x000f0010..0x000f001f -> 0x IO 0x000f8001..0x000f8001 -> 0x Removing ISA hole at 0x000f0010 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pciex at d2000: Legacy ISA memory support enabled PCIE1: successfully set as root-complex PCI host bridge /plb/pci at c0ec0 (primary) ranges: MEM 0x000d8000..0x000d -> 0x8000 MEM 0x000c0ee0..0x000c0eef -> 0x IO 0x000c0800..0x000c0800 -> 0x Removing ISA hole at 0x000c0ee0 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pci at c0ec0: Legacy ISA memory support enabled gpiochip_add: registered GPIOs 224 to 255 on device: /plb/opb/gpio at ef600b00 PCI: Probing PCI hardware PCI host bridge to bus :80 pci_bus :80: root bus resource [io 0xfffe-0xfffe] pci_bus :80: root bus resource [mem 0xe8000-0xe] PCI: Hiding 4xx host bridge resources :80:00.0 pci :81:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' pci :80:00.0: PCI bridge to [bus 81-bf] PCI host bridge to bus 0001:00 pci_bus 0001:00: root bus resource [io 0x-0x] pci_bus 0001:00: root bus resource [mem 0xd8000-0xd] pci :80:00.0: BAR 15: assigned [mem 0xe8000-0xe97ff pref] pci :80:00.0: BAR 14: assigned [mem 0xe9800-0xe980f] pci :80:00.0: BAR 13: assigned [io 0xfffe1000-0xfffe1fff] pci :81:00.0: BAR 0: assigned [mem 0xe8000-0xe8fff 64bit pref] pci :81:00.0: BAR 6: assigned [mem 0xe9000-0xe9001 pref] pci :81:00.0: BAR 2: assigned [mem 0xe9800-0xe9800 64bit] pci :81:00.1: BAR 0: assigned [mem 0xe9801-0xe9801 64bit] pci :81:00.0: BAR 4: assigned [io 0xfffe1000-0xfffe10ff] pci :80:00.0: PCI bridge to [bus 81-bf] pci :80:00.0: bridge window [io 0xfffe1000-0xfffe1fff] pci :80:00.0: bridge window [mem 0xe9800-0xe980f] pci :80:00.0: bridge window [mem 0xe8000-0xe97ff pref] pci 0001:
Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon 9250 pci
unable to have a working radeon kms framebuffer with linux-3.3-rc2 on ppc video card: Radeon 9250 PCI here the boot log: Using Canyonlands machine description Initializing cgroup subsys cpu Linux version 3.3.0-rc2 (root@sam460) (gcc version 4.5.3 (CRUX PPC) ) #2 Sat Feb 4 20:34:21 CET 2012 Zone PFN ranges: DMA 0x -> 0x0003 Normal empty HighMem 0x0003 -> 0x0008 Movable zone start PFN for each node Early memory PFN ranges 0: 0x -> 0x0008 MMU: Allocated 1088 bytes of context maps for 255 contexts Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520192 Kernel command line: root=/dev/sda3 ro video=800x600 console=tty0 console=ttyS0,115200 udbg-immortal PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 2072736k/2097152k available (6772k kernel code, 24416k reserved, 188k data, 143k bss, 196k init) Kernel virtual memory layout: * 0xfffcf000..0xf000 : fixmap * 0xffc0..0xffe0 : highmem PTEs * 0xffa0..0xffc0 : consistent mem * 0xffa0..0xffa0 : early ioremap * 0xf100..0xffa0 : vmalloc & ioremap SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:512 nr_irqs:512 16 UIC0 (32 IRQ sources) at DCR 0xc0 UIC1 (32 IRQ sources) at DCR 0xd0 UIC2 (32 IRQ sources) at DCR 0xe0 UIC3 (32 IRQ sources) at DCR 0xf0 clocksource: timebase mult[db6db7] shift[24] registered Console: colour dummy device 80x25 console [tty0] enabled pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 devtmpfs: initialized NET: Registered protocol family 16 256k L2-cache enabled PCIE0: Port disabled via device-tree PCIE1: Checking link... PCIE1: No device detected. PCI host bridge /plb/pciex@d2000 (primary) ranges: MEM 0x000e8000..0x000e -> 0x8000 MEM 0x000f0010..0x000f001f -> 0x IO 0x000f8001..0x000f8001 -> 0x Removing ISA hole at 0x000f0010 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pciex@d2000: Legacy ISA memory support enabled PCIE1: successfully set as root-complex PCI host bridge /plb/pci@c0ec0 (primary) ranges: MEM 0x000d8000..0x000d -> 0x8000 MEM 0x000c0ee0..0x000c0eef -> 0x IO 0x000c0800..0x000c0800 -> 0x Removing ISA hole at 0x000c0ee0 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pci@c0ec0: Legacy ISA memory support enabled gpiochip_add: registered GPIOs 224 to 255 on device: /plb/opb/gpio@ef600b00 PCI: Probing PCI hardware PCI host bridge to bus :80 pci_bus :80: root bus resource [io 0xfffe-0xfffe] pci_bus :80: root bus resource [mem 0xe8000-0xe] PCI: Hiding 4xx host bridge resources :80:00.0 pci :80:00.0: PCI bridge to [bus 81-bf] PCI host bridge to bus 0001:00 pci_bus 0001:00: root bus resource [io 0x-0x] pci_bus 0001:00: root bus resource [mem 0xd8000-0xd] pci :80:00.0: PCI bridge to [bus 81-bf] pci 0001:00:04.0: BAR 0: assigned [mem 0xd8000-0xd87ff pref] pci 0001:00:04.1: BAR 0: assigned [mem 0xd8800-0xd8fff pref] pci 0001:00:06.0: BAR 0: assigned [mem 0xd9000-0xd93ff] pci 0001:00:06.0: BAR 1: assigned [mem 0xd9400-0xd941f] pci 0001:00:04.0: BAR 6: assigned [mem 0xd9420-0xd9421 pref] pci 0001:00:04.0: BAR 2: assigned [mem 0xd9422-0xd9422] pci 0001:00:04.1: BAR 1: assigned [mem 0xd9423-0xd9423] pci 0001:00:04.0: BAR 1: assigned [io 0x1000-0x10ff] bio: create slab at 0 vgaarb: device added: PCI:0001:00:04.0,decodes=io+mem,owns=io+mem,locks=none vgaarb: loaded vgaarb: bridge control possible 0001:00:04.0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Switching to clocksource timebase NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered UDP hash table entries: 512 (order: 1, 8192 bytes) UDP-Lite hash table entries: 512 (order: 1, 8192 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. Could not remap bcsr setting trigger mode 3 for irq 43 failed (uic_set_irq_type+0x0/0x164) setting trigger mode 3
Re: linux-3.3-rc2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
On Fri, 3 Feb 2012 02:56:18 +0100 acrux wrote: unable to have a working radeon kms framebuffer with linux-3.3-rc2 on ppc video card: Radeon X1650PRO PCIE here the boot log: U-Boot 2010.06.05 (Jul 05 2011 - 17:53:34) CPU: AMCC PowerPC 460EX Rev. B at 1166.667 MHz (PLB=233 OPB=116 EBC=116) No Security/Kasumi support Bootstrap Option H - Boot ROM Location I2C (Addr 0x52) Internal PCI arbiter enabled 32 kB I-Cache 32 kB D-Cache Board: Sam460ex, PCIe 4x + SATA-2 I2C: ready DRAM: 2 GiB (ECC not enabled, 466 MHz, CL4) PCI: Bus Dev VenId DevId Class Int 00 06 126f 0501 0380 00 PCIE1: successfully set as root-complex 02 00 1002 71c1 0300 ff Net: ppc_4xx_eth0 FPGA: Revision 03 (2010-10-07) SM502: found VGA: 1 VESA: OK Using Canyonlands machine description Initializing cgroup subsys cpu Linux version 3.3.0-rc2 (root@sam460) (gcc version 4.5.3 (CRUX PPC) ) #2 Sat Feb 4 20:34:21 CET 2012 Zone PFN ranges: DMA 0x -> 0x0003 Normal empty HighMem 0x0003 -> 0x0008 Movable zone start PFN for each node Early memory PFN ranges 0: 0x -> 0x0008 MMU: Allocated 1088 bytes of context maps for 255 contexts Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520192 Kernel command line: root=/dev/sda3 ro video=800x600 console=tty0 console=ttyS0,115200 udbg-immortal PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 2072736k/2097152k available (6772k kernel code, 24416k reserved, 188k data, 143k bss, 196k init) Kernel virtual memory layout: * 0xfffcf000..0xf000 : fixmap * 0xffc0..0xffe0 : highmem PTEs * 0xffa0..0xffc0 : consistent mem * 0xffa0..0xffa0 : early ioremap * 0xf100..0xffa0 : vmalloc & ioremap SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:512 nr_irqs:512 16 UIC0 (32 IRQ sources) at DCR 0xc0 UIC1 (32 IRQ sources) at DCR 0xd0 UIC2 (32 IRQ sources) at DCR 0xe0 UIC3 (32 IRQ sources) at DCR 0xf0 clocksource: timebase mult[db6db7] shift[24] registered Console: colour dummy device 80x25 console [tty0] enabled pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 devtmpfs: initialized NET: Registered protocol family 16 256k L2-cache enabled PCIE0: Port disabled via device-tree PCIE1: Checking link... PCIE1: Device detected, waiting for link... PCIE1: link is up ! PCI host bridge /plb/pciex@d2000 (primary) ranges: MEM 0x000e8000..0x000e -> 0x8000 MEM 0x000f0010..0x000f001f -> 0x IO 0x000f8001..0x000f8001 -> 0x Removing ISA hole at 0x000f0010 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pciex@d2000: Legacy ISA memory support enabled PCIE1: successfully set as root-complex PCI host bridge /plb/pci@c0ec0 (primary) ranges: MEM 0x000d8000..0x000d -> 0x8000 MEM 0x000c0ee0..0x000c0eef -> 0x IO 0x000c0800..0x000c0800 -> 0x Removing ISA hole at 0x000c0ee0 4xx PCI DMA offset set to 0x 4xx PCI DMA window base to 0x DMA window size 0x8000 /plb/pci@c0ec0: Legacy ISA memory support enabled gpiochip_add: registered GPIOs 224 to 255 on device: /plb/opb/gpio@ef600b00 PCI: Probing PCI hardware PCI host bridge to bus :80 pci_bus :80: root bus resource [io 0xfffe-0xfffe] pci_bus :80: root bus resource [mem 0xe8000-0xe] PCI: Hiding 4xx host bridge resources :80:00.0 pci :81:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' pci :80:00.0: PCI bridge to [bus 81-bf] PCI host bridge to bus 0001:00 pci_bus 0001:00: root bus resource [io 0x-0x] pci_bus 0001:00: root bus resource [mem 0xd8000-0xd] pci :80:00.0: BAR 15: assigned [mem 0xe8000-0xe97ff pref] pci :80:00.0: BAR 14: assigned [mem 0xe9800-0xe980f] pci :80:00.0: BAR 13: assigned [io 0xfffe1000-0xfffe1fff] pci :81:00.0: BAR 0: assigned [mem 0xe8000-0xe8fff 64bit pref] pci :81:00.0: BAR 6: assigned [mem 0xe9000-0xe9001 pref] pci :81:00.0: BAR 2: assigned [mem 0xe9800-0xe9800 64bit] pci :81:00.1: BAR 0: assigned [mem 0xe9801-0xe9801 64bit] pci :81:00.0: BAR 4: assigned [io 0xfffe1000-0xfffe10ff] pci :80:00.0: PCI bridge to [bus 81-bf] pci :80:00.0: bridge window [io 0xfffe1000-0xfffe1fff] pci :80:00.0: bridge window [mem 0xe9800-0xe980f] pci :80:00.0: bridge window [mem 0xe8000-0xe97ff pref] pci 0001:00:06.0: BAR 0: assigned
linux-3.2.2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
000c 5484103a 7cc52b78 7c802214 <7c0004ac> 7ca0252c 3860 4e800020 ---[ end trace 9e9e815408964066 ]--- Kernel panic - not syncing: Attempted to kill init! Call Trace: Rebooting in 180 seconds.. -- acrux
linux-3.2.2 and radeon kms failure on ppc32 with Radeon 9250 pci
er+0xbc/0x23c [ef835f40] [c03cca6c] driver_register+0xb8/0x144 [ef835f60] [c02f3ab4] __pci_register_driver+0x4c/0xc8 [ef835f80] [c03438c4] drm_pci_init+0x7c/0xf8 [ef835fa0] [c067aa88] radeon_init+0xc8/0xd0 [ef835fb0] [c0001608] do_one_initcall+0xe0/0x1b8 [ef835fe0] [c0661798] kernel_init+0x88/0x120 [ef835ff0] [c000b140] kernel_thread+0x4c/0x68 Instruction dump: 9923 38a5 38630001 4218 54abf0be 7c691b78 396b0001 7d6903a6 4818 706b0003 4082ffd8 4be4 39290004 4200fff8 54a907be ---[ end trace a97f9099d7d670b8 ]--- Kernel panic - not syncing: Attempted to kill init! Call Trace: Rebooting in 180 seconds.. -- acrux
linux-3.2.2 and radeon kms failure on ppc32 with Radeon X1650PRO pcie
103a 7cc52b78 7c802214 <7c0004ac> 7ca0252c 3860 4e800020 ---[ end trace 9e9e815408964066 ]--- Kernel panic - not syncing: Attempted to kill init! Call Trace: Rebooting in 180 seconds.. -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
linux-3.2.2 and radeon kms failure on ppc32 with Radeon 9250 pci
3c [ef835f40] [c03cca6c] driver_register+0xb8/0x144 [ef835f60] [c02f3ab4] __pci_register_driver+0x4c/0xc8 [ef835f80] [c03438c4] drm_pci_init+0x7c/0xf8 [ef835fa0] [c067aa88] radeon_init+0xc8/0xd0 [ef835fb0] [c0001608] do_one_initcall+0xe0/0x1b8 [ef835fe0] [c0661798] kernel_init+0x88/0x120 [ef835ff0] [c000b140] kernel_thread+0x4c/0x68 Instruction dump: 9923 38a5 38630001 4218 54abf0be 7c691b78 396b0001 7d6903a6 4818 706b0003 4082ffd8 4be4 39290004 4200fff8 54a907be ---[ end trace a97f9099d7d670b8 ]--- Kernel panic - not syncing: Attempted to kill init! Call Trace: Rebooting in 180 seconds.. -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 10:34:03 +0100 Michel D?nzer wrote: > On Son, 2012-01-29 at 23:27 +0100, acrux wrote: > > hi all, > > i'm unable to have a working Radeon KMS framebuffer with an ATI FireGL > > V5600 on my YDL Powerstation and i'm obliged to use the old > > OpenFirmware fb. > > > > That's from my dmesg [1]: > > > > [...] > > vgaarb: device added: PCI::f1:00.0,decodes=io+mem,owns=none,locks=none > > vgaarb: loaded > > vgaarb: bridge control possible :f1:00.0 > > [...] > > [drm] Initialized drm 1.1.0 20060810 > > [drm] radeon defaulting to kernel modesetting. > > [drm] radeon kernel modesetting enabled. > > [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). > > radeon :f1:00.0: Using 32-bit DMA via iommu > > [drm] register mmio base: 0xE800 > > [drm] register mmio size: 65536 > > radeon :f1:00.0: Invalid ROM contents > > radeon :f1:00.0: Expecting atombios for R600 GPU > > radeon :f1:00.0: Fatal error during GPU init > > Looks like there's a problem retrieving the card's ROM contents. Does > rebuilding the kernel with CONFIG_VGA_ARB disabled make a difference? > > again without radeon kms and the problems is still here.. more a good numbers of straces for another different cause. http://cruxppc.org/~acrux/config-kms2 http://cruxppc.org/~acrux/dmesg-kms2 [...] [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). radeon :f1:00.0: Using 32-bit DMA via iommu [drm] register mmio base: 0xE800 [drm] register mmio size: 65536 radeon :f1:00.0: Invalid ROM contents radeon :f1:00.0: Expecting atombios for R600 GPU radeon :f1:00.0: Fatal error during GPU init [drm] radeon: finishing device. [TTM] Memory type 2 has not been initialized. radeon: probe of :f1:00.0 failed with error -22 best, --nico -- acrux
failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 16:10:03 +0100 Andreas Schwab wrote: > Michel D?nzer writes: > > > On Mon, 2012-01-30 at 14:03 +0100, acrux wrote: > >> hi Michel, > >> thanks for your help but i'm unable to disable VGA_ARB 'cause it's > >> automatically enabled. > >> Can you suggest me a way to disable it? > >> Here my kernel config: http://cruxppc.org/~acrux/config-kms > > > > Might be due to VGA_ARB_MAX_GPUS, which depends on VGA_ARB. Try removing > > that from .config as well. > > > > If that still doesn't work, please describe how exactly you're trying to > > disable VGA_ARB. > > You need to enable CONFIG_EXPERT to be able to toggle VGA_ARB. > > Andreas. > oh, shame on me! That was the trick. Thank you Andreas. --nico -- acrux
failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 08:58:28 -0500 Alex Deucher wrote: _omissis__ > > > > hi Michel, > > thanks for your help but i'm unable to disable VGA_ARB 'cause it's > > automatically enabled. > > Can you suggest me a way to disable it? > > Here my kernel config: http://cruxppc.org/~acrux/config-kms > > > > Also make sure you enable PCI quirks. > as you can read from my config it was already enabled (btw, it's automatically enabled too) --nico -- acrux
failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 10:34:03 +0100 Michel D?nzer wrote: > On Son, 2012-01-29 at 23:27 +0100, acrux wrote: > > hi all, > > i'm unable to have a working Radeon KMS framebuffer with an ATI FireGL > > V5600 on my YDL Powerstation and i'm obliged to use the old > > OpenFirmware fb. > > > > That's from my dmesg [1]: > > > > [...] > > vgaarb: device added: PCI::f1:00.0,decodes=io+mem,owns=none,locks=none > > vgaarb: loaded > > vgaarb: bridge control possible :f1:00.0 > > [...] > > [drm] Initialized drm 1.1.0 20060810 > > [drm] radeon defaulting to kernel modesetting. > > [drm] radeon kernel modesetting enabled. > > [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). > > radeon :f1:00.0: Using 32-bit DMA via iommu > > [drm] register mmio base: 0xE800 > > [drm] register mmio size: 65536 > > radeon :f1:00.0: Invalid ROM contents > > radeon :f1:00.0: Expecting atombios for R600 GPU > > radeon :f1:00.0: Fatal error during GPU init > > Looks like there's a problem retrieving the card's ROM contents. Does > rebuilding the kernel with CONFIG_VGA_ARB disabled make a difference? > > hi Michel, thanks for your help but i'm unable to disable VGA_ARB 'cause it's automatically enabled. Can you suggest me a way to disable it? Here my kernel config: http://cruxppc.org/~acrux/config-kms best, --nico -- acrux
Re: failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 16:10:03 +0100 Andreas Schwab wrote: > Michel Dänzer writes: > > > On Mon, 2012-01-30 at 14:03 +0100, acrux wrote: > >> hi Michel, > >> thanks for your help but i'm unable to disable VGA_ARB 'cause it's > >> automatically enabled. > >> Can you suggest me a way to disable it? > >> Here my kernel config: http://cruxppc.org/~acrux/config-kms > > > > Might be due to VGA_ARB_MAX_GPUS, which depends on VGA_ARB. Try removing > > that from .config as well. > > > > If that still doesn't work, please describe how exactly you're trying to > > disable VGA_ARB. > > You need to enable CONFIG_EXPERT to be able to toggle VGA_ARB. > > Andreas. > oh, shame on me! That was the trick. Thank you Andreas. --nico -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 10:34:03 +0100 Michel Dänzer wrote: > On Son, 2012-01-29 at 23:27 +0100, acrux wrote: > > hi all, > > i'm unable to have a working Radeon KMS framebuffer with an ATI FireGL > > V5600 on my YDL Powerstation and i'm obliged to use the old > > OpenFirmware fb. > > > > That's from my dmesg [1]: > > > > [...] > > vgaarb: device added: PCI::f1:00.0,decodes=io+mem,owns=none,locks=none > > vgaarb: loaded > > vgaarb: bridge control possible :f1:00.0 > > [...] > > [drm] Initialized drm 1.1.0 20060810 > > [drm] radeon defaulting to kernel modesetting. > > [drm] radeon kernel modesetting enabled. > > [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). > > radeon :f1:00.0: Using 32-bit DMA via iommu > > [drm] register mmio base: 0xE800 > > [drm] register mmio size: 65536 > > radeon :f1:00.0: Invalid ROM contents > > radeon :f1:00.0: Expecting atombios for R600 GPU > > radeon :f1:00.0: Fatal error during GPU init > > Looks like there's a problem retrieving the card's ROM contents. Does > rebuilding the kernel with CONFIG_VGA_ARB disabled make a difference? > > again without radeon kms and the problems is still here.. more a good numbers of straces for another different cause. http://cruxppc.org/~acrux/config-kms2 http://cruxppc.org/~acrux/dmesg-kms2 [...] [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). radeon :f1:00.0: Using 32-bit DMA via iommu [drm] register mmio base: 0xE800 [drm] register mmio size: 65536 radeon :f1:00.0: Invalid ROM contents radeon :f1:00.0: Expecting atombios for R600 GPU radeon :f1:00.0: Fatal error during GPU init [drm] radeon: finishing device. [TTM] Memory type 2 has not been initialized. radeon: probe of :f1:00.0 failed with error -22 best, --nico -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 08:58:28 -0500 Alex Deucher wrote: _omissis__ > > > > hi Michel, > > thanks for your help but i'm unable to disable VGA_ARB 'cause it's > > automatically enabled. > > Can you suggest me a way to disable it? > > Here my kernel config: http://cruxppc.org/~acrux/config-kms > > > > Also make sure you enable PCI quirks. > as you can read from my config it was already enabled (btw, it's automatically enabled too) --nico -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
On Mon, 30 Jan 2012 10:34:03 +0100 Michel Dänzer wrote: > On Son, 2012-01-29 at 23:27 +0100, acrux wrote: > > hi all, > > i'm unable to have a working Radeon KMS framebuffer with an ATI FireGL > > V5600 on my YDL Powerstation and i'm obliged to use the old > > OpenFirmware fb. > > > > That's from my dmesg [1]: > > > > [...] > > vgaarb: device added: PCI::f1:00.0,decodes=io+mem,owns=none,locks=none > > vgaarb: loaded > > vgaarb: bridge control possible :f1:00.0 > > [...] > > [drm] Initialized drm 1.1.0 20060810 > > [drm] radeon defaulting to kernel modesetting. > > [drm] radeon kernel modesetting enabled. > > [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). > > radeon :f1:00.0: Using 32-bit DMA via iommu > > [drm] register mmio base: 0xE800 > > [drm] register mmio size: 65536 > > radeon :f1:00.0: Invalid ROM contents > > radeon :f1:00.0: Expecting atombios for R600 GPU > > radeon :f1:00.0: Fatal error during GPU init > > Looks like there's a problem retrieving the card's ROM contents. Does > rebuilding the kernel with CONFIG_VGA_ARB disabled make a difference? > > hi Michel, thanks for your help but i'm unable to disable VGA_ARB 'cause it's automatically enabled. Can you suggest me a way to disable it? Here my kernel config: http://cruxppc.org/~acrux/config-kms best, --nico -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
hi all, i'm unable to have a working Radeon KMS framebuffer with an ATI FireGL V5600 on my YDL Powerstation and i'm obliged to use the old OpenFirmware fb. That's from my dmesg [1]: [...] vgaarb: device added: PCI::f1:00.0,decodes=io+mem,owns=none,locks=none vgaarb: loaded vgaarb: bridge control possible :f1:00.0 [...] [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). radeon :f1:00.0: Using 32-bit DMA via iommu [drm] register mmio base: 0xE800 [drm] register mmio size: 65536 radeon :f1:00.0: Invalid ROM contents radeon :f1:00.0: Expecting atombios for R600 GPU radeon :f1:00.0: Fatal error during GPU init [drm] radeon: finishing device. [TTM] Memory type 2 has not been initialized. radeon: probe of :f1:00.0 failed with error -22 This is about the video card: root at radio:~# lspci :f0:0b.0 PCI bridge: Apple Computer Inc. CPC945 PCIe Bridge :f1:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630GL [FireGL v5600] 0001:00:01.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-X bridge (rev b0) 0001:00:02.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-X bridge (rev b0) 0001:00:03.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:04.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:05.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:06.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:07.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 0001:00:08.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 0001:00:08.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 0001:01:01.0 RAID bus controller: IBM Obsidian chipset SCSI controller (rev 01) 0001:02:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet (rev 10) 0001:02:04.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet (rev 10) 0001:07:00.0 USB controller: Advanced Micro Devices [AMD] AMD-8111 USB OHCI (rev 0b) 0001:07:00.1 USB controller: Advanced Micro Devices [AMD] AMD-8111 USB OHCI (rev 0b) 0001:07:02.0 Serial controller: Exar Corp. XR17C/D152 Dual PCI UART (rev 02) root at radio:~# lspci -nn|grep VGA :f1:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV630GL [FireGL v5600] [1002:958c] :f1:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630GL [FireGL v5600] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices [AMD] nee ATI Device 0b02 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: radeon thanks for your help, --nico [1] http://cruxppc.org/~acrux/dmesg-kms -- acrux
failure on linux-3.2 and radeon kms with a FireGL V5600 on PPC64
hi all, i'm unable to have a working Radeon KMS framebuffer with an ATI FireGL V5600 on my YDL Powerstation and i'm obliged to use the old OpenFirmware fb. That's from my dmesg [1]: [...] vgaarb: device added: PCI::f1:00.0,decodes=io+mem,owns=none,locks=none vgaarb: loaded vgaarb: bridge control possible :f1:00.0 [...] [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RV630 0x1002:0x958C 0x1002:0x0B02). radeon :f1:00.0: Using 32-bit DMA via iommu [drm] register mmio base: 0xE800 [drm] register mmio size: 65536 radeon :f1:00.0: Invalid ROM contents radeon :f1:00.0: Expecting atombios for R600 GPU radeon :f1:00.0: Fatal error during GPU init [drm] radeon: finishing device. [TTM] Memory type 2 has not been initialized. radeon: probe of :f1:00.0 failed with error -22 This is about the video card: root@radio:~# lspci :f0:0b.0 PCI bridge: Apple Computer Inc. CPC945 PCIe Bridge :f1:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630GL [FireGL v5600] 0001:00:01.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-X bridge (rev b0) 0001:00:02.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-X bridge (rev b0) 0001:00:03.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:04.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:05.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:06.0 PCI bridge: Broadcom BCM5780 [HT2000] PCI-Express Bridge (rev b0) 0001:00:07.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 0001:00:08.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 0001:00:08.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 0001:01:01.0 RAID bus controller: IBM Obsidian chipset SCSI controller (rev 01) 0001:02:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet (rev 10) 0001:02:04.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5780 Gigabit Ethernet (rev 10) 0001:07:00.0 USB controller: Advanced Micro Devices [AMD] AMD-8111 USB OHCI (rev 0b) 0001:07:00.1 USB controller: Advanced Micro Devices [AMD] AMD-8111 USB OHCI (rev 0b) 0001:07:02.0 Serial controller: Exar Corp. XR17C/D152 Dual PCI UART (rev 02) root@radio:~# lspci -nn|grep VGA :f1:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV630GL [FireGL v5600] [1002:958c] :f1:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630GL [FireGL v5600] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices [AMD] nee ATI Device 0b02 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: radeon thanks for your help, --nico [1] http://cruxppc.org/~acrux/dmesg-kms -- acrux ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
