linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jordan <triplesquarednine@gmail.com>
To: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: 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: Sun, 13 Apr 2014 11:50:49 -0400	[thread overview]
Message-ID: <CAOcfFMxc=Ldp_bvvz228_8C9SxqbCbfgzaAjBrf4n2oigG7_wg@mail.gmail.com> (raw)

Hey list.

1. So after finally having some time off of work [after a busy couple
of months] i have come back to trying to sort out linux-rt on my AMD
PHenom II 965 system - which had failed to boot post 3.12.5-rt7

first, i need to make a correction -rt8 DID boot fine and was stable
[after one/initial lockup, it never locked again, and obviously booted
fine.]. but i figured this out, only after doing a git-bisect on -rt7
to -rt8 ... and never got around to testing -rt8 to -rt9... However, I
decided to give 3.14-rt a run - and again - ended up with the machine
failing to boot... Next, i decided to revert all three of the patches
that you pointed out Sebastion;

| timers-do-not-raise-softirq-unconditionally.patch
| timer-Raise-softirq-if-there-s-irq_work.patch
| timer-rt-Always-raise-the-softirq-if-there-s-irq_wor.patch

well, what i actually ended up doing was reverting the first and
modifying the 1st patch to revert the other two patches (by changing
../kernel/timer.c section of the original patch). [ i reverted after
applying the linux-rt patch, not split queue];
http://pastebin.com/zwsZg9ZM

[ninez@localhost ~]$ uname -a
Linux localhost 3.14.0-rt1-1-l-pa #1 SMP PREEMPT RT Sun Apr 13
10:44:19 EDT 2014 x86_64 GNU/Linux

I've been running 3.14-rt for a couple of hours now and it appears to
be stable, thus far - without those patches/fixes applied [and
obviously doesn't boot at all with them applied...and as you know - i
am not the only AMD user affected by the boot failures...so i am
thinking those patches really need to be looked at again, as they
cause serious regressions for some of us :\

It also presents a problem because i package linux-rt and how i am
supposed to update it, when if i revert these patches, afaict - other
H/W may not boot. [wasn't it some i7 machines that failed or
something?]... So i am not sure what to do [aside from not updating my
packages until the problem is resolved upstream].

2. Nvidia [and possibly/most likely other out-of-tree drivers] make
use or __rt_mutex_init - which apparently has been changed from
EXPORT_SYMBOL to EXPORT_SYMBOL_GPL in 3.14 [or 3.13?] (and obviously
in 3.12 it was EXPORT_SYMBOL). I had to end up switching nvidia's
license to GPL in order to be able to use the driver/modules. I'm not
sure what is supposed to happen here, but nvidia should be usable
without having to change it's license [since i never had to before,
aside from similar situations where symbols where changed to gpl, only
to be reverted back, as has happened before].

anyway, I am less concerned about the nvidia issue [im just pointing
it out] and am obviously more concerned about being able to sort out
the boot failure issues, as afaict - they are caused by changes in
-rt9, not upstream.

cheerz

Jordan

             reply	other threads:[~2014-04-13 15:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 15:50 jordan [this message]
2014-04-15 16:15 ` 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-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
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='CAOcfFMxc=Ldp_bvvz228_8C9SxqbCbfgzaAjBrf4n2oigG7_wg@mail.gmail.com' \
    --to=triplesquarednine@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).