Javen,
Here are some questions
(1) When I unload the driver "#rem_drv mydriver", the intr resources
have been removed "ddi_intr_remove_handler()" and free. Then driver
calls "_fini()" successfully. Then kernel "panic" on a thread -
"thread_intr_creat()". When I enable "kmem_flags= 0xf", I didn't see
memory fault be caught. Why all interrupt resources have been removed
but still kernel still want to dispatch interrupt to mydriver?
(2) Last time, you mentioned that, in my case, I don't need to care about
which driver thread (sd or ses) is running. But I found that sometimes
there is no more command down after several inquiry commands and no device
link but sometimes I can see "/[EMAIL PROTECTED],0/pci8086,[EMAIL
PROTECTED]/[EMAIL PROTECTED],[EMAIL PROTECTED]/[EMAIL PROTECTED],0" or
"ses0 is /[EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci1103,[EMAIL
PROTECTED]/[EMAIL PROTECTED],0" and it pops up several
device link like "/dev/dsk/c4d0s0" after driver installation. I can make
sure
that all inquiry commands been returned with success (scsi_hba_probe()= 0)
on
existing disk channel. What's possible cause of this ?
Thanks
Steve
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
