On Sat, Jun 11, 2022 at 04:29:06AM +0100, Chris Narkiewicz wrote:
> On Fri, Jun 10, 2022 at 01:45:09PM +1000, Jonathan Gray wrote:
> > Thanks, it would appear to be something outside of drm then.
>
> I managed to run latest snapshot 2022-06-11, but
> I did it by upgrading sets from 2022-05-25.
>
On Fri, Jun 10, 2022 at 11:53:42AM +0100, Chris Narkiewicz wrote:
> On Fri, Jun 10, 2022 at 01:45:09PM +1000, Jonathan Gray wrote:
> > Thanks, it would appear to be something outside of drm then.
>
> Is there a way to do a bisect with CVS? I could perhaps compile a bunch of
> kernel versions to
On Fri, Jun 10, 2022 at 04:26:06AM +0100, Chris Narkiewicz wrote:
> On Fri, Jun 10, 2022 at 12:34:47PM +1000, Jonathan Gray wrote:
> > you don't need to start from tarballs, try
>
> Your instructions worked and I booted patched kernel.
>
> The patch doesn' work - the behaviour the same
> as in
On Fri, Jun 10, 2022 at 03:03:08AM +0100, Chris Narkiewicz wrote:
> On Thu, Jun 09, 2022 at 03:25:06PM +1000, Jonathan Gray wrote:
> > Can you try this diff against -current which reverts some drm commits
> > from that timeframe?
>
> So I tried and can't compile it - probably unrelated to the
On Wed, Jun 08, 2022 at 11:42:21PM +0100, Chris Narkiewicz wrote:
> On Wed, Jun 08, 2022 at 09:56:09PM +1000, Jonathan Gray wrote:
> > some older snapshots can be found at
> > https://ftp.hostserver.de/archive/
>
> Thanks.
>
> I did a bisect and here is the result:
>
> Works:
>
