From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 96631] New: after Updating kernel ,system failed to boot
Date: Tue, 14 Apr 2015 09:31:04 +0000 [thread overview]
Message-ID: <bug-96631-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=96631
Bug ID: 96631
Summary: after Updating kernel ,system failed to boot
Product: SCSI Drivers
Version: 2.5
Kernel Version: kernel-ml-3.19.2-1.el7.elrepo.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Other
Assignee: scsi_drivers-other@kernel-bugs.osdl.org
Reporter: xiaozhe.ou@samsung.com
Regression: No
Created attachment 174011
--> https://bugzilla.kernel.org/attachment.cgi?id=174011&action=edit
failure info
We update the CentOS-7.0-1406-x86_64-DVD kernel to
kernel-ml-3.19.2-1.el7.elrepo.x86_64,then we reboot system and enter 3.19.2
kernel. The screen stop at boot message as attachment shows. But you can log in
use ssh, and "uname -a" show the system has been updated with new kernel.
Why the screen printing stopped and show failure boot with new kernel?
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2015-04-14 9:31 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=bug-96631-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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).