All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-serial@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Sean Young <sean@mess.org>, Matthias Brugger <mbrugger@suse.com>,
	linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [serial8250_interrupt] RIP: 0010:arch_local_irq_restore+0x2/0x8
Date: Thu, 23 Nov 2017 07:36:23 +0800	[thread overview]
Message-ID: <20171122233623.7ud3wvtuemfvl3t3@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <1511275154.25007.349.camel@linux.intel.com>

On Tue, Nov 21, 2017 at 04:39:14PM +0200, Andy Shevchenko wrote:
>On Tue, 2017-11-21 at 21:31 +0800, Fengguang Wu wrote:
>> On Tue, Nov 21, 2017 at 08:33:57PM +0800, Fengguang Wu wrote:
>> > Hello,
>> >
>> > FYI this happens in mainline kernel 4.14.0-02748-gabc36be.
>> > It shows up since v4.13 .
>>
>> Sorry it actually also shows up in 4.10:
>
>This one means that interrupt storm is occurred. Last time I saw that
>was by the fact of some specific IOAPIC configuration when DMA for UART
>was enabled.
>
>I'm pretty sure that is not the case here. Though, it would be nice to
>see link to the following files:

It's basically a KVM machine. This is adapted from the reproduce
script attached in the first email: 

kvm=(
        qemu-system-x86_64
        -enable-kvm
        -cpu IvyBridge
        -kernel $kernel
        -initrd initrd.img
        -m 1536
        -smp 2
        -device e1000,netdev=net0
        -netdev user,id=net0,hostfwd=tcp::23406-:22
        -boot order=nc
        -no-reboot
        -watchdog i6300esb
        -watchdog-action debug
        -rtc base=localtime
        -drive file=disk-vm-ivb41-1G-7-0,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-1,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-2,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-3,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-4,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-5,media=disk,if=virtio
        -serial stdio
        -display none
        -monitor null
)

append=(
        ip=::::vm-ivb41-1G-7::dhcp
        root=/dev/ram0
        user=lkp
        job=/job-script
        ARCH=x86_64
        kconfig=x86_64-allyesdebian
        branch=linus/master
        commit=abc36be236358162202e86ad88616ff95a755101
        BOOT_IMAGE=/pkg/linux/x86_64-allyesdebian/gcc-6/abc36be236358162202e86ad88616ff95a755101/vmlinuz-4.14.0-02748-gabc36be
        max_uptime=600
        RESULT_ROOT=/result/boot/1/vm-ivb41-1G/debian-x86_64-2016-08-31.cgz/x86_64-allyesdebian/gcc-6/abc36be236358162202e86ad88616ff95a755101/0
        result_service=tmpfs
        debug
        apic=debug
        sysrq_always_enabled
        rcupdate.rcu_cpu_stall_timeout=100
        net.ifnames=0
        printk.devkmsg=on
        panic=-1
        softlockup_panic=1
        nmi_watchdog=panic
        oops=panic
        load_ramdisk=2
        prompt_ramdisk=0
        drbd.minor_count=8
        systemd.log_level=err
        ignore_loglevel
        console=tty0
        earlyprintk=ttyS0,115200
        console=ttyS0,115200
        vga=normal
        rw
)

Thanks,
Fengguang

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: lkp@lists.01.org
Subject: Re: [serial8250_interrupt] RIP: 0010:arch_local_irq_restore+0x2/0x8
Date: Thu, 23 Nov 2017 07:36:23 +0800	[thread overview]
Message-ID: <20171122233623.7ud3wvtuemfvl3t3@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <1511275154.25007.349.camel@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2691 bytes --]

On Tue, Nov 21, 2017 at 04:39:14PM +0200, Andy Shevchenko wrote:
>On Tue, 2017-11-21 at 21:31 +0800, Fengguang Wu wrote:
>> On Tue, Nov 21, 2017 at 08:33:57PM +0800, Fengguang Wu wrote:
>> > Hello,
>> >
>> > FYI this happens in mainline kernel 4.14.0-02748-gabc36be.
>> > It shows up since v4.13 .
>>
>> Sorry it actually also shows up in 4.10:
>
>This one means that interrupt storm is occurred. Last time I saw that
>was by the fact of some specific IOAPIC configuration when DMA for UART
>was enabled.
>
>I'm pretty sure that is not the case here. Though, it would be nice to
>see link to the following files:

It's basically a KVM machine. This is adapted from the reproduce
script attached in the first email: 

