On Wed, Feb 18, 2009 at 9:27 PM, Mark Johnson <[email protected]> wrote: > Can you do a > mdb -k > [0]> ::interrupts > [0]> $q >
http://pastebin.com/f4d9f5f5e > > and see if anything is sharing the interrupt with qlc? > > Looks like smart array and usb. This is from booting with nosmp. I'm using CPQary3-1.91-solaris10-i386. I REALLY hope that's not the one causing problems :( > >> Is this enough, or do you still need the output of "findstack" to find >> which driver is trying to attach? > > Yeah, I'd like to see what driver is causing it. > That may be hard, as I'm unable to duplicate it. >From booting with "-B $ZFS-BOOTFS,disable-qlc=true,console=ttya -kd", without nosmp, this is after several more ",10:c" http://pastebin.com/f649adb83 I have no idea how to "see these two threads stuck at the same point?" (what is the reference that is the same after reboots anyway? CMD? THREAD?) Searching for "THREAD: attach_drivers()", I found only one ffffff001300dc60 fffffffffbc5f530 0 0 60 ffffff0347578244 PC: _resume_from_idle+0xfa THREAD: attach_drivers() stack pointer for thread ffffff001300dc60: ffffff001300d7a0 [ ffffff001300d7a0 _resume_from_idle+0xfa() ] swtch+0x160() cv_wait+0x61() ndi_devi_enter+0x68() walk_devs+0xe2() ddi_walk_devs+0x22() pcie`pcie_scan_mps+0x51() pcie`pcie_get_fabric_mps+0x1d() pcie`pcie_init_bus+0x3b3() npe`npe_initchild+0x111() npe`npe_ctlops+0x233() init_node+0x78() i_ndi_config_node+0xfa() i_ddi_attachchild+0x40() i_ddi_attach_node_hierarchy+0x61() attach_driver_nodes+0x59() ddi_hold_installed_driver+0x116() attach_drivers+0x37() thread_start+8() But there's no mod_load there. and then [4]> ffffff001300dc60::findstack -v stack pointer for thread ffffff001300dc60: ffffff001300d7a0 [ ffffff001300d7a0 _resume_from_idle+0xfa() ] ffffff001300d7d0 swtch+0x160() ffffff001300d800 cv_wait+0x61(ffffff0347578244, ffffff0347578158) ffffff001300d840 ndi_devi_enter+0x68(ffffff03475780f0, ffffff001300d854) ffffff001300d8b0 walk_devs+0xe2(ffffff034757b008, fffffffff7a11dc0, ffffff001300d900, 1) ffffff001300d8e0 ddi_walk_devs+0x22(ffffff034757b008, fffffffff7a11dc0, ffffff001300d900) ffffff001300d940 pcie`pcie_scan_mps+0x51(ffffff034757b4d8, ffffff034757b008, ffffff001300d984) ffffff001300d970 pcie`pcie_get_fabric_mps+0x1d(ffffff034757b4d8, ffffff034757b008, ffffff001300d984) ffffff001300d9b0 pcie`pcie_init_bus+0x3b3(ffffff034757b008) ffffff001300da40 npe`npe_initchild+0x111(ffffff034757b008) ffffff001300dac0 npe`npe_ctlops+0x233(ffffff034757b4d8, ffffff034757b4d8, 1, ffffff034757b008, 0) ffffff001300db00 init_node+0x78(ffffff034757b008) ffffff001300db40 i_ndi_config_node+0xfa(ffffff034757b008, 6, 0) ffffff001300db60 i_ddi_attachchild+0x40(ffffff034757b008) ffffff001300dba0 i_ddi_attach_node_hierarchy+0x61(ffffff034757b008) ffffff001300dbe0 attach_driver_nodes+0x59(b8) ffffff001300dc20 ddi_hold_installed_driver+0x116(b8) ffffff001300dc40 attach_drivers+0x37() ffffff001300dc50 thread_start+8() So I decided to reboot again, this time using the same number of ",10:c" in your initial mail, got another THREAD: attach_drivers(), but still no mod_load http://pastebin.com/f1faf9e29 Any ideas? Regards, Fajar _______________________________________________ xen-discuss mailing list [email protected]
