Re: 2.6.16-rt22/23 kernels hanging after registering IO schedulers

From: Mark Knecht
Date: Mon May 22 2006 - 20:29:49 EST

On 5/22/06, Steven Rostedt <rostedt@xxxxxxxxxxx> 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 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

-- 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at