touch-packages team mailing list archive

[SneA <vianney.bajart@xxxxxxxxx>]

Running latest Vivid daily build on Lenovo Thinkpad 10 with Samsung eMMC
MDGAGC 116 GiB:

Ubuntu 15.04 (vivid-desktop-amd64.iso 2015-02-16 8:05)
Linux 3.18.0-13-generic
systemd 218-10ubuntu1

[   12.337332] mmc0: BKOPS_EN bit is not set
[   12.348788] mmc0: new HS200 MMC card at address 0001
[   12.361382] input: ThinkPad 10 Touch Case as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:17EF:6061.0001/input/input2
[   12.361578] hid-generic 0003:17EF:6061.0001: input,hidraw0: USB HID v1.11 Keyboard [ThinkPad 10 Touch Case] on usb-0000:00:14.0-1/input0
[   12.361964] input: ThinkPad 10 Touch Case as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:17EF:6061.0002/input/input3
[   12.362273] hid-generic 0003:17EF:6061.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [ThinkPad 10 Touch Case] on usb-0000:00:14.0-1/input1
[   12.369112] mmcblk0: mmc0:0001 MDGAGC 116 GiB 
[   12.369786] mmcblk0boot0: mmc0:0001 MDGAGC partition 1 4.00 MiB
[   12.370414] mmcblk0boot1: mmc0:0001 MDGAGC partition 2 4.00 MiB
[   12.370976] mmcblk0rpmb: mmc0:0001 MDGAGC partition 3 4.00 MiB
[   12.376682]  mmcblk0: p1 p2 p3 p4

Still get these errors:

[   21.950514] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
[   21.950537] mmc0: Got data interrupt 0x00600000 even though no data operation was in progress.
[   21.952904] mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
[   21.955002] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   21.955007] mmcblk0: error -84 transferring data, sector 244277120, nr 8, cmd response 0x900, card status 0x0
[   21.955011] mmcblk0: retrying using single block read
...
[   22.197516] mmcblk0boot0: error -84 transferring data, sector 8071, nr 1, cmd response 0x900, card status 0x0
[   22.199814] mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
[   22.201911] mmcblk0boot1: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   22.201914] mmcblk0boot1: error -84 transferring data, sector 8064, nr 8, cmd response 0x900, card status 0x0
[   22.201917] mmcblk0boot1: retrying using single block read
...
[   22.241280] Buffer I/O error on dev mmcblk0boot0, logical block 1008, async page read
[   22.244301] mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
[   22.246331] mmcblk0boot1: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   22.246335] mmcblk0boot1: error -84 transferring data, sector 8064, nr 8, cmd response 0x900, card status 0x0
[   22.246337] mmcblk0boot1: retrying using single block read
[   22.248553] mmcblk0boot1: error -84 transferring data, sector 8064, nr 8, cmd response 0x900, card status 0x0
...
[   22.265044] Buffer I/O error on dev mmcblk0boot1, logical block 1008, async page read



** Attachment added: "dmesg"
   https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+attachment/4320371/+files/dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Released
Status in udisks package in Ubuntu:
  Triaged

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with "mmcblkXrpmb" if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected Memory Block is provided. This function provides means for the system to store data to the specific memory area in an authenticated and replay protected manner.
  In that case, any read/write access to this partition device will report errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  -> mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  -> mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 -> ../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 -> ../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 -> ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 -> ../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 -> ../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 -> ../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 -> ../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end"

  For issue 2:
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb"
  ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}"

  Please consider this issues fix in next udev release .

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