kernel hangs while usb-stick is attached during boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kernel-image-2.6.7-amd64 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kernel-
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
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/DebuggingKe rnelProblems> Thanks!