From: "H. Peter Anvin" <hpa@zytor.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Mark Stanovich <mrktimber@gmail.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.35.3
Date: Mon, 23 Aug 2010 11:45:13 -0700 [thread overview]
Message-ID: <4C72C1B9.1010503@zytor.com> (raw)
In-Reply-To: <4C72B82C.7060707@msgid.tls.msk.ru>
On 08/23/2010 11:04 AM, Michael Tokarev wrote:
> 21.08.2010 07:44, H. Peter Anvin wrote:
>> On 08/20/2010 08:40 PM, Mark Stanovich wrote:
>>> After updating to the 2.6.35.3 stable release, my machine was rebooting
>>> automatically during the first few seconds of boot.
>>>
>>> I bisected to the first bad commit of
>>>
>>> commit 568132624386f53e87575195d868db
>>> 9afb2e9316
>>> Author: H. Peter Anvin <hpa@zytor.com <mailto:hpa@zytor.com>>
>>> Date: Tue Jul 27 17:01:49 2010 -0700
>>>
>>> x86: Add memory modify constraints to xchg() and cmpxchg()
>
> This commit also present in 2.6.32.stable (since 2.6.32.19).
> Should it be fixed there as well?
>
Yes, in particular 69309a05907546fb686b251d4ab041c26afe1e1d should be
applied to all instances of this commit.
As far as we can tell it's a gcc bug, but it hasn't been thoroughly
root-caused to that yet.
-hpa
next prev parent reply other threads:[~2010-08-23 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=wyG13QOU3EQwaO3qBxY=aR=ftiP4s7YpemrPp@mail.gmail.com>
2010-08-21 3:44 ` Linux 2.6.35.3 H. Peter Anvin
2010-08-21 4:06 ` Mark Stanovich
2010-08-21 4:41 ` H. Peter Anvin
2010-08-21 4:50 ` Greg KH
2010-08-23 1:31 ` H. Peter Anvin
2010-08-23 1:56 ` Mark Stanovich
2010-08-23 3:03 ` Greg KH
2010-08-23 13:47 ` Mark Stanovich
2010-08-23 21:35 ` Greg KH
2010-08-23 18:04 ` Michael Tokarev
2010-08-23 18:45 ` H. Peter Anvin [this message]
2010-08-21 3:44 Mark Stanovich
-- strict thread matches above, loose matches on Subject: below --
2010-08-20 20:49 Greg KH
2010-08-20 20:49 ` Greg KH
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=4C72C1B9.1010503@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mrktimber@gmail.com \
--cc=torvalds@linux-foundation.org \
/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.