From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96361] New: [Bisected, radeon]Non-infinite boot loop since v3.13
Date: Wed, 08 Apr 2015 22:14:08 +0000 [thread overview]
Message-ID: <bug-96361-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=96361
Bug ID: 96361
Summary: [Bisected, radeon]Non-infinite boot loop since v3.13
Product: Drivers
Version: 2.5
Kernel Version: 3.19
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: servuswiegehtz@yahoo.de
Regression: No
For a while now my desktop pc experiences boot issues. I try to boot and after
grub the screen just goes in standby mode and sometimes it reboots and
sometimes just nothing happens. After a few tries it usually succeeds in
booting.
So I bisected the kernel and this is the first bad commit:
6c7bccea390853bdec5b76fe31fc50f3b36f75d5
Steps to reproduce: not sure, seems to be a rare bug. install a linux kernel
newer than 3.13 and boot
Hardware:
AMD Phenom X4 955
AMD 5770 (Evergreen, Juniper)
I tried to get a log from systemd (journalctl --boot=-1) but there is none for
the failed boot attempt.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-04-08 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 22:14 bugzilla-daemon [this message]
2015-04-09 13:04 ` [Bug 96361] [Bisected, radeon]Non-infinite boot loop since v3.13 bugzilla-daemon
2015-04-09 19:01 ` bugzilla-daemon
2015-04-09 19:13 ` bugzilla-daemon
2015-04-09 20:21 ` bugzilla-daemon
2015-04-15 20:41 ` bugzilla-daemon
2015-11-24 13: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-96361-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.