Bad page state in qemu-system-x86 process

Bug #1602443 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned
qemu (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

---Problem Description---
BUG: Bad page state in process qemu-system-x86

[ 2284.443389] Call Trace:
[ 2284.443398] [<ffffffff813eb1a3>] dump_stack+0x63/0x90
[ 2284.443404] [<ffffffff811924ae>] bad_page.part.68+0xae/0x100
[ 2284.443408] [<ffffffff81192ef6>] free_pages_prepare+0x2e6/0x310
[ 2284.443413] [<ffffffff811fe2c1>] ? uncharge_list+0xc1/0xd0
[ 2284.443417] [<ffffffff81195345>] free_hot_cold_page+0x35/0x1c0
[ 2284.443422] [<ffffffff8119db40>] put_page+0x40/0x50
[ 2284.443428] [<ffffffff8124a367>] dio_bio_complete+0x77/0xc0
[ 2284.443432] [<ffffffff8124cf0f>] do_blockdev_direct_IO+0x23bf/0x3410
[ 2284.443435] [<ffffffff81190407>] ? mempool_free_slab+0x17/0x20
[ 2284.443440] [<ffffffff81247b80>] ? I_BDEV+0x20/0x20
[ 2284.443443] [<ffffffff8124dfa3>] __blockdev_direct_IO+0x43/0x50
[ 2284.443447] [<ffffffff81248628>] blkdev_direct_IO+0x58/0x80
[ 2284.443461] [<ffffffff8118f4fb>] generic_file_read_iter+0x47b/0x5c0
[ 2284.443465] [<ffffffff810ef329>] ? hrtimer_cancel+0x19/0x20
[ 2284.443472] [<ffffffff811008a6>] ? futex_wait+0x206/0x280
[ 2284.443476] [<ffffffff812489f5>] blkdev_read_iter+0x35/0x40
[ 2284.443482] [<ffffffff8120c9ac>] do_iter_readv_writev+0x6c/0xa0
[ 2284.443486] [<ffffffff8120d52f>] do_readv_writev+0x18f/0x230
[ 2284.443492] [<ffffffff810ac0b0>] ? wake_up_q+0x70/0x70
[ 2284.443496] [<ffffffff8120d606>] vfs_readv+0x36/0x50
[ 2284.443501] [<ffffffff8120e4e5>] SyS_preadv+0xc5/0xe0

There are VMs running on qemu/kvm with root fs mounted from AoE storage volumes.

Contact Information = John Keenleyside <email address hidden>; David Wright <email address hidden>

---uname output---
Linux h0102-u07 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Machine Type = Supermicro SYS-1028U-TNRTP+

The reporter was requested to provide recreation steps and sosreport and also report the problem in parallel with Supermicro.

Revision history for this message
bugproxy (bugproxy) wrote : dmesg output

Default Comment by Bridge

tags: added: architecture-x8664 bugnameltc-143506 severity-medium targetmilestone-inin16041
Changed in ubuntu:
assignee: nobody → Taco Screen team (taco-screen-team)
affects: ubuntu → qemu (Ubuntu)
Luciano Chavez (lnx1138)
Changed in qemu (Ubuntu):
assignee: Taco Screen team (taco-screen-team) → nobody
Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in qemu (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.