> On Mon, 2018-01-08 at 11:08 -0800, Tim Mouraveiko wrote:
> >
> >
> > I think you missed one of my posts from last week. The code has
> > nothing to do with linux.
>
> Like the 'f00f' bug in the Pentium days, there may well be a way that a
> kernel can *pre
> On Mon, 2018-01-08 at 11:08 -0800, Tim Mouraveiko wrote:
> >
> >
> > I think you missed one of my posts from last week. The code has
> > nothing to do with linux.
>
> Like the 'f00f' bug in the Pentium days, there may well be a way that a
> kernel can *pre
> On Mon 2018-01-08 07:58:33, Tim Mouraveiko wrote:
> > > Hi!
> > >
> > > > > Is the sequence available from ring 3, or does it need ring 0?
> > > > >
> > > > > Can we get the code? Extraordinary claims and all that...
> >
> On Mon 2018-01-08 07:58:33, Tim Mouraveiko wrote:
> > > Hi!
> > >
> > > > > Is the sequence available from ring 3, or does it need ring 0?
> > > > >
> > > > > Can we get the code? Extraordinary claims and all that...
> >
> On Monday 08 of January 2018, Tim Mouraveiko wrote:
> > > Hi!
> > >
> > > > > Is the sequence available from ring 3, or does it need ring 0?
> > > > >
> > > > > Can we get the code? Extraordinary claims and all that...
> >
> On Monday 08 of January 2018, Tim Mouraveiko wrote:
> > > Hi!
> > >
> > > > > Is the sequence available from ring 3, or does it need ring 0?
> > > > >
> > > > > Can we get the code? Extraordinary claims and all that...
> >
> Hi!
>
> > > Is the sequence available from ring 3, or does it need ring 0?
> > >
> > > Can we get the code? Extraordinary claims and all that...
> > >
> >
> > I did not test privilege level. Are you suggesting that I put the code out
> > there for everyone to
> > see or what?
>
> Yes, that's
> Hi!
>
> > > Is the sequence available from ring 3, or does it need ring 0?
> > >
> > > Can we get the code? Extraordinary claims and all that...
> > >
> >
> > I did not test privilege level. Are you suggesting that I put the code out
> > there for everyone to
> > see or what?
>
> Yes, that's
> Hi!
>
> On Thu 2018-01-04 17:21:36, Tim Mouraveiko wrote:
> > > On Thu 2018-01-04 14:13:56, Tim Mouraveiko wrote:
> > > > > > As I mentioned before, I repeatedly and fully power-cycled the
> > > > > > motherboard and reset BIOS
> Hi!
>
> On Thu 2018-01-04 17:21:36, Tim Mouraveiko wrote:
> > > On Thu 2018-01-04 14:13:56, Tim Mouraveiko wrote:
> > > > > > As I mentioned before, I repeatedly and fully power-cycled the
> > > > > > motherboard and reset BIOS
> On Thu, Jan 4, 2018 at 4:00 PM, Tim Mouraveiko <tim...@ipcopper.com> wrote:
> > Pavel,
> >
> > As I mentioned before, I repeatedly and fully power-cycled the motherboard
> > and reset BIOS
> > and etc. It made no difference. I can see that the p
> On Thu, Jan 4, 2018 at 4:00 PM, Tim Mouraveiko wrote:
> > Pavel,
> >
> > As I mentioned before, I repeatedly and fully power-cycled the motherboard
> > and reset BIOS
> > and etc. It made no difference. I can see that the processor was not
> > drawing a
> On 2018-01-05 10:21, Tim Mouraveiko wrote:
> >> On Thu 2018-01-04 14:13:56, Tim Mouraveiko wrote:
> >> Actually... I don't think your code works. That's why I'm curious. But
> >> if it works, its rather a big news... and I'm sure Intel and cloud
> >&g
> On 2018-01-05 10:21, Tim Mouraveiko wrote:
> >> On Thu 2018-01-04 14:13:56, Tim Mouraveiko wrote:
> >> Actually... I don't think your code works. That's why I'm curious. But
> >> if it works, its rather a big news... and I'm sure Intel and cloud
> >&g
> On Thu 2018-01-04 14:13:56, Tim Mouraveiko wrote:
> > > > As I mentioned before, I repeatedly and fully power-cycled the
> > > > motherboard and reset BIOS
> > > > and etc. It made no difference. I can see that the processor was not
> > > > d
> On Thu 2018-01-04 14:13:56, Tim Mouraveiko wrote:
> > > > As I mentioned before, I repeatedly and fully power-cycled the
> > > > motherboard and reset BIOS
> > > > and etc. It made no difference. I can see that the processor was not
> > > > d
> > As I mentioned before, I repeatedly and fully power-cycled the motherboard
> > and reset BIOS
> > and etc. It made no difference. I can see that the processor was not
> > drawing any power. The
> > software code behaved in a similar fashion on other processors, until I
> > fixed it so that
> > As I mentioned before, I repeatedly and fully power-cycled the motherboard
> > and reset BIOS
> > and etc. It made no difference. I can see that the processor was not
> > drawing any power. The
> > software code behaved in a similar fashion on other processors, until I
> > fixed it so that
> On Thu, Jan 4, 2018 at 11:00 PM, Tim Mouraveiko <tim...@ipcopper.com> wrote:
> > Pavel,
> >
> > As I mentioned before, I repeatedly and fully power-cycled the motherboard
> > and reset BIOS
> > and etc. It made no difference. I can see that the p
> On Thu, Jan 4, 2018 at 11:00 PM, Tim Mouraveiko wrote:
> > Pavel,
> >
> > As I mentioned before, I repeatedly and fully power-cycled the motherboard
> > and reset BIOS
> > and etc. It made no difference. I can see that the processor was not
> > drawing a
Pavel,
As I mentioned before, I repeatedly and fully power-cycled the motherboard and
reset BIOS
and etc. It made no difference. I can see that the processor was not drawing
any power. The
software code behaved in a similar fashion on other processors, until I fixed
it so that it would
not
Pavel,
As I mentioned before, I repeatedly and fully power-cycled the motherboard and
reset BIOS
and etc. It made no difference. I can see that the processor was not drawing
any power. The
software code behaved in a similar fashion on other processors, until I fixed
it so that it would
not
Hi,
In all my years of extensive experience writing drivers and kernels, I never
came across a situation
where you could brick an x86 CPU. Not until recently, when I was working on
debugging a piece of
code and I bricked an Intel CPU. I am not talking about an experimental
motherboard or
Hi,
In all my years of extensive experience writing drivers and kernels, I never
came across a situation
where you could brick an x86 CPU. Not until recently, when I was working on
debugging a piece of
code and I bricked an Intel CPU. I am not talking about an experimental
motherboard or
On 12/26/2017 09:43 PM, Tom Lendacky wrote:
>AMD processors are not subject to the types of attacks that the kernel page
>table isolation
feature protects against.
There is no doubt this is a serious flaw. This thread reminded me - about a
year ago we
discovered a software code that bricked
On 12/26/2017 09:43 PM, Tom Lendacky wrote:
>AMD processors are not subject to the types of attacks that the kernel page
>table isolation
feature protects against.
There is no doubt this is a serious flaw. This thread reminded me - about a
year ago we
discovered a software code that bricked
26 matches
Mail list logo
