installing on rx2620

[Anton Shterenlikht]

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

At the same time VFP looks fine:

LEDs | LOCATOR | SYSTEM | POWER
-----------------------------------------------------------------------------
| OFF | ON GREEN | ON GREEN
-----------------------------------------------------------------------------
Status | System running normally.
-----------------------------------------------------------------------------


Now, what is really interesting is that if I try to install
over fibre, the installation passes "chunk 3" stage (where
the install onto a local disk hangs), but
on the console I see at that moment this LOR:

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:2
85
KDB: stack backtrace:
db_trace_self(0xe000000004130af0) at db_trace_self+0x20
db_trace_self_wrapper(0xe0000000046b6bd0) at db_trace_self_wrapper+0x70
kdb_backtrace(0xe000000004d6a470, 0xe0000000046e0280) at kdb_backtrace+0xc0
_witness_debugger(0x1, 0xe000000004bba030, 0xe0000000046e1b20, 0x999, 0xe0000000
04be2fc8) at _witness_debugger+0x60
witness_checkorder(0xe00000001197ae00, 0x9, 0xffffffffffffffff, 0x11d, 0x0) at w
itness_checkorder+0x12c0
_sx_xlock(0xe00000001197ae00, 0x0, 0xe000000004be2fc8, 0x11d) at _sx_xlock+0xc0
ufsdirhash_acquire(0xe000000011a565e8, 0xe00000001197ae00, 0xe000000004a7ecc0) a
t ufsdirhash_acquire+0x50
ufsdirhash_add(0xe000000011a565e8, 0xa0000000c5e73020, 0x810, 0xa0000000c5e72ff0
, 0xe000000004a86a20, 0xda1) at ufsdirhash_add+0x20
ufs_direnter(0xe000000011a5a5a0, 0xe000000011a66780, 0xa0000000c5e73020, 0xa0000
000c5e73378, 0x0) at ufs_direnter+0x10e0
ufs_makeinode(0xa0000000c5e73128, 0xe000000011a5a5a0, 0xa0000000c5e73350, 0xa000
0000c5

the best match I could find is this:
http://sources.zabbadoz.net/freebsd/lor/261.html

but the line numbers are quite different.


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)

On fs1 I've VMS bootable, fs2 must be the freebsd disk, but it's empty.
If I manually copy loader.efi from anothe ia64 box to fs2, I can't
then find a kernel.

will update

many thanks
anton

[Marcel Moolenaar]

Post by Anton Shterenlikht
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.
Extracting base into / directory...
no panic, no reboot, just sits there indefinitely

Can you break into the kernel debugger and run the following
commands:
ps
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...
*snip*

Post by Anton Shterenlikht
http://sources.zabbadoz.net/freebsd/lor/261.html

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

Post by Anton Shterenlikht
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
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.

Post by Anton Shterenlikht
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.

Post by Anton Shterenlikht
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:...

FYI,

[Anton Shterenlikht]

Post by Marcel Moolenaar

Post by Anton Shterenlikht
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.
Extracting base into / directory...
no panic, no reboot, just sits there indefinitely

Can you break into the kernel debugger and run the following
ps
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...

yes, the disks are old.. these are 17g seagate scsi disks.
If the problem is in disk fw, this might explain why I don't
get reboots on my main ia64 - there I've more modern 73g disks.

I'm not sure where to look, so here are some bits of info
I think might be useful:

fs0:\> info fw

FIRMWARE INFORMATION


System Firmware Revision: 4.29 [4748]
BMC Revision: 4.04
Management Processor Revision: E.03.32
Updatable EFI Drivers:
Floating-Point Software Assistance Handler: 00000118
LSI Logic Ultra320 SCSI Driver: 01050400
Broadcom Gigabit Ethernet Driver: 0007000A
SCSI Bus Driver: 00000021
SCSI Tape Driver: 00000020
Intel(R) PRO/1000 Ethernet Driver: 00002160
Usb Ohci Driver: 00000033
USB Bus Driver: 00000014
USB Bot Mass Storage Driver: 00000014
Generic USB Mass Storage Driver: 00000015

