[Dell Vostro 3750] ubuntu 12.04 doesn't boot when usb device plugged in (except usb mouse)

[Rudolfs Caune]

On DELL Vostro 3750 with Ubuntu 12.04 beta 64bit, boot stops with black screen is in one of USB ports is plugged USB device that is not USB mouse. I have tried USB HDD and laptop cooler USB and in both cases Ubuntu does not boot. It gets till grub and after that it loads for few seconds and then stops not even showing logo screen.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: djbacon 1993 F.... pulseaudio
 /dev/snd/pcmC0D0p: djbacon 1993 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf2b00000 irq 54'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,102804c6,00100100'
   Controls : 19
   Simple ctrls : 11
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=099b65c3-d636-4ada-9e1b-0e9984c79454
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Dell System Vostro 3750
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=eb98f17b-648a-4a2e-85cb-462736e19441 ro quiet splash pcie_aspm=force vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.78
SourcePackage: linux
StagingDrivers: mei zram
Tags: precise staging precise staging
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-04-06 (6 days ago)
UserGroups: adm admin lpadmin sambashare vboxusers
dmi.bios.date: 05/19/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0VP036
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/19/2011:svnDellInc.:pnDellSystemVostro3750:pvr:rvnDellInc.:rn0VP036:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System Vostro 3750
dmi.sys.vendor: Dell Inc.

[Rudolfs Caune (djbacons)]

I forgot to mention that same problem was before upgrade with Ubuntu 11.10.

[hexafraction (rarkenin)]

I'm not seeing the same issue. I have tried multiple combinations of external HDD's, flash drives, USB optical drives, webcams, etc., but have not seen any boot-up failures under 11.10. I cannot vouch for 10.04--maybe it is your system? What USB device are you using? Any hubs? Is the device in question getting power or data?(Check lights on device)

[Rudolfs Caune (djbacons)]

The USB is the one on right side. There are one USB2 and two USB3. In USB2 i have USB mouse and on USB3 i have cooler. Nothing else. USB3 is also where i plug in my USB HDD. I don't know what could be the problem, cause i do no t use any USB hubs.
Maybe it is relevant that i have dual boot with Windows 7.

The only thing that comes to mind is that when i boot with USB HDD plugged in, Ubuntu tries to boot from that USB HDD and fails. I don't know what Ubuntu "thinks" is my laptop cooler.

[Rudolfs Caune (djbacons)]

I just restarted and tested again. If i connect my laptop cooler, Ubuntu loads till the place where it should show logo screen, but instead it stops with black screen. Then i plug out cooler and it boots up properly.
Windows7 boots with cooler plugged in so this is something Ubuntu related.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 978891

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Rudolfs Caune (djbacons)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/

[Paddy Launch (paddylaunch-deactivatedaccount)]

This affects me, same laptop. I find that if I have a USB mouse plugged into either of the USB 3.0 ports on the right-hand side then boot will fail with a perpetual black screen, and the laptop fan going into noisy overdrive.

[Rudolfs Caune (djbacons)]

Now that you mentioned noisy fan, i must say that it's also getting noisy when i get black screen of failing boot.
The only difference is that my USB mouse is the only thing that can be plugged in to have successful boot. If anything else is plugged in, i get black screen and fan gets louder.

[Paddy Launch (paddylaunch-deactivatedaccount)]

I have tested using the upstream kernel, linux-image-3.4.0-030400-generic.

With a USB mouse plugged into either the USB 2.0 port or the USB / eSATA port, it boots normally.

With a USB mouse plugged into either of the USB 3.0 ports, the boot stalls exactly as described in the above bug report, except that you get the following error message on the screen:

[2.293920] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed
[2.293948] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed

[David Sanz Kirbis (bj7u6139zdyf2a6nz2ly74oec10f2lnel-info-jjcftv6wldnzq84cskygyvhqqb9qwjfcq)]

In my case, just hitting "enter" key after ubuntu startup sounds and the black screen appears makes the lightdm greeter show up, (and the startup sounds again :b )

[Ricardo Martins (ri2ario)]

Same problem with ASUS Ultrabook UX31A when I plug the wireless mouse device. I need to remove it if I restart of boot from zero.

[Joseph Salisbury (jsalisbury)]

The v3.7-rc2 kernel is now available. It would be helpful if folks affected by this bug could test this latest kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc2-raring/

[James D. (jamesd603)]

I have this same problem with raring 13.04 latest kernel and all updates, AMD 13.4 proprietary video drivers.

When my logitech USB wireless mouse is plugged into the regular USB 2 port on my HP DV6 envy notebook ubuntu hangs at boot with a black screen and the cpu fan goes faster, assuming theres a runaway process using more CPU or some kind of hang...

this is the driver... i have not tried with a usb disk drive attached yet

[ 777.219291] hid-generic 0003:046D:C521.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:12.0-1/input0
[ 777.224262] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:12.0/usb2/2-1/2-1:1.1/input/input13
[ 777.224565] hid-generic 0003:046D:C521.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:12.0-1/input1

[Jon (jricketson)]

I have also just started having this problem on a Lenovo T500. I can boot into recovery mode, but am unable to boot normally while my usb drive is connected. The cpu (as noted above) goes crazy and overheats in fairly short order and I have to let it cooldown before I can try again. Interestingly, it has happened before, but intermittently. Now it is apparently happening every time. I have tried to figure out what logs I could show, but since the boot doesn't get far enough to get to a usable system, I am a bit stumped by what I could look at.

Jonathan

[James D. (jamesd603)]

