Bug 672086 - kernel 2.6.35.10-74 sometimes doesn't complete booting
Summary: kernel 2.6.35.10-74 sometimes doesn't complete booting
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-23 21:17 UTC by antonio montagnani
Modified: 2012-08-16 13:44 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 13:44:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg when able to boot (59.13 KB, application/octet-stream)
2011-02-08 21:04 UTC, antonio montagnani
no flags Details
dmesg.old file (59.92 KB, application/octet-stream)
2011-02-08 21:06 UTC, antonio montagnani
no flags Details

Description antonio montagnani 2011-01-23 21:17:50 UTC
Description of problem:
Similar to bug 664145

Version-Release number of selected component (if applicable):
2.6.35.10-74

How reproducible:
sometimes, let us say once in ten days or less

Steps to Reproduce:
1.just boot
2.wait
3.
  
Actual results:
boot is not completed

Expected results:
it should boot fine

Additional info:

when it happens, if I boot to a previous kernel and reboot it works fine

Comment 1 antonio montagnani 2011-02-03 20:59:47 UTC
it happened tonight again, with ene_ir error.
It cannot be reproduced regularly as it happened once in ten days :-(

Comment 2 antonio montagnani 2011-02-06 14:23:53 UTC
for better understanding I still get:

Starting udev: udevd-work[495] `/sbin/modprobe -bv acpi: ENE0100:` unexpected
exit with statua 0x0009       [OK]

It happened again this morning

Comment 3 Dario Castellarin 2011-02-06 16:26:00 UTC
Are you on a dual-boot system? I noticed I still got this error when rebooting from Windows XP on my laptop. Windows XP couldn't even detect the IR device, so any driver installation failed, and after any reboot from Windows to Fedora, it would hang with the same error code.
However now I updated to Windows 7, which correctly recognised and installed the device, and I no more see it happening.

This on a Compal JFL92 (Santech X3610).

Comment 4 antonio montagnani 2011-02-06 16:40:12 UTC
yes, but Windows Vista is booted once a week just to update antivirus program, but it is not the case of last two times.

Today it happened when I restarted the machine in the afternoon and it had been shut down in fedora, so I suppose that  is not connected to dual boot.
My system is an acer 5720 see:

http://www.smolts.org/client/show/pub_c38b5c49-9c83-4457-8db8-03d91072afa6

Comment 5 Jarod Wilson 2011-02-07 04:58:48 UTC
Probably need to see dmesg output from when ene_ir fails to load to have any hope of figuring this one out.

Comment 6 antonio montagnani 2011-02-07 05:40:28 UTC
how do I get dmesg output when it fails? 
sorry for the stupid question.
At the moment I have blacklisted the ene_ir toy :-)

Comment 7 antonio montagnani 2011-02-08 21:04:22 UTC
Created attachment 477690 [details]
dmesg when able to boot

Comment 8 antonio montagnani 2011-02-08 21:05:46 UTC
kernel 2.6.35.11-83.fc14.i686.PAE is having same erratic behaviour

No problem if I blacklist ene_ir (that will be my final choice)

Comment 9 antonio montagnani 2011-02-08 21:06:52 UTC
Created attachment 477691 [details]
dmesg.old file

not sure if is dmesg when not able to boot.

Comment 10 Didier COMBES 2011-03-15 21:54:16 UTC
I've got the same symptom but error appears 1 / 3 on kernel 2.6.35.11-83.fc14.x86_64.
I've got dual boot with XP SP3 + Fedora (Grub is the bootloader).
It seems that error appear nearly every time on cold bold. I have to reboot once or twice to have correct booting.
Material : Acer Aspire 7720G.
I look for log with this error but it seems that boot error sequence is not stored in dmesg or messages files.

Comment 11 Fedora End Of Life 2012-08-16 13:44:19 UTC
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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.