> > The "-v" option wasn't supposed to fix the problem.
> > The idea is to trace which driver / kernel
> > module is the last before the kernel hang.
> >
> > What are the final three lines printed on the
> > console before the kernel is hanging?
>
> ,ahh. my apology, mybe i'm just too eager to use my
> opensolaris. the last 3 lines were:
>
> cpu0: Intel(r) Celeron(r) CPU 900 @ 2.20GHz
> PCI express-device: pci1039,a...@6,pcie_pci0
> pcie_pci0 is /p...@0,0/pci1039,a...@6
> _
Hmm, what drivers are reported immediately before the cpu0: line?
Was it "ehci", "uhci", "kb8042" and "mouse8042" (= USB and PS/2 drivers) ?
Usually the USB and PS/2 keyboard and mouse drivers are
initialized before the cpu driver; on some systems the
Solaris kernel hangs at this point; sometimes users have been
able to work around this hang by enabling or disabling USB
legacy support in the BIOS.
In case playing with the USB legacy BIOS support doesn't help,
try to boot the kernel with kernel module tracing enabled
moddebug/W 80000000)
see this web page:
http://blogs.sun.com/dmick/entry/diagnosing_kernel_hangs_panics_with
What trace messages are displayed on the console
when the kernel hangs?
When booted with the kernel debugger and "moddebug/W 80000000",
Is it possible to break into the kernel debugger by pressing F1 + A ?
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
