From nobody Sat Dec 28 18:35:32 2024 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YL9z92JGCz5j1Xp for ; Sat, 28 Dec 2024 18:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YL9z91Bkvz4wL8 for ; Sat, 28 Dec 2024 18:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1735410933; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xvi7nyB7JPhaKtNWXregerqXcC1ENOJ5yY1kFQC5Ix8=; b=YUJUDEM69vzroaKw8eDkPngQ0oMCYyLj7ytDsDfq0Pxp7vsBJPn/f3NXM/MXLli5vxkBDx zidWJSWtV35aqLGZZkDsyi50vLkIUnqUaf5FoxL5f5Iczc0ItyxKSipoP0uxsm7z9gFie/ PmgVcazY+YGUDATU86ZpGiMQQCRXchXIyfk1N4M01QJoKRzxetrH1+ubqK33UmaMTni8uL w7JuHBXQrCEXqW9fjb4xsz9cfaZ66SBvhX1CRNRZ0yhURcDk27Ui9F3yvsgaPvGomGLej9 d75vItlAvdx25cLR1jir/rEkrpYiqB1vR5aCMPtNmWKOY+D+dnTh/kxim9F7wg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1735410933; a=rsa-sha256; cv=none; b=RhpyB2kWJ0Zr6h1Arq/iy7Kf/CAKq8/RoZaYNwP3ZvamOkI+HT7jLzmehKa964y+UutEeW +hbLlsbYRdUq/EXXbcLsMF5WSQGt3YQ9L+E/ZCPk6pqgT1N1lAnjXDd4s55ULqsAN9g3Zy nnFUXEIHAT5nEn5Dpb9vtCik8BsRts+5Wpw8CqWltsn+McvGm/aKihECkxvGHzZKEuARv1 QB4SGeCCc/OE5ZjBdyqITL/dP687UPRt5zAy6x4gq0BqpcpjHLyH3VZZ/fvwCjEdKUIopV RVWA9KUYAKbvXSRcJAUA14dlOjCVEMVTo5318MLtRzrloxFq3Mr2fmXV5t4/Qg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YL9z90pDRzbx6 for ; Sat, 28 Dec 2024 18:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4BSIZWl6013497 for ; Sat, 28 Dec 2024 18:35:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4BSIZWSD013496 for virtualization@FreeBSD.org; Sat, 28 Dec 2024 18:35:32 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 283103] Yet another Parallels arm64 panic Date: Sat, 28 Dec 2024 18:35:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283103 --- Comment #7 from Andriy Gapon --- (In reply to Andrew Turner from comment #3) I've been thinking about sleeping ithreads for another reason, sorry for hijacking this bug report. There could be a chip connected, e.g., via I2C. And that chip could also be capable of generating a signal (an interrupt) v= ia a GPIO line. It's not a problem to configure the GPIO interrupt but it may become a prob= lem if the interrupt handler needs to access the chip via a bus that requires waiting / sleeping. I think that at present the described setup can only work if we force the b= us to spinning / polling but that may be sub-optimal. --=20 You are receiving this mail because: You are the assignee for the bug.=