> 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 *prevent* the code sequence from killing
> 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 *prevent* the code sequence from killing
> 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...
> > > > >
> > > >
> > > > I did not test privilege level. Are you suggesting
> 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...
> > > > >
> > > >
> > > > I did not test privilege level. Are you suggesting
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...
> > > >
> > >
> > > I did not test privilege level. Are you suggesting that I put the code
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...
> > > >
> > >
> > > I did not test privilege level. Are you suggesting that I put the code
> 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...
> > > >
> > > > I did not test privilege level. Are you suggesting that I
> 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...
> > > >
> > > > I did not test privilege level. Are you suggesting that I
> 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
On 4.01.2018 02:47, Tim Mouraveiko wrote:
> 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.
On 4.01.2018 02:47, Tim Mouraveiko wrote:
> 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.
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 what I'm suggesting.
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 what I'm suggesting.
> 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
> > > > > > and etc. It made no difference. I can see that the
> 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
> > > > > > and etc. It made no difference. I can see that the
> 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 any power. The
> >
> 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 any power. The
> > software code behaved
> 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
> >> providers are going to be interested.
> >>
>
> 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
> >> providers are going to be interested.
> >>
>
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
> > > > > and etc. It made no difference. I can see that the processor was not
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
> > > > > and etc. It made no difference. I can see that the processor was not
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
> any power. The
> software code
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
> any power. The
> software code behaved in a similar
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
>> providers are going to be interested.
>>
>
> I first
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
>> providers are going to be interested.
>>
>
> I first
> 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
> > > > drawing any power. The
> > > > software code behaved
> 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
> > > > drawing any power. The
> > > > software code behaved
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
> > > drawing any power. The
> > > software code behaved in a similar
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
> > > drawing any power. The
> > > software code behaved in a similar
> > 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 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 any power. The
> >
> 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 any power. The
> > software code behaved
Hi!
> 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
Hi!
> 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
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
> any power. The
> software code
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
> any power. The
> software code behaved in a similar
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
>
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
>
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
44 matches
Mail list logo