From: Thomas Gleixner <tglx@linutronix.de>
To: Uwaysi Bin Kareem <uwaysi.bin.kareem@paradoxuncreated.com>
Cc: Sven-Thorsten Dietrich <sven@thebigcorporation.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.6.2-rt4
Date: Wed, 24 Oct 2012 11:59:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1210241156380.2756@ionos> (raw)
In-Reply-To: <op.wmobxtv66426ze@localhost.localdomain>
On Wed, 24 Oct 2012, Uwaysi Bin Kareem wrote:
> On Wed, 24 Oct 2012 07:01:54 +0200, Sven-Thorsten Dietrich
> <sven@thebigcorporation.com> wrote:
>
> >
> > On Oct 23, 2012, at 3:53 PM, Uwaysi Bin Kareem
> > <uwaysi.bin.kareem@paradoxuncreated.com> wrote:
> >
> > > I think it complains about not finding rootdevice. Anyway, I am getting a
> > > new machine, so it might not be much of an issue. If you still want to try
> > > and find the bug let me know. Also how do I compile without threadirqs, if
> > > I enable basic-rt, threadirqs are enabled in .config also.
> >
> > rootdevice issues are most likely drivers/initrd related. Does your .config
> > match a working Kernel's .config?
>
> Yes, it works fine without basic-rt, or full-rt. Do you know if basic-rt can
> be compiled without threadirqs?
No. And that's not interesting at all. We really want to know what's
going wrong when you have irq threading enabled.
You can also try the following. Compile the kernel without RT and add
"threadirqs" on the kernel command line. So that's just mainline + irq
threading. Does that work?
In any case it would be helpful if you provide the full dmesg output
of a failing boot.
Thanks,
tglx
next prev parent reply other threads:[~2012-10-24 9:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 19:40 [ANNOUNCE] 3.6.2-rt4 Thomas Gleixner
[not found] ` <op.wmk8f6m96426ze@localhost.localdomain>
[not found] ` <alpine.LFD.2.02.1210222029480.2756@ionos>
2012-10-22 21:05 ` Uwaysi Bin Kareem
2012-10-23 6:52 ` Thomas Gleixner
2012-10-23 22:53 ` Uwaysi Bin Kareem
2012-10-24 5:01 ` Sven-Thorsten Dietrich
2012-10-24 8:16 ` Uwaysi Bin Kareem
2012-10-24 9:59 ` Thomas Gleixner [this message]
2012-10-24 10:48 ` Uwaysi Bin Kareem
2012-10-24 14:27 ` Thomas Gleixner
2012-10-24 17:06 ` Uwaysi Bin Kareem
2012-10-24 18:38 ` Thomas Gleixner
2012-10-24 18:47 ` Uwaysi Bin Kareem
2012-10-24 19:24 ` Thomas Gleixner
2012-10-24 19:32 ` Uwaysi Bin Kareem
2012-10-24 19:49 ` Thomas Gleixner
2012-10-24 19:57 ` Uwaysi Bin Kareem
2012-10-25 21:21 ` Thomas Gleixner
2012-10-26 14:24 ` Paul Gortmaker
2012-10-22 21:54 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2012-10-26 21:45 Uwaysi Bin Kareem
2012-10-26 21:54 ` Paul Gortmaker
2012-10-26 22:24 ` Uwaysi Bin Kareem
2012-10-27 0:17 ` Sven-Thorsten Dietrich
2012-10-27 9:41 ` Uwaysi Bin Kareem
2012-10-27 9:50 ` Uwaysi Bin Kareem
2012-10-29 20:39 Ove Karlsen
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=alpine.LFD.2.02.1210241156380.2756@ionos \
--to=tglx@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=sven@thebigcorporation.com \
--cc=uwaysi.bin.kareem@paradoxuncreated.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).