From: "flinco@libero.it" <flinco@libero.it>
To: <mad_soft@inbox.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Arkadiusz Miskiewicz <arekm@maven.pl>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Feng Tang <feng.tang@intel.com>, Len Brown <len.brown@intel.com>
Subject: R: Re: R: [Bug #14886] Asus P2B-DS not detected as SMP moterboard
Date: Tue, 26 Jan 2010 19:42:42 +0100 (CET) [thread overview]
Message-ID: <30248841.411931264531362541.JavaMail.defaultUser@defaultHost> (raw)
Hi Dmitry,
I will try current git as soon as possible and I will post the results.
Many thanks and Best Regards,
Lorenzo Buzzi
>----Messaggio originale----
>Da: mad_soft@inbox.ru
>Data: 26/01/2010 16.53
>A: "Linux Kernel Mailing List"<linux-kernel@vger.kernel.org>
>Cc: "flinco@libero.it"<flinco@libero.it>, "Rafael J. Wysocki"<rjw@sisk.pl>,
"Kernel Testers List"<kernel-testers@vger.kernel.org>, "Arkadiusz Miskiewicz"
<arekm@maven.pl>, "H. Peter Anvin"<hpa@zytor.com>, "Andrew Morton"<akpm@linux-
foundation.org>, "Feng Tang"<feng.tang@intel.com>, "Len Brown"<len.brown@intel.
com>
>Ogg: Re: R: [Bug #14886] Asus P2B-DS not detected as SMP moterboard
>
>On 20:40 Mon 11 Jan , Rafael J. Wysocki wrote:
>> On Monday 11 January 2010, flinco@libero.it wrote:
>> > Tried 2.6.32.3. The issue is still present.
>>
>> Thanks for the update.
>>
>> Rafael
>
>(I have some troubles with registering on kernel bugzilla, so posting here,
>adding people from bug to CC: list)
>
>Hi!
>I'm also using P2B-DS and can confirm that starting with kernel 2.6.32
>SMP stopped working (and don't work still - tested with current git
>v2.6.33-rc5-238-g158c168) The issue seems to have something to do with the
>fact that ACPI is blacklisted on P2B-DS. I used to workaround this bug
>on newer kernels (>=2.6.32) by passing "acpi=force" in kernel arguments.
>Finally, yesterday I found some time to write simple automated bisection
>script and leaved it to run on machine overnight. Here's result:
>---------------------------------------------------------------------------
>e5b8fc6ac158f65598f58dba2c0d52ba3b412f52 is the first bad commit
>commit e5b8fc6ac158f65598f58dba2c0d52ba3b412f52
>Author: Len Brown <len.brown@intel.com>
>Date: Tue Jul 7 23:22:58 2009 -0400
>
> ACPI: check acpi_disabled in acpi_table_parse() and
acpi_table_parse_entries()
>
> Allow consumers of the acpi_table_parse()/acpi_table_parse_entries() API
> to gracefully handle the acpi_disabled=1 case via return value
> rather than checking the global flag themselves.
>
> Signed-off-by: Feng Tang <feng.tang@intel.com>
> Signed-off-by: Len Brown <len.brown@intel.com>
>---------------------------------------------------------------------------
>
>I re-checked this result and yes - reverting this commit on both 2.6.32 and
>current git (v2.6.33-rc5-238-g158c168) makes problem go away.
>
>--
>Best regards,
>Dmitry "MAD" Artamonow
>
>
reply other threads:[~2010-01-26 18:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=30248841.411931264531362541.JavaMail.defaultUser@defaultHost \
--to=flinco@libero.it \
--cc=akpm@linux-foundation.org \
--cc=arekm@maven.pl \
--cc=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=kernel-testers@vger.kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mad_soft@inbox.ru \
--cc=rjw@sisk.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox