public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 196223] jdb2 journal - hung after suspend-resume test
Date: Fri, 30 Jun 2017 07:41:27 +0000	[thread overview]
Message-ID: <bug-196223-13602-azSAL8DVP6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196223-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=196223

--- Comment #1 from Marta Löfstedt (marta.lofstedt@intel.com) ---
reproduced with 4.12.0-rc7-next-20170630

[ 1209.338769] INFO: task systemd:1 blocked for more than 120 seconds.
[ 1209.338848]       Tainted: G     U  W       4.12.0-rc7-next-20170630 #2
[ 1209.338916] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 1209.338996] systemd         D    0     1      0 0x00000000
[ 1209.339002] Call Trace:
[ 1209.339015]  __schedule+0x3c7/0x830
[ 1209.339022]  ? bit_wait+0x60/0x60
[ 1209.339026]  schedule+0x36/0x80
[ 1209.339031]  io_schedule+0x16/0x40
[ 1209.339036]  bit_wait_io+0x11/0x60
[ 1209.339041]  __wait_on_bit+0x58/0x90
[ 1209.339047]  ? submit_bio+0x73/0x150
[ 1209.339052]  out_of_line_wait_on_bit+0x8e/0xb0
[ 1209.339058]  ? bit_waitqueue+0x40/0x40
[ 1209.339064]  __wait_on_buffer+0x32/0x40
[ 1209.339070]  __ext4_get_inode_loc+0x1b3/0x400
[ 1209.339076]  ext4_iget+0x92/0xbc0
[ 1209.339082]  ext4_iget_normal+0x2f/0x40
[ 1209.339087]  ext4_lookup+0xea/0x270
[ 1209.339091]  lookup_slow+0xa5/0x160
[ 1209.339096]  walk_component+0x1bf/0x370
[ 1209.339099]  ? path_init+0x1e4/0x3a0
[ 1209.339103]  path_lookupat+0x73/0x220
[ 1209.339107]  filename_lookup+0xb8/0x1a0
[ 1209.339113]  ? __check_object_size+0xb3/0x190
[ 1209.339119]  ? strncpy_from_user+0x4d/0x170
[ 1209.339124]  user_path_at_empty+0x36/0x40
[ 1209.339127]  ? user_path_at_empty+0x36/0x40
[ 1209.339132]  vfs_statx+0x83/0xf0
[ 1209.339137]  SYSC_newstat+0x3d/0x70
[ 1209.339144]  ? __do_page_fault+0x266/0x4e0
[ 1209.339149]  SyS_newstat+0xe/0x10
[ 1209.339153]  entry_SYSCALL_64_fastpath+0x1e/0xa9
[ 1209.339157] RIP: 0033:0x7f3dc48a4215
[ 1209.339160] RSP: 002b:00007ffe95210158 EFLAGS: 00000246 ORIG_RAX:
0000000000000004
[ 1209.339164] RAX: ffffffffffffffda RBX: 00007ffe95210360 RCX:
00007f3dc48a4215
[ 1209.339166] RDX: 00007ffe952101f0 RSI: 00007ffe952101f0 RDI:
00007f3dc4938038
[ 1209.339168] RBP: 0000000000000001 R08: 000000512bfda2a0 R09:
0000000000000020
[ 1209.339170] R10: 2ce33e6c02ce33e7 R11: 0000000000000246 R12:
0000000000000000
[ 1209.339172] R13: 0000000000000000 R14: 00007ffe95210370 R15:
000000512bfb9c88

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2017-06-30  7:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  6:11 [Bug 196223] New: jdb2 journal - hung after suspend-resume test bugzilla-daemon
2017-06-30  7:41 ` bugzilla-daemon [this message]
2017-06-30  7:51 ` [Bug 196223] " bugzilla-daemon
2017-06-30 14:55 ` bugzilla-daemon
2017-07-03  6:15 ` bugzilla-daemon
2017-07-03 13:49 ` bugzilla-daemon
2017-07-04  5:56 ` bugzilla-daemon
2017-07-04 22:49 ` bugzilla-daemon
2017-07-05 13:12 ` bugzilla-daemon
2017-07-07  8:20 ` bugzilla-daemon
2017-07-07 14:14 ` bugzilla-daemon
2017-07-08 18:58 ` bugzilla-daemon
2017-07-08 19:22 ` bugzilla-daemon
2017-07-09  5:05 ` bugzilla-daemon
2017-07-09  5:27 ` bugzilla-daemon
2017-07-10  5:04 ` bugzilla-daemon
2017-07-10  5:10 ` bugzilla-daemon
2017-07-10  5:14 ` bugzilla-daemon
2017-07-10 12:58 ` bugzilla-daemon
2017-07-10 22:52 ` bugzilla-daemon
2017-07-11  8:12 ` bugzilla-daemon
2017-07-11  8:40 ` bugzilla-daemon
2017-07-11  9:59 ` bugzilla-daemon
2017-07-11 13:15 ` bugzilla-daemon
2017-07-11 17:17 ` bugzilla-daemon
2017-07-12  7:52 ` bugzilla-daemon
2017-07-12 14:17 ` bugzilla-daemon

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=bug-196223-13602-azSAL8DVP6@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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