linux-next acpi changes make vmware server unusable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I built a linux-next kernel yesterday and discovered that the free
vmware server 2 would start to boot the kernel and very quickly just
power off.  vmware gave some crap message about the MBR being wrong,
which obviously wasn't the case since grub started and the kernel
started booting.  Looking at the last line on the serial console for the
new kernel and the next line in a working kernel I knew the next output
was supposed to be in the ACPI code.  I bisected drivers/acpi and found
that d6c349993fc7c9dabf873796c4e82bb94544b3ce is first bad commit.

I have no idea what vmware is doing, or what we are doing, but before
that patch I was able to boot and after it, vmware just shuts itself
off.

-Eric


--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux