On Wed, May 28, 2014 at 05:20:11PM +0200, Peter Zijlstra wrote:
> > >
> > > Pentium 4 's were not 64bit, were they?
> >
> > Not all, but there were 64bit varians (Xeons iirc).
>
> http://en.wikipedia.org/wiki/Pentium_d
>
> consumer netburst chip with x86_64.
Yeah, thanks.
--
To unsubscribe
On Wed, May 28, 2014 at 06:06:32PM +0400, Cyrill Gorcunov wrote:
> On Wed, May 28, 2014 at 03:56:17PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> > >
> > > It crashes more or less instantly (sorry for the line
On Wed, May 28, 2014 at 03:56:17PM +0200, Pavel Machek wrote:
> Hi!
>
> > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> >
> > It crashes more or less instantly (sorry for the line wrapping,
> > just got the serial console hooked up and don't have minicom
Hi!
> So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
>
> It crashes more or less instantly (sorry for the line wrapping,
> just got the serial console hooked up and don't have minicom configured
> right yet).
>
> this is 3.15-rc4 with the anti-memory corruption
Hi!
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial console hooked up and don't have minicom configured
right yet).
this is 3.15-rc4 with the anti-memory corruption patch
On Wed, May 28, 2014 at 03:56:17PM +0200, Pavel Machek wrote:
Hi!
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial console hooked up and don't have minicom configured
right
On Wed, May 28, 2014 at 06:06:32PM +0400, Cyrill Gorcunov wrote:
On Wed, May 28, 2014 at 03:56:17PM +0200, Pavel Machek wrote:
Hi!
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got
On Wed, May 28, 2014 at 05:20:11PM +0200, Peter Zijlstra wrote:
Pentium 4 's were not 64bit, were they?
Not all, but there were 64bit varians (Xeons iirc).
http://en.wikipedia.org/wiki/Pentium_d
consumer netburst chip with x86_64.
Yeah, thanks.
--
To unsubscribe from this list:
On Thu, May 15, 2014 at 01:31:16AM -0400, Vince Weaver wrote:
> On Thu, 15 May 2014, Cyrill Gorcunov wrote:
>
> > So I'm experiencing the same problem on latest -tip + my patches applied.
>
> glad it's not just me.
>
> I find the problem to be reproducible and so in theory it might be
>
On Thu, May 15, 2014 at 01:31:16AM -0400, Vince Weaver wrote:
On Thu, 15 May 2014, Cyrill Gorcunov wrote:
So I'm experiencing the same problem on latest -tip + my patches applied.
glad it's not just me.
I find the problem to be reproducible and so in theory it might be
possible to
On Thu, 15 May 2014, Cyrill Gorcunov wrote:
> So I'm experiencing the same problem on latest -tip + my patches applied.
glad it's not just me.
I find the problem to be reproducible and so in theory it might be
possible to generate a small reproducing test case.
I meant to do that already but
On Fri, May 09, 2014 at 12:19:49PM -0400, Vince Weaver wrote:
> On Thu, 8 May 2014, Cyrill Gorcunov wrote:
> >
> > Updated.
> > ---
> > arch/x86/kernel/cpu/perf_event_p4.c | 67
> >
> > 1 file changed, 30 insertions(+), 37 deletions(-)
>
> I tried this
On Thu, 15 May 2014, Cyrill Gorcunov wrote:
So I'm experiencing the same problem on latest -tip + my patches applied.
glad it's not just me.
I find the problem to be reproducible and so in theory it might be
possible to generate a small reproducing test case.
I meant to do that already but
On Fri, May 09, 2014 at 12:19:49PM -0400, Vince Weaver wrote:
On Thu, 8 May 2014, Cyrill Gorcunov wrote:
Updated.
---
arch/x86/kernel/cpu/perf_event_p4.c | 67
1 file changed, 30 insertions(+), 37 deletions(-)
I tried this patch, and even
On Fri, May 09, 2014 at 12:19:49PM -0400, Vince Weaver wrote:
> On Thu, 8 May 2014, Cyrill Gorcunov wrote:
> >
> > Updated.
> > ---
> > arch/x86/kernel/cpu/perf_event_p4.c | 67
> >
> > 1 file changed, 30 insertions(+), 37 deletions(-)
>
> I tried this
On Thu, 8 May 2014, Cyrill Gorcunov wrote:
>
> Updated.
> ---
> arch/x86/kernel/cpu/perf_event_p4.c | 67
>
> 1 file changed, 30 insertions(+), 37 deletions(-)
I tried this patch, and even though it seemed to fix one of the NMI storms
I was experiencing
On Thu, 8 May 2014, Cyrill Gorcunov wrote:
Updated.
---
arch/x86/kernel/cpu/perf_event_p4.c | 67
1 file changed, 30 insertions(+), 37 deletions(-)
I tried this patch, and even though it seemed to fix one of the NMI storms
I was experiencing I've
On Fri, May 09, 2014 at 12:19:49PM -0400, Vince Weaver wrote:
On Thu, 8 May 2014, Cyrill Gorcunov wrote:
Updated.
---
arch/x86/kernel/cpu/perf_event_p4.c | 67
1 file changed, 30 insertions(+), 37 deletions(-)
I tried this patch, and even
On Thu, May 08, 2014 at 11:49:30AM +0400, Cyrill Gorcunov wrote:
> > Don, Vince, could you please give the patch a run? I've only compile tested
> > it obviously since I've no real p4 hw. And the patch itself is a bit ugly
> > but should bring the light if we're still having problems in events
> >
On Thu, May 08, 2014 at 11:37:56AM +0400, Cyrill Gorcunov wrote:
> On Wed, May 07, 2014 at 10:00:50PM -0400, Don Zickus wrote:
> >
> > I think my commit 13beacee817d27a40ffc6f065ea0042685611dd5 explains this
> > corruption. Though I have to admit I haven't looked through the problem
> > very
On Wed, May 07, 2014 at 10:00:50PM -0400, Don Zickus wrote:
>
> I think my commit 13beacee817d27a40ffc6f065ea0042685611dd5 explains this
> corruption. Though I have to admit I haven't looked through the problem
> very closely yet.
>
> IOW my lazy fix in that commit doesn't cover fuzzers and the
On Wed, May 07, 2014 at 10:00:50PM -0400, Don Zickus wrote:
I think my commit 13beacee817d27a40ffc6f065ea0042685611dd5 explains this
corruption. Though I have to admit I haven't looked through the problem
very closely yet.
IOW my lazy fix in that commit doesn't cover fuzzers and the real
On Thu, May 08, 2014 at 11:37:56AM +0400, Cyrill Gorcunov wrote:
On Wed, May 07, 2014 at 10:00:50PM -0400, Don Zickus wrote:
I think my commit 13beacee817d27a40ffc6f065ea0042685611dd5 explains this
corruption. Though I have to admit I haven't looked through the problem
very closely yet.
On Thu, May 08, 2014 at 11:49:30AM +0400, Cyrill Gorcunov wrote:
Don, Vince, could you please give the patch a run? I've only compile tested
it obviously since I've no real p4 hw. And the patch itself is a bit ugly
but should bring the light if we're still having problems in events
On Thu, May 08, 2014 at 01:14:56AM -0400, Vince Weaver wrote:
> >
> > There were a bug in p4 pmu Don (CC'ed) fixed not that long ago but I fear
> > not all corner cases might be covered yet.
>
> I hit the NMI warnings somewhat often on Intel hardware (Haswell, Core2)
> but it usually doesn't
On Wed, May 07, 2014 at 10:00:50PM -0400, Don Zickus wrote:
> >
> > If i'm right (btw it's possible to use addr2line helper?) then hwc->config
> > is corrupted and p4_config_get_bind returned nil simply because proper event
> > was not found. And I don't understand how it could happen because
On Thu, 8 May 2014, Cyrill Gorcunov wrote:
> > > The NMI issue is probably the only one that is p4 related, and I do get
> > > the NMI warnings on other machines too, it's just the p4 is the only one
> > > where it brings down the machine.
> >
> > Vince, could you please provde more details on
On Wed, May 07, 2014 at 12:23:08AM +0400, Cyrill Gorcunov wrote:
> On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
> >
> > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> >
> > It crashes more or less instantly (sorry for the line wrapping,
> > just
On Thu, May 08, 2014 at 01:51:44AM +0400, Cyrill Gorcunov wrote:
>
> > When fuzzing on the p4 *other* things do happen.
> > * at least two warnings pop up almost instantly
> > * eventually the machine will crash in an endless NMI storm
> > * also I managed to get the machine wedged
On Wed, May 07, 2014 at 05:17:22PM -0400, Vince Weaver wrote:
> On Wed, 7 May 2014, Cyrill Gorcunov wrote:
>
> > > I thought I was running with PeterZ's latest patch that was supposed to
> > > avoid the corruption. Hmmm. Let me reboot and try a few more things.
> >
> > Thanks! Please ping me
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
> > I thought I was running with PeterZ's latest patch that was supposed to
> > avoid the corruption. Hmmm. Let me reboot and try a few more things.
>
> Thanks! Please ping me if find something new.
It turns out to be my fault, I was running with an
On Wed, May 07, 2014 at 01:07:40PM -0400, Vince Weaver wrote:
> >
> > Vince, I'm trying to figure out where it might come from, but no
> > ideas yet.
>
> I just got this, also looks like poison (see RBX).
Indeed, except ending 2b value.
> This could be related to the ongoing memory corruption
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
> On Wed, May 07, 2014 at 08:49:02PM +0400, Cyrill Gorcunov wrote:
> > On Wed, May 07, 2014 at 12:46:24PM -0400, Vince Weaver wrote:
> > >
> > > sorry for the delay, I like to compile kernels locally and it takes a
> > > really long time to build a
On Wed, May 07, 2014 at 08:49:02PM +0400, Cyrill Gorcunov wrote:
> On Wed, May 07, 2014 at 12:46:24PM -0400, Vince Weaver wrote:
> >
> > sorry for the delay, I like to compile kernels locally and it takes a
> > really long time to build a ftrace-enabled kernel on a pentium 4 it seems.
> >
> >
On Wed, May 07, 2014 at 12:46:24PM -0400, Vince Weaver wrote:
>
> sorry for the delay, I like to compile kernels locally and it takes a
> really long time to build a ftrace-enabled kernel on a pentium 4 it seems.
>
> Anyway I threw some printks in, and this is what I get:
>
> [ 447.572626]
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
> On Tue, May 06, 2014 at 05:30:19PM -0400, Vince Weaver wrote:
> > On Wed, 7 May 2014, Cyrill Gorcunov wrote:
> >
> > > > [ 67.872274] BUG: unable to handle kernel NULL pointer dereference at
> > > > 0004
> > > > [ 67.876146] IP: []
> > > >
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
On Tue, May 06, 2014 at 05:30:19PM -0400, Vince Weaver wrote:
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
[ 67.872274] BUG: unable to handle kernel NULL pointer dereference at
0004
[ 67.876146] IP: [81013df2]
On Wed, May 07, 2014 at 12:46:24PM -0400, Vince Weaver wrote:
sorry for the delay, I like to compile kernels locally and it takes a
really long time to build a ftrace-enabled kernel on a pentium 4 it seems.
Anyway I threw some printks in, and this is what I get:
[ 447.572626] VMW:
On Wed, May 07, 2014 at 08:49:02PM +0400, Cyrill Gorcunov wrote:
On Wed, May 07, 2014 at 12:46:24PM -0400, Vince Weaver wrote:
sorry for the delay, I like to compile kernels locally and it takes a
really long time to build a ftrace-enabled kernel on a pentium 4 it seems.
Anyway I
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
On Wed, May 07, 2014 at 08:49:02PM +0400, Cyrill Gorcunov wrote:
On Wed, May 07, 2014 at 12:46:24PM -0400, Vince Weaver wrote:
sorry for the delay, I like to compile kernels locally and it takes a
really long time to build a ftrace-enabled
On Wed, May 07, 2014 at 01:07:40PM -0400, Vince Weaver wrote:
Vince, I'm trying to figure out where it might come from, but no
ideas yet.
I just got this, also looks like poison (see RBX).
Indeed, except ending 2b value.
This could be related to the ongoing memory corruption bug found
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
I thought I was running with PeterZ's latest patch that was supposed to
avoid the corruption. Hmmm. Let me reboot and try a few more things.
Thanks! Please ping me if find something new.
It turns out to be my fault, I was running with an
On Wed, May 07, 2014 at 05:17:22PM -0400, Vince Weaver wrote:
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
I thought I was running with PeterZ's latest patch that was supposed to
avoid the corruption. Hmmm. Let me reboot and try a few more things.
Thanks! Please ping me if find
On Thu, May 08, 2014 at 01:51:44AM +0400, Cyrill Gorcunov wrote:
When fuzzing on the p4 *other* things do happen.
* at least two warnings pop up almost instantly
* eventually the machine will crash in an endless NMI storm
* also I managed to get the machine wedged with an
On Wed, May 07, 2014 at 12:23:08AM +0400, Cyrill Gorcunov wrote:
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the
On Thu, 8 May 2014, Cyrill Gorcunov wrote:
The NMI issue is probably the only one that is p4 related, and I do get
the NMI warnings on other machines too, it's just the p4 is the only one
where it brings down the machine.
Vince, could you please provde more details on that? Is it
On Wed, May 07, 2014 at 10:00:50PM -0400, Don Zickus wrote:
If i'm right (btw it's possible to use addr2line helper?) then hwc-config
is corrupted and p4_config_get_bind returned nil simply because proper event
was not found. And I don't understand how it could happen because before
On Thu, May 08, 2014 at 01:14:56AM -0400, Vince Weaver wrote:
There were a bug in p4 pmu Don (CC'ed) fixed not that long ago but I fear
not all corner cases might be covered yet.
I hit the NMI warnings somewhat often on Intel hardware (Haswell, Core2)
but it usually doesn't make the
On Tue, May 06, 2014 at 05:30:19PM -0400, Vince Weaver wrote:
> On Wed, 7 May 2014, Cyrill Gorcunov wrote:
>
> > > [ 67.872274] BUG: unable to handle kernel NULL pointer dereference at
> > > 0004
> > > [ 67.876146] IP: [] p4_pmu_schedule_events+0xa5/0x331
> >
> > This looks like
> >
>
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
> > [ 67.872274] BUG: unable to handle kernel NULL pointer dereference at
> > 0004
> > [ 67.876146] IP: [] p4_pmu_schedule_events+0xa5/0x331
>
> This looks like
>
> p4_pmu_schedule_events:
> ...
> bind =
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
>
> So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
>
> It crashes more or less instantly (sorry for the line wrapping,
> just got the serial console hooked up and don't have minicom configured
> right
On Tue, 6 May 2014, Cyrill Gorcunov wrote:
> On Tue, May 06, 2014 at 12:11:49PM -0400, Vince Weaver wrote:
> >
> > If I had infinite time I'd try to get the SGI Octane, Ultrasparc, and
> > avr32 boards up and going again.
>
> Btw, Vince, perf_fuzzer -- it's
>
On Tue, May 06, 2014 at 12:11:49PM -0400, Vince Weaver wrote:
>
> If I had infinite time I'd try to get the SGI Octane, Ultrasparc, and
> avr32 boards up and going again.
Btw, Vince, perf_fuzzer -- it's
http://web.eece.maine.edu/~vweaver/projects/perf_events/fuzzer/?
--
To unsubscribe from
On Tue, 6 May 2014, Peter Zijlstra wrote:
> On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
> >
> > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> >
> > It crashes more or less instantly (sorry for the line wrapping,
> > just got the serial console
On Tue, May 06, 2014 at 12:05:41PM -0400, Vince Weaver wrote:
> On Tue, 6 May 2014, Cyrill Gorcunov wrote:
>
> > On Tue, May 06, 2014 at 05:46:37PM +0200, Peter Zijlstra wrote:
> > > On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
> > > >
> > > > So just to be difficult I fired up
On Tue, 6 May 2014, Cyrill Gorcunov wrote:
> On Tue, May 06, 2014 at 05:46:37PM +0200, Peter Zijlstra wrote:
> > On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
> > >
> > > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> > >
> > > It crashes more or
On Tue, May 06, 2014 at 05:46:37PM +0200, Peter Zijlstra wrote:
> On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
> >
> > So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
> >
> > It crashes more or less instantly (sorry for the line wrapping,
> > just got
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
>
> So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
>
> It crashes more or less instantly (sorry for the line wrapping,
> just got the serial console hooked up and don't have minicom configured
> right
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial console hooked up and don't have minicom configured
right yet).
this is 3.15-rc4 with the anti-memory corruption patch applied.
[
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial console hooked up and don't have minicom configured
right yet).
this is 3.15-rc4 with the anti-memory corruption patch applied.
[
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial console hooked up and don't have minicom configured
right yet).
On Tue, May 06, 2014 at 05:46:37PM +0200, Peter Zijlstra wrote:
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial
On Tue, 6 May 2014, Cyrill Gorcunov wrote:
On Tue, May 06, 2014 at 05:46:37PM +0200, Peter Zijlstra wrote:
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly
On Tue, May 06, 2014 at 12:05:41PM -0400, Vince Weaver wrote:
On Tue, 6 May 2014, Cyrill Gorcunov wrote:
On Tue, May 06, 2014 at 05:46:37PM +0200, Peter Zijlstra wrote:
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
So just to be difficult I fired up the perf_fuzzer
On Tue, 6 May 2014, Peter Zijlstra wrote:
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial console hooked up
On Tue, May 06, 2014 at 12:11:49PM -0400, Vince Weaver wrote:
If I had infinite time I'd try to get the SGI Octane, Ultrasparc, and
avr32 boards up and going again.
Btw, Vince, perf_fuzzer -- it's
http://web.eece.maine.edu/~vweaver/projects/perf_events/fuzzer/?
--
To unsubscribe from this
On Tue, 6 May 2014, Cyrill Gorcunov wrote:
On Tue, May 06, 2014 at 12:11:49PM -0400, Vince Weaver wrote:
If I had infinite time I'd try to get the SGI Octane, Ultrasparc, and
avr32 boards up and going again.
Btw, Vince, perf_fuzzer -- it's
On Tue, May 06, 2014 at 11:42:58AM -0400, Vince Weaver wrote:
So just to be difficult I fired up the perf_fuzzer on a Pentium 4 machine.
It crashes more or less instantly (sorry for the line wrapping,
just got the serial console hooked up and don't have minicom configured
right yet).
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
[ 67.872274] BUG: unable to handle kernel NULL pointer dereference at
0004
[ 67.876146] IP: [81013df2] p4_pmu_schedule_events+0xa5/0x331
This looks like
p4_pmu_schedule_events:
...
bind =
On Tue, May 06, 2014 at 05:30:19PM -0400, Vince Weaver wrote:
On Wed, 7 May 2014, Cyrill Gorcunov wrote:
[ 67.872274] BUG: unable to handle kernel NULL pointer dereference at
0004
[ 67.876146] IP: [81013df2] p4_pmu_schedule_events+0xa5/0x331
This looks like
70 matches
Mail list logo
