2014-05-16 13:53 GMT+02:00 Ville Syrjälä :
> On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
>> On Tue, May 13, 2014 at 05:21:49PM +0200, Jörg Otte wrote:
>> > 2014-05-13 15:22 GMT+02:00 Daniel Vetter :
>> > > On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
>> > >> On
On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
> On Tue, May 13, 2014 at 05:21:49PM +0200, Jörg Otte wrote:
> > 2014-05-13 15:22 GMT+02:00 Daniel Vetter :
> > > On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
> > >> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
On Tue, May 13, 2014 at 05:46:31PM +0100, Damien Lespiau wrote:
> On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
> > > Doesn't work for me, I still have an underrun at boot-up.
> >
> > I'm at a loss tbh with ideas. We successfully disable both pipes, then
> > enable pipe A and it a
On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
> > Doesn't work for me, I still have an underrun at boot-up.
>
> I'm at a loss tbh with ideas. We successfully disable both pipes, then
> enable pipe A and it all works.
>
> Then we enable pipe B and _both_ pipes underrun immediately
On Tue, May 13, 2014 at 05:21:49PM +0200, Jörg Otte wrote:
> 2014-05-13 15:22 GMT+02:00 Daniel Vetter :
> > On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
> >> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
> >> >>> Branch drm-intel-nightly as of
> >> >>> ed60c27 drm-intel-nigh
2014-05-13 15:22 GMT+02:00 Daniel Vetter :
> On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
>> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
>> >>> Branch drm-intel-nightly as of
>> >>> ed60c27 drm-intel-nightly: 2014y-05m-09d-21h-51m-45s integration manifest
>> >>> looks badl
On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
> >>> Branch drm-intel-nightly as of
> >>> ed60c27 drm-intel-nightly: 2014y-05m-09d-21h-51m-45s integration manifest
> >>> looks badly:
> >>>- KDE splash screen on boot-up is not
On Tue, May 13, 2014 at 12:59 PM, Chris Wilson wrote:
> On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
>> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
>> >>> Branch drm-intel-nightly as of
>> >>> ed60c27 drm-intel-nightly: 2014y-05m-09d-21h-51m-45s integration manifest
>> >>
On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
> >>> Branch drm-intel-nightly as of
> >>> ed60c27 drm-intel-nightly: 2014y-05m-09d-21h-51m-45s integration manifest
> >>> looks badly:
> >>>- KDE splash screen on boot-up is not
On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
>>> Branch drm-intel-nightly as of
>>> ed60c27 drm-intel-nightly: 2014y-05m-09d-21h-51m-45s integration manifest
>>> looks badly:
>>>- KDE splash screen on boot-up is not visible
>>>- x-windows don't have title and menu bars
>>>- KDE s
2014-05-12 21:03 GMT+02:00 Daniel Vetter :
> On Mon, May 12, 2014 at 01:25:24PM +0200, Jörg Otte wrote:
>> 2014-05-11 18:49 GMT+02:00 Daniel Vetter :
>> > On Sat, May 10, 2014 at 10:52 AM, Jörg Otte wrote:
>> >>> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>> On Fri, May 0
On Mon, May 12, 2014 at 01:25:24PM +0200, Jörg Otte wrote:
> 2014-05-11 18:49 GMT+02:00 Daniel Vetter :
> > On Sat, May 10, 2014 at 10:52 AM, Jörg Otte wrote:
> >>> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
> >
2014-05-11 18:49 GMT+02:00 Daniel Vetter :
> On Sat, May 10, 2014 at 10:52 AM, Jörg Otte wrote:
>>> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
> > Jörg, can you please boot with drm.debug=0xe, reproduce the i
On Sat, May 10, 2014 at 10:52 AM, Jörg Otte wrote:
>> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>>> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
>>> > > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
>>> > > then attach the complete dmesg?
On Fri, May 9, 2014 at 11:18 PM, Dave Airlie wrote:
> Please don't make things more prominent if the fixes can't be merged
> without rewriting the world,
>
> Distros have auto reporting tools for the major backtrace warnings,
> and releasing kernels with unfixable ones in it make it hard to know
>
2014-05-09 19:03 GMT+02:00 Ville Syrjälä :
> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
>> > > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
>> > > then attach the complete dmesg? Please make
On 10 May 2014 03:03, Ville Syrjälä wrote:
> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
>> > > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
>> > > then attach the complete dmesg? Please make
On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
> > > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
> > > then attach the complete dmesg? Please make sure that the dmesg
> > > contains the boot-up s
On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
> > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
> > then attach the complete dmesg? Please make sure that the dmesg
> > contains the boot-up stuff too.
> >
> > Thanks, Daniel
> Here it is. I should mention it only
19 matches
Mail list logo
