Hi Tom,

Can you post prtconf and prtconf -D output?
I suspect the bofi-nexus entry in bofi.conf is not correct.

max

tom60 wrote:
Hi Alta,

I have not got any help yet.

I am testing motherboard "igb" driver. Here is the drvconfig result which was done on a x86 server running nv119.

bash-3.2# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
       inet 127.0.0.1 netmask ff000000
igb0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
       inet 172.17.138.72 netmask fffffe00 broadcast 172.17.139.255
       ether 0:30:48:c3:da:bc
qlge2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
       inet 192.168.43.72 netmask ffffff00 broadcast 192.168.43.255
       ether 0:c0:dd:12:1:58
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
       inet6 ::1/128

bash-3.2# drvconfig -i bofi
drvconfig: driver failed to attach: bofi

bash-3.2# uname -a
SunOS einstein 5.11 snv_119 i86pc i386 i86pc

Tom

bash-3.2# cat /kernel/drv/bofi.conf
#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License, Version 1.0 only
# (the "License").  You may not use this file except in compliance
# with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# or http://www.opensolaris.org/os/licensing.
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [yyyy] [name of copyright owner]
#
# CDDL HEADER END
#
#
# Copyright (c) 2000 by Sun Microsystems, Inc.
# All rights reserved.
#
#ident  "%Z%%M% %I%     %E% SMI"

name="bofi" parent="pseudo";

# The 'bofi-nexus' property specifies the name of the nexus where data accesses # are intercepted. This should be the name of the parent (or ancestor) nexus of
# the driver(s) to be tested.
#bofi-nexus="nexus_to_intercept";
bofi-nexus="pci";

# The 'bofi-to-test' property identifies a list of drivers whose accesses
# should be intercepted, or if each name is preceeded by the ! character a list # of drivers not to test. If any name is not preceeded by this character then # every name is assumed to be the name of a driver to test. If the property
# value is undefined or the empty string then all drivers will be tested.
#bofi-to-test="driver_to_test1 driver_to_test2 ...";
bofi-to-test="igb";

# The 'bofi-ddi-check' property may be set to "on" or "off".  The "on"
# setting causes bofi to validate that the mapped address returned from
# ddi_regs_map_setup(9F) is not used outside the context of DDI data
# access calls.  When set to "off", no validation occurs.
bofi-ddi-check="on";

# The 'bofi-range-check' property may be set to "panic", "warn" or "off".
# The "warn" and "panic" settings cause bofi to validate that requested data # access sizes are consistent with the access handle used to perform the data
# access. The "warn" setting causes warning to be displayed on the system
# console on misuse. The "panic" setting causes the system to panic on misuse.
# When set to "off", no validation occurs.
bofi-range-check="panic";

# The 'bofi-sync-check' property may be set to "on" or "off".  The "on"
# setting causes bofi to validate that the tested drivers are compliant with # respect the use of ddi_dma_sync(9F) calls. When set to "off", no validation
# occurs.
bofi-sync-check="on";
bash-3.2#

--------------------------------------------------
From: "Alta Elstad" <[email protected]>
Sent: Thursday, February 18, 2010 10:33 AM
To: <[email protected]>
Subject: Re: [driver-discuss] Solaris driver hardening test

Tom,

Did you get any help with this?

Has the devlink for the bofi driver been created properly?

Have you tried to manually run something like
drvconfig -i bofi
to get the device nodes created properly?

Please let us know whether you solved your problem.
/alta
--
This message posted from opensolaris.org
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss


_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to