Hi,
The following commit permanently turns my screen off when x server is
started (i3 330M Ironlake):
[83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb
reference for the idr
Reverting this commit fixed the issue.
Thanks in advance.
Emmanuel
Adding relevant mailing lists.
On Sat, Nov 8, 2014 at 7:34 PM, Emmanuel Benisty <[email protected]> wrote:
> Hi,
>
> The following commit permanently turns my screen off when x server is
> started (i3 330M Ironlake):
>
> [83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb
> reference for the idr
>
> Reverting this commit fixed the issue.
This is definitely unexpected. I think we need a bit more data to
figure out what's going on here:
- Please boot with drm.debug=0xe added to your kernel cmdline and grab
the dmesg right after boot-up for both a working or broken kernel.
- Are you using any special i915 cmdline options?
Everything else should be in the debug logs I hope.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
Hi Daniel,
Thanks for your reply and very sorry for the belated reply, some gmail
filtering issues...
On Mon, Nov 10, 2014 at 10:19 PM, Daniel Vetter <[email protected]> wrote:
> Adding relevant mailing lists.
>
>
> On Sat, Nov 8, 2014 at 7:34 PM, Emmanuel Benisty <[email protected]> wrote:
>> Hi,
>>
>> The following commit permanently turns my screen off when x server is
>> started (i3 330M Ironlake):
>>
>> [83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb
>> reference for the idr
>>
>> Reverting this commit fixed the issue.
>
> This is definitely unexpected. I think we need a bit more data to
> figure out what's going on here:
> - Please boot with drm.debug=0xe added to your kernel cmdline and grab
> the dmesg right after boot-up for both a working or broken kernel.
Please see attached files.
> - Are you using any special i915 cmdline options?
Nope.
Thanks a lot,
Emmanuel
Hi Daniel,
> On Mon, Nov 10, 2014 at 10:19 PM, Daniel Vetter <[email protected]> wrote:
>> Adding relevant mailing lists.
>>
>>
>> On Sat, Nov 8, 2014 at 7:34 PM, Emmanuel Benisty <[email protected]> wrote:
>>> Hi,
>>>
>>> The following commit permanently turns my screen off when x server is
>>> started (i3 330M Ironlake):
>>>
>>> [83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb
>>> reference for the idr
>>>
>>> Reverting this commit fixed the issue.
>>
>> This is definitely unexpected. I think we need a bit more data to
>> figure out what's going on here:
>> - Please boot with drm.debug=0xe added to your kernel cmdline and grab
>> the dmesg right after boot-up for both a working or broken kernel.
>
> Please see attached files.
>
>> - Are you using any special i915 cmdline options?
>
> Nope.
Is there anything else I could provide to help fixing this issue? It's
still in Linus' tree.
Thanks in advance.
On Sun, Dec 14, 2014 at 02:07:19AM +0100, Emmanuel Benisty wrote:
> Hi Daniel,
>
> > On Mon, Nov 10, 2014 at 10:19 PM, Daniel Vetter <[email protected]> wrote:
> >> Adding relevant mailing lists.
> >>
> >>
> >> On Sat, Nov 8, 2014 at 7:34 PM, Emmanuel Benisty <[email protected]> wrote:
> >>> Hi,
> >>>
> >>> The following commit permanently turns my screen off when x server is
> >>> started (i3 330M Ironlake):
> >>>
> >>> [83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb
> >>> reference for the idr
> >>>
> >>> Reverting this commit fixed the issue.
> >>
> >> This is definitely unexpected. I think we need a bit more data to
> >> figure out what's going on here:
> >> - Please boot with drm.debug=0xe added to your kernel cmdline and grab
> >> the dmesg right after boot-up for both a working or broken kernel.
> >
> > Please see attached files.
> >
> >> - Are you using any special i915 cmdline options?
> >
> > Nope.
>
> Is there anything else I could provide to help fixing this issue? It's
> still in Linus' tree.
Sorry for the delay. Absolutely no difference in the relevant parts of the
log. There could be the chance that something is hidden somewhere, so can
please grab a new set of logs but this time with drm.debug=0xe?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
On Mon, Dec 15, 2014 at 8:31 AM, Daniel Vetter <[email protected]> wrote:
[---snip---]
> Sorry for the delay. Absolutely no difference in the relevant parts of the
> log. There could be the chance that something is hidden somewhere, so can
> please grab a new set of logs but this time with drm.debug=0xe?
Thanks for your reply Daniel. However, former logs were already
generated with drm.debug=0xe.
On Mon, Dec 15, 2014 at 12:46:09PM +0100, Emmanuel Benisty wrote:
> On Mon, Dec 15, 2014 at 8:31 AM, Daniel Vetter <[email protected]> wrote:
>
> [---snip---]
>
> > Sorry for the delay. Absolutely no difference in the relevant parts of the
> > log. There could be the chance that something is hidden somewhere, so can
> > please grab a new set of logs but this time with drm.debug=0xe?
>
> Thanks for your reply Daniel. However, former logs were already
> generated with drm.debug=0xe.
Argh, I've meant 0xf. That enables the super-verbose stuff which might
shed some light on what's happening differently here.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
On 14.12.2014, Emmanuel Benisty wrote:
> >>> The following commit permanently turns my screen off when x server is
> >>> started (i3 330M Ironlake):
> >>>
> >>> [83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb
> >>> reference for the idr
> >>>
> >>> Reverting this commit fixed the issue.
Haven't seen your mail until now. Seems to be the same bug that I'm encountering.
https://bugs.freedesktop.org/show_bug.cgi?id=87330
https://lkml.org/lkml/2014/12/14/26