From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Joakim Hernberg <jhernberg@alchemy.lu>,
Ralf Mardorf <ralf.mardorf@rocketmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 3.18.9-rt4 kernel panic - Was: 3.18.9-rt4
Date: Mon, 16 Mar 2015 15:01:50 +0100 [thread overview]
Message-ID: <20150316140150.GB28130@linutronix.de> (raw)
In-Reply-To: <20150315145153.44f5217c@tor.valhalla.alchemy.lu>
* Joakim Hernberg | 2015-03-15 14:51:53 [+0100]:
>I remember that you had boot problems a while ago, together
>with a couple of other AMD cpu users. IIRC it just affected a few
>specific AMD cpus. AFAIK, you could not succesfully boot any kernel
>starting with with 3.12.6-rt9, and I have another report from another
>afflicted user saying that the boot problem was fixed by reverting:
>
>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
>
>This might be significant, as these patches are in play again, at
>least on 3.18-rt.
As of v3.18-RT these patches are revereted. In two pix I see cpufreq
with k8. My AMD here uses acpi-cpufreq so I never run into this. So
maybe I find something once I look…. I the meantime you could you please
drop cpufreq from your .config and try again?
Sebastian
--
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:[~2015-03-16 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 21:30 3.18.9-rt4 Ralf Mardorf
2015-03-14 9:43 ` 3.18.9-rt4 kernel panic - Was: 3.18.9-rt4 Ralf Mardorf
2015-03-15 13:51 ` Joakim Hernberg
2015-03-16 14:01 ` Sebastian Andrzej Siewior [this message]
2015-03-16 16:23 ` Sebastian Andrzej Siewior
2015-03-17 5:13 ` Ralf Mardorf
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=20150316140150.GB28130@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jhernberg@alchemy.lu \
--cc=linux-rt-users@vger.kernel.org \
--cc=ralf.mardorf@rocketmail.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).