From: "Mark Knecht" <markknecht@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Clark Williams" <williams@redhat.com>,
"Robert Crocombe" <rwcrocombe@raytheon.com>
Subject: Re: 2.6.16-rt22/23 kernels hanging after registering IO schedulers
Date: Mon, 22 May 2006 17:30:06 -0700 [thread overview]
Message-ID: <5bdc1c8b0605221730t2bf43ab8j1ec3ebd98a4e459e@mail.gmail.com> (raw)
In-Reply-To: <1148333237.4997.7.camel@localhost.localdomain>
On 5/22/06, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sun, 2006-05-21 at 14:10 -0700, Mark Knecht wrote:
>
> > Hi Steve,
> > It's good to hear from you and great if you can take a look at
> > this. I did some more ground work and now feel bad that I didn't
> > report back much earlier. It appears that the problems have started
> > with the very first revision of 2.6.16-rt support. I am currently
> > writing you from 2.6.16 from kernel.org which booted fine. However
> > 2.6.16-rt1 fails the same way as all the later kernels that I tried
> > with a hang right after registering the schedulers.
>
> You're getting farther than I am. My system crashes in init_8259A right
> in the unlocking of the i8259A_lock. It takes an exception in the
> local_irq_restore of the raw_spin_unlock_irqrestore. I tried unlocking
> the lock and locking it again at the beginning of the function, and that
> seems to work fine. But this function didn't change between the
> previous versions that do work. So I think something is very wacky
> going on someplace else.
>
> Unfortunately, I'm very behind in the work that I get paid for, so I
> really don't have any more time to look into this. Especially since my
> main developing machine happens to be my x86_64.
>
> Hopefully, Ingo can find something, or I catch up and can work on this
> again.
>
> -- Steve
>
<SNIP>
Steve,
Hi. Hey, I'm happy to even get a response! Don't worry at all about
not being able to work on it right now. I completely understand. I'm
sure Ingo will pop up one of these days soon and we'll get all this
ironed out.
In the meantime I'm looking into redoing the config file from
scratch tonight to see if something has cropped up using make
oldconfig. I've not had problems with that myself but I have read
reports on the web that others have.
I'll let you all know if I find any new results.
Cheers,
Mark
prev parent reply other threads:[~2006-05-23 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 17:22 2.6.16-rt22/23 kernels hanging after registering IO schedulers Mark Knecht
2006-05-21 17:24 ` Steven Rostedt
2006-05-21 21:10 ` Mark Knecht
2006-05-22 21:27 ` Steven Rostedt
2006-05-23 0:30 ` Mark Knecht [this message]
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=5bdc1c8b0605221730t2bf43ab8j1ec3ebd98a4e459e@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=rwcrocombe@raytheon.com \
--cc=williams@redhat.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