From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: nando@ccrma.Stanford.EDU, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 4.0.4-rt1
Date: Sun, 24 May 2015 13:59:46 -0700 [thread overview]
Message-ID: <55623BC2.80307@localhost> (raw)
In-Reply-To: <20150519213923.GA26363@linutronix.de>
On 05/19/2015 02:39 PM, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
>
> I'm pleased to announce the v4.0.4-rt1 patch set.
Great!!
> Changes since v3.18.13-rt10
>
> - Rebase to v4.0.
>
> - David Hildenbrand's series of decouple of preempt_disable from
> pagefault_disable is part of the series.
>
> While doing the v4.0 I stumbled upon a few things. Therefore I plan to
> reorder the -RT queue and merge patches where possible. Also I intend to
> drop PREEMPT_RTB and PREEMPT_RT_BASE unless there is need for it…
...
I had to do this to get it to build (looks like it is not rt specific,
probably just a typo in mainline):
--------
--- linux-4.0/sound/soc/intel/sst/sst.c~ 2015-04-12 15:12:50.000000000 -0700
+++ linux-4.0/sound/soc/intel/sst/sst.c 2015-05-23 21:51:46.000000000 -0700
@@ -368,8 +368,8 @@
* initialize by FW or driver when firmware is loaded
*/
spin_lock_irqsave(&ctx->ipc_spin_lock, irq_flags);
- sst_shim_write64(shim, SST_IMRX, shim_regs->imrx),
- sst_shim_write64(shim, SST_CSR, shim_regs->csr),
+ sst_shim_write64(shim, SST_IMRX, shim_regs->imrx);
+ sst_shim_write64(shim, SST_CSR, shim_regs->csr);
spin_unlock_irqrestore(&ctx->ipc_spin_lock, irq_flags);
}
--------
On a desktop with an i7-3770k it seems to run fine (but I have not have
time to test for latency problems).
On my laptop, a lenovo w540, I get this continuously - so it is not
really usable at this point:
--------
May 24 13:51:41 localhost kernel: ------------[ cut here ]------------
May 24 13:51:41 localhost kernel: WARNING: CPU: 5 PID: 361 at
drivers/gpu/drm/i915/intel_display.c:9748
intel_check_page_flip+0xaa/0xf0 [i915]()
May 24 13:51:41 localhost kernel: WARN_ON(!in_interrupt())
May 24 13:51:41 localhost kernel: Modules linked in:
May 24 13:51:41 localhost kernel: rfcomm fuse ccm xt_CHECKSUM
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netbios_ns
nf_conntrack_broadcast ip6t_rpfilter ip6t_REJ\
ECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_broute bridge stp
llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6
nf_defrag_ipv6 nf_nat_ipv6 ip6table_mang\
le ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
iptable_mangle iptable_security\
iptable_raw bnep bbswitch(OE) vfat fat iTCO_wdt iTCO_vendor_support
arc4 intel_rapl iosf_mbi coretemp kvm_intel kvm uvcvideo
crct10dif_pclmul videobuf2_vmalloc videobuf\
2_core crc32_pclmul crc32c_intel videobuf2_memops ghash_clmulni_intel
v4l2_common videodev media iwlmvm btusb serio_raw mac80211 bluetooth
snd_hda_codec_realtek
May 24 13:51:41 localhost kernel: snd_hda_codec_hdmi
snd_hda_codec_generic iwlwifi snd_hda_intel sdhci_pci snd_hda_controller
cfg80211 sdhci snd_hda_codec mmc_core snd_h\
wdep lpc_ich snd_seq mei_me i2c_i801 mfd_core snd_seq_device mei snd_pcm
thinkpad_acpi snd_timer ie31200_edac snd shpchp edac_core soundcore
tpm_tis rfkill tpm nfsd auth\
_rpcgss nfs_acl lockd grace sunrpc i915 i2c_algo_bit e1000e
drm_kms_helper ptp drm pps_core wmi video
May 24 13:51:41 localhost kernel: CPU: 5 PID: 361 Comm: irq/30-i915
Tainted: G W OE 4.0.4-201.rt1.2.fc21.ccrma.x86_64+rt #1
May 24 13:51:41 localhost kernel: Hardware name: LENOVO
20BGCTO1WW/20BGCTO1WW, BIOS GNET65WW (2.13 ) 06/20/2014
May 24 13:51:41 localhost kernel: 0000000000000000 000000001f35af7b
ffff8804651afc78 ffffffff8179c0b9
May 24 13:51:41 localhost kernel: 0000000000000000 ffff8804651afcd0
ffff8804651afcb8 ffffffff8109ee1a
May 24 13:51:41 localhost kernel: ffff8804651afcb8 ffff88046638c000
ffff880469dd7800 0000000000000001
May 24 13:51:41 localhost kernel: Call Trace:
May 24 13:51:41 localhost kernel: [<ffffffff8179c0b9>] dump_stack+0x4c/0x81
May 24 13:51:41 localhost kernel: [<ffffffff8109ee1a>]
warn_slowpath_common+0x8a/0xe0
May 24 13:51:41 localhost kernel: [<ffffffff8109eec5>]
warn_slowpath_fmt+0x55/0x70
May 24 13:51:41 localhost kernel: [<ffffffffa0186dda>]
intel_check_page_flip+0xaa/0xf0 [i915]
May 24 13:51:41 localhost kernel: [<ffffffffa0152018>]
ironlake_irq_handler+0x2e8/0x1000 [i915]
May 24 13:51:41 localhost kernel: [<ffffffff81014610>] ?
__switch_to+0x150/0x610
May 24 13:51:41 localhost kernel: [<ffffffff810fb040>] ?
irq_thread_fn+0x50/0x50
May 24 13:51:41 localhost kernel: [<ffffffff810fb067>]
irq_forced_thread_fn+0x27/0x80
May 24 13:51:41 localhost kernel: [<ffffffff810fb61f>]
irq_thread+0x12f/0x180
May 24 13:51:41 localhost kernel: [<ffffffff810fb0f0>] ?
wake_threads_waitq+0x30/0x30
May 24 13:51:41 localhost kernel: [<ffffffff810fb4f0>] ?
irq_thread_check_affinity+0x90/0x90
May 24 13:51:41 localhost kernel: [<ffffffff810bf4ba>] kthread+0xca/0xe0
May 24 13:51:41 localhost kernel: [<ffffffff810bf3f0>] ?
kthread_worker_fn+0x180/0x180
May 24 13:51:41 localhost kernel: [<ffffffff817a2098>]
ret_from_fork+0x58/0x90
May 24 13:51:41 localhost kernel: [<ffffffff810bf3f0>] ?
kthread_worker_fn+0x180/0x180
May 24 13:51:41 localhost kernel: ---[ end trace 00000000000005fe ]---
May 24 13:51:41 localhost kernel: ------------[ cut here ]------------
--------
Any patches I could try to fix this?
-- Fernando
next prev parent reply other threads:[~2015-05-24 20:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 21:39 [ANNOUNCE] 4.0.4-rt1 Sebastian Andrzej Siewior
2015-05-19 22:33 ` Carsten Emde
2015-05-19 22:51 ` Pavel Vasilyev
2015-05-20 7:12 ` Sebastian Andrzej Siewior
2015-05-20 13:18 ` Daniel Wagner
2015-05-19 22:48 ` Pavel Vasilyev
2015-05-20 3:14 ` Mike Galbraith
2015-05-20 10:06 ` Pavel Vasilyev
2015-06-11 12:09 ` Sebastian Andrzej Siewior
2015-05-23 11:57 ` Pavel Vasilyev
2015-06-11 12:08 ` Sebastian Andrzej Siewior
2015-05-24 20:59 ` Fernando Lopez-Lezcano [this message]
2015-06-11 12:22 ` [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement Sebastian Andrzej Siewior
2015-06-11 13:04 ` Mats Karrman
2015-06-11 13:14 ` [PATCH v2] " Sebastian Andrzej Siewior
2015-06-12 7:22 ` Vinod Koul
2015-06-12 10:37 ` Mark Brown
2015-05-26 13:34 ` [ANNOUNCE] 4.0.4-rt1 Clark Williams
2015-05-26 13:38 ` Steven Rostedt
2015-05-26 13:48 ` Clark Williams
2015-05-26 14:49 ` Mike Galbraith
2015-05-26 15:19 ` Steven Rostedt
2015-05-26 15:43 ` Clark Williams
2015-05-26 19:41 ` Fernando Lopez-Lezcano
2015-05-29 1:56 ` Fernando Lopez-Lezcano
2015-06-09 16:45 ` Fernando Lopez-Lezcano
2015-06-09 22:05 ` Pavel Vasilyev
2015-06-10 2:41 ` Mike Galbraith
2015-06-10 3:10 ` Fernando Lopez-Lezcano
2015-06-09 22:10 ` Pavel Vasilyev
2015-06-11 12:38 ` Sebastian Andrzej Siewior
2015-05-28 8:41 ` Joakim Hernberg
2015-06-11 12:34 ` Sebastian Andrzej Siewior
2015-05-27 9:44 ` Joakim Hernberg
2015-05-27 10:19 ` Jeremy Jongepier
2015-05-28 8:33 ` Joakim Hernberg
2015-05-27 15:50 ` Ralf Mardorf
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=55623BC2.80307@localhost \
--to=nando@ccrma.stanford.edu \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).