From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750745AbWHOWKs (ORCPT ); Tue, 15 Aug 2006 18:10:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750747AbWHOWKs (ORCPT ); Tue, 15 Aug 2006 18:10:48 -0400 Received: from mx1.redhat.com ([66.187.233.31]:21937 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1750745AbWHOWKr (ORCPT ); Tue, 15 Aug 2006 18:10:47 -0400 Date: Tue, 15 Aug 2006 18:10:35 -0400 From: Dave Jones To: Linux Kernel Subject: peculiar suspend/resume bug. Message-ID: <20060815221035.GX7612@redhat.com> Mail-Followup-To: Dave Jones , Linux Kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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? Dave -- http://www.codemonkey.org.uk