Most recent kernel where this bug did not occur: none. I tried ubuntu edgy live cd (2.6.17-x), same problems Distribution: Ubuntu Linux, also tried booting fedora and knoppix, to no avail Hardware Environment: MSI-S420 notebook (MS-141214 barebone) Software Environment: kernel Problem Description: Just bought this notebook, and it wont boot unless I add "acpi=off" or "hpet=disable" to the kernel parameters. This bug might be related to Bug 6984 since that is also an MSI notebook with an ATI chipset. When I boot with no options, there are the last kernel messages: using HPET for base-timer using HPET for gettimeofday Detected 2000.186 MHz processor Using hpet for high-res timesource. After that, the machine hangs (even no response to sysrq key combinations). I tried "nohpet" instead of "hpet=disable" but that doesn't work. If more information is needed (which it probably will be), please point me to the right resources with information on how to obtain that information. I am not a kernel hacker. Steps to reproduce: boot without "acpi=off" or "hpet=disable".
Sooooo much has changed since 2.6.15. Can you test 2.6.18?
I upgraded from ubuntu dapper to edgy, and I run kernel 2.6.17-10 now. The issues persists. Is there reason to believe 2.6.18 will fix this? I ask because installing a new kernel would be risky and takes time, so it's better to be informed in advance. perhaps related messages in my kernel log (while booting with hpet=disable): [17179569.184000] ACPI: HPET (v001 MSI OEMHPET 0x07072006 MSFT 0x00000097) @ 0x77fd4230 [17179569.184000] ACPI: HPET id: 0x0 base: 0xfed00000 When booting, I can also see some messages (something like BIOS not supported), these messages do not end up in the kernel log, and they scroll away too fast. How can I get hold of them?
I managed to read these messages: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not using MMCONFIG PCI: Cannot allocate resource region 3 of device 0000:00:00.0 happen when I boot with hpet=disable. With anything else, I only get the third message and the machine hangs. Do you think it is useful to try with latest kernel 2.6.18? (ie. did anything even remotely relevant change???)
uh-oh, mmconfig stuff. Andi, could you please take a look at this one?
Dimitry, Ubuntu won't show most of the kernel output by default. Remove the "quiet" and "splash" arguments from the kernel command line in grub. The MMConfig stuff is harmless.
Dimitry, Were you able to get the boot trace without boot parameters as it noted in #5? And have you done any testing with latest kernels since then? Thanks.
We recently fixed a regression that could have caused this in mainline. So please test 2.6.22 when it comes out (any day now) or apply http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0f8dc2f06560e2ca126d1670a24126ba08357d38