installing on rx2620

Marcel Moolenaar xcllnt at
Thu Feb 11 18:19:43 UTC 2010

On Feb 11, 2010, at 6:19 AM, Anton Shterenlikht wrote:

> Marcel
> Here are some observations regarding installing on rx2620,
> more precisely, the difference between installing on a local
> disk and on a fibre disk. In both cases mpt(4) is used.
> When installing on a local 17G disk, I get stopped at:
> 	Extracting base into / directory... 
> 	4170752 bytes read from base dist, chunk  3 of 59 @ 1390.2 KBytes/sec.
> no panic, no reboot, just sits there indefinitely

Can you break into the kernel debugger and run the following
	show alllocks
	show intrcnt

BTW: I've had weird behaviour that got resolved for the most part
by doing a firmware update, including the firmware on the harddisk
itself. Can you list all the firmware versions for me, including
the harddisk's. I want to check if there are any updates...

Also: this may be related to the spontaneous reboots we're seeing
during package build...

> lock order reversal:
> 1st 0xa00000007d58cc18 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559
> 2nd 0xe00000001197ae00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285
> the best match I could find is this:

I wouldn't worry about LORs at this time. As far as I know
they're harmless enough...

> Finally, when I install on a disk via fibre, and
> all was fine, no problems, I cannot find a bootable
> partition on the disk. Below is an extract from
> EFI map:
> Device mapping table
>  fs0  : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part1,Sig79A0351D-DB3C-11
> DE-8F43-00110A31E60A)
>  fs1  : Acpi(HWP0002,600)/Pci(1|0)/Fibre(WWN500805F3000EC221,Lun2000000000000)/
> HD(Part1,Sig0044C4A1-3543-11DC-81DF-AA000400FEFF)
>  fs2  : Acpi(HWP0002,600)/Pci(1|0)/Fibre(WWN500805F3000EC221,Lun2000000000000)/
> HD(Part4,Sig0044C4A0-3543-11DC-81E0-AA000400FEFF)

You seem to be having multiple EFI system partitions on the Fibre
disk. There can be only one.

> On fs1 I've VMS bootable, fs2 must be the freebsd disk, but it's empty.

That's not how it works. fs1: is the EFI system partition on the
fibre disk. It should contain the VMS and FreeBSD loaders.

> If I manually copy loader.efi from anothe ia64 box to fs2, I can't
> then find a kernel.

You need to pass -dev part<X>: to the loader, where <X> is the right
partition number.

Put differently: you need to tell the loader which partition is the
FreeBSD partition you want to boot. For backward compatibility it'll
use the partition from which the loader itself was loaded (i.e. fs2
in your case), but if you used sysinstall, the kernel is most likely
on fs1:...


Marcel Moolenaar
xcllnt at

More information about the freebsd-ia64 mailing list