On Fri, 17 Nov 2000 10:30:02 PST, John Baldwin wrote: > # sysctl -w debug.ktr_verbose=1 ; command_that_makes_my_machine_go_boom All very well and good once you've figured out which command makes your machine go boom. But as I said, the locks I'm getting appear completely arbitrary. I'm no hard-core hacker, but I'm not completely clueless when it comes to isolating problems by way of deductive reasoning, and I'm stumped as to what's causing these. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: CURRENT is freezing again ... Kris Kennaway
- Re: CURRENT is freezing again ... Kris Kennaway
- Re: CURRENT is freezing again ... Mark Murray
- Re: CURRENT is freezing again ... Warner Losh
- Re: CURRENT is freezing again ... Poul-Henning Kamp
- Re: CURRENT is freezing again ... Warner Losh
- Re: CURRENT is freezing again ... Mike Smith
- Re: CURRENT is freezing again ... Wilko Bulte
- Re: CURRENT is freezing again ... Andrew Gallatin
- Re: CURRENT is freezing again ... John Baldwin
- Re: CURRENT is freezing again ... Sheldon Hearn
- Re: CURRENT is freezing again ... John Baldwin
- Re: CURRENT is freezing again ... Michael Harnois
- Re: CURRENT is freezing again ... Mark Huizer
- RE: CURRENT is freezing again ... John Baldwin
- Re: CURRENT is freezing again ... Soren Schmidt
- Re: CURRENT is freezing again ... Michael C . Wu
- Re: CURRENT is freezing again ... Soren Schmidt
- missing interrupts (was Re: CURRENT is freezing again ..... Andrew Gallatin
- Re: missing interrupts (was Re: CURRENT is freezing... Bruce Evans
- Re: missing interrupts (was Re: CURRENT is free... Andrew Gallatin