Lets open the IA64 lane. Who has one?
#11
RE: Lets open the IA64 lane. Who has one?
(01-22-2019, 06:39 PM)bjornl Wrote:  Also, if someone remembers which OEM drivesleds that also fits in a Prism/Altix (/Origin300?) I would like to know. I think it was some IBM or Intel drivesled.

Those drive sleds are the same as the ones used in some older servers / server barebones from Intel, see that copy of the old Nekochan wiki page about the Altix 350 for details.

Indigo Indy Indigo2 IMPACT O2 Octane Octane2 Origin 200 = Origin 200 - Origin 200 = Origin 200


johnnym
Octane

Posts: 60
Threads: 3
Joined: Jun 2018
Find Reply
01-22-2019, 08:06 PM
#12
RE: Lets open the IA64 lane. Who has one?
The last two weeks i tried various things with the prism to get linux up and running (Thanks to johnnym), and i'd like to let you know.

AFAIK the best kernel to run on it are the 2.4 or 2.6 versions, they work pretty flawless. A choice of OS would be Debian 6.0, or gentoo.

In 2015 i already tried to get gentoo 2007 or 2008 running, but my compiled kernel failed to load and i gave up. I put back the disk i used back then in the prism, recompiled the kernel, and got it running. First step was kernel 2.4 which works. Then i upgraded to 2.6.something, which also works good. Besides that i have an up-to-date system, besides the kernel. I can emerge all things and everything works as expected (besides X).

The next one i tried was 3.4.49, which also runs great.

Next try: 3.19.19. Compiles, boots and runs. But i have a strange problem with it and can't figure out whats the matter: After booting the machine runs good for around 10 seconds. Then the cursor stops blinking and just stands still. If i press something on the keyboard, it seems the machine recovers, and i get 10x the key i pressed on the prompt. This also affects ssh sessions. I log in, type a command, i get output, then the machine hangs. It hangs exactly as long until i press a button on the keyboard attached to the machine. Then all commands are shown and executed in the ssh session i typed before. After some seconds the same thing happens and it freezes again.
I can't figure out what the matter is. I think i set nearly the same options in the kernel config.



Next step was 4.14. Boots up, but can't enable devices. I get the error -22 after every device (Sorry for the long output)
Every 4.x kernel has this issue (Tried 4.17 and 4.19)
Code:
ELILO v3.16 for EFI/IA-64
..
Uncompressing Linux... done
Loading file initrd.img-4.14.83-gentoo...done
Linux version 4.14.83-gentoo ([email protected]) (gcc version 7.3.0 (Gentoo 7.3.0-r3 p1.4)) #1 SMP Thu Dec 6 21:51:12 CET 8
EFI v1.10 by INTEL:
efi:  SALsystab=0x3002a08df0  ACPI 2.0=0x3002a095e0  HCDP=0x31efead110
booting generic kernel on platform sn2
console [sn_sal0] enabled
PCDP: v3 at 0x31efead110
Explicit "console="; ignoring PCDP
ACPI: Early table checksum verification disabled
ACPI: RSDP 0x0000003002A095E0 000024 (v02 SGI   )
ACPI: XSDT 0x0000003002A09620 000044 (v01 SGI    XSDTSN2  00010001 ?    00000001)
ACPI: APIC 0x0000003002A09680 000044 (v01 SGI    APICSN2  00010001 ?    00000001)
ACPI: SRAT 0x0000003002A096E0 000078 (v01 SGI    SRATSN2  00010001 ?    00000001)
ACPI: SLIT 0x0000003002A09770 00002D (v01 SGI    SLITSN2  00010001 ?    00000001)
ACPI: FACP 0x0000003002A09840 0000F4 (v03 SGI    FACPSN2  00030001 ?    00000001)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 0, using default 32 (20170728/tbfadt-708)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 0, using default 16 (20170728/tbfadt-708)
ACPI BIOS Warning (bug): Invalid length for FADT/PmTimerBlock: 0, using default 32 (20170728/tbfadt-708)
ACPI: DSDT 0x0000003002A09800 000024 (v02 SGI    DSDTSN2  00020001 ?    00000001)
ACPI: FACS 0x0000003002A097B0 000040
ACPI: Local APIC address c0000000fee00000
2 CPUs available, 2 CPUs total
Number of logical nodes in system = 1
Number of memory chunks in system = 1
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Initial ramdisk at: 0xe0000031eccde000 (6990475 bytes)
SAL 3.2: SGI SN2 version 4.65
SAL Platform features:
ITC_Drift

SAL: AP wakeup using external interrupt vector 0x12
Increasing MCA rendezvous timeout from 20000 to 49000 milliseconds
MCA related initialization done
ACPI: Early table checksum verification disabled
ACPI: RSDP 0x0000003002A095E0 000024 (v02 SGI   )
ACPI: XSDT 0x0000003002A09620 000044 (v01 SGI    XSDTSN2  00010001 ?    00000001)
ACPI: APIC 0x0000003002A09680 000044 (v01 SGI    APICSN2  00010001 ?    00000001)
ACPI: SRAT 0x0000003002A096E0 000078 (v01 SGI    SRATSN2  00010001 ?    00000001)
ACPI: SLIT 0x0000003002A09770 00002D (v01 SGI    SLITSN2  00010001 ?    00000001)
ACPI: FACP 0x0000003002A09840 0000F4 (v03 SGI    FACPSN2  00030001 ?    00000001)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 0, using default 32 (20170728/tbfadt-708)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 0, using default 16 (20170728/tbfadt-708)
ACPI BIOS Warning (bug): Invalid length for FADT/PmTimerBlock: 0, using default 32 (20170728/tbfadt-708)
ACPI: DSDT 0x0000003002A09800 000024 (v02 SGI    DSDTSN2  00020001 ?    00000001)
ACPI: FACS 0x0000003002A097B0 000040
SGI SAL version 4.65
clocksource: sn2_rtc: mask: 0x7fffffffffffff max_cycles: 0x49cd42e20, max_idle_ns: 440795202120 ns
Virtual mem_map starts at 0xa0007fffd4400000
Zone ranges:
 DMA      [mem 0x0000003003000000-0x0003ffffffffffff]
 Normal   empty
Movable zone start for each node
Early memory node ranges
 node   0: [mem 0x0000003003000000-0x00000031ee7fbfff]
 node   0: [mem 0x00000031ef800000-0x00000031efd57fff]
 node   0: [mem 0x00000031efd94000-0x00000031efe0ffff]
 node   0: [mem 0x00000031efe80000-0x00000031efe97fff]
Initmem setup node 0 [mem 0x0000003003000000-0x00000031efe97fff]
Built 1 zonelists, mobility grouping on.  Total pages: 501948
Policy zone: DMA
Kernel command line: BOOT_IMAGE=net0:vmlinuz-4.14.83-gentoo  root=/dev/nfs console=ttySG0 modprobe=sgiioc4 break=premout
PID hash table entries: 4096 (order: 1, 32768 bytes)
Sorting __ex_table...
Memory: 8000880K/8058784K available (13797K kernel code, 1169K rwdata, 1740K rodata, 1344K init, 1942K bss, 57904K rese)
Hierarchical RCU implementation.
       RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
NR_IRQS: 1024
ACPI: Local APIC address c0000000fee00000
register_intr: No IOSAPIC for GSI 52

clocksource: itc: mask: 0xffffffffffffffff max_cycles: 0x171024fa93b, max_idle_ns: 440795253189 ns
Console: colour VGA+ 80x25
console [ttySG0] enabled
console [ttySG0] enabled
console [sn_sal0] disabled
console [sn_sal0] disabled
Calibrating delay loop... 2390.01 BogoMIPS (lpj=4780032)
pid_max: default: 32768 minimum: 301
ACPI: Core revision 20170728
ACPI Exception: AE_NO_ACPI_TABLES, While loading namespace from ACPI tables (20170728/tbxfload-103)
ACPI: Unable to load the System Description Tables
Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes)
Mount-cache hash table entries: 16384 (order: 3, 131072 bytes)
Mountpoint-cache hash table entries: 16384 (order: 3, 131072 bytes)
Boot processor id 0x0/0x0
Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
Fixed BSP b0 value from CPU 1

smp: Brought up 1 node, 2 CPUs
Total of 2 processors activated (4780.03 BogoMIPS).
devtmpfs: initialized
random: get_random_u32 called from bucket_table_alloc+0x510/0x610 with crng_init=0
DMI not present or invalid.
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
futex hash table entries: 512 (order: 2, 65536 bytes)
NET: Registered protocol family 16
ACPI: bus type PCI registered
acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
ACPI  DSDT OEM Rev 0x20001
irq 54, desc: a000000101250e80, depth: 1, count: 0, unhandled: 0
irq 54, desc: a000000101250e80, depth: 1, count: 0, unhandled: 0
->handle_irq():  a00000010103bb40,
0xa00000010103bb40
->irq_data.chip(): a00000010132cd00,
0xa00000010132cd00
->action():           (null)
Unexpected irq vector 0x36 on CPU 0!
PCI host bridge to bus 0001:00
pci_bus 0001:00: root bus resource [io  0x0000-0xffff]
pci_bus 0001:00: root bus resource [mem 0x800000c1c0000000-0x800000c1c00fffff] (bus address [0x00000000-0x000fffff])
pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0001:00:01.0: can't claim BAR 0 [mem 0x00200000-0x002fffff]: no compatible bridge window
pci 0001:00:03.0: can't claim BAR 0 [mem 0x00300000-0x00300fff 64bit]: no compatible bridge window
pci 0001:00:04.0: can't claim BAR 0 [mem 0x00310000-0x0031ffff 64bit]: no compatible bridge window
pci 0001:00:02.0: PCI bridge to [bus 01]
pci 0001:00:02.0: can't claim BAR 8 [mem 0x00400000-0x004fffff]: no compatible bridge window
pci 0001:01:02.0: can't claim BAR 0 [mem 0x00400000-0x00400fff]: no compatible bridge window
pci 0001:01:02.1: can't claim BAR 0 [mem 0x00401000-0x00401fff]: no compatible bridge window
pci 0001:01:02.2: can't claim BAR 0 [mem 0x00402000-0x004020ff]: no compatible bridge window
PCI host bridge to bus 0002:00
pci_bus 0002:00: root bus resource [io  0x0000-0xffff]
pci_bus 0002:00: root bus resource [mem 0x00000000-0x000fffff]
pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
PCI host bridge to bus 0003:00
pci_bus 0003:00: root bus resource [io  0x8000004000600000-0x800000400060ffff] (bus address [0x0000-0xffff])
pci_bus 0003:00: root bus resource [mem 0x8000004000700000-0x80000040007fffff] (bus address [0x00000000-0x000fffff])
pci_bus 0003:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0003:00:02.0: can't claim BAR 0 [mem 0x00200000-0x0020ffff 64bit]: no compatible bridge window
PCI host bridge to bus 0004:00
pci_bus 0004:00: root bus resource [io  0x8000004010200000-0x800000401020ffff] (bus address [0x0000-0xffff])
pci_bus 0004:00: root bus resource [mem 0x8000004010600000-0x80000040106fffff] (bus address [0x00000000-0x000fffff])
pci_bus 0004:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0004:00:01.2: can't claim BAR 0 [mem 0x00200000-0x002000ff]: no compatible bridge window
PCI host bridge to bus 0005:00
pci_bus 0005:00: root bus resource [io  0x0000-0xffff]
pci_bus 0005:00: root bus resource [mem 0x00000000-0x000fffff]
pci_bus 0005:00: No busn resource found for root bus, will use [bus 00-ff]
PCI host bridge to bus 0006:00
pci_bus 0006:00: root bus resource [io  0x800000c023000000-0x800000c02300ffff] (bus address [0x0000-0xffff])
pci_bus 0006:00: root bus resource [mem 0x800000c028000000-0x800000c0280fffff] (bus address [0x00000000-0x000fffff])
pci_bus 0006:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0006:00:00.0: can't claim BAR 0 [mem 0x08000000-0x0fffffff pref]: no compatible bridge window
pci 0006:00:00.0: can't claim BAR 2 [mem 0x00100000-0x0010ffff]: no compatible bridge window
pci 0006:00:00.0: can't claim BAR 6 [mem 0x00120000-0x0013ffff pref]: no compatible bridge window
pci 0006:00:00.1: can't claim BAR 0 [mem 0x10000000-0x17ffffff pref]: no compatible bridge window
pci 0006:00:00.1: can't claim BAR 1 [mem 0x00110000-0x0011ffff]: no compatible bridge window
->handle_irq():  a000000101042310,
0xa000000101042310
->irq_data.chip(): a00000010132cd00,
0xa00000010132cd00
->action(): e000003005ca2900
->action->handler(): a00000010105c350,
0xa00000010105c350
Unexpected irq vector 0x36 on CPU 1!
HugeTLB registered 256 MiB page size, pre-allocated 0 pages
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
random: fast init done
ACPI: SCI (ACPI GSI 52) not registered
ACPI: Interpreter enabled
ACPI: (supports S0)
ACPI: Using IOSAPIC for interrupt routing
pci 0006:00:00.0: vgaarb: setting as boot VGA device
pci 0006:00:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
pci 0006:00:00.0: vgaarb: bridge control possible
vgaarb: loaded
SCSI subsystem initialized
ACPI: bus type USB registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
PTP clock support registered
dmi: Firmware registration failed.
Registered efivars operations
clocksource: Switched to clocksource sn2_rtc
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 2048 (order 0, 16384 bytes)
pnp: PnP ACPI init
pnp: PnP ACPI: found 0 devices
NET: Registered protocol family 2
TCP established hash table entries: 65536 (order: 5, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
UDP hash table entries: 4096 (order: 3, 131072 bytes)
UDP-Lite hash table entries: 4096 (order: 3, 131072 bytes)
NET: Registered protocol family 1
pci 0001:00:02.0: can't enable device: BAR 8 [mem size 0x00100000] not assigned
pci 0001:00:02.0: Error enabling bridge (-22), continuing
pci 0001:01:02.0: can't enable device: BAR 0 [mem size 0x00001000] not assigned
pci 0001:01:02.0: Can't enable PCI device, BIOS handoff failed.
pci 0001:00:02.0: can't enable device: BAR 8 [mem size 0x00100000] not assigned
pci 0001:00:02.0: Error enabling bridge (-22), continuing
pci 0001:01:02.1: can't enable device: BAR 0 [mem size 0x00001000] not assigned
pci 0001:01:02.1: Can't enable PCI device, BIOS handoff failed.
pci 0001:00:02.0: can't enable device: BAR 8 [mem size 0x00100000] not assigned
pci 0001:00:02.0: Error enabling bridge (-22), continuing
pci 0001:01:02.2: can't enable device: BAR 0 [mem size 0x00000100] not assigned
pci 0001:01:02.2: Can't enable PCI device, BIOS handoff failed.
pci 0004:00:01.0: can't derive routing for PCI INT A
pci 0004:00:01.0: PCI INT A: no GSI
pci 0004:00:01.1: can't derive routing for PCI INT B
pci 0004:00:01.1: PCI INT B: no GSI
pci 0004:00:01.2: can't enable device: BAR 0 [mem size 0x00000100] not assigned
pci 0004:00:01.2: Can't enable PCI device, BIOS handoff failed.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 6816kB freed
perfmon: version 2.0 IRQ 238
perfmon: Itanium 2 PMU detected, 16 PMCs, 18 PMDs, 4 counters (47 bits)
PAL Information Facility v0.5
perfmon: added sampling format default_format
perfmon_default_smpl: default_format v2.0 registered
workingset: timestamp_bits=52 max_order=19 bucket_order=0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
SGI XFS with ACLs, security attributes, no debug enabled
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
io scheduler mq-deadline registered
io scheduler kyber registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
sn_console: Console driver init
ttySG0 at I/O 0x0 (irq = 0, base_baud = 0) is a SGI SN L1
EFI Time Services Driver v0.4
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
ACPI: Power Button [PWRF]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input1
ACPI: Sleep Button [SLPF]
brd: module loaded
loop: module loaded
IOC4 0001:00:01.0: can't enable device: BAR 0 [mem size 0x00100000] not assigned
ioc4_probe: Failed to enable IOC4 device for pci_dev 0001:00:01.0.
IOC4: probe of 0001:00:01.0 failed with error -22
rdac: device handler registered
hp_sw: device handler registered
emc: device handler registered
alua: device handler registered
Loading Adaptec I2O RAID: Version 2.4 Build 5go
Detecting Adaptec I2O RAID controllers...
sata_vsc 0001:00:03.0: can't enable device: BAR 0 [mem size 0x00001000 64bit] not assigned
sata_vsc: probe of 0001:00:03.0 failed with error -22
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Fusion MPT base driver 3.04.20
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.20
Fusion MPT FC Host driver 3.04.20
Fusion MPT SAS Host driver 3.04.20
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
pci 0001:00:02.0: can't enable device: BAR 8 [mem size 0x00100000] not assigned
pci 0001:00:02.0: Error enabling bridge (-22), continuing
ehci-pci 0001:01:02.2: can't enable device: BAR 0 [mem size 0x00000100] not assigned
ehci-pci 0004:00:01.2: can't enable device: BAR 0 [mem size 0x00000100] not assigned
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
pci 0001:00:02.0: can't enable device: BAR 8 [mem size 0x00100000] not assigned
pci 0001:00:02.0: Error enabling bridge (-22), continuing
ohci-pci 0001:01:02.0: can't enable device: BAR 0 [mem size 0x00001000] not assigned
pci 0001:00:02.0: can't enable device: BAR 8 [mem size 0x00100000] not assigned
pci 0001:00:02.0: Error enabling bridge (-22), continuing
ohci-pci 0001:01:02.1: can't enable device: BAR 0 [mem size 0x00001000] not assigned
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0004:00:01.0: can't derive routing for PCI INT A
uhci_hcd 0004:00:01.0: PCI INT A: no GSI
uhci_hcd 0004:00:01.0: UHCI Host Controller
uhci_hcd 0004:00:01.0: new USB bus registered, assigned bus number 1
salruntime_sn_intr_handler:  Invalid provider_call 3
salruntime_sn_intr_handler:  Invalid provider_call 3
uhci_hcd 0004:00:01.0: irq 63, io base 0x8000004010201000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
uhci_hcd 0004:00:01.1: can't derive routing for PCI INT B
uhci_hcd 0004:00:01.1: PCI INT B: no GSI
uhci_hcd 0004:00:01.1: UHCI Host Controller
uhci_hcd 0004:00:01.1: new USB bus registered, assigned bus number 2
salruntime_sn_intr_handler:  Invalid provider_call 3
uhci_hcd 0004:00:01.1: irq 64, io base 0x8000004010201020
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
mousedev: PS/2 mouse device common for all mice
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR Sharp protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR XMP protocol handler initialized
device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: [email protected]
EFI Variables Facility v0.08 2004-May-17
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Initializing XFRM netlink socket
NET: Registered protocol family 17
Freeing unused kernel memory: 1344K
This architecture does not have kernel memory protection.
Loading, please wait...
Starting version 240
usb 1-1: new low-speed USB device number 2 using uhci_hcd
tg3.c:v3.137 (May 11, 2014)
tg3 0001:00:04.0: can't enable device: BAR 0 [mem size 0x00010000 64bit] not assigned
tg3 0001:00:04.0: Cannot enable PCI device, aborting
tg3: probe of 0001:00:04.0 failed with error -22
tg3 0003:00:02.0: can't enable device: BAR 0 [mem size 0x00010000 64bit] not assigned
tg3 0003:00:02.0: Cannot enable PCI device, aborting
tg3: probe of 0003:00:02.0 failed with error -22
input: Chicony HP Elite USB Keyboard as /devices/pci0004:00/0004:00:01.0/usb1/1-1/1-1:1.0/0003:03F0:034A.0001/input/inp2
hid-generic 0003:03F0:034A.0001: input: USB HID v1.10 Keyboard [Chicony HP Elite USB Keyboard] on usb-0004:00:01.0-1/in0
input: Chicony HP Elite USB Keyboard as /devices/pci0004:00/0004:00:01.0/usb1/1-1/1-1:1.1/0003:03F0:034A.0002/input/inp3
hid-generic 0003:03F0:034A.0002: input: USB HID v1.10 Device [Chicony HP Elite USB Keyboard] on usb-0004:00:01.0-1/inpu1
Begin: Loading essential drivers ... done.
Spawning shell within the initramfs

No devices are available, no network, no nothing.


So i've chosen a kernel between 3.4 and 4.x, and my choice was 3.8.13.
Results in kernel panic at boot:

Code:
Loading: gentoo_ne
Starting: gentoo_ne
ELILO v3.12 for EFI/IA-64
..
Uncompressing Linux... done
Loading file \initramfs-genkernel-ia64-3.8.13-gentoo...done
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.8.13-gentoo ([email protected]) (gcc version 4.9.4 (Gentoo 4.9.4 p1.3, pie-0.6.4) ) #2 SMP Sun 9
[    0.000000] EFI v1.10 by INTEL: SALsystab=0x3002a08df0 ACPI 2.0=0x3002a095e0 HCDP=0x31efead110
[    0.000000] booting generic kernel on platform sn2
[    0.000000] console [sn_sal0] enabled
[    0.000000] PCDP: v3 at 0x31efead110
[    0.000000] Explicit "console="; ignoring PCDP
[    0.000000] ACPI: RSDP 0000003002a095e0 00024 (v02    SGI)
[    0.000000] ACPI: XSDT 0000003002a09620 00044 (v01    SGI  XSDTSN2 00010001    ? 00000001)
[    0.000000] ACPI: APIC 0000003002a09680 00044 (v01    SGI  APICSN2 00010001    ? 00000001)
[    0.000000] ACPI: SRAT 0000003002a096e0 00078 (v01    SGI  SRATSN2 00010001    ? 00000001)
[    0.000000] ACPI: SLIT 0000003002a09770 0002D (v01    SGI  SLITSN2 00010001    ? 00000001)
[    0.000000] ACPI: FACP 0000003002a09840 000F4 (v03    SGI  FACPSN2 00030001    ? 00000001)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Pm1aEventBlock: 32/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Pm1aControlBlock: 16/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/PmTimerBlock: 32/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Gpe0Block: 64/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: Invalid length for FADT/Pm1aEventBlock: 0, using default 32 (20121018/tbfadt-648)
[    0.000000] ACPI BIOS Bug: Warning: Invalid length for FADT/Pm1aControlBlock: 0, using default 16 (20121018/tbfadt-6)
[    0.000000] ACPI BIOS Bug: Warning: Invalid length for FADT/PmTimerBlock: 0, using default 32 (20121018/tbfadt-648)
[    0.000000] ACPI: DSDT 0000003002a09800 00024 (v02    SGI  DSDTSN2 00020001    ? 00000001)
[    0.000000] ACPI: FACS 0000003002a097b0 00040
[    0.000000] ACPI: Local APIC address c0000000fee00000
[    0.000000] 2 CPUs available, 2 CPUs total
[    0.000000] Number of logical nodes in system = 1
[    0.000000] Number of memory chunks in system = 1
[    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] Initial ramdisk at: 0xe0000031ee14c000 (2743660 bytes)
[    0.000000] SAL 3.2: SGI SN2 version 4.65
[    0.000000] SAL Platform features: ITC_Drift
[    0.000000] SAL: AP wakeup using external interrupt vector 0x12
[    0.000000] Increasing MCA rendezvous timeout from 20000 to 49000 milliseconds
[    0.000000] MCA related initialization done
[    0.000000] ACPI: RSDP 0000003002a095e0 00024 (v02    SGI)
[    0.000000] ACPI: XSDT 0000003002a09620 00044 (v01    SGI  XSDTSN2 00010001    ? 00000001)
[    0.000000] ACPI: APIC 0000003002a09680 00044 (v01    SGI  APICSN2 00010001    ? 00000001)
[    0.000000] ACPI: SRAT 0000003002a096e0 00078 (v01    SGI  SRATSN2 00010001    ? 00000001)
[    0.000000] ACPI: SLIT 0000003002a09770 0002D (v01    SGI  SLITSN2 00010001    ? 00000001)
[    0.000000] ACPI: FACP 0000003002a09840 000F4 (v03    SGI  FACPSN2 00030001    ? 00000001)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Pm1aEventBlock: 32/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Pm1aControlBlock: 16/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/PmTimerBlock: 32/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: 32/64X length mismatch in FADT/Gpe0Block: 64/0 (20121018/tbfadt-567)
[    0.000000] ACPI BIOS Bug: Warning: Invalid length for FADT/Pm1aEventBlock: 0, using default 32 (20121018/tbfadt-648)
[    0.000000] ACPI BIOS Bug: Warning: Invalid length for FADT/Pm1aControlBlock: 0, using default 16 (20121018/tbfadt-6)
[    0.000000] ACPI BIOS Bug: Warning: Invalid length for FADT/PmTimerBlock: 0, using default 32 (20121018/tbfadt-648)
[    0.000000] ACPI: DSDT 0000003002a09800 00024 (v02    SGI  DSDTSN2 00020001    ? 00000001)
[    0.000000] ACPI: FACS 0000003002a097b0 00040
[    0.000000] SGI SAL version 4.65
[    0.000000] Virtual mem_map starts at 0xa0007fffd4400000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x3003000000-0x3ffffffffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x3003000000-0x31ee7fbfff]
[    0.000000]   node   0: [mem 0x31ef800000-0x31efd57fff]
[    0.000000]   node   0: [mem 0x31efd94000-0x31efe0ffff]
[    0.000000]   node   0: [mem 0x31efe80000-0x31efe97fff]
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 501948
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: BOOT_IMAGE=dev001:/vmlinuz-3.8.13-gentoo  console=ttySG0 initramfs-genkernel-ia64-33
[    0.000000] PID hash table entries: 4096 (order: 1, 32768 bytes)
[    0.000000] Memory: 8007712k/8036752k available (13371k code, 51072k reserved, 5146k data, 896k init)
[    0.000000] SLUB: Genslabs=17, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=256
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  CONFIG_RCU_FANOUT set to non-default value of 32
[    0.000000]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2.
[    0.000000] NR_IRQS:1024
[    0.000000] ACPI: Local APIC address c0000000fee00000
[    0.000000] register_intr: No IOSAPIC for GSI 52
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [ttySG0] enabled
[    0.000000] console [ttySG0] enabled
[    0.008000] Calibrating delay loop... 2390.01 BogoMIPS (lpj=4780032)
[    0.016444] pid_max: default: 32768 minimum: 301
[    0.017452] Security Framework initialized
[    0.018618] Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes)
[    0.028180] Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes)
[    0.033878] Mount-cache hash table entries: 1024
[    0.035439] Initializing cgroup subsys cpuacct
[    0.036011] Initializing cgroup subsys devices
[    0.192009] Initializing cgroup subsys freezer
[    0.192863] ACPI: Core revision 20121018
[    0.193811] Boot processor id 0x0/0x0
[    0.004000] Fixed BSP b0 value from CPU 1
[    0.195907] Brought up 2 CPUs
[    0.196000] Total of 2 processors activated (4780.03 BogoMIPS).
[    0.201496] devtmpfs: initialized
[    0.222912] DMI not present or invalid.
[    0.222912] NET: Registered protocol family 16
[    0.222912] ACPI: bus type pci registered
[    0.222947] ACPI  DSDT OEM Rev 0x20001
[    0.226558] irq 54, desc: a00000010110c580, depth: 1, count: 0, unhandled: 0
[    0.224007] irq 54, desc: a00000010110c580, depth: 1, count: 0, unhandled: 0
[    0.224012] ->handle_irq():  a000000100f70020, 0xa000000100f70020
[    0.224014] ->irq_data.chip(): a0000001011c5d00, 0xa0000001011c5d00
[    0.224015] ->action():           (null)
[    0.224017] Unexpected irq vector 0x36 on CPU 0!
[    0.225857] PCI host bridge to bus 0001:00
[    0.225863] pci_bus 0001:00: root bus resource [io  0x0000-0xffff]
[    0.225868] pci_bus 0001:00: root bus resource [mem 0x800000c1c0000000-0x800000c1c00fffff] (bus address [0x00000000-)
[    0.225871] pci_bus 0001:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.225936] pci 0001:00:01.0: [10a9:100a] type 00 class 0x0b4000
[    0.226022] pci 0001:00:01.0: reg 10: [mem 0x00200000-0x002fffff]
[    0.226466] pci 0001:00:02.0: [104c:ac28] type 01 class 0x060400
[    0.227114] pci 0001:00:03.0: [1725:7174] type 00 class 0x010600
[    0.227256] pci 0001:00:03.0: reg 10: [mem 0x00300000-0x00300fff 64bit]
[    0.228257] pci 0001:00:04.0: [14e4:1645] type 00 class 0x020000
[    0.228400] pci 0001:00:04.0: reg 10: [mem 0x00310000-0x0031ffff 64bit]
[    0.229097] pci 0001:00:04.0: PME# supported from D3hot
[    0.229255] Unable to handle kernel NULL pointer dereference (address 0000000000000020)
[    0.229259] swapper/0[1]: Oops 11012296146944 [1]
[    0.229262] Modules linked in:
[    0.229263]
[    0.229263] Pid: 1, CPU 0, comm:            swapper/0
[    0.229267] psr : 00001210084a6018 ifs : 800000000000040b ip  : [<a000000100adb271>]    Not tainted (3.8.13-gentoo)
[    0.229278] ip is at sn_pci_fixup_slot+0x101/0x4e0
[    0.229279] unat: 0000000000000000 pfs : 000000000000040b rsc : 0000000000000003
[    0.229281] rnat: 0000003002483538 bsps: 0000003002483538 pr  : 0000000000029a89
[    0.229282] ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
[    0.229284] csd : 0000000000000000 ssd : 0000000000000000
[    0.229285] b0  : a000000100adb260 b6  : 00000000ffb2a230 b7  : a00000010082faf0
[    0.229287] f6  : 000000000000000000000 f7  : 1003e8888888888888889
[    0.229288] f8  : 1003e0000000000000000 f9  : 1003e0000000065e0c2f8
[    0.229289] f10 : 1003e0feb1e76c0000000 f11 : 1003e0000000000000000
[    0.229291] r1  : a00000010140d8c0 r2  : e000003004c85ca8 r3  : 0000000000000000
[    0.229293] r8  : 0000000000000000 r9  : e000003004c85ca0 r10 : 0000000000000000
[    0.229294] r11 : 0000000000000000 r12 : e00000300593fce0 r13 : e000003005938000
[    0.229295] r14 : 0000000000000010 r15 : e000003004c85ca0 r16 : 0000000000000000
[    0.229297] r17 : 0000000000000002 r18 : 0000000000000002 r19 : 0000000000000000
[    0.229298] r20 : e000003004c806a8 r21 : e000003004cba2f8 r22 : e000003004cba2b8
[    0.229300] r23 : e000003004cba2e8 r24 : e000003004cba2d0 r25 : 0000000000000020
[    0.229301] r26 : c00000c010000000 r27 : 0000000000004000 r28 : 0000000000000000
[    0.229303] r29 : 0000000000000001 r30 : 0000000000000018 r31 : 0000000000000b1e
[    0.229313]
[    0.229313] Call Trace:
[    0.229322]  [<a000000100013500>] show_stack+0x40/0x90
[    0.229322]                                 sp=e00000300593f8b0 bsp=e0000030059391b8
[    0.229325] Disabling lock debugging due to kernel taint
[    0.229345] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    0.229345]
[    0.228000] ->handle_irq():  a000000100f762c0, 0xa000000100f762c0
[    0.228000] ->irq_data.chip(): a0000001011c5d00, 0xa0000001011c5d00
[    0.228000] ->action(): e000003004cb9f00
[    0.228000] ->action->handler(): a000000100f93af0, 0xa000000100f93af0
[    0.228000] Unexpected irq vector 0x36 on CPU 1!


Conclusion: I stick to 3.4.49 for the moment, because i can't figure out what the problem with the other ones is.
And no, i didn't think about X for a second in the progress. I have the radeon driver included, and lspci also shows me a compatible device, but i even dont get a framebuffer console, so i think we're out of luck for X.
(This post was last modified: 01-27-2019, 03:18 PM by MrWeedster.)
MrWeedster
O2

Posts: 16
Threads: 2
Joined: Jan 2019
Find Reply
01-27-2019, 03:16 PM
#13
RE: Lets open the IA64 lane. Who has one?
(01-27-2019, 03:16 PM)MrWeedster Wrote:  The last two weeks i tried various things with the prism to get linux up and running (Thanks to johnnym), and i'd like to let you know.

AFAIK the best kernel to run on it are the 2.4 or 2.6 versions, they work pretty flawless. A choice of OS would be Debian 6.0, or gentoo.

In 2015 i already tried to get gentoo 2007 or 2008 running, but my compiled kernel failed to load and i gave up. I put back the disk i used back then in the prism, recompiled the kernel, and got it running. First step was kernel 2.4 which works. Then i upgraded to 2.6.something, which also works good. Besides that i have an up-to-date system, besides the kernel. I can emerge all things and everything works as expected (besides X).

The next one i tried was 3.4.49, which also runs great.

Next try: 3.19.19. Compiles, boots and runs. But i have a strange problem with it and can't figure out whats the matter: After booting the machine runs good for around 10 seconds. Then the cursor stops blinking and just stands still. If i press something on the keyboard, it seems the machine recovers, and i get 10x the key i pressed on the prompt. This also affects ssh sessions. I log in, type a command, i get output, then the machine hangs. It hangs exactly as long until i press a button on the keyboard attached to the machine. Then all commands are shown and executed in the ssh session i typed before. After some seconds the same thing happens and it freezes again.
I can't figure out what the matter is. I think i set nearly the same options in the kernel config.


[...]

So i've chosen a kernel between 3.4 and 4.x, and my choice was 3.8.13.
Results in kernel panic at boot:

[...]

Conclusion: I stick to 3.4.49 for the moment, because i can't figure out what the problem with the other ones is.
And no, i didn't think about X for a second in the progress. I have the radeon driver included, and lspci also shows me a compatible device, but i even dont get a framebuffer console, so i think we're out of luck for X.

Does 3.4.99 (last one of the 3.4.x versions) also work for you? Something out of 3.5.0, 3.6.0, 3.7.0 and 3.8.0 could be the next steps for testing if 3.4.99 works, maybe one of 3.6.0 or 3.7.0. The process is tedious, but could help to limit the amount of commits to check which possibly broke Prism support in the Linux kernel. If you PM me your kernel config I can help you with compiling a few specimens for testing, though my installed compiler on Gentoo is much newer.

