Subject: Re: peculiar suspend/resume bug.
From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <20060815221035.GX7612@redhat.com>
References: <20060815221035.GX7612@redhat.com>
Content-Type: text/plain
Date: Wed, 16 Aug 2006 10:19:59 +1000
Message-Id: <1155687599.3193.12.camel@nigel.suspend2.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 924
Lines: 30

Hi Dave.

On Tue, 2006-08-15 at 18:10 -0400, Dave Jones wrote:
> Here's a fun one.
> - Get a dual core cpufreq aware laptop (Like say, a core-duo)
> - Add a cpufreq monitor to gnome-panel. Configure it
>   to watch the 2nd core.
> - Suspend.
> - Resume.
> 
> Watch the cpufreq monitor die horribly.
> 
> I believe this is because we take down the 2nd core at suspend
> time with cpu hotplug, and for some reason we're scheduling
> userspace before we bring that second core back up.
> 
> Anyone have any clues why this is happening?

If you hotunplug and replug the cpu using the sysfs interface, rather
than suspending and resuming, does the same thing happen?

Regards,

Nigel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/