[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

2015-02-12 Thread Patrick Buchner
@Martin: No Problem, you find the output attached.

** Attachment added: udevadm.txt
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+attachment/4317928/+files/udevadm.txt

-- 
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:
  In Progress

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

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


[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

2015-02-12 Thread Patrick Buchner
@Martin: This was the issue, problem now solved with disabling
/lib/udev/rules.d/80-udisks.rules !

-- 
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:
  In Progress
Status in udisks package in Ubuntu:
  New

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

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


[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

2015-02-11 Thread Patrick Buchner
I tested your new rules on my Acer ES1-111M but the issue still
persists.

[1.595088] mmcblk0rpmb: mmc0:0001 HBG4e\x05 partition 3 4.00 MiB
...
[9.829699] mmcblk0rpmb: error -110 transferring data, sector 8064, nr 8, 
cmd response 0x900, card status 0xb00
[9.829706] mmcblk0rpmb: retrying using single block read
[9.831769] mmcblk0rpmb: timed out sending r/w cmd command, card status 
0x400900
[9.833802] mmcblk0rpmb: timed out sending r/w cmd command, card status 
0x400900
[9.835838] mmcblk0rpmb: timed out sending r/w cmd command, card status 
0x400900
[9.837868] mmcblk0rpmb: timed out sending r/w cmd command, card status 
0x400900
[9.839898] mmcblk0rpmb: timed out sending r/w cmd command, card status 
0x400900
[9.841937] mmcblk0rpmb: timed out sending r/w cmd command, card status 
0x400900
[9.841941] end_request: I/O error, dev mmcblk0rpmb, sector 8064
[9.841946] Buffer I/O error on device mmcblk0rpmb, logical block 1008
...

-- 
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:
  In Progress

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

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


[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

2015-02-01 Thread Patrick Buchner
Same bug occurs with Vivid (booted as live-system),

uname -a:
Linux ubuntu-desktop-next 3.18.0-12-generic #13-Ubuntu SMP Thu Jan 29 04:35:32 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

System: Acer ES1-111M

-- 
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:
  Confirmed

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

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