From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1752537AbYKRLPp@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752537AbYKRLPp (ORCPT <rfc822;w@1wt.eu>);
	Tue, 18 Nov 2008 06:15:45 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751902AbYKRLPg
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 18 Nov 2008 06:15:36 -0500
Received: from mail-gx0-f29.google.com ([209.85.217.29]:59017 "EHLO
	mail-gx0-f29.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751715AbYKRLPf (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 18 Nov 2008 06:15:35 -0500
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=XVYdQIP09rXMCKdkUx6ZzGk3+5onBr8CrQyCjkaJSlNP2jm9+xpdZFI2mHkZ72Xvha
         2F3OKIxCvZFcM4+f2U+B5Pe68E05gAtf0Q7BXkMELhBHT1NePuAXdYW2kPdQRW0HmdNk
         TuLaxwxBEdKrxLRSS7XbsOktIiTUjp5stCIuA=
Message-ID: <9b2b86520811180315u410019f0y7e6fab66b51a225e@mail.gmail.com>
Date: Tue, 18 Nov 2008 11:15:33 +0000
From: "Alan Jenkins" <alan-jenkins@tuffmail.co.uk>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Subject: Re: [ 11.333737] is this a ghost?
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <1227001038.3184.6.camel@LiNuX>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1227001038.3184.6.camel@LiNuX>
X-Google-Sender-Auth: f890f4309a59106c
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 11/18/08, Justin P. Mattock <justinmattock@gmail.com> wrote:
> in dmesg I see:
> [   11.333737]
> but nothing else.
>           ---------------(cut)-----------------
> [   11.247147] Monitor-Mwait will be used to enter C-1 state
> [   11.247151] Monitor-Mwait will be used to enter C-2 state
> [   11.247154] Monitor-Mwait will be used to enter C-3 state
> [   11.247671] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
> [   11.247996] processor ACPI_CPU:00: registered as cooling_device0
> [   11.248008] ACPI: Processor [CPU0] (supports 8 throttling states)
> [   11.306465] ACPI: SSDT 3FEB8F10, 0087 (r1 APPLE   Cpu1Ist     3000
> INTL 20050309)<7>power_supply ADP1: No power supply yet

Look at this last line.  The "<7>" is a priority marker.  Normally it
marks the start of a line, and should be hidden.  So you seem to be
missing a line break just after "20050309)"...

> [   11.306831] power_supply ADP1: power_supply_changed
> [   11.306839] ACPI: AC Adapter [ADP1] (on-line)
> [   11.333737]                         <------------what's with this!!!

...which seems to be delayed and reappears here?

> [   11.342937] power_supply ADP1: power_supply_changed_work
> [   11.351901] power_supply ADP1: power_supply_update_gen_leds 1
> [   11.351916] ACPI: SSDT 3FEB7F10, 0085 (r1 APPLE   Cpu1Cst     3000
> INTL 20050309)

> if you need to see the full dmesg I can attach..
> I've seen this happen on a random.

I guess you have a multicore processor (or some other sort of SMP), right?

I think kernel messages are not completely synchronized by design, for
reliability reasons.  (e.g. to make sure critical error messages /
backtraces can get through on a dying system).