Created attachment 978916 [details] dmesg log immediately after a successful resume from suspend Description of problem: Right after a successful resume from suspend, the first message in dmesg output is: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. Version-Release number of selected component (if applicable): unknown How reproducible: unknown Steps to Reproduce: 1. dmesg > before.txt 2. Shut laptop lid 3. Open laptop lid 4. Log in 5. dmesg > after.txt 6. Open before.txt and after.txt 7. Read first message after last before.txt message Actual results: [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. Expected results: No bug Additional info: Dell Inspiron 1525 laptop Fedora 21 Workstation Processor: Intel® Pentium(R) Dual CPU T2390 @ 1.86GHz × 2 OS Type: 64-bit Graphics: Intel® 965GM GNOME: Version 3.14.2
Hi Gilles, As the message tries to explain with the [FIRMWARE bug] prefix, this is a bug in the firmware aka BIOS of your laptop, not in Linux itself, so there is little we can do to fix it. Do you see any adverse side effects from this, e.g. does backlight control using the brightness up / down buttons on the keyboard still work after a suspend / resume ? If everything still works, then it is safe to ignore the message and this bug can be closed. Regards, Hans
(In reply to Hans de Goede from comment #1) > Hi Gilles, > > As the message tries to explain with the [FIRMWARE bug] prefix, this is a > bug in the firmware aka BIOS of your laptop, not in Linux itself, so there > is little we can do to fix it. > > Do you see any adverse side effects from this, e.g. does backlight control > using the brightness up / down buttons on the keyboard still work after a > suspend / resume ? > > If everything still works, then it is safe to ignore the message and this > bug can be closed. > > Regards, > > Hans Hi Hans, Nothing bad seems to happen when the resume actually succeeds… But resuming from suspend often fails and I get a black screen with a working cursor. I also get tons of bugs in my dmesg related to my graphics driver. See: https://bugzilla.redhat.com/show_bug.cgi?id=962386 https://bugzilla.redhat.com/show_bug.cgi?id=1177477 https://bugzilla.redhat.com/show_bug.cgi?id=1176645 https://bugzilla.redhat.com/show_bug.cgi?id=1178543 I have no idea if they are all linked together, or many separate bugs. When resume from suspend fails, the brightness buttons and the PrntScrn buttons are the only ones that stop working.
Hi, Yes those warnings in your dmesg look like the intel kernel driver is seriously unhappy on your system. It is probably best to directly file a bug with the intel upstream developers, as they know the code best and thus can help you best. The procedure for this is described here: https://01.org/linuxgraphics/documentation/how-report-bugs Regards, Hans
Thank you very much Hans for the procedure. I'm confused about which category to choose. Is it: 1) xorg & Driver/intel 2) Mesa & Drivers/DRI/i915 3) DRI & DRM/Intel For procedure 2.1, what should be the subsystem/feature? I'm going to dive into this documentation before filing the most complete bug I can ever file. Thank you again.
(In reply to Gilles-Philippe Morin from comment #4) > Thank you very much Hans for the procedure. > > I'm confused about which category to choose. Is it: > 1) xorg & Driver/intel > 2) Mesa & Drivers/DRI/i915 > 3) DRI & DRM/Intel Your problem seems to be with the kernel driver which falls under DRM/Intel, so category 3. > For procedure 2.1, what should be the subsystem/feature? I'm not 100% sure, but I think that using "965GM kms" will do fine for starters, if incorrect it can always be changed later. > I'm going to dive into this documentation before filing the most complete > bug I can ever file. Thank you again. You're welcome, and thanks for filing a detailed bug-report upstream that way you're not only helping yourself but also other Linux users.
(In reply to Hans de Goede from comment #5) > (In reply to Gilles-Philippe Morin from comment #4) > > Thank you very much Hans for the procedure. > > > > I'm confused about which category to choose. Is it: > > 1) xorg & Driver/intel > > 2) Mesa & Drivers/DRI/i915 > > 3) DRI & DRM/Intel > > Your problem seems to be with the kernel driver which falls under DRM/Intel, > so category 3. > > > For procedure 2.1, what should be the subsystem/feature? > > I'm not 100% sure, but I think that using "965GM kms" will do fine for > starters, if incorrect it can always be changed later. > > > I'm going to dive into this documentation before filing the most complete > > bug I can ever file. Thank you again. > > You're welcome, and thanks for filing a detailed bug-report upstream that > way you're not only helping yourself but also other Linux users. Unfortunately, I have no other choice than to give up. Everything is way too technical and I don't know how Linux works. I tried getting help on IRC, social networks, mailing lists, online Intel chat support, but I am always referred to bugzilla, Intel documentation, and Google. I have never felt so alone on the Web. I tried really hard to understand https://01.org/linuxgraphics/documentation/how-debug-suspend-resume-issues-0 I really tried, but it's assuming so much that I know so many things that it's a real torture. "lsof /proc/acpi/event" doesn't do anything in a terminal. I don't know how to kill processes. I don't know how to switch from text console mode (init level 3) to X mode (init level 5) and vice versa. But then, I tried the cycle in a new TTY and it quite never fails. I don't know how to obtain a dmesg output after the resume fails and my laptop becomes unusable. I have no idea how dumps work. I don't know how to remove modules, let alone know what modules are. But then, I tried doing something written on the Arch Linux wiki: Does i915.modeset=0 in GRUB remove the i915 module? I tried it and it stopped graphical animations in GNOME. With that thing my laptop does not suspend anymore when I close the lid and after I press the Off button to go to sleep the graphics don't wake up anymore. Most importantly, I cannot switch back to Fedora 20 or jump to Ubuntu, and I am afraid that this bug will soon be on all recent distributions if I don't report it. People in IRC chat rooms are indirectly tell me that I'm wasting their time and that I should use Google instead. Google is a mess and points me to unanswered questions in forums and technical documentation. Mailing lists tell me to go upstream. Upstream mailing lists are developer-focused. Intel chat support tells me Intel does not support Linux*. Social networks point me to my own bug reports on Bugzilla.
I'm sorry to hear about your troubles filing a bug with the upstream Intel developers. I don't think you need to follow the exact instructions of: https://01.org/linuxgraphics/documentation/how-debug-suspend-resume-issues-0 You can just file a bug with the info you've been able to gather and then we can see how things progress from there.
(In reply to Hans de Goede from comment #7) > I'm sorry to hear about your troubles filing a bug with the upstream Intel > developers. > > I don't think you need to follow the exact instructions of: > > https://01.org/linuxgraphics/documentation/how-debug-suspend-resume-issues-0 > > You can just file a bug with the info you've been able to gather and then we > can see how things progress from there. I filed that bug: https://bugs.freedesktop.org/show_bug.cgi?id=87772 However, it is already marked as NEEDINFO, so I guess things are not very promising for me…
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.