Just applied kernel 3.8.0-19-generic today to ubuntu 13.04 and so far so good. I havent done a ton of reboots to thoroughly test but previously it only took a couple tries. I will be right back to report if it happens again.

[James D. (jamesd603)]

Nope... same problem.. its worse with a usb mouse plugged in, but the lockups can happen at boot with nothing plugged in... this could be a different bug than the OP

[solazs (solazs)]

I have encountered this bug on a Dell Inspiron N7110, but only if i have anything plugged into one of my USB 3.0 ports.
I've got kernel 3.9.4 running, but it hasn't been fixed.
The system boots into recovery.
I tried booting without quiet splash options, and took a photo of the screen, but didn't see any errors.
My USB mouse gets recognized as a mouse and a driver gets assigned. then it switches to the fancy look console, than it hangs, with the fan spinnig madly.
Attached a (poor) photo of the screen with the last boot messages.

[solazs (solazs)]

Attached output of lsusb and lsusb -t with mouse plugged into the port where it was during problematic boot.
(the mouse is the one with the blank description)
if you need any other information, let me know.

[solazs (solazs)]

The problem is still there with the newest 3.11 mainline kernel.
Windows boots fine.
I've upgraded the USB chip firmware, but it didn't change anything.

[Guglielmo Collotta (gughi-coll)]

This bug also affects my Asus U36SD running Ubuntu 13.04 with 3.8.13-03081304-generic.
As James D. says, a few comments up, the lockup can also happen when nothing is plugged in,
even though far less frequently.

[Joseph Salisbury (jsalisbury)]

Can you follow the "Boot options" instructions on the following wiki to enable additional output on boot:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

[solazs (solazs)]

Here's a photo of the console output of the boot with the latest 3.11 rc5 mainline kernel, with boot options quiet splash and vt_handoff removed and debug=vc added.

[Guglielmo Collotta (gughi-coll)]

Ok, here are the logs I found. Hope these are the ones you were asking for

[Guglielmo Collotta (gughi-coll)]

also this, don't know if it can help

[Guglielmo Collotta (gughi-coll)]

I also experienced a "panic error" (I think this is how it was called) at boot when trying kernel 3.10.7

[Wojtek Zabołotny (wzab01)]

It seems, that the same, or very similar bug is reported and investigated at:
1. https://bugzilla.kernel.org/show_bug.cgi?id=42844
2. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644174

However both above reports suggested, that problem is limited to Dell Vostro 3750, and probably related to erroneous BIOS.
If this is a problem affecting broader class of machines, maybe the chances that it will be solved are better.

Is the problem you experience associated with i915 compatible GPU in your laptop?
Is the problem worked around if you boot your machine with i915.modeset=0 kernel parameter?

[Wojtek Zabołotny (wzab01)]

What are the common features of all affected machines?
Are they all using uPD720200 USB 3.0 controller and i915 GPU from Intel?
Are they all using the Optimus engine to switch between two GPUs?

[Wojtek Zabołotny (wzab01)]

Does your system hangs also if you power-up with a device connected to USB-3.0 port and disconnect it when BIOS asks for power-upp password (this would suggest that the error is associated with the information about state of the system prepared by BIOS)?

[Wojtek Zabołotny (wzab01)]

Adding the "acpi_backlight=vendor" kernel parameter allows my system (Dell Vostro 3750) to boot with different USB devices connected to the USB 3.0 ports.
This solution was suggested by Len Brown in https://bugzilla.kernel.org/show_bug.cgi?id=42844#c4
--
Regards,
Wojtek

[solazs (solazs)]

The "acpi_backlight=vendor kernel parameter does not affect the bug on my Dell Inspiron N7110.

[penalvch (penalvch)]

DJBacon, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Guglielmo Collotta (gughi-coll)]

I have had problems more frequently trying to boot after installing kernel 3.11, which started ok the first time but afterwards I couldnt boot any of the availabe kernels.
I am not sure the problem is related but here are the screenshots:

[penalvch (penalvch)]

Guglielmo Collotta, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[solazs (solazs)]

ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: solazs 1798 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=85d91b76-f19c-4de1-9335-509fe171a978
InstallationDate: Installed on 2013-09-11 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130910)
MachineType: Dell Inc. Dell System Inspiron N7110
MarkForUpload: True
Package: linux (not installed)
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=b3e93c9e-256c-4002-9511-08f3dcb87563 ro quiet splash
ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-5-generic N/A
 linux-backports-modules-3.11.0-5-generic N/A
 linux-firmware 1.113
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Tags: saucy
Uname: Linux 3.11.0-5-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/05/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 09G8VY
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA13:bd09/05/2012:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn09G8VY:rvr:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System Inspiron N7110
dmi.sys.vendor: Dell Inc.

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

apport information

[solazs (solazs)]

Sorry for the double post, but here is the requested apport-collect info from a DELL N7110 with the same problem.

[penalvch (penalvch)]

solazs, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[albert fishnets (mateolingerhaus)]

I have this same problem in ubuntu 13.10 with ASUS mother board. If any non-input device is plugged in, I cannot boot into Ubuntu. I get Grub, but after that just a blinking grey line with no output. Debian, Fedora, and Windows, boot just fine on the same machine with USB stuff plugged in. I also had to remove all of my hard drives to install 13.10. It gave the infamous intramfs error upon attempts to boot.

[penalvch (penalvch)]

albert fishnets, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Joseph Salisbury (jsalisbury)]

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

This bug was nominated against a series that is no longer supported, ie raring. The bug task representing the raring nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

This bug was nominated against a series that is no longer supported, ie quantal. The bug task representing the quantal nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[penalvch (penalvch)]

Rudolfs Caune, could you please advise if this is now resolved for you?

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release