* [parisc-linux] running gcc testsuite triggers ongoing page faults
@ 2004-01-11 9:16 Matthias Klose
2004-01-11 10:08 ` Randolph Chung
` (3 more replies)
0 siblings, 4 replies; 10+ messages in thread
From: Matthias Klose @ 2004-01-11 9:16 UTC (permalink / raw)
To: parisc-linux, debian-hppa
I think I did see this first with gcc-3.3 from 20031229. Running the
3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
all CPU time, together with syslogd and klogd. /var get's filled with
log messages in kern.log, syslog and debug.
The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
Jan 11 06:42:49 pampa kernel: do_page_fault() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 000lt() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 00000ab50a94d690 00000ab50a94d694 0000000000020dd4
Jan 11 06:42:49 pampa kernel: r28-31 00000ab54abfccfa 0000000040336584 00000000faf06a80 0000000000000004
Jan 11 06:42:49 pampa kernel: sr0-3 0000000000d28480 0000000000d28480 0000000000000000 0000000000d28480
Jan 11 06:42:49 pampa kernel: sr4-7 0000000000d28480 0000000000d28480 0000000000d28480 0000000000d28480
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: IASQ: 0000000000d28480 0000000000d28480 IAOQ: 0000000040259043 0000000040259047
Jan 11 06:42:49 pampa kernel: IIR: 0f881094 ISR: 0000000000d28480 IOR: 000000004abfccfe
Jan 11 06:42:49 pampa kernel: CPU: 1 CR30: 0000000018f5c000 CR31: 0000000000008020
Jan 11 06:42:49 pampa kernel: ORIG_R28: 00000ab54abfccfa
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: do_page_fault() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 00000ab50a94d690 00000ab50a94d694 0000000000020dd4
Jan 11 06:42:49 pampa kernel: r28-31 00000ab54abfccfa 0000000040336584 00000000faf06a80 0000000000000004
Jan 11 06:42:49 pampa kernel: sr0-3 0000000000d28480 0000000000d28480 0000000000000000 0000000000d28480
Jan 11 06:42:49 pampa kernel: sr4-7 0000000000d28480 0000000000d28480 0000000000d28480 0000000000d28480
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: IASQ: 0000000000d28480 0000000000d28480 IAOQ: 0000000040259043 0000000040259047
Jan 11 06:42:49 pampa kernel: IIR: 0f881094 ISR: 0000000000d28480 IOR: 000000004abfccfe
Jan 11 06:42:49 pampa kernel: CPU: 1 CR30: 0000000018f5c000 CR31: 0000000000008020
Jan 11 06:42:49 pampa kernel: ORIG_R28: 00000ab54abfccfa
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: do_page_fault() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 00000ab50a94d690 00000ab50a94d694 0000000000020dd4
Jan 11 06:42:49 pampa kernel: r28-31 00000ab54abfccfa 0000000040336584 00000000faf06a80 0000000000000004
Jan 11 06:42:49 pampa kernel: sr0-3 0000000000d28480 0000000000d28480 0000000000000000 0000000000d28480
Jan 11 06:42:49 pampa kernel: sr4-7 0000000000d28480 0000000000d28480 0000000000d28480 0000000000d28480
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: IASQ: 0000000000d28480 0000000000d28480 IAOQ: 0000000040259043 0000000040259047
Jan 11 06:42:49 pampa kernel: IIR: 0f881094 ISR: 0000000000d28480 IOR: 000000004abfccfe
Jan 11 06:42:49 pampa kernel: CPU: 1 CR30: 0000000018f5c000 CR31: 0000000000008020
Jan 11 06:42:49 pampa kernel: ORIG_R28: 00000ab54abfccfa
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 9:16 [parisc-linux] running gcc testsuite triggers ongoing page faults Matthias Klose
@ 2004-01-11 10:08 ` Randolph Chung
2004-01-11 11:39 ` Matthias Klose
2004-01-11 11:39 ` Matthias Klose
2004-01-11 10:08 ` Randolph Chung
` (2 subsequent siblings)
3 siblings, 2 replies; 10+ messages in thread
From: Randolph Chung @ 2004-01-11 10:08 UTC (permalink / raw)
To: Matthias Klose; +Cc: parisc-linux, debian-hppa
In reference to a message from Matthias Klose, dated Jan 11:
> I think I did see this first with gcc-3.3 from 20031229. Running the
> 3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
> all CPU time, together with syslogd and klogd. /var get's filled with
> log messages in kern.log, syslog and debug.
>
> The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
jda sees this problem too, but we haven't been able to isolate it. if
you can find out which test case causes this we might be able to figure
it out.
also it appears that when running a UP kernel this doesn't happen.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 9:16 [parisc-linux] running gcc testsuite triggers ongoing page faults Matthias Klose
2004-01-11 10:08 ` Randolph Chung
@ 2004-01-11 10:08 ` Randolph Chung
2004-01-11 20:49 ` John David Anglin
2004-01-11 20:49 ` John David Anglin
3 siblings, 0 replies; 10+ messages in thread
From: Randolph Chung @ 2004-01-11 10:08 UTC (permalink / raw)
To: Matthias Klose; +Cc: parisc-linux, debian-hppa
In reference to a message from Matthias Klose, dated Jan 11:
> I think I did see this first with gcc-3.3 from 20031229. Running the
> 3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
> all CPU time, together with syslogd and klogd. /var get's filled with
> log messages in kern.log, syslog and debug.
>
> The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
jda sees this problem too, but we haven't been able to isolate it. if
you can find out which test case causes this we might be able to figure
it out.
also it appears that when running a UP kernel this doesn't happen.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 10:08 ` Randolph Chung
2004-01-11 11:39 ` Matthias Klose
@ 2004-01-11 11:39 ` Matthias Klose
2004-01-11 14:25 ` Randolph Chung
2004-01-11 14:25 ` Randolph Chung
1 sibling, 2 replies; 10+ messages in thread
From: Matthias Klose @ 2004-01-11 11:39 UTC (permalink / raw)
To: Randolph Chung; +Cc: parisc-linux, debian-hppa
Randolph Chung writes:
> In reference to a message from Matthias Klose, dated Jan 11:
> > I think I did see this first with gcc-3.3 from 20031229. Running the
> > 3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
> > all CPU time, together with syslogd and klogd. /var get's filled with
> > log messages in kern.log, syslog and debug.
> >
> > The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
>
> jda sees this problem too, but we haven't been able to isolate it. if
> you can find out which test case causes this we might be able to figure
> it out.
well, the last testcase logged in build/gcc/testsuite/gcc.log is
gcc.c-torture/execute/931004-12.c compilation, -O1
the next one would be
gcc.c-torture/execute/931004-12.c compilation, -O2
> also it appears that when running a UP kernel this doesn't happen.
>
> randolph
> --
> Randolph Chung
> Debian GNU/Linux Developer, hppa/ia64 ports
> http://www.tausq.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 10:08 ` Randolph Chung
@ 2004-01-11 11:39 ` Matthias Klose
2004-01-11 11:39 ` Matthias Klose
1 sibling, 0 replies; 10+ messages in thread
From: Matthias Klose @ 2004-01-11 11:39 UTC (permalink / raw)
To: Randolph Chung; +Cc: parisc-linux, debian-hppa
Randolph Chung writes:
> In reference to a message from Matthias Klose, dated Jan 11:
> > I think I did see this first with gcc-3.3 from 20031229. Running the
> > 3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
> > all CPU time, together with syslogd and klogd. /var get's filled with
> > log messages in kern.log, syslog and debug.
> >
> > The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
>
> jda sees this problem too, but we haven't been able to isolate it. if
> you can find out which test case causes this we might be able to figure
> it out.
well, the last testcase logged in build/gcc/testsuite/gcc.log is
gcc.c-torture/execute/931004-12.c compilation, -O1
the next one would be
gcc.c-torture/execute/931004-12.c compilation, -O2
> also it appears that when running a UP kernel this doesn't happen.
>
> randolph
> --
> Randolph Chung
> Debian GNU/Linux Developer, hppa/ia64 ports
> http://www.tausq.org/
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 11:39 ` Matthias Klose
@ 2004-01-11 14:25 ` Randolph Chung
2004-01-11 14:25 ` Randolph Chung
1 sibling, 0 replies; 10+ messages in thread
From: Randolph Chung @ 2004-01-11 14:25 UTC (permalink / raw)
To: Matthias Klose; +Cc: parisc-linux, debian-hppa
> well, the last testcase logged in build/gcc/testsuite/gcc.log is
>
> gcc.c-torture/execute/931004-12.c compilation, -O1
>
> the next one would be
>
> gcc.c-torture/execute/931004-12.c compilation, -O2
does it always die at the same test case?
randolph
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 11:39 ` Matthias Klose
2004-01-11 14:25 ` Randolph Chung
@ 2004-01-11 14:25 ` Randolph Chung
1 sibling, 0 replies; 10+ messages in thread
From: Randolph Chung @ 2004-01-11 14:25 UTC (permalink / raw)
To: Matthias Klose; +Cc: parisc-linux, debian-hppa
> well, the last testcase logged in build/gcc/testsuite/gcc.log is
>
> gcc.c-torture/execute/931004-12.c compilation, -O1
>
> the next one would be
>
> gcc.c-torture/execute/931004-12.c compilation, -O2
does it always die at the same test case?
randolph
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 9:16 [parisc-linux] running gcc testsuite triggers ongoing page faults Matthias Klose
` (2 preceding siblings ...)
2004-01-11 20:49 ` John David Anglin
@ 2004-01-11 20:49 ` John David Anglin
3 siblings, 0 replies; 10+ messages in thread
From: John David Anglin @ 2004-01-11 20:49 UTC (permalink / raw)
To: Matthias Klose; +Cc: parisc-linux, debian-hppa
> I think I did see this first with gcc-3.3 from 20031229. Running the
> 3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
> all CPU time, together with syslogd and klogd. /var get's filled with
> log messages in kern.log, syslog and debug.
>
> The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
I've had similar problems on gsyprf11, but recent kernels seem to be
better. I believe that this is more likely on SMP kernels and we have
never had a stable one on gsyprf11. You can kill expect and GCC will
move on to the next suite. I haven't seen this on the C3750.
This definitely isn't a GCC problem. The problem never occurs under
hpux. It's probably some kind of timing or locking issue that just
happens to get tweaked by a particular test.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
2004-01-11 9:16 [parisc-linux] running gcc testsuite triggers ongoing page faults Matthias Klose
2004-01-11 10:08 ` Randolph Chung
2004-01-11 10:08 ` Randolph Chung
@ 2004-01-11 20:49 ` John David Anglin
2004-01-11 20:49 ` John David Anglin
3 siblings, 0 replies; 10+ messages in thread
From: John David Anglin @ 2004-01-11 20:49 UTC (permalink / raw)
To: Matthias Klose; +Cc: parisc-linux, debian-hppa
> I think I did see this first with gcc-3.3 from 20031229. Running the
> 3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
> all CPU time, together with syslogd and klogd. /var get's filled with
> log messages in kern.log, syslog and debug.
>
> The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
I've had similar problems on gsyprf11, but recent kernels seem to be
better. I believe that this is more likely on SMP kernels and we have
never had a stable one on gsyprf11. You can kill expect and GCC will
move on to the next suite. I haven't seen this on the C3750.
This definitely isn't a GCC problem. The problem never occurs under
hpux. It's probably some kind of timing or locking issue that just
happens to get tweaked by a particular test.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
^ permalink raw reply [flat|nested] 10+ messages in thread
* [parisc-linux] running gcc testsuite triggers ongoing page faults
@ 2004-01-11 9:16 Matthias Klose
0 siblings, 0 replies; 10+ messages in thread
From: Matthias Klose @ 2004-01-11 9:16 UTC (permalink / raw)
To: parisc-linux, debian-hppa
I think I did see this first with gcc-3.3 from 20031229. Running the
3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
all CPU time, together with syslogd and klogd. /var get's filled with
log messages in kern.log, syslog and debug.
The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)
Jan 11 06:42:49 pampa kernel: do_page_fault() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 000lt() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 00000ab50a94d690 00000ab50a94d694 0000000000020dd4
Jan 11 06:42:49 pampa kernel: r28-31 00000ab54abfccfa 0000000040336584 00000000faf06a80 0000000000000004
Jan 11 06:42:49 pampa kernel: sr0-3 0000000000d28480 0000000000d28480 0000000000000000 0000000000d28480
Jan 11 06:42:49 pampa kernel: sr4-7 0000000000d28480 0000000000d28480 0000000000d28480 0000000000d28480
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: IASQ: 0000000000d28480 0000000000d28480 IAOQ: 0000000040259043 0000000040259047
Jan 11 06:42:49 pampa kernel: IIR: 0f881094 ISR: 0000000000d28480 IOR: 000000004abfccfe
Jan 11 06:42:49 pampa kernel: CPU: 1 CR30: 0000000018f5c000 CR31: 0000000000008020
Jan 11 06:42:49 pampa kernel: ORIG_R28: 00000ab54abfccfa
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: do_page_fault() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 00000ab50a94d690 00000ab50a94d694 0000000000020dd4
Jan 11 06:42:49 pampa kernel: r28-31 00000ab54abfccfa 0000000040336584 00000000faf06a80 0000000000000004
Jan 11 06:42:49 pampa kernel: sr0-3 0000000000d28480 0000000000d28480 0000000000000000 0000000000d28480
Jan 11 06:42:49 pampa kernel: sr4-7 0000000000d28480 0000000000d28480 0000000000d28480 0000000000d28480
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: IASQ: 0000000000d28480 0000000000d28480 IAOQ: 0000000040259043 0000000040259047
Jan 11 06:42:49 pampa kernel: IIR: 0f881094 ISR: 0000000000d28480 IOR: 000000004abfccfe
Jan 11 06:42:49 pampa kernel: CPU: 1 CR30: 0000000018f5c000 CR31: 0000000000008020
Jan 11 06:42:49 pampa kernel: ORIG_R28: 00000ab54abfccfa
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: do_page_fault() pid=13367 command='expect' type=15 address=0x4abfccfe
Jan 11 06:42:49 pampa kernel: vm_start = 0x40353000, vm_end = 0x40355000
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
Jan 11 06:42:49 pampa kernel: PSW: 00000000000001001111111100001111 Not tainted
Jan 11 06:42:49 pampa kernel: r00-03 0000000000000000 0000000040336510 000000004033655c fffffffffffffffa
Jan 11 06:42:49 pampa kernel: r04-07 0000000040336570 0000000000001008 0000000000001002 0000000000000063
Jan 11 06:42:49 pampa kernel: r08-11 0000000000021148 0000000000207a8c 0000000000000006 0000000000005438
Jan 11 06:42:49 pampa kernel: r12-15 0000000040050a6c 0000000040050a78 0000000000021618 0000000000000001
Jan 11 06:42:49 pampa kernel: r16-19 0000000000000000 0000000000000001 0000000000000000 00000000403349c8
Jan 11 06:42:49 pampa kernel: r20-23 0000000000207bb8 00000ab50a94d694 00000000402af66a 00000000002067a8
Jan 11 06:42:49 pampa kernel: r24-27 00000000400a8ec2 00000ab50a94d690 00000ab50a94d694 0000000000020dd4
Jan 11 06:42:49 pampa kernel: r28-31 00000ab54abfccfa 0000000040336584 00000000faf06a80 0000000000000004
Jan 11 06:42:49 pampa kernel: sr0-3 0000000000d28480 0000000000d28480 0000000000000000 0000000000d28480
Jan 11 06:42:49 pampa kernel: sr4-7 0000000000d28480 0000000000d28480 0000000000d28480 0000000000d28480
Jan 11 06:42:49 pampa kernel:
Jan 11 06:42:49 pampa kernel: IASQ: 0000000000d28480 0000000000d28480 IAOQ: 0000000040259043 0000000040259047
Jan 11 06:42:49 pampa kernel: IIR: 0f881094 ISR: 0000000000d28480 IOR: 000000004abfccfe
Jan 11 06:42:49 pampa kernel: CPU: 1 CR30: 0000000018f5c000 CR31: 0000000000008020
Jan 11 06:42:49 pampa kernel: ORIG_R28: 00000ab54abfccfa
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2004-01-11 20:49 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-11 9:16 [parisc-linux] running gcc testsuite triggers ongoing page faults Matthias Klose
2004-01-11 10:08 ` Randolph Chung
2004-01-11 11:39 ` Matthias Klose
2004-01-11 11:39 ` Matthias Klose
2004-01-11 14:25 ` Randolph Chung
2004-01-11 14:25 ` Randolph Chung
2004-01-11 10:08 ` Randolph Chung
2004-01-11 20:49 ` John David Anglin
2004-01-11 20:49 ` John David Anglin
2004-01-11 9:16 Matthias Klose
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.