> > Besides the obvious need to fix this one problem, shouldn't we > > ASSERT ih->ih_handler != NULL before calling it? > > It isn't null in this case, it is 0xdeadc0de. Can you try a pre-preemption > kernel and see if that fixes it? *BLUSH* Of course ehehe ;-) Ok, I will. Can you give me a date I should try going back to, without kernel getting out of sync with my world? Bye, Andrea -- Yes, I've heard of "decaf." What's your point? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Kernel Panic from Yesterday's CVSup Crist J. Clark
- RE: Kernel Panic from Yesterday's CVSup John Baldwin
- Re: Kernel Panic from Yesterday's CVSup Jim Bloom
- Re: Kernel Panic from Yesterday's CVSup Andrea Campi
- Re: Kernel Panic from Yesterday's CVS... John Baldwin
- Re: Kernel Panic from Yesterday'... Mark Murray
- Re: Kernel Panic from Yesterday'... Andrea Campi
- Re: Kernel Panic from Yester... Andrea Campi
- Re: Kernel Panic from Ye... John Baldwin
- Re: Kernel Panic from Ye... Andrea Campi
- Re: Kernel Panic from Ye... John Baldwin
- Re: Kernel Panic from Ye... Andrea Campi
- Re: Kernel Panic from Ye... Andrea Campi
- Re: Kernel Panic from Ye... Jake Burkholder
- Re: Kernel Panic from Ye... Andrea Campi
- Re: Kernel Panic from Ye... John Baldwin
- Re: Kernel Panic from Ye... Andrea Campi
- Re: Kernel Panic from Ye... Alexander N. Kabaev
- Re: Kernel Panic from Ye... Jake Burkholder
- Re: Kernel Panic from Ye... Andrea Campi