ISCSI device mapping on Solaris 10

Hi,
A brief overview of my situation:
I have 3 Oracle Solaris X86-64 virtual machines that I'm using for testing. I have configured a ZFS storage pool on one of them (named solastorage), that will serve as my iSCSI target. The remaining 2 servers (solarac1 and solarac2) are meant to be my RAC nodes for a test Oracle 11g R2 RAC installation.
/etc/hosts listing:
# ZFS iSCSI target
192.168.247.150 solastorage solastorage.domain.com
# RAC Public IPs
192.168.247.131 solarac1 solarac1.domain.com loghost
192.168.247.132 solarac2 solarac2.domain.com
A brief overview of the steps carried out at solastorage (after enabling the iSCSI target service):
zpool create rac_volume mirror c0d1 c1d1
zfs create -V 0.5g rac_volume/ocr
zfs create -V 0.5g rac_volume/voting
zfs set shareiscsi=on rac_volume/ocr
zfs set shareiscsi=on rac_volume/voting
On both the RAC servers (of course I've enabled the iSCSI initiator service on both):
iscsiadm modify discovery -t enable
iscsiadm add discovery-address 192.168.247.150
devfsadm -i iscsi
After that, when I run format on both sides, I can see the following:
solarac1# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63>
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c3t15d0 <DEFAULT cyl 509 alt 2 hd 64 sec 32>
/iscsi/[email protected]%3A02%3A54d1d1d2-7154-ee78-94e6-c3d053ca7ab50001,0
2. c3t16d0 <DEFAULT cyl 2045 alt 2 hd 128 sec 32>
/iscsi/[email protected]%3A02%3Af109f049-9f76-6a16-c36a-d42c4d6818fe0001,0
solarac2# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 2607 alt 2 hd 255 sec 63>
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c2t2d0 <DEFAULT cyl 509 alt 2 hd 64 sec 32>
/iscsi/[email protected]%3A02%3A54d1d1d2-7154-ee78-94e6-c3d053ca7ab50001,0
2. c2t3d0 <DEFAULT cyl 2045 alt 2 hd 128 sec 32>
/iscsi/[email protected]%3A02%3Af109f049-9f76-6a16-c36a-d42c4d6818fe0001,0
solastorage# iscsitadm list target -v | more
Target: rac_volume/ocr
iSCSI Name: iqn.1986-03.com.sun:02:54d1d1d2-7154-ee78-94e6-c3d053ca7ab5
Alias: rac_volume/ocr
Connections: 2
Initiator:
iSCSI Name: iqn.1986-03.com.sun:01:2a95e0f4ffff.4d586ac7
Alias: solarac1
Initiator:
iSCSI Name: iqn.1986-03.com.sun:01:2a95e0f4ffff.4d5b7cef
Alias: solarac2
ACL list:
TPGT list:
LUN information:
LUN: 0
GUID: 600144f04d5b8fca00000c29655dc000
VID: SUN
PID: SOLARIS
Type: disk
Size: 512M
Backing store: /dev/zvol/rdsk/rac_volume/ocr
Status: online
So, here I can see the same devices on both the servers, only it is being recognised with different device names. Without using any 3rd-party software (for example Oracle Cluster), how can I manually map the device names on both these servers so that they are the same?
Previously, for Oracle 10g Release 2, I was able to use the metainit commands to create a pseudo-name that is the same on both servers. However, as of Oracle 11g R2, devices with the naming format /dev/md/rdsk/.... are no longer valid.
Does anyone know of a way I can manually re-map these devices to the same device names on the OS level, without needing Oracle Cluster or something similar?
Thanks in advance,
NS Selvam
Edited by: NS Selvam on Feb 16, 2011 1:32 AM
Edited by: NS Selvam on Feb 16, 2011 1:33 AM

Thank you for your response.
Setting the "ddi-forceattach" property in Pseudo driver .conf file will not
help. Solaris does not "attach" Pseudo drivers which do not have ".conf"
children (even though the Pseudo driver conf file has "ddi-forceattach=1"
property set). Opening the Pseudo device file will attach the Pseudo driver.I'm confused... We have a .conf file, as mentioned, but what makes
it a "Pseudo driver .conf" rather than just a "driver .conf"?
From what I undestand of your requirement, the following should be sufficient :
1. Set property : "ddi-forceattach=1" for all physical devices that is
required by Pseudo driver.
2. Application opens the Pseudo device node.
Let me know if you have any queries / issues. I do have further questions.
Included below is a version of our .conf file modified to protect the
names of the guilty.
As you can see, there is part of it which defines a pseudo device,
and then a set of properties that apply to all devices. Or that's the
intention.
In #1, you said to set the ddi-forceattach property for all "physical
devices", but how do I do this, if it's not what I'm already doing? And what
do you mean "required by Pseudo driver"?
name="foobar" parent="pseudo" instance=1000 FOOBAR_PSEUDO=1;
ddi-forceattach=1
FOOBAR_SYM1=1
FOOBAR_SYM2=2
FOOBAR_SYM3=3;
On a Solaris 9 system of mine, recently I believe I have seen multiple cases
where I've booted, and a physical device has not gotten attached, but if I
reboot, it will be attached the next time.
Thanks,
Nathan

Similar Messages

Raw devices mapping inconsistent

Raw devices mapping gets changed each time service iscsi is restarted . or node is restarted
udev has been configured using these scripts.
nas configured using openfiler
55-openiscsi.rules
KERNEL=="sd*", BUS=="scsi", PROGRAM="/etc/udev/scripts/iscsidev.sh %b",SYMLINK+="iscsi/%c/%part%"
iscsidev.sh
#!/bin/sh
# FILE: /etc/udev/scripts/iscsidev.sh
BUS=${1}
HOST=${BUS%%:*}
[ -e /sys/class/iscsi_host ] || exit 1
file="/sys/class/iscsi_host/host*/device/session*/iscsi_session*/targetname"
target_name=$(cat ${file})
# This is not an open-scsi drive
if [ -z "${target_name}" ]; then
exit 1
fi
echo "${target_name##*.}"
Please suggest.

Hi,
To find how raw devices are being mapped to phsyical device run this command /usr/sbin/lspv | grep -i
for example # /usr/sbin/lspv | grep -i "0009005fb9c23648"
see this link
http://download.oracle.com/docs/cd/B28359_01/install.111/b28258/storage.htm#CDEJFCCB

802.11x device drivers in Solaris 10

Can any one point me to a list of 802.11x devices supported by Solaris 10
Thanks
Enzo

http://www.sun.com/bigadmin/hcl/

Raw device mapping

accidentally we lost the rawdevice mapping file /etc/sysconfig/rawdevices. since we do not have OS backup we could not restore this file.
without this file ASM could not mount diskgroups....
Is it possible to find the device mapping from anykind of OS or Oracle Log/Trace files?
Oracle alert log contains only /dev/raw/raw1....

Hi,
If the raw devices are still bound to the block device and you haven't rebooted since you lost you rawdevices config file then you could identify the major/minor numbers using /usr/bin/raw -qa
The example below shows that dev/raw/raw1 is bound to /dev/sdb1
[root@foo]# raw -qa
/dev/raw/raw1: bound to major 8, minor 17
[root@rmukvm214 dev]# ls -l sdb1
brw-rw---- 1 root disk 8, 17 Jun 17 16:14 sdb1
I'm not sure if this is the most elegant or safest way of piecing this information back together, as mentioned you might want to raise an SR with Oracle support.
Regards

WRT1900AC - wireless device shows as wired connection in device map

Just purchased the WRT1900AC and going through the process of setting up my devices.
I have a fitbit aria wireless scale and after connecting it to the router it appears as a LAN device instead of a wireless device in the device map. It appears to work, so it's not a functional problem but rather a cosmetic one.
The device has firmware 1.1.8.164461 (updated today).

Yes there is a known bug regarding this.
Please remember to Kudo those that help you.
Linksys
Communities Technical Support

About iscsi hd mapping sequence

I want to build up RAc enviroment that use openfiler as iscsi target storage
I have following shared iscsi disks
[root@rac1 ~]# iscsi-ls -l |grep 'NAME\|sd'
TARGET NAME : test2
Device: /dev/sdc
TARGET NAME : test1
Device: /dev/sdd
TARGET NAME : asm3
Device: /dev/sdf
TARGET NAME : asm1
Device: /dev/sde
TARGET NAME : asm2
Device: /dev/sdi
TARGET NAME : votedisk
Device: /dev/sdh
TARGET NAME : ocr
Device: /dev/sdg
but ,the disk mapping order will change after reboot,How can I fix them in order even after system reboot?
any suggestion

pls forgive my poor english
It's not something about permittion,or even it's not the business of database but storage or OS problem
In my scenario I just found /dev/sdb mapps my iscsi target (named ocr) after reboot /dev/sdb mapps iscsi target (named votedisk)
I can not get persistent local disk label

Gettin Error While activating Device Mapping Rule

Hi all,
I am getting below error while generating Device attribute mapping Rule :
Err:Metainfo FM MMW_DM_DSMS_METH_META - Class Name not specified
Any idea how to resolve this problem.
Regards,
Abhishek

Hi Abhishek,
Custom attributes will not be reflected under category list.
It can be viewed by clicking 'customize' button only in sdoe_rmm01.Do not add custom attributes part of category.
If you have clicked 'Admin UI display' while creating it will get reflected in the admin portal under single valued or multi valued attributes tabs .This way it allowes you to assign custom atrribute values to devices from admin portal.
By the way when you created the other attributes.in category .how did you manage to give proper data types ?
When you say , backward compatible, are you planning to migrate the SyncBOs defined in MI to the current DOE?If yes , this is all that you need to do.
Regards,
Liji

Problem with a DDI Device driver for Solaris 8 and 9 on a Sun-Blade-1500

The problem has to do with dma allocated memory and the little-endian format.
When I copy blocks bigger than 256 bytes to the dma memory, using a uiomove() or bcopy(), the data after the first 32 bytes is swapped around over 8 bytes.
The bcopy from a driver (stack) buffer into the dma virtual memory has the same affect.
So it has to do with the kernel dma allocated memory and the endianess.
When I set the byte order to big-endian inside the ddi_device_acc_attr the data seems to be alright, also with bigger transfer sizes.
My device however needs the little-endian format.
I have the same the same device driver running without any errors on a Sun Blade-150 Solaris 8 for a long time now.
Can somebody please advise me?
Data example,
test data: 0x00,0x01,0x02,?.
64, 128 or 256 bytes blocks:
000: 07 06 05 04 03 02 01 00 0F 0E 0D 0C 0B 0A 09 08
016: 17 16 15 14 13 12 11 10 1F 1E 1D 1C 1B 1A 19 18
032: 27 26 25 24 23 22 21 20 2F 2E 2D 2C 2B 2A 29 28
048: 37 36 35 34 33 32 31 30 3F 3E 3D 3C 3B 3A 39 38
064: 47 46 45 44 43 42 41 40 4F 4E 4D 4C 4B 4A 49 48
080: 57 56 55 54 53 52 51 50 5F 5E 5D 5C 5B 5A 59 58
096: 67 66 65 64 63 62 61 60 6F 6E 6D 6C 6B 6A 69 68
112: 77 76 75 74 73 72 71 70 7F 7E 7D 7C 7B 7A 79 78
512 or 1024 bytes blocks:
000: 07 06 05 04 03 02 01 00 0F 0E 0D 0C 0B 0A 09 08
016: 17 16 15 14 13 12 11 10 1F 1E 1D 1C 1B 1A 19 18
032: 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F <----- ?
048: 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F <----- ?
064: 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F <----- ?
080: 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F <----- ?
096: 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F <----- ?
112: 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F <----- ?
Code example, how I allocate the DMA (kernel) memory:
DDI_STRUCTURE_LE_ACC = Little Endian format
DDI_STRUCTURE_BE_ACC = Big Endian format
static struct ddi_device_acc_attr sse_dma_attr =
DDI_DEVICE_ATTR_V0, /* The version number of this structure */
DDI_STRUCTURE_LE_ACC, /* see above */
DDI_STRICTORDER_ACC, /* How CPU will reference data, default */
The dma definitions for allocating the DMA memory
static ddi_dma_attr_t dmaattr= {
DMA_ATTR_V0, /* version */
0, /* starting address for DVMA */
0xffffffff, /* end address for DVMA */
0xffffffff, /* max transfer count in one cookie */
0x1, /* address restrictive alignment, 1 = byte alignment */
0x7, /* burst sizes */
1, /* min number of byes */
0x00ffffff, /* max number of bytes device can transmit/receive */
0xffffffff, /* upper bound of the DMA engine's address */
1,
512,
0, /* DDI_DMA_FORCE_PHYSICAL doesn't work */
ddi_dma_alloc_handle()
if((ret=ddi_dma_alloc_handle(xsp->dip,
&dmaattr,
DDI_DMA_SLEEP,
NULL,
dmahandle_out)) != DDI_SUCCESS)
cmn_err(CE_CONT, "ucr_dma_alloc_memory, "
"ERROR ddi_dma_alloc_handle status = %d\n",
ret);
return(ret);
if((ret=ddi_dma_mem_alloc(*dmahandle_out,
(uint_t) size,
dma_acc_attr,
DDI_DMA_CONSISTENT,
DDI_DMA_SLEEP,
NULL,
(caddr_t *)&raw_kern_addr,
&real_len,
dma_acc_handle_out)) != DDI_SUCCESS)
cmn_err(CE_CONT, "ucr_ucr_dma_alloc_memory, "
"ERROR ddi_dma_mem_alloc status = %d\n",
ret);
ddi_dma_free_handle(dmahandle_out);
return(ret);
This will also init the PCI - IOMMU for
address translation.
if((ret=ddi_dma_addr_bind_handle(*dmahandle_out,
NULL,
(caddr_t)raw_kern_addr,
real_len,
DDI_DMA_RDWR | DDI_DMA_CONSISTENT,
DDI_DMA_SLEEP,
NULL,
&dma_cookie,
&count)) != DDI_SUCCESS)
cmn_err(CE_CONT, "ucr_ucr_dma_alloc_memory, "
"ERROR ddi_dma_addr_bind_handle status = %d\n",
ret);
ddi_dma_mem_free(dma_acc_handle_out);
ddi_dma_free_handle(dmahandle_out);
return(ret);
if((ret=ddi_dma_sync(*dmahandle_out,
0,
real_len,
DDI_DMA_SYNC_FORDEV)) != DDI_SUCCESS)
cmn_err(CE_CONT, "ucr_ucr_dma_alloc_memory, "
"ERROR ddi_dma_sync status = %d\n", ret);
ddi_dma_unbind_handle(*dmahandle_out);
ddi_dma_mem_free(dma_acc_handle_out);
ddi_dma_free_handle(dmahandle_out);
return(ret);

I am having the similar problem identified in this thread.
OS: Sun Solaris 10 01/06
Hardware: Sun Blade 2500
PCI Memory card.
Problem: When driver moves more then 40 bytes via PIO from a PCI device memory card, the long words are swapped starting at 40 byte transfer size and greater.
device memory description:
static ddi_device_acc_attr_t sdram_access_attr =
DDI_DEVICE_ATTR_V0, /* Boilerplate value */
DDI_STRUCTURE_LE_ACC,
DDI_STRICTORDER_ACC /* Don't reorder accesses */
The user application does a read call, which goes to xxread. xxread calls physio( xxstrategy, bp, dev, B_READ, xxminphys, uio );
In xxstrategy the transfer is done using
ddi_mem_rep_get8(ucb->ucb_sdram_accHndl,
(uint8_t*) kaddr,
(uint8_t*) raddr,
(size_t) bp->b_resid),
(uint_t) DDI_DEV_AUTOINCR );
PCI Device memory is loaded with incrementing address (8bit), 0,1,2... This is confirmed using a PCI Bus Analyzer.
A read of 36 bytes or less returns:
03 02 01 00 07 06 05 04 ...
A read of 40 bytes returns:
07 06 05 04 03 02 01 00 ...
If I peek 1 byte at a time using ddi_get8(ucb->ucb_sdram_accHndl, ...) I get
00 01 02 03 04 05 06 07
Why are the long words swapped starting at 40 byte transfer size and greater?

Install device conflict for Solaris 9 on V60X

Can anyone help
Getting the following message when installing Solaris 9 on v60x using raid 1 ...
Warning: Resource Conflict - both devices are added
NON-ACPI device: ISY0050
Port:3F0-3F5, 3F7, IRQ: 6; DMA: 2
ACPI device: ISY0050
Port:3F2-3F3, 3F4-3F5, 3F7; IRQ: 6; DMA: 2

Cool, so i ignore the device conflict warning message and carry on, it gets thru the webstart dialogs to the welcome wizard, display a progress bar which get to 25% and then the wizard disapears, I click 'send kiosk to background', but the wizard has vanished, maybe it went of the visible screen area?
What i have achived tho is to stripe the disk for raid-1 and re-install the service partition, and the partial webstart intall as above.
My problem however is that it wont boot up, giving message
'no bootable partition'. The webstart doco says it creates the required fdisk partitions etc
There is a note in the 'solaris 9 install guide' that says ...
'if you restored the service partition before starting the install, you might not be able to upgrade to the Sun OE' .
Thanks for that Sun. Any ideas guys, perhaps its only a warning message.

Resource Conflict Warning (ACPI/NON-ACPI devices) while installing solaris

Hi,
I am trying to install Solaris 8 on my system.
Intel Celeron 1.7 Ghz
128 MB RAM
Gigabyte 8LD 533K Motherboard with Intel Chipset.
While installing, the second installation screen titled "Bus
Enumeration" gives the following warning.
Warning: Resource Conflict:
ACPI Device: PNP0C01.
Memory: (about 5 to 6 memory addresses in hexadecimal form are shown)
NON-ACPI Device: PNP0C01.
Memory: (about 5 to 6 memory addresses in hexadecimal form are shown,
which are different from the ones shown under the ACPI device list)
I ignored the message and pressed F2 key as suggested.
The next screen "Solaris Boot" comes and after choosing the CD (as
the target from which the OS is to be installed), The next screen
comes up asking me to chose the type of installation 1) Solaris
Interactive and 2) Jumpstart. No matter which option I choose, the
system shows 2-3 messages, and even before I can read them, the
system reboots. Thus I am unable to install Solaris.
I searched on Google and as one person had suggested tried tweaking
the BIOS. (Disable APM etc). But it did not work, because I don't
have an option that specifically gives the Disable/Enable option for
APM. I get the Advanced Power Management screen, but it shows some
different options.
I spoke about this problem with a friend who has some experience on
Solaris and he put the CD Drive and the Hard Disk on two different
buses, but it didn't help. I still get the same message.
I would be very grateful if someone could suggest a method so I can
install Solaris.
Regards,
pmu

The next screen comes up asking me to chose the type of installation 1) Solaris
Interactive and 2) Jumpstart. At this screen, type
b kadb -v
instead of choosing 1) or 2). Now you should be able to read the error messages from the kernel that
prevent booting into Solaris.

Device attaches on Solaris 10

Hello,
We have a device driver that's been working on Solaris 7 and higher for some time. We're seeing different behavior on Solaris 10 that is causing us problems. We are running on Sparcs.
Our driver has one pseudo device and one or more physical devices.
Normally when the driver loads, the attach function is called for the pseudo device and the physical devices (in some not necessarily predictable order).
This loading would usually take place when the pseudo device was opened, but could be due to the driver initially being installed or sometimes when the system boots.
With Solaris 10, after rebooting the system, sometimes the pseudo device access only causes the pseudo device to be attached, and not the physical devices.
Our driver is actually accessed by applications soley via the pseudo device, rather than by individual devices, so this causes a big problem for us.
Is there anything we can do to cause the behavior to revert back to what it was before? Anything which causes the physical devices to all be attached would be fine, such as some call the attach for the pseudo device could make. Or something to put in our .conf file, etc.
Thanks,
Nathan

Thank you for your response.
Setting the "ddi-forceattach" property in Pseudo driver .conf file will not
help. Solaris does not "attach" Pseudo drivers which do not have ".conf"
children (even though the Pseudo driver conf file has "ddi-forceattach=1"
property set). Opening the Pseudo device file will attach the Pseudo driver.I'm confused... We have a .conf file, as mentioned, but what makes
it a "Pseudo driver .conf" rather than just a "driver .conf"?
From what I undestand of your requirement, the following should be sufficient :
1. Set property : "ddi-forceattach=1" for all physical devices that is
required by Pseudo driver.
2. Application opens the Pseudo device node.
Let me know if you have any queries / issues. I do have further questions.
Included below is a version of our .conf file modified to protect the
names of the guilty.
As you can see, there is part of it which defines a pseudo device,
and then a set of properties that apply to all devices. Or that's the
intention.
In #1, you said to set the ddi-forceattach property for all "physical
devices", but how do I do this, if it's not what I'm already doing? And what
do you mean "required by Pseudo driver"?
name="foobar" parent="pseudo" instance=1000 FOOBAR_PSEUDO=1;
ddi-forceattach=1
FOOBAR_SYM1=1
FOOBAR_SYM2=2
FOOBAR_SYM3=3;
On a Solaris 9 system of mine, recently I believe I have seen multiple cases
where I've booted, and a physical device has not gotten attached, but if I
reboot, it will be attached the next time.
Thanks,
Nathan

