On 25.04.2014 20:39, Paul Gortmaker wrote:
On 14-04-25 01:23 PM, jordan wrote:
On Fri, Apr 25, 2014 at 10:43 AM, Paul Gortmaker
<paul.gortmaker@xxxxxxxxxxxxx> wrote:
On 14-04-19 10:42 AM, jordan wrote:
Hey Paul,
I've got some AMD kit that has just been freed up from winter
heating duty - sometime later this week I should be able to try to
reproduce what you have seen, and knowing it works w/o the above
softirq patch monkeying around should be a good lead on this.
That would be awesome! IIRC, Sebastian said that he didn't have said
h/w CPU kicking around to test with, at some point in my original
thread on this subject... and i just don't have the skill set required
So I stuck the -rt patches onto 3.14.1 last night; made a defconfig
and then enabled RT_FULL in the resulting .config and that booted
right up on a 1090T six core phenom, which kind of surprised me.
that surprises me too - maybe 3.14.1 fixed something? ...anyway, I am
only home for a short while [lunch] but i will try building 3.14.1-rt
when i get home and see what happens / report back.
I had to drop one ipv6 patch that was now in stable, but otherwise
it was straight forward to make a 3.14.1-rt
P.
--
I should be able to dig up an athlon quad and see what it does...
worth a look, i suppose.
thanks Paul for the update
Jordan Johnston
I had not been able to boot my Phenom II X4 910e PC with any of the
latest RT kernels (3.12 after 3.12.5-rt7 or 3.14 or not even the latest
3.10 versions) until I today disabled AMD C1E from BIOS. An other way to
get it to boot was "acpi=off" as a parameter to kernel but I need
"button". I tried many others "processor.max_cstate=0",
"processor.nocst", etc...
Without RT patch the "AMD C1E" is not a problem.
Cheers
Kimmo
--
To unsubscribe from this list: send the line "unsubscribe
linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
