Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Sep 25, 2013 at 09:56:52AM +0200, Daniel Vetter wrote: > On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: > > On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin > > wrote: > > > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: > > >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: > > >> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] > > >> > > > >> > Hi, > > >> > > > >> > saw your posting in [1]... can you try the patches below? > > >> > Not sure if they apply. > > >> > Did you try v3.11-rc6(+)... or drm-intel-nightly? > > >> > > > >> > Regards, > > >> > - Sedat - > > >> > > > >> > [1] > > >> > http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html > > >> > > >> Same thing observed with v3.11-rc7. > > > > > > I still see this with 3.11. > > > Following this message, my VGA monitor goes blank and > > > shows an error suggesting a wrong resolution or frequency are set. > > > Anyone? > > > > Daniel, Jesse? > > > > still ongoing I think. > > Yeah, I've dismissed it since the original issue in this thread is > resolved. But it's something else. > > Note to bug reporters: Please don't me-too, but start a new thread/report > - almost every gfx bug is different, even if it superficially looks the > same. > > Michael, can you please boot with drm.debug=0xe, reproduce the problem and > then attach the complete dmesg? Please make sure dmesg contains everything > since boot-up, if not please increase the dmesg buffer size with > log_buf_len=4M. > > Also please test the latest drm-intel-fixes release to check that we > haven't just forgotten to send the patch to stable (there's at least one > flags mismatch fix already in-flight to 3.11 stable kernels). > > Thanks, Daniel > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch Will do. Holidays starting now so expect some reports next week. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: > On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin wrote: > > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: > >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: > >> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] > >> > > >> > Hi, > >> > > >> > saw your posting in [1]... can you try the patches below? > >> > Not sure if they apply. > >> > Did you try v3.11-rc6(+)... or drm-intel-nightly? > >> > > >> > Regards, > >> > - Sedat - > >> > > >> > [1] > >> > http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html > >> > >> Same thing observed with v3.11-rc7. > > > > I still see this with 3.11. > > Following this message, my VGA monitor goes blank and > > shows an error suggesting a wrong resolution or frequency are set. > > Anyone? > > Daniel, Jesse? > > still ongoing I think. Yeah, I've dismissed it since the original issue in this thread is resolved. But it's something else. Note to bug reporters: Please don't me-too, but start a new thread/report - almost every gfx bug is different, even if it superficially looks the same. Michael, can you please boot with drm.debug=0xe, reproduce the problem and then attach the complete dmesg? Please make sure dmesg contains everything since boot-up, if not please increase the dmesg buffer size with log_buf_len=4M. Also please test the latest drm-intel-fixes release to check that we haven't just forgotten to send the patch to stable (there's at least one flags mismatch fix already in-flight to 3.11 stable kernels). Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin m...@redhat.com wrote: On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] Hi, saw your posting in [1]... can you try the patches below? Not sure if they apply. Did you try v3.11-rc6(+)... or drm-intel-nightly? Regards, - Sedat - [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html Same thing observed with v3.11-rc7. I still see this with 3.11. Following this message, my VGA monitor goes blank and shows an error suggesting a wrong resolution or frequency are set. Anyone? Daniel, Jesse? still ongoing I think. Yeah, I've dismissed it since the original issue in this thread is resolved. But it's something else. Note to bug reporters: Please don't me-too, but start a new thread/report - almost every gfx bug is different, even if it superficially looks the same. Michael, can you please boot with drm.debug=0xe, reproduce the problem and then attach the complete dmesg? Please make sure dmesg contains everything since boot-up, if not please increase the dmesg buffer size with log_buf_len=4M. Also please test the latest drm-intel-fixes release to check that we haven't just forgotten to send the patch to stable (there's at least one flags mismatch fix already in-flight to 3.11 stable kernels). Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Sep 25, 2013 at 09:56:52AM +0200, Daniel Vetter wrote: On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin m...@redhat.com wrote: On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] Hi, saw your posting in [1]... can you try the patches below? Not sure if they apply. Did you try v3.11-rc6(+)... or drm-intel-nightly? Regards, - Sedat - [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html Same thing observed with v3.11-rc7. I still see this with 3.11. Following this message, my VGA monitor goes blank and shows an error suggesting a wrong resolution or frequency are set. Anyone? Daniel, Jesse? still ongoing I think. Yeah, I've dismissed it since the original issue in this thread is resolved. But it's something else. Note to bug reporters: Please don't me-too, but start a new thread/report - almost every gfx bug is different, even if it superficially looks the same. Michael, can you please boot with drm.debug=0xe, reproduce the problem and then attach the complete dmesg? Please make sure dmesg contains everything since boot-up, if not please increase the dmesg buffer size with log_buf_len=4M. Also please test the latest drm-intel-fixes release to check that we haven't just forgotten to send the patch to stable (there's at least one flags mismatch fix already in-flight to 3.11 stable kernels). Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch Will do. Holidays starting now so expect some reports next week. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin wrote: > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: >> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] >> > >> > Hi, >> > >> > saw your posting in [1]... can you try the patches below? >> > Not sure if they apply. >> > Did you try v3.11-rc6(+)... or drm-intel-nightly? >> > >> > Regards, >> > - Sedat - >> > >> > [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html >> >> Same thing observed with v3.11-rc7. > > I still see this with 3.11. > Following this message, my VGA monitor goes blank and > shows an error suggesting a wrong resolution or frequency are set. > Anyone? Daniel, Jesse? still ongoing I think. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin m...@redhat.com wrote: On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] Hi, saw your posting in [1]... can you try the patches below? Not sure if they apply. Did you try v3.11-rc6(+)... or drm-intel-nightly? Regards, - Sedat - [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html Same thing observed with v3.11-rc7. I still see this with 3.11. Following this message, my VGA monitor goes blank and shows an error suggesting a wrong resolution or frequency are set. Anyone? Daniel, Jesse? still ongoing I think. Dave. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: > On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: > > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] > > > > Hi, > > > > saw your posting in [1]... can you try the patches below? > > Not sure if they apply. > > Did you try v3.11-rc6(+)... or drm-intel-nightly? > > > > Regards, > > - Sedat - > > > > [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html > > Same thing observed with v3.11-rc7. I still see this with 3.11. Following this message, my VGA monitor goes blank and shows an error suggesting a wrong resolution or frequency are set. Anyone? > > > > > -- Forwarded message -- > > From: Sedat Dilek > > Date: Tue, Jul 2, 2013 at 7:31 AM > > Subject: Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several > > call-traces ] > > To: Daniel Vetter > > Cc: "Barnes, Jesse" , Stephen Rothwell > > , linux-next , Linux > > Kernel Mailing List , intel-gfx > > , DRI > > , Dave Airlie > > > > > > On Mon, Jul 1, 2013 at 11:03 AM, Sedat Dilek wrote: > > > On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter > > > wrote: > > >> On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek > > >> wrote: > > >>> On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell > > >>> wrote: > > Hi all, > > > > Changes since 20130628: > > > > The regulator tree gained a build failure so I used the version from > > next-20130628. > > > > The trivial tree gained a conflict against the fbdev tree. > > > > The arm-soc tree gained a conflict against the net-next tree. > > > > The akpm tree lost a few patches that turned up elsewhere and I > > removed 2 > > that were causing run time problems. > > > > >>> > > >>> [ CC drm and drm-intel folks ] > > >>> > > >>> [ Did not check any relevant MLs ] > > >>> > > >>> Please, see attached dmesg output. > > >> > > >> Clock mismatch, one for Jesse to figure out. Note that this patch is > > >> for 3.12, I simply haven't yet gotten around to properly split my > > >> patch queue so a few spilled into -next. I'll do that now. > > > > > > I like lightspeed-fast replies :-). > > > > > > Guess "drm/i915: get mode clock when reading the pipe config v9" [1] > > > is the cause. > > > > > > > Problem solved by applying these patches to next-20130701 from > > intel-gfx patchwork-service [0]: > > > >[1/2] drm/i915: fixup messages in pipe_config_compare > >[2/2] drm/i915: get clock config when checking CRTC state too > > > > AFAICS 2/2 was folded into updated "drm/i915: get mode clock when > > reading the pipe config v9" [3]. > > > > It would be kind to be CCed on the patches and get also some credits. > > Also a CC to the report in linux-next should IMHO be done. > > > > - Sedat - > > > > [0] https://patchwork.kernel.org/project/intel-gfx/list/ > > [1] https://patchwork.kernel.org/patch/2809031/ > > [2] https://patchwork.kernel.org/patch/2809021/ > > [3] > > http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-nightly=f1f644dc66cbaf5a4c7dcde683361536b41885b9 > > > > > - Sedat - > > > > > > [1] > > > http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-next-queued=d325d8b4f351f9d45e7c8baabf581fd21f343133 > > > > > >> -Daniel > > >> -- > > >> Daniel Vetter > > >> Software Engineer, Intel Corporation > > >> +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] Hi, saw your posting in [1]... can you try the patches below? Not sure if they apply. Did you try v3.11-rc6(+)... or drm-intel-nightly? Regards, - Sedat - [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html Same thing observed with v3.11-rc7. I still see this with 3.11. Following this message, my VGA monitor goes blank and shows an error suggesting a wrong resolution or frequency are set. Anyone? -- Forwarded message -- From: Sedat Dilek sedat.di...@gmail.com Date: Tue, Jul 2, 2013 at 7:31 AM Subject: Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ] To: Daniel Vetter daniel.vet...@ffwll.ch Cc: Barnes, Jesse jbar...@virtuousgeek.org, Stephen Rothwell s...@canb.auug.org.au, linux-next linux-n...@vger.kernel.org, Linux Kernel Mailing List linux-kernel@vger.kernel.org, intel-gfx intel-...@lists.freedesktop.org, DRI dri-de...@lists.freedesktop.org, Dave Airlie airl...@gmail.com On Mon, Jul 1, 2013 at 11:03 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote: On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130628: The regulator tree gained a build failure so I used the version from next-20130628. The trivial tree gained a conflict against the fbdev tree. The arm-soc tree gained a conflict against the net-next tree. The akpm tree lost a few patches that turned up elsewhere and I removed 2 that were causing run time problems. [ CC drm and drm-intel folks ] [ Did not check any relevant MLs ] Please, see attached dmesg output. Clock mismatch, one for Jesse to figure out. Note that this patch is for 3.12, I simply haven't yet gotten around to properly split my patch queue so a few spilled into -next. I'll do that now. I like lightspeed-fast replies :-). Guess drm/i915: get mode clock when reading the pipe config v9 [1] is the cause. Problem solved by applying these patches to next-20130701 from intel-gfx patchwork-service [0]: [1/2] drm/i915: fixup messages in pipe_config_compare [2/2] drm/i915: get clock config when checking CRTC state too AFAICS 2/2 was folded into updated drm/i915: get mode clock when reading the pipe config v9 [3]. It would be kind to be CCed on the patches and get also some credits. Also a CC to the report in linux-next should IMHO be done. - Sedat - [0] https://patchwork.kernel.org/project/intel-gfx/list/ [1] https://patchwork.kernel.org/patch/2809031/ [2] https://patchwork.kernel.org/patch/2809021/ [3] http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-nightlyid=f1f644dc66cbaf5a4c7dcde683361536b41885b9 - Sedat - [1] http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-next-queuedid=d325d8b4f351f9d45e7c8baabf581fd21f343133 -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] > > Hi, > > saw your posting in [1]... can you try the patches below? > Not sure if they apply. > Did you try v3.11-rc6(+)... or drm-intel-nightly? > > Regards, > - Sedat - > > [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html Same thing observed with v3.11-rc7. > > -- Forwarded message -- > From: Sedat Dilek > Date: Tue, Jul 2, 2013 at 7:31 AM > Subject: Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces > ] > To: Daniel Vetter > Cc: "Barnes, Jesse" , Stephen Rothwell > , linux-next , Linux > Kernel Mailing List , intel-gfx > , DRI > , Dave Airlie > > > On Mon, Jul 1, 2013 at 11:03 AM, Sedat Dilek wrote: > > On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter > > wrote: > >> On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote: > >>> On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell > >>> wrote: > Hi all, > > Changes since 20130628: > > The regulator tree gained a build failure so I used the version from > next-20130628. > > The trivial tree gained a conflict against the fbdev tree. > > The arm-soc tree gained a conflict against the net-next tree. > > The akpm tree lost a few patches that turned up elsewhere and I removed 2 > that were causing run time problems. > > >>> > >>> [ CC drm and drm-intel folks ] > >>> > >>> [ Did not check any relevant MLs ] > >>> > >>> Please, see attached dmesg output. > >> > >> Clock mismatch, one for Jesse to figure out. Note that this patch is > >> for 3.12, I simply haven't yet gotten around to properly split my > >> patch queue so a few spilled into -next. I'll do that now. > > > > I like lightspeed-fast replies :-). > > > > Guess "drm/i915: get mode clock when reading the pipe config v9" [1] > > is the cause. > > > > Problem solved by applying these patches to next-20130701 from > intel-gfx patchwork-service [0]: > >[1/2] drm/i915: fixup messages in pipe_config_compare >[2/2] drm/i915: get clock config when checking CRTC state too > > AFAICS 2/2 was folded into updated "drm/i915: get mode clock when > reading the pipe config v9" [3]. > > It would be kind to be CCed on the patches and get also some credits. > Also a CC to the report in linux-next should IMHO be done. > > - Sedat - > > [0] https://patchwork.kernel.org/project/intel-gfx/list/ > [1] https://patchwork.kernel.org/patch/2809031/ > [2] https://patchwork.kernel.org/patch/2809021/ > [3] > http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-nightly=f1f644dc66cbaf5a4c7dcde683361536b41885b9 > > > - Sedat - > > > > [1] > > http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-next-queued=d325d8b4f351f9d45e7c8baabf581fd21f343133 > > > >> -Daniel > >> -- > >> Daniel Vetter > >> Software Engineer, Intel Corporation > >> +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] Hi, saw your posting in [1]... can you try the patches below? Not sure if they apply. Did you try v3.11-rc6(+)... or drm-intel-nightly? Regards, - Sedat - [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html Same thing observed with v3.11-rc7. -- Forwarded message -- From: Sedat Dilek sedat.di...@gmail.com Date: Tue, Jul 2, 2013 at 7:31 AM Subject: Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ] To: Daniel Vetter daniel.vet...@ffwll.ch Cc: Barnes, Jesse jbar...@virtuousgeek.org, Stephen Rothwell s...@canb.auug.org.au, linux-next linux-n...@vger.kernel.org, Linux Kernel Mailing List linux-kernel@vger.kernel.org, intel-gfx intel-...@lists.freedesktop.org, DRI dri-de...@lists.freedesktop.org, Dave Airlie airl...@gmail.com On Mon, Jul 1, 2013 at 11:03 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote: On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130628: The regulator tree gained a build failure so I used the version from next-20130628. The trivial tree gained a conflict against the fbdev tree. The arm-soc tree gained a conflict against the net-next tree. The akpm tree lost a few patches that turned up elsewhere and I removed 2 that were causing run time problems. [ CC drm and drm-intel folks ] [ Did not check any relevant MLs ] Please, see attached dmesg output. Clock mismatch, one for Jesse to figure out. Note that this patch is for 3.12, I simply haven't yet gotten around to properly split my patch queue so a few spilled into -next. I'll do that now. I like lightspeed-fast replies :-). Guess drm/i915: get mode clock when reading the pipe config v9 [1] is the cause. Problem solved by applying these patches to next-20130701 from intel-gfx patchwork-service [0]: [1/2] drm/i915: fixup messages in pipe_config_compare [2/2] drm/i915: get clock config when checking CRTC state too AFAICS 2/2 was folded into updated drm/i915: get mode clock when reading the pipe config v9 [3]. It would be kind to be CCed on the patches and get also some credits. Also a CC to the report in linux-next should IMHO be done. - Sedat - [0] https://patchwork.kernel.org/project/intel-gfx/list/ [1] https://patchwork.kernel.org/patch/2809031/ [2] https://patchwork.kernel.org/patch/2809021/ [3] http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-nightlyid=f1f644dc66cbaf5a4c7dcde683361536b41885b9 - Sedat - [1] http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-next-queuedid=d325d8b4f351f9d45e7c8baabf581fd21f343133 -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
