public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: James Dingwall <james@dingwall.me.uk>, linux-kernel@vger.kernel.org
Subject: Re: xen/evtchn.c: Interrupt for port 32, but apparently not enabled; per-user 0000000012b765d1
Date: Wed, 24 Jul 2024 15:55:40 +0200	[thread overview]
Message-ID: <bf1f5bfa-446c-4aea-a092-8cd9e7a786c3@suse.com> (raw)
In-Reply-To: <ZqEA5BnhTYsxMq/f@dingwall.me.uk>


[-- Attachment #1.1.1: Type: text/plain, Size: 910 bytes --]

On 24.07.24 15:25, James Dingwall wrote:
> Hi,
> 
> I have built a kernel derived from Ubuntu's Ubuntu-hwe-6.8-6.8.0-40.40_22.04.1
> tag.  The logs are quiet until I start the first guest which has two network
> cards passed through.  At this point the kernel log gets flooded with the
> warning below.  This appears to the same warning which this commit was
> supposed to suppress:
> 
> 51c23bd691c0f1fb95b29731c356c6fd69925d17: xen/evtchn: avoid WARN() when unbinding an event channel
> 
> The tag already includes that commit and in my config:
> 
> $ grep CONFIG_DEBUG_SHIRQ /boot/config-6.8.0-40-generic
> # CONFIG_DEBUG_SHIRQ is not set
> 
> Could there be a related change which also needs to be picked or is there
> the possibility that there is another trigger?

As the original reporter of the issue tested the patch to fix it,
there seems to be another trigger. :-(


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2024-07-24 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 13:25 xen/evtchn.c: Interrupt for port 32, but apparently not enabled; per-user 0000000012b765d1 James Dingwall
2024-07-24 13:55 ` Juergen Gross [this message]
2024-07-25  8:19   ` James Dingwall
2024-07-25 13:50   ` James Dingwall
2024-07-28 14:27   ` James Dingwall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf1f5bfa-446c-4aea-a092-8cd9e7a786c3@suse.com \
    --to=jgross@suse.com \
    --cc=james@dingwall.me.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox