Re: [r300/ppc] lockups
On Wed, 2005-06-22 at 18:36 +1000, Benjamin Herrenschmidt wrote: The problem is simple: when setting up the AGP aperture, it's putting it after the framebuffer + CONFIG_APER_SIZE, which is wrong. On that guy, CONFIG_APER_SIZE might only be _half_ of the mapped vram space (as the card can be setup for 2 contiguous apertures). We need to make sure the DRM uses what is in MC_FB_LOCATION top, and that itself should be set ideally to max(CONFIG_APER_SIZE*2,CONFIG_MEMSIZE) to avoid any possible kind of overlap. Has this been changed by now? i.e. should I try again? johannes signature.asc Description: This is a digitally signed message part
Re: [r300/ppc] lockups
On Thu, 2005-08-25 at 23:26 +0200, Johannes Berg wrote: On Wed, 2005-06-22 at 18:36 +1000, Benjamin Herrenschmidt wrote: The problem is simple: when setting up the AGP aperture, it's putting it after the framebuffer + CONFIG_APER_SIZE, which is wrong. On that guy, CONFIG_APER_SIZE might only be _half_ of the mapped vram space (as the card can be setup for 2 contiguous apertures). We need to make sure the DRM uses what is in MC_FB_LOCATION top, and that itself should be set ideally to max(CONFIG_APER_SIZE*2,CONFIG_MEMSIZE) to avoid any possible kind of overlap. Has this been changed by now? i.e. should I try again? Not sure my patch got merged, I'll have to dig into that again. Ben. --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300/ppc] lockups
On Thu, 2005-08-25 at 23:42 +0200, Jerome Glisse wrote: IIRC there have been a patch to xorg for that and to DRM too. Give it a try :) For whatever reason, I can't seem to build xorg right now. I'll have a try another time, but thanks for the heads-up. johannes signature.asc Description: This is a digitally signed message part
Re: [r300/ppc] lockups
On Tue, 2005-06-21 at 16:44 +0200, Johannes Berg wrote: Jerome Glisse wrote: I can remember from the top of my head but there is maybe some patch that could be revealent for ppc not included in this snapshot. Thus i think you should consider trying building xorg from cvs. Anyway with a g4 it will compiles a lot faster than on dumb x86 ;) Ok, I'll have a try. But I doubt I can before the weekend though. Nicolai: If you want to take a look first-hand, I can take the pb to university (assuming you are prefect at upb dot de which I have reason to believe) next week. Can't do it this week due to a talk I have to give on Friday. The problem is simple: when setting up the AGP aperture, it's putting it after the framebuffer + CONFIG_APER_SIZE, which is wrong. On that guy, CONFIG_APER_SIZE might only be _half_ of the mapped vram space (as the card can be setup for 2 contiguous apertures). We need to make sure the DRM uses what is in MC_FB_LOCATION top, and that itself should be set ideally to max(CONFIG_APER_SIZE*2,CONFIG_MEMSIZE) to avoid any possible kind of overlap. Ben. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300/ppc] lockups
On 6/21/05, Vladimir Dergachev [EMAIL PROTECTED] wrote: On Sat, 18 Jun 2005, Johannes Berg wrote: Any idea where I should start looking for the source of the lockups or what else to do? The problem is likely either due to the radeon memory controller - in particular registers like MC_FB_LOCATION MC_AGP_LOCATION - or some sort of AGP issue with ring buffer not working properly. IIRC Paul has a similar problem with his powerbook and Ben provided patch against xorg drm for correcting the way this reg are setup. But this patch were for normal drm. Maybe once we get time we should look at that an program properly this reg in r300... Jerome Glisse --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300/ppc] lockups
On Tuesday 21 June 2005 10:54, Jerome Glisse wrote: On 6/21/05, Vladimir Dergachev [EMAIL PROTECTED] wrote: On Sat, 18 Jun 2005, Johannes Berg wrote: Any idea where I should start looking for the source of the lockups or what else to do? The problem is likely either due to the radeon memory controller - in particular registers like MC_FB_LOCATION MC_AGP_LOCATION - or some sort of AGP issue with ring buffer not working properly. IIRC Paul has a similar problem with his powerbook and Ben provided patch against xorg drm for correcting the way this reg are setup. But this patch were for normal drm. Maybe once we get time we should look at that an program properly this reg in r300... Not knowing this particular patch or whether anybody has tried our driver on PPC, what about endianness issues? I know it's obvious, but who knows... cu, Nicolai pgpi0g7Vngt13.pgp Description: PGP signature
Re: [r300/ppc] lockups
On 6/21/05, Johannes Berg [EMAIL PROTECTED] wrote: Hi, I mainly used r300 on ppc so far thus yes it works. Good to know. I am using it on x86 for the 9800 lockup. But as i used a g5 i don't know if there is an issue with the agp of g4, don't think so... And IIRC someone told me that it worked on a powerbook which is, i presume, what Johannes got. Yes, the latest model. Btw Johannes you compile everythings yourself ? You use snapshot of what mesa, xorg, ... ? I used mesa cvs, r300 cvs and xorg cvs snapshot from http://xorg.freedesktop.org/snapshots/xorg-x11-6.8.99.11.tar.bz2 Kernel 2.6.12-rc5 (I think), only major patchset in it is suspend2. You should better build xorg from cvs on your platform. If i can steal the pb of a friend i will give it a try... Do you really think it makes a difference? I can give it a try though. I can remember from the top of my head but there is maybe some patch that could be revealent for ppc not included in this snapshot. Thus i think you should consider trying building xorg from cvs. Anyway with a g4 it will compiles a lot faster than on dumb x86 ;) Jerome Glisse --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300/ppc] lockups
Hi, I mainly used r300 on ppc so far thus yes it works. Good to know. I am using it on x86 for the 9800 lockup. But as i used a g5 i don't know if there is an issue with the agp of g4, don't think so... And IIRC someone told me that it worked on a powerbook which is, i presume, what Johannes got. Yes, the latest model. Btw Johannes you compile everythings yourself ? You use snapshot of what mesa, xorg, ... ? I used mesa cvs, r300 cvs and xorg cvs snapshot from http://xorg.freedesktop.org/snapshots/xorg-x11-6.8.99.11.tar.bz2 Kernel 2.6.12-rc5 (I think), only major patchset in it is suspend2. You should better build xorg from cvs on your platform. If i can steal the pb of a friend i will give it a try... Do you really think it makes a difference? I can give it a try though. johannes --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300/ppc] lockups
On 6/21/05, Nicolai Haehnle [EMAIL PROTECTED] wrote: On Tuesday 21 June 2005 10:54, Jerome Glisse wrote: On 6/21/05, Vladimir Dergachev [EMAIL PROTECTED] wrote: On Sat, 18 Jun 2005, Johannes Berg wrote: Any idea where I should start looking for the source of the lockups or what else to do? The problem is likely either due to the radeon memory controller - in particular registers like MC_FB_LOCATION MC_AGP_LOCATION - or some sort of AGP issue with ring buffer not working properly. IIRC Paul has a similar problem with his powerbook and Ben provided patch against xorg drm for correcting the way this reg are setup. But this patch were for normal drm. Maybe once we get time we should look at that an program properly this reg in r300... Not knowing this particular patch or whether anybody has tried our driver on PPC, what about endianness issues? I know it's obvious, but who knows... I mainly used r300 on ppc so far thus yes it works. I am using it on x86 for the 9800 lockup. But as i used a g5 i don't know if there is an issue with the agp of g4, don't think so... And IIRC someone told me that it worked on a powerbook which is, i presume, what Johannes got. Btw Johannes you compile everythings yourself ? You use snapshot of what mesa, xorg, ... ? You should better build xorg from cvs on your platform. If i can steal the pb of a friend i will give it a try... Jerome Glisse --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300/ppc] lockups
Jerome Glisse wrote: I can remember from the top of my head but there is maybe some patch that could be revealent for ppc not included in this snapshot. Thus i think you should consider trying building xorg from cvs. Anyway with a g4 it will compiles a lot faster than on dumb x86 ;) Ok, I'll have a try. But I doubt I can before the weekend though. Nicolai: If you want to take a look first-hand, I can take the pb to university (assuming you are prefect at upb dot de which I have reason to believe) next week. Can't do it this week due to a talk I have to give on Friday. johannes --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [r300/ppc] lockups
On Sat, 18 Jun 2005, Johannes Berg wrote: Hi, I just tried the latest r300 cvs code (with current mesa cvs, latest Xorg snapshot) but all I get is a lockup as soon as the X server starts. If I have debugging enabled, I get a loop of radeon_do_cp_idle calls. Hardware is: :00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 255 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 48 Region 0: Memory at b800 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at 802400 [size=256] Region 2: Memory at b000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at f100 [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Status: RQ=80 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=none Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Any idea where I should start looking for the source of the lockups or what else to do? The problem is likely either due to the radeon memory controller - in particular registers like MC_FB_LOCATION MC_AGP_LOCATION - or some sort of AGP issue with ring buffer not working properly. The 2d support should work - the fact that it does not indicates a screw up someplace obvious. Check that the registers mentioned above are programmed to what Xserver and drm driver think they are. In particular look for endianness errors, though this might not be it.. To avoid lockups you can modify Xserver code to put exit(0) just after those are set - you will need a separate box to ssh in as the monitor will not be in a usable state. best Vladimir Dergachev Thanks, johannes --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[r300/ppc] lockups
Hi, I just tried the latest r300 cvs code (with current mesa cvs, latest Xorg snapshot) but all I get is a lockup as soon as the X server starts. If I have debugging enabled, I get a loop of radeon_do_cp_idle calls. Hardware is: :00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 255 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 48 Region 0: Memory at b800 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at 802400 [size=256] Region 2: Memory at b000 (32-bit, non-prefetchable) [size=64K] Expansion ROM at f100 [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Status: RQ=80 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=none Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Any idea where I should start looking for the source of the lockups or what else to do? Thanks, johannes signature.asc Description: This is a digitally signed message part
