On Fri, Oct 2, 2020 at 9:27 PM Rob Clark wrote:
>
> On Fri, Oct 2, 2020 at 11:54 AM Daniel Vetter wrote:
> >
> > On Fri, Oct 02, 2020 at 10:22:42AM -0700, Rob Clark wrote:
> > > On Fri, Oct 2, 2020 at 12:36 AM Daniel Vetter wrote:
> > > >
> > > > On Fri, Oct 2, 2020 at 3:47 AM Abhinav Kumar
>
On Fri, Oct 2, 2020 at 11:54 AM Daniel Vetter wrote:
>
> On Fri, Oct 02, 2020 at 10:22:42AM -0700, Rob Clark wrote:
> > On Fri, Oct 2, 2020 at 12:36 AM Daniel Vetter wrote:
> > >
> > > On Fri, Oct 2, 2020 at 3:47 AM Abhinav Kumar
> > > wrote:
> > > >
> > > > Add support to capture the drm atomi
On Fri, Oct 02, 2020 at 10:22:42AM -0700, Rob Clark wrote:
> On Fri, Oct 2, 2020 at 12:36 AM Daniel Vetter wrote:
> >
> > On Fri, Oct 2, 2020 at 3:47 AM Abhinav Kumar
> > wrote:
> > >
> > > Add support to capture the drm atomic state snapshot which
> > > can then be wired up with the devcoredump
On Fri, Oct 2, 2020 at 12:36 AM Daniel Vetter wrote:
>
> On Fri, Oct 2, 2020 at 3:47 AM Abhinav Kumar wrote:
> >
> > Add support to capture the drm atomic state snapshot which
> > can then be wired up with the devcoredump of the relevant display
> > errors to give useful information to debug the
On Fri, Oct 2, 2020 at 3:47 AM Abhinav Kumar wrote:
>
> Add support to capture the drm atomic state snapshot which
> can then be wired up with the devcoredump of the relevant display
> errors to give useful information to debug the issues.
>
> Since the devcoredump is read by usermode and it is al
Add support to capture the drm atomic state snapshot which
can then be wired up with the devcoredump of the relevant display
errors to give useful information to debug the issues.
Since the devcoredump is read by usermode and it is allowed
upto 5 minutes to read the coredump, capturing the snapsho
