From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 192131] Hang up at boot time [<c0c4d1ac>] (io_schedule_timeout) from [<c0c4e344>] (bit_wait_i)
Date: Mon, 09 Jan 2017 06:00:08 +0000 [thread overview]
Message-ID: <bug-192131-13602-Ro208uTJHT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-192131-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=192131
--- Comment #1 from Myy <bugux@miouyouyou.fr> ---
It turns out that compiling kernels up to the following commit work:
92c020d08d83673ecd15a9069d4457378668da31
Then after this one, I got the reported problem:
7b9dc3f75fc8be046e76387a22a21f421ce55b53
It seems that it's really a scheduler problem, and not a filesystem problem. If
you're administrator, feel free to move this to the right section.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-01-09 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 23:51 [Bug 192131] New: Hang up at boot time [<c0c4d1ac>] (io_schedule_timeout) from [<c0c4e344>] (bit_wait_i) bugzilla-daemon
2017-01-09 6:00 ` bugzilla-daemon [this message]
2017-01-10 7:39 ` [Bug 192131] " 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-192131-13602-Ro208uTJHT@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).