Jaunty Alpha 4 amd64 boot fails after usb initialization

Bug #330866 reported by tqft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Jaunty Alpha 4 amd64 boot fails after usb initialization

Jaunty A4 i386 live cd boots to desktop and appears to work
Debian 5.0 Lenny amd64 boot fails in installing base system (at installing libc6 don't know and may or may not be relevant)

Jaunty A4 cd boots on machine

I tried a variety of boot options acpi, lapic, irqpoll on and off - all with similar results to below

Turned off quiet and splash to see where it failed.

Would get to usb initialization (external card reader) and appear fine
then would hang - max time left was 30 minutes and no further response so rebooted.
depending on the option

irqpoll not set
would get error debconf-communi [1542] segfault at
ffffffffe0 1773f00 ip
00007f2f272b9289 sp
00007fff2f7ebb20
error6 in libperl.so.5.10.0 [72f27256000+167000]

or
irqpoll set
[I noted that during test with irqpoll saw warning
 "sd needs updating pls use bus type methods"
 "sr needs updating pls use bus type methods"
]

fixed recursive fault but reboot is needed
end trace 341465510449d2a3
CR2 ffffe202001befec0
RSP ffff8800b081ad8

Revision history for this message
tqft (ianburrows-au) wrote :
Revision history for this message
Nick Booker (nmbooker) wrote :

Kernel guys: is this a kernel issue?

Revision history for this message
Munzir Taha (منذر طه) (munzirtaha) wrote :

I just tried alpha 6 in Dell Studio 1535 and got an I/O error cannot boot CD or something similar

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

I am confirming this report based on the comments above. There should be enough information for the developers to begin working this. Thanks for helping improve Ubuntu.

Changed in linux:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
TJ (tj) wrote :

We need more information including logs of the error reports to determine a response to this - possibly captured using a serial console or netconsole with kernel command-line option "debug".

Revision history for this message
Munzir Taha (منذر طه) (munzirtaha) wrote :

I don't have serial port nor another PC to send messages to but my problem may be different than this one. I just got that error in the very beginning before getting any kernel messages in my console

Revision history for this message
tqft (ianburrows-au) wrote :

Tried --debug on both live cd and install test
But no serial console or net console
It did appear to fail earlier - with the live cd got a stack trace ending at
c08c09014cb5d0a3

Tried Gentoo live cd 2008.0 amd64
Booted but did when reading from read/write to tempfs early in the boot process

Unless someone has a test idea I am giving up as it looks like a hardware problem - should be 64bit hardware but the firmware is borked in there somewhere

I may try a FreeBSD x64 sometime soon and see if I can get a useful error message

Revision history for this message
Evan (ev) wrote :

This is not a bug in ubiquity, moving back to the kernel.

Changed in ubiquity (Ubuntu):
importance: Medium → Undecided
status: Confirmed → Invalid
Revision history for this message
Evan (ev) wrote :

Actually, I just noticed the comments about debconf-communicator segfaulting. Can you attach /var/log/syslog from the live CD?

Changed in ubiquity (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
tqft (ianburrows-au) wrote :

Cannot capture the output from LiveCD - tried Jaunty amd64 Release version this morning

best I could get as the messages scrolled past was
debconf-communi[1227]
segfault fffffffe1dedfdd8
error 6 in libperl

and then similar message repeated.

Have tried a variety of BIOS settings, kernel boot comamnds - irqpoll, acpi=on noacpi nolapic, safe graphics mode and various combinations thereof .

Revision history for this message
Manoj Iyer (manjo) wrote :

Is this still a problem with the released version of Jaunty ?

Revision history for this message
tqft (ianburrows-au) wrote :

As per comment 10
"tried Jaunty amd64 Release version"
Yes still a problem with release version

Recent tests with Open Solaris (booted but not stable) and NetBSD indicate it might work but (this was me trying NetBSd last week)
NetBSD wanted to work until the disk borked.

http://slashdot.org/comments.pl?sid=1216891&threshold=1&commentsort=0&mode=thread&cid=27769827

"FreeBSD64 chokes as well at some point.
OpenSolaris CD boots but I couldn't tell if it was running in x64 mode or not. Didn't stay up long enough (Gnome &/or X would bork after about 5 minutes)"

It may be a problem with the ich7 driver but I don't know a good way to test it

Revision history for this message
Evan (ev) wrote :

tqft,

Are you able to download a recent Karmic daily-live CD (http://cdimage.ubuntu.com/daily-live) and let us know if that works?

Thanks!

Revision history for this message
tqft (ianburrows-au) wrote :

Downloaded from link
731527168 2009-10-21 08:25 karmic-desktop-amd64.iso

Same basic result - wants to start but fails

Starts, allows livecd to start

Fails a few seconds exactly how depending on which options are set (acpi, apic, irqpoll).

I give up - has to be the firmware in motherboard is buggy. No more updates either.

Thanks for trying.

Revision history for this message
Evan (ev) wrote :

This definitely sounds like a kernel bug or hardware issue, given the reporter's most recent comments. I'm marking the installer task as invalid.

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi tqft,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 330866

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
tqft (ianburrows-au) wrote :

Tried mainline kernel
ian@tqft:~/Desktop/ubuntumainlinekernelamd64$ sudo dpkg -i linux-image-2.6.34-999-generic_2.6.34-999.201003141003_amd64.deb && sudo pkg -i linux-headers-2.6.34-999-generic_2.6.34-999.201003141003_amd64.deb
[sudo] password for ian:
dpkg: error processing linux-image-2.6.34-999-generic_2.6.34-999.201003141003_amd64.deb (--install):
 package architecture (amd64) does not match system (i386)
Errors were encountered while processing:
 linux-image-2.6.34-999-generic_2.6.34-999.201003141003_amd64.deb

No luck.

Next is lucid beta.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.