kvm=(
        qemu-system-x86_64
        -enable-kvm
        -cpu IvyBridge
        -kernel $kernel
        -initrd initrd.img
        -m 1536
        -smp 2
        -device e1000,netdev=net0
        -netdev user,id=net0,hostfwd=tcp::23406-:22
        -boot order=nc
        -no-reboot
        -watchdog i6300esb
        -watchdog-action debug
        -rtc base=localtime
        -drive file=disk-vm-ivb41-1G-7-0,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-1,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-2,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-3,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-4,media=disk,if=virtio
        -drive file=disk-vm-ivb41-1G-7-5,media=disk,if=virtio
        -serial stdio
        -display none
        -monitor null
)

append=(
        ip=::::vm-ivb41-1G-7::dhcp
        root=/dev/ram0
        user=lkp
        job=/job-script
        ARCH=x86_64
        kconfig=x86_64-allyesdebian
        branch=linus/master
        commit=abc36be236358162202e86ad88616ff95a755101
        BOOT_IMAGE=/pkg/linux/x86_64-allyesdebian/gcc-6/abc36be236358162202e86ad88616ff95a755101/vmlinuz-4.14.0-02748-gabc36be
        max_uptime=600
        RESULT_ROOT=/result/boot/1/vm-ivb41-1G/debian-x86_64-2016-08-31.cgz/x86_64-allyesdebian/gcc-6/abc36be236358162202e86ad88616ff95a755101/0
        result_service=tmpfs
        debug
        apic=debug
        sysrq_always_enabled
        rcupdate.rcu_cpu_stall_timeout=100
        net.ifnames=0
        printk.devkmsg=on
        panic=-1
        softlockup_panic=1
        nmi_watchdog=panic
        oops=panic
        load_ramdisk=2
        prompt_ramdisk=0
        drbd.minor_count=8
        systemd.log_level=err
        ignore_loglevel
        console=tty0
        earlyprintk=ttyS0,115200
        console=ttyS0,115200
        vga=normal
        rw
)

