Scott Duplichan wrote: > ]Could you use windbg to get more details, in particular find out > ]what the ATI driver was trying to do? > > For the infinite loop case, I captured a stack trace: > > nt!DbgBreakPointWithStatus > nt!KiBugCheckDebugBreak+0x14 > nt!KeBugCheck2+0x7c8 > nt!KeBugCheckEx+0x104 > dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3e > dxgkrnl!TdrTimedOperationDelay+0xbb > atikmdag!OsServices::Wait+0x92 > atikmdag!MCIL_WaitFor+0x50 > atikmdag!Cail_MCILWaitFor+0x72 > atikmdag!Cail_R600_WaitForIdle+0x52 > atikmdag!Cail_R600_WaitForIdle+0x172 > atikmdag!Cail_ExecuteAsicSetupTable+0x98 > atikmdag!CAIL_ASICSetup+0x7b > atikmdag!CAIL_VPURecoveryBegin+0x20e > atikmdag!CAILVPURecoveryBegin+0x19 > atikmdag!AsicInit::ResetTheAsic+0x4a > atikmdag!DISPATCHER::HeavyWeightReset+0x65 > atikmdag!DISPATCHER::ResetFromTimeoutWorker+0x16b > atikmdag!Dispatch_ResetFromTimeout+0x67 > dxgkrnl!DXGADAPTER::DdiResetFromTimeout+0x4c > dxgkrnl!DXGADAPTER::PrepareToReset+0xf6 > dxgkrnl!TdrIsRecoveryRequired+0x279 > dxgmms1!VidSchiReportHwHang+0x4ce > dxgmms1!VidSchiCheckHwProgress+0xee > dxgmms1!VidSchiWaitForSchedulerEvents+0x319 > dxgmms1!VidSchiScheduleCommandToRun+0x3d9 > dxgmms1!VidSchiWorkerThread+0x196 > nt!PspSystemThreadStartup+0x1a9 > nt!KxStartSystemThread+0x16
Nice! > Looks like it had a hang early and some recovery attempts were > unsuccessful. I think it might be useful to talk to the radeon dri (Linux kernel graphics) people about this, they might be able to provide some hints about why the asic would get stuck and not even be resettable. //Peter -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