Best practices for attaching iSCSI devices

Hello all,
My environment: Nexus 5010 with 2148T FEX switches in the racks.
Can (or should) I use the 2148T as the switch between clustered servers and the iSCSI SAN? The SAN is a Dell MD3000i connected to Dell R710 servers, Win Ent 2008 R2 Server.
Plans are to use two vlans so I have dual data paths to the SAN. Being new to the Nexus, I'm not sure what the best practice/configuration is for that.
Any suggestions on reading materials or best practice configurations would be appreciated!
Thanks...
Ted

We recently implemented Nexus 7010s, 5020s, and 2248s in our data center. Now we would like to harden them from a security persective; are there any Best Practices available for hardening Nexus devices?
Hi Carl,
I dont think a specifc hardening document has been realsed but yes you can refer the generic ios based hardening and try with NX-OS which are all supported or not.
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080120f48.shtml
Hope to Help !!
Ganesh.H
Remeber to rate the helpful post

Find ASM DEVICES Mapping

Hello,
If oracleasm fail to scan/list disks then how can we find that which devices asm disks mapped on to.
Thanks,
P.Sran

Hi,
while I am not too sure that I understand the question correctly as well, I would dare to kind of contradict to my colleagues answering one should check the ASM diskstring. And that is because, as far as I understood, you have an issue with Oracle ASM not scanning / listing the disks. Well, that could be, because of the Diskstring. However, it could very well be that the ASM instance would not start up correctly for some reason. Thus, no ASM diskstring to set. However, the kfod command (in the ASM home) might help you in this situation:
[ASM]> kfod disks=all
Disk Size Path
================================================================================
1: 34726 Mb /dev/raw/raw1
2: 34726 Mb /dev/raw/raw2
3: 34177 Mb /dev/raw/raw3
4: 34177 Mb /dev/raw/raw4
ORACLE_SID ORACLE_HOME
================================================================================
+ASM2 /ora/base/product/11g/racdb
+ASM1 /ora/base/product/11g/racdb
Maybe that helps!? Thanks.

