/var/log/messages, of course contain no clues since nothing gets written to it until after syslog has started. dmesg's output looks normal to me. Output is as follows:-
Code: Select all
root@mythfr1:/var/log # dmesg 6>Switching to clocksource tsc \ usb 2-7: new low-speed USB device number 2 using ohci_hcd done. VFS: Mounted root (squashfs filesystem) readonly on device 1:0. Freeing unused kernel memory: 348k freed Registering unionfs 2.5.11 (for 3.3.0-rc3) >udevd: starting version 182 NET: Registered protocol family 17 Real Time Clock Driver v1.12b loop: module loaded ppdev: user-space parallel port driver input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0 ACPI: Power Button [PWRB] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 ACPI: Power Button [PWRF] wmi: Mapper loaded i2c i2c-0: nForce2 SMBus adapter at 0x1c00 i2c i2c-1: nForce2 SMBus adapter at 0x1c80 input: iMON Panel, Knob and Mouse(15c2:0038) as /devices/pci0000:00/0000:00:04.0/usb2/2-7/2-7:1.0/input/input2 IR NEC protocol handler initialized IR RC5(x) protocol handler initialized snd_hda_intel 0000:00:09.0: power state changed by ACPI to D0 snd_hda_intel 0000:00:09.0: power state changed by ACPI to D0 ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 20 hda_intel: Disabling MSI snd_hda_intel 0000:00:09.0: setting latency timer to 64 it87: Found IT8718F chip at 0x290, revision 5 it87: Beeping is supported Registered IR keymap rc-imon-pad input: iMON Remote (15c2:0038) as /devices/pci0000:00/0000:00:04.0/usb2/2-7/2-7:1.0/rc/rc0/input3 rc0: iMON Remote (15c2:0038) as /devices/pci0000:00/0000:00:04.0/usb2/2-7/2-7:1.0/rc/rc0 imon 2-7:1.0: iMON device (15c2:0038, intf0) on usb<2:2> initialized imon 2-7:1.1: iMON device (15c2:0038, intf1) on usb<2:2> initialized usbcore: registered new interface driver imon usbcore: registered new interface driver usbhid usbhid: USB HID core driver IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR SANYO protocol handler initialized IR MCE Keyboard/mouse protocol handler initialized lirc_dev: IR Remote Control driver registered, major 252 IR LIRC bridge handler initialized hda_codec: ALC889A: BIOS auto-probing. p4-clockmod: Warning: EST-capable CPU detected. The acpi-cpufreq module offers voltage scaling in addition to frequency scaling. You should use that instead of p4-clockmod, if possible. p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available coretemp coretemp.0: Using relative temperature scale! coretemp coretemp.0: Using relative temperature scale! lirc_imon: module is from the staging directory, the quality is unknown, you have been warned. usbcore: registered new interface driver lirc_imon Linux agpgart interface v0.103 nvidia: module license 'NVIDIA' taints kernel. Disabling lock debugging due to kernel taint ACPI: PCI Interrupt Link [AIGP] enabled at IRQ 23 nvidia 0000:00:10.0: setting latency timer to 64 vgaarb: device changed decodes: PCI:0000:00:10.0,olddecodes=io+mem,decodes=none:owns=io+mem NVRM: loading NVIDIA UNIX x86 Kernel Module 295.53 Fri May 11 23:13:15 PDT 2012 p4-clockmod: Warning: EST-capable CPU detected. The acpi-cpufreq module offers voltage scaling in addition to frequency scaling. You should use that instead of p4-clockmod, if possible. p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available unionfs: new lower inode mtime (bindex=0, name=certs) unionfs: new lower inode mtime (bindex=0, name=libexec) unionfs: new lower inode mtime (bindex=0, name=gdk-pixbuf-2.0)
Any ideas what might be causing this issue and how I might be able to get around it? It's not a critical problem by any stretch of the imagination since the machine does operate more or less normally after starting, but it is irritating to have to wait several minutes for the machine to boot.