Re: [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig

Dave Jones <[email protected]>
Newsgroups org.kernel.vger.cpufreq
Message-ID <[email protected]>
On Mon, Jun 09, 2014 at 12:20:42AM +0100, Ben Hutchings wrote:
 > longhaul quickly caused hard lockups and possibly killed the memory
 > module on my EPIA-PD board.  It is commented as:
 > 
 > 'BIG FAT DISCLAIMER: Work in progress code. Possibly *dangerous*'

that last part may have been overly dramatic. When I was originally
writing this driver I was using pre-production cpu's which were
marginal to begin with. Production hw should have been more tolerant.
What didn't help was a lot of the EPIAs were made with *Really*
shitty capacitors that would pop open and ooze over the boards. Might want
to eyeball those, you can usually tell when they've gone bad.

 > Let's put another warning where people are more likely to see it.

That said, I'm not against itbeing marked BROKEN (I thought it
already was), and certainly don't recommend distros enabling it.

I'd also not stand in the way of someone throwing it out completely
given the small amount of systems out there likely still running this.

	Dave
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.