Description of problem:
Boot machine - message appears briefly during boot and normal boot continues
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot machine
Brief message on screen before graphical boot, but boot then continues normally with no further issues.
No unusual messages on screen
Possibly same bug as reported for f12 at https://bugzilla.redhat.com/show_bug.cgi?id=578694
Created attachment 460775 [details]
dmesg file showing same line as on screen during boot
*** Bug 653810 has been marked as a duplicate of this bug. ***
Me too, except that I didn't notice it amongst the noise of a successful boot, I noticed it during hibernate/resume where it is the only error message (but repeated twice during hibernate and a third time during resume).
It is quite disturbing to get error messages during hibernate.
This is on a Dell D630 laptop with Fedora-14. kernel-18.104.22.168-83.fc14.x86_64
I confirm this BUG
Upon booting appears this error message: "ata4.01: failed to resume link (SControl 0)"
Fedora 15 - kernel-22.214.171.124-30.fc15,i686.PAE here.
seems to me. something happen after upgrade kernel from 126.96.36.199-2 to 188.8.131.52-30 or 184.108.40.206-32.fc15.x86_64
Linux version 220.127.116.11-27.fc15.x86_64 (gcc version 4.6.0 20110428 (Red Hat 4.6.0-6) (GCC) ) #1 SMP Sun May 15 17:23:28 UTC 2011
Lnux version 18.104.22.168-30.fc15.x86_64 (gcc version 4.6.0 20110509 (Red Hat 4.6.0-7) (GCC) )
Linux version 22.214.171.124-32.fc15.x86_64(gcc version 4.6.0 20110530 (Red Hat 4.6.0-9)
this 2 bad kernels give me some ata1:00 message link and unlinked
and hangs firefox for one minute, today with 126.96.36.199-30, resume from suspend , hang computer, thing that never happened since upgrade to Fedora 15 one month ago.
Back to kernel 188.8.131.52-27.fc15.x86_64 every thing fine , I suspend and wake many times I want and always perfect.
I follow this bug #714040 , #714023, #716623, #669892, to try understand, I could work with those bad kernel but after times , suspends and resumes dont' work soo weel, and Firefox have stops , especially when have sshfs tunneling that was broken by a suspend.
Could be hardware failure of ata , but back on last good kernel things seems fine.
My issue is fixed on kernel 184.108.40.206-35 , I think is was :
* Wed Jul 06 2011 Chuck Ebbert <firstname.lastname@example.org> 220.127.116.11-35 - Revert SCSI/block patches from 18.104.22.168 that caused more problems
"ata4.01: failed to resume link (SControl 0)" - upon boot.
FC 15 - Kernal - 22.214.171.124-35.fc15.i686
FWIW, I have also seen this on F14. I reported it to the linux-ide list, and the reply may be relevant to this bug: http://permalink.gmane.org/gmane.linux.ide/49813
Same problem here.
It also appears (from the noise of it) that the Hard Drive is powered off and on again at this moment. This doesn't appear when booting an other (commercial) OS.
FC15 on Acer Aspire 5920G.
I'm using Fedora 15 and I found that once I changed the SATA mode in my bios settings from IDE to AHCI the message went away.
on a Dell D630
Switching my SATA BIOS settings to AHCI solved this problem for me.
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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.
The process we are following is described here: