#1638: LiveCD fails, Hanging at "Starting init..."
-----------------------------------+----------------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  [EMAIL PROTECTED]
     Type:  defect                 |       Status:  new                         
  
 Priority:  high                   |    Milestone:  6.2                         
  
Component:  CD                     |      Version:  x86-6.1.1-3                 
  
 Severity:  normal                 |   Resolution:                              
  
 Keywords:  init unionfs           |  
-----------------------------------+----------------------------------------
Comment (by [EMAIL PROTECTED]):

 Many thanks for the screenshots, almost all of them are relevant. In fact,
 there are too many suspicious things so that there are now too many ways
 to dig.

  * on screen01.jpg, you caught __call_usermodehelper (i.e., trying to call
 /sbin/hotplug).
  * on screen02.jpg, you caught blk_unplug_work (some block device
 disappeared, huh?)
  * on screen05.jpg, there is ret_from_fork (presumably, /sbin/hotplug
 returned)
  * on screen0{6,7}.jpg, there are three SCSI error handlers. They do match
 what I have on my linux-2.6.16-ide1 system, so if there is indeed
 something SCSI-related in the laptop, they are normal. But is SCSI (or USB
 storage) really there? And why three devices?

 So please debug further in the following order:

  * Boot with the "usb-handoff" parameter
  * If that doesn't help, try removing SCSI drivers and USB host
 controllers from the kernel config one-by-one, rebuilding the kernel and
 rebooting. The end result should be one of the following:
    * SCSI is red herring here, removing all of SCSI and USB didn't help
    * Driver FOO kills the boot process, let's remove it.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/livecd/ticket/1638>
LiveCD Trac <http://wiki.linuxfromscratch.org/livecd/>
Linux From Scratch LiveCD
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to