fs0:\>

fs0:\> devices
C T D
T Y C I
R P F A
L E G G #P #D #C Device Name
== = = = == == == =============================================================
0D R - - - 1 4 Acpi(HWP0002,0)
0E R - - - 1 4 Acpi(HWP0002,100)
0F R - - - 1 - Acpi(HWP0002,200)
10 R - - - 1 - Acpi(HWP0002,300)
11 R - - - 1 - Acpi(HWP0002,400)
12 R - - - 1 1 Acpi(HWP0002,600)
13 R - - - 1 3 Acpi(HWP0002,700)
17 D - - 1 2 - Usb Open Host Controller
18 D - - 1 2 - Usb Open Host Controller
19 D - - 1 - - Acpi(HWP0002,0)/Pci(1|2)
1A B X X 1 1 1 PCI IDE/ATAPI Controller
1B B X X 1 2 2 LSI Logic Ultra320 SCSI Controller
1C D X X 1 2 - LSI Logic Ultra320 SCSI Controller
1D B - - 1 1 1 Acpi(HWP0002,100)/Pci(2|0)
1E B - - 1 1 1 Acpi(HWP0002,100)/Pci(2|1)
20 B X X 1 2 1 PCI-X 2.0 4Gb Fibre Channel Port (Port 1)
21 D - - 1 - - Acpi(HWP0002,700)/Pci(1|0)
22 B - - 1 1 1 Acpi(HWP0002,700)/Pci(1|1)
23 D - - 1 2 - Acpi(HWP0002,700)/Pci(2|0)
33 D - - 1 - - Primary Standard Error Device
34 D - - 1 - - Primary Console Input Device
35 D - - 1 - - Primary Console Output Device
3A R - - - 1 1 Acpi(PNP0501,0)
3B B - - 1 1 1 16550 Serial UART
3C D - - 1 - - VT-100+ Serial Console
3D B - - 1 1 1 16550 Serial UART
3E B - - 1 5 3 VT-100+ Serial Console
50 B X X 1 2 1 DV-28E-C
51 D X X 1 1 - SEAGATE ST318452LC 2213
52 B X X 1 2 2 SEAGATE ST318452LC 2213
53 D - - 1 3 - Acpi(HWP0002,100)/Pci(2|0)/Mac(0013215B051C)
54 D - - 1 3 - Acpi(HWP0002,100)/Pci(2|1)/Mac(0013215B051D)
55 B X X 1 2 3 Acpi(HWP0002,600)/Pci(1|0)/Fibre(WWN500805F3000EC221,Lun2000000000000)
92 D - - 1 2 - FAT File System [FAT12] 20 MB
93 D - - 1 2 - FAT File System [FAT16] 511 MB
94 D - - 1 1 - Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part2,SigG0)
95 D - - 1 2 - FAT File System [FAT16] 125 MB
96 D - - 1 2 - FAT File System [FAT16] 292 MB
97 D - - 1 1 - Acpi(HWP0002,600)/Pci(1|0)/Fibre(WWN500805F3000EC221,Lun2000000000000)/HD(Part5,Sig0044C4A0-3543-11DC-81DF-AA000400FEFF)

fs0:\>

Handles 51 and 52 are the two disks

