dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98016] [bisected] Fury fails to boot on drm-next-4.9
Date: Wed, 05 Oct 2016 09:18:03 +0000	[thread overview]
Message-ID: <bug-98016-502-jZVFQRkm0p@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98016-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=98016

--- Comment #7 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Ernst Sjöstrand from comment #6)
> Do you think I can get both false positives and false negatives?
> Have tested a bit more but still behaving in a silly way...

I guess your issue not as clear cut as mine then.

If you find that you can sometimes boot and sometimes not on the same kernel
after power off, then that's going to be quite a pain and time consuming to
find.

It's not really normal to have to power off - I haven't needed to for ages,
just that with my recent boot up issue I knew I did need to as when I first
built it it worked from a reboot, but not the next day from off. I though your
issue may be similar, but apparently not.

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

[-- Attachment #1.2: Type: text/html, Size: 1713 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-10-05  9:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-02 13:31 [Bug 98016] [bisected] Fury fails to boot since vce3: add support for third vce ring bugzilla-daemon
2016-10-02 13:55 ` bugzilla-daemon
2016-10-03 20:08 ` bugzilla-daemon
2016-10-03 20:51 ` [Bug 98016] [bisected] Fury fails to boot on drm-next-4.9 bugzilla-daemon
2016-10-04  9:18 ` bugzilla-daemon
2016-10-04  9:30 ` bugzilla-daemon
2016-10-05  7:08 ` bugzilla-daemon
2016-10-05  9:18 ` bugzilla-daemon [this message]
2016-10-10 10:35 ` bugzilla-daemon
2016-10-14 11:39 ` bugzilla-daemon
2016-10-14 14:38 ` bugzilla-daemon
2016-10-14 14:50 ` bugzilla-daemon
2016-10-14 23:02 ` bugzilla-daemon
2016-10-14 23:03 ` bugzilla-daemon
2016-10-16 18:00 ` bugzilla-daemon
2016-10-25 13:41 ` bugzilla-daemon
2016-12-14 10:58 ` 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-98016-502-jZVFQRkm0p@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox