search for: mmcblk0

...atching hardware (0)! [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: earlyprintk=xenboot lpj=8000000 console=ttyAMA1 root=/dev/mmcblk0 debug rw init=/bin/bash [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] __ex_table already sorted, skipping sor...

...xenbits.xen.org/xen.git and my device tree comes from: git://xenbits.xen.org/people/sstabellini/device-trees.git . These are my xen and kernel arguments: bootargs = "dom0_mem=128M dom0_max_vcpus=1 console=com1,vga"; xen,dom0-bootargs = "earlyprintk=xenboot console=ttyAMA0 root=/dev/mmcblk0 init=/bin/bash rw ip=dhcp"; This is how I launch the model ( where the variables of course contain the right paths ): ./model_shell ../resources/Cortex-A15x1/cadi_system_Linux-Release-GCC-4.4.so $1 -C motherboard.flashloader0.fname=$2 -C motherboard.smsc_91c111.enabled=1 -C motherboard.hostbr...

Hello list, in a previous post I mentioned I had managed to make USB-Stick with 2048 byte sectors bootable. In fact I wiped out my Linux partitions bootrecord. This was with an old version of extlinux as still distributed by openSuSE. Interestingly enough the current version syslinux-3.61-pre2, spares my hard disk, but still seems to live under the impression it is the USB stick. The setup is

...10:06 by lists at colorremedies.com: > On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz <> rgm at htt-consult.com> > wrote: > >> ---------------------------------------- >> > SSD's, in particular SD Cards (which you're not using, which is noted as > /dev/mmcblk0...) store you data as a probabilistic representation, and > through a lot of magic, the probability of retrieving your data correctly > from SSD is made very high. Almost deterministic. > > The magic is in the firmware, and so there's some possibility any given SSD > problem is r...

On 08/09/2017 10:46 AM, Chris Murphy wrote: > If it's a bad sector problem, you'd write to sector 17066160 and see if the > drive complies or spits back a write error. It looks like a bad sector in > that the same LBA is reported each time but I've only ever seen this with > both a read error and a UNC error. So I'm not sure it's a bad sector. > > What is

...tes [ 4.808742] Btrfs loaded, crc32c=crc32c-generic [ 4.809731] mvebu-pcie soc:pcie: /soc/pcie/pcie at 2,0: reset gpio is active low [ 4.809763] mvebu-pcie soc:pcie: /soc/pcie/pcie at 3,0: reset gpio is active low [ 4.855040] mmc0: new high speed SDHC card at address aaaa [ 4.855241] mmcblk0: mmc0:aaaa SL16G 14.8 GiB [ 4.857099] mmcblk0: p1 p2 [ 4.905724] ata1.00: ATA-9: Samsung SSD 850 EVO mSATA 250GB, EMT41B6Q, max UDMA/133 [ 4.913401] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32) [ 4.923153] ata1.00: supports DRM functions and may not be fully accessible...

...it's a new SSD it's slightly concerning. You can either keep an eye on it, or put a little pressure on the manufacturer or place of purchase that you have a bad sector and would like to swap out the unit. SSD's, in particular SD Cards (which you're not using, which is noted as /dev/mmcblk0...) store you data as a probabilistic representation, and through a lot of magic, the probability of retrieving your data correctly from SSD is made very high. Almost deterministic. The magic is in the firmware, and so there's some possibility any given SSD problem is related to a firmware bug...

...tes [ 4.799285] Btrfs loaded, crc32c=crc32c-generic [ 4.799923] mvebu-pcie soc:pcie: /soc/pcie/pcie at 2,0: reset gpio is active low [ 4.799955] mvebu-pcie soc:pcie: /soc/pcie/pcie at 3,0: reset gpio is active low [ 4.845740] mmc0: new high speed SDHC card at address aaaa [ 4.845942] mmcblk0: mmc0:aaaa SL16G 14.8 GiB [ 4.847782] mmcblk0: p1 p2 [ 4.897477] ata1.00: ATA-9: Samsung SSD 850 EVO mSATA 250GB, EMT41B6Q, max UDMA/133 [ 4.905155] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32) [ 4.914917] ata1.00: supports DRM functions and may not be fully accessible...

Hi Ben, Thanks for your reply. My replies follow in between. Luís On Thu, Jan 25, 2018 at 5:40 AM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 24 January 2018 at 06:19, Luís Mendes <luis.p.mendes at gmail.com> wrote: >> Hi Arnd, >> >> Sorry for sending this email directly to you, but maybe you can help >> me, or guide me where to look for. >>

...n 25 13:16:36 localhost kernel: [ 9.361305] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0 Jan 25 13:16:36 localhost kernel: [ 9.658257] Adding 1952764k swap on /dev/sda1. Priority:-2 extents:1 across:1952764k SS Jan 25 13:16:36 localhost kernel: [ 10.274184] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Jan 25 13:16:38 localhost kernel: [ 13.686118] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 25 13:16:39 localhost kernel: [ 13.783210] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 25 13:16:39 localhost ke...

...te Protect is off [ 4.728269] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 4.728949] sda: sda1 sda2 sda3 [ 4.729516] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 4.765833] mmc0: new high speed SDHC card at address aaaa [ 4.765986] mmcblk0: mmc0:aaaa SL16G 14.8 GiB [ 4.767826] mmcblk0: p1 p2 [ 4.946475] ata3: SATA link down (SStatus 0 SControl 300) [ 4.952279] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00 [ 4.958215] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 4.964583] pci_bus 0000:00: root bus re...

Hi everyone, I''m trying to start up domU on xen for ARM (Cortex-A15 Fast models). I follow the instructions to build xen-tools with this link: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling. But there seems to be something wrong when I start up domU. First, I get errors in create domU with xl: root@(none):/home/xiaogw# xl create domU-config xc: error:

This series of patches makes Xen pass a (somewhat) valid device tree to dom0. The device tree for dom0 is the same as the one supplied to Xen except the memory and chosen nodes are adjusted appropriately. We don''t yet make use of the device tree to map MMIO regions or setup interrupts for the guest and we still include the UART used for Xen''s console. Note that loading Linux

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See