On Tue, May 21, 2013 at 1:28 PM, Ben Guthro wrote:
> On Tue, May 21, 2013 at 10:02 AM, Daniel Vetter wrote:
>> On Tue, May 21, 2013 at 3:44 PM, Ben Guthro wrote:
>>>> This will break kms since now you have the vbios and the linux kms driver
>>>> fightin
On Tue, May 21, 2013 at 10:02 AM, Daniel Vetter wrote:
> On Tue, May 21, 2013 at 3:44 PM, Ben Guthro wrote:
>>> This will break kms since now you have the vbios and the linux kms driver
>>> fighting over the same piece of hw. Does
>>>
>>> xset dpms force o
On Tue, May 21, 2013 at 9:44 AM, Ben Guthro wrote:
> On Tue, May 21, 2013 at 4:00 AM, Daniel Vetter wrote:
>> On Fri, May 17, 2013 at 09:26:18AM -0400, Ben Guthro wrote:
>>> On Fri, May 17, 2013 at 7:52 AM, Ben Guthro wrote:
>>> > On Thu, May 16, 2013 at 9:24 AM
On Tue, May 21, 2013 at 4:00 AM, Daniel Vetter wrote:
> On Fri, May 17, 2013 at 09:26:18AM -0400, Ben Guthro wrote:
>> On Fri, May 17, 2013 at 7:52 AM, Ben Guthro wrote:
>> > On Thu, May 16, 2013 at 9:24 AM, Ben Guthro wrote:
>> >> On Wed, May 15, 2013 at 4:42 PM
On Fri, May 17, 2013 at 7:52 AM, Ben Guthro wrote:
> On Thu, May 16, 2013 at 9:24 AM, Ben Guthro wrote:
>> On Wed, May 15, 2013 at 4:42 PM, Ben Guthro wrote:
>>> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro wrote:
>>>> I am attempting to debug an issue wi
On Thu, May 16, 2013 at 9:24 AM, Ben Guthro wrote:
> On Wed, May 15, 2013 at 4:42 PM, Ben Guthro wrote:
>> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro wrote:
>>> I am attempting to debug an issue with some Haswell laptop systems
>>> which do not restore their screen
On Wed, May 15, 2013 at 4:42 PM, Ben Guthro wrote:
> On Tue, May 14, 2013 at 5:01 PM, Ben Guthro wrote:
>> I am attempting to debug an issue with some Haswell laptop systems
>> which do not restore their screen after resuming from S3 when running
>> on the stable 3.8 k
On Tue, May 14, 2013 at 5:01 PM, Ben Guthro wrote:
> I am attempting to debug an issue with some Haswell laptop systems
> which do not restore their screen after resuming from S3 when running
> on the stable 3.8 kernel (3.8.13)
> The backlight is OK, but the screen is just black.
>
I am attempting to debug an issue with some Haswell laptop systems
which do not restore their screen after resuming from S3 when running
on the stable 3.8 kernel (3.8.13)
The backlight is OK, but the screen is just black.
In trying to determine what was going wrong, I tried looking at the
output o
; >>> On 05.03.13 at 17:33, Ben Guthro wrote:
> > I turned up the debug, but didn't see this
> > I am seeing other oops messages in the log now though...not sure if these
> > are related.
>
> The first one likely is related (rax being 00aa00aa and
>
On Wed, Nov 7, 2012 at 2:43 PM, Ben Guthro wrote:
>>
>>
>> There seems to be a mismatch for these IRQ delivery - or at least exhibits
>> the behavior similar to such a problem.
>>
>
> I was mistaken here. The i8042 IRQ would just start up the IRQ handling -
On Wed, Nov 7, 2012 at 11:22 AM, Ben Guthro wrote:
> I'm trying to debug an issue on an older lapop (Toshiba Satellite A505) -
> that has an i3 processor (M330) - and intel graphics.
> This is running under Xen-unstable, and a 3.7-rc4 pvops kernel - but can
> also be reproduced
I'm trying to debug an issue on an older lapop (Toshiba Satellite A505) -
that has an i3 processor (M330) - and intel graphics.
This is running under Xen-unstable, and a 3.7-rc4 pvops kernel - but can
also be reproduced using kernels as old as 3.2.23 - and hypervisors as old
as 4.0.4
(I have cross
bit with Paulo's new
> way of handling ddi/fdi on haswell, we somehow never bothered with the
> real fix. Should be quite as soon as Paulo's patchbomb lands.
> -Daniel
>
> >
> > Thanks
> > --xingchao
> >
> > From: ben.gut...@gmail.com [mailto:
I am seeing this same trace (and no video) on multiple Haswell SDP's, with
3.6-rc7 (and earlier kernels)
Was there ever a resolution on this?
On Wed, Aug 15, 2012 at 3:24 AM, Wang, Xingchao wrote:
> Hi,
>
> Some update related to this warning.
> Ironlake_crtc_dpms() will enable/disable crtc wh
[ end trace 941488b1333d181e ]---
On Fri, Aug 10, 2012 at 10:21 PM, Ben Guthro wrote:
> I'll try to do this early next week, and report back.
>
>
> On Fri, Aug 10, 2012 at 7:37 PM, Ben Widawsky wrote:
>> On 2012-08-10 09:25, Ben Guthro wrote:
>>>
>>>
I'll try to do this early next week, and report back.
On Fri, Aug 10, 2012 at 7:37 PM, Ben Widawsky wrote:
> On 2012-08-10 09:25, Ben Guthro wrote:
>>
>> Hello, I've been attempting to get a Shark Bay / Haswell platform up &
>> running, and have been having so
0x200
[ 16.923652] [] system_call_fastpath+0x16/0x1b
[ 16.930548] ---[ end trace fa81da3bacf4c4b0 ]---
On Fri, Aug 10, 2012 at 1:16 PM, Daniel Vetter wrote:
> On Fri, Aug 10, 2012 at 12:51:42PM -0400, Ben Guthro wrote:
>> specifically, I get the following in my serial console - it is a
&g
] [] sys_init_module+0x8f/0x200
[ 16.251599] [] system_call_fastpath+0x16/0x1b
[ 16.258494] ---[ end trace 949ccd38b0452265 ]---
On Fri, Aug 10, 2012 at 12:25 PM, Ben Guthro wrote:
> Hello, I've been attempting to get a Shark Bay / Haswell platform up &
> running, and have b
Hello, I've been attempting to get a Shark Bay / Haswell platform up &
running, and have been having some difficulties that I'm hoping you
all can possibly help with.
I first tried the 3.5 kernel, and had some success after applying the
following patch:
https://patchwork.kernel.org/patch/1229541/
issues on other platforms?
On Wed, Feb 1, 2012 at 10:17 AM, Ben Guthro wrote:
> I'm moving my company's distro from 2.6.38 to 3.2.X (currently 3.2.2)
> - and have found a regression in i915 that I'm hoping someone here
> might have a fix for, already.
>
> On so
ny thoughts, patches, suggestions are appreciated.
- Ben Guthro
[ 28.064432] [ cut here ]
[ 28.064468] WARNING: at
/builds/orc-precise/linux-3.2/drivers/gpu/drm/i915/intel_dp.c:1071
ironlake_edp_panel_vdd_off+0xbf/0xd0 [i915]()
[ 28.064472] Hardware name: Latitude E551
Sorry. no change in behavior, with my E6410.
On Tue, Jun 29, 2010 at 9:46 PM, Dave Airlie wrote:
> From: Dave Airlie
>
> The eDP spec claims a 20% overhead for the 8:10 encoding scheme used on the
> wire. Take this into account when picking the lane/clock speed for the panel.
>
> v3: some panel
This also didn't fix the Dell E6410. I'll also note this in the bug.
I'm trying to work with some contacts at Dell to get this routed to
the right person as well...but am having limited luck with that, so
far.
On Mon, Jun 28, 2010 at 2:28 AM, Dave Airlie wrote:
> On Mon, Jun 28, 2010 at 4:04 PM,
FWIW, this didn't seem solve the boot issue I'm seeing with the Dell E6410...
On Fri, Jun 25, 2010 at 2:59 AM, Keith Packard wrote:
> On Fri, 25 Jun 2010 16:21:40 +1000, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> We've just gotten an eDP laptop, and kms was booting to a black screen.
>>
>>
FWIW, I filed a bug here on this issue, to have something to attach
the output of various useful info
https://bugs.freedesktop.org/show_bug.cgi?id=28746
On Thu, Jun 24, 2010 at 2:55 PM, Ben Guthro
wrote:
> I posted a similar question to LKML yesterday, but perhaps this is a
> better for
I posted a similar question to LKML yesterday, but perhaps this is a
better forum for this discussion, as it seemed to get lost amongst
many other non-graphics related discussions.
I have a problematic machine, that I have traced the problem down to
what I think is an issue with the i915 detection
27 matches
Mail list logo
