From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Levitsky Subject: Re: Another bad usage of smp_processor_id Date: Sun, 12 Sep 2010 11:37:57 +0200 Message-ID: <1284284277.2928.6.camel@maxim-laptop> References: <1283077579.5529.2.camel@maxim-laptop> <1283336736.3564.0.camel@maxim-laptop> <1283493662.2111.3158.camel@rui> <1283847507.2750.1.camel@maxim-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:62011 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752027Ab0ILJiC (ORCPT ); Sun, 12 Sep 2010 05:38:02 -0400 Received: by fxm16 with SMTP id 16so2619685fxm.19 for ; Sun, 12 Sep 2010 02:38:00 -0700 (PDT) In-Reply-To: <1283847507.2750.1.camel@maxim-laptop> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Zhang Rui Cc: "linux-acpi@vger.kernel.org" On Tue, 2010-09-07 at 11:18 +0300, Maxim Levitsky wrote: > On Fri, 2010-09-03 at 14:01 +0800, Zhang Rui wrote: > > Hi, Maxim, > > > > please try this patch and see if the problem still exists. :) > Yes it does :) > And its worse since my system now panics on resume... > Kernel log attached. Ping. Best regards, Maxim Levitsky