It does fail in the same way.
-Erich
On Wed, Jun 18, 2014 at 2:31 PM, Greg KH <greg@xxxxxxxxx> wrote:
On Wed, Jun 18, 2014 at 07:32:52PM +0000, Erich Eickmeyer wrote:
Dear Mr. Brandewie, et al,
I have noticed a kernel bug that causes it to fail to boot on my
machine, an
Acer Aspire E1-510P. The following is a transcription of the kernel
panic:
>Disabling lock debugging due to kernel taint
>mce: [Hardware Error]: CPU2: Machine Check Exception: 4 Bank 0:
>b200000430000423
>mce: [Hardware Error]: TSC 365f6dc39e
>mce: [Hardware Error]: PROCESSOR 0:30673 TIME 1402862769 SOCKET 0
APIC 4
>microcode 31a
>mce: [Hardware Error]: Run the above through 'mcelog --ascii'
>mce: [Hardware Error]: CPU3: Machine Check Exception: 4 Bank 0:
>b200000430000423
>mce: [Hardware Error]: TSC 365f6fa2e4
>mce: [Hardware Error]: PROCESSOR 0:30673 TIME 1402862769 SOCKET 0
APIC 6
>microcode 31a
>mce: [Hardware Error]: Run the above through 'mcelog --ascii'
>mce: [Hardware Error]: CPU1: Machine Check Exception: 4 Bank 0:
>b200000010000000
>mce: [Hardware Error]: TSC 365f73e988
>mce: [Hardware Error]: PROCESSOR 0:30673 TIME 1402862769 SOCKET 0
APIC 2
>microcode 31a
>mce: [Hardware Error]: Run the above through 'mcelog --ascii'
>mce: [Hardware Error]: CPU0: Machine Check Exception: 4 Bank 0:
>b200000010000000
>mce: [Hardware Error]: TSC 365f730e28
>mce: [Hardware Error]: PROCESSOR 0:30673 TIME 142862769 SOCKET 0
APIC 0
>microcode 31a
>mce: [Hardware Error]: Run the above through 'mcelog --ascii'
>mce: [Hardware Error]: Machine Check: Processor context corrupt
>Kernel panic - not syncing: Fatal Machine check
>Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range:
>0xffffffff80000000-0xfffffffff9fffffff)
>Rebooting in 90 seconds..
Kernel bisection points to this commit:
>dd4c4afb005de0415ea06e3586b017e193c1539e is the first bad commit
>commit dd4c4afb005de0415ea06e3586b017e193c1539e
>Author: Dirk Brandewie <dirk.j.brandewie@xxxxxxxxx>
>Date: Thu May 8 12:57:23 2014 -0700
>
> intel_pstate: Set turbo VID for BayTrail
> commit 21855ff5bcbdd075e1c99772827a84912ab083dd upstream.
> A documentation update exposed that there is a separate set of
VID
> values that must be used in the turbo/boost P state range. Add
> enumerating and setting the correct VID for P states in the
turbo
> range.
> Signed-off-by: Dirk Brandewie <dirk.j.brandewie@xxxxxxxxx>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
>
Not good. Does 3.16-rc1 also fail for you in the same way?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html