From: Pavel Vasilyev <pavel@pavlinux.ru>
To: jordan <triplesquarednine@gmail.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
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, 24 Apr 2014 01:09:35 +0400 [thread overview]
Message-ID: <53582C0F.8040901@pavlinux.ru> (raw)
In-Reply-To: <CAOcfFMxc=Ldp_bvvz228_8C9SxqbCbfgzaAjBrf4n2oigG7_wg@mail.gmail.com>
13.04.2014 19:50, jordan пишет:
> 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
Please show patch between 3.14-rt1 and 3.14-rt1-you-version
--
Pavel.
--
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
next prev parent reply other threads:[~2014-04-23 21:09 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
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 ` Pavel Vasilyev [this message]
2014-04-23 21:39 ` 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
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=53582C0F.8040901@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=linux-rt-users@vger.kernel.org \
--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 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).