tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: mutex_oncpu() called on destroyed mutex?

To: tech-kern%netbsd.org@localhost
Subject: Re: mutex_oncpu() called on destroyed mutex?
From: Edgar Fuß <ef%math.uni-bonn.de@localhost>
Date: Tue, 7 Aug 2018 20:25:04 +0200

> Disabling preemption only affects the CPU that disabled it.
But preemption is *en*abled in the code segment I quoted!

> What's the stack trace of the panic?
mutex_vector_enter() at netbsd:mutex_vector_enter+0x32c
unp_thread() at netbsd:unp_thread+0x2eb

Follow-Ups:
- Re: mutex_oncpu() called on destroyed mutex?
  - From: Edgar Fuß

References:
- repeated panics in mutex_vector_enter (from unp_thread)
  - From: Edgar Fuß
- mutex_oncpu() called on destroyed mutex? (was: repeated panics in mutex_vector_enter (from unp_thread))
  - From: Edgar Fuß
- Re: mutex_oncpu() called on destroyed mutex? (was: repeated panics in mutex_vector_enter (from unp_thread))
  - From: Jason Thorpe

Prev by Date: Re: mutex_oncpu() called on destroyed mutex? (was: repeated panics in mutex_vector_enter (from unp_thread))
Next by Date: Re: panic: biodone2 already
Previous by Thread: Re: mutex_oncpu() called on destroyed mutex? (was: repeated panics in mutex_vector_enter (from unp_thread))
Next by Thread: Re: mutex_oncpu() called on destroyed mutex?
Indexes:

Home | Main Index | Thread Index | Old Index