fs0:\> devtree
Device Tree
Ctrl[04]
Ctrl[06] VenHw(SysROM)
Ctrl[0D] Acpi(HWP0002,0)
Ctrl[17] Usb Open Host Controller
Ctrl[18] Usb Open Host Controller
Ctrl[19] Acpi(HWP0002,0)/Pci(1|2)
Ctrl[1A] PCI IDE/ATAPI Controller
Ctrl[50] DV-28E-C
Ctrl[92] FAT File System [FAT12] 20 MB
Ctrl[0E] Acpi(HWP0002,100)
Ctrl[1B] LSI Logic Ultra320 SCSI Controller
Ctrl[51] SEAGATE ST318452LC 2213
Ctrl[52] SEAGATE ST318452LC 2213
Ctrl[93] FAT File System [FAT16] 511 MB
Ctrl[94] Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun1,Lun0)/HD(Part2,SigG0)
Ctrl[1C] LSI Logic Ultra320 SCSI Controller
Ctrl[1D] Acpi(HWP0002,100)/Pci(2|0)
Ctrl[53] Acpi(HWP0002,100)/Pci(2|0)/Mac(0013215B051C)
Ctrl[1E] Acpi(HWP0002,100)/Pci(2|1)
Ctrl[54] Acpi(HWP0002,100)/Pci(2|1)/Mac(0013215B051D)
Ctrl[0F] Acpi(HWP0002,200)
Ctrl[10] Acpi(HWP0002,300)
Ctrl[11] Acpi(HWP0002,400)
Ctrl[12] Acpi(HWP0002,600)
Ctrl[20] PCI-X 2.0 4Gb Fibre Channel Port (Port 1)
Ctrl[55] Acpi(HWP0002,600)/Pci(1|0)/Fibre(WWN500805F3000EC221,Lun2000000000000)
Ctrl[95] FAT File System [FAT16] 125 MB
Ctrl[96] FAT File System [FAT16] 292 MB
Ctrl[97] Acpi(HWP0002,600)/Pci(1|0)/Fibre(WWN500805F3000EC221,Lun2000000000000)/HD(Part5,Sig0044C4A0-3543-11DC-81DF-AA000400FEFF)
Ctrl[13] Acpi(HWP0002,700)
Ctrl[21] Acpi(HWP0002,700)/Pci(1|0)
Ctrl[22] Acpi(HWP0002,700)/Pci(1|1)
Ctrl[3D] 16550 Serial UART
Ctrl[3E] VT-100+ Serial Console
Ctrl[34] Primary Console Input Device
Ctrl[35] Primary Console Output Device
Ctrl[33] Primary Standard Error Device
Ctrl[23] Acpi(HWP0002,700)/Pci(2|0)
Ctrl[3A] Acpi(PNP0501,0)
Ctrl[3B] 16550 Serial UART
Ctrl[3C] VT-100+ Serial Console
Ctrl[4E] VenHw(D65A6B8C-71E5-4DF0-A909-F0D2992B5AA9)

fs0:\>

Anyway, I see at
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=447331&swItem=ux-57970-1&prodNameId=441910&swEnvOID=54&swLang=13&taskId=135&mode=4&idx=0

that HP has EFI fw update images for SEAGATE ST318452LC. I'll go ahead and try
to reflash fw on these disks.

Maybe I should also upde fibre and scsi controller fw..

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

Post by Anton Shterenlikht
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.

Post by Anton Shterenlikht
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:...

wow.. that I didn't know. I need to check this out.

many thanks
anton

[Anton Shterenlikht]

Post by Marcel Moolenaar

Post by Anton Shterenlikht
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.
Extracting base into / directory...
no panic, no reboot, just sits there indefinitely

Can you break into the kernel debugger and run the following
ps
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...

I've tried, but failed so far:

fs0:\ia64\common-firmware\disks\PF_DIPFSC0208EFI\18> ode dfdutilu; update st318452l5

***************************************************************************
****** ******
****** Offline Diagnostic Environment ******
****** ******
****** (C) Copyright Hewlett-Packard Co 1993-2007 ******
****** All Rights Reserved ******
****** ******
****** HP shall not be liable for any damages resulting from the ******
****** use of this program. ******
****** ******
****** TC Version B.00.22 ******
****** SysLib Version B.00.11 ******
****** ******
***************************************************************************

Type HELP for command information.
EFI_CMD> ;DFDUTILU; UPDATE ST318452L5

***************************************************************************
****** ******
****** DFDUTILU ******
****** ******
****** Copyright (C) 2007 by Hewlett-Packard Company ******
****** All Rights Reserved ******
****** ******
****** HP shall not be liable for any damages resulting from the ******
****** use of this program. ******
****** ******
****** Version B.00.30 ******
****** ******
***************************************************************************

