> Oh ... one more thing. Did your e-mail client line wrap that last line?
>
>> mce: [Hardware Error]: PROCESSOR 0:306d4 TIME 1526932210 SOCKET 0 APIC
>> 0 microcode 2a
>
> That should all be on one line.
Sorry IF ANY Problem
anyway i send the message using gmail with plain text mode
--
software e
On Mon, May 21, 2018 at 05:06:14PM -0700, Luck, Tony wrote:
> On Tue, May 22, 2018 at 02:43:37AM +0530, Jeffrin Thalakkottoor wrote:
> > mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 5: ee40110b
> > mce: [Hardware Error]: TSC 0 ADDR 16080 MISC 5040008086
> > mce: [Hardware Error]:
On Tue, May 22, 2018 at 02:43:37AM +0530, Jeffrin Thalakkottoor wrote:
> mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 5: ee40110b
> mce: [Hardware Error]: TSC 0 ADDR 16080 MISC 5040008086
> mce: [Hardware Error]: PROCESSOR 0:306d4 TIME 1526932210 SOCKET 0 APIC
> 0 microcode 2a
T
On Tue, May 22, 2018 at 2:27 AM, Luck, Tony wrote:
> How about this:
>
> $ sudo dmesg -r | grep -C 30 Bank
>
> -Tony
-->
$sudo dmesg -r | grep -C 30 Bank
x2apic: IRQ remapping doesn't support X2APIC mode
..TIMER:
I guess I didn't explain that very clearly. I need all the lines
in betweeen.
How about this:
$ sudo dmesg -r | grep -C 30 Bank
-Tony
On Mon, May 21, 2018 at 09:58:03AM -0700, Luck, Tony wrote:
> So BIOS did something to trigger some issues in the L3
> cache (more than once since the overflow and filter bits
> are both set).
>
> I think (but am not 100% sure because I don't have an
> internal decoder that knows about this specif
> (*) Can you send a snip from the raw dmesg output that starts
> a couple of lines before:
>
>
> ... [Hardware Error]: CPU 0: Machine Check: 0 Bank: 5 ...
>
> and continues a couple of lines past
>
> ... [Hardware Error]: PROCESSOR 0:306d4 ...
>
> and I'll take a look at why mcelog
On Mon, May 21, 2018 at 05:31:52PM +0530, Jeffrin Thalakkottoor wrote:
> > Ok, but please do not top-post.
>
> Ok
>
> > Looks like mcelog has trouble decoding this. Have you updated mcelog to
> > the latest version in your distro?
> .
> mcelog 153+dfsg-1
So this is
> Ok, but please do not top-post.
Ok
> Looks like mcelog has trouble decoding this. Have you updated mcelog to
> the latest version in your distro?
.
mcelog 153+dfsg-1
--
software engineer
rajagiri school of engineering and technology
On Sun, May 20, 2018 at 05:27:32PM +0530, Jeffrin Thalakkottoor wrote:
> output for "dmesg | mcelog --ascii" command related
Ok, but please do not top-post.
...
> Hardware event. This is not a software error.
> CPU 0 BANK 0 TSC dead
> STATUS 0 MCGSTATUS 0
> line timer enabled
> smpboot: CPU0: I
output for "dmesg | mcelog --ascii" command related
->
microcode: microcode updated early to revision 0x2a, date = 2018-01-18
Linux
that system is normally not crashing. as far as i know, there are no
other bad effects
it happens during every boot.it is not a one time message.
output for "sudo dmesg | grep -B 40 44919" command related
--
On Mon, May 14, 2018 at 06:27:52PM +0200, Borislav Petkov wrote:
> On Mon, May 14, 2018 at 09:19:11PM +0530, Jeffrin Thalakkottoor wrote:
> > hello,
> >
> > output related of "sudo dmesg -l emerg" from my laptop...
> >
> > -
On Mon, May 14, 2018 at 09:19:11PM +0530, Jeffrin Thalakkottoor wrote:
> hello,
>
> output related of "sudo dmesg -l emerg" from my laptop...
>
> --->
> $sudo dmesg -l emerg
> [sudo] password for jeff
14 matches
Mail list logo
