Public bug reported:
I haven't yet figured a way to get data from the failed launch, as I get
dropped into the BusyBox terminal with the (initramfs) prompt which
appears to be a ram disk.
Any method of attempting to boot (or install) from the LiveCD causes this
wonderful BusyBox failure, including the CD integrity check. I've
double-checked the CD and the image for integrity. The CD matches image, the
image verifies in bittorrent, and the image has the correct MD5 checksum.
First off, I'm running an AMD64 Athlon (1 core) on a custom machine with
an ASUS A8V motherboard. There's a Western Digital harddrive on the
primary IDE and a DVD-CD R/W LITEON drive on the secondary IDE. There's
another, larger, Western Digital drive on the 3rd SATA port out of 4
SATA port.
However, I'm trying to run this off of standard i386 ISA build, not the
amd64/x86-64 ISA build.
Taking out quiet and splash I get the following lines during boot. These are
_NOT_ pasted, but loosely transcribed to/from paper:
ata1 SATA link down (SStatus 0 SControl 300)
ata2 SATA link down (SStatus 0 SControl 300)
ata3 SATA link up 3.0 GBps (SStatus 123 SControl 300)
After a few moments, I get dumped into a BusyBox/initramfs terminal.
However I can't do anything yet, as my USB drivers haven't yet loaded.
Waiting what seems like around 10-30 seconds(estimate, but it doesn't
change between launches) yields the following messages, after the
busybox terminal has loaded:
ata 3.00: qc timeout (cmd 0xec)
ata 3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3: failed to recover some devices, retrying in 5 sec
ata3 SATA link up 3.0 GBps (SStatus 123 SControl 300)
repeat the qc timeout, failed to identify, failed to recover some
devices message set for a total of 3 times, and then the boot process
seems to continue, but after it gets through with my keyboard or so on
USB, it's done and the limited console is now available.
Going through the log again with dmesg, there's another error inbetween these
repeating attempts to contact my hard drive on the 3rd SATA port that didn't
show up on-screen during the failure to boot:
APIC error on CPU0: 0(0)
This message repeats with the others right before each qc timeout I
believe, though I don't remember the APIC error's exact placement.
Doing a no apic option on bootup didn't change a thing.
I can't get all the way through my 7.10 normal boot because I screwed up X, but
I gathered what happens on a successful 7.10 boot into recovery mode:
[ 41.523393] ata1: SATA link down (SStatus 0 SControl 300)
[ 41.835112] ata2: SATA link down (SStatus 0 SControl 300)
[ 42.318687] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 42.350820] ata3.00: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133
[ 42.350872] ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 42.351777] ata3.00: configured for UDMA/133
[ 42.662381] ata4: SATA link down (SStatus 0 SControl 300)
[ 42.662526] scsi 2:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 12.0
PQ: 0 ANSI: 5
[ 42.663027] ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 22 (level, low) ->
IRQ 22
I have that entire dmesg log if necessary.
Interestingly enough, the USB drivers appear to load earlier in 7.10
than they do in 8.04 beta.
If I can gather anything else, I'd be happy to. I also apologize if this is a
duplicate, but I couldn't find a dup of it.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Boot failure in 8.04 beta (SATA or apic related)
https://bugs.launchpad.net/bugs/207639
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
