AIX 7.2 - Error initializing a device into the kernel. Post: 303029143

Sponsored Content

Operating Systems AIX AIX 7.2 - Error initializing a device into the kernel. Post 303029143 by c3rb3rus on Tuesday 22nd of January 2019 02:39:16 PM

01-22-2019

Registered User

AIX 7.2 - Error initializing a device into the kernel.

On a fresh bare metal (no LPARs) install of AIX 7.2 running cfgmgr is returning..

Code:

# cfgmgr
Method error (/usr/lib/methods/cfgstorfworkcom -l sfwcomm2 ):
        0514-040 Error initializing a device into the kernel.
Method error (/usr/lib/methods/cfgstorfworkcom -l sfwcomm3 ):
        0514-040 Error initializing a device into the kernel.
Method error (/usr/lib/methods/cfgqlfscsi -l fscsi2 ):
        0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgqlfscsi -l fscsi3 ):
        0514-061 Cannot find a child device.
Method error (/usr/lib/methods/cfgstorfworkcom -l sfwcomm2 ):
        0514-040 Error initializing a device into the kernel.
Method error (/usr/lib/methods/cfgstorfworkcom -l sfwcomm3 ):
        0514-040 Error initializing a device into the kernel.

I suspect it has something to do with my FC I/O cards, missing driver or something since that particular sfwcomm shows up as "Defined"....

# lsdev -C | grep sfwcomm
sfwcomm0 Available 05-00-01-FF Fibre Channel Storage Framework Comm
sfwcomm1 Available 05-01-01-FF Fibre Channel Storage Framework Comm
sfwcomm2 Defined 07-00-01-FF Fibre Channel Storage Framework Comm
sfwcomm3 Defined 07-01-01-FF Fibre Channel Storage Framework Comm
sfwcomm4 Available 0A-00-01-FF Fibre Channel Storage Framework Comm
sfwcomm5 Available 0A-01-01-FF Fibre Channel Storage Framework Comm

The two "defined" FC I/O devices are not plugged into anything at this time, they are to be used later down the road.

# lscfg | grep fc
+ fcs4 U78D3.001.WZS03A7-P1-C8-T1 PCIe3 2-Port 16Gb FC Adapter (df1000e21410f103)
+ fcs5 U78D3.001.WZS03A7-P1-C8-T2 PCIe3 2-Port 16Gb FC Adapter (df1000e21410f103)
+ fcs2 U78D3.001.WZS03A7-P1-C4-T1 PCIe2 8Gb 2-Port FC Adapter (77103225141004f3)
+ fcs3 U78D3.001.WZS03A7-P1-C4-T2 PCIe2 8Gb 2-Port FC Adapter (77103225141004f3)
+ fcs0 U78D3.001.WZS03A7-P1-C2-T1 PCIe3 2-Port 16Gb FC Adapter (df1000e21410f103)
+ fcs1 U78D3.001.WZS03A7-P1-C2-T2 PCIe3 2-Port 16Gb FC Adapter (df1000e21410f103)

The "fc0 - 1 - 4 - 5" work fine after i switched to using AIXPCM (HBAs detected by storage, etc.), not sure why fc2-3 are throwing errors.

Why is cfgmgr throwing "Error initializing a device into the kernel" errors?

--- Post updated at 11:39 AM ---

Turns out because those two FC ports were not connected to anything that is where the error was coming from, I plugged two ECW0 - Optical Wrap Plugs into the FC ports and running "cfgmgr" on AIX no longer produces errors. Running fcstat against the ports returns data as well.

This User Gave Thanks to c3rb3rus For This Post:

c3rb3rus

View Public Profile for c3rb3rus

Find all posts by c3rb3rus

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dleting a Device in AIX 4.3

I need to delete a TTY in my AIX 4.3 system. I have tried using the smit but everytime I try it, there is a message telling me that the device is in use and cannot be changed. How do I take the device "offline", so to speak, so that I can edit the settings and/or delete it. V/R Djassi

2. UNIX for Advanced & Expert Users

Kernel and Device Driver Programming

I am looking for a guide on how to program for either the Linux or FreeBSD (includes 4.4BSD, NetBSD or OpenBSD) kernel. I would prefer to learn how to write device drivers, but anything would help. If you know, please email me at *removed* or leave a post here Regards, Farhan

3. Linux

Linux Device Driver: avoid mem copy from/to user/kernel space

I recently started working with Linux and wrote my first device driver for a hardware chip controlled by a host CPU running Linux 2.6.x kernel. 1. The user space process makes an IOCTL call with pointer to a user memory buffer. 2. The kernel device driver in the big switch-case of IOCTL,...

4. Fedora

Is Kernel module is the same as a device driver?

I have been reading prep questions for my second unix academy exam, and there's a nuance, I'm not sure I understand it correctly. I've been under impression from my readings of book by Evi Nemeth and from unix academy DVDs I've been watching, that kernel's modules are drivers. I think of it, as...

5. UNIX for Advanced & Expert Users

Get pointer for existing device class (struct class) in Linux kernel module

Hi all! I am trying to register a device in an existing device class, but I am having trouble getting the pointer to an existing class. I can create a class in a module, get the pointer to it and then use it to register the device with: *cl = class_create(THIS_MODULE, className);...

6. Android

Running only the Linux kernel of an Android device

I am looking for a way to run on top of the Linux kernel of an Android device. I want to use the existing configured Linux beneath Android rather than put a new Linux distribution onto a device. The article "The Android boot process from power on" (sorry, forum won't let me paste the link)...

7. UNIX for Advanced & Expert Users

Kernel crash - NULL pointer dereference when calling DEVICE_WRITE from KTHREAD in a USB device drive

I'm writing a simple USB driver to drive a stepper motor based on USB Skeleton 2.2 Driver, kernel 3.8. The basic version is running properly. As a advancement, I introduced KTHREAD to call the DEVICE_WRITE (skel_write) (), so that the driver will be available for other tasks & requests. Calling...

8. AIX

AIX - NIC device explanation need

Hello, I have some doubt about the NIC device on my AIX box. When using lsdev command / > lsdev -Cc adapter | grep en ent0 Available 03-00 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003) ent1 Available 03-01 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003) ent2...

LEARN ABOUT SUNOS

socal

socal(7D)							      Devices								 socal(7D)

NAME

       socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver

SYNOPSIS

       socal@sbus-slot,0

DESCRIPTION

       The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces.  Each Fibre Channel interface
       can connect to a Fibre Channel Arbitrated Loop (FC-AL).

       The  socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.

FILES

       /kernel/drv/socal       ELF Kernel Module

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Architecture		     |SPARC			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       sbus(4), sf(7D), ssd(7D)

       Writing Device Drivers

       ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)

       ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)

       Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)

DIAGNOSTICS

       The messages described below  may appear on system console in addition to being logged.

       On the console, these messages are preceded by:

       socal%d: port %a

       where  %d is the instance number of the	socal controller and  %a is the port on the host adapter.

       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: bad soft state.

	   Driver did not attach, devices will be inaccessible.

       attach failed: unable to alloc xport struct.

	   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							    9 May 1997								 socal(7D)