SCSI termination problem installing Redhat 7.1

Guy M. Streeter streeter at redhat.com
Wed May 28 08:23:01 EST 2003


The Red Hat Linux 7.1 distribution for pSeries supports the 620, 640,
and 660 lines of pSeries systems.
The p610 is not supported.

--Guy

On Tue, 2003-05-27 at 17:04, Christian Foerster wrote:
> Hi,
>
> we finally made some progress installing Redhat 7.1 on the p610. We
> successfully booted the kernel over ethernet and have got the installer
> been displayed over serial console. We have been able to configure
> network connection. We choose FTP install and have got the base files
> downloaded by the installer!
>
> Then the Redhat Anaconda installer application starts and lets us
> choose the system type we want to install. We chose 'custom
> installation' and the Anaconda application crashes immediately. It has
> been the same with 'server' and 'workstation' installion type.
>
> We guess its because of some SCSI conflict with our machine. The dmesg
> output says something so. Below you can find the Anaconda error message
> and the dmesg kernel output. Booting with the Suse kernel leads to the
> same affect. It complains about SCSI bus termination. However
> installation of AIX works like a charm.
>
> Any idea? Can someone maybe provide us with a working install kernel
> for the p610.
>
> Chris
>
>
> ############# Anaconda Error Message #################
>
> An internal error occurred in the     # x x
>                    x installation program. Please report   a x 
>                    x this error to Red Hat (through the    a x
> x
>                    x bugzilla.redhat.com web site) as      a x 
> 
>                    x soon as possible. Traceback           a x
> x
>                    x (innermost last):                     a x x
>                    x   File "/usr/bin/anaconda.real",      a x 
> 
>                    x line 533, in ?                        a x 
> 
>                    x     intf.run(todo, test = test)       a x 
>                    x   File                                a x
> x
>                    x "/var/tmp/anaconda-7.1//usr/lib/anac  a x
> x
>                    x onda/text.py", line 1144, in run
>
>
> ################## dmesg boot kernel output
> ###############################
>
> Naca Info...
>
> naca                       = 0xc000000000004000
> naca->processorCount       = 0x0000000000000001
> naca->physicalMemorySize   = 0x0000000020000000
> naca->dCacheL1LineSize     = 0x0000000000000080
> naca->dCacheL1LogLineSize  = 0x0000000000000007
> naca->dCacheL1LinesPerPage = 0x0000000000000020
> naca->iCacheL1LineSize     = 0x0000000000000080
> naca->iCacheL1LogLineSize  = 0x0000000000000007
> naca->iCacheL1LinesPerPage = 0x0000000000000020
> naca->pftSize              = 0x0000000000000017
> naca->serialPortAddr       = 0x00000000f80003f8
> naca->interrupt_controller = 0x0000000000000001
>
> HTAB Info ...
>
> htab_data.htab             = 0xc00000001e800000
> htab_data.num_ptegs        = 0x0000000000010000
>
> -----------------------------------------------------
> <chrp_progress> MM:exit
> <chrp_progress> id mach: done
> <chrp_progress> setup_arch:enter
> <chrp_progress> setup_arch:bootmem
> OpenPIC addr: ffc00000
> <chrp_progress> setup_arch: exit
> <chrp_progress> openpic enter
> <chrp_progress> openpic timer
> <chrp_progress> openpic ipi
> <chrp_progress> openpic ext
> <chrp_progress> openpic spurious
> <chrp_progress> openpic exit
> Linux version 2.4.9-23.19.8 (root at shiznit.hsv.redhat.com) (gcc version
> 3.0.5 200
> 20418 (prerelease)) #1 SMP Wed Nov 20 14:10:18 CST 2002
> Boot arguments: console=ttyS0,9600 text
> Python workaround: reg0: 18e3388
> Python workaround: reg0: 18eb788
> On node 0 totalpages: 131072
> zone(0): 131072 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: console=ttyS0,9600 text
> OpenPIC Version 1.2 (8 CPUs and 1 IRQ sources) at e000000002207000
> OpenPIC reversed IPI registers detected
> time_init: decrementer frequency = 95.141636 MHz
> time_init: processor frequency   = 333.000000 MHz
> Console: colour dummy device 80x25
> Calibrating delay loop... 332.99 BogoMips
> Memory: 482008k available (1936k kernel code, 3176k data, 304k init)
> [c000000000
> 000000,c000000020000000]
> Dentry-cache hash table entries: 65536 (order: 8, 1048576 bytes)
> Inode-cache hash table entries: 32768 (order: 7, 524288 bytes)
> Mount-cache hash table entries: 8192 (order: 5, 131072 bytes)
> Buffer-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Page-cache hash table entries: 131072 (order: 9, 2097152 bytes)
> proc_ppc64: Creating /proc/ppc64/pmc
> PCI: /proc/ppc64/pci created.
> PCI: PciFr created at: 0xc000000001b0b000
> PCI: /proc/ppc64/pcifr created.
> POSIX conformance testing by UNIFIX
> Entering SMP Mode...
> Probe found 1 CPUs
> Waiting for 0 CPUs
> PCI: Probing PCI hardware
> Using INTC for W82c105 IDE controller.
> Unknown bridge resource 0: assuming transparent
> Unknown bridge resource 2: assuming transparent
> PCI: Cannot allocate resource region 3 of PCI bridge 0
> PCI: resource is a0000..9ffff (200), parent c000000000277520
> PCI: Probing PCI hardware done
> <chrp_progress>
> <chrp_progress> 2.4.9-23.19.8
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> i/pSeries Real Time Clock Driver v1.1
> RTAS daemon started
> PPC64 nvram contains 110592 bytes
> Starting kswapd v1.8
> matroxfb: Matrox G450 detected
> matroxfb: 640x480x8bpp (virtual: 640x26208)
> matroxfb: framebuffer at 0xC0000000, mapped to 0xe00000000224c000, size
> 33554432
>
> Console: switching to colour frame buffer device 80x30
> fb0: MATROX VGA frame buffer device
> Detected PS/2 Mouse Port.
> pty: 2048 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
> SERIAL_PCI en
> abled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> block: queued sectors max/low 318485kB/187413kB, 960 slots per queue
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> Floppy drive(s): fd0 is 2.88M
> FDC 0 is a National Semiconductor PC87306
> loop: loaded (max 8 devices)
> SCSI subsystem driver Revision: 1.00
> PCI: Enabling device 00:0c.0 (0140 -> 0143)
> sym53c8xx: at PCI bus 0, device 12, function 0
> sym53c8xx: setting PCI_COMMAND_MASTER...(fix-up)
> sym53c8xx: 53c1010-66 detected
> PCI: Enabling device 00:0c.1 (0140 -> 0143)
> sym53c8xx: at PCI bus 0, device 12, function 1
> sym53c8xx: setting PCI_COMMAND_MASTER...(fix-up)
> sym53c8xx: 53c1010-66 detected
> sym53c1010-66-0: rev 0x1 on pci bus 0 device 12 function 0 irq 20
> sym53c1010-66-0: ID 7, Fast-80, Parity Checking
> sym53c1010-66-0: suspicious SCSI data while resetting the BUS.
> sym53c1010-66-0: dp1,d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o
> = 0x4001
> 00, expecting 0x100
> sym53c1010-66-0: FATAL ERROR: CHECK SCSI BUS - CABLES, TERMINATION,
> DEVICE POWER
>   etc.!
> sym53c1010-66-0: giving up ...
> sym53c1010-66-0: rev 0x1 on pci bus 0 device 12 function 1 irq 17
> sym53c1010-66-0: ID 7, Fast-80, Parity Checking
> sym53c1010-66-0: handling phase mismatch from SCRIPTS.
> scsi0 : sym53c8xx-1.7.3c-20010512
> B0roxfb_crtc2: secondary head of fb0 was registered as fb1
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 2048 buckets, 32Kbytes
> TCP: Hash tables configured (established 65536 bind 65536)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 982k freed
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 304k init
> Greetings.
> Red Hat install init version 7.0 starting
> mounting /proc filesystem... done
> mounting /dev/pts (unix98 pty) filesystem... done
> Red Hat install init version 7.0 using a serial console
> remember, cereal is an important part of a nutritionally balanced
> breakfast.
>
> could not set new controlling tty
> checking for NFS root filesystem...no
> trying to remount root filesystem read write... done
> checking for writeable /tmp... yes
> running install...
> running /sbin/loader
>


** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/





More information about the Linuxppc64-dev mailing list