lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 18 Nov 2008 11:15:33 +0000
From:	"Alan Jenkins" <alan-jenkins@...fmail.co.uk>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [ 11.333737] is this a ghost?

On 11/18/08, Justin P. Mattock <justinmattock@...il.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).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