From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199619] screen stays dark for long on bootup since kernel 4.17.0-rc2+
Date: Mon, 11 Jun 2018 16:34:20 +0000 [thread overview]
Message-ID: <bug-199619-2300-p5NfMQvuai@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199619-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199619
Giorgio (giorgio.colacchio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |giorgio.colacchio@gmail.com
--- Comment #7 from Giorgio (giorgio.colacchio@gmail.com) ---
Hi Elmar,
I don’t know if it may be of help, anyway I have a similar problem: the point
is that my problem does not seem related to graphic drivers. My OS is
Slackware64 14.2, kernel 4.17.0. At boot, after the usual kernel messages, this
is what I see, at the end, on the screen (please, note that I boot in non
graphical mode, that is in init 3):
Welcome to Linux 4.17.0 (tty1)
darkstar login: [ 15.869206] wlan0: authenticate with 64:59:f8:cd:3a:88
[ 15.887504] wlan0: send auth to 64:59:f8:cd:3a:88 (try 1/3)
[ 15.892825] wlan0: authenticated
[ 15.895108] wlan0: associate with 64:59:f8:cd:3a:88 (try 1/3)
[ 15.899592] wlan0: RX AssocResp from 64:59:f8:cd:3a:88 (capab=0x411 status=0
aid=3)
[ 15.900872] wlan0: associated
as you can see, after the welcome message I can’t insert my login username –
because of the extra messages related to wlan authentication/association – and
as a consequence the system gets stuck. However, (in my case) we are dealing
here with a “trivial” bug, since it suffices to press Enter in order to restore
the login prompt and then start X.
I don’t know if this bug may be related to yours: in any case I would try to
boot in runlevel 3 in order to see what happens.
All the best,
Giorgio
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-11 16:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 7:34 [Bug 199619] New: screen stays dark for long on bootup since kernel 4.17.0-rc2+ bugzilla-daemon
2018-05-07 10:23 ` [Bug 199619] " bugzilla-daemon
2018-05-07 11:03 ` bugzilla-daemon
2018-05-12 8:00 ` bugzilla-daemon
2018-05-20 23:43 ` bugzilla-daemon
2018-06-08 17:01 ` bugzilla-daemon
2018-06-08 17:32 ` bugzilla-daemon
2018-06-11 16:34 ` bugzilla-daemon [this message]
2018-06-11 16:35 ` bugzilla-daemon
2018-06-19 19:51 ` bugzilla-daemon
2018-06-20 8:44 ` bugzilla-daemon
2018-09-11 6:52 ` bugzilla-daemon
2018-09-11 11:00 ` bugzilla-daemon
2018-09-12 8:00 ` bugzilla-daemon
2018-11-28 13:18 ` 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-199619-2300-p5NfMQvuai@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.