From: Jiri Slaby <jslaby@suse.cz>
To: Dmitry Vyukov <dvyukov@google.com>,
devel@driverdev.osuosl.org, arve@google.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)
Date: Mon, 4 Apr 2016 09:55:10 +0200 [thread overview]
Message-ID: <57021DDE.9030102@suse.cz> (raw)
In-Reply-To: <CACT4Y+bFF2GBCZrZ+veXAGm1ZeJNiFAbFRuxNvBM30gSju=aPQ@mail.gmail.com>
On 04/02/2016, 12:35 PM, Dmitry Vyukov wrote:
> Hello,
>
> After updating from 8e0f93cda48ed054e1216bab5c60017e1a5fc1e8 to
> 05cf8077e54b20dddb756eaa26f3aeb5c38dd3cf (Apr 1) I've started seeing
> the following warnings:
>
> genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)
> CPU: 3 PID: 6626 Comm: init Tainted: G W 4.6.0-rc1+ #338
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> ffffffff87eb26a0 ffff88003da17618 ffffffff82c8ea9f ffffffff86f0c740
> fffffbfff0fd64d4 ffff88003e8a6aa8 ffff88005eb4c4c8 00000000fffffff0
> ffffffff874f6be0 ffff880034ae63a8 ffff88003da17708 ffffffff8149e73c
> Call Trace:
> [< inline >] __dump_stack lib/dump_stack.c:15
> [<ffffffff82c8ea9f>] dump_stack+0x12e/0x18f lib/dump_stack.c:51
> [<ffffffff8149e73c>] __setup_irq+0x11fc/0x1610 kernel/irq/manage.c:1369
> [<ffffffff8149ef55>] request_threaded_irq+0x275/0x410 kernel/irq/manage.c:1652
> [< inline >] request_irq include/linux/interrupt.h:147
...
> They appear after boot every 10 seconds.
> I am using qemu. Here are GOLDFISH related .config values:
>
> CONFIG_GOLDFISH=y
> # CONFIG_X86_GOLDFISH is not set
> CONFIG_KEYBOARD_GOLDFISH_EVENTS=y
> CONFIG_GOLDFISH_TTY=y
> CONFIG_BATTERY_GOLDFISH=y
> CONFIG_FB_GOLDFISH=y
> CONFIG_MMC_GOLDFISH=y
> CONFIG_GOLDFISH_AUDIO=y
> CONFIG_MTD_GOLDFISH_NAND=y
> CONFIG_GOLDFISH_BUS=y
> CONFIG_GOLDFISH_PIPE=y
>
> Is it a known issue? How can it be fixed?
This is a conflict between request_irq of goldfish and 8250. Setting
SERIAL_8250_SHARE_IRQ (which is the default) should make the trace gone.
Note that GOLDFISH=y makes sense only if you build a goldfish kernel.
I.e. setting both 8250 and goldfish does not make much sense IIRC.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2016-04-04 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 10:35 Dmitry Vyukov
2016-04-04 7:55 ` Jiri Slaby [this message]
2016-04-04 8:06 ` Dmitry Vyukov
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=57021DDE.9030102@suse.cz \
--to=jslaby@suse.cz \
--cc=arve@google.com \
--cc=devel@driverdev.osuosl.org \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®