In message: <1129735927.689.37.camel_at_localhost.localdomain> Marten Vijn <info_at_martenvijn.nl> writes: : On Tue, 2005-10-18 at 17:04 -0600, M. Warner Losh wrote: : : 1 ==> Maybe you could also try: : > : > On Sat, 2005-10-15 at 22:21 -0600, M. Warner Losh wrote: : > ...> Please consider applying the following patch. : > <cut> : > and see if that changes anything... : : With or without the patch there is no difference. : : : 2 ==> : > Any chance for a trace? Without it, this is impossible to make : > progress on since it doesn't happen for me here... : : Yes, I would like but I don't know how jet. : : added for debugging to my kernelconfig: : : options KTR : options KTR_ENTRIES=1024 : options KTR_VERBOSE : options KTR_ALQ Actually you need the following: # # Compile with kernel debugger related code. # options KDB # # Enable the ddb debugger backend. # options DDB and when the panic happens, you'll get 'db> ' prompt. Type 'trace' there and report what comes back. WarnerReceived on Wed Oct 19 2005 - 13:30:50 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:45 UTC