[Bug 28402] random radeon/kms/drm related freezes with kernel 2.6.34
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 9 04:48:19 PDT 2010
https://bugs.freedesktop.org/show_bug.cgi?id=28402
--- Comment #59 from Martin Steigerwald <Martin at Lichtvoll.de> 2010-09-09 04:48:18 PDT ---
(In reply to comment #57)
> (In reply to comment #56)
> > (In reply to comment #48)
> > > (In reply to comment #47)
> > > > Created an attachment (id=38516)
View: https://bugs.freedesktop.org/attachment.cgi?id=38516
Review: https://bugs.freedesktop.org/review?bug=28402&attachment=38516
[details] [details]
> > > > possible fix
> > > >
> > > > Does this patch help? It always aligns the MC vram and gtt bases to size.
> > >
> > > I'm sorry to report that it does not. I've tried with
> > > 96576a9e1a0cdb8a43d3af5846be0948f52b4460 (current drm-next in airlied's tree).
> > > This freezes without any patches, seems stable with airlied's patch to put vmem
> > > at address 0, but freezes still with your patch.
> > >
> > > Lukas, can you confirm that this patch still freezes?
> >
> > I've tried this patch again today, this time using vanilla 2.6.36-rc3.
> > Unfortunately it froze again upon launching firefox.
>
> Hm... damn. My 2.6.36-rc3 with alex' patch didn't give me a freeze for ~ 1 day.
> And I'm pretty sure, that I applied the patch correctly and didn't mix up any
> of these patches. (did some checks ...)
> However, I did a reset of the whole tree, pulled the newest version and applied
> alex' patch again.
> I'm on 2.6.36-rc3-00185-gd56557a-dirty and testing..
You seem to be the same gfx card, but different surrounding hardware, a
Fujitsu-Siemens laptop? Maybe Alex patch works on your hardware, but does not
work on Da Fox' and my ThinkPad T42?
You have:
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon
9600 M10] (prog-if 00 [VGA controller])
Subsystem: Fujitsu Limited. Device 127f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B+ DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 66 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at c8000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 2000 [size=256]
Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at c0120000 [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=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x1
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: radeon
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon
9600 M10] (prog-if 00 [VGA controller])
Subsystem: IBM Device 0550
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B+ DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 66 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 3000 [size=256]
Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at c0120000 [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=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW-
Rate=x1
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: radeon
Region 0 memory and I/O ports are at different addresses. Maybe that explains
it? Apart from that only PMEClk looks slightly different. I don't know what all
that means exactly, but maybe its a hint?
Maybe its also from difference in userspace that triggers or not triggers
slightly different code paths? I have Debian Squeeze/Sid/Experimental with:
martin at shambhala:~> apt-show-versions | egrep
"(xserver-xorg/|xserver-xorg-core/|xserver-xorg-video-radeon/|libgl1-mesa-dri/|libdrm2/|libdrm-radeon1/|kde-window-manager/|kdelibs5/)"
kde-window-manager/squeeze uptodate 4:4.4.5-3
kdelibs5/squeeze uptodate 4:4.4.5-1
libdrm-radeon1/experimental uptodate 2.4.21-2
libdrm2/experimental uptodate 2.4.21-2
libgl1-mesa-dri/experimental uptodate 7.8.2-2
xserver-xorg/squeeze uptodate 1:7.5+6
xserver-xorg-core/squeeze uptodate 2:1.7.7-4
xserver-xorg-video-radeon/squeeze uptodate 1:6.13.1-2
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the dri-devel
mailing list