What new report? i just commented that i'm affected to and said what
i've done to run into the bug, i were not able to do anything within the
livesystem after the error occured, it just crashed down so that even
getty-Terminals (F1-F6) won't open.
--
Lukas Wringer http://www.
Lukas, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
--
You received this bug
trying to install ubuntu wily on MMC of my Convertible results in dozens
of errors cause of MMC I/O problems. i tried ubiquity and debootstrap,
different partition-formats (e.g.e ext 2-4, fat 32, btrfs) are also not
working except that btrfs throws more errors.
--
You received this bug notificati
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422338
T
I retract the latter part of comment #28, where I state that Ubuntu
14.04-2 is repeatably installable on this device. I have just
attempted reinstallation of Ubuntu 14.04-2 and it failed with repeated
block write errors. This indicates problems were present in the
earlier version and were not i
Jérôme Pouiller, just to advise, your attachment wouldn't be a patch
that is immediately integrable into Ubuntu.
Despite this, in order to focus on the hardware you have, and your bisect
results, please file a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
-
There are multiple cause to this bug.
However, patch in attachement may for bug described by Dan Parslow.
It is result of a bisect between a working kernel 3.14 and a non working
kernel 3.17.
** Patch added:
"0001-Revert-mmc-sdhci-add-DDR50-1.8V-mode-support-for-Bay.patch"
https://bugs.laun
Dan Parslow, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422338
Title:
I
The MMC I/O errors as detailed in the bug description continue to occur
in Vivid. This prevents installation, and also will eventually occur
with any intensive write activity, for example if attempting to copy a
working system to the eMMC with rsync.
Voyo Minipc, wih Atom CPU Z3735F, and Samsung
I also have this long boot time issue with an eMMC device on my trusty machine
(3.13.0-45 kernel).
Simply upgrading to the new systemd packages didn't help at all,
but w/ the patch mentioned in comment #26, it is working now.
--
You received this bug notification because you are a member of Ubun
I made some investigations:
In some cases system work correctly until it reboot. Applying this patch
http://permalink.gmane.org/gmane.linux.kernel.mmc/28281 help in this case.
I also find that opening eMMC ith O_SYNC (or mounting partition with "sync"
flag) improve results.
Finally, I notic
I confirm the problem on the Atom Z37xxx. (comment #23)
( 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor
Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0f) )
I get these errors while installing the system on a baytrail tablet with
eMMC (bug https://bugs.launchpad.
I encounter the bug on my think pad x250. as hard drive I use a Crucial
MX100.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422338
Title:
I/O errors on mmc partitions
To manage notifications abou
For information, I have an Atom E3845 and I observe same problem.
This issue may be related to erratas:
- For Z36xx and Z37xx, errata VLT7 described here:
http://www.intel.fr/content/dam/www/public/us/en/documents/specification-updates/atom-Z36xxx-Z37xxx-spec-update.pdf
- For E38xx, er
*** This bug is a duplicate of bug 1333140 ***
https://bugs.launchpad.net/bugs/1333140
I have just tried the 04-02-2015 vivid build with latest bios version
and the problem is still present.
Which additional information would be useful to understand the problem?
--
You received this bug not
*** This bug is a duplicate of bug 1333140 ***
https://bugs.launchpad.net/bugs/1333140
Please note that it's very unlikely that the computer's BIOS has anyhing
to do with this. It's the linux kernel which exposes these RPMB devices,
and this issue is well understood. It's certainly not "incomp
Vianney Bajart, as per http://support.lenovo.com/us/en/products/tablets
/thinkpad-tablet-series/thinkpad-10 an update to your computer's buggy
and outdated BIOS is available (1.27). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?
If it doesn't,
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422338
Title:
I/O errors on mmc partitions
To manage notifications about this bug go
apport information provided
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422338
Title:
I/O errors on mmc partitions
To manage
apport information
** Tags added: apport-collected
** Description changed:
Running live USB of the 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
Assigning to the kernel for now, as that looks like a block device
driver issue at first sight.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
> Or does this happen automatically by merely placing a card into the
reader?
In my case, /dev/mmcblk0 is not a removable SD card, it is the internal
storage of the machine that comes in the form of a embedded MMC (eMMC).
Here is the result of lsblk command:
NAME MAJ:MIN RM SIZE RO TY
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422338
Title:
I/O errors on mmc partitions
To manage notifications about this bug go to:
https:
> I get multiple errors when trying to access to mmc partitions:
Ah, so this happens if you actually try and mount the card, and try to
access it manually? Or does this happen automatically by merely placing
a card into the reader?
--
You received this bug notification because you are a member o
** Package changed: systemd (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422338
Title:
I/O errors on mmc partitions
To manage notifications about this bug go to:
https://bugs.l
25 matches
Mail list logo
