Bug 165381 - [cpufreq] powerd(8) eats CPUs for breakfast
Summary: [cpufreq] powerd(8) eats CPUs for breakfast
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-21 23:10 UTC by Jamie Gritton
Modified: 2018-01-03 05:16 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jamie Gritton freebsd_committer freebsd_triage 2012-02-21 23:10:10 UTC
I have a desktop amd64 system with an Athlon 7750 CPU (don't know the
chipset offhand) that I decided to try powerd on, as I'm fond of quiet
fans.  I set powerd_enable="YES" in rc.conf and ran "sh /etc/rc.d/powerd
start".  After one or two minutes, my display froze.  After resetting
the box, I got nothing.  After a hard power-cycle, nothing.  After waiting
ten minutes for everything to get nice and cool and another power cycle,
nothing.  Not even the first BIOS screen.  It was pretty clear something
was fried, most likely the CPU.

That's OK, I had another currently unused system (don't we all?) and I
swapped CPUs...

How-To-Repeat: Swap CPUs and turn the computer on again, without remembering to remove
the powerd_enable="YES" like from rc.conf.  Sure enough, two minutes later
I fried my second CPU.  After a quick eBay purchase of a third 7750,
this time I remembered to fix my rc.conf and everything works again.

I apologize for not having more information, but with no CPU it's hard
to get a good crash dump.
Comment 1 Chris Rees freebsd_committer freebsd_triage 2013-03-12 21:16:07 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-acpi

This appears to be a rather serious issue-- anyone know about powerd on 
amd?
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:29 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped