Daniel,
>>
>> the problem is still there with the latest 3.14.14. But the good news
>> is that I have finally been able to get a full dmesg log!
>> Please find it attached. I hope this helps and let me know what else I
>> need to do to assist.
>>
>> The log shows two hibernate-resume cycles, and y
On Mon, Aug 11, 2014 at 12:38:41AM +0100, Pedro Ribeiro wrote:
> On 2 June 2014 21:15, Pedro Ribeiro wrote:
> > On 27 May 2014 08:15, Daniel Vetter wrote:
> >> On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro wrote:
> >>> Kern.log is attached, but as you can see it does not contain the same
> >>>
On 2 June 2014 21:15, Pedro Ribeiro wrote:
> On 27 May 2014 08:15, Daniel Vetter wrote:
>> On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro wrote:
>>> Kern.log is attached, but as you can see it does not contain the same
>>> verbose drm debug information as dmesg... Should I just keep piping
>>> d
On 27 May 2014 08:15, Daniel Vetter wrote:
> On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro wrote:
>> Kern.log is attached, but as you can see it does not contain the same
>> verbose drm debug information as dmesg... Should I just keep piping
>> dmesg to a file and then cat it all together?
>> I
On Mon, May 26, 2014 at 9:44 PM, Pedro Ribeiro wrote:
> Kern.log is attached, but as you can see it does not contain the same
> verbose drm debug information as dmesg... Should I just keep piping
> dmesg to a file and then cat it all together?
> I never really understood why there are so many logs
On 26 May 2014 20:14, Daniel Vetter wrote:
> On Mon, May 26, 2014 at 9:07 PM, Pedro Ribeiro wrote:
>> sorry for my ignorance, but do you know where in a Debian system would
>> I have the full log output since boot time? The /var/log/dmesg does
>> not seem to contain all the output in the "dmesg"
On Mon, May 26, 2014 at 9:07 PM, Pedro Ribeiro wrote:
> sorry for my ignorance, but do you know where in a Debian system would
> I have the full log output since boot time? The /var/log/dmesg does
> not seem to contain all the output in the "dmesg" command.
/var/log/kern.log, althought that conta
On 26 May 2014 19:19, Daniel Vetter wrote:
> On Mon, May 26, 2014 at 8:07 PM, Pedro Ribeiro wrote:
>> On 26 May 2014 10:22, Jani Nikula wrote:
>>> On Sat, 24 May 2014, Pedro Ribeiro wrote:
Hi,
I'm getting this error consistently with the Debian 3.14.4 after
resuming from hib
On Mon, May 26, 2014 at 8:07 PM, Pedro Ribeiro wrote:
> On 26 May 2014 10:22, Jani Nikula wrote:
>> On Sat, 24 May 2014, Pedro Ribeiro wrote:
>>> Hi,
>>>
>>> I'm getting this error consistently with the Debian 3.14.4 after
>>> resuming from hibernation:
>>
>> Does this ever happen on a fresh boo
On 26 May 2014 10:22, Jani Nikula wrote:
> On Sat, 24 May 2014, Pedro Ribeiro wrote:
>> Hi,
>>
>> I'm getting this error consistently with the Debian 3.14.4 after
>> resuming from hibernation:
>
> Does this ever happen on a fresh boot or when resuming from suspend to
> ram?
>
> BR,
> Jani.
>
Hi
On Sat, 24 May 2014, Pedro Ribeiro wrote:
> Hi,
>
> I'm getting this error consistently with the Debian 3.14.4 after
> resuming from hibernation:
Does this ever happen on a fresh boot or when resuming from suspend to
ram?
BR,
Jani.
>
> [ 931.032142] [ cut here ]
> [ 9
Hi,
I'm getting this error consistently with the Debian 3.14.4 after
resuming from hibernation:
[ 931.032142] [ cut here ]
[ 931.032209] WARNING: CPU: 0 PID: 4715 at
/build/linux-Zc5oK7/linux-3.14.4/drivers/gpu/drm/i915/intel_panel.c:723
i965_enable_backlight+0x122/0x150
12 matches
Mail list logo
