On Tue, Jan 31, 2012 at 8:06 PM, Seth Forshee
wrote:
> On Fri, Jan 20, 2012 at 05:08:31PM -0600, Seth Forshee wrote:
>> > Can you track down who is calling the connector->detect() callbacks
>> > during suspend and resume?
>>
>> I got two different stack traces, see below.
>>
>> And to slightly ame
On Tue, Jan 31, 2012 at 8:06 PM, Seth Forshee
wrote:
> On Fri, Jan 20, 2012 at 05:08:31PM -0600, Seth Forshee wrote:
>> > Can you track down who is calling the connector->detect() callbacks
>> > during suspend and resume?
>>
>> I got two different stack traces, see below.
>>
>> And to slightly ame
On Fri, Jan 20, 2012 at 05:08:31PM -0600, Seth Forshee wrote:
> > Can you track down who is calling the connector->detect() callbacks
> > during suspend and resume?
>
> I got two different stack traces, see below.
>
> And to slightly amend my statement above, I'm only seeing the wrong
> status re
On Fri, Jan 20, 2012 at 05:08:31PM -0600, Seth Forshee wrote:
> > Can you track down who is calling the connector->detect() callbacks
> > during suspend and resume?
>
> I got two different stack traces, see below.
>
> And to slightly amend my statement above, I'm only seeing the wrong
> status re
On Fri, Jan 20, 2012 at 11:09:29PM +0200, Pasi Kärkkäinen wrote:
> On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> > On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote:
> > > On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
> > > wrote:
> > > > I'm seeing several issues rel
On Fri, Jan 20, 2012 at 04:39:31PM -0500, Alex Deucher wrote:
> On Fri, Jan 20, 2012 at 4:12 PM, Seth Forshee
> wrote:
> > On Fri, Jan 20, 2012 at 02:38:37PM -0500, Alex Deucher wrote:
> >> On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
> >> wrote:
> >> > On Thu, Jan 19, 2012 at 02:53:17PM -0600,
On Fri, Jan 20, 2012 at 02:38:37PM -0500, Alex Deucher wrote:
> On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
> wrote:
> > On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> >> > > 2. Occasional long delays when suspending. When this happens I see
> >> > > messages like following
On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> > > 2. Occasional long delays when suspending. When this happens I see
> > > messages like following in dmesg:
> > >
> > > [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
> > > 5secs aborting
> > > [drm:a
On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote:
> > On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
> > wrote:
> > > I'm seeing several issues related to the radeon driver on a MacBook Pro
> > > 8,2 with the following gra
On Fri, Jan 20, 2012 at 11:09:29PM +0200, Pasi K?rkk?inen wrote:
> On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> > On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote:
> > > On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
> > > wrote:
> > > > I'm seeing several issues rel
On Fri, Jan 20, 2012 at 04:39:31PM -0500, Alex Deucher wrote:
> On Fri, Jan 20, 2012 at 4:12 PM, Seth Forshee
> wrote:
> > On Fri, Jan 20, 2012 at 02:38:37PM -0500, Alex Deucher wrote:
> >> On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
> >> wrote:
> >> > On Thu, Jan 19, 2012 at 02:53:17PM -0600,
On Fri, Jan 20, 2012 at 4:12 PM, Seth Forshee
wrote:
> On Fri, Jan 20, 2012 at 02:38:37PM -0500, Alex Deucher wrote:
>> On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
>> wrote:
>> > On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
>> >> > > ?2. Occasional long delays when suspending.
On Fri, Jan 20, 2012 at 02:38:37PM -0500, Alex Deucher wrote:
> On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
> wrote:
> > On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> >> > > ?2. Occasional long delays when suspending. When this happens I see
> >> > > ? ?messages like following
On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
wrote:
> On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
>> > > ?2. Occasional long delays when suspending. When this happens I see
>> > > ? ?messages like following in dmesg:
>> > >
>> > > ? ? ?[drm:atom_op_jump] *ERROR* atombios stuck
On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote:
> > On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
> > wrote:
> > > I'm seeing several issues related to the radeon driver on a MacBook Pro
> > > 8,2 with the following gra
On Fri, Jan 20, 2012 at 4:12 PM, Seth Forshee
wrote:
> On Fri, Jan 20, 2012 at 02:38:37PM -0500, Alex Deucher wrote:
>> On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
>> wrote:
>> > On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
>> >> > > 2. Occasional long delays when suspending.
On Fri, Jan 20, 2012 at 10:53 AM, Seth Forshee
wrote:
> On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
>> > > 2. Occasional long delays when suspending. When this happens I see
>> > > messages like following in dmesg:
>> > >
>> > > [drm:atom_op_jump] *ERROR* atombios stuck
On Thu, Jan 19, 2012 at 02:53:17PM -0600, Seth Forshee wrote:
> > > ?2. Occasional long delays when suspending. When this happens I see
> > > ? ?messages like following in dmesg:
> > >
> > > ? ? ?[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
> > > 5secs aborting
> > > ? ? ?[drm:a
On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote:
> On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
> wrote:
> > I'm seeing several issues related to the radeon driver on a MacBook Pro
> > 8,2 with the following graphics card:
> >
> > ATI Technologies Inc Whistler [AMD Radeon HD 6600M
On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote:
> On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
> wrote:
> > I'm seeing several issues related to the radeon driver on a MacBook Pro
> > 8,2 with the following graphics card:
> >
> > ?ATI Technologies Inc Whistler [AMD Radeon HD 6600M
On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
wrote:
> I'm seeing several issues related to the radeon driver on a MacBook Pro
> 8,2 with the following graphics card:
>
> ?ATI Technologies Inc Whistler [AMD Radeon HD 6600M Series] [1002:6741]
>
> All problems were observed when using kernel versi
On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
wrote:
> I'm seeing several issues related to the radeon driver on a MacBook Pro
> 8,2 with the following graphics card:
>
> ATI Technologies Inc Whistler [AMD Radeon HD 6600M Series] [1002:6741]
>
> All problems were observed when using kernel versi
I'm seeing several issues related to the radeon driver on a MacBook Pro
8,2 with the following graphics card:
ATI Technologies Inc Whistler [AMD Radeon HD 6600M Series] [1002:6741]
All problems were observed when using kernel version 3.2.1. None are
seen when using fglrx.
1. Excessive power d
I'm seeing several issues related to the radeon driver on a MacBook Pro
8,2 with the following graphics card:
ATI Technologies Inc Whistler [AMD Radeon HD 6600M Series] [1002:6741]
All problems were observed when using kernel version 3.2.1. None are
seen when using fglrx.
1. Excessive power d
24 matches
Mail list logo