Problem running spin with hercules - s390x - Fedora mailing-lists

4 Aug 2009


      I am having the same problem running the spin from 
http://secondary.fedoraproject.org/pub/alt/spins/S390/ that I had 
previously with the current update of 17 Jul.
I tried the hercules snapshots of 2/10, 12/31 and 10/29.  The problem is 
due to an error with diag 224 causing the Fedora 11 kernel to crash, and 
panic when trying to getting ready to run init.  I pull the ivansoft 
snapshots of the above dates.  There was a change to the source on 10/29 
made by Ivan which seemed to be an attempt to fix something in the diag.
I tried 1 and 2 cpus, and when the fedora disk boots up, it has two 
linux kernels, and I tried all combinations in a matrix.
I would be interested if anyone can supply an exact hercules snapshot 
date that builds on the amd64, or x86 platforms, and runs this 
snapshot.  The only thing cited in any reports I have found cite a 
version based on an rpm, which does not trace back to the hercules 
source date pull, or a platform, again which does not track back to the 
hercules source.
To the hercules group, it would be nice if the actual source pull date 
was embedded somewhere and was available by a command, or in the 
banner.  Now that hercules uses SVN, the revision is unique and would 
track to a particular source as well. Currently it shows the build date, 
which is unfortunately the date I pulled and built the source, and does 
not uniquely identify when the source was pulled from SVN.  This 
identifier would more exactly track which source is needed have a 
particular set of symptoms.
An example of the traceback panic info I am seeing is below.  The exact 
numbers may be slightly different, but the hypfs is the same.
Thanks
Jim
Call 
Trace:                                                                    +
( <00000000006714f4>! hypfs_diag_init+0x34/0x1dc)
  <0000000000671428>! hypfs_init+0x48/0xe0
  <0000000000012106>! do_one_initcall+0x86/0x180
  <00000000006645b4>! kernel_init+0x3ec/0x460
  <000000000001c1d2>! kernel_thread_starter+0x6/0xc
  <000000000001c1cc>! kernel_thread_starter+0x0/0xc
Last Breaking-Event-Address:
  <0000000000035048>! diag204_get_buffer+0x134/0x138
Call Trace:
( <00000000fffbaec6>! 0xfffbaec6)
  <0000000000023e5e>! on_panic_notify+0x52/0x70
  <0000000000415708>! notifier_call_chain+0x48/0x9c
  <00000000004157ca>! atomic_notifier_call_chain+0x32/0x44
  <000000000040f4c6>! panic+0xd6/0x204
  <0000000000057070>! do_exit+0xa8/0x884
  <000000000001736c>! default_trap_handler+0x0/0x78
  <0000000000012d26>! do_no_context+0x132/0x13c
  <0000000000414854>! do_protection_exception+0x29c/0x378
  <000000000002908c>! sysc_return+0x0/0x8
  <000000000067150a>! hypfs_diag_init+0x4a/0x1dc
( <00000000006714f4>! hypfs_diag_init+0x34/0x1dc)
  <0000000000671428>! hypfs_init+0x48/0xe0
  <0000000000012106>! do_one_initcall+0x86/0x180
  <00000000006645b4>! kernel_init+0x3ec/0x460
  <000000000001c1d2>! kernel_thread_starter+0x6/0xc
  <000000000001c1cc>! kernel_thread_starter+0x0/0xc
Last Breaking-Event-Address:
  <0000000000023dd4>! stop_run+0xec/0x124
 <4>---  end trace 561bb236c8008520 !---