1:40 a.m.
Peter Sylvester píše v Po 29. 06. 2009 v 00:32 +0200:
The bug about a hercules snapshot that I reported had been corrected
in a later snapshot.
but since sanpshot 5280 an EXTENDED_DIAG204 is enabled by default
and fedora doesn't like it. disabling in the feature header make fedora
work.
Is this what you see with EXTENDED_DIAG204 enabled?
08:28:58 CPU0000: SIGP Stop (05) CPU0001, PARM 0000000000000000: CC 0
08:28:58 Freeing initrd memory: 2604k freed
08:28:58 Unable to handle kernel pointer dereference at virtual kernel address 0000000000
08:28:58 013000
08:28:58 Oops: 0004 #1! SMP
08:28:58 Modules linked in:
08:28:58 CPU: 0 Not tainted 2.6.29.3-159.fc11.s390x #1
08:28:58 Process swapper (pid: 1, task: 000000007fe98000, ksp: 000000007fe97940)
08:28:58 Krnl PSW : 0704d00180000000 000000000067150a (hypfs_diag_init+0x4a/0x1dc)
08:28:58 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 EA:3
08:28:58 Krnl GPRS: 0000000000010007 0000000000000001 000003e000013000 000003e000000002
08:28:58 0000000000035002 00000000006714f4 ffffffffffffffff 0000000000000000
08:28:58 0000000000000040 00000000006598b8 0000000000000000 000000007fe97d50
08:28:58 0000000000696d00 000000000041aff8 00000000006714f4 000000007fe97d50
08:28:58 Krnl Code: 00000000006714fa: a7240035 brc 2,671564
08:28:58 00000000006714fe: e300d0080004 lg %r0,8(%r13)
08:28:58 0000000000671504: e310b0a40014 lgf %r1,164(%r11)
08:28:58 >000000000067150a: 83200204 diag %r2,%r0,516
08:28:58 000000000067150e: b9020000 ltgr %r0,%r0
08:28:58 0000000000671512: a7740005 brc 7,67151c
08:28:58 0000000000671516: 1211 ltr %r1,%r1
08:28:58 0000000000671518: a7a40011 brc 10,67153a
08:28:58 Call Trace:
08:28:58 ( <00000000006714f4>! hypfs_diag_init+0x34/0x1dc)
08:28:58 <0000000000671428>! hypfs_init+0x48/0xe0
08:28:58 <0000000000012106>! do_one_initcall+0x86/0x180
08:28:58 <00000000006645b4>! kernel_init+0x3ec/0x460
08:28:58 <000000000001c1d2>! kernel_thread_starter+0x6/0xc
08:28:58 <000000000001c1cc>! kernel_thread_starter+0x0/0xc
08:28:58 Last Breaking-Event-Address:
08:28:58 <0000000000035048>! diag204_get_buffer+0x134/0x138
08:28:58 <4>--- end trace 561bb236c800851f !---
08:28:58 Kernel panic - not syncing: Attempted to kill init
08:28:58
08:28:58 HHCCP014I CPU0000: Operation exception CODE=0001 ILC=2
08:28:58 CPU0000: PSW=00000000 00000000 0000000000000002 INST=0000 ????? ,
?
08:28:58 CPU0000: R0=0000000000000000 R1=0000000000001000
08:28:58 CPU0000: R2=000000007FE97948 R3=0000000000000000
08:28:58 CPU0000: R4=00000000006AA62E R5=0000000000000001
08:28:58 CPU0000: R6=0000000000000000 R7=0000000000000000
08:28:58 CPU0000: R8=0000000000000020 R9=00000000006AA62E
08:28:58 CPU0000: RA=0000000000000000 RB=000000007FE97898
08:28:58 CPU0000: RC=0000000000000000 RD=0000000000419608
08:28:58 CPU0000: RE=0000000000023E5E RF=000000007FE97898
08:28:58 <0>------------ cut here !------------
08:28:58 Kernel BUG at 0000000000000002 verbose debug info unavailable!
08:28:58 illegal operation: 0001 #2! SMP
08:28:58 Modules linked in:
08:28:58 CPU: 0 Tainted: G D 2.6.29.3-159.fc11.s390x #1
08:28:58 Process swapper (pid: 1, task: 000000007fe98000, ksp: 000000007fe97940)
08:28:58 Krnl PSW : (null) 0000000000000002 (0x2)
08:28:58 R:0 T:0 IO:0 EX:0 Key:0 M:0 W:0 P:0 AS:0 CC:0 PM:0 EA:0
08:28:58 Krnl GPRS: 0000000000000000 0000000000001000 000000007fe97948 0000000000000000
08:28:58 00000000006aa62e 0000000000000001 0000000000000000 0000000000000000
08:28:58 0000000000000020 00000000006aa62e 0000000000000000 000000007fe97898
08:28:58 0000000000000000 0000000000419608 0000000000023e5e 000000007fe97898
08:28:58 Krnl Code:>0000000000000002: 0000 unknown
08:28:58 0000000000000004: 0000 unknown
08:28:58 0000000000000006: 0000 unknown
08:28:58 0000000000000008: 0000 unknown
08:28:58 000000000000000a: 0000 unknown
08:28:58 000000000000000c: 0000 unknown
08:28:58 000000000000000e: 0000 unknown
08:28:58 0000000000000010: 0000 unknown
08:28:58 Call Trace:
08:28:58 ( <00000000fffb9a80>! 0xfffb9a80)
08:28:58 <0000000000023e5e>! on_panic_notify+0x52/0x70
08:28:58 <0000000000414eb0>! notifier_call_chain+0x48/0x9c
08:28:58 <0000000000414f72>! atomic_notifier_call_chain+0x32/0x44
08:28:58 <000000000040ec6e>! panic+0xd6/0x204
08:28:58 <0000000000056f5c>! do_exit+0xa8/0x944
08:28:58 <000000000001736c>! default_trap_handler+0x0/0x78
08:28:58 <0000000000012d26>! do_no_context+0x132/0x13c
08:28:58 <0000000000413ffc>! do_protection_exception+0x29c/0x378
08:28:58 <000000000002908c>! sysc_return+0x0/0x8
08:28:58 <000000000067150a>! hypfs_diag_init+0x4a/0x1dc
08:28:58 ( <00000000006714f4>! hypfs_diag_init+0x34/0x1dc)
08:28:58 <0000000000671428>! hypfs_init+0x48/0xe0
08:28:58 <0000000000012106>! do_one_initcall+0x86/0x180
08:28:58 <00000000006645b4>! kernel_init+0x3ec/0x460
08:28:58 <000000000001c1d2>! kernel_thread_starter+0x6/0xc
08:28:58 <000000000001c1cc>! kernel_thread_starter+0x0/0xc
08:28:58 Last Breaking-Event-Address:
08:28:58 <0000000000023dd4>! stop_run+0xec/0x124
08:28:58 <4>--- end trace 561bb236c8008520 !---
08:28:58 Fixing recursive fault but reboot is needed
It could be bug in the DIAG204 implementation in Hercules or a real bug
in the kernel. I will recheck it with the latest kernel from the
development version of Fedora.
Dan