On Mon, Aug 24, 2015 at 05:37:17PM -0500, sherry hurwitz wrote:
Hey Sherry,
> I have duplicated your problem and asked the HW architect that wrote
> 832 to review the diff between the 822 and 832 microcode patch.
were there any updates to this issue in the meantime?
Thanks.
--
Regards/Gruss,
On 08/18/2015 05:10 AM, Jiri Olsa wrote:
On Mon, Aug 17, 2015 at 09:06:59AM -0700, Andy Lutomirski wrote:
On Sun, Aug 16, 2015 at 9:36 PM, Borislav Petkov wrote:
On Mon, Aug 17, 2015 at 12:29:56AM +0200, Jiri Olsa wrote:
hi,
'perf test 18' is failing on systems with AMD processor.
Hmm, sti
On Wed, Aug 19, 2015 at 06:12:50PM +0200, Borislav Petkov wrote:
> On Wed, Aug 19, 2015 at 05:58:17PM +0200, Jiri Olsa wrote:
> > if anything happens there, I dont see it ;-)
> >
> > I was told RHEL7 went off and on several times with AMD microcode,
> > now it's the period we actually install it..
On Wed, Aug 19, 2015 at 05:58:17PM +0200, Jiri Olsa wrote:
> if anything happens there, I dont see it ;-)
>
> I was told RHEL7 went off and on several times with AMD microcode,
> now it's the period we actually install it..
"went off an on"? What do you mean exactly?
> I'll poke around to see wh
On Wed, Aug 19, 2015 at 05:47:00PM +0200, Borislav Petkov wrote:
> On Wed, Aug 19, 2015 at 10:55:46AM +0200, Jiri Olsa wrote:
> > this is the perf breakpoint address:
> > 0045b260 :
> >
> > this is trace_printk output for NEW microcode 0x6000832:
> >
> > DEBUG EX
> > perf-89
On Wed, Aug 19, 2015 at 10:55:46AM +0200, Jiri Olsa wrote:
> this is the perf breakpoint address:
> 0045b260 :
>
> this is trace_printk output for NEW microcode 0x6000832:
>
> DEBUG EX
> perf-893 [003] d... 1358.053633: sync_regs: sync_regs eregs
> 88012ecc7f58, regs
On Wed, Aug 19, 2015 at 05:55:19AM +0200, Borislav Petkov wrote:
> On Tue, Aug 18, 2015 at 12:10:25PM +0200, Jiri Olsa wrote:
> > buut anyway, it looks like latest AMD firmware issue:
> >
> > [root@amd-pike-07 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version
> > 0x6000822
> > [root@amd-p
On Tue, Aug 18, 2015 at 12:10:25PM +0200, Jiri Olsa wrote:
> buut anyway, it looks like latest AMD firmware issue:
>
> [root@amd-pike-07 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version
> 0x6000822
> [root@amd-pike-07 perf]# ./perf test 18
> 18: Test breakpoint overflow signal handler
On Mon, Aug 17, 2015 at 09:06:59AM -0700, Andy Lutomirski wrote:
> On Sun, Aug 16, 2015 at 9:36 PM, Borislav Petkov wrote:
> > On Mon, Aug 17, 2015 at 12:29:56AM +0200, Jiri Olsa wrote:
> >> hi,
> >> 'perf test 18' is failing on systems with AMD processor.
> >
> > Hmm, still using that b0rked test
On Mon, Aug 17, 2015 at 09:06:59AM -0700, Andy Lutomirski wrote:
> >> expected course of actions is:
> >> 1) CPU hits 'test_function'
> >> 2) DB exception is triggered, with RFLAGS.RF=0
> >> 3) DB exception handler sets regs->RFLAGS.RF=1 and perf handler
> >> triggers irq_work pending wo
On Sun, Aug 16, 2015 at 9:36 PM, Borislav Petkov wrote:
> On Mon, Aug 17, 2015 at 12:29:56AM +0200, Jiri Olsa wrote:
>> hi,
>> 'perf test 18' is failing on systems with AMD processor.
>
> Hmm, still using that b0rked test box? :-)
>
> Also, which kernel?
>
> There have been substantial changes to
On Mon, Aug 17, 2015 at 06:36:03AM +0200, Borislav Petkov wrote:
> On Mon, Aug 17, 2015 at 12:29:56AM +0200, Jiri Olsa wrote:
> > hi,
> > 'perf test 18' is failing on systems with AMD processor.
>
> Hmm, still using that b0rked test box? :-)
heh, nope.. have seen this on at least 2 boxes so far
On Mon, Aug 17, 2015 at 12:29:56AM +0200, Jiri Olsa wrote:
> hi,
> 'perf test 18' is failing on systems with AMD processor.
Hmm, still using that b0rked test box? :-)
Also, which kernel?
There have been substantial changes to the entry code recently. Although
I don't see anything being done diff
13 matches
Mail list logo
