From: Ludwig Petrosyan <ludwig.petrosyan@desy.de>
To: linux-kernel@vger.kernel.org
Cc: "Thomas Bruns" <Thomas.Bruns@desy.de>,
"Gerhard Schleßelmann" <gerhard.schlesselmann@desy.de>
Subject: kernel 3.13-61/62 /cpu1/cpufreq/stats
Date: Mon, 24 Aug 2015 14:44:33 +0200 [thread overview]
Message-ID: <55DB11B1.7020407@desy.de> (raw)
Hello
we have problem boot kernel 3.13-61/62 on the MTCA crate, some time it
boots some time no.
In the kernel log we found this problem:
[ 16.168871] ------------[ cut here ]------------
[ 16.173513] WARNING: CPU: 0 PID: 4 at
/build/linux-lts-trusty-G19QHO/linux-lts-trusty-3.13.0/fs/sysfs/dir.c:486 sysfs_warn_dup+0x91/0xb0()
[ 16.185967] sysfs: cannot create duplicate filename
'/devices/system/cpu/cpu1/cpufreq/stats'
we found out thid peoblen is solved in the kernel 3.14 (file
linux/drivers/cpufreq/cpufreq.c), is there some way to solve it for
kernel 3.13-61/62
(some boot parameters ...) ?
The older kernel 3.13-55 runs fine on the same CPU.
with best regards
Ludwig Petrosyan
DESY
reply other threads:[~2015-08-24 12:53 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=55DB11B1.7020407@desy.de \
--to=ludwig.petrosyan@desy.de \
--cc=Thomas.Bruns@desy.de \
--cc=gerhard.schlesselmann@desy.de \
--cc=linux-kernel@vger.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