Start-up hangs/jams on gutsy

This doesn't look like a bug. Have you recently installed a program or changed any config files?

I'm experiencing this problem with other kernels besides 2.6.22-14-generic. I have recently installed programs but can't remember necessarily which ones. Does ubuntu keep a log of things like this? Whatever it is, why will it boot the second time and not the first?

We need more information to fix this problem. Has this problem been occurring ever since you installed Gutsy or since you've modified your system? If the former, what kind of hardware are you running? If the latter, can you describe any changes you think may have had an affect on your system?

It used to do it once in a while, but hardly at all. In the last week or so it has been every time. I have installed a program called 'startupmanager'. This is the only thing that I can think would have changed settings. But uninstalling it doesn't make any difference...

Startupmanager may have left some settings behind (it has done so on my system).

Can you give me any idea how I can get rid of these settings?

I can't; the launchpad is a place where we try and fix software problems. For support questions, you should visit www.ubuntuforums.org

There is also a support section on Launchpad: http://launchpad.net/support

I don't really understand your approach here.

You've said that startupmanager HAS left settings behind on your system - is the program still installed for you? where have you found these settings left behind on your system?

Maybe if I delete these, my problem will be solved?

I'm still not sure whether this is startupmanager's problem or not. I've tried uninstalling that program but to no effect.

I've attached a photo of what my screen says at the point that the pc jams. I'm hoping someone will be able to make sense of this? Please help, it's such an annoying problem and it happens the same EVERY time - won't boot the first time but works fine the second! There must be a solution to this!

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Info as requested:

mark@mark-desktop:~$ uname -a
Linux mark-desktop 2.6.22-14-rt #1 SMP PREEMPT RT Mon Oct 15 01:05:51 GMT 2007 i686 GNU/Linux

See also attachments in this and next post. Thanks.

Hey bradford, after looking at the picture you gave me and some documentation, it looks like you may have a USB2 problem. Could you report if the command ' sudo rmmod ehci_hcd ' solves your problems? By the way, when starting your computer, do you have a USB peripheral attached? If so does this problem happen only when the peripheral is attached at boot time?
See: https://help.ubuntu.com/community/DebuggingUSBStorage

Hey bradford, after looking at the picture you gave me and some documentation, it looks like you may have a USB2 problem. Could you report if the command ' sudo rmmod ehci_hcd ' solves your problems? By the way, when starting your computer, do you have a USB peripheral attached? If so does this problem happen only when the peripheral is attached at boot time? Thank you for attaching the kernel logs!
See: https://help.ubuntu.com/community/DebuggingUSBStorage

That command doesn't solve my problems unfortunately. The only USB peripheral I have is my USB mouse, can't see why that would suddenly be a problem? For the most part, the problem does come on the assignment of bus #6.

This is my read-out from 'lsusb':

mark@mark-desktop:~$ lsusb
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 003 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel Mouse
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000

Bus #6 seems notably absent from here. Is this anything significant?

It's still having problems, even with all the usb peripherals disconnected. And it always seems to hang on the same line (see photo above) when bus #6 is assigned.

Here's today's read-out from 'lsusb' (with bus #6 present this time):

mark@mark-desktop:~$ lsusb
Bus 008 Device 001: ID 0000:0000
Bus 007 Device 001: ID 0000:0000
Bus 003 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel Mouse
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

There must be something I can do about this?

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

This is continuing to happen on ANY kernel that I use. It is always the USB bus #6 that it hangs on. I'm sure there must be an easy answer to this, it's so repeatable, it does the same thing every time (see photo here: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/163182/comments/10 and the logs above)! Please help...

I've opened a new task against the actively developed kernel 2.6.24...

Thank you for taking the time to report this bug and helping to make Ubuntu better. The Hardy Heron Alpha series was recently released. Alpha2 and subsequent releases contain an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . Please note that Alpha3 will be released within the next day or two so you many want to wait. You should be able to then test this bug with the new kernel on the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks!

Also, when you say it happens on _any_ kernel, which kernels are you talking about? Ubuntu kernels? Which versions? Hopefully trying it out with Hardy Alpha 2 or 3 will show better results...

My PC was originally a windows pc and i added ubuntu as a separate partition. I've recently been using windows for a few things and the jam in start-up has been happening on windows start-up as well as ubuntu start-up. Does my pc have some sort of memory problem on boot-up?

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 163182

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . 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.