From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103783] atombios stuck in loop for more than 5secs
Date: Sat, 25 Nov 2017 11:08:07 +0000 [thread overview]
Message-ID: <bug-103783-502-yV6CmN24Zq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103783-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1255 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103783
--- Comment #10 from vkrevs@yahoo.com ---
OTOH, TLP services are not enabled according to tlp-stat -s, so does that mean
my laptop is not using TLP after all?
tlp-stat -s
--- TLP 1.0 --------------------------------------------
+++ System Info
System = Dell Inc. Inspiron 5770
BIOS = 1.0.5
Release = "openSUSE Tumbleweed"
Kernel = 4.14.0-1-default #1 SMP PREEMPT Mon Nov 13 21:02:46 UTC 2017
(ab9e909) x86_64
/proc/cmdline = BOOT_IMAGE=/boot/vmlinuz-4.14.0-1-default
root=UUID=d58e8e85-bfdd-4a74-a694-5149ccd85110 quiet resume=/dev/sda3
splash=silent quiet showopts
Init system = systemd v234
Boot mode = UEFI
+++ TLP Status
State = enabled
Last run = 11:02:47, 14 sec(s) ago
Mode = AC
Power source = AC
Notice: tlp.service is not enabled -- invoke "systemctl enable tlp.service" to
correct this!
Notice: tlp-sleep.service is not enabled -- invoke "systemctl enable
tlp-sleep.service" to correct this!
Notice: systemd-rfkill.service is not masked -- invoke "systemctl mask
systemd-rfkill.service" to correct this!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2039 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
next prev parent reply other threads:[~2017-11-25 11:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 17:54 [Bug 103783] atombios stuck in loop for more than 5secs bugzilla-daemon
2017-11-16 17:55 ` bugzilla-daemon
2017-11-16 17:55 ` bugzilla-daemon
2017-11-16 17:58 ` bugzilla-daemon
2017-11-16 18:00 ` bugzilla-daemon
2017-11-16 18:10 ` bugzilla-daemon
2017-11-16 18:10 ` bugzilla-daemon
2017-11-16 19:36 ` bugzilla-daemon
2017-11-18 20:54 ` bugzilla-daemon
2017-11-24 22:28 ` bugzilla-daemon
2017-11-25 9:21 ` bugzilla-daemon
2017-11-25 11:08 ` bugzilla-daemon [this message]
2017-11-27 12:49 ` bugzilla-daemon
2017-11-27 20:03 ` bugzilla-daemon
2017-11-28 1:38 ` bugzilla-daemon
2017-12-05 18:38 ` bugzilla-daemon
2019-11-19 8:26 ` 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-103783-502-yV6CmN24Zq@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;
as well as URLs for NNTP newsgroup(s).