Indigo Indy Indigo2 IMPACT O2 Octane Octane2 Origin 200 = Origin 200 - Origin 200 = Origin 200


johnnym
Octane

Posts: 60
Threads: 3
Joined: Jun 2018
Find Reply
01-27-2019, 08:14 PM
#14
RE: Lets open the IA64 lane. Who has one?
No one has mentioned anything about HP-UX. It's mature, well supported, and should be fairly easy to use. My last experience with that OS was about ten years ago, but it's not bad, and on HP hardware it's certainly a "native" operating system.

I've wanted an Itanium machine for a while but it's never been in the cards. Ideally I'd like an Itanium 1 machine just to see how bad they actually were, but those seem to be getting fairly rare. There was an HP i2000 on eBay for a while but it seems to have vanished, not sure if it sold or if the seller just got tired of the very little interest on a box that had a fairly inflated price.
hbent
O2

Posts: 5
Threads: 3
Joined: Nov 2018
Find Reply
04-12-2019, 07:58 PM
#15
RE: Lets open the IA64 lane. Who has one?
HP's Itanium2 machines were pretty good. HP-UX also runs just fine. It may not be that pretty, but it works and is very solid.

The Itanium 1 (aka Merced) based machines are a difficult topic. Many people said back then that they were slow and they certainly weren't exceptionally fast, but unless you wanted the IA32 emulation, things weren't all that bad, especially compared to other 64bit platforms.
However, the Merced based systems have one very big problem. They were basically all designed by Intel and OEMed by many vendors who could then choose the color of the plastic parts and a few add-on cards. The i2000 type was available from HP, IBM, Dell, Fujitsu-Siemens, and even SGI. Aside from this, there is one rather important problem with the i2000 type machines: most of them are dead. It's a common fault when the machines runs for a while, between 10 minutes to 2 hours, and then suddenly freezes hard. You can then unplug it, let it cool down, and then start again. I once tried to replace parts until this error could be fixed, but after having replaced all the parts (literally) the problem still persisted. Other i2000 owners told me about the same problems. I finally suspected a design flaw. These were not meant to be perfect products, but rather a first entry into the IA64 world, so people could develop apps and get used to it.
Aside from this, HP-UX on the i2000 wasn't all that bad. It could run 11.22 and it worked fine, expect for its lack of an X11 server. Apparently, this was due to bugs in the chipset. At least that's what HP said. Of course, Windows could support graphics on the machine back in the days. Some people said that graphics were not very fast though.
There was a server class Itanium 1 machine with up to 4 CPUs. HP called it an rx4610, but it was also available from IBM and Compaq. I haven't seen one of these in ages, so I have no idea if these have aged better. I guess it's best to avoid the Itanium1 boxes. I can definitely recommend the HP rx2600 and zx6000. These are great, among the best hardware HP has produced.

Concerning the start of the thread, I have a HP zx6000 (2 * 1.5GHz), HP rx2600 (2 * 1.5GHz), HP rx5670 (4 * 1.5GHz), and SGI Altix 350 (16 * 1.6GHz). All HPs run HP-UX and the Altix runs SuSE 9SP3. If you want graphics on the Altix/Prism, you have to stick to the SGI Propack, which was available for specific releases of SuSE and RedHat. The last version for the 350 and Prism is SuSE 9 with Propack 4. It is weird when you consider that the HP zx6000 and the SGI deskside Prism have used the same ATI FireGL X graphics cards, but the HP enjoyed widespread support and worked fine with a number of OSs, yet the Prism was caught in this hell of proprietary devices drivers and kernel modules.
lunatic
O2

Posts: 1
Threads: 0
Joined: Apr 2019
Find Reply
04-14-2019, 07:05 PM


Forum Jump:


Users browsing this thread: 1 Guest(s)