From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 115441] New: Cant boot with nvme with recent kernels
Date: Tue, 29 Mar 2016 08:40:41 +0000 [thread overview]
Message-ID: <bug-115441-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=115441
Bug ID: 115441
Summary: Cant boot with nvme with recent kernels
Product: File System
Version: 2.5
Kernel Version: 4.3.6-040306
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: jarkko_korpi@hotmail.com
Regression: No
I didnt know what exactly is the component I should be targeting. Most likely
not filesystems. The kernel version I added, does work, but any effort 4.4
series or newer has been a result not booting system which has been fixed using
earlier kernel.
There is some regression that prevents you from booting from nvme ssd. Grub
works, but you just cant boot from the disk.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-03-29 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 8:40 bugzilla-daemon [this message]
2016-03-29 22:10 ` [Bug 115441] Cant boot with nvme with recent kernels 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-115441-13602@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