From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: "Richard Schütz" <r.schtz@t-online.de>,
"Lionel Debroux" <lionel_debroux@yahoo.fr>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)
Date: Fri, 4 Feb 2011 21:36:19 +0100 [thread overview]
Message-ID: <201102042136.20165.rjw@sisk.pl> (raw)
In-Reply-To: <201102040844.05490.ozan@pardus.org.tr>
On Friday, February 04, 2011, Ozan Çağlayan wrote:
> Cuma 04 Şubat 2011 günü (saat 00:51:31) Rafael J. Wysocki şunları yazmıştı:
>
> > Hmm. Are those boxes uniprocessor running SMP kernels?
>
> The kernel is SMP.
>
> ASUS X61S is
> CPU0: Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz stepping 0a
>
> F50SV has 2 CPU's too according to dmesg:
> [ 0.000000] Processor #0 (Bootup-CPU)
> [ 0.000000] Processor #1
> [ 0.000000] I/O APIC #2 Version 20 at 0xFEC00000.
> [ 0.000000] IOAPIC[0]: apic_id 2, version 20, address 0xfec00000, GSI 0-23
> [ 0.000000] Processors: 2
> [ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
>
> ASUS N51JQ (occasional shutdown hang) has:
> CPU0: Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz stepping 05
> [ 0.132435] Booting Node 0, Processors #1 #2 #3 #4 #5 #6 #7 Ok.
> [ 0.768809] Brought up 8 CPUs
OK, so it's not the case I was thinking of. Ohwell.
At this point I guess it's best to open a bug entry in the kernel Bugzilla,
against ACPI (although ACPI may be a red herring), and put some system
information (ie. dmesg outputs from working kernels, if any, outputs of
acpidump) -- or links to where it can be found.
Thanks,
Rafael
next prev parent reply other threads:[~2011-02-04 20:36 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 14:28 Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Ozan Çağlayan
2011-01-23 15:00 ` Richard Schütz
2011-01-23 15:11 ` Gene Heskett
2011-01-23 16:49 ` Ozan Çağlayan
2011-01-23 16:56 ` Ozan Çağlayan
2011-01-23 20:24 ` Ozan Çağlayan
2011-01-23 20:24 ` Ozan Çağlayan
2011-01-24 9:00 ` Ozan Çağlayan
2011-01-24 9:04 ` Lionel Debroux
2011-01-24 9:04 ` Lionel Debroux
2011-01-24 9:21 ` Ozan Çağlayan
2011-01-24 9:47 ` Lionel Debroux
2011-01-24 9:47 ` Lionel Debroux
2011-01-24 20:14 ` Lionel Debroux
2011-01-25 2:56 ` Len Brown
2011-01-26 7:41 ` Lionel Debroux
2011-01-27 7:59 ` Lionel Debroux
2011-01-25 6:22 ` Ozan Çağlayan
2011-01-25 19:38 ` Rafael J. Wysocki
2011-01-25 19:38 ` Rafael J. Wysocki
2011-01-25 19:45 ` Ozan Çağlayan
2011-01-25 19:54 ` Rafael J. Wysocki
2011-01-25 19:54 ` Rafael J. Wysocki
2011-01-25 20:00 ` Ozan Çağlayan
2011-01-29 17:49 ` Ozan Çağlayan
2011-01-30 20:30 ` Ozan Çağlayan
2011-01-30 20:30 ` Ozan Çağlayan
2011-01-30 22:48 ` Rafael J. Wysocki
2011-01-31 8:53 ` Ozan Çağlayan
2011-01-31 9:50 ` Rafael J. Wysocki
2011-01-31 9:50 ` Rafael J. Wysocki
2011-01-31 10:03 ` Ozan Çağlayan
2011-01-31 10:14 ` Rafael J. Wysocki
2011-01-31 10:14 ` Rafael J. Wysocki
2011-01-31 10:20 ` Richard Schütz
2011-01-31 10:23 ` Rafael J. Wysocki
2011-01-31 10:29 ` Richard Schütz
2011-01-31 10:29 ` Richard Schütz
2011-01-31 18:24 ` Rafael J. Wysocki
2011-01-31 18:24 ` Rafael J. Wysocki
2011-01-31 18:29 ` Ozan Çağlayan
2011-01-31 18:33 ` Rafael J. Wysocki
2011-01-31 18:38 ` Ozan Çağlayan
2011-01-31 19:12 ` Rafael J. Wysocki
2011-01-31 19:12 ` Rafael J. Wysocki
2011-01-31 20:35 ` Ozan Çağlayan
2011-01-31 20:42 ` Rafael J. Wysocki
2011-01-31 20:42 ` Ozan Çağlayan
2011-01-31 20:42 ` Ozan Çağlayan
2011-01-31 21:04 ` Ozan Çağlayan
2011-01-31 22:52 ` Rafael J. Wysocki
2011-02-03 21:10 ` Ozan Çağlayan
2011-02-03 22:04 ` Rafael J. Wysocki
2011-02-03 22:13 ` Ozan Çağlayan
2011-02-03 22:51 ` Rafael J. Wysocki
2011-02-04 6:44 ` Ozan Çağlayan
2011-02-04 6:44 ` Ozan Çağlayan
2011-02-04 20:36 ` Rafael J. Wysocki [this message]
2011-02-05 13:21 ` Ozan Çağlayan
2011-02-05 18:16 ` Rafael J. Wysocki
2011-02-05 18:16 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201102042136.20165.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel_debroux@yahoo.fr \
--cc=ozan@pardus.org.tr \
--cc=platform-driver-x86@vger.kernel.org \
--cc=r.schtz@t-online.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.