Re: Can't Boot after latest Feisty Upgrade
- From: John Graddy <jwgraddy@xxxxxxxxxxxx>
- Date: Fri, 13 Apr 2007 17:58:35 -0500
I have just about come to the conclusion that I'm not smart enough to
use Linux as the OS on my system.
I have a very fundamental question about the suggestions that I have
been receiving. When do I need to go through the update process again?
For example, when I edit the /etc/network/interfaces, do I need to do go
through the update process again before I reboot to check out the
results of the edits that I made. It's not clear to me if editing a
data file (e.g. /etc/network/interfaces) effects the boot process of
whatever kernel I boot, or, do I have to edit the data file and also
build a new kernel after editing for the changes to take effect?
I have included below, the messages in the dmesg log that show the
delays I reported. I have included several messages before and after
each large increment in the time field. These are extracts from the
log. I would be happy to provide the entire log, but, it is 7 pages
long. Can you include attachments in emails to this list?
Thanks,
John
[ 0.000000] If you got timer trouble try acpi_use_timer_override
[ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
[ 0.000000] If you got timer trouble try acpi_use_timer_override
[ 0.000000] Allocating PCI resources starting at 30000000 (gap:
20000000:dec00000)
[ 0.000000] Detected 2079.590 MHz processor.
[ 20.278415] Built 1 zonelists. Total pages: 130033
[ 20.278418] Kernel command line:
root=UUID=e7527156-aa96-4a40-a196-a2282a2f7f5c ro quiet splash
[ 20.278574] Found and enabled local APIC!
[ 20.278577] mapped APIC to ffffd000 (fee00000)
[ 20.278580] Enabling fast FPU save and restore... done.
[ 20.278582] Enabling unmasked SIMD FPU exception support... done.
[ 20.278592] Initializing CPU#0
[ 25.126842] usb 1-1: new full speed USB device using ohci_hcd and
address 3
[ 25.359792] usb 1-1: configuration #1 chosen from 1 choice
[ 25.462838] ata2.00: ATAPI, max UDMA/33
[ 25.462842] ata2.01: ATAPI, max MWDMA2
[ 55.438931] ata2.00: qc timeout (cmd 0xef)
[ 55.438939] ata2.00: failed to set xfermode (err_mask=0x4)
[ 55.438944] ata2: failed to recover some devices, retrying in 5 secs
[ 90.898976] ata2.00: qc timeout (cmd 0xef)
[ 90.898982] ata2.00: failed to set xfermode (err_mask=0x4)
[ 90.898988] ata2.00: limiting speed to UDMA/33:PIO3
[ 90.898990] ata2: failed to recover some devices, retrying in 5 secs
[ 126.359024] ata2.00: qc timeout (cmd 0xef)
[ 126.359030] ata2.00: failed to set xfermode (err_mask=0x4)
[ 126.359034] ata2.00: disabled
[ 126.359036] ata2: failed to recover some devices, retrying in 5 secs
[ 131.359086] ata2.01: failed to set xfermode (err_mask=0x40)
[ 131.359090] ata2: failed to recover some devices, retrying in 5 secs
[ 136.843003] ata2.01: configured for MWDMA2
[ 136.843133] scsi 0:0:0:0: Direct-Access ATA ST3120026A
3.06 PQ: 0 ANSI: 5
[ 136.843510] scsi 0:0:1:0: Direct-Access ATA WDC WD600BB-32BS
12.0 PQ: 0 ANSI: 5
[ 136.844084] scsi 1:0:1:0: CD-ROM CREATIVE CD5233E
2.05 PQ: 0 ANSI: 5
[ 136.863844] SCSI device sda: 234441648 512-byte hdwr sectors (120034
MB)
[ 136.863877] sda: Write Protect is off
[ 137.136390] Attempting manual resume
[ 137.136394] swsusp: Resume From Partition 8:5
[ 137.136396] PM: Checking swsusp image.
[ 137.136696] PM: Resume from disk failed.
[ 137.177394] kjournald starting. Commit interval 5 seconds
[ 137.177406] EXT3-fs: mounted filesystem with ordered data mode.
[ 148.953374] NET: Registered protocol family 17
[ 149.243476] Linux agpgart interface v0.102 (c) Dave Jones
[ 149.405834] agpgart: Detected NVIDIA nForce2 chipset
[ 149.410053] agpgart: AGP aperture is 64M @ 0xe8000000
[ 149.462690] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 149.474611] shpchp: Standard Hot Plug PCI Controller Driver version:
0.4
[ 149.493304] i2c_adapter i2c-0: nForce2 SMBus adapter at 0x5000
[ 149.493340] i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5100
[ 153.017395] powernow_k7: Unknown symbol
acpi_processor_register_performance
[ 153.049978] acpi_cpufreq: Unknown symbol acpi_processor_notify_smm
[ 153.050015] acpi_cpufreq: Unknown symbol
acpi_processor_unregister_performance
[ 153.050102] acpi_cpufreq: Unknown symbol
acpi_processor_preregister_performance
[ 153.050146] acpi_cpufreq: Unknown symbol
acpi_processor_register_performance
[ 158.157676] ppdev: user-space parallel port driver
[ 159.128850] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[ 159.659835] Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
[ 160.027055] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
recovery directory
[ 160.144358] NFSD: starting 90-second grace period
[ 163.620477] Bluetooth: Core ver 2.11
[ 163.620550] NET: Registered protocol family 31
[ 163.620553] Bluetooth: HCI device and connection manager initialized
[ 163.620557] Bluetooth: HCI socket layer initialized
[ 163.663710] Bluetooth: L2CAP ver 2.8
[ 163.663715] Bluetooth: L2CAP socket layer initialized
[ 163.757534] Bluetooth: RFCOMM socket layer initialized
[ 163.757549] Bluetooth: RFCOMM TTY layer initialized
[ 163.757552] Bluetooth: RFCOMM ver 1.8
[ 174.596896] eth0: no IPv6 routers present
[18038.611389] eth0: no IPv6 routers present
On Wed, 2007-04-11 at 16:09 -0700, NoOp wrote:
On 04/11/2007 02:23 PM, John Graddy wrote:
On Tue, 2007-04-10 at 15:21 -0700, NoOp wrote:
The files you asked for follow later in this post.
Can you post your /var/log/boot and also your /etc/network/interfaces
files (feel free to modify the IP's of the last slightly).
The /var/log/boot file is strange in that it has only entries for Feb.
14. Did you intend to ask for /var/log/bootstrap? That one has a lot
of entries about pre-dependency problems.
I was hoping for a current one. Mine is updated on each boot & to be
honest I can't remember how I turned it on.
I have also examined the Dmesg log at Peter Garrett's suggestion and
have found some strange (at least strange to me) happenings. I have
identified 2 minutes and 18 seconds of unexplained delays.
Can you post those delays?
The files that you wanted to sww follow:
Do you have all of those interfaces? If not, I would suggest that you
edit to only one interface right now. During boot the system will look
for each one & can cause significate delay if it doesn't find each one.
Eventually it will time out & move one to the next.
/etc/network/interfaces
auto lo
iface lo inet loopback
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
auto eth2
iface eth2 inet dhcp
auto ath0
iface ath0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
iface ppp0 inet ppp
provider ppp0
Ref:
https://bugs.launchpad.net/ubuntu/+bug/102675
You might also want to look through some of these:
<http://www.google.com/search?hl=en&q=+site:bugs.launchpad.net+feisty+%2Blong+boot+%2Brecent+update>
--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
- Follow-Ups:
- Re: Can't Boot after latest Feisty Upgrade
- From: NoOp
- Re: Can't Boot after latest Feisty Upgrade
- From: Scott Lockwood
- Re: Can't Boot after latest Feisty Upgrade
- From: Patton Echols
- Re: Can't Boot after latest Feisty Upgrade
- References:
- Can't Boot after latest Feisty Upgrade
- From: John Graddy
- Re: Can't Boot after latest Feisty Upgrade
- From: Peter Garrett
- Re: Can't Boot after latest Feisty Upgrade
- From: John Graddy
- Re: Can't Boot after latest Feisty Upgrade
- From: NoOp
- Re: Can't Boot after latest Feisty Upgrade
- From: John Graddy
- Re: Can't Boot after latest Feisty Upgrade
- From: John Graddy
- Re: Can't Boot after latest Feisty Upgrade
- From: NoOp
- Re: Can't Boot after latest Feisty Upgrade
- From: NoOp
- Re: Can't Boot after latest Feisty Upgrade
- From: John Graddy
- Re: Can't Boot after latest Feisty Upgrade
- From: NoOp
- Re: Can't Boot after latest Feisty Upgrade
- From: John Graddy
- Re: Can't Boot after latest Feisty Upgrade
- From: NoOp
- Can't Boot after latest Feisty Upgrade
- Prev by Date: Re:
- Next by Date: Re:
- Previous by thread: Re: Can't Boot after latest Feisty Upgrade
- Next by thread: Re: Can't Boot after latest Feisty Upgrade
- Index(es):
Relevant Pages
|