You are not logged in.

Pages: 1 2

#26 2014-11-13 15:08:40

MK13
Member
From: Germany
Registered: 2014-04-12
Posts: 80

Re: Kernel traps & core dumps

Did you perhaps forget to suspend/resume? I would expect to see another block of 'CPUx microcode updated early to revision 0x1c, date = 2014-07-03' after a resume.

Offline

#27 2014-11-13 23:06:25

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Kernel traps & core dumps

Yeah, @MK13, I forgot to suspend and resume after that. Ooops!

After boot, but before suspend:

[mrunion@rustyhump ~]$ sudo dmesg | grep microcode
[    0.000000] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.091537] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.112431] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.133396] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.446628] microcode: CPU0 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446631] microcode: CPU1 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446637] microcode: CPU2 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446644] microcode: CPU3 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446650] microcode: CPU4 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446656] microcode: CPU5 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446662] microcode: CPU6 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446669] microcode: CPU7 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446702] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

After resume from suspend:

[mrunion@rustyhump ~]$ sudo dmesg | grep microcode
[    0.000000] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.091537] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.112431] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.133396] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.446628] microcode: CPU0 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446631] microcode: CPU1 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446637] microcode: CPU2 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446644] microcode: CPU3 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446650] microcode: CPU4 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446656] microcode: CPU5 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446662] microcode: CPU6 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446669] microcode: CPU7 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446702] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[  441.473471] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[  441.487877] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[  441.501980] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[  441.516096] CPU4 microcode updated early to revision 0x1c, date = 2014-07-03

I guess this still isn't too helpful then.

Last edited by mrunion (2014-11-13 23:06:57)

Matt

"It is very difficult to educate the educated."

Offline

#28 2014-11-14 10:35:25

MK13
Member
From: Germany
Registered: 2014-04-12
Posts: 80

Re: Kernel traps & core dumps

mrunion wrote:

Yeah, @MK13, I forgot to suspend and resume after that. Ooops!

big_smile

Could you provide the output of the following command?

cat /proc/cpuinfo | egrep "processor|physical id|core id" | sed 's/^processor/\nprocessor/g'

It shows which CPUx corresponds to which physical CPU core. It is interesting because after boot CPU0-3 are updated with the new micorcode and after a resume CPU1-4.

Last edited by MK13 (2014-11-14 12:16:01)

Offline

#29 2014-11-15 02:21:36

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Kernel traps & core dumps

I redid the mircrocode output, and added the new request at the end:

After startup before suspend:

[mrunion@rustyhump ~]$ sudo dmesg | grep microcode
[    0.000000] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.091406] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.112398] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.133364] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.446432] microcode: CPU0 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446435] microcode: CPU1 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446441] microcode: CPU2 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446447] microcode: CPU3 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446454] microcode: CPU4 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446460] microcode: CPU5 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446467] microcode: CPU6 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446472] microcode: CPU7 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446506] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

After suspend:

[mrunion@rustyhump ~]$ sudo dmesg | grep microcode
[    0.000000] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.091406] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.112398] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.133364] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[    0.446432] microcode: CPU0 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446435] microcode: CPU1 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446441] microcode: CPU2 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446447] microcode: CPU3 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446454] microcode: CPU4 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446460] microcode: CPU5 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446467] microcode: CPU6 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446472] microcode: CPU7 sig=0x306c3, pf=0x10, revision=0x1c
[    0.446506] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[  669.889893] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[  669.904389] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[  669.918606] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[  669.932721] CPU4 microcode updated early to revision 0x1c, date = 2014-07-03

Processor info:

[mrunion@rustyhump ~]$ sudo cat /proc/cpuinfo | egrep "processor|physical id|core id" | sed 's/^processor/\nprocessor/g'
processor       : 0
physical id     : 0
core id         : 0

processor       : 1
physical id     : 0
core id         : 1

processor       : 2
physical id     : 0
core id         : 2

processor       : 3
physical id     : 0
core id         : 3

processor       : 4
physical id     : 0
core id         : 0

processor       : 5
physical id     : 0
core id         : 1

processor       : 6
physical id     : 0
core id         : 2

processor       : 7
physical id     : 0
core id         : 3

Last edited by mrunion (2014-11-15 02:25:04)

Matt

"It is very difficult to educate the educated."

Offline

#30 2014-11-15 11:35:04

MK13
Member
From: Germany
Registered: 2014-04-12
Posts: 80

Re: Kernel traps & core dumps

As I thought: CPU4 is the HT for physical core 0. So on resume the CPU4 receives the update which will affect CPU0 too.

Yesterday a patch was released on the kernel bugzilla and brain0 already build a new version with the fix in the testing repo. With this, my issues are gone.

Offline

#31 2014-11-15 17:48:23

GourdCaptain
Member
Registered: 2009-04-18
Posts: 121

Re: Kernel traps & core dumps

MK13 wrote:

As I thought: CPU4 is the HT for physical core 0. So on resume the CPU4 receives the update which will affect CPU0 too.

Yesterday a patch was released on the kernel bugzilla and brain0 already build a new version with the fix in the testing repo. With this, my issues are gone.

Which Kernel version should we be looking for that has this fix?

Avatar by Ditey: https://twitter.com/phrobitey

Offline

#32 2014-11-15 19:15:57

MK13
Member
From: Germany
Registered: 2014-04-12
Posts: 80

Re: Kernel traps & core dumps

The fix is included in version 3.17.3-1,  at least in our testing repository: https://www.archlinux.org/packages/test … _64/linux/

Don't know about the official kernel though.

Last edited by MK13 (2014-11-15 19:16:39)

Offline

#33 2014-11-16 21:56:52

InvalidInterrupt
Member
Registered: 2014-11-01
Posts: 4

Re: Kernel traps & core dumps

Quick PSA:
The patched kernel has been pushed to the core repo. If you're experiencing this issue, update your system and see if that helps.

After doing a quick search through the kernel's git commit messages, the change doesn't seem to be in their repo yet.

Offline

#34 2014-11-16 22:05:15

MK13
Member
From: Germany
Registered: 2014-04-12
Posts: 80

Re: Kernel traps & core dumps

Thanks for the update InvalidInterrupt.

I would like to thank everyone who helped in solving the issue, this is why I love FOSS.

Offline

Pages: 1 2

Board footer

Powered by FluxBB