Daro, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your 
earliest convenience, could you please test the latest upstream kernel 
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please 
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Tags added: latest-bios-a14 regression-update

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1653009

Title:
  Ubuntu 16.04 fails to boot from Sandisk usb stick with latest kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There is a regression from 4.4.0-45.66 to 4.4.0-47.68.

  While booting I get error:
  [    6.669572] usb 2-1.2: device descriptor read/64, error -110

  and booting process fails resuming to BusyBox

  The workaround is to unplug and replug the usb stick and the booting
  process goes further

  [   15.652666] usb 2-1.2: new high-speed USB device number 7 using ehci-pci
  [   15.746752] usb 2-1.2: New USB device found, idVendor=0781, idProduct=5583
  [   15.748238] usb 2-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [   15.749708] usb 2-1.2: Product: Ultra Fit
  [   15.751156] usb 2-1.2: Manufacturer: SanDisk
  [   15.752588] usb 2-1.2: SerialNumber: 4C530001160413113001
  [   15.758906] usb-storage 2-1.2:1.0: USB Mass Storage device detected

  On 4.4.0-45.66 kernel everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  darek      1386 F.... pulseaudio
  CurrentDesktop: LXDE
  Date: Wed Dec 28 22:14:27 2016
  HibernationDevice: RESUME=UUID=e7e49edd-f274-4ac4-ae57-ebbeb8082257
  InstallationDate: Installed on 2015-11-10 (414 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E5420
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=ee3725ef-3af5-4853-84aa-d4526d8e6014 ro priority=low rootwait
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware                            1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (249 days ago)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0H5TG2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653009/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to