PROBLEM: 2.6.30 fails to detect hardware limitation requiring "noapic"

[Ron House]

Hello, I hope this is the right place to report a kernel bug.

I have an Acer desktop, bog standard system.

My previous kernel 2.6.26 tells me that I need to set option "noapic", 
and then halts. This behaviour is correct.

Although it would be nice if the kernel dealt with noapic automatically, 
the attempt to make this happen in 2.6.30 doesn't work.

Booting with 2.6.30 gives me a bootup with many errors - USB ports not 
responding, failure to set the clock, and others. Then when it has 
finished booting, both the mouse and keyboard are dead. (But the system 
is running and can be accessed via ssh.)

When I reboot 2.6.30 with "noapic", it boots correctly.

My comment on this is that 2.6.26 is actually more useful than 2.6.30, 
because 2.6.30 doesn't give any clue as to what is wrong or how to fix 
it. If I hadn't previously had the experience with 2.6.26, I would have 
been hopelessly lost.

Hope this is useful, and thank you so much for the wonderful software!

--
Ron House.
Building Peace: http://peacelegacy.org
Australian Birds: http://wingedhearts.org
Principle of Goodness academic site: http://principleofgoodness.net
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/