Sponsored Content
Operating Systems HP-UX rp 3440 flash red light and can't boot to unix Post 302167668 by Perderabo on Friday 15th of February 2008 08:00:03 AM
Old 02-15-2008
A High Priority Machine Check (HPMC) means that the kernel found a bad hardware issue. All I can suggest is to call HP to get your system fixed.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dual boot Red Hat and 2000

Hi, I'm trying to set up a dual boot with Win2000 and Red Hat. I installed Win 2000 first a partitioned 2 separate drives. When I start the Red Hat install with Disk Druid, it sees my partitioned drives, but won't let me install Red Hat. What is my issue? (4 Replies)
Discussion started by: jensam
4 Replies

2. Filesystems, Disks and Memory

Red Hat Linux Boot Problems

Hi. I have an 81 gig hard drive and split it up into 2 partitions. One for linux and the other for windows. I had my windows up and running and it was doing fine. Then i started my linux. I go Red Hat Linux out and installed it on the partition. This all worked out well. However, when i rebooted... (10 Replies)
Discussion started by: vertigo
10 Replies

3. UNIX for Dummies Questions & Answers

red hat linux installation boot floppy disk

Hi, My dear friends, I am trying to install red hat linux. I have downloaded its disc1. On the instructions page, the next stage is to make the boot disk, so that I can boot from the floppy. However, I am unable to locate the boot image iso file. I tried on google, but I got a few files which... (3 Replies)
Discussion started by: linuxpenguin
3 Replies

4. Linux

How to remove Red Hat 4 OS from dual boot

Hi Xperts out there Previously i have Vista Standard installed in my notebook. Then i have installed Red Hat 4 and currently my notebook are dual boot OS. Now i'm thinking to remove all my Red Hat 4 out. So how to achive this without risking my Vista Standard. :D (5 Replies)
Discussion started by: adzuanamir
5 Replies

5. Ubuntu

make Ubuntu and Red Hat boot partitions

Is it possible to make multiboot partitions of Ubuntu and red hat Linux? (4 Replies)
Discussion started by: sito
4 Replies

6. Red Hat

Buffer I/O error in red hat linux boot up

I get error message when boot up red hat linux Buffer I/O error on device hdc ,logical block XX ... /dev/hdc:read failed after 0 of 2048 at 0 : input/output error ..... I paste the /etc/fstab file in here /dev/hdc is cdrom How can I fix it Please advice # cat /etc/fstab # This file... (3 Replies)
Discussion started by: chuikingman
3 Replies

7. Solaris

Net Boot with Flash install

I have a blade 6000 chassis with a T6340 blade. The blade took a dump and I am trying to rebuild it with a Flash Archive. I am using net boot from an E2900 and the flash is located on a an array that is attached to my v245 management server. I can net boot and I can select flash install. When I put... (1 Reply)
Discussion started by: ryan_ford
1 Replies
usoc(7D)							      Devices								  usoc(7D)

NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL. FILES
/kernel/drv/usoc 32-bit ELF kernel module /kernel/drv/sparcv9/usoc 64-bit ELF kernel module ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Interface stability |Unknown | +-----------------------------+-----------------------------+ |Availability |SUNWusoc | +-----------------------------+-----------------------------+ SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D) Writing Device Drivers Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994 Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996 Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998 Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998 DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by: usoc%d: where usoc%d: is the per-port instance number of the usoc controller. Fibre Channel is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is OFFLINE The Fibre Channel loop is now offline. attach failed: device in slave-only slot. Move soc+ card to another slot. attach failed: alloc soft state. Driver did not attach, devices will be inaccessible. attach failed: bad soft state. Driver did not attach, devices will be inaccessible. attach failed: unable to map eeprom Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map XRAM Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map registers Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access status register Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to install interrupt handler Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access host adapter XRAM Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to write host adapter XRAM Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: read/write mismatch in XRAM Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. SunOS 5.10 20 Jul 1999 usoc(7D)
All times are GMT -4. The time now is 01:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy