All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kimmo Taskinen <kimmo.taskinen@me.com>
To: jordan <triplesquarednine@gmail.com>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: WAS: linux-rt fails to boot on > 3.12.5.-rt7 ... NOW IS: linux-rt-3.14 boots by reverting patches + nvidia uses __rt_mutex_init [which in 3.14 has been changed to EXPORT_SYMBOL_GPL]
Date: Thu, 15 May 2014 18:05:58 +0300	[thread overview]
Message-ID: <5374D7D6.4090108@me.com> (raw)
In-Reply-To: <CAOcfFMxLAeqqf-WuwNzE0im800EGN-=OBP06Wz0h8sUr=EKWig@mail.gmail.com>

On 14.05.2014 16:18, jordan wrote:
> Hey Kimmo,
>
>>> you can get the patch here; http://pastebin.com/VG7X5WjK ... it
>>> applies over 3.14.3-rt5 [after you've already applied the -rt patch,
>>> you apply it]. It's yielded working AMD Phenom systems for me
>>> [although, i don't have the exact same H/W as you]. it might be worth
>>> a try, just to see if it works.
>> I can confirm that applying the patch in http://pastebin.com/VG7X5WjK to
>> 3.14.3-rt5 makes my system bootable even with AMD C1E enabled.
>> To clarify my previous email, those other tricks "processor.max_cstate=0",
>> "processor.nocst", etc... did not help.
> Well, it looks like you are another person who's system is unstable
> when those 3 upstream -rt patches are applied. Reverting [as you have
> done now] should result in a usable/stable system for you [its worked
> for myself and others for a few releases now. Maybe you can post back
> on how that goes for you?]. Although, depending on config; ie: if you
> are using no_hz_idle/full you may see "NOHZ: softirq pending 40"
> [which one of the patches we reverted fixes, IIRC]. Myself, I don't
> use NO_HZ_* and use the 'periodic timers' in the kernel, instead.
I use also the "periodic timers". There are quite many more who have the 
system effected by this problem. It's the feedback from Daphile users. 
Daphile is my "distro" using the RT kernel (www.daphile.com).

Actually I'm not able give you feedback on the longterm stability of the 
reverted version because the Phenom PC is my home server and I can use 
it only for quick testing. I'm hoping too that Paul or someone else 
finds a better solutions for this :-).

Kimmo
>
> anyway, I am not sure how to fix this, beyond reverting / using that
> patch. I know that some of the devs have had a hard time reproducing
> the problem - maybe Paul will have better luck on another AMD system
> [here is hoping]. But at least for now, you should be able to use that
> patch.
>
> jordan
>
>> Kimmo
>>>
>>>> OK, so I never got back to finding a system that could reproduce this,
>>>> but it sounds like it is still worthwhile; thanks for the reminder and
>>>> I'll go see if I can reproduce this on a quad since the six core was OK.
>>> Hey Paul, I also forgot to get back to you ;) ... I had been carrying
>>> over my .config - so i tried using defconfig too [just to see] and it
>>> was no different. I was astonished that yours booted up just fine,
>>> because i know of other AMD users [aside from Kimmo] who can't boot on
>>> vainlla-rt... Again, 3.14.x-rtX boot and work just fine for me, by
>>> reverting those patches. I had thought maybe -rt5 would boot [it
>>> looked to have some substantial changes], but alas -rt5 also required
>>> the patch for a working system.
>>>
>>> Jordan
>>>
>>>> P.
>>>> --
>>>>
>>>>> Cheers
>>>>> Kimmo
>>>>>
>>>>>> --
>>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>>> linux-rt-users" in
>>>>>> the body of a message to majordomo@vger.kernel.org
>>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>>>


  reply	other threads:[~2014-05-15 15:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 15:50 WAS: linux-rt fails to boot on > 3.12.5.-rt7 ... NOW IS: linux-rt-3.14 boots by reverting patches + nvidia uses __rt_mutex_init [which in 3.14 has been changed to EXPORT_SYMBOL_GPL] jordan
2014-04-15 16:15 ` jordan
2014-04-19 13:48   ` Paul Gortmaker
2014-04-19 14:42     ` jordan
2014-04-25 14:43       ` Paul Gortmaker
2014-04-25 17:23         ` jordan
2014-04-25 17:39           ` Paul Gortmaker
2014-05-14  0:38             ` Kimmo Taskinen
     [not found]               ` <5372BDC5.3070309@me.com>
2014-05-14  0:51                 ` Kimmo Taskinen
2014-05-14  2:17               ` Paul Gortmaker
2014-05-14  2:47                 ` jordan
2014-05-14  9:03                   ` Kimmo Taskinen
2014-05-14 13:18                     ` jordan
2014-05-15 15:05                       ` Kimmo Taskinen [this message]
2014-05-19 13:14               ` Ralf Mardorf
2014-05-19 13:15                 ` Ralf Mardorf
2014-05-19 15:16                   ` Joakim Hernberg
2014-05-19 19:02                     ` Ralf Mardorf
2014-05-20 18:36                       ` Joakim Hernberg
2014-05-20 20:27                         ` jordan
2014-04-21  8:48     ` WAS: linux-rt fails to boot on > 3.12.5.-rt7 ... NOW IS: linux-rt-3.14 boots by reverting patches Stanislav Meduna
2014-04-23 21:09 ` WAS: linux-rt fails to boot on > 3.12.5.-rt7 ... NOW IS: linux-rt-3.14 boots by reverting patches + nvidia uses __rt_mutex_init [which in 3.14 has been changed to EXPORT_SYMBOL_GPL] Pavel Vasilyev
2014-04-23 21:39   ` Pavel Vasilyev

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=5374D7D6.4090108@me.com \
    --to=kimmo.taskinen@me.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=triplesquarednine@gmail.com \
    /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.