Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

amdtemp module does not find any sensors on 5.99.55

0 views
Skip to first unread message

Paul Goyette

unread,
Jul 30, 2011, 4:00:23 PM7/30/11
to
I've just updated my main server from 5.99.52 to 5.99.55 and it seems
that the amdtemp module no longer registers the CPU temp sensors. This
was working on 5.99.52.

If it matters, this is on a dual-Opteron-6172 (2 sockets, each with 12
cores).

-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer | | pgoyette at netbsd.org |
-------------------------------------------------------------------------

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de

Martin Husemann

unread,
Jul 30, 2011, 4:09:27 PM7/30/11
to
On Sat, Jul 30, 2011 at 01:00:23PM -0700, Paul Goyette wrote:
> I've just updated my main server from 5.99.52 to 5.99.55 and it seems
> that the amdtemp module no longer registers the CPU temp sensors. This
> was working on 5.99.52.

Anything in dmesg?

Martin

Paul Goyette

unread,
Jul 30, 2011, 4:12:34 PM7/30/11
to
Nothing in dmesg, nothing in /var/log/messages, and nothing on the
console.

And it is also not working on my Phenom-II (6-core) processors.

Seems it is probably related to recent change to modularize it. In
5.99.52, it was compiled into the kernel and working fine. But with
5.99.55 it has been modularized and not working.

On Sat, 30 Jul 2011, Martin Husemann wrote:

> On Sat, Jul 30, 2011 at 01:00:23PM -0700, Paul Goyette wrote:

>> I've just updated my main server from 5.99.52 to 5.99.55 and it seems
>> that the amdtemp module no longer registers the CPU temp sensors. This
>> was working on 5.99.52.
>

> Anything in dmesg?
>
> Martin
>
> !DSPAM:4e3464ff2352695413051!

Martin Husemann

unread,
Jul 30, 2011, 4:13:50 PM7/30/11
to
On Sat, Jul 30, 2011 at 01:12:34PM -0700, Paul Goyette wrote:
> Nothing in dmesg, nothing in /var/log/messages, and nothing on the
> console.

So it does not even attach?

Martin

Paul Goyette

unread,
Jul 31, 2011, 12:54:59 AM7/31/11
to
As an added datapoint, amdtemp still attaches and is functional if the
driver is built into the kernel, as is the case in the amd64/GENERIC
kernel. It seems to fail only when loaded after autoconfig is done.

I will try to look into it in the next few days...


On Sat, 30 Jul 2011, Paul Goyette wrote:

> On Sat, 30 Jul 2011, Martin Husemann wrote:
>

>> On Sat, Jul 30, 2011 at 01:12:34PM -0700, Paul Goyette wrote:
>>> Nothing in dmesg, nothing in /var/log/messages, and nothing on the
>>> console.
>>
>> So it does not even attach?
>

> Correct


>
>
> -------------------------------------------------------------------------
> | Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
> | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
> | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
> | Kernel Developer | | pgoyette at netbsd.org |
> -------------------------------------------------------------------------
>

-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer | | pgoyette at netbsd.org |
-------------------------------------------------------------------------

--

0 new messages