What version of Go are you using (go version)?

$ go version
go version go1.17.8 linux/arm

Does this issue reproduce with the latest release?

It was not tested with 1.18 yet.

What operating system and processor architecture are you using (go env)?

Linux 4.14.114 armv7l

What did you do?

We use the context to signal when to stop the goroutine in various places like shown below.

for {
  select {
    case <-ctx.Done():
	    return nil
    case .... 
  }
}

For a couple of months we randomly get on some of our IoT gateway in the field:

panic: interface conversion: interface {} is bool, not chan struct {}

At the point <-ctx.Done()

Sometimes, it is not a boolean but rather a value attached to the context. But we couldn't identify a pattern yet.

What did you expect to see?

No panic, instead signaling on the done channel.

Hint

I am not 100% but could it be that the done atomic.Value is not 64bit aligned? At least then, we might have issues with our 32bit arm architecture.
https://go-review.googlesource.com/c/go/+/288193/4/src/context/context.go#342

type cancelCtx struct {
	Context

	mu       sync.Mutex            // protects following fields
-->	done     atomic.Value          // of chan struct{}, created lazily, closed by first cancel call
	children map[canceler]struct{} // set to nil by the first cancel call
	err      error                 // set to non-nil by the first cancel call
}