Bug 532367 - Fedora 12 takes half an hour to boot.
Summary: Fedora 12 takes half an hour to boot.
Keywords:
Status: CLOSED DUPLICATE of bug 530393
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-01 21:21 UTC by Thomas Ahle
Modified: 2009-11-04 19:35 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-04 19:35:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output (46.11 KB, text/plain)
2009-11-02 07:11 UTC, Thomas Ahle
no flags Details

Description Thomas Ahle 2009-11-01 21:21:51 UTC
Description of problem:
When I try to boot fedora 12 beta 2, I see the following written four times:
tmp_tis 00:0a: tmp_transmit: tmp_send: error -62
The four lines appear with 5-10 minutes in between.
After that the system very quickly writes something, of which I am not sure, but I think the word nouveau is included. Then it boots fine.

How reproducible:
Always. On both om my laptops, no matter if I boot from a cd (install cd/live cd/net install), an usb (live cd) or from my hard drive.

Steps to Reproduce:
1. Turn on the computer
  
Actual results:
The boot takes half an hour waiting for something to timeout.

Expected results:
A boot time less than a minute.

Comment 1 Thomas Ahle 2009-11-01 23:33:37 UTC
I removed rhgb and quiet.
Just before the tmp_tis lines I now got:
ACPI: EC: missing confirmations, witch off interrupt mode.

On a side node, the nouveau lines also seams to not be related to the problem after all, as there is a lot of "noice" lines before it.

Comment 2 Thomas Ahle 2009-11-02 07:11:54 UTC
Created attachment 367072 [details]
dmesg output

Comment 3 Chuck Ebbert 2009-11-02 18:33:13 UTC
What is in the file /proc/interrupts after you finish booting? Please paste the contents into the comment box here.

Comment 4 Thomas Ahle 2009-11-02 21:27:39 UTC
           CPU0       CPU1       
  0:     999467     827911   IO-APIC-edge      timer
  1:          5       8634   IO-APIC-edge      i8042
  5:          0          0   IO-APIC-edge      parport0
  8:          0          1   IO-APIC-edge      rtc0
  9:       4941      93446   IO-APIC-fasteoi   acpi
 11:          0          0   IO-APIC-edge      tpm0
 12:         74     376563   IO-APIC-edge      i8042
 14:          0          0   IO-APIC-edge      ata_piix
 15:          0          0   IO-APIC-edge      ata_piix
 16:          7         10   IO-APIC-fasteoi   uhci_hcd:usb3, nouveau
 17:         52          1   IO-APIC-fasteoi   firewire_ohci
 18:          1          0   IO-APIC-fasteoi   ehci_hcd:usb1, uhci_hcd:usb7, yenta, mmc0, tifm_7xx1
 19:      30876       3947   IO-APIC-fasteoi   ata_piix, uhci_hcd:usb6
 21:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4
 22:       1280         89   IO-APIC-fasteoi   HDA Intel
 23:          0          0   IO-APIC-fasteoi   ehci_hcd:usb2, uhci_hcd:usb5
 29:      29073      22579   PCI-MSI-edge      iwlagn
 30:          2          1   PCI-MSI-edge      eth0
NMI:          0          0   Non-maskable interrupts
LOC:     847673     572948   Local timer interrupts
SPU:          0          0   Spurious interrupts
CNT:          0          0   Performance counter interrupts
PND:          0          0   Performance pending work
RES:     150139     112950   Rescheduling interrupts
CAL:         80         76   Function call interrupts
TLB:        562        626   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:         13         13   Machine check polls
ERR:          0
MIS:          0

Comment 5 Chuck Ebbert 2009-11-04 19:35:08 UTC

*** This bug has been marked as a duplicate of bug 530393 ***


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