ia64 stable/10 r286316: hang at Entering /boot/kernel/kernel

[Anton Shterenlikht]

>From marcel at xcllnt.net Fri Aug 28 23:15:06 2015
>
>
>> On Aug 28, 2015, at 3:35 AM, Konstantin Belousov <kostikbel at gmail.com> =
>wrote:
>>=20
>> Might be, try the latest stable/10 kernel with the problematic =
>revision
>> r286316 reversed ?  This might add more points to the Marcel' note =
>about
>> some static relocation table processed early.
>
>I built a kernel off of revision 286315 and got this:
>
>	eris% objdump -R kernel | grep FPTR64LSB | wc -l
>	    5377
>
>We only reserve room for 4096 relocations, so we=E2=80=99re over
>as it is.
>
>A kernel off of revision 286316 gave me this:
>	eris% objdump -R kernel | grep FPTR64LSB | wc -l
>	    5377
>
>Same. Odd, but ok. It=E2=80=99s possible that the memory layout
>changed such that we now scribble over something that=E2=80=99s
>important.
>
>To be sure: Anton can you apply the following patch and
>tell me if it makes a difference. It doubles the space
>we set aside for relocations.
>
>Index: sys/ia64/ia64/locore.S
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>--- sys/ia64/ia64/locore.S	(revision 286316)
>+++ sys/ia64/ia64/locore.S	(working copy)
>@@ -357,5 +357,5 @@
> 	.align	16
> 	.global fptr_storage
> fptr_storage:
>-	.space	4096*16			// XXX
>+	.space	8192*16			// XXX
> fptr_storage_end:

So, 286316 boots ok without the patch if
I remove everything from /boot/loader.conf.

With the patch, and with 

kern.dfldsiz=536748032  # default soft limit for process data
kern.dflssiz=536748032  # default soft limit for stack
# hard limits
kern.maxdsiz=536748032  # hard limit for process data
kern.maxssiz=536748032  # hard limit for stack
kern.maxtsiz=536748032  # hard limit for text size

First time round I got:

da1: Command Queueing enabled
da1: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C)

Loader variables:

Manual root filesystem specification:
  <fstype>:<device> [options]
      Mount <device> using filesystem <fstype>
      and with the specified (optional) option list.

    eg. ufs:/dev/da0s1a
        zfs:tank
        cd9660:/dev/acd0 ro
          (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)

  ?               List valid disk boot devices
  .               Yield 1 second (for background tasks)
  <empty line>    Abort manual input

mountroot> 


And following an auto-reboot:

OK  boot -s
?[37m?[44mBooting...?[m
Entering /boot/kernel/kernel at 0x9ffc000000010500...


I'll do a few more tries now.

Anton