From: Xishi Qiu <qiuxishi@huawei.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: does anyone have seen this bug? reset_interrupt+0x82/0xa0 [floppy]
Date: Tue, 16 May 2017 14:40:51 +0800 [thread overview]
Message-ID: <591A9EF3.2050905@huawei.com> (raw)
2017-05-12T04:46:36.373001+08:00[^[[32m OK ^[[0m] Reached target System Initialization.
2017-05-12T04:46:36.385253+08:00[^[[32m OK ^[[0m] Reached target Basic System.
2017-05-12T04:46:43.049936+08:00[ 25.839157] BUG: unable to handle kernel [ 25.841509] floppy0: no floppy controllers found
2017-05-12T04:46:43.597615+08:00NULL pointer dereference[ 25.841740] work still pending
2017-05-12T04:46:44.376251+08:00 at 0000000000000010
2017-05-12T04:46:44.621685+08:00[ 27.413928] IP: [<ffffffffa00048d2>] reset_interrupt+0x82/0xa0 [floppy]
2017-05-12T04:46:45.324827+08:00[ 28.117060] PGD 0
2017-05-12T04:46:45.615632+08:00[ 28.407879] Oops: 0000 [#1] SMP
2017-05-12T04:46:45.710419+08:00[ 28.501984] Modules linked in: virtio(+) crc32c_intel(+) floppy(+)
2017-05-12T04:46:45.899891+08:00[ 28.692147] CPU: 13 PID: 159 Comm: kworker/u32:1 Not tainted 3.10.0-327.28.56.6.x86_64 #1
2017-05-12T04:46:46.187787+08:00[ 28.980030] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.1-0-gb3ef39f-20170509_142013-build9a64a246a222 04/01/2014
2017-05-12T04:46:46.597071+08:00[ 29.385246] Workqueue: floppy reset_interrupt [floppy]
2017-05-12T04:46:46.785518+08:00[ 29.577762] task: ffff880425fe6780 ti: ffff880425840000 task.ti: ffff880425840000
2017-05-12T04:46:47.059479+08:00[ 29.851728] RIP: 0010:[<ffffffffa00048d2>] [<ffffffffa00048d2>] reset_interrupt+0x82/0xa0 [floppy]
2017-05-12T04:46:47.473387+08:00[ 30.231355] RSP: 0018:ffff880425843e18 EFLAGS: 00010202
2017-05-12T04:46:47.695370+08:00[ 30.487624] RAX: 0000000000000000 RBX: ffffffffa000b180 RCX: dead000000200200
2017-05-12T04:46:47.886238+08:00[ 30.678467] RDX: 0000000000000000 RSI: 0000000000c200c0 RDI: ffffffffa0009828
2017-05-12T04:46:48.054132+08:00[ 30.846395] RBP: ffff880425843e18 R08: ffffffffa000b188 R09: 00017ffcda00b180
2017-05-12T04:46:48.216490+08:00[ 31.008753] R10: 00017ffcda00b180 R11: 00000000000003ff R12: ffff880428845880
2017-05-12T04:46:48.417821+08:00[ 31.210077] R13: ffff880429178c00 R14: ffff880425236a00 R15: 0000000000000400
2017-05-12T04:46:48.565850+08:00[ 31.358107] FS: 0000000000000000(0000) GS:ffff88042f540000(0000) knlGS:0000000000000000
2017-05-12T04:46:48.969712+08:00[ 31.761961] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2017-05-12T04:46:49.527370+08:00[ 32.319621] CR2: 0000000000000010 CR3: 000000042569b000 CR4: 00000000001407e0
2017-05-12T04:46:49.996451+08:00[ 32.788704] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
2017-05-12T04:46:50.008769+08:00[ 32.801019] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
2017-05-12T04:46:50.025615+08:00[ 32.817840] Stack:
2017-05-12T04:46:50.033198+08:00[ 32.825441] ffff880425843e60 ffffffff8109d8ab 0000000129178c18 0000000000000000
2017-05-12T04:46:50.058276+08:00[ 32.850530] ffff880429178c18 ffff8804288458b0 ffff880425fe6780 ffff880428845880
2017-05-12T04:46:50.088493+08:00[ 32.880752] ffff880429178c00 ffff880425843ec0 ffffffff8109e67b ffff880425843fd8
2017-05-12T04:46:50.116903+08:00[ 32.909158] Call Trace:
2017-05-12T04:46:50.126325+08:00[ 32.918578] [<ffffffff8109d8ab>] process_one_work+0x17b/0x470
2017-05-12T04:46:50.135293+08:00[ 32.927550] [<ffffffff8109e67b>] worker_thread+0x11b/0x400
2017-05-12T04:46:50.144728+08:00[ 32.936983] [<ffffffff8109e560>] ? rescuer_thread+0x400/0x400
2017-05-12T04:46:50.174593+08:00[ 32.966841] [<ffffffff810a5dbf>] kthread+0xcf/0xe0
2017-05-12T04:46:50.189138+08:00[ 32.981394] [<ffffffff810b4ca6>] ? finish_task_switch+0x56/0x180
2017-05-12T04:46:50.197718+08:00[ 32.989977] [<ffffffff810a5cf0>] ? kthread_create_on_node+0x140/0x140
2017-05-12T04:46:50.208049+08:00[ 33.000291] [<ffffffff81652418>] ret_from_fork+0x58/0x90
2017-05-12T04:46:50.216998+08:00[ 33.009262] [<ffffffff810a5cf0>] ? kthread_create_on_node+0x140/0x140
2017-05-12T04:46:50.227458+08:00[ 33.019717] Code: c7 c2 0d 88 00 a0 48 c7 c6 10 81 00 a0 48 c7 c7 2b 89 00 a0 31 c0 e8 cc 72 63 e1 eb a9 48 8b 05 ad 8d 00 00 48 c7 c7 28 98 00 a0 <48> 8b 70 10 31 c0 e8 b1 72 63 e1 48 8b 05 94 8d 00 00 ff 50 10
2017-05-12T04:46:51.568674+08:00[ 34.360929] RIP [<ffffffffa00048d2>] reset_interrupt+0x82/0xa0 [floppy]
2017-05-12T04:46:52.196079+08:00[ 34.988324] RSP <ffff880425843e18>
2017-05-12T04:46:52.212738+08:00[ 35.004995] CR2: 0000000000000010
2017-05-12T04:46:52.229520+08:00[ 35.021777] ---[ end trace 9881c03b6b437287 ]---
2017-05-12T04:46:52.253266+08:00[ 35.045520] Kernel panic - not syncing: Fatal exception
reply other threads:[~2017-05-16 6:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=591A9EF3.2050905@huawei.com \
--to=qiuxishi@huawei.com \
--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 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.