Description of problem: Sometimes the system seem not to react when i get back to it after a while; I move mouse, tap keyboard, but screen is still black Sometimes it wakes up if i salute it Ctrl-Alt-F12, and i can get back to other terminals including KDE issuing Ctrl-Alt-Fx But sometimes i need to power cycle. Actually, if i put in a USB memory it seem to aces it (blinks) but screen is dead. Version-Release number of selected component (if applicable): mga1 fully updated, running KDE How reproducible: about four times a week without irqpoll never with irqpoll. Steps to Reproduce: 1) Go have lunch, end work day (and computer powers off screen, locks screen) 2) Get back to a sometimes "dead" computer 3) "Did i save my documents"?! 4) Doh! Traces: Without irqpoll, occasionally i recieve in all terminals the message Message from syslogd@svarten at Nov 29 15:44:16 ... kernel:Disabling IRQ #17 From log: kernel: irq 17: nobody cared (try booting with the "irqpoll" option) So i added irqpoll to boot line, and never saw it again for weeks, neither the behaviour nor hangup. To test, i removed irqpoll and within a day i got hit with a hangup. More info in my threads: https://forums.mageia.org/en/viewtopic.php?f=8&t=1601 https://forums.mageia.org/en/viewtopic.php?f=8&t=1602
Created attachment 1532 [details] dmesg.txt dmesg.txt from Morgan's forum thread
assigning to kernel maintainer
Source RPM: (none) => kernelAssignee: bugsquad => tmbSummary: Sometimes getting unresponsive UNLESS i give it irqpoll boot parameter => Sometimes system getting unresponsive UNLESS i give it irqpoll boot parameterCC: (none) => marja11
I also see the disabled irq problem. I have screen saver disabled so I can not comment on that part of the problem. Snippet from # dmidecode --type bios BIOS Information Vendor: Phoenix Technologies, LTD Version: 3.48 Release Date: 03/24/2006 # dmidecode --type 2,10 SMBIOS 2.4 present. Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: MSI Product Name: AMETHYST-M Version: 1.0 Serial Number: # uname -r 3.2.6-desktop-0.rc1.1.mga2
Blocks: (none) => 4490CC: (none) => junk_no_spam
Created attachment 1533 [details] dmesg > dmesg.log results
Blocks: 4490 => (none)
Hm. Yesterday i saw a "Disabling IRQ #17" message on same machine. No issues.
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
I think i have seen message twice since last post. No percived issues. Still running mga1.
CC: junk_no_spam => (none)
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED