On Sun, 2010-08-15 at 21:01 -0700, Linus Torvalds wrote:
> On Sun, Aug 15, 2010 at 8:30 PM, Dave Airlie wrote:
> >
> > At least we should replace mdelay with msleep in those functions.
>
> How precise does the timing have to be? I think i2c is self-clocking,
> so it's ok to see big skews?
On Sun, 2010-08-15 at 19:32 -0700, Linus Torvalds wrote:
> I started wondering why 'top' was showing an otherwise idle system as
> having a load average of 0.5+, and worker threads constantly using the
> CPU.
>
> So I did a system-wide profile, and got the attached output (look at
> it in a
On Mon, 2010-08-16 at 10:27 -0400, Andy Lutomirski wrote:
> But that's really the problem, because intel_sdvo_dvi_init contains:
>
> connector->polled = DRM_CONNECTOR_POLL_CONNECT |
> DRM_CONNECTOR_POLL_DISCONNECT;
>
> I don't know if SDVO is supposed to send hotplug interrupts
[cc: intel-gfx]
Linus Torvalds wrote:
> On Sun, Aug 15, 2010 at 9:06 PM, Andy Lutomirski
> wrote:
>> You might be hitting the infamous hotplug storm [1]. The symptoms vary by
>> kernel version.
>
> Hmm. I don't think it's a storm. The drm.debug=4 thing shows things
> just every 10
On Sun, Aug 15, 2010 at 07:32:15PM -0700, Linus Torvalds wrote:
> I started wondering why 'top' was showing an otherwise idle system as
> having a load average of 0.5+, and worker threads constantly using the
> CPU.
>
> So I did a system-wide profile, and got the attached output (look at
> it in
Linus Torvalds wrote:
> I started wondering why 'top' was showing an otherwise idle system as
> having a load average of 0.5+, and worker threads constantly using the
> CPU.
>
> So I did a system-wide profile, and got the attached output (look at
> it in a really wide terminal).
>
> There seems
Linus Torvalds wrote:
I started wondering why 'top' was showing an otherwise idle system as
having a load average of 0.5+, and worker threads constantly using the
CPU.
So I did a system-wide profile, and got the attached output (look at
it in a really wide terminal).
There seems to be
[cc: intel-gfx]
Linus Torvalds wrote:
On Sun, Aug 15, 2010 at 9:06 PM, Andy Lutomirski l...@myrealbox.com wrote:
You might be hitting the infamous hotplug storm [1]. The symptoms vary by
kernel version.
Hmm. I don't think it's a storm. The drm.debug=4 thing shows things
just every 10
On Sun, Aug 15, 2010 at 9:06 PM, Andy Lutomirski wrote:
>
> You might be hitting the infamous hotplug storm [1]. ?The symptoms vary by
> kernel version.
Hmm. I don't think it's a storm. The drm.debug=4 thing shows things
just every 10 seconds. That seems pretty controlled.
Of course, it seems
On Sun, Aug 15, 2010 at 8:30 PM, Dave Airlie wrote:
>
> At least we should replace mdelay with msleep in those functions.
How precise does the timing have to be? I think i2c is self-clocking,
so it's ok to see big skews? Becuase msleep() can be off by quite a
bit (mdelay can too, but it's _way_
I started wondering why 'top' was showing an otherwise idle system as
having a load average of 0.5+, and worker threads constantly using the
CPU.
So I did a system-wide profile, and got the attached output (look at
it in a really wide terminal).
There seems to be something _seriously_ wrong with
On Sun, Aug 15, 2010 at 07:32:15PM -0700, Linus Torvalds wrote:
I started wondering why 'top' was showing an otherwise idle system as
having a load average of 0.5+, and worker threads constantly using the
CPU.
So I did a system-wide profile, and got the attached output (look at
it in a
On Sun, 2010-08-15 at 19:32 -0700, Linus Torvalds wrote:
I started wondering why 'top' was showing an otherwise idle system as
having a load average of 0.5+, and worker threads constantly using the
CPU.
So I did a system-wide profile, and got the attached output (look at
it in a really wide
On Sun, Aug 15, 2010 at 8:30 PM, Dave Airlie airl...@redhat.com wrote:
At least we should replace mdelay with msleep in those functions.
How precise does the timing have to be? I think i2c is self-clocking,
so it's ok to see big skews? Becuase msleep() can be off by quite a
bit (mdelay can too,
On Sun, Aug 15, 2010 at 9:06 PM, Andy Lutomirski l...@myrealbox.com wrote:
You might be hitting the infamous hotplug storm [1]. The symptoms vary by
kernel version.
Hmm. I don't think it's a storm. The drm.debug=4 thing shows things
just every 10 seconds. That seems pretty controlled.
Of
On Sun, 2010-08-15 at 21:01 -0700, Linus Torvalds wrote:
On Sun, Aug 15, 2010 at 8:30 PM, Dave Airlie airl...@redhat.com wrote:
At least we should replace mdelay with msleep in those functions.
How precise does the timing have to be? I think i2c is self-clocking,
so it's ok to see big
16 matches
Mail list logo
