dolfyn, 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: bios-outdated-cdcn37ww
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1622376
Title:
Mounting SDXC Cards unreliable
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ubuntu 16.04 Lenovo Y700 laptop
Using Sandisk SDXC Cards (camera/pictures) works for one card (mounts)
but not for the other (does not mount). Cars and built-in reader works
without any problems in this other (obviously) popular OS.
Conclusion: both cards are OK, the reader is OK.
The mounting card:
[94183.755973] mmc0: new ultra high speed DDR50 SDXC card at address aaaa
[94183.756646] mmcblk0: mmc0:aaaa SL64G 59.5 GiB
[94183.770742] mmcblk0: p1
udisksd[3993]: Mounted /dev/mmcblk0p1 at /media/xxx/6337-6134 on behalf of
uid 1000
.
.
.
udisksd[3993]: Cleaning up mount point /media/xxx/6337-6134 (device 179:1 is
not mounted)
udisksd[3993]: Unmounted /dev/mmcblk0p1 on behalf of uid 1000
[94251.132197] mmc0: card aaaa removed
The failing card (does not fail when running under an alternative OS):
[94804.132020] sdhci: Timeout waiting for Buffer Read Ready interrupt during
tuning procedure, falling back to fixed sampling clock
[94804.132100] mmc0: tuning execution failed
[94804.132111] mmc0: error -5 whilst initialising SD card
Curious...
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: hk 3842 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Sep 11 20:12:15 2016
HibernationDevice: RESUME=UUID=87c83c29-86d9-4674-a81c-4012e557565f
InstallationDate: Installed on 2016-06-21 (82 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Lsusb:
Bus 002 Device 002: ID 8086:0a66 Intel Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80NV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed
root=UUID=560e20f5-d2aa-48c1-ab12-55c2a34639f8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-36-generic N/A
linux-backports-modules-4.4.0-36-generic N/A
linux-firmware 1.157.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: CDCN35WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Allsparks 5A
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad Y700-15ISK
dmi.modalias:
dmi:bvnLENOVO:bvrCDCN35WW:bd03/29/2016:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
dmi.product.name: 80NV
dmi.product.version: Lenovo ideapad Y700-15ISK
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622376/+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
