From: Thomas Gleixner <tglx@linutronix.de>
To: Lyude Paul <lyude@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
keith.busch@intel.com, Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: "irq/matrix: Spread interrupts on allocation" breaks nouveau in mainline kernel
Date: Wed, 24 Jan 2018 13:50:52 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801241349060.1997@nanos> (raw)
In-Reply-To: <1516744873.29151.3.camel@redhat.com>
On Tue, 23 Jan 2018, Lyude Paul wrote:
> Hi! Sorry to be the bearer of bad news, but this patch actually seems to break
> suspending and resuming with nouveau on my machine:
> [ 31.003578] WARNING: CPU: 0 PID: 11523 at kernel/smp.c:291
> smp_call_function_single+0xdc/0xe0
This warning has absolutely no relationship to that patch.
> [ 31.003592] RIP: 0010:smp_call_function_single+0xdc/0xe0
> [ 31.003603] ? rdmsr_safe_on_cpu+0x4b/0x70
> [ 31.003604] rdmsr_safe_on_cpu+0x4b/0x70
> [ 31.003606] get_block_address.isra.0+0x6e/0xe0
> [ 31.003607] mce_amd_feature_init+0x63/0x2c0
> [ 31.003609] mce_syscore_resume+0x1e/0x30
> [ 31.003611] syscore_resume+0x4b/0x170
> [ 31.003613] suspend_devices_and_enter+0x608/0x7e0
> [ 31.003614] pm_suspend+0x315/0x380
> [ 31.003615] state_store+0x7d/0xe0
> [ 31.003618] kernfs_fop_write+0xfa/0x180
> [ 31.003620] __vfs_write+0x23/0x130
> [ 31.003623] ? SYSC_newfstat+0x29/0x40
> [ 31.003625] ? _cond_resched+0x15/0x40
> [ 31.003626] vfs_write+0xad/0x1a0
> [ 31.003627] SyS_write+0x42/0x90
> [ 31.003629] entry_SYSCALL_64_fastpath+0x24/0x87
Borislav?
Thanks,
tglx
next prev parent reply other threads:[~2018-01-24 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 22:01 Lyude Paul
2018-01-24 1:26 ` Lyude Paul
2018-01-24 12:52 ` Thomas Gleixner
2018-01-24 17:49 ` Lyude Paul
2018-01-24 19:13 ` Ghannam, Yazen
2018-01-24 19:56 ` Lyude Paul
2018-01-24 20:02 ` Lyude Paul
2018-01-25 3:29 ` Mike Galbraith
2018-01-25 18:29 ` Lyude Paul
2018-01-25 8:54 ` Thomas Gleixner
2018-01-25 18:23 ` Lyude Paul
2018-01-25 18:46 ` Thomas Gleixner
2018-01-25 19:25 ` Lyude Paul
2018-01-25 20:12 ` Thomas Gleixner
2018-01-24 12:50 ` Thomas Gleixner [this message]
2018-01-24 13:38 ` Borislav Petkov
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=alpine.DEB.2.20.1801241349060.1997@nanos \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®