Mapping onto Solaris 10 projects in an MP configuration

I have the scenario where we have a Tuxedo 8.1 MP application running on 3 nodes in a virtual environment. The challenge is to map the user to a Solaris 1o "project" with sufficient kernel parameters. This is not an issue on the master node as we can run "newtask -p <project>" in a script prior to running tmboot. However the remote nodes run out of kernel as I haven't found a way to map the remote node to an appropriate project. I have tried entering "newtask -p <project>" into the ENVFILE but that doesn't seem to work.

SOLVED:
Disabled ECC in the bios (though Windows and Gentoo Linux show now trouble whatsoever with my ECC memory, solaris doesn't like it)

How to write ACPI device driver for Solaris 8 (SPARC Edition)

Hi, All,
I wonder how to write ACPI driver to access battery life,
can anyone help ? thanks!!

I am having the similar problem identified in this thread.
OS: Sun Solaris 10 01/06
Hardware: Sun Blade 2500
PCI Memory card.
Problem: When driver moves more then 40 bytes via PIO from a PCI device memory card, the long words are swapped starting at 40 byte transfer size and greater.
device memory description:
static ddi_device_acc_attr_t sdram_access_attr =
DDI_DEVICE_ATTR_V0, /* Boilerplate value */
DDI_STRUCTURE_LE_ACC,
DDI_STRICTORDER_ACC /* Don't reorder accesses */
The user application does a read call, which goes to xxread. xxread calls physio( xxstrategy, bp, dev, B_READ, xxminphys, uio );
In xxstrategy the transfer is done using
ddi_mem_rep_get8(ucb->ucb_sdram_accHndl,
(uint8_t*) kaddr,
(uint8_t*) raddr,
(size_t) bp->b_resid),
(uint_t) DDI_DEV_AUTOINCR );
PCI Device memory is loaded with incrementing address (8bit), 0,1,2... This is confirmed using a PCI Bus Analyzer.
A read of 36 bytes or less returns:
03 02 01 00 07 06 05 04 ...
A read of 40 bytes returns:
07 06 05 04 03 02 01 00 ...
If I peek 1 byte at a time using ddi_get8(ucb->ucb_sdram_accHndl, ...) I get
00 01 02 03 04 05 06 07
Why are the long words swapped starting at 40 byte transfer size and greater?

ISCSI device mapping on Solaris 10

Similar Messages

Maybe you are looking for