From: Matthias Hopf <mhopf@suse.de>
To: Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Matthieu CASTET <castet.matthieu@free.fr>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Milton Miller <miltonm@bga.com>,
linux-kernel@vger.kernel.org, Oliver Neukum <oneukum@suse.de>
Subject: [REGRESSION] S3 suspend on SandyBridge freezes due to on_each_cpu() change (bd924e8)
Date: Wed, 26 Jan 2011 17:02:31 +0100 [thread overview]
Message-ID: <20110126160231.GA29021@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
While bisecting a dri S3 issue I stumbled in 2.6.38-rc1 over a
regression because of NX protection (5bd5a4, currently being discussed),
and with a patch fixing this issue I stumbled again in 2.6.38-rc2
because of commit bd924e8:
smp: Allow on_each_cpu() to be called while early_boot_irqs_disabled status to init/main.c
Reverting this commit makes suspend work on SandyBridge again. I haven't
tested reverting this commit on v2.6.38-rc2 yet, though.
I'm compiling for i586, not x86_64.
lspci -vvv output is attached.
(for internal reference: machine NUE874)
Matthias
--
Matthias Hopf <mhopf@suse.de> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de
Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
[-- Attachment #2: lspci.txt.gz --]
[-- Type: application/x-gzip, Size: 3328 bytes --]
next reply other threads:[~2011-01-26 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 16:02 Matthias Hopf [this message]
2011-01-28 16:49 ` [REGRESSION] S3 suspend on SandyBridge freezes due to on_each_cpu() change (bd924e8) Matthias Hopf
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=20110126160231.GA29021@suse.de \
--to=mhopf@suse.de \
--cc=akpm@linux-foundation.org \
--cc=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@bga.com \
--cc=mingo@elte.hu \
--cc=oneukum@suse.de \
--cc=peterz@infradead.org \
--cc=tj@kernel.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.