kernel hangs while usb-stick is attached during boot

Bug #63799 reported by Jürgen
6
Affects Status Importance Assigned to Milestone
kernel-image-2.6.7-amd64 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kernel-image-2.6-amd64-generic

Hi,

I have a weird kernel lockup which can be reproduced.

I downloaded Edgy 6.10 amd64 to confirm a bug in dapper. Trying to boot from a usb stick I've unpacked the iso onto the stick and copied the contents of casper exept the big image file into the main directory of the stick in order to make it bootable with syslinux (didn't work with subdirectories). After that the boot process went without problems but hung up when the usb-stick was activated.

Ok so I burned the image but it didn't boot at all (mounting root file system)
And it got even more confused since the normal Dapper K7 (12) kernel didn't boot anymore either !

I could still boot with the regular 386 kernel

The reason was, that I still had the (non booting) usb stick in the back of my computer!!!

After removal everything worked normal again ! (CD/HD etc.)

My assumtion is that the files necessary for the boot process are somehow mixed in from the stick leading to desaster.

If it is of any help I would delete file after file from the stick to find out which file is to blame.

I consider the priority very low since it can easily be fixed, but it might lead to a clue to other strange behaviours during the boot process.

Jürgen

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the following additional information, if you have not already done so (please 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" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "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 here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks!

Revision history for this message
Mackenzie Morgan (maco.m) wrote :

In Hardy, can you boot with a USB stick attached? If you can't, can you do so in Intrepid? I haven't experienced any problems booting while my flash drive is in.

Revision history for this message
RJ Clay (rjclay) wrote :

Still pending response for more information about the status of this bug. If it is still present, please provide the further information that has been requested regarding it.

Changed in kernel-image-2.6.7-amd64:
status: New → Incomplete
Revision history for this message
Jürgen (j-w-ott) wrote : Re: [Bug 63799] Re: kernel hangs while usb-stick is attached during boot

Hi

after trying to make a USB-Stick bootable (didn't work) I didn't delete the
files. One day I forgot this stick in my PC. The PC started normal from hd
and then had a complete hangup when initializing the USB-subsystem.

My feeling was that nothing external should have any effect on the
boot-process.

Since I got no response I have overwritten the stick since and recreating the
fault will be difficult.

I will make a bootable USB-stick again and try once again the next week!

regards Jürgen Ott

Thanks for taking users serious !!

Am Samstag 30 August 2008 schrieb Jame:
> Still pending response for more information about the status of this
> bug. If it is still present, please provide the further information
> that has been requested regarding it.
>
>
> ** Changed in: kernel-image-2.6.7-amd64 (Ubuntu)
> Status: New => Incomplete

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kernel-image-2.6.7-amd64:
status: Incomplete → Invalid
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.