Type HELP for command information.
Looking for SCSI devices via LSI SPT device driver.....
Looking for SCSI devices via ExtSPT device driver.....
No device found from ExtSPT driver

The Shared Library <SLMOD.EFI> is loaded.
for Non-Cellular Sys
... <20> modules found

***************************************************************************
* HP Supported Disks Found *
***************************************************************************
Indx Path Product ID Bus Size Rev
--- ------------------- --------------------------------- ------ ------ ------
0 0/1/1/0.1.0
SCSI SEAGATE ST318452LC SCSI 18. GB 2213

^^^^^^^^^^^^^^^^^^^^^^^^
that's the one


1 0/5/1/0
PCI-X 2.0 4Gb Fibre Channel Port Port 1 Fibre N/A
2 0/5/1/0.8.0.ff.1.6.2000000000000
SCSI COMPAQ MSA1000 VOLUME Fibre 8.6 GB 4.32
3 0/5/1/0.8.0.ff.1.6.0
SCSI COMPAQ MSA1000 Fibre N/A 4.32
4 0/5/1/0.8.0.ff.1.6.3000000000000
SCSI COMPAQ MSA1000 VOLUME Fibre 131 MB 4.32
5 0/5/1/0.8.0.ff.1.6.4000000000000
SCSI COMPAQ MSA1000 VOLUME Fibre 107 GB 4.32
6 0/5/1/0.8.0.ff.1.6.5000000000000
SCSI COMPAQ MSA1000 VOLUME Fibre 21. GB 4.32

Legend:
Indx = Index number used for referencing the device
Rev = Firmware Revision of the device

Note: Due to different calculation methods used, the size
of the device shown is only a rough approximation.

Please wait while I search for all the firmware files.
Note: This may take a while if you are booting from tape.
...........................

***************************************************************************
* Firmware Files Found (not disks) *
***************************************************************************
File name Intended Product ID Rev. Size
----------------------------- -------------------------------- ------ --------
MAJ3182MC8 HP 18.2GMAJ3182MC disk drive HP08 233472
MAM318402 HP 18.2GMAM3184MC disk drive HP02 368640
MAN318407 HP 18.2GMAN3184MC disk drive HP07 399360
MAS3184NC4 HP 18.2GMAS3184NC disk drive HPC4 374784
Mx10k31811 HP 18.2GATLAS10K3_18_SCA disk drive HP11 377856
S37320718C3 HP 18 GST373207LC#18 disk drive HPC3 537600
ST318404L4 HP 18.2GST318404LC disk drive HP04 537600
ST318406L5 HP 18.2GST318406LC disk drive HP05 600064
ST318452L5 HP 18.2GST318452LC disk drive HP05 602112
^^^^^^^^^^ ^^^^^^^^^^^^^^^^
and that's the fw file for this disk

ST318453LC8 HP 18.2GST318453LC disk drive HPC8 627712
ST33675483 HP 18.2GST336754LC#18 disk drive HPC3 858112
ST373207LC182 HP 18.2GST373207LC#18 disk drive HPC2 858112
ST373455LC188 HP 18.2GST373455LC#18 disk drive HPC8 757760

Legend:
File name = name of the firmware file
Intended Product ID = firmware file's intended product name
Rev. = firmware Revision of the firmware file
Size = exact byte size of the firmware image
No HP 18.2GST318452LC disk drive disks were found to need updating on the system.
Aborting.

DFDUTILU>


So the fw update program confirms the disk is there,
but doesn't want to update the firmware. Either it's up to date,
or something else is going wrong. For the system firmware there
was an option to force reflash, even if it's up-to-date.
Not sure how to do it here.

many thanks
anton

[Marcel Moolenaar]

Post by Anton Shterenlikht
Indx Path Product ID Bus Size Rev
--- ------------------- --------------------------------- ------ ------ ------
0 0/1/1/0.1.0
SCSI SEAGATE ST318452LC SCSI 18. GB 2213
^^^^^^^^^^^^^^^^^^^^^^^^
that's the one

This is not a HP disk, so I'm sure it won't work...