Thanks,
Fengguang

  parent reply	other threads:[~2017-11-22 23:36 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  9:05 active bugs in the first week of 4.15 merge window Fengguang Wu
2017-11-21 10:04 ` [test_abba] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 10:04   ` Fengguang Wu
2017-11-21 10:54 ` [ata_port_detach] WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6613 ata_port_detach+0x9b/0x180 Fengguang Wu
2017-11-21 10:54   ` Fengguang Wu
2017-11-21 11:30   ` Arnd Bergmann
2017-11-21 11:30     ` Arnd Bergmann
2017-11-21 11:07 ` [tracer_init_tracefs] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1] Fengguang Wu
2017-11-21 11:07   ` Fengguang Wu
2017-11-21 12:27   ` Fengguang Wu
2017-11-21 12:27     ` Fengguang Wu
2017-11-21 13:55     ` Thomas Gleixner
2017-11-21 13:55       ` Thomas Gleixner
2017-11-21 11:10 ` [rbtree_test_init] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1] Fengguang Wu
2017-11-21 11:10   ` Fengguang Wu
2017-11-21 21:59   ` Andrew Morton
2017-11-21 21:59     ` Andrew Morton
2017-11-22  2:15     ` Fengguang Wu
2017-11-22  2:15       ` Fengguang Wu
2017-11-21 11:19 ` [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 62s! Fengguang Wu
2017-11-21 11:19   ` Fengguang Wu
2017-11-21 11:52   ` [test_rht_init] INFO: task swapper/0:1 blocked for more than 120 seconds Fengguang Wu
2017-11-21 11:52     ` Fengguang Wu
2017-11-27 21:34     ` Linus Torvalds
2017-11-27 21:34       ` Linus Torvalds
2017-11-27 21:32   ` [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 62s! Linus Torvalds
2017-11-27 21:32     ` Linus Torvalds
2017-11-21 11:53 ` [vga_arb_device_init] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 11:53   ` Fengguang Wu
2017-11-21 16:52   ` Lukas Wunner
2017-11-21 16:52     ` Lukas Wunner
2017-11-21 16:52     ` Lukas Wunner
2017-11-22  9:07     ` Daniel Vetter
2017-11-22  9:07       ` Daniel Vetter
2017-11-22  9:07       ` Daniel Vetter
2017-11-21 17:08   ` [char-misc] " Daniel Vetter
2017-11-21 17:08     ` Daniel Vetter
2017-11-21 12:04 ` [migration_cpu_stop] WARNING: CPU: 0 PID: 11 at kernel/sched/core.c:1187 set_task_cpu+0x257/0x6b6 Fengguang Wu
2017-11-21 12:04   ` Fengguang Wu
2017-11-21 13:34   ` Peter Zijlstra
2017-11-21 13:34     ` Peter Zijlstra
2017-11-21 13:51     ` Fengguang Wu
2017-11-21 13:51       ` Fengguang Wu
2017-11-21 16:13       ` Paul E. McKenney
2017-11-21 16:13         ` Paul E. McKenney
2017-11-22 12:18         ` Fengguang Wu
2017-11-22 12:18           ` Fengguang Wu
2017-11-21 14:01     ` Rafael J. Wysocki
2017-11-21 14:01       ` Rafael J. Wysocki
2017-11-21 12:09 ` [ata_port_probe] BUG: unable to handle kernel NULL pointer dereference at 0000000000000350 Fengguang Wu
2017-11-21 12:09   ` Fengguang Wu
2017-11-21 12:19   ` Fengguang Wu
2017-11-21 12:19     ` Fengguang Wu
2017-11-21 12:54     ` Arnd Bergmann
2017-11-21 12:54       ` Arnd Bergmann
2017-11-21 14:57       ` Tejun Heo
2017-11-21 14:57         ` Tejun Heo
2017-11-21 15:30         ` Arnd Bergmann
2017-11-21 15:30           ` Arnd Bergmann
2017-11-21 12:12 ` [RING_BUFFER_BENCHMARK] INFO: task rb_producer:73 blocked for more than 120 seconds Fengguang Wu
2017-11-21 13:28   ` Fengguang Wu
2017-11-21 13:28     ` Fengguang Wu
2017-11-21 12:33 ` [serial8250_interrupt] RIP: 0010:arch_local_irq_restore+0x2/0x8 Fengguang Wu
2017-11-21 12:33   ` Fengguang Wu
2017-11-21 12:33   ` Fengguang Wu
2017-11-21 13:31   ` Fengguang Wu
2017-11-21 13:31     ` Fengguang Wu
2017-11-21 14:39     ` Andy Shevchenko
2017-11-21 14:39       ` Andy Shevchenko
2017-11-21 21:14       ` Andy Shevchenko
2017-11-21 21:14         ` Andy Shevchenko
2017-11-22 23:36       ` Fengguang Wu [this message]
2017-11-22 23:36         ` Fengguang Wu
2017-11-22 23:43         ` Fengguang Wu
2017-11-22 23:43           ` Fengguang Wu
2017-11-21 12:41 ` [e1000_shutdown] e1000 0000:00:03.0: disabling already-disabled device Fengguang Wu
2017-11-21 12:41   ` Fengguang Wu
2017-11-21 12:41   ` [Intel-wired-lan] " Fengguang Wu
2017-11-21 22:10   ` Tushar Dave
2017-11-21 22:10     ` Tushar Dave
2017-11-21 22:10     ` [Intel-wired-lan] " Tushar Dave
2017-11-22 23:13     ` Fengguang Wu
2017-11-22 23:13       ` Fengguang Wu
2017-11-22 23:13       ` [Intel-wired-lan] " Fengguang Wu
2017-11-27 19:31       ` Tushar Dave
2017-11-27 19:31         ` Tushar Dave
2017-11-27 19:31         ` [Intel-wired-lan] " Tushar Dave
2017-12-04 11:33         ` Fengguang Wu
2017-12-04 11:33           ` Fengguang Wu
2017-12-04 11:33           ` [Intel-wired-lan] " Fengguang Wu
2017-12-05 19:19           ` Tushar Dave
2017-12-05 19:19             ` Tushar Dave
2017-12-05 19:19             ` [Intel-wired-lan] " Tushar Dave
2017-11-21 12:50 ` [test_cycle_work] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 12:50   ` Fengguang Wu
2017-11-21 13:01 ` [hrtimer_active] INFO: trying to register non-static key Fengguang Wu
2017-11-21 13:01   ` Fengguang Wu
2017-11-22 14:37   ` [hrtimer_active ^W ata_port_wait_eh] " Thomas Gleixner
2017-11-22 14:37     ` Thomas Gleixner
2017-11-24 12:49     ` Tejun Heo
2017-11-24 12:49       ` Tejun Heo
2017-11-24 13:41       ` Fengguang Wu
2017-11-24 13:41         ` Fengguang Wu

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=20171122233623.7ud3wvtuemfvl3t3@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mbrugger@suse.com \
    --cc=sean@mess.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.