Kyle McDonald wrote:
Hi All,
I've got this 'ips' driver from the SUNWips_nv pkg on the OpenSolaris
ServeRAID project page. I'm trying to get it to work with my ServeRAID
7K card in an IBM x346.
The project page states that the community is working on ServeRAID
4x,5x, and 6x support while Sun is working on ServeRAID 7x and 8x
support, but the page isn't clear as to whether or not the Community and
Sun project teams are working in the same source code, or whether or not
the downloadable pkg contains the work of both teams, or just the
community work.
To compound the confusion, My ServeRAID 7K card actually has the same
PCI ID (pci9005,250) as the ServeRAID 6M, and that is one of the PCI
ID's this package adds to /etc/driver_aliases.
Actually, after browsing the pci.id file in the OS sources, and checking
the output of prtconf, I'm starting to wonder on this last point. The
main pci id of the 7K and 6M are the same, but the other (sub?) ID's
don't match at all. Though according to the prtconf output, they should
be compatible (If I'm reading this correctly.)
pci1014,28e (driver not attached)
Hardware properties:
name='assigned-addresses' type=int items=5
value=820a7010.00000000.d6fff000.00000000.00001000
name='reg' type=int items=10
value=000a7000.00000000.00000000.00000000.00000000.020a7010.00000000.00000000.00000000.00001000
name='compatible' type=string items=7
value='pci9005,250.1014.28e.7' +
'pci9005,250.1014.28e' + 'pci1014,28e' + 'pci9005,250.7' + 'pci9005,250'
+ 'pciclass,010400' + 'pcicl
ass,0104'
name='model' type=string items=1
value='RAID controller'
name='power-consumption' type=int items=2
value=00000001.00000001
.
.
.
I'm not naive enough to expect it to work just because the PCI ID's
match, but it does see to be worth a try. It's not working, but I can't
tell if I've hit the end of the road or if there is more I can do?
When the kernel boots, it prints these messages:
SunOS Release 5.11 Version snv_91 32-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Last shutdown is later than time on time-of-day chip; check date.
Configuring /dev
WARNING: mutex_init: d1089552 is not 4 byte aligned; caller
ips_attach+3ad in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
WARNING: mutex_init: d108955a is not 4 byte aligned; caller
ips_attach+3de in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
WARNING: mutex_init: d108965e is not 4 byte aligned; caller
ips_attach+40f in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
While debugging another problem, I've seen issues with the 32bit kernel
running out of kernel heap. Those prolems disappeared when I switched to
the 64bit kernel, so I thought I'd try that here too. I went and
installed the ips driver into the amd64 x86.miniroot, and tried the
network boot again. this time the kernel spit out more, similiar messages:
Loading kmdb...
Welcome to kmdb
kmdb: unable to determine terminal type: assuming `vt100'
Loaded modules: [ unix krtld genunix ]
[0]> ::cont
SunOS Release 5.11 Version snv_91 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Last shutdown is later than time on time-of-day chip; check date.
Configuring /dev
WARNING: mutex_init: ffffff01d8049a86 is not 8 byte aligned; caller
ips_attach+22b in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
WARNING: mutex_init: ffffff01d8049a8e is not 8 byte aligned; caller
ips_attach+264 in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
WARNING: mutex_init: ffffff01d8049a6c is not 8 byte aligned; caller
ips_attach+27e in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
WARNING: mutex_init: ffffff01d8049b92 is not 8 byte aligned; caller
ips_attach+29e in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
WARNING: mutex_init: ffffff01d8049a7c is not 8 byte aligned; caller
ips_attach+2b8 in module ips. This is unsupported and may cause a panic.
Please report this to the kernel module supplier.
-
1. Solaris Interactive (default)
2. Custom JumpStart
3. Solaris Interactive Text (Desktop session)
4. Solaris Interactive Text (Console session)
5. Apply driver updates
6. Single user shell
Enter the number of your choice.
Selected: 6
Single user shell
Searching for installed OS instances...
Loaded modules: [ scsi_vhci crypto uppc neti sd ptm ufs mpt zfs uhci
hook lofs
ip logindmux usba specfs pcplusmp md random cpu.generic sctp arp ]
kmdb: target stopped at:
kmdb_enter+0xb: movq %rax,%rdi
[4]> ::ptree
fffffffffbc26770 sched
ffffff01ce945a48 fsflush
ffffff01ce9466a8 pageout
ffffff01ce947308 init
ffffff01ce94bdf0 devfsadm
ffffff01ce94ca50 syseventd
ffffff01ce941008 dlmgmtd
ffffff01ce9428c8 svc.configd
ffffff01ce944188 svc.startd
ffffff01ce944de8 install-discover
ffffff01ce941c68 install-recovery
ffffff01ce943528 rootdev
[4]> ::stack
kmdb_enter+0xb()
debug_enter+0x37(0)
abort_sequence_enter+0x35(0)
asy`async_rxint+0x24d(ffffff01cde59680, f9)
asy`asyintr+0xc7(ffffff01cde59680)
av_dispatch_autovect+0x78(4)
dispatch_hilevel+0x1b(4, 0)
switch_sp_and_call+0x13()
do_interrupt+0xdb(ffffff0007fe5b00, 0)
_interrupt+0xba()
i86_mwait+0xd()
cpu_idle_mwait+0x114()
idle+0x10e()
thread_start+8()
[4]>
So, Any ideas what is going wrong here?
Is there any hope, or should I give up now?
-Kyle
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
