Results 1 to 8 of 8

Thread: [12.04] Boot Sometimes Hangs (kernel 3.6)

  1. #1
    Join Date
    Nov 2009
    Beans
    7

    Question [12.04] Boot Sometimes Hangs (kernel 3.6)

    Hello,
    Sometimes (out of every 5 boots or so), the boot process hangs infinitely about USB peripherals initialization.

    System: Linux G-PC 3.6.7-ck1 #1 SMP PREEMPT Mon Nov 26 21:54:56 EET 2012 i686 i686 i386 GNU/Linux

    This is a custom kernel, but the same happens when using a 3.6.x kernel from Ubuntu's mainline kernel archive. The system is otherwise stable. The problem does not happen with the official Precise 3.2 kernel.

    Here is a screenshot of the hung state:


    Here is a log file excerpt of the normal boot:
    Code:
    [    2.474129] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
    [    2.474169] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    2.474470] hub 1-1:1.0: USB hub found
    [    2.474557] hub 1-1:1.0: 6 ports detected
    [    2.515403] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    [    2.580072] usb 2-1: new high-speed USB device number 2 using ehci_hcd
    [    2.629973] tsc: Refined TSC clocksource calibration: 1696.146 MHz
    [    2.630018] Switching to clocksource tsc
    [    2.703526] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
    [    2.703581] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [    2.703929] hub 2-1:1.0: USB hub found
    [    2.704073] hub 2-1:1.0: 8 ports detected
    [    2.768156] udevd[377]: starting version 175
    [    2.863055] usb 3-3: new high-speed USB device number 2 using xhci_hcd
    [    2.884733] usb 3-3: New USB device found, idVendor=5986, idProduct=0295
    [    2.884738] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    2.884741] usb 3-3: Product: Lenovo EasyCamera
    [    2.884744] usb 3-3: Manufacturer: Vimicro corp.
    [    2.886934] wmi: Mapper loaded
    [    2.895592] lp: driver loaded but no devices found
    [    2.898560] ACPI Warning: 0x00000428-0x0000042f SystemIO conflicts with Region \PMIO 1 (20120711/utaddress-251)
    [    2.898568] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [    2.898573] ACPI Warning: 0x00000500-0x0000053f SystemIO conflicts with Region \GPIO 1 (20120711/utaddress-251)
    [    2.898577] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [    2.898578] lpc_ich: Resource conflict(s) found affecting gpio_ich
    [    2.901399] mei 0000:00:16.0: setting latency timer to 64
    [    2.901469] mei 0000:00:16.0: irq 43 for MSI/MSI-X
    [    2.908508] cfg80211: Calling CRDA to update world regulatory domain
    [    2.911087] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x12
    [    2.919386] mei 0000:00:16.0: wd: failed to find the client
    [    2.927232] [drm] Initialized drm 1.1.0 20060810
    [    2.929314] device-mapper: multipath: version 1.5.0 loaded
    [    2.938643] Intel(R) Wireless WiFi driver for Linux, in-tree:
    [    2.938644] Copyright(c) 2003-2012 Intel Corporation
    [    2.938798] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [    2.938800] iwlwifi 0000:03:00.0: pci_resource_base = f847c000
    [    2.938802] iwlwifi 0000:03:00.0: HW Revision ID = 0xC4
    [    2.939210] iwlwifi 0000:03:00.0: irq 44 for MSI/MSI-X
    [    2.951199] pci 0000:00:00.0: Intel Ivybridge Chipset
    [    2.952238] pci 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
    [    2.953392] pci 0000:00:00.0: detected 65536K stolen memory
    [    2.953439] i915 0000:00:02.0: setting latency timer to 64
    [    2.957224] i915 0000:00:02.0: irq 45 for MSI/MSI-X
    [    2.957237] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [    2.957239] [drm] Driver supports precise vblank timestamp query.
    [    2.957336] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [    2.963088] usb 1-1.2: new full-speed USB device number 3 using ehci_hcd
    [    2.994742] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x12
    [    3.000319] microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x12
    [    3.003391] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x12
    [    3.005062] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
    [    3.006507] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1
    [    3.012062] cfg80211: World regulatory domain updated:
    [    3.012065] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [    3.012067] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [    3.012070] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [    3.012072] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [    3.012073] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [    3.012075] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [    3.012999] Linux video capture interface: v2.00
    [    3.017176] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (5986:0295)
    [    3.017902] input: Lenovo EasyCamera as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/input/input4
    [    3.017976] usbcore: registered new interface driver uvcvideo
    [    3.017978] USB Video Class driver (1.1.1)
    [    3.029797] iwldvm: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [    3.029801] iwldvm: Copyright(c) 2003-2012 Intel Corporation
    [    3.029819] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
    [    3.029822] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
    [    3.029824] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
    [    3.029826] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
    [    3.029828] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
    [    3.029832] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Wireless-N 2200 BGN, REV=0x104
    [    3.029936] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [    3.037462] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio.
    [    3.048227] iwlwifi 0000:03:00.0: device EEPROM VER=0x81c, CALIB=0x6
    [    3.048232] iwlwifi 0000:03:00.0: Device SKU: 0x150
    [    3.048235] iwlwifi 0000:03:00.0: Valid Tx ant: 0x3, Valid Rx ant: 0x3
    [    3.048294] Registered led device: phy0-led
    [    3.048322] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
    [    3.048984] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c52f
    [    3.048988] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    3.048991] usb 1-1.2: Product: USB Receiver
    [    3.048994] usb 1-1.2: Manufacturer: Logitech
    [    3.056091] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
    [    3.059157] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
    [    3.083771] usbcore: registered new interface driver usbhid
    [    3.083775] usbhid: USB HID core driver
    [    3.104237] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input5
    [    3.104532] hid-generic 0003:046D:C52F.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1a.0-1.2/input0
    [    3.105387] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input6
    [    3.105600] hid-generic 0003:046D:C52F.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1a.0-1.2/input1
    [    3.423321] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
    [    3.595495] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
    [    3.632452] fbcon: inteldrmfb (fb0) is primary device
    [    3.652501] EXT4-fs (sdb1): mounted filesystem with writeback data mode. Opts: (null)
    [    3.814924] Console: switching to colour frame buffer device 170x48
    [    3.817904] fb0: inteldrmfb frame buffer device
    [    3.817904] drm: registered panic notifier
    [    3.829769] init: failsafe main process (893) killed by TERM signal
    ...
    Any help appreciated!

  2. #2
    Join Date
    Jul 2011
    Beans
    3,037
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: [12.04] Boot Sometimes Hangs (kernel 3.6)

    Are the USB devices connected to the machine in both cases the same? After the Logitech mouse (?) it seems as if a hdd is being mounted (/dev/sdb). Could this device be the problem?

  3. #3
    Join Date
    Nov 2009
    Beans
    7

    Re: [12.04] Boot Sometimes Hangs (kernel 3.6)

    Quote Originally Posted by 2F4U View Post
    Are the USB devices connected to the machine in both cases the same? After the Logitech mouse (?) it seems as if a hdd is being mounted (/dev/sdb). Could this device be the problem?
    Hi,
    Thanks for your reply.
    sdb is the internal hard drive device (sda being the SSD root filesystem is on) so it is not the problem.
    I also tried without any USB device plugged in, but the problem still occured sometimes.

  4. #4
    dino99's Avatar
    dino99 is offline Ubuntu addict and loving it
    Join Date
    Jun 2006
    Location
    Nux Jam
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: [12.04] Boot Sometimes Hangs (kernel 3.6)

    there are some issues around like yours, and seems related to some hardware. So the better is to try finding something usefull logged .

    but try updating the pciids & usbids

    Code:
    sudo update-pciids && update-usbids

  5. #5
    Join Date
    Nov 2009
    Beans
    7

    Re: [12.04] Boot Sometimes Hangs (kernel 3.6)

    Quote Originally Posted by dino99 View Post
    there are some issues around like yours, and seems related to some hardware. So the better is to try finding something usefull logged .

    but try updating the pciids & usbids

    Code:
    sudo update-pciids && update-usbids
    Hi,
    Ran the two commands and updated the IDs. Will see if that does help with this problem.
    The hardware details are as below:
    Code:
    $ sudo lspci
    00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
    00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
    00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
    00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
    00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
    00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
    00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
    00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
    00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
    00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
    02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
    03:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4)
    $ sudo lsusb
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 003 Device 002: ID 5986:0295 Acer, Inc 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Wireless Mouse M305

  6. #6
    Join Date
    Jan 2013
    Beans
    1

    Re: [12.04] Boot Sometimes Hangs (kernel 3.6)

    Any luck with the problem? I am facing the same problem on ubuntu 12.04 3.2.0-35-generic-pae.
    Whenever it hangs, nothing is logged in dmesg, kern.log and syslog. Not sure how I should debug the problem.

  7. #7
    Join Date
    Mar 2013
    Beans
    1

    Re: [12.04] Boot Sometimes Hangs (kernel 3.6)

    I have the very same problem! If the rootfs is on the SSD, it won't boot (it will mount the rootfs just fine according to the kernel output) and if the rootfs is on my (now external) SATA disk, then it boots just fine! For me, it actually during EVERY boot from the SSD, and it hangs after scanning the ata bus and switching to tsc

    BTW: you can boot with the kernel parameter "nousb" and you will see, that it's not USB related.

    I'm using a self-compiled 3.8.x kernel. And actually I'm not using Ubuntu but Gentoo.

  8. #8
    Join Date
    Mar 2014
    Beans
    1

    Re: [12.04] Boot Sometimes Hangs (kernel 3.6)

    Quote Originally Posted by Nase0815 View Post
    I have the very same problem! If the rootfs is on the SSD, it won't boot (it will mount the rootfs just fine according to the kernel output) and if the rootfs is on my (now external) SATA disk, then it boots just fine! For me, it actually during EVERY boot from the SSD, and it hangs after scanning the ata bus and switching to tsc

    BTW: you can boot with the kernel parameter "nousb" and you will see, that it's not USB related.

    I'm using a self-compiled 3.8.x kernel. And actually I'm not using Ubuntu but Gentoo.
    The cause might be the following:

    * you have copied the root filesystem from old drive to new (SSD) drive WITHOUT the /dev directory and your kernel does not use or mount /dev temporary filesystem automatically

    In that case you have few ways to solve it:

    * copy the missing /dev files from the old drive
    * OR make sure your kernel has DEVTMPFS support built-in and make sure kernel mounts the /dev on boot (configuration option DEVTMPFS_MOUNT or kernel boot parameter 'devtmpfs.mount=1')

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •