From: Mark Hansen <meh@winfirst.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Kernel Panic when running sensors on new CentOS kernel (3.10.0-229.1.2)
Date: Wed, 08 Apr 2015 19:15:08 +0000 [thread overview]
Message-ID: <55257E3C.1080206@winfirst.com> (raw)
In-Reply-To: <55256D66.1000400@winfirst.com>
On 4/8/2015 11:52 AM, Guenter Roeck wrote:
> On Wed, Apr 08, 2015 at 11:27:05AM -0700, Guenter Roeck wrote:
>> On Wed, Apr 08, 2015 at 11:03:18AM -0700, Mark Hansen wrote:
>
> [ ... ]
>> >
>> I would guess that some patch from a later kernel version was back-ported,
>> but is missing a critical part. Do you know if the source code for that kernel
>> is available somewhere ?
>>
>
> Never mind, I found the source and had a look. It turns out that the
> hardware monitoring code in drivers/gpu/drm/radeon/radeon_pm.c (which
> is what affects you) is broken in 7.1. You might want to open a case
> with the CentOS community (or possibly Fedora / Redhat).
>
> Guenter
>
Guenter,
Thanks for the quick look. I've had a question posted to the CentOS 7.x forum since the weekend
but not much response there. I can see if I can figure out how to open the case with the CentOS
team. Is there any way you can provide me with what I'll need to tell them, so they know what
is broken, or do you think the information I provided in my initial e-mail here will be enough?
Thanks again,
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2015-04-08 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 18:03 [lm-sensors] Kernel Panic when running sensors on new CentOS kernel (3.10.0-229.1.2) Mark Hansen
2015-04-08 18:27 ` Guenter Roeck
2015-04-08 18:52 ` Guenter Roeck
2015-04-08 19:15 ` Mark Hansen [this message]
2015-04-08 19:40 ` Guenter Roeck
2015-04-09 7:43 ` Jean Delvare
2015-04-09 16:27 ` Mark Hansen
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=55257E3C.1080206@winfirst.com \
--to=meh@winfirst.com \
--cc=lm-sensors@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 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.