Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 908710 Details for
Bug 1109435
[abrt] WARNING: CPU: 0 PID: 5257 at fs/fs-writeback.c:1197 __mark_inode_dirty+0x26d/0x270()
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
File: dmesg
dmesg (text/plain), 200.33 KB, created by
Todd Dragovich
on 2014-06-13 22:06:09 UTC
(
hide
)
Description:
File: dmesg
Filename:
MIME Type:
Creator:
Todd Dragovich
Created:
2014-06-13 22:06:09 UTC
Size:
200.33 KB
patch
obsolete
>[ 0.000000] Initializing cgroup subsys cpuset >[ 0.000000] Initializing cgroup subsys cpu >[ 0.000000] Initializing cgroup subsys cpuacct >[ 0.000000] Linux version 3.14.4-200.fc20.x86_64 (mockbuild@bkernel02) (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) ) #1 SMP Tue May 13 13:51:08 UTC 2014 >[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.14.4-200.fc20.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root rhgb quiet >[ 0.000000] e820: BIOS-provided physical RAM map: >[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dbff] usable >[ 0.000000] BIOS-e820: [mem 0x000000000009dc00-0x000000000009ffff] reserved >[ 0.000000] BIOS-e820: [mem 0x00000000000d0000-0x00000000000fffff] reserved >[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000d7e6ffff] usable >[ 0.000000] BIOS-e820: [mem 0x00000000d7e70000-0x00000000d7e82fff] ACPI data >[ 0.000000] BIOS-e820: [mem 0x00000000d7e83000-0x00000000d7e84fff] ACPI NVS >[ 0.000000] BIOS-e820: [mem 0x00000000d7e85000-0x00000000efffffff] reserved >[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved >[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved >[ 0.000000] BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved >[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000011fffffff] usable >[ 0.000000] NX (Execute Disable) protection: active >[ 0.000000] SMBIOS 2.4 present. >[ 0.000000] DMI: TOSHIBA Satellite A215/IALAA, BIOS V2.30 01/15/2010 >[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved >[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable >[ 0.000000] e820: last_pfn = 0x120000 max_arch_pfn = 0x400000000 >[ 0.000000] MTRR default type: uncachable >[ 0.000000] MTRR fixed ranges enabled: >[ 0.000000] 00000-9FFFF write-back >[ 0.000000] A0000-BFFFF uncachable >[ 0.000000] C0000-CFFFF write-protect >[ 0.000000] D0000-DFFFF uncachable >[ 0.000000] E0000-FFFFF write-protect >[ 0.000000] MTRR variable ranges enabled: >[ 0.000000] 0 base 0000000000 mask FF80000000 write-back >[ 0.000000] 1 base 0080000000 mask FFC0000000 write-back >[ 0.000000] 2 base 00C0000000 mask FFE0000000 write-back >[ 0.000000] 3 disabled >[ 0.000000] 4 disabled >[ 0.000000] 5 disabled >[ 0.000000] 6 disabled >[ 0.000000] 7 disabled >[ 0.000000] TOM2: 0000000120000000 aka 4608M >[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 >[ 0.000000] e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved >[ 0.000000] e820: last_pfn = 0xd7e70 max_arch_pfn = 0x400000000 >[ 0.000000] found SMP MP-table at [mem 0x000f7300-0x000f730f] mapped at [ffff8800000f7300] >[ 0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576 >[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff] >[ 0.000000] [mem 0x00000000-0x000fffff] page 4k >[ 0.000000] BRK [0x0201c000, 0x0201cfff] PGTABLE >[ 0.000000] BRK [0x0201d000, 0x0201dfff] PGTABLE >[ 0.000000] BRK [0x0201e000, 0x0201efff] PGTABLE >[ 0.000000] init_memory_mapping: [mem 0x11fe00000-0x11fffffff] >[ 0.000000] [mem 0x11fe00000-0x11fffffff] page 2M >[ 0.000000] BRK [0x0201f000, 0x0201ffff] PGTABLE >[ 0.000000] init_memory_mapping: [mem 0x11c000000-0x11fdfffff] >[ 0.000000] [mem 0x11c000000-0x11fdfffff] page 2M >[ 0.000000] init_memory_mapping: [mem 0x100000000-0x11bffffff] >[ 0.000000] [mem 0x100000000-0x11bffffff] page 2M >[ 0.000000] init_memory_mapping: [mem 0x00100000-0xd7e6ffff] >[ 0.000000] [mem 0x00100000-0x001fffff] page 4k >[ 0.000000] [mem 0x00200000-0xd7dfffff] page 2M >[ 0.000000] [mem 0xd7e00000-0xd7e6ffff] page 4k >[ 0.000000] RAMDISK: [mem 0x35b24000-0x36d89fff] >[ 0.000000] ACPI: RSDP 00000000000f7260 000024 (v02 TOSCPL) >[ 0.000000] ACPI: XSDT 00000000d7e7aa9c 000064 (v01 TOSCPL TOSCPL00 06040000 LTP 00000000) >[ 0.000000] ACPI: FACP 00000000d7e8297b 0000F4 (v03 TOSCPL Herring 06040000 ATI 000F4240) >[ 0.000000] ACPI: DSDT 00000000d7e7ab00 007E7B (v01 TOSCPL SB600 06040000 MSFT 03000000) >[ 0.000000] ACPI: FACS 00000000d7e84fc0 000040 >[ 0.000000] ACPI: TCPA 00000000d7e82ae3 000032 (v02 TOSCPL 06040000 PTEC 00000000) >[ 0.000000] ACPI: SLIC 00000000d7e82b15 000176 (v01 TOSCPL TOSCPL00 06040000 LOHR 00000000) >[ 0.000000] ACPI: SSDT 00000000d7e82c8b 000182 (v01 PTLTD POWERNOW 06040000 LTP 00000001) >[ 0.000000] ACPI: APIC 00000000d7e82e0d 000054 (v01 PTLTD ? APIC 06040000 LTP 00000000) >[ 0.000000] ACPI: MCFG 00000000d7e82e61 00003C (v01 PTLTD MCFG 06040000 LTP 00000000) >[ 0.000000] ACPI: HPET 00000000d7e82e9d 000038 (v01 PTLTD HPETTBL 06040000 LTP 00000001) >[ 0.000000] ACPI: ASF! 00000000d7e82ed5 00012B (v32 DMA AMDTBL 06040000 PTL 00000001) >[ 0.000000] ACPI: Local APIC address 0xfee00000 >[ 0.000000] Scanning NUMA topology in Northbridge 24 >[ 0.000000] No NUMA configuration found >[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000011fffffff] >[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x11fffffff] >[ 0.000000] NODE_DATA [mem 0x11ffe8000-0x11fffbfff] >[ 0.000000] [ffffea0000000000-ffffea00047fffff] PMD -> [ffff88011b800000-ffff88011f5fffff] on node 0 >[ 0.000000] Zone ranges: >[ 0.000000] DMA [mem 0x00001000-0x00ffffff] >[ 0.000000] DMA32 [mem 0x01000000-0xffffffff] >[ 0.000000] Normal [mem 0x100000000-0x11fffffff] >[ 0.000000] Movable zone start for each node >[ 0.000000] Early memory node ranges >[ 0.000000] node 0: [mem 0x00001000-0x0009cfff] >[ 0.000000] node 0: [mem 0x00100000-0xd7e6ffff] >[ 0.000000] node 0: [mem 0x100000000-0x11fffffff] >[ 0.000000] On node 0 totalpages: 1015308 >[ 0.000000] DMA zone: 64 pages used for memmap >[ 0.000000] DMA zone: 21 pages reserved >[ 0.000000] DMA zone: 3996 pages, LIFO batch:0 >[ 0.000000] DMA32 zone: 13754 pages used for memmap >[ 0.000000] DMA32 zone: 880240 pages, LIFO batch:31 >[ 0.000000] Normal zone: 2048 pages used for memmap >[ 0.000000] Normal zone: 131072 pages, LIFO batch:31 >[ 0.000000] Detected use of extended apic ids on hypertransport bus >[ 0.000000] ACPI: PM-Timer IO Port: 0x8008 >[ 0.000000] ACPI: Local APIC address 0xfee00000 >[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) >[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) >[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) >[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) >[ 0.000000] IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23 >[ 0.000000] ACPI: IRQ9 used by override. >[ 0.000000] Using ACPI (MADT) for SMP configuration information >[ 0.000000] ACPI: HPET id: 0x43538310 base: 0xfed00000 >[ 0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs >[ 0.000000] nr_irqs_gsi: 40 >[ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff] >[ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff] >[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000cffff] >[ 0.000000] PM: Registered nosave memory: [mem 0x000d0000-0x000fffff] >[ 0.000000] PM: Registered nosave memory: [mem 0xd7e70000-0xd7e82fff] >[ 0.000000] PM: Registered nosave memory: [mem 0xd7e83000-0xd7e84fff] >[ 0.000000] PM: Registered nosave memory: [mem 0xd7e85000-0xefffffff] >[ 0.000000] PM: Registered nosave memory: [mem 0xf0000000-0xfebfffff] >[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec0ffff] >[ 0.000000] PM: Registered nosave memory: [mem 0xfec10000-0xfedfffff] >[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff] >[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xffefffff] >[ 0.000000] PM: Registered nosave memory: [mem 0xfff00000-0xffffffff] >[ 0.000000] e820: [mem 0xf0000000-0xfebfffff] available for PCI devices >[ 0.000000] Booting paravirtualized kernel on bare hardware >[ 0.000000] setup_percpu: NR_CPUS:1024 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1 >[ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88011fc00000 s86848 r8192 d23744 u1048576 >[ 0.000000] pcpu-alloc: s86848 r8192 d23744 u1048576 alloc=1*2097152 >[ 0.000000] pcpu-alloc: [0] 0 1 >[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 999421 >[ 0.000000] Policy zone: Normal >[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.14.4-200.fc20.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root rhgb quiet >[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) >[ 0.000000] Memory: 3895672K/4061232K available (7182K kernel code, 1079K rwdata, 3044K rodata, 1448K init, 1644K bss, 165560K reserved) >[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 >[ 0.000000] Hierarchical RCU implementation. >[ 0.000000] RCU restricting CPUs from NR_CPUS=1024 to nr_cpu_ids=2. >[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 >[ 0.000000] NR_IRQS:65792 nr_irqs:512 16 >[ 0.000000] spurious 8259A interrupt: IRQ7. >[ 0.000000] Console: colour VGA+ 80x25 >[ 0.000000] console [tty0] enabled >[ 0.000000] allocated 16252928 bytes of page_cgroup >[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups >[ 0.000000] hpet clockevent registered >[ 0.000000] tsc: Fast TSC calibration using PIT >[ 0.000000] tsc: Detected 1596.023 MHz processor >[ 0.000000] tsc: Marking TSC unstable due to TSCs unsynchronized >[ 0.002018] Calibrating delay loop (skipped), value calculated using timer frequency.. 3192.04 BogoMIPS (lpj=1596023) >[ 0.002023] pid_max: default: 32768 minimum: 301 >[ 0.002038] ACPI: Core revision 20131218 >[ 0.002041] TOSHIBA Satellite detected - force copy of DSDT to local memory >[ 0.002198] ACPI: Forced DSDT copy: length 0x07E7B copied locally, original unmapped >[ 0.008661] ACPI: All ACPI Tables successfully acquired >[ 0.009050] Security Framework initialized >[ 0.009062] SELinux: Initializing. >[ 0.009073] SELinux: Starting in permissive mode >[ 0.010318] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) >[ 0.013470] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) >[ 0.015184] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) >[ 0.015213] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes) >[ 0.015669] Initializing cgroup subsys memory >[ 0.015680] Initializing cgroup subsys devices >[ 0.015683] Initializing cgroup subsys freezer >[ 0.015686] Initializing cgroup subsys net_cls >[ 0.015689] Initializing cgroup subsys blkio >[ 0.015692] Initializing cgroup subsys perf_event >[ 0.015696] Initializing cgroup subsys hugetlb >[ 0.015735] tseg: 00d7f00000 >[ 0.015739] CPU: Physical Processor ID: 0 >[ 0.015741] CPU: Processor Core ID: 0 >[ 0.015744] mce: CPU supports 5 MCE banks >[ 0.015754] LVT offset 0 assigned for vector 0xf9 >[ 0.015759] process: using AMD E400 aware idle routine >[ 0.015764] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4 >Last level dTLB entries: 4KB 512, 2MB 8, 4MB 4, 1GB 0 >tlb_flushall_shift: 6 >[ 0.015889] Freeing SMP alternatives memory: 24K (ffffffff81e79000 - ffffffff81e7f000) >[ 0.017198] ftrace: allocating 26320 entries in 103 pages >[ 0.029556] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1 >[ 0.031000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC >[ 0.031000] ...trying to set up timer (IRQ0) through the 8259A ... >[ 0.031000] ..... (found apic 0 pin 0) ... >[ 0.041169] ....... works. >[ 0.041171] smpboot: CPU0: AMD Turion(tm) 64 X2 Mobile Technology TL-52 (fam: 0f, model: 48, stepping: 02) >[ 0.042000] Performance Events: AMD PMU driver. >[ 0.042000] ... version: 0 >[ 0.042000] ... bit width: 48 >[ 0.042000] ... generic registers: 4 >[ 0.042000] ... value mask: 0000ffffffffffff >[ 0.042000] ... max period: 00007fffffffffff >[ 0.042000] ... fixed-purpose events: 0 >[ 0.042000] ... event mask: 000000000000000f >[ 0.043254] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. >[ 0.043411] x86: Booting SMP configuration: >[ 0.043415] .... node #0, CPUs: #1 >[ 0.003000] process: System has AMD C1E enabled >[ 0.114048] process: Switch to broadcast mode on CPU1 >[ 0.114096] x86: Booted up 1 node, 2 CPUs >[ 0.114100] smpboot: Total of 2 processors activated (6383.92 BogoMIPS) >[ 0.114776] process: Switch to broadcast mode on CPU0 >[ 0.114776] devtmpfs: initialized >[ 0.123000] PM: Registering ACPI NVS region [mem 0xd7e83000-0xd7e84fff] (8192 bytes) >[ 0.124230] atomic64 test passed for x86-64 platform with CX8 and with SSE >[ 0.124234] pinctrl core: initialized pinctrl subsystem >[ 0.124321] RTC time: 15:56:21, date: 06/13/14 >[ 0.124400] NET: Registered protocol family 16 >[ 0.124608] cpuidle: using governor menu >[ 0.124617] node 0 link 0: io port [1000, fffff] >[ 0.124621] TOM: 00000000e0000000 aka 3584M >[ 0.124624] node 0 link 0: mmio [f8100000, ffffffff] >[ 0.124629] node 0 link 0: mmio [f8000000, f80fffff] >[ 0.124632] node 0 link 0: mmio [f8000000, f7ffffff] >[ 0.124635] node 0 link 0: mmio [f0000000, f7ffffff] >[ 0.124638] node 0 link 0: mmio [a0000, bffff] >[ 0.124641] node 0 link 0: mmio [f0000000, efffffff] >[ 0.124644] node 0 link 0: mmio [e0000000, efffffff] >[ 0.124648] node 0 link 0: mmio [e0000000, dfffffff] >[ 0.124650] TOM2: 0000000120000000 aka 4608M >[ 0.124655] bus: [bus 00-ff] on node 0 link 0 >[ 0.124657] bus: 00 [io 0x0000-0xffff] >[ 0.124660] bus: 00 [mem 0xe0000000-0xffffffff] >[ 0.124662] bus: 00 [mem 0x000a0000-0x000bffff] >[ 0.124664] bus: 00 [mem 0x120000000-0xfcffffffff] >[ 0.124761] ACPI: bus type PCI registered >[ 0.124765] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 >[ 0.124895] PCI: MMCONFIG for domain 0000 [bus 00-1a] at [mem 0xe0000000-0xe1afffff] (base 0xe0000000) >[ 0.124900] PCI: MMCONFIG at [mem 0xe0000000-0xe1afffff] reserved in E820 >[ 0.126647] PCI: Using configuration type 1 for base access >[ 0.130100] bio: create slab <bio-0> at 0 >[ 0.130105] ACPI: Added _OSI(Module Device) >[ 0.130111] ACPI: Added _OSI(Processor Device) >[ 0.130113] ACPI: Added _OSI(3.0 _SCP Extensions) >[ 0.130115] ACPI: Added _OSI(Processor Aggregator Device) >[ 0.131954] ACPI Error: No handler for Region [ERAM] (ffff88011b43cea0) [EmbeddedControl] (20131218/evregion-162) >[ 0.131961] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20131218/exfldio-299) >[ 0.131967] ACPI Error: Method parse/execution failed [\_SB_.HTEV] (Node ffff88011b437780), AE_NOT_EXIST (20131218/psparse-536) >[ 0.131976] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPC0.EC0_._REG] (Node ffff88011b441078), AE_NOT_EXIST (20131218/psparse-536) >[ 0.134571] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored >[ 0.140052] ACPI: Interpreter enabled >[ 0.140060] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-580) >[ 0.140066] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580) >[ 0.140087] ACPI: (supports S0 S3 S4 S5) >[ 0.140090] ACPI: Using IOAPIC for interrupt routing >[ 0.140196] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug >[ 0.140403] ACPI: No dock devices found. >[ 0.140822] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness >[ 0.140854] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness >[ 0.221685] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness >[ 0.221721] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness >[ 0.223805] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) >[ 0.223815] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] >[ 0.223879] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] >[ 0.226521] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-1a] only partially covers this bridge >[ 0.226869] PCI host bridge to bus 0000:00 >[ 0.226874] pci_bus 0000:00: root bus resource [bus 00-ff] >[ 0.226879] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] >[ 0.226882] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d1fff] >[ 0.226886] pci_bus 0000:00: root bus resource [mem 0x000d2000-0x000d3fff] >[ 0.226890] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d5fff] >[ 0.226893] pci_bus 0000:00: root bus resource [mem 0x000d6000-0x000d7fff] >[ 0.226897] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000d9fff] >[ 0.226901] pci_bus 0000:00: root bus resource [mem 0x000da000-0x000dbfff] >[ 0.226904] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000ddfff] >[ 0.226908] pci_bus 0000:00: root bus resource [mem 0x000de000-0x000dffff] >[ 0.226912] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xffffffff] >[ 0.226916] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] >[ 0.226919] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] >[ 0.226931] pci 0000:00:00.0: [1002:7910] type 00 class 0x060000 >[ 0.227084] pci 0000:00:01.0: [1002:7912] type 01 class 0x060400 >[ 0.227244] pci 0000:00:05.0: [1002:7915] type 01 class 0x060400 >[ 0.227290] pci 0000:00:05.0: PME# supported from D0 D3hot D3cold >[ 0.227362] pci 0000:00:05.0: System wakeup disabled by ACPI >[ 0.227438] pci 0000:00:06.0: [1002:7916] type 01 class 0x060400 >[ 0.227484] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold >[ 0.227553] pci 0000:00:06.0: System wakeup disabled by ACPI >[ 0.227627] pci 0000:00:07.0: [1002:7917] type 01 class 0x060400 >[ 0.227673] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold >[ 0.227827] pci 0000:00:12.0: [1002:4380] type 00 class 0x01018f >[ 0.227851] pci 0000:00:12.0: reg 0x10: [io 0x8440-0x8447] >[ 0.227864] pci 0000:00:12.0: reg 0x14: [io 0x8434-0x8437] >[ 0.227878] pci 0000:00:12.0: reg 0x18: [io 0x8438-0x843f] >[ 0.227891] pci 0000:00:12.0: reg 0x1c: [io 0x8430-0x8433] >[ 0.227904] pci 0000:00:12.0: reg 0x20: [io 0x8400-0x840f] >[ 0.227918] pci 0000:00:12.0: reg 0x24: [mem 0xf8709000-0xf87093ff] >[ 0.227944] pci 0000:00:12.0: set SATA to AHCI mode >[ 0.228101] pci 0000:00:13.0: [1002:4387] type 00 class 0x0c0310 >[ 0.228119] pci 0000:00:13.0: reg 0x10: [mem 0xf8704000-0xf8704fff] >[ 0.228262] pci 0000:00:13.0: System wakeup disabled by ACPI >[ 0.228341] pci 0000:00:13.1: [1002:4388] type 00 class 0x0c0310 >[ 0.228359] pci 0000:00:13.1: reg 0x10: [mem 0xf8705000-0xf8705fff] >[ 0.228499] pci 0000:00:13.1: System wakeup disabled by ACPI >[ 0.228571] pci 0000:00:13.2: [1002:4389] type 00 class 0x0c0310 >[ 0.228590] pci 0000:00:13.2: reg 0x10: [mem 0xf8706000-0xf8706fff] >[ 0.228727] pci 0000:00:13.2: System wakeup disabled by ACPI >[ 0.228805] pci 0000:00:13.3: [1002:438a] type 00 class 0x0c0310 >[ 0.228823] pci 0000:00:13.3: reg 0x10: [mem 0xf8707000-0xf8707fff] >[ 0.228960] pci 0000:00:13.3: System wakeup disabled by ACPI >[ 0.229031] pci 0000:00:13.4: [1002:438b] type 00 class 0x0c0310 >[ 0.229049] pci 0000:00:13.4: reg 0x10: [mem 0xf8708000-0xf8708fff] >[ 0.229191] pci 0000:00:13.4: System wakeup disabled by ACPI >[ 0.229270] pci 0000:00:13.5: [1002:4386] type 00 class 0x0c0320 >[ 0.229294] pci 0000:00:13.5: reg 0x10: [mem 0xf8709400-0xf87094ff] >[ 0.229395] pci 0000:00:13.5: supports D1 D2 >[ 0.229398] pci 0000:00:13.5: PME# supported from D0 D1 D2 D3hot >[ 0.229477] pci 0000:00:13.5: System wakeup disabled by ACPI >[ 0.229557] pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500 >[ 0.229585] pci 0000:00:14.0: reg 0x10: [io 0x8410-0x841f] >[ 0.229789] pci 0000:00:14.1: [1002:438c] type 00 class 0x01018a >[ 0.229806] pci 0000:00:14.1: reg 0x10: [io 0x01f0-0x01f7] >[ 0.229819] pci 0000:00:14.1: reg 0x14: [io 0x03f4-0x03f7] >[ 0.229832] pci 0000:00:14.1: reg 0x18: [io 0x0000-0x0007] >[ 0.229845] pci 0000:00:14.1: reg 0x1c: [io 0x0000-0x0003] >[ 0.229858] pci 0000:00:14.1: reg 0x20: [io 0x8420-0x842f] >[ 0.230015] pci 0000:00:14.2: [1002:4383] type 00 class 0x040300 >[ 0.230043] pci 0000:00:14.2: reg 0x10: [mem 0xf8700000-0xf8703fff 64bit] >[ 0.230126] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold >[ 0.230193] pci 0000:00:14.2: System wakeup disabled by ACPI >[ 0.230267] pci 0000:00:14.3: [1002:438d] type 00 class 0x060100 >[ 0.230468] pci 0000:00:14.4: [1002:4384] type 01 class 0x060401 >[ 0.230572] pci 0000:00:14.4: System wakeup disabled by ACPI >[ 0.230655] pci 0000:00:18.0: [1022:1100] type 00 class 0x060000 >[ 0.230788] pci 0000:00:18.1: [1022:1101] type 00 class 0x060000 >[ 0.230914] pci 0000:00:18.2: [1022:1102] type 00 class 0x060000 >[ 0.231043] pci 0000:00:18.3: [1022:1103] type 00 class 0x060000 >[ 0.231260] pci 0000:01:05.0: [1002:791f] type 00 class 0x030000 >[ 0.231275] pci 0000:01:05.0: reg 0x10: [mem 0xf0000000-0xf7ffffff 64bit pref] >[ 0.231284] pci 0000:01:05.0: reg 0x18: [mem 0xf8100000-0xf810ffff 64bit] >[ 0.231292] pci 0000:01:05.0: reg 0x20: [io 0x9000-0x90ff] >[ 0.231299] pci 0000:01:05.0: reg 0x24: [mem 0xf8000000-0xf80fffff] >[ 0.231323] pci 0000:01:05.0: supports D1 D2 >[ 0.231407] pci 0000:00:01.0: PCI bridge to [bus 01] >[ 0.231413] pci 0000:00:01.0: bridge window [io 0x9000-0x9fff] >[ 0.231418] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf81fffff] >[ 0.231423] pci 0000:00:01.0: bridge window [mem 0xf0000000-0xf7ffffff 64bit pref] >[ 0.231496] pci 0000:00:05.0: PCI bridge to [bus 08-0d] >[ 0.231502] pci 0000:00:05.0: bridge window [io 0x0000-0x0fff] >[ 0.231506] pci 0000:00:05.0: bridge window [mem 0x00000000-0x000fffff] >[ 0.231589] pci 0000:0e:00.0: [10ec:8136] type 00 class 0x020000 >[ 0.231607] pci 0000:0e:00.0: reg 0x10: [io 0xa000-0xa0ff] >[ 0.231637] pci 0000:0e:00.0: reg 0x18: [mem 0xf8300000-0xf8300fff 64bit] >[ 0.231670] pci 0000:0e:00.0: reg 0x30: [mem 0x00000000-0x0001ffff pref] >[ 0.231761] pci 0000:0e:00.0: supports D1 D2 >[ 0.231764] pci 0000:0e:00.0: PME# supported from D1 D2 D3hot D3cold >[ 0.231850] pci 0000:0e:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' >[ 0.231863] pci 0000:00:06.0: PCI bridge to [bus 0e] >[ 0.231869] pci 0000:00:06.0: bridge window [io 0xa000-0xafff] >[ 0.231873] pci 0000:00:06.0: bridge window [mem 0xf8300000-0xf83fffff] >[ 0.231951] pci 0000:14:00.0: [168c:001c] type 00 class 0x020000 >[ 0.231973] pci 0000:14:00.0: reg 0x10: [mem 0xf8200000-0xf820ffff 64bit] >[ 0.232156] pci 0000:14:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' >[ 0.232165] pci 0000:00:07.0: PCI bridge to [bus 14] >[ 0.232172] pci 0000:00:07.0: bridge window [mem 0xf8200000-0xf82fffff] >[ 0.232269] pci 0000:1a:04.0: [104c:8039] type 02 class 0x060700 >[ 0.232297] pci 0000:1a:04.0: reg 0x10: [mem 0xf8404000-0xf8404fff] >[ 0.232342] pci 0000:1a:04.0: supports D1 D2 >[ 0.232345] pci 0000:1a:04.0: PME# supported from D0 D1 D2 D3hot D3cold >[ 0.232444] pci 0000:1a:04.1: [104c:803a] type 00 class 0x0c0010 >[ 0.232472] pci 0000:1a:04.1: reg 0x10: [mem 0xf8406000-0xf84067ff] >[ 0.232489] pci 0000:1a:04.1: reg 0x14: [mem 0xf8400000-0xf8403fff] >[ 0.232597] pci 0000:1a:04.1: supports D1 D2 >[ 0.232600] pci 0000:1a:04.1: PME# supported from D0 D1 D2 D3hot >[ 0.232696] pci 0000:1a:04.2: [104c:803b] type 00 class 0x018000 >[ 0.232722] pci 0000:1a:04.2: reg 0x10: [mem 0xf8405000-0xf8405fff] >[ 0.232836] pci 0000:1a:04.2: supports D1 D2 >[ 0.232839] pci 0000:1a:04.2: PME# supported from D0 D1 D2 D3hot >[ 0.232933] pci 0000:1a:04.3: [104c:803c] type 00 class 0x080501 >[ 0.232960] pci 0000:1a:04.3: reg 0x10: [mem 0xf8406800-0xf84068ff] >[ 0.233082] pci 0000:1a:04.3: supports D1 D2 >[ 0.233085] pci 0000:1a:04.3: PME# supported from D0 D1 D2 D3hot >[ 0.233225] pci 0000:00:14.4: PCI bridge to [bus 1a-1b] (subtractive decode) >[ 0.233235] pci 0000:00:14.4: bridge window [mem 0xf8400000-0xf84fffff] >[ 0.233241] pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode) >[ 0.233245] pci 0000:00:14.4: bridge window [mem 0x000d0000-0x000d1fff] (subtractive decode) >[ 0.233249] pci 0000:00:14.4: bridge window [mem 0x000d2000-0x000d3fff] (subtractive decode) >[ 0.233253] pci 0000:00:14.4: bridge window [mem 0x000d4000-0x000d5fff] (subtractive decode) >[ 0.233256] pci 0000:00:14.4: bridge window [mem 0x000d6000-0x000d7fff] (subtractive decode) >[ 0.233260] pci 0000:00:14.4: bridge window [mem 0x000d8000-0x000d9fff] (subtractive decode) >[ 0.233264] pci 0000:00:14.4: bridge window [mem 0x000da000-0x000dbfff] (subtractive decode) >[ 0.233267] pci 0000:00:14.4: bridge window [mem 0x000dc000-0x000ddfff] (subtractive decode) >[ 0.233271] pci 0000:00:14.4: bridge window [mem 0x000de000-0x000dffff] (subtractive decode) >[ 0.233275] pci 0000:00:14.4: bridge window [mem 0xf0000000-0xffffffff] (subtractive decode) >[ 0.233278] pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7] (subtractive decode) >[ 0.233282] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff] (subtractive decode) >[ 0.233360] pci_bus 0000:1b: busn_res: can not insert [bus 1b-ff] under [bus 1a-1b] (conflicts with (null) [bus 1a-1b]) >[ 0.233367] pci_bus 0000:1b: busn_res: [bus 1b-ff] end is updated to 1e >[ 0.233371] pci_bus 0000:1b: busn_res: can not insert [bus 1b-1e] under [bus 1a-1b] (conflicts with (null) [bus 1a-1b]) >[ 0.233378] pci_bus 0000:1b: [bus 1b-1e] partially hidden behind transparent bridge 0000:1a [bus 1a-1b] >[ 0.233875] ACPI: PCI Interrupt Link [LNKA] (IRQs 10 11) *0, disabled. >[ 0.233964] ACPI: PCI Interrupt Link [LNKB] (IRQs 10 11) *0, disabled. >[ 0.234056] ACPI: PCI Interrupt Link [LNKC] (IRQs 10 11) *0, disabled. >[ 0.234143] ACPI: PCI Interrupt Link [LNKD] (IRQs 10 11) *0, disabled. >[ 0.234229] ACPI: PCI Interrupt Link [LNKE] (IRQs 10 11) *0, disabled. >[ 0.234317] ACPI: PCI Interrupt Link [LNKF] (IRQs 10 11) *0, disabled. >[ 0.234403] ACPI: PCI Interrupt Link [LNKG] (IRQs 10 11) *0, disabled. >[ 0.234490] ACPI: PCI Interrupt Link [LNKH] (IRQs 10 11) *0, disabled. >[ 0.257130] ACPI: Enabled 3 GPEs in block 00 to 1F >[ 0.257212] ACPI : EC: GPE = 0x13, I/O: command/status = 0x66, data = 0x62 >[ 0.258045] vgaarb: device added: PCI:0000:01:05.0,decodes=io+mem,owns=io+mem,locks=none >[ 0.258049] vgaarb: loaded >[ 0.258051] vgaarb: bridge control possible 0000:01:05.0 >[ 0.258193] SCSI subsystem initialized >[ 0.258225] libata version 3.00 loaded. >[ 0.258225] ACPI: bus type USB registered >[ 0.258225] usbcore: registered new interface driver usbfs >[ 0.258225] usbcore: registered new interface driver hub >[ 0.258225] usbcore: registered new device driver usb >[ 0.258225] PCI: Using ACPI for IRQ routing >[ 0.259652] PCI: pci_cache_line_size set to 64 bytes >[ 0.259755] e820: reserve RAM buffer [mem 0x0009dc00-0x0009ffff] >[ 0.259759] e820: reserve RAM buffer [mem 0xd7e70000-0xd7ffffff] >[ 0.259943] NetLabel: Initializing >[ 0.259945] NetLabel: domain hash size = 128 >[ 0.259947] NetLabel: protocols = UNLABELED CIPSOv4 >[ 0.259968] NetLabel: unlabeled traffic allowed by default >[ 0.260064] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0 >[ 0.260070] hpet0: 4 comparators, 32-bit 14.318180 MHz counter >[ 0.262055] Switched to clocksource hpet >[ 0.277303] pnp: PnP ACPI init >[ 0.277336] ACPI: bus type PNP registered >[ 0.277673] system 00:00: [mem 0xfec00000-0xfec00fff] could not be reserved >[ 0.277678] system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved >[ 0.277685] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) >[ 0.278293] pnp 00:01: [dma 4] >[ 0.278344] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) >[ 0.278419] pnp 00:02: Plug and Play ACPI device, IDs PNP0c04 (active) >[ 0.278483] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active) >[ 0.278546] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active) >[ 0.278618] pnp 00:05: Plug and Play ACPI device, IDs PNP0303 (active) >[ 0.278683] pnp 00:06: Plug and Play ACPI device, IDs SYN0705 SYN0700 SYN0002 PNP0f13 (active) >[ 0.278817] system 00:07: [io 0x1080] has been reserved >[ 0.278822] system 00:07: [io 0x0220-0x022f] has been reserved >[ 0.278826] system 00:07: [io 0x040b] has been reserved >[ 0.278830] system 00:07: [io 0x04d0-0x04d1] has been reserved >[ 0.278835] system 00:07: [io 0x04d6] has been reserved >[ 0.278838] system 00:07: [io 0x0530-0x0537] has been reserved >[ 0.278842] system 00:07: [io 0x0c00-0x0c01] has been reserved >[ 0.278846] system 00:07: [io 0x0c14] has been reserved >[ 0.278850] system 00:07: [io 0x0c50-0x0c52] has been reserved >[ 0.278854] system 00:07: [io 0x0c6c] has been reserved >[ 0.278858] system 00:07: [io 0x0c6f] has been reserved >[ 0.278862] system 00:07: [io 0x0cd0-0x0cd1] has been reserved >[ 0.278866] system 00:07: [io 0x0cd2-0x0cd3] has been reserved >[ 0.278870] system 00:07: [io 0x0cd4-0x0cd5] has been reserved >[ 0.278874] system 00:07: [io 0x0cd6-0x0cd7] has been reserved >[ 0.278878] system 00:07: [io 0x0cd8-0x0cdf] has been reserved >[ 0.278882] system 00:07: [io 0x8000-0x805f] could not be reserved >[ 0.278887] system 00:07: [io 0x8100-0x81ff window] has been reserved >[ 0.278891] system 00:07: [io 0x8200-0x82ff window] has been reserved >[ 0.278896] system 00:07: [io 0x0f40-0x0f47] has been reserved >[ 0.278900] system 00:07: [io 0x087f] has been reserved >[ 0.278905] system 00:07: [io 0xfd60-0xfddf] has been reserved >[ 0.278910] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) >[ 0.279068] system 00:08: [mem 0x000e0000-0x000fffff] could not be reserved >[ 0.279073] system 00:08: [mem 0xfff00000-0xffffffff] has been reserved >[ 0.279078] system 00:08: Plug and Play ACPI device, IDs PNP0c01 (active) >[ 0.279288] pnp 00:09: Plug and Play ACPI device, IDs PNP0103 (active) >[ 0.302114] pnp: PnP ACPI: found 10 devices >[ 0.302118] ACPI: bus type PNP unregistered >[ 0.311655] pci 0000:00:05.0: bridge window [io 0x1000-0x0fff] to [bus 08-0d] add_size 1000 >[ 0.311663] pci 0000:00:05.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 08-0d] add_size 200000 >[ 0.311667] pci 0000:00:05.0: bridge window [mem 0x00100000-0x000fffff] to [bus 08-0d] add_size 200000 >[ 0.311698] pci 0000:1a:04.0: res[13]=[io 0x0100-0x00ff] get_res_add_size add_size 100 >[ 0.311702] pci 0000:1a:04.0: res[14]=[io 0x0100-0x00ff] get_res_add_size add_size 100 >[ 0.311708] pci 0000:00:14.4: bridge window [io 0x1000-0x0fff] to [bus 1a-1b] add_size 1000 >[ 0.311713] pci 0000:1a:04.0: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000 >[ 0.311718] pci 0000:00:14.4: bridge window [mem 0x04000000-0x03ffffff pref] to [bus 1a-1b] add_size 4000000 >[ 0.311736] pci 0000:00:14.4: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000 >[ 0.311740] pci 0000:00:05.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000 >[ 0.311745] pci 0000:00:05.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000 >[ 0.311749] pci 0000:00:05.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000 >[ 0.311754] pci 0000:00:14.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000 >[ 0.311767] pci 0000:00:14.4: BAR 15: can't assign mem pref (size 0x4000000) >[ 0.311776] pci 0000:00:05.0: BAR 14: assigned [mem 0xf8500000-0xf86fffff] >[ 0.311788] pci 0000:00:05.0: BAR 15: assigned [mem 0xf8800000-0xf89fffff 64bit pref] >[ 0.311796] pci 0000:00:06.0: BAR 15: assigned [mem 0xf8a00000-0xf8afffff pref] >[ 0.311804] pci 0000:00:05.0: BAR 13: assigned [io 0x2000-0x2fff] >[ 0.311810] pci 0000:00:14.4: BAR 13: assigned [io 0x3000-0x3fff] >[ 0.311820] pci 0000:00:06.0: BAR 15: assigned [mem 0xf8500000-0xf85fffff pref] >[ 0.311828] pci 0000:00:14.4: BAR 15: can't assign mem pref (size 0x4000000) >[ 0.311836] pci 0000:00:05.0: BAR 14: assigned [mem 0xf8800000-0xf89fffff] >[ 0.311848] pci 0000:00:05.0: BAR 15: assigned [mem 0xf8a00000-0xf8bfffff 64bit pref] >[ 0.311853] pci 0000:00:01.0: PCI bridge to [bus 01] >[ 0.311858] pci 0000:00:01.0: bridge window [io 0x9000-0x9fff] >[ 0.311863] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf81fffff] >[ 0.311868] pci 0000:00:01.0: bridge window [mem 0xf0000000-0xf7ffffff 64bit pref] >[ 0.311873] pci 0000:00:05.0: PCI bridge to [bus 08-0d] >[ 0.311878] pci 0000:00:05.0: bridge window [io 0x2000-0x2fff] >[ 0.311883] pci 0000:00:05.0: bridge window [mem 0xf8800000-0xf89fffff] >[ 0.311887] pci 0000:00:05.0: bridge window [mem 0xf8a00000-0xf8bfffff 64bit pref] >[ 0.311895] pci 0000:0e:00.0: BAR 6: assigned [mem 0xf8500000-0xf851ffff pref] >[ 0.311899] pci 0000:00:06.0: PCI bridge to [bus 0e] >[ 0.311903] pci 0000:00:06.0: bridge window [io 0xa000-0xafff] >[ 0.311908] pci 0000:00:06.0: bridge window [mem 0xf8300000-0xf83fffff] >[ 0.311913] pci 0000:00:06.0: bridge window [mem 0xf8500000-0xf85fffff pref] >[ 0.311918] pci 0000:00:07.0: PCI bridge to [bus 14] >[ 0.311923] pci 0000:00:07.0: bridge window [mem 0xf8200000-0xf82fffff] >[ 0.311933] pci 0000:1a:04.0: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000 >[ 0.311937] pci 0000:1a:04.0: res[16]=[mem 0x04000000-0x03ffffff] get_res_add_size add_size 4000000 >[ 0.311941] pci 0000:1a:04.0: res[13]=[io 0x0100-0x00ff] get_res_add_size add_size 100 >[ 0.311945] pci 0000:1a:04.0: res[14]=[io 0x0100-0x00ff] get_res_add_size add_size 100 >[ 0.311959] pci 0000:1a:04.0: BAR 15: can't assign mem pref (size 0x4000000) >[ 0.311972] pci 0000:1a:04.0: BAR 16: can't assign mem (size 0x4000000) >[ 0.311976] pci 0000:1a:04.0: BAR 13: assigned [io 0x3000-0x30ff] >[ 0.311981] pci 0000:1a:04.0: BAR 14: assigned [io 0x3400-0x34ff] >[ 0.311993] pci 0000:1a:04.0: BAR 16: can't assign mem (size 0x4000000) >[ 0.312018] pci 0000:1a:04.0: BAR 15: can't assign mem pref (size 0x4000000) >[ 0.312022] pci 0000:1a:04.0: CardBus bridge to [bus 1b-1e] >[ 0.312026] pci 0000:1a:04.0: bridge window [io 0x3000-0x30ff] >[ 0.312033] pci 0000:1a:04.0: bridge window [io 0x3400-0x34ff] >[ 0.312040] pci 0000:00:14.4: PCI bridge to [bus 1a-1b] >[ 0.312045] pci 0000:00:14.4: bridge window [io 0x3000-0x3fff] >[ 0.312053] pci 0000:00:14.4: bridge window [mem 0xf8400000-0xf84fffff] >[ 0.312066] pci_bus 0000:00: resource 4 [mem 0x000a0000-0x000bffff] >[ 0.312069] pci_bus 0000:00: resource 5 [mem 0x000d0000-0x000d1fff] >[ 0.312073] pci_bus 0000:00: resource 6 [mem 0x000d2000-0x000d3fff] >[ 0.312077] pci_bus 0000:00: resource 7 [mem 0x000d4000-0x000d5fff] >[ 0.312081] pci_bus 0000:00: resource 8 [mem 0x000d6000-0x000d7fff] >[ 0.312084] pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000d9fff] >[ 0.312088] pci_bus 0000:00: resource 10 [mem 0x000da000-0x000dbfff] >[ 0.312092] pci_bus 0000:00: resource 11 [mem 0x000dc000-0x000ddfff] >[ 0.312096] pci_bus 0000:00: resource 12 [mem 0x000de000-0x000dffff] >[ 0.312100] pci_bus 0000:00: resource 13 [mem 0xf0000000-0xffffffff] >[ 0.312104] pci_bus 0000:00: resource 14 [io 0x0000-0x0cf7] >[ 0.312107] pci_bus 0000:00: resource 15 [io 0x0d00-0xffff] >[ 0.312111] pci_bus 0000:01: resource 0 [io 0x9000-0x9fff] >[ 0.312115] pci_bus 0000:01: resource 1 [mem 0xf8000000-0xf81fffff] >[ 0.312119] pci_bus 0000:01: resource 2 [mem 0xf0000000-0xf7ffffff 64bit pref] >[ 0.312123] pci_bus 0000:08: resource 0 [io 0x2000-0x2fff] >[ 0.312127] pci_bus 0000:08: resource 1 [mem 0xf8800000-0xf89fffff] >[ 0.312131] pci_bus 0000:08: resource 2 [mem 0xf8a00000-0xf8bfffff 64bit pref] >[ 0.312135] pci_bus 0000:0e: resource 0 [io 0xa000-0xafff] >[ 0.312139] pci_bus 0000:0e: resource 1 [mem 0xf8300000-0xf83fffff] >[ 0.312142] pci_bus 0000:0e: resource 2 [mem 0xf8500000-0xf85fffff pref] >[ 0.312147] pci_bus 0000:14: resource 1 [mem 0xf8200000-0xf82fffff] >[ 0.312151] pci_bus 0000:1a: resource 0 [io 0x3000-0x3fff] >[ 0.312154] pci_bus 0000:1a: resource 1 [mem 0xf8400000-0xf84fffff] >[ 0.312158] pci_bus 0000:1a: resource 4 [mem 0x000a0000-0x000bffff] >[ 0.312162] pci_bus 0000:1a: resource 5 [mem 0x000d0000-0x000d1fff] >[ 0.312165] pci_bus 0000:1a: resource 6 [mem 0x000d2000-0x000d3fff] >[ 0.312169] pci_bus 0000:1a: resource 7 [mem 0x000d4000-0x000d5fff] >[ 0.312173] pci_bus 0000:1a: resource 8 [mem 0x000d6000-0x000d7fff] >[ 0.312177] pci_bus 0000:1a: resource 9 [mem 0x000d8000-0x000d9fff] >[ 0.312181] pci_bus 0000:1a: resource 10 [mem 0x000da000-0x000dbfff] >[ 0.312184] pci_bus 0000:1a: resource 11 [mem 0x000dc000-0x000ddfff] >[ 0.312188] pci_bus 0000:1a: resource 12 [mem 0x000de000-0x000dffff] >[ 0.312192] pci_bus 0000:1a: resource 13 [mem 0xf0000000-0xffffffff] >[ 0.312196] pci_bus 0000:1a: resource 14 [io 0x0000-0x0cf7] >[ 0.312200] pci_bus 0000:1a: resource 15 [io 0x0d00-0xffff] >[ 0.312204] pci_bus 0000:1b: resource 0 [io 0x3000-0x30ff] >[ 0.312207] pci_bus 0000:1b: resource 1 [io 0x3400-0x34ff] >[ 0.312276] NET: Registered protocol family 2 >[ 0.312587] TCP established hash table entries: 32768 (order: 6, 262144 bytes) >[ 0.312845] TCP bind hash table entries: 32768 (order: 7, 524288 bytes) >[ 0.313174] TCP: Hash tables configured (established 32768 bind 32768) >[ 0.313254] TCP: reno registered >[ 0.313281] UDP hash table entries: 2048 (order: 4, 65536 bytes) >[ 0.313330] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes) >[ 0.313504] NET: Registered protocol family 1 >[ 0.314882] pci 0000:01:05.0: Boot video device >[ 0.314910] PCI: CLS 32 bytes, default 64 >[ 0.315040] Unpacking initramfs... >[ 0.886509] Freeing initrd memory: 18840K (ffff880035b24000 - ffff880036d8a000) >[ 0.886518] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) >[ 0.886522] software IO TLB [mem 0xd3e70000-0xd7e70000] (64MB) mapped at [ffff8800d3e70000-ffff8800d7e6ffff] >[ 0.887727] futex hash table entries: 512 (order: 3, 32768 bytes) >[ 0.887752] Initialise system trusted keyring >[ 0.887832] audit: initializing netlink subsys (disabled) >[ 0.887865] audit: type=2000 audit(1402674980.886:1): initialized >[ 0.926825] HugeTLB registered 2 MB page size, pre-allocated 0 pages >[ 0.929868] zbud: loaded >[ 0.930188] VFS: Disk quotas dquot_6.5.2 >[ 0.930285] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >[ 0.931144] msgmni has been set to 7645 >[ 0.931259] Key type big_key registered >[ 0.931262] SELinux: Registering netfilter hooks >[ 0.932820] alg: No test for stdrng (krng) >[ 0.932836] NET: Registered protocol family 38 >[ 0.932842] Key type asymmetric registered >[ 0.932844] Asymmetric key parser 'x509' registered >[ 0.932943] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) >[ 0.933030] io scheduler noop registered >[ 0.933033] io scheduler deadline registered >[ 0.933104] io scheduler cfq registered (default) >[ 0.933307] pcieport 0000:00:05.0: enabling device (0000 -> 0003) >[ 0.933349] pcieport 0000:00:05.0: irq 40 for MSI/MSI-X >[ 0.933490] pcieport 0000:00:06.0: irq 41 for MSI/MSI-X >[ 0.933596] pcieport 0000:00:07.0: irq 42 for MSI/MSI-X >[ 0.933741] pcieport 0000:00:05.0: Signaling PME through PCIe PME interrupt >[ 0.933746] pcie_pme 0000:00:05.0:pcie01: service driver pcie_pme loaded >[ 0.933769] pcieport 0000:00:06.0: Signaling PME through PCIe PME interrupt >[ 0.933772] pci 0000:0e:00.0: Signaling PME through PCIe PME interrupt >[ 0.933777] pcie_pme 0000:00:06.0:pcie01: service driver pcie_pme loaded >[ 0.933798] pcieport 0000:00:07.0: Signaling PME through PCIe PME interrupt >[ 0.933802] pci 0000:14:00.0: Signaling PME through PCIe PME interrupt >[ 0.933806] pcie_pme 0000:00:07.0:pcie01: service driver pcie_pme loaded >[ 0.933831] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 >[ 0.933920] pciehp 0000:00:05.0:pcie04: Slot #4 AttnBtn- AttnInd- PwrInd- PwrCtrl- MRL- Interlock- NoCompl- LLActRep+ >[ 0.933962] pciehp 0000:00:05.0:pcie04: service driver pciehp loaded >[ 0.933973] pciehp: PCI Express Hot Plug Controller Driver version: 0.4 >[ 0.937651] ACPI: AC Adapter [ACAD] (on-line) >[ 0.937828] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input0 >[ 0.937863] ACPI: Lid Switch [LID] >[ 0.937942] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 >[ 0.937948] ACPI: Power Button [PWRB] >[ 0.938071] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 >[ 0.938075] ACPI: Power Button [PWRF] >[ 0.938160] ACPI: processor limited to max C-state 1 >[ 0.938339] GHES: HEST is not enabled! >[ 0.938452] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled >[ 1.081582] ACPI: Battery Slot [BAT1] (battery present) >[ 1.081863] Non-volatile memory driver v1.3 >[ 1.081868] Linux agpgart interface v0.103 >[ 1.082421] ahci 0000:00:12.0: version 3.0 >[ 1.082603] ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit >[ 1.082720] ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode >[ 1.082726] ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pmp pio slum part ccc >[ 1.084144] scsi0 : ahci >[ 1.084408] scsi1 : ahci >[ 1.084618] scsi2 : ahci >[ 1.084874] scsi3 : ahci >[ 1.084979] ata1: SATA max UDMA/133 abar m1024@0xf8709000 port 0xf8709100 irq 22 >[ 1.084983] ata2: SATA max UDMA/133 abar m1024@0xf8709000 port 0xf8709180 irq 22 >[ 1.084987] ata3: SATA max UDMA/133 abar m1024@0xf8709000 port 0xf8709200 irq 22 >[ 1.084991] ata4: SATA max UDMA/133 abar m1024@0xf8709000 port 0xf8709280 irq 22 >[ 1.085304] libphy: Fixed MDIO Bus: probed >[ 1.085481] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver >[ 1.085488] ehci-pci: EHCI PCI platform driver >[ 1.085678] ehci-pci 0000:00:13.5: EHCI Host Controller >[ 1.085773] ehci-pci 0000:00:13.5: new USB bus registered, assigned bus number 1 >[ 1.085781] ehci-pci 0000:00:13.5: applying AMD SB600/SB700 USB freeze workaround >[ 1.085799] ehci-pci 0000:00:13.5: debug port 1 >[ 1.085872] ehci-pci 0000:00:13.5: irq 19, io mem 0xf8709400 >[ 1.091039] ehci-pci 0000:00:13.5: USB 2.0 started, EHCI 1.00 >[ 1.091146] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 >[ 1.091150] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >[ 1.091154] usb usb1: Product: EHCI Host Controller >[ 1.091158] usb usb1: Manufacturer: Linux 3.14.4-200.fc20.x86_64 ehci_hcd >[ 1.091161] usb usb1: SerialNumber: 0000:00:13.5 >[ 1.091403] hub 1-0:1.0: USB hub found >[ 1.091416] hub 1-0:1.0: 10 ports detected >[ 1.091854] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver >[ 1.091861] ohci-pci: OHCI PCI platform driver >[ 1.092004] ohci-pci 0000:00:13.0: OHCI PCI host controller >[ 1.092111] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 2 >[ 1.092165] ohci-pci 0000:00:13.0: irq 16, io mem 0xf8704000 >[ 1.143145] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 >[ 1.143149] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >[ 1.143153] usb usb2: Product: OHCI PCI host controller >[ 1.143157] usb usb2: Manufacturer: Linux 3.14.4-200.fc20.x86_64 ohci_hcd >[ 1.143160] usb usb2: SerialNumber: 0000:00:13.0 >[ 1.143367] hub 2-0:1.0: USB hub found >[ 1.143385] hub 2-0:1.0: 2 ports detected >[ 1.143665] ohci-pci 0000:00:13.1: OHCI PCI host controller >[ 1.143747] ohci-pci 0000:00:13.1: new USB bus registered, assigned bus number 3 >[ 1.143786] ohci-pci 0000:00:13.1: irq 17, io mem 0xf8705000 >[ 1.194137] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 >[ 1.194141] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >[ 1.194145] usb usb3: Product: OHCI PCI host controller >[ 1.194149] usb usb3: Manufacturer: Linux 3.14.4-200.fc20.x86_64 ohci_hcd >[ 1.194153] usb usb3: SerialNumber: 0000:00:13.1 >[ 1.194359] hub 3-0:1.0: USB hub found >[ 1.194378] hub 3-0:1.0: 2 ports detected >[ 1.194655] ohci-pci 0000:00:13.2: OHCI PCI host controller >[ 1.194745] ohci-pci 0000:00:13.2: new USB bus registered, assigned bus number 4 >[ 1.194793] ohci-pci 0000:00:13.2: irq 18, io mem 0xf8706000 >[ 1.245133] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 >[ 1.245137] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >[ 1.245141] usb usb4: Product: OHCI PCI host controller >[ 1.245145] usb usb4: Manufacturer: Linux 3.14.4-200.fc20.x86_64 ohci_hcd >[ 1.245148] usb usb4: SerialNumber: 0000:00:13.2 >[ 1.245358] hub 4-0:1.0: USB hub found >[ 1.245375] hub 4-0:1.0: 2 ports detected >[ 1.245646] ohci-pci 0000:00:13.3: OHCI PCI host controller >[ 1.245729] ohci-pci 0000:00:13.3: new USB bus registered, assigned bus number 5 >[ 1.245760] ohci-pci 0000:00:13.3: irq 17, io mem 0xf8707000 >[ 1.296141] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 >[ 1.296145] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >[ 1.296149] usb usb5: Product: OHCI PCI host controller >[ 1.296153] usb usb5: Manufacturer: Linux 3.14.4-200.fc20.x86_64 ohci_hcd >[ 1.296156] usb usb5: SerialNumber: 0000:00:13.3 >[ 1.296368] hub 5-0:1.0: USB hub found >[ 1.296384] hub 5-0:1.0: 2 ports detected >[ 1.296662] ohci-pci 0000:00:13.4: OHCI PCI host controller >[ 1.296744] ohci-pci 0000:00:13.4: new USB bus registered, assigned bus number 6 >[ 1.296780] ohci-pci 0000:00:13.4: irq 18, io mem 0xf8708000 >[ 1.347130] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 >[ 1.347135] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >[ 1.347138] usb usb6: Product: OHCI PCI host controller >[ 1.347141] usb usb6: Manufacturer: Linux 3.14.4-200.fc20.x86_64 ohci_hcd >[ 1.347145] usb usb6: SerialNumber: 0000:00:13.4 >[ 1.347345] hub 6-0:1.0: USB hub found >[ 1.347362] hub 6-0:1.0: 2 ports detected >[ 1.347531] uhci_hcd: USB Universal Host Controller Interface driver >[ 1.347677] usbcore: registered new interface driver usbserial >[ 1.347691] usbcore: registered new interface driver usbserial_generic >[ 1.347708] usbserial: USB Serial support registered for generic >[ 1.347772] i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12 >[ 1.376022] serio: i8042 KBD port at 0x60,0x64 irq 1 >[ 1.376030] serio: i8042 AUX port at 0x60,0x64 irq 12 >[ 1.376228] mousedev: PS/2 mouse device common for all mice >[ 1.378734] rtc_cmos 00:03: RTC can wake from S4 >[ 1.378931] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 >[ 1.378968] rtc_cmos 00:03: alarms up to one month, 114 bytes nvram, hpet irqs >[ 1.379136] device-mapper: uevent: version 1.0.3 >[ 1.379285] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com >[ 1.379679] hidraw: raw HID events driver (C) Jiri Kosina >[ 1.379894] usbcore: registered new interface driver usbhid >[ 1.379896] usbhid: USB HID core driver >[ 1.379973] drop_monitor: Initializing network drop monitor service >[ 1.380089] ip_tables: (C) 2000-2006 Netfilter Core Team >[ 1.380138] TCP: cubic registered >[ 1.380141] Initializing XFRM netlink socket >[ 1.380378] NET: Registered protocol family 10 >[ 1.380754] mip6: Mobile IPv6 >[ 1.380758] NET: Registered protocol family 17 >[ 1.381299] Loading compiled-in X.509 certificates >[ 1.383081] Loaded X.509 cert 'Fedora kernel signing key: 738e76e610adb0ed591744b5f49616fed55a3615' >[ 1.383110] registered taskstats version 1 >[ 1.383769] Magic number: 2:458:942 >[ 1.383896] rtc_cmos 00:03: setting system clock to 2014-06-13 15:56:22 UTC (1402674982) >[ 1.383996] PM: Hibernation image not present or could not be loaded. >[ 1.389050] ata3: SATA link down (SStatus 0 SControl 300) >[ 1.394074] ata4: SATA link down (SStatus 0 SControl 300) >[ 1.394109] ata2: SATA link down (SStatus 0 SControl 300) >[ 1.404826] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 >[ 1.549039] ata1: softreset failed (device not ready) >[ 1.549085] ata1: applying PMP SRST workaround and retrying >[ 1.645058] usb 1-10: new high-speed USB device number 3 using ehci-pci >[ 1.704062] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) >[ 1.707349] ata1.00: ATA-8: Seagate ST95005620AS, TD27, max UDMA/133 >[ 1.707353] ata1.00: 976773168 sectors, multi 16: LBA48 >[ 1.707358] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd >[ 1.711819] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd >[ 1.711823] ata1.00: configured for UDMA/133 >[ 1.712072] scsi 0:0:0:0: Direct-Access ATA Seagate ST950056 TD27 PQ: 0 ANSI: 5 >[ 1.712343] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) >[ 1.712353] sd 0:0:0:0: Attached scsi generic sg0 type 0 >[ 1.712410] sd 0:0:0:0: [sda] Write Protect is off >[ 1.712415] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 >[ 1.712445] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA >[ 1.713266] sda: sda1 sda2 sda3 sda4 < sda5 > >[ 1.713964] sd 0:0:0:0: [sda] Attached SCSI disk >[ 1.716360] Freeing unused kernel memory: 1448K (ffffffff81d0f000 - ffffffff81e79000) >[ 1.716366] Write protecting the kernel read-only data: 12288k >[ 1.722404] Freeing unused kernel memory: 1000K (ffff880001706000 - ffff880001800000) >[ 1.728430] Freeing unused kernel memory: 1052K (ffff880001af9000 - ffff880001c00000) >[ 1.734307] systemd[1]: systemd 208 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ) >[ 1.734566] systemd[1]: Running in initial RAM disk. >[ 1.734691] systemd[1]: Set hostname to <localhost.localdomain>. >[ 1.735762] random: systemd urandom read with 24 bits of entropy available >[ 1.761615] usb 1-10: New USB device found, idVendor=05dc, idProduct=ea00 >[ 1.761624] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3 >[ 1.761627] usb 1-10: Product: ExpressCard >[ 1.761631] usb 1-10: Manufacturer: Lexar >[ 1.761633] usb 1-10: SerialNumber: 0A4EDA01222157200407 >[ 1.792462] systemd[1]: Expecting device dev-mapper-fedora\x2droot.device... >[ 1.792498] systemd[1]: Starting -.slice. >[ 1.792779] systemd[1]: Created slice -.slice. >[ 1.792803] systemd[1]: Starting System Slice. >[ 1.792934] systemd[1]: Created slice System Slice. >[ 1.792952] systemd[1]: Starting Slices. >[ 1.792972] systemd[1]: Reached target Slices. >[ 1.792989] systemd[1]: Starting Timers. >[ 1.793041] systemd[1]: Reached target Timers. >[ 1.793060] systemd[1]: Starting Journal Socket. >[ 1.793174] systemd[1]: Listening on Journal Socket. >[ 1.793402] systemd[1]: Starting dracut cmdline hook... >[ 1.794182] systemd[1]: Starting Journal Service... >[ 1.800993] systemd[1]: Started Journal Service. >[ 1.999068] usb 5-1: new full-speed USB device number 2 using ohci-pci >[ 2.165096] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001 >[ 2.165104] usb 5-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 >[ 2.165108] usb 5-1: Product: CSR8510 A10 >[ 2.174198] systemd-udevd[233]: starting version 208 >[ 2.316378] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded >[ 2.316695] r8169 0000:0e:00.0: irq 43 for MSI/MSI-X >[ 2.316965] r8169 0000:0e:00.0 eth0: RTL8101e at 0xffffc9000000a000, 00:1b:38:1e:3a:4a, XID 14000000 IRQ 43 >[ 2.319612] [drm] Initialized drm 1.1.0 20060810 >[ 2.347672] usb-storage 1-10:1.0: USB Mass Storage device detected >[ 2.357347] scsi4 : pata_atiixp >[ 2.361107] yenta_cardbus 0000:1a:04.0: CardBus bridge found [1179:ff00] >[ 2.361151] yenta_cardbus 0000:1a:04.0: CardBus bridge to [bus 1b-1e] >[ 2.361156] yenta_cardbus 0000:1a:04.0: bridge window [io 0x3000-0x30ff] >[ 2.361164] yenta_cardbus 0000:1a:04.0: bridge window [io 0x3400-0x34ff] >[ 2.361171] yenta_cardbus 0000:1a:04.0: bridge window [mem 0xf8c00000-0xf8ffffff] >[ 2.361178] yenta_cardbus 0000:1a:04.0: bridge window [mem 0xf9000000-0xf93fffff] >[ 2.361187] yenta_cardbus 0000:1a:04.0: Enabling burst memory read transactions >[ 2.361194] yenta_cardbus 0000:1a:04.0: Using CSCINT to route CSC interrupts to PCI >[ 2.361197] yenta_cardbus 0000:1a:04.0: Routing CardBus interrupts to PCI >[ 2.361205] yenta_cardbus 0000:1a:04.0: TI: mfunc 0x10a01b22, devctl 0x64 >[ 2.365048] scsi6 : pata_atiixp >[ 2.365168] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x8420 irq 14 >[ 2.365172] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x8428 irq 15 >[ 2.382212] scsi5 : usb-storage 1-10:1.0 >[ 2.382384] usbcore: registered new interface driver usb-storage >[ 2.396168] [drm] radeon kernel modesetting enabled. >[ 2.397601] [drm] initializing kernel modesetting (RS690 0x1002:0x791F 0x1179:0xFF00). >[ 2.397627] [drm] register mmio base: 0xF8100000 >[ 2.397629] [drm] register mmio size: 65536 >[ 2.398287] ATOM BIOS: ATI >[ 2.399314] radeon 0000:01:05.0: VRAM: 128M 0x00000000D8000000 - 0x00000000DFFFFFFF (128M used) >[ 2.399320] radeon 0000:01:05.0: GTT: 512M 0x00000000A0000000 - 0x00000000BFFFFFFF >[ 2.399356] [drm] Detected VRAM RAM=128M, BAR=128M >[ 2.399358] [drm] RAM width 128bits DDR >[ 2.400214] [TTM] Zone kernel: Available graphics memory: 1959018 kiB >[ 2.400218] [TTM] Initializing pool allocator >[ 2.400227] [TTM] Initializing DMA pool allocator >[ 2.400261] [drm] radeon: 128M of VRAM memory ready >[ 2.400264] [drm] radeon: 512M of GTT memory ready. >[ 2.400300] [drm] GART: num cpu pages 131072, num gpu pages 131072 >[ 2.412547] [drm] radeon: 1 quad pipes, 1 z pipes initialized. >[ 2.422714] [drm] PCIE GART of 512M enabled (table at 0x0000000036780000). >[ 2.427283] radeon 0000:01:05.0: WB enabled >[ 2.427293] radeon 0000:01:05.0: fence driver on ring 0 use gpu addr 0x00000000a0000000 and cpu addr 0xffff880036666000 >[ 2.427297] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). >[ 2.427299] [drm] Driver supports precise vblank timestamp query. >[ 2.427334] radeon 0000:01:05.0: irq 44 for MSI/MSI-X >[ 2.427351] radeon 0000:01:05.0: radeon: using MSI. >[ 2.427381] [drm] radeon: irq initialized. >[ 2.427400] [drm] Loading RS690/RS740 Microcode >[ 2.429371] [drm] radeon: ring at 0x00000000A0001000 >[ 2.429398] [drm] ring test succeeded in 1 usecs >[ 2.430446] [drm] ib test succeeded in 0 usecs >[ 2.439173] systemd-udevd[244]: renamed network interface eth0 to p6p1 >[ 2.452038] [drm] radeon atom DIG backlight initialized >[ 2.452047] [drm] Radeon Display Connectors >[ 2.452049] [drm] Connector 0: >[ 2.452053] [drm] VGA-1 >[ 2.452056] [drm] DDC: 0x7e50 0x7e40 0x7e54 0x7e44 0x7e58 0x7e48 0x7e5c 0x7e4c >[ 2.452058] [drm] Encoders: >[ 2.452060] [drm] CRT1: INTERNAL_KLDSCP_DAC1 >[ 2.452062] [drm] Connector 1: >[ 2.452064] [drm] LVDS-1 >[ 2.452066] [drm] DDC: 0x7e40 0x7e50 0x7e44 0x7e54 0x7e48 0x7e58 0x7e4c 0x7e5c >[ 2.452068] [drm] Encoders: >[ 2.452070] [drm] LCD1: INTERNAL_LVTM1 >[ 2.452071] [drm] Connector 2: >[ 2.452073] [drm] SVIDEO-1 >[ 2.452075] [drm] Encoders: >[ 2.452076] [drm] TV1: INTERNAL_KLDSCP_DAC1 >[ 2.528547] ata5.00: ATAPI: MATSHITADVD-RAM UJ-850S, 1.21, max UDMA/33 >[ 2.534496] ata5.00: configured for UDMA/33 >[ 2.538188] scsi 4:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-850S 1.21 PQ: 0 ANSI: 5 >[ 2.549876] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray >[ 2.549882] cdrom: Uniform CD-ROM driver Revision: 3.20 >[ 2.550152] sr 4:0:0:0: Attached scsi CD-ROM sr0 >[ 2.550388] sr 4:0:0:0: Attached scsi generic sg1 type 5 >[ 2.674115] yenta_cardbus 0000:1a:04.0: ISA IRQ mask 0x0cf8, PCI irq 20 >[ 2.674124] yenta_cardbus 0000:1a:04.0: Socket status: 30000006 >[ 2.674129] pci_bus 0000:1a: Raising subordinate bus# of parent bus (#1a) from #1b to #1e >[ 2.674433] yenta_cardbus 0000:1a:04.0: pcmcia: parent PCI bridge window: [io 0x3000-0x3fff] >[ 2.674438] yenta_cardbus 0000:1a:04.0: pcmcia: parent PCI bridge window: [mem 0xf8400000-0xf84fffff] >[ 2.674443] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf8400000-0xf84fffff: >[ 2.674449] excluding 0xf8400000-0xf840ffff >[ 2.684815] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff: >[ 2.684831] excluding 0xc0000-0xcffff 0xe0000-0xfffff >[ 2.684896] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: >[ 2.684916] excluding 0xa0000000-0xa0ffffff >[ 2.684966] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: >[ 2.684986] excluding 0x60000000-0x60ffffff >[ 2.730096] firewire_ohci 0000:1a:04.1: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x2 >[ 2.797327] input: ALPS PS/2 Device as /devices/platform/i8042/serio1/input/input6 >[ 2.809882] random: nonblocking pool is initialized >[ 2.829756] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input5 >[ 2.933572] [drm] fb mappable at 0xF0040000 >[ 2.933578] [drm] vram apper at 0xF0000000 >[ 2.933581] [drm] size 4096000 >[ 2.933583] [drm] fb depth is 24 >[ 2.933585] [drm] pitch is 5120 >[ 2.933727] fbcon: radeondrmfb (fb0) is primary device >[ 3.231208] firewire_core 0000:1a:04.1: created device fw0: GUID 00023f77c041919e, S400 >[ 3.277269] Console: switching to colour frame buffer device 160x50 >[ 3.287444] radeon 0000:01:05.0: fb0: radeondrmfb frame buffer device >[ 3.287446] radeon 0000:01:05.0: registered panic notifier >[ 3.287468] [drm] Initialized radeon 2.37.0 20080528 for 0000:01:05.0 on minor 0 >[ 3.386241] scsi 5:0:0:0: Direct-Access Lexar ExpressCard 1100 PQ: 0 ANSI: 0 CCS >[ 3.386740] sd 5:0:0:0: Attached scsi generic sg2 type 0 >[ 3.388111] sd 5:0:0:0: [sdb] 15663104 512-byte logical blocks: (8.01 GB/7.46 GiB) >[ 3.389083] sd 5:0:0:0: [sdb] Write Protect is off >[ 3.389088] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 >[ 3.389975] sd 5:0:0:0: [sdb] No Caching mode page found >[ 3.390119] sd 5:0:0:0: [sdb] Assuming drive cache: write through >[ 3.394113] sd 5:0:0:0: [sdb] No Caching mode page found >[ 3.394210] sd 5:0:0:0: [sdb] Assuming drive cache: write through >[ 3.394866] sdb: sdb1 >[ 3.414362] sd 5:0:0:0: [sdb] No Caching mode page found >[ 3.414469] sd 5:0:0:0: [sdb] Assuming drive cache: write through >[ 3.414569] sd 5:0:0:0: [sdb] Attached SCSI removable disk >[ 3.503266] bio: create slab <bio-1> at 1 >[ 3.953888] PM: Starting manual resume from disk >[ 3.953901] PM: Hibernation image partition 253:0 present >[ 3.953904] PM: Looking for hibernation image. >[ 3.954237] PM: Image not found (code -22) >[ 3.954240] PM: Hibernation image not present or could not be loaded. >[ 4.004433] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) >[ 4.417394] systemd-journald[88]: Received SIGTERM >[ 5.030063] audit: type=1404 audit(1402674986.145:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 >[ 5.161516] SELinux: 2048 avtab hash slots, 100073 rules. >[ 5.187441] SELinux: 2048 avtab hash slots, 100073 rules. >[ 5.264037] SELinux: 8 users, 86 roles, 4808 types, 281 bools, 1 sens, 1024 cats >[ 5.264044] SELinux: 83 classes, 100073 rules >[ 5.273050] SELinux: Completing initialization. >[ 5.273056] SELinux: Setting up existing superblocks. >[ 5.273072] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts >[ 5.273092] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts >[ 5.273102] SELinux: initialized (dev proc, type proc), uses genfs_contexts >[ 5.273178] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >[ 5.273230] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs >[ 5.274649] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts >[ 5.276512] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs >[ 5.276518] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs >[ 5.276529] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts >[ 5.276534] SELinux: initialized (dev aio, type aio), not configured for labeling >[ 5.276541] SELinux: initialized (dev devpts, type devpts), uses transition SIDs >[ 5.276575] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs >[ 5.276586] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs >[ 5.276599] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts >[ 5.276625] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts >[ 5.277346] SELinux: initialized (dev securityfs, type securityfs), uses genfs_contexts >[ 5.277351] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >[ 5.277369] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >[ 5.277538] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >[ 5.277601] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277613] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts >[ 5.277617] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277626] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277635] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277648] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277655] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277661] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277667] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277680] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277686] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts >[ 5.277695] SELinux: initialized (dev configfs, type configfs), uses genfs_contexts >[ 5.277707] SELinux: initialized (dev dm-1, type ext4), uses xattr >[ 5.296844] audit: type=1403 audit(1402674986.411:3): policy loaded auid=4294967295 ses=4294967295 >[ 5.305535] systemd[1]: Successfully loaded SELinux policy in 285.239ms. >[ 5.418826] systemd[1]: RTC configured in localtime, applying delta of -300 minutes to system time. >[ 5.515862] systemd[1]: Relabelled /dev and /run in 85.485ms. >[ 7.498677] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts >[ 8.089981] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs >[ 8.091453] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses transition SIDs >[ 9.003884] RPC: Registered named UNIX socket transport module. >[ 9.003891] RPC: Registered udp transport module. >[ 9.003893] RPC: Registered tcp transport module. >[ 9.003895] RPC: Registered tcp NFSv4.1 backchannel transport module. >[ 9.004396] SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts >[ 9.328115] systemd-udevd[502]: starting version 208 >[ 9.398867] EXT4-fs (dm-1): re-mounted. Opts: (null) >[ 9.398993] SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts >[ 10.217804] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 >[ 10.258368] wmi: Mapper loaded >[ 10.348521] Bluetooth: Core ver 2.18 >[ 10.348672] NET: Registered protocol family 31 >[ 10.348674] Bluetooth: HCI device and connection manager initialized >[ 10.348685] Bluetooth: HCI socket layer initialized >[ 10.348689] Bluetooth: L2CAP socket layer initialized >[ 10.348706] Bluetooth: SCO socket layer initialized >[ 10.349745] ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no) >[ 10.349832] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness >[ 10.352285] acpi device:2a: registered as cooling_device2 >[ 10.352412] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:28/LNXVIDEO:01/input/input7 >[ 10.545810] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). >[ 10.546508] SELinux: initialized (dev nfsd, type nfsd), uses genfs_contexts >[ 10.721346] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff: >[ 10.721362] excluding 0xc0000-0xcffff 0xe0000-0xfffff >[ 10.721451] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: >[ 10.721471] excluding 0xa0000000-0xa0ffffff >[ 10.721545] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: >[ 10.721565] excluding 0x60000000-0x60ffffff >[ 10.953104] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x8410, revision 0 >[ 10.953170] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0x8050 >[ 10.955735] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05 >[ 10.955823] sp5100_tco: PCI Revision ID: 0x14 >[ 10.955850] sp5100_tco: failed to find MMIO address, giving up. >[ 10.990781] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19 >[ 10.990904] input: Toshiba input device as /devices/virtual/input/input8 >[ 11.006033] tifm_core: MMC/SD card detected in socket 0:1 >[ 11.156131] usbcore: registered new interface driver btusb >[ 11.201341] sdhci: Secure Digital Host Controller Interface driver >[ 11.201349] sdhci: Copyright(c) Pierre Ossman >[ 11.205143] sdhci-pci 0000:1a:04.3: SDHCI controller found [104c:803c] (rev 0) >[ 11.205417] mmc0: SDHCI controller on PCI [0000:1a:04.3] using DMA >[ 11.323113] microcode: AMD CPU family 0xf not supported >[ 11.342746] ALSA sound/pci/hda/hda_intel.c:3390 0000:00:14.2: Using LPIB position fix >[ 11.349194] ALSA sound/pci/hda/hda_intel.c:1799 0000:00:14.2: Enable sync_write for stable communication >[ 11.416657] ALSA sound/pci/hda/hda_auto_parser.c:393 autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker >[ 11.416666] ALSA sound/pci/hda/hda_auto_parser.c:397 speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) >[ 11.416671] ALSA sound/pci/hda/hda_auto_parser.c:401 hp_outs=1 (0x15/0x0/0x0/0x0/0x0) >[ 11.416674] ALSA sound/pci/hda/hda_auto_parser.c:402 mono: mono_out=0x0 >[ 11.416677] ALSA sound/pci/hda/hda_auto_parser.c:406 inputs: >[ 11.416680] ALSA sound/pci/hda/hda_auto_parser.c:410 Mic=0x18 >[ 11.416684] ALSA sound/pci/hda/patch_realtek.c:504 realtek: No valid SSID, checking pincfg 0x4016852d for NID 0x1d >[ 11.416687] ALSA sound/pci/hda/patch_realtek.c:520 realtek: Enabling init ASM_ID=0x852d CODEC_ID=10ec0268 >[ 11.431319] input: HDA ATI SB Front Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input10 >[ 11.431505] input: HDA ATI SB Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input9 >[ 11.459461] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141 >[ 11.533274] cfg80211: Calling CRDA to update world regulatory domain >[ 11.579450] ath5k 0000:14:00.0: registered as 'phy0' >[ 11.765651] MCE: In-kernel MCE decoding enabled. >[ 11.770323] EDAC MC: Ver: 3.0.0 >[ 11.773739] AMD64 EDAC driver v3.4.0 >[ 11.773802] EDAC amd64: DRAM ECC disabled. >[ 11.773810] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. > Either enable ECC checking or force module loading by setting 'ecc_enable_override'. > (Note that use of the override may cause unknown side effects.) >[ 11.799945] mmc1: new SDHC card at address 1234 >[ 11.805030] kvm: Nested Virtualization enabled >[ 11.808649] powernow-k8: fid 0x8 (1600 MHz), vid 0x12 >[ 11.808656] powernow-k8: fid 0x0 (800 MHz), vid 0x1e >[ 11.808739] powernow-k8: Found 1 AMD Turion(tm) 64 X2 Mobile Technology TL-52 (2 cpu cores) (version 2.20.00) >[ 11.812415] mmcblk0: mmc1:1234 SA16G 14.4 GiB >[ 11.821356] mmcblk0: p1 p2 < p5 p6 p7 > p3 >[ 12.118111] ath: EEPROM regdomain: 0x64 >[ 12.118125] ath: EEPROM indicates we should expect a direct regpair map >[ 12.118135] ath: Country alpha2 being used: 00 >[ 12.118140] ath: Regpair used: 0x64 >[ 12.136276] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' >[ 12.137167] ath5k: phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) >[ 12.161187] systemd-udevd[519]: renamed network interface wlan0 to wlp20s0 >[ 12.238608] cfg80211: World regulatory domain updated: >[ 12.238617] cfg80211: DFS Master region: unset >[ 12.238619] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >[ 12.238623] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm) >[ 12.238625] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) >[ 12.238628] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm) >[ 12.238630] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm) >[ 12.238633] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm) >[ 12.238636] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm) >[ 12.623733] Adding 2047996k swap on /dev/mapper/fedora-swap. Priority:-1 extents:1 across:2047996k FS >[ 14.305386] fuse init (API version 7.22) >[ 14.329681] SELinux: initialized (dev fusectl, type fusectl), uses genfs_contexts >[ 15.577170] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) >[ 15.864157] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) >[ 15.864174] SELinux: initialized (dev dm-3, type ext4), uses xattr >[ 15.865670] SELinux: initialized (dev sda3, type ext4), uses xattr >[ 15.945889] systemd-journald[469]: Received request to flush runtime journal from PID 1 >[ 16.163068] audit: type=1305 audit(1402692997.278:4): audit_pid=663 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1 >[ 17.398107] systemd[1]: Unit rngd.service entered failed state. >[ 17.431045] systemd[1]: Unit mcelog.service entered failed state. >[ 28.849690] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) >[ 29.274298] ip6_tables: (C) 2000-2006 Netfilter Core Team >[ 29.389299] Ebtables v2.0 registered >[ 29.412384] Bridge firewalling registered >[ 33.588544] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 >[ 33.588551] Bluetooth: BNEP filters: protocol multicast >[ 33.588568] Bluetooth: BNEP socket layer initialized >[ 34.385949] r8169 0000:0e:00.0 p6p1: link down >[ 34.387298] IPv6: ADDRCONF(NETDEV_UP): p6p1: link is not ready >[ 34.403569] IPv6: ADDRCONF(NETDEV_UP): wlp20s0: link is not ready >[ 36.104212] wlp20s0: authenticate with e8:3e:fc:92:f8:d0 >[ 36.107658] wlp20s0: send auth to e8:3e:fc:92:f8:d0 (try 1/3) >[ 36.109933] wlp20s0: authenticated >[ 36.111052] wlp20s0: associate with e8:3e:fc:92:f8:d0 (try 1/3) >[ 36.112635] wlp20s0: RX AssocResp from e8:3e:fc:92:f8:d0 (capab=0x411 status=0 aid=3) >[ 36.112747] wlp20s0: associated >[ 36.112805] IPv6: ADDRCONF(NETDEV_CHANGE): wlp20s0: link becomes ready >[ 36.112892] cfg80211: Calling CRDA for country: US >[ 36.123328] ath: EEPROM regdomain: 0x8348 >[ 36.123336] ath: EEPROM indicates we should expect a country code >[ 36.123339] ath: doing EEPROM country->regdmn map search >[ 36.123341] ath: country maps to regdmn code: 0x3a >[ 36.123343] ath: Country alpha2 being used: US >[ 36.123345] ath: Regpair used: 0x3a >[ 36.123348] ath: regdomain 0x8348 dynamically updated by country IE >[ 36.123350] cfg80211: Regulatory domain changed to country: US >[ 36.123352] cfg80211: DFS Master region: unset >[ 36.123354] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >[ 36.123357] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm) >[ 36.123360] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm) >[ 36.123362] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm) >[ 36.123365] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm) >[ 36.123367] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm) >[ 53.109665] Bluetooth: RFCOMM TTY layer initialized >[ 53.109709] Bluetooth: RFCOMM socket layer initialized >[ 53.109949] Bluetooth: RFCOMM ver 1.11 >[ 136.148922] tifm0 : demand removing card from socket 0:1 >[ 136.148986] mmc1: card 1234 removed >[ 141.193448] tifm_core: MMC/SD card detected in socket 0:1 >[ 142.450411] mmc1: error -110 whilst initialising SD card >[ 142.502300] mmc1: new SDHC card at address 1234 >[ 142.505561] mmcblk0: mmc1:1234 SA16G 14.4 GiB >[ 142.516600] mmcblk0: p1 p2 < p5 p6 p7 > p3 >[ 153.684218] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) >[ 153.684235] SELinux: initialized (dev mmcblk0p3, type ext4), uses xattr >[ 191.449901] FAT-fs (mmcblk0p5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. >[ 191.450301] SELinux: initialized (dev mmcblk0p5, type vfat), uses genfs_contexts >[ 779.569860] EXT4-fs (mmcblk0p6): #blocks per group too big: 134250496 >[ 1104.842478] tifm0 : demand removing card from socket 0:1 >[ 1104.842602] mmc1: card 1234 removed >[ 1108.124796] JBD2: Error -5 detected when updating journal superblock for mmcblk0p3-8. >[ 1141.593074] tifm_core: MMC/SD card detected in socket 0:1 >[ 1181.656065] ISO 9660 Extensions: Microsoft Joliet Level 3 >[ 1183.634776] ISO 9660 Extensions: RRIP_1991A >[ 1183.635062] SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts >[ 1192.555418] tifm0 : demand removing card from socket 0:1 >[ 1196.641088] tifm_core: MMC/SD card detected in socket 0:1 >[ 1197.845077] mmc1: error -110 whilst initialising SD card >[ 1197.892595] mmc1: new SDHC card at address 1234 >[ 1197.896597] mmcblk0: mmc1:1234 SA16G 14.4 GiB >[ 1197.905828] mmcblk0: p1 p2 < p5 p6 p7 > p3 >[ 1209.201663] EXT4-fs (mmcblk0p6): warning: mounting unchecked fs, running e2fsck is recommended >[ 1209.213616] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null) >[ 1209.213633] SELinux: initialized (dev mmcblk0p6, type ext4), uses xattr >[ 1216.016028] tifm_sd0:1 : card failed to respond for a long period of time (19, 1) >[ 1216.016120] tifm0 : demand removing card from socket 0:1 >[ 1216.016182] mmc1: card 1234 removed >[ 1216.016283] mmcblk0: error -123 sending status command, retrying >[ 1216.016287] mmcblk0: error -123 sending status command, retrying >[ 1216.016290] mmcblk0: error -123 sending status command, aborting >[ 1216.016296] end_request: I/O error, dev mmcblk0, sector 15826208 >[ 1216.016328] end_request: I/O error, dev mmcblk0, sector 15826216 >[ 1216.016336] end_request: I/O error, dev mmcblk0, sector 15826224 >[ 1216.016344] end_request: I/O error, dev mmcblk0, sector 15826232 >[ 1216.016352] end_request: I/O error, dev mmcblk0, sector 15826240 >[ 1216.016360] end_request: I/O error, dev mmcblk0, sector 15826248 >[ 1216.016368] end_request: I/O error, dev mmcblk0, sector 15826256 >[ 1216.016375] end_request: I/O error, dev mmcblk0, sector 15826264 >[ 1216.016383] end_request: I/O error, dev mmcblk0, sector 15826272 >[ 1216.016390] end_request: I/O error, dev mmcblk0, sector 15826280 >[ 1216.016757] mmcblk0: error -123 sending status command, retrying >[ 1216.016761] mmcblk0: error -123 sending status command, retrying >[ 1216.016764] mmcblk0: error -123 sending status command, aborting >[ 1216.017110] Aborting journal on device mmcblk0p6-8. >[ 1216.017196] mmcblk0: error -123 sending status command, retrying >[ 1216.017199] mmcblk0: error -123 sending status command, retrying >[ 1216.017203] mmcblk0: error -123 sending status command, aborting >[ 1216.017208] Buffer I/O error on device mmcblk0p6, logical block 1606435 >[ 1216.017210] lost page write due to I/O error on mmcblk0p6 >[ 1216.017227] JBD2: Error -5 detected when updating journal superblock for mmcblk0p6-8. >[ 1216.017547] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 136303, block 0) >[ 1216.017575] EXT4-fs error (device mmcblk0p6): ext4_journal_check_start:56: Detected aborted journal >[ 1216.017582] EXT4-fs (mmcblk0p6): Remounting filesystem read-only >[ 1216.017585] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.018001] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 136160, block 0) >[ 1216.018226] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 136036, block 0) >[ 1216.018471] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 136330, block 0) >[ 1216.018668] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 136353, block 0) >[ 1216.018906] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 136337, block 0) >[ 1216.019602] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 135579, block 0) >[ 1216.019817] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 6674, block 0) >[ 1216.019998] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 261019, block 0) >[ 1216.020225] EXT4-fs warning (device mmcblk0p6): __ext4_read_dirblock:908: error reading directory block (ino 15049, block 0) >[ 1216.023520] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #6944: block 1268: comm nepomukfilewatc: unable to read itable block >[ 1216.023529] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.024424] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #659294: block 2621957: comm nepomukfilewatc: unable to read itable block >[ 1216.024431] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.024812] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #6651: block 1250: comm nepomukfilewatc: unable to read itable block >[ 1216.024816] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.025319] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #15425: block 1799: comm nepomukfilewatc: unable to read itable block >[ 1216.025323] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.025972] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #15972: block 1833: comm nepomukfilewatc: unable to read itable block >[ 1216.025978] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.028819] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #136936: block 524734: comm nepomukfilewatc: unable to read itable block >[ 1216.028828] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.029619] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #15434: block 1799: comm nepomukfilewatc: unable to read itable block >[ 1216.029625] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.030153] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3919: inode #657651: block 2621855: comm nepomukfilewatc: unable to read itable block >[ 1216.030158] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected >[ 1216.030304] EXT4-fs error (device mmcblk0p6): ext4_find_entry:1309: inode #655441: comm nepomukfilewatc: reading directory lblock 0 >[ 1216.030438] EXT4-fs error (device mmcblk0p6): ext4_find_entry:1309: inode #655441: comm nepomukfilewatc: reading directory lblock 0 >[ 1216.080974] tifm_core: MMC/SD card detected in socket 0:1 >[ 1216.142147] EXT4-fs error (device mmcblk0p6): ext4_put_super:791: Couldn't clean up the journal >[ 1216.364855] mmc1: new SDHC card at address 1234 >[ 1216.366061] mmcblk0: mmc1:1234 SA16G 14.4 GiB >[ 1216.372788] mmcblk0: p1 p2 < p5 p6 p7 > p3 >[ 1249.207333] FAT-fs (mmcblk0p5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. >[ 1249.207353] SELinux: initialized (dev mmcblk0p5, type vfat), uses genfs_contexts >[ 2524.863119] tifm0 : demand removing card from socket 0:1 >[ 2524.863253] mmc1: card 1234 removed >[ 2528.566235] tifm_core: MMC/SD card detected in socket 0:1 >[ 2528.716300] mmc1: new SDHC card at address 0007 >[ 2528.720940] mmcblk0: mmc1:0007 SD16G 14.6 GiB >[ 2528.723642] mmcblk0: p1 >[ 2528.814060] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0xb00 >[ 2535.975966] SELinux: initialized (dev mmcblk0p1, type vfat), uses genfs_contexts >[ 2574.622522] SELinux: initialized (dev proc, type proc), uses genfs_contexts >[ 3166.982373] tifm0 : demand removing card from socket 0:1 >[ 3166.982438] mmc1: card 0007 removed >[ 3167.045219] FAT-fs (mmcblk0p1): unable to read boot sector to mark fs as dirty >[ 3171.482065] tifm_core: MMC/SD card detected in socket 0:1 >[ 3172.671044] mmc1: error -110 whilst initialising SD card >[ 3172.718425] mmc1: new SDHC card at address 1234 >[ 3172.720489] mmcblk0: mmc1:1234 SA16G 14.4 GiB >[ 3172.728515] mmcblk0: p1 p2 < p5 p6 p7 > p3 >[ 3177.778741] tifm0 : demand removing card from socket 0:1 >[ 3177.778805] mmc1: card 1234 removed >[ 3191.911044] tifm_core: MMC/SD card detected in socket 0:1 >[ 3193.100035] mmc1: error -110 whilst initialising SD card >[ 3193.147303] mmc1: new SDHC card at address 1234 >[ 3193.149726] mmcblk0: mmc1:1234 SA16G 14.4 GiB >[ 3193.157439] mmcblk0: p1 p2 < p5 p6 p7 > p3 >[ 3402.361780] perf samples too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 >[ 3830.003826] ath5k: ath5k_hw_get_isr: ISR: 0x00000080 IMR: 0x00000000 >[ 4002.344054] tifm_sd0:1 : card failed to respond for a long period of time (19, 1) >[ 4002.344448] tifm0 : demand removing card from socket 0:1 >[ 4002.344586] mmc1: card 1234 removed >[ 4002.344687] mmcblk0: error -123 sending status command, retrying >[ 4002.344694] mmcblk0: error -123 sending status command, retrying >[ 4002.344700] mmcblk0: error -123 sending status command, aborting >[ 4002.344711] blk_update_request: 145 callbacks suppressed >[ 4002.344716] end_request: I/O error, dev mmcblk0, sector 32768 >[ 4002.344727] Buffer I/O error on device mmcblk0, logical block 4096 >[ 4002.344732] lost page write due to I/O error on mmcblk0 >[ 4002.344844] end_request: I/O error, dev mmcblk0, sector 32776 >[ 4002.344850] Buffer I/O error on device mmcblk0, logical block 4097 >[ 4002.344855] lost page write due to I/O error on mmcblk0 >[ 4002.344876] end_request: I/O error, dev mmcblk0, sector 32784 >[ 4002.344882] Buffer I/O error on device mmcblk0, logical block 4098 >[ 4002.344887] lost page write due to I/O error on mmcblk0 >[ 4002.344907] end_request: I/O error, dev mmcblk0, sector 32792 >[ 4002.344912] Buffer I/O error on device mmcblk0, logical block 4099 >[ 4002.344917] lost page write due to I/O error on mmcblk0 >[ 4002.344937] end_request: I/O error, dev mmcblk0, sector 32800 >[ 4002.344943] Buffer I/O error on device mmcblk0, logical block 4100 >[ 4002.344947] lost page write due to I/O error on mmcblk0 >[ 4002.344967] end_request: I/O error, dev mmcblk0, sector 32808 >[ 4002.344973] Buffer I/O error on device mmcblk0, logical block 4101 >[ 4002.344977] lost page write due to I/O error on mmcblk0 >[ 4002.344997] end_request: I/O error, dev mmcblk0, sector 32816 >[ 4002.345044] Buffer I/O error on device mmcblk0, logical block 4102 >[ 4002.345049] lost page write due to I/O error on mmcblk0 >[ 4002.345068] end_request: I/O error, dev mmcblk0, sector 32824 >[ 4002.345074] Buffer I/O error on device mmcblk0, logical block 4103 >[ 4002.345079] lost page write due to I/O error on mmcblk0 >[ 4002.345097] end_request: I/O error, dev mmcblk0, sector 32832 >[ 4002.345103] Buffer I/O error on device mmcblk0, logical block 4104 >[ 4002.345107] lost page write due to I/O error on mmcblk0 >[ 4002.345125] end_request: I/O error, dev mmcblk0, sector 32840 >[ 4002.345131] Buffer I/O error on device mmcblk0, logical block 4105 >[ 4002.345135] lost page write due to I/O error on mmcblk0 >[ 4002.346273] mmcblk0: error -123 sending status command, retrying >[ 4002.346280] mmcblk0: error -123 sending status command, retrying >[ 4002.346286] mmcblk0: error -123 sending status command, aborting >[ 4002.347418] mmcblk0: error -123 sending status command, retrying >[ 4002.347425] mmcblk0: error -123 sending status command, retrying >[ 4002.347431] mmcblk0: error -123 sending status command, aborting >[ 4002.348582] mmcblk0: error -123 sending status command, retrying >[ 4002.348590] mmcblk0: error -123 sending status command, retrying >[ 4002.348596] mmcblk0: error -123 sending status command, aborting >[ 4002.349801] mmcblk0: error -123 sending status command, retrying >[ 4002.349809] mmcblk0: error -123 sending status command, retrying >[ 4002.349815] mmcblk0: error -123 sending status command, aborting >[ 4002.351192] mmcblk0: error -123 sending status command, retrying >[ 4002.351200] mmcblk0: error -123 sending status command, retrying >[ 4002.351206] mmcblk0: error -123 sending status command, aborting >[ 4002.352333] mmcblk0: error -123 sending status command, retrying >[ 4002.352340] mmcblk0: error -123 sending status command, retrying >[ 4002.352346] mmcblk0: error -123 sending status command, aborting >[ 4002.353676] mmcblk0: error -123 sending status command, retrying >[ 4002.353683] mmcblk0: error -123 sending status command, retrying >[ 4002.353689] mmcblk0: error -123 sending status command, aborting >[ 4002.355070] mmcblk0: error -123 sending status command, retrying >[ 4002.355077] mmcblk0: error -123 sending status command, retrying >[ 4002.355083] mmcblk0: error -123 sending status command, aborting >[ 4002.356305] mmcblk0: error -123 sending status command, retrying >[ 4002.356312] mmcblk0: error -123 sending status command, retrying >[ 4002.356318] mmcblk0: error -123 sending status command, aborting >[ 4002.357483] mmcblk0: error -123 sending status command, retrying >[ 4002.357491] mmcblk0: error -123 sending status command, retrying >[ 4002.357497] mmcblk0: error -123 sending status command, aborting >[ 4002.358646] mmcblk0: error -123 sending status command, retrying >[ 4002.358653] mmcblk0: error -123 sending status command, retrying >[ 4002.358659] mmcblk0: error -123 sending status command, aborting >[ 4002.359977] mmcblk0: error -123 sending status command, retrying >[ 4002.359985] mmcblk0: error -123 sending status command, retrying >[ 4002.359991] mmcblk0: error -123 sending status command, aborting >[ 4002.361289] mmcblk0: error -123 sending status command, retrying >[ 4002.361296] mmcblk0: error -123 sending status command, retrying >[ 4002.361302] mmcblk0: error -123 sending status command, aborting >[ 4002.362494] mmcblk0: error -123 sending status command, retrying >[ 4002.362501] mmcblk0: error -123 sending status command, retrying >[ 4002.362508] mmcblk0: error -123 sending status command, aborting >[ 4002.363765] mmcblk0: error -123 sending status command, retrying >[ 4002.363772] mmcblk0: error -123 sending status command, retrying >[ 4002.363778] mmcblk0: error -123 sending status command, aborting >[ 4002.365066] mmcblk0: error -123 sending status command, retrying >[ 4002.365073] mmcblk0: error -123 sending status command, retrying >[ 4002.365079] mmcblk0: error -123 sending status command, aborting >[ 4002.366379] mmcblk0: error -123 sending status command, retrying >[ 4002.366386] mmcblk0: error -123 sending status command, retrying >[ 4002.366392] mmcblk0: error -123 sending status command, aborting >[ 4002.367598] mmcblk0: error -123 sending status command, retrying >[ 4002.367605] mmcblk0: error -123 sending status command, retrying >[ 4002.367611] mmcblk0: error -123 sending status command, aborting >[ 4002.368939] mmcblk0: error -123 sending status command, retrying >[ 4002.368947] mmcblk0: error -123 sending status command, retrying >[ 4002.368953] mmcblk0: error -123 sending status command, aborting >[ 4002.370149] mmcblk0: error -123 sending status command, retrying >[ 4002.370155] mmcblk0: error -123 sending status command, retrying >[ 4002.370161] mmcblk0: error -123 sending status command, aborting >[ 4002.371482] mmcblk0: error -123 sending status command, retrying >[ 4002.371489] mmcblk0: error -123 sending status command, retrying >[ 4002.371495] mmcblk0: error -123 sending status command, aborting >[ 4002.372659] mmcblk0: error -123 sending status command, retrying >[ 4002.372666] mmcblk0: error -123 sending status command, retrying >[ 4002.372672] mmcblk0: error -123 sending status command, aborting >[ 4002.374028] mmcblk0: error -123 sending status command, retrying >[ 4002.374035] mmcblk0: error -123 sending status command, retrying >[ 4002.374041] mmcblk0: error -123 sending status command, aborting >[ 4002.375320] mmcblk0: error -123 sending status command, retrying >[ 4002.375326] mmcblk0: error -123 sending status command, retrying >[ 4002.375333] mmcblk0: error -123 sending status command, aborting >[ 4002.376648] mmcblk0: error -123 sending status command, retrying >[ 4002.376655] mmcblk0: error -123 sending status command, retrying >[ 4002.376661] mmcblk0: error -123 sending status command, aborting >[ 4002.377994] mmcblk0: error -123 sending status command, retrying >[ 4002.378002] mmcblk0: error -123 sending status command, retrying >[ 4002.378022] mmcblk0: error -123 sending status command, aborting >[ 4002.379281] mmcblk0: error -123 sending status command, retrying >[ 4002.379288] mmcblk0: error -123 sending status command, retrying >[ 4002.379295] mmcblk0: error -123 sending status command, aborting >[ 4002.380591] mmcblk0: error -123 sending status command, retrying >[ 4002.380598] mmcblk0: error -123 sending status command, retrying >[ 4002.380605] mmcblk0: error -123 sending status command, aborting >[ 4002.381913] mmcblk0: error -123 sending status command, retrying >[ 4002.381920] mmcblk0: error -123 sending status command, retrying >[ 4002.381926] mmcblk0: error -123 sending status command, aborting >[ 4002.383187] mmcblk0: error -123 sending status command, retrying >[ 4002.383194] mmcblk0: error -123 sending status command, retrying >[ 4002.383200] mmcblk0: error -123 sending status command, aborting >[ 4002.384493] mmcblk0: error -123 sending status command, retrying >[ 4002.384499] mmcblk0: error -123 sending status command, retrying >[ 4002.384505] mmcblk0: error -123 sending status command, aborting >[ 4002.385827] mmcblk0: error -123 sending status command, retrying >[ 4002.385834] mmcblk0: error -123 sending status command, retrying >[ 4002.385840] mmcblk0: error -123 sending status command, aborting >[ 4002.387185] mmcblk0: error -123 sending status command, retrying >[ 4002.387193] mmcblk0: error -123 sending status command, retrying >[ 4002.387199] mmcblk0: error -123 sending status command, aborting >[ 4002.388543] mmcblk0: error -123 sending status command, retrying >[ 4002.388550] mmcblk0: error -123 sending status command, retrying >[ 4002.388556] mmcblk0: error -123 sending status command, aborting >[ 4002.389872] mmcblk0: error -123 sending status command, retrying >[ 4002.389879] mmcblk0: error -123 sending status command, retrying >[ 4002.389885] mmcblk0: error -123 sending status command, aborting >[ 4002.391211] mmcblk0: error -123 sending status command, retrying >[ 4002.391218] mmcblk0: error -123 sending status command, retrying >[ 4002.391224] mmcblk0: error -123 sending status command, aborting >[ 4002.392553] mmcblk0: error -123 sending status command, retrying >[ 4002.392560] mmcblk0: error -123 sending status command, retrying >[ 4002.392566] mmcblk0: error -123 sending status command, aborting >[ 4002.393932] mmcblk0: error -123 sending status command, retrying >[ 4002.393939] mmcblk0: error -123 sending status command, retrying >[ 4002.393945] mmcblk0: error -123 sending status command, aborting >[ 4002.395294] mmcblk0: error -123 sending status command, retrying >[ 4002.395301] mmcblk0: error -123 sending status command, retrying >[ 4002.395307] mmcblk0: error -123 sending status command, aborting >[ 4002.396572] mmcblk0: error -123 sending status command, retrying >[ 4002.396579] mmcblk0: error -123 sending status command, retrying >[ 4002.396585] mmcblk0: error -123 sending status command, aborting >[ 4002.397888] mmcblk0: error -123 sending status command, retrying >[ 4002.397895] mmcblk0: error -123 sending status command, retrying >[ 4002.397901] mmcblk0: error -123 sending status command, aborting >[ 4002.399286] mmcblk0: error -123 sending status command, retrying >[ 4002.399293] mmcblk0: error -123 sending status command, retrying >[ 4002.399299] mmcblk0: error -123 sending status command, aborting >[ 4002.400622] mmcblk0: error -123 sending status command, retrying >[ 4002.400629] mmcblk0: error -123 sending status command, retrying >[ 4002.400635] mmcblk0: error -123 sending status command, aborting >[ 4002.401988] mmcblk0: error -123 sending status command, retrying >[ 4002.401996] mmcblk0: error -123 sending status command, retrying >[ 4002.402019] mmcblk0: error -123 sending status command, aborting >[ 4002.403315] mmcblk0: error -123 sending status command, retrying >[ 4002.403322] mmcblk0: error -123 sending status command, retrying >[ 4002.403328] mmcblk0: error -123 sending status command, aborting >[ 4002.404615] mmcblk0: error -123 sending status command, retrying >[ 4002.404622] mmcblk0: error -123 sending status command, retrying >[ 4002.404629] mmcblk0: error -123 sending status command, aborting >[ 4002.405893] mmcblk0: error -123 sending status command, retrying >[ 4002.405900] mmcblk0: error -123 sending status command, retrying >[ 4002.405906] mmcblk0: error -123 sending status command, aborting >[ 4002.407221] mmcblk0: error -123 sending status command, retrying >[ 4002.407228] mmcblk0: error -123 sending status command, retrying >[ 4002.407234] mmcblk0: error -123 sending status command, aborting >[ 4002.408561] mmcblk0: error -123 sending status command, retrying >[ 4002.408568] mmcblk0: error -123 sending status command, retrying >[ 4002.408574] mmcblk0: error -123 sending status command, aborting >[ 4002.409867] mmcblk0: error -123 sending status command, retrying >[ 4002.409874] mmcblk0: error -123 sending status command, retrying >[ 4002.409880] mmcblk0: error -123 sending status command, aborting >[ 4002.411227] mmcblk0: error -123 sending status command, retrying >[ 4002.411234] mmcblk0: error -123 sending status command, retrying >[ 4002.411240] mmcblk0: error -123 sending status command, aborting >[ 4002.412602] mmcblk0: error -123 sending status command, retrying >[ 4002.412609] mmcblk0: error -123 sending status command, retrying >[ 4002.412615] mmcblk0: error -123 sending status command, aborting >[ 4002.413874] mmcblk0: error -123 sending status command, retrying >[ 4002.413882] mmcblk0: error -123 sending status command, retrying >[ 4002.413888] mmcblk0: error -123 sending status command, aborting >[ 4002.415230] mmcblk0: error -123 sending status command, retrying >[ 4002.415237] mmcblk0: error -123 sending status command, retrying >[ 4002.415243] mmcblk0: error -123 sending status command, aborting >[ 4002.416505] mmcblk0: error -123 sending status command, retrying >[ 4002.416512] mmcblk0: error -123 sending status command, retrying >[ 4002.416518] mmcblk0: error -123 sending status command, aborting >[ 4002.417788] mmcblk0: error -123 sending status command, retrying >[ 4002.417795] mmcblk0: error -123 sending status command, retrying >[ 4002.417801] mmcblk0: error -123 sending status command, aborting >[ 4002.419051] mmcblk0: error -123 sending status command, retrying >[ 4002.419059] mmcblk0: error -123 sending status command, retrying >[ 4002.419065] mmcblk0: error -123 sending status command, aborting >[ 4002.420303] mmcblk0: error -123 sending status command, retrying >[ 4002.420310] mmcblk0: error -123 sending status command, retrying >[ 4002.420317] mmcblk0: error -123 sending status command, aborting >[ 4002.421611] mmcblk0: error -123 sending status command, retrying >[ 4002.421618] mmcblk0: error -123 sending status command, retrying >[ 4002.421624] mmcblk0: error -123 sending status command, aborting >[ 4002.423022] mmcblk0: error -123 sending status command, retrying >[ 4002.423029] mmcblk0: error -123 sending status command, retrying >[ 4002.423036] mmcblk0: error -123 sending status command, aborting >[ 4002.424445] mmcblk0: error -123 sending status command, retrying >[ 4002.424452] mmcblk0: error -123 sending status command, retrying >[ 4002.424458] mmcblk0: error -123 sending status command, aborting >[ 4002.425860] mmcblk0: error -123 sending status command, retrying >[ 4002.425866] mmcblk0: error -123 sending status command, retrying >[ 4002.425872] mmcblk0: error -123 sending status command, aborting >[ 4002.427296] mmcblk0: error -123 sending status command, retrying >[ 4002.427303] mmcblk0: error -123 sending status command, retrying >[ 4002.427309] mmcblk0: error -123 sending status command, aborting >[ 4002.429029] mmcblk0: error -123 sending status command, retrying >[ 4002.429037] mmcblk0: error -123 sending status command, retrying >[ 4002.429042] mmcblk0: error -123 sending status command, aborting >[ 4002.430549] mmcblk0: error -123 sending status command, retrying >[ 4002.430556] mmcblk0: error -123 sending status command, retrying >[ 4002.430562] mmcblk0: error -123 sending status command, aborting >[ 4002.431979] mmcblk0: error -123 sending status command, retrying >[ 4002.431986] mmcblk0: error -123 sending status command, retrying >[ 4002.431992] mmcblk0: error -123 sending status command, aborting >[ 4002.433456] mmcblk0: error -123 sending status command, retrying >[ 4002.433463] mmcblk0: error -123 sending status command, retrying >[ 4002.433469] mmcblk0: error -123 sending status command, aborting >[ 4002.434874] mmcblk0: error -123 sending status command, retrying >[ 4002.434880] mmcblk0: error -123 sending status command, retrying >[ 4002.434886] mmcblk0: error -123 sending status command, aborting >[ 4002.436301] mmcblk0: error -123 sending status command, retrying >[ 4002.436308] mmcblk0: error -123 sending status command, retrying >[ 4002.436314] mmcblk0: error -123 sending status command, aborting >[ 4002.437750] mmcblk0: error -123 sending status command, retrying >[ 4002.437757] mmcblk0: error -123 sending status command, retrying >[ 4002.437762] mmcblk0: error -123 sending status command, aborting >[ 4002.439196] mmcblk0: error -123 sending status command, retrying >[ 4002.439203] mmcblk0: error -123 sending status command, retrying >[ 4002.439209] mmcblk0: error -123 sending status command, aborting >[ 4002.440583] mmcblk0: error -123 sending status command, retrying >[ 4002.440591] mmcblk0: error -123 sending status command, retrying >[ 4002.440597] mmcblk0: error -123 sending status command, aborting >[ 4002.442002] mmcblk0: error -123 sending status command, retrying >[ 4002.442029] mmcblk0: error -123 sending status command, retrying >[ 4002.442035] mmcblk0: error -123 sending status command, aborting >[ 4002.443472] mmcblk0: error -123 sending status command, retrying >[ 4002.443480] mmcblk0: error -123 sending status command, retrying >[ 4002.443486] mmcblk0: error -123 sending status command, aborting >[ 4002.444909] mmcblk0: error -123 sending status command, retrying >[ 4002.444916] mmcblk0: error -123 sending status command, retrying >[ 4002.444922] mmcblk0: error -123 sending status command, aborting >[ 4002.446321] mmcblk0: error -123 sending status command, retrying >[ 4002.446328] mmcblk0: error -123 sending status command, retrying >[ 4002.446334] mmcblk0: error -123 sending status command, aborting >[ 4002.447721] mmcblk0: error -123 sending status command, retrying >[ 4002.447728] mmcblk0: error -123 sending status command, retrying >[ 4002.447734] mmcblk0: error -123 sending status command, aborting >[ 4002.449194] mmcblk0: error -123 sending status command, retrying >[ 4002.449202] mmcblk0: error -123 sending status command, retrying >[ 4002.449208] mmcblk0: error -123 sending status command, aborting >[ 4002.450582] mmcblk0: error -123 sending status command, retrying >[ 4002.450589] mmcblk0: error -123 sending status command, retrying >[ 4002.450595] mmcblk0: error -123 sending status command, aborting >[ 4002.452022] mmcblk0: error -123 sending status command, retrying >[ 4002.452030] mmcblk0: error -123 sending status command, retrying >[ 4002.452036] mmcblk0: error -123 sending status command, aborting >[ 4002.453420] mmcblk0: error -123 sending status command, retrying >[ 4002.453428] mmcblk0: error -123 sending status command, retrying >[ 4002.453434] mmcblk0: error -123 sending status command, aborting >[ 4002.454862] mmcblk0: error -123 sending status command, retrying >[ 4002.454870] mmcblk0: error -123 sending status command, retrying >[ 4002.454876] mmcblk0: error -123 sending status command, aborting >[ 4002.456281] mmcblk0: error -123 sending status command, retrying >[ 4002.456289] mmcblk0: error -123 sending status command, retrying >[ 4002.456295] mmcblk0: error -123 sending status command, aborting >[ 4002.457700] mmcblk0: error -123 sending status command, retrying >[ 4002.457708] mmcblk0: error -123 sending status command, retrying >[ 4002.457715] mmcblk0: error -123 sending status command, aborting >[ 4002.459111] mmcblk0: error -123 sending status command, retrying >[ 4002.459119] mmcblk0: error -123 sending status command, retrying >[ 4002.459125] mmcblk0: error -123 sending status command, aborting >[ 4002.460260] mmcblk0: error -123 sending status command, retrying >[ 4002.460267] mmcblk0: error -123 sending status command, retrying >[ 4002.460273] mmcblk0: error -123 sending status command, aborting >[ 4002.461367] mmcblk0: error -123 sending status command, retrying >[ 4002.461374] mmcblk0: error -123 sending status command, retrying >[ 4002.461380] mmcblk0: error -123 sending status command, aborting >[ 4002.462646] mmcblk0: error -123 sending status command, retrying >[ 4002.462652] mmcblk0: error -123 sending status command, retrying >[ 4002.462657] mmcblk0: error -123 sending status command, aborting >[ 4002.463828] mmcblk0: error -123 sending status command, retrying >[ 4002.463835] mmcblk0: error -123 sending status command, retrying >[ 4002.463842] mmcblk0: error -123 sending status command, aborting >[ 4002.464978] mmcblk0: error -123 sending status command, retrying >[ 4002.464985] mmcblk0: error -123 sending status command, retrying >[ 4002.464991] mmcblk0: error -123 sending status command, aborting >[ 4002.466137] mmcblk0: error -123 sending status command, retrying >[ 4002.466143] mmcblk0: error -123 sending status command, retrying >[ 4002.466149] mmcblk0: error -123 sending status command, aborting >[ 4002.467316] mmcblk0: error -123 sending status command, retrying >[ 4002.467323] mmcblk0: error -123 sending status command, retrying >[ 4002.467329] mmcblk0: error -123 sending status command, aborting >[ 4002.468457] mmcblk0: error -123 sending status command, retrying >[ 4002.468464] mmcblk0: error -123 sending status command, retrying >[ 4002.468470] mmcblk0: error -123 sending status command, aborting >[ 4002.469655] mmcblk0: error -123 sending status command, retrying >[ 4002.469662] mmcblk0: error -123 sending status command, retrying >[ 4002.469668] mmcblk0: error -123 sending status command, aborting >[ 4002.470991] mmcblk0: error -123 sending status command, retrying >[ 4002.470998] mmcblk0: error -123 sending status command, retrying >[ 4002.471022] mmcblk0: error -123 sending status command, aborting >[ 4002.472194] mmcblk0: error -123 sending status command, retrying >[ 4002.472201] mmcblk0: error -123 sending status command, retrying >[ 4002.472207] mmcblk0: error -123 sending status command, aborting >[ 4002.473367] mmcblk0: error -123 sending status command, retrying >[ 4002.473374] mmcblk0: error -123 sending status command, retrying >[ 4002.473381] mmcblk0: error -123 sending status command, aborting >[ 4002.474478] mmcblk0: error -123 sending status command, retrying >[ 4002.474485] mmcblk0: error -123 sending status command, retrying >[ 4002.474491] mmcblk0: error -123 sending status command, aborting >[ 4002.475619] mmcblk0: error -123 sending status command, retrying >[ 4002.475626] mmcblk0: error -123 sending status command, retrying >[ 4002.475632] mmcblk0: error -123 sending status command, aborting >[ 4002.476766] mmcblk0: error -123 sending status command, retrying >[ 4002.476773] mmcblk0: error -123 sending status command, retrying >[ 4002.476779] mmcblk0: error -123 sending status command, aborting >[ 4002.477940] mmcblk0: error -123 sending status command, retrying >[ 4002.477948] mmcblk0: error -123 sending status command, retrying >[ 4002.477954] mmcblk0: error -123 sending status command, aborting >[ 4002.479101] mmcblk0: error -123 sending status command, retrying >[ 4002.479108] mmcblk0: error -123 sending status command, retrying >[ 4002.479114] mmcblk0: error -123 sending status command, aborting >[ 4002.480344] mmcblk0: error -123 sending status command, retrying >[ 4002.480351] mmcblk0: error -123 sending status command, retrying >[ 4002.480357] mmcblk0: error -123 sending status command, aborting >[ 4002.481589] mmcblk0: error -123 sending status command, retrying >[ 4002.481596] mmcblk0: error -123 sending status command, retrying >[ 4002.481602] mmcblk0: error -123 sending status command, aborting >[ 4002.482764] mmcblk0: error -123 sending status command, retrying >[ 4002.482771] mmcblk0: error -123 sending status command, retrying >[ 4002.482777] mmcblk0: error -123 sending status command, aborting >[ 4002.483880] mmcblk0: error -123 sending status command, retrying >[ 4002.483887] mmcblk0: error -123 sending status command, retrying >[ 4002.483893] mmcblk0: error -123 sending status command, aborting >[ 4002.484976] mmcblk0: error -123 sending status command, retrying >[ 4002.484983] mmcblk0: error -123 sending status command, retrying >[ 4002.484990] mmcblk0: error -123 sending status command, aborting >[ 4002.486124] mmcblk0: error -123 sending status command, retrying >[ 4002.486131] mmcblk0: error -123 sending status command, retrying >[ 4002.486137] mmcblk0: error -123 sending status command, aborting >[ 4002.487194] mmcblk0: error -123 sending status command, retrying >[ 4002.487201] mmcblk0: error -123 sending status command, retrying >[ 4002.487207] mmcblk0: error -123 sending status command, aborting >[ 4002.488310] mmcblk0: error -123 sending status command, retrying >[ 4002.488317] mmcblk0: error -123 sending status command, retrying >[ 4002.488323] mmcblk0: error -123 sending status command, aborting >[ 4002.489468] mmcblk0: error -123 sending status command, retrying >[ 4002.489475] mmcblk0: error -123 sending status command, retrying >[ 4002.489481] mmcblk0: error -123 sending status command, aborting >[ 4002.490588] mmcblk0: error -123 sending status command, retrying >[ 4002.490596] mmcblk0: error -123 sending status command, retrying >[ 4002.490602] mmcblk0: error -123 sending status command, aborting >[ 4002.491665] mmcblk0: error -123 sending status command, retrying >[ 4002.491672] mmcblk0: error -123 sending status command, retrying >[ 4002.491679] mmcblk0: error -123 sending status command, aborting >[ 4002.492827] mmcblk0: error -123 sending status command, retrying >[ 4002.492834] mmcblk0: error -123 sending status command, retrying >[ 4002.492840] mmcblk0: error -123 sending status command, aborting >[ 4002.493454] mmcblk0: error -123 sending status command, retrying >[ 4002.493458] mmcblk0: error -123 sending status command, retrying >[ 4002.493460] mmcblk0: error -123 sending status command, aborting >[ 4002.494569] mmcblk0: error -123 sending status command, retrying >[ 4002.494573] mmcblk0: error -123 sending status command, retrying >[ 4002.494576] mmcblk0: error -123 sending status command, aborting >[ 4002.495154] mmcblk0: error -123 sending status command, retrying >[ 4002.495157] mmcblk0: error -123 sending status command, retrying >[ 4002.495160] mmcblk0: error -123 sending status command, aborting >[ 4002.495738] mmcblk0: error -123 sending status command, retrying >[ 4002.495742] mmcblk0: error -123 sending status command, retrying >[ 4002.495745] mmcblk0: error -123 sending status command, aborting >[ 4002.496297] mmcblk0: error -123 sending status command, retrying >[ 4002.496300] mmcblk0: error -123 sending status command, retrying >[ 4002.496303] mmcblk0: error -123 sending status command, aborting >[ 4002.496950] mmcblk0: error -123 sending status command, retrying >[ 4002.496954] mmcblk0: error -123 sending status command, retrying >[ 4002.496957] mmcblk0: error -123 sending status command, aborting >[ 4002.497563] mmcblk0: error -123 sending status command, retrying >[ 4002.497566] mmcblk0: error -123 sending status command, retrying >[ 4002.497569] mmcblk0: error -123 sending status command, aborting >[ 4002.498118] mmcblk0: error -123 sending status command, retrying >[ 4002.498122] mmcblk0: error -123 sending status command, retrying >[ 4002.498125] mmcblk0: error -123 sending status command, aborting >[ 4002.498655] mmcblk0: error -123 sending status command, retrying >[ 4002.498658] mmcblk0: error -123 sending status command, retrying >[ 4002.498661] mmcblk0: error -123 sending status command, aborting >[ 4002.499263] mmcblk0: error -123 sending status command, retrying >[ 4002.499267] mmcblk0: error -123 sending status command, retrying >[ 4002.499270] mmcblk0: error -123 sending status command, aborting >[ 4002.499835] mmcblk0: error -123 sending status command, retrying >[ 4002.499838] mmcblk0: error -123 sending status command, retrying >[ 4002.499841] mmcblk0: error -123 sending status command, aborting >[ 4002.500434] mmcblk0: error -123 sending status command, retrying >[ 4002.500437] mmcblk0: error -123 sending status command, retrying >[ 4002.500440] mmcblk0: error -123 sending status command, aborting >[ 4002.501128] mmcblk0: error -123 sending status command, retrying >[ 4002.501132] mmcblk0: error -123 sending status command, retrying >[ 4002.501134] mmcblk0: error -123 sending status command, aborting >[ 4002.501774] mmcblk0: error -123 sending status command, retrying >[ 4002.501778] mmcblk0: error -123 sending status command, retrying >[ 4002.501781] mmcblk0: error -123 sending status command, aborting >[ 4002.502420] mmcblk0: error -123 sending status command, retrying >[ 4002.502423] mmcblk0: error -123 sending status command, retrying >[ 4002.502426] mmcblk0: error -123 sending status command, aborting >[ 4002.502990] mmcblk0: error -123 sending status command, retrying >[ 4002.502993] mmcblk0: error -123 sending status command, retrying >[ 4002.502996] mmcblk0: error -123 sending status command, aborting >[ 4002.503590] mmcblk0: error -123 sending status command, retrying >[ 4002.503594] mmcblk0: error -123 sending status command, retrying >[ 4002.503597] mmcblk0: error -123 sending status command, aborting >[ 4002.504125] mmcblk0: error -123 sending status command, retrying >[ 4002.504128] mmcblk0: error -123 sending status command, retrying >[ 4002.504131] mmcblk0: error -123 sending status command, aborting >[ 4002.504709] mmcblk0: error -123 sending status command, retrying >[ 4002.504713] mmcblk0: error -123 sending status command, retrying >[ 4002.504716] mmcblk0: error -123 sending status command, aborting >[ 4002.505276] mmcblk0: error -123 sending status command, retrying >[ 4002.505279] mmcblk0: error -123 sending status command, retrying >[ 4002.505282] mmcblk0: error -123 sending status command, aborting >[ 4002.505795] mmcblk0: error -123 sending status command, retrying >[ 4002.505799] mmcblk0: error -123 sending status command, retrying >[ 4002.505802] mmcblk0: error -123 sending status command, aborting >[ 4002.506299] mmcblk0: error -123 sending status command, retrying >[ 4002.506302] mmcblk0: error -123 sending status command, retrying >[ 4002.506305] mmcblk0: error -123 sending status command, aborting >[ 4002.506849] mmcblk0: error -123 sending status command, retrying >[ 4002.506852] mmcblk0: error -123 sending status command, retrying >[ 4002.506856] mmcblk0: error -123 sending status command, aborting >[ 4002.507416] mmcblk0: error -123 sending status command, retrying >[ 4002.507420] mmcblk0: error -123 sending status command, retrying >[ 4002.507423] mmcblk0: error -123 sending status command, aborting >[ 4002.507949] mmcblk0: error -123 sending status command, retrying >[ 4002.507952] mmcblk0: error -123 sending status command, retrying >[ 4002.507955] mmcblk0: error -123 sending status command, aborting >[ 4002.508463] mmcblk0: error -123 sending status command, retrying >[ 4002.508467] mmcblk0: error -123 sending status command, retrying >[ 4002.508469] mmcblk0: error -123 sending status command, aborting >[ 4002.508952] mmcblk0: error -123 sending status command, retrying >[ 4002.508955] mmcblk0: error -123 sending status command, retrying >[ 4002.508958] mmcblk0: error -123 sending status command, aborting >[ 4002.509470] mmcblk0: error -123 sending status command, retrying >[ 4002.509473] mmcblk0: error -123 sending status command, retrying >[ 4002.509476] mmcblk0: error -123 sending status command, aborting >[ 4002.509960] mmcblk0: error -123 sending status command, retrying >[ 4002.509963] mmcblk0: error -123 sending status command, retrying >[ 4002.509966] mmcblk0: error -123 sending status command, aborting >[ 4002.510477] mmcblk0: error -123 sending status command, retrying >[ 4002.510480] mmcblk0: error -123 sending status command, retrying >[ 4002.510483] mmcblk0: error -123 sending status command, aborting >[ 4002.510975] mmcblk0: error -123 sending status command, retrying >[ 4002.510978] mmcblk0: error -123 sending status command, retrying >[ 4002.510981] mmcblk0: error -123 sending status command, aborting >[ 4002.511505] mmcblk0: error -123 sending status command, retrying >[ 4002.511508] mmcblk0: error -123 sending status command, retrying >[ 4002.511511] mmcblk0: error -123 sending status command, aborting >[ 4002.512187] mmcblk0: error -123 sending status command, retrying >[ 4002.512191] mmcblk0: error -123 sending status command, retrying >[ 4002.512194] mmcblk0: error -123 sending status command, aborting >[ 4002.512934] mmcblk0: error -123 sending status command, retrying >[ 4002.512937] mmcblk0: error -123 sending status command, retrying >[ 4002.512940] mmcblk0: error -123 sending status command, aborting >[ 4002.513689] mmcblk0: error -123 sending status command, retrying >[ 4002.513693] mmcblk0: error -123 sending status command, retrying >[ 4002.513696] mmcblk0: error -123 sending status command, aborting >[ 4002.514407] mmcblk0: error -123 sending status command, retrying >[ 4002.514411] mmcblk0: error -123 sending status command, retrying >[ 4002.514414] mmcblk0: error -123 sending status command, aborting >[ 4002.515079] mmcblk0: error -123 sending status command, retrying >[ 4002.515082] mmcblk0: error -123 sending status command, retrying >[ 4002.515085] mmcblk0: error -123 sending status command, aborting >[ 4002.515719] mmcblk0: error -123 sending status command, retrying >[ 4002.515722] mmcblk0: error -123 sending status command, retrying >[ 4002.515725] mmcblk0: error -123 sending status command, aborting >[ 4002.516392] mmcblk0: error -123 sending status command, retrying >[ 4002.516395] mmcblk0: error -123 sending status command, retrying >[ 4002.516398] mmcblk0: error -123 sending status command, aborting >[ 4002.517066] mmcblk0: error -123 sending status command, retrying >[ 4002.517070] mmcblk0: error -123 sending status command, retrying >[ 4002.517072] mmcblk0: error -123 sending status command, aborting >[ 4002.517714] mmcblk0: error -123 sending status command, retrying >[ 4002.517718] mmcblk0: error -123 sending status command, retrying >[ 4002.517721] mmcblk0: error -123 sending status command, aborting >[ 4002.518394] mmcblk0: error -123 sending status command, retrying >[ 4002.518397] mmcblk0: error -123 sending status command, retrying >[ 4002.518400] mmcblk0: error -123 sending status command, aborting >[ 4002.519078] mmcblk0: error -123 sending status command, retrying >[ 4002.519081] mmcblk0: error -123 sending status command, retrying >[ 4002.519084] mmcblk0: error -123 sending status command, aborting >[ 4002.519681] mmcblk0: error -123 sending status command, retrying >[ 4002.519684] mmcblk0: error -123 sending status command, retrying >[ 4002.519687] mmcblk0: error -123 sending status command, aborting >[ 4002.520313] mmcblk0: error -123 sending status command, retrying >[ 4002.520317] mmcblk0: error -123 sending status command, retrying >[ 4002.520320] mmcblk0: error -123 sending status command, aborting >[ 4002.520823] mmcblk0: error -123 sending status command, retrying >[ 4002.520826] mmcblk0: error -123 sending status command, retrying >[ 4002.520829] mmcblk0: error -123 sending status command, aborting >[ 4002.521357] mmcblk0: error -123 sending status command, retrying >[ 4002.521360] mmcblk0: error -123 sending status command, retrying >[ 4002.521363] mmcblk0: error -123 sending status command, aborting >[ 4002.521959] mmcblk0: error -123 sending status command, retrying >[ 4002.521962] mmcblk0: error -123 sending status command, retrying >[ 4002.521965] mmcblk0: error -123 sending status command, aborting >[ 4002.522480] mmcblk0: error -123 sending status command, retrying >[ 4002.522483] mmcblk0: error -123 sending status command, retrying >[ 4002.522486] mmcblk0: error -123 sending status command, aborting >[ 4002.522973] mmcblk0: error -123 sending status command, retrying >[ 4002.522977] mmcblk0: error -123 sending status command, retrying >[ 4002.522980] mmcblk0: error -123 sending status command, aborting >[ 4002.523494] mmcblk0: error -123 sending status command, retrying >[ 4002.523497] mmcblk0: error -123 sending status command, retrying >[ 4002.523500] mmcblk0: error -123 sending status command, aborting >[ 4002.524128] mmcblk0: error -123 sending status command, retrying >[ 4002.524132] mmcblk0: error -123 sending status command, retrying >[ 4002.524135] mmcblk0: error -123 sending status command, aborting >[ 4002.524628] mmcblk0: error -123 sending status command, retrying >[ 4002.524631] mmcblk0: error -123 sending status command, retrying >[ 4002.524634] mmcblk0: error -123 sending status command, aborting >[ 4002.525155] mmcblk0: error -123 sending status command, retrying >[ 4002.525158] mmcblk0: error -123 sending status command, retrying >[ 4002.525161] mmcblk0: error -123 sending status command, aborting >[ 4002.525770] mmcblk0: error -123 sending status command, retrying >[ 4002.525773] mmcblk0: error -123 sending status command, retrying >[ 4002.525776] mmcblk0: error -123 sending status command, aborting >[ 4002.526331] mmcblk0: error -123 sending status command, retrying >[ 4002.526334] mmcblk0: error -123 sending status command, retrying >[ 4002.526337] mmcblk0: error -123 sending status command, aborting >[ 4002.526869] mmcblk0: error -123 sending status command, retrying >[ 4002.526872] mmcblk0: error -123 sending status command, retrying >[ 4002.526876] mmcblk0: error -123 sending status command, aborting >[ 4002.527434] mmcblk0: error -123 sending status command, retrying >[ 4002.527438] mmcblk0: error -123 sending status command, retrying >[ 4002.527441] mmcblk0: error -123 sending status command, aborting >[ 4002.528086] mmcblk0: error -123 sending status command, retrying >[ 4002.528089] mmcblk0: error -123 sending status command, retrying >[ 4002.528092] mmcblk0: error -123 sending status command, aborting >[ 4002.528629] mmcblk0: error -123 sending status command, retrying >[ 4002.528632] mmcblk0: error -123 sending status command, retrying >[ 4002.528636] mmcblk0: error -123 sending status command, aborting >[ 4002.529158] mmcblk0: error -123 sending status command, retrying >[ 4002.529161] mmcblk0: error -123 sending status command, retrying >[ 4002.529164] mmcblk0: error -123 sending status command, aborting >[ 4002.529771] mmcblk0: error -123 sending status command, retrying >[ 4002.529775] mmcblk0: error -123 sending status command, retrying >[ 4002.529778] mmcblk0: error -123 sending status command, aborting >[ 4002.530537] mmcblk0: error -123 sending status command, retrying >[ 4002.530541] mmcblk0: error -123 sending status command, retrying >[ 4002.530544] mmcblk0: error -123 sending status command, aborting >[ 4002.531095] mmcblk0: error -123 sending status command, retrying >[ 4002.531099] mmcblk0: error -123 sending status command, retrying >[ 4002.531102] mmcblk0: error -123 sending status command, aborting >[ 4002.531661] mmcblk0: error -123 sending status command, retrying >[ 4002.531664] mmcblk0: error -123 sending status command, retrying >[ 4002.531667] mmcblk0: error -123 sending status command, aborting >[ 4002.532372] mmcblk0: error -123 sending status command, retrying >[ 4002.532376] mmcblk0: error -123 sending status command, retrying >[ 4002.532379] mmcblk0: error -123 sending status command, aborting >[ 4002.532976] mmcblk0: error -123 sending status command, retrying >[ 4002.532980] mmcblk0: error -123 sending status command, retrying >[ 4002.532983] mmcblk0: error -123 sending status command, aborting >[ 4002.533539] mmcblk0: error -123 sending status command, retrying >[ 4002.533542] mmcblk0: error -123 sending status command, retrying >[ 4002.533545] mmcblk0: error -123 sending status command, aborting >[ 4002.534161] mmcblk0: error -123 sending status command, retrying >[ 4002.534165] mmcblk0: error -123 sending status command, retrying >[ 4002.534167] mmcblk0: error -123 sending status command, aborting >[ 4002.534840] mmcblk0: error -123 sending status command, retrying >[ 4002.534844] mmcblk0: error -123 sending status command, retrying >[ 4002.534847] mmcblk0: error -123 sending status command, aborting >[ 4002.535440] mmcblk0: error -123 sending status command, retrying >[ 4002.535444] mmcblk0: error -123 sending status command, retrying >[ 4002.535447] mmcblk0: error -123 sending status command, aborting >[ 4002.535988] mmcblk0: error -123 sending status command, retrying >[ 4002.535991] mmcblk0: error -123 sending status command, retrying >[ 4002.535994] mmcblk0: error -123 sending status command, aborting >[ 4002.536549] mmcblk0: error -123 sending status command, retrying >[ 4002.536552] mmcblk0: error -123 sending status command, retrying >[ 4002.536555] mmcblk0: error -123 sending status command, aborting >[ 4002.537224] mmcblk0: error -123 sending status command, retrying >[ 4002.537228] mmcblk0: error -123 sending status command, retrying >[ 4002.537231] mmcblk0: error -123 sending status command, aborting >[ 4002.537817] mmcblk0: error -123 sending status command, retrying >[ 4002.537821] mmcblk0: error -123 sending status command, retrying >[ 4002.537824] mmcblk0: error -123 sending status command, aborting >[ 4002.538456] mmcblk0: error -123 sending status command, retrying >[ 4002.538459] mmcblk0: error -123 sending status command, retrying >[ 4002.538462] mmcblk0: error -123 sending status command, aborting >[ 4002.539158] mmcblk0: error -123 sending status command, retrying >[ 4002.539162] mmcblk0: error -123 sending status command, retrying >[ 4002.539165] mmcblk0: error -123 sending status command, aborting >[ 4002.539679] mmcblk0: error -123 sending status command, retrying >[ 4002.539682] mmcblk0: error -123 sending status command, retrying >[ 4002.539685] mmcblk0: error -123 sending status command, aborting >[ 4002.540203] mmcblk0: error -123 sending status command, retrying >[ 4002.540206] mmcblk0: error -123 sending status command, retrying >[ 4002.540209] mmcblk0: error -123 sending status command, aborting >[ 4002.540739] mmcblk0: error -123 sending status command, retrying >[ 4002.540743] mmcblk0: error -123 sending status command, retrying >[ 4002.540746] mmcblk0: error -123 sending status command, aborting >[ 4002.541381] mmcblk0: error -123 sending status command, retrying >[ 4002.541385] mmcblk0: error -123 sending status command, retrying >[ 4002.541387] mmcblk0: error -123 sending status command, aborting >[ 4002.541916] mmcblk0: error -123 sending status command, retrying >[ 4002.541920] mmcblk0: error -123 sending status command, retrying >[ 4002.541923] mmcblk0: error -123 sending status command, aborting >[ 4002.542456] mmcblk0: error -123 sending status command, retrying >[ 4002.542459] mmcblk0: error -123 sending status command, retrying >[ 4002.542462] mmcblk0: error -123 sending status command, aborting >[ 4002.542970] mmcblk0: error -123 sending status command, retrying >[ 4002.542973] mmcblk0: error -123 sending status command, retrying >[ 4002.542976] mmcblk0: error -123 sending status command, aborting >[ 4002.543636] mmcblk0: error -123 sending status command, retrying >[ 4002.543640] mmcblk0: error -123 sending status command, retrying >[ 4002.543643] mmcblk0: error -123 sending status command, aborting >[ 4002.544251] mmcblk0: error -123 sending status command, retrying >[ 4002.544255] mmcblk0: error -123 sending status command, retrying >[ 4002.544258] mmcblk0: error -123 sending status command, aborting >[ 4002.544779] mmcblk0: error -123 sending status command, retrying >[ 4002.544783] mmcblk0: error -123 sending status command, retrying >[ 4002.544786] mmcblk0: error -123 sending status command, aborting >[ 4002.545379] mmcblk0: error -123 sending status command, retrying >[ 4002.545382] mmcblk0: error -123 sending status command, retrying >[ 4002.545385] mmcblk0: error -123 sending status command, aborting >[ 4002.545944] mmcblk0: error -123 sending status command, retrying >[ 4002.545948] mmcblk0: error -123 sending status command, retrying >[ 4002.545950] mmcblk0: error -123 sending status command, aborting >[ 4002.546456] mmcblk0: error -123 sending status command, retrying >[ 4002.546460] mmcblk0: error -123 sending status command, retrying >[ 4002.546463] mmcblk0: error -123 sending status command, aborting >[ 4002.546981] mmcblk0: error -123 sending status command, retrying >[ 4002.546985] mmcblk0: error -123 sending status command, retrying >[ 4002.546987] mmcblk0: error -123 sending status command, aborting >[ 4002.547576] mmcblk0: error -123 sending status command, retrying >[ 4002.547580] mmcblk0: error -123 sending status command, retrying >[ 4002.547583] mmcblk0: error -123 sending status command, aborting >[ 4002.548122] mmcblk0: error -123 sending status command, retrying >[ 4002.548126] mmcblk0: error -123 sending status command, retrying >[ 4002.548129] mmcblk0: error -123 sending status command, aborting >[ 4002.548651] mmcblk0: error -123 sending status command, retrying >[ 4002.548655] mmcblk0: error -123 sending status command, retrying >[ 4002.548658] mmcblk0: error -123 sending status command, aborting >[ 4002.549284] mmcblk0: error -123 sending status command, retrying >[ 4002.549288] mmcblk0: error -123 sending status command, retrying >[ 4002.549291] mmcblk0: error -123 sending status command, aborting >[ 4002.549817] mmcblk0: error -123 sending status command, retrying >[ 4002.549821] mmcblk0: error -123 sending status command, retrying >[ 4002.549824] mmcblk0: error -123 sending status command, aborting >[ 4002.550348] mmcblk0: error -123 sending status command, retrying >[ 4002.550351] mmcblk0: error -123 sending status command, retrying >[ 4002.550354] mmcblk0: error -123 sending status command, aborting >[ 4002.550891] mmcblk0: error -123 sending status command, retrying >[ 4002.550894] mmcblk0: error -123 sending status command, retrying >[ 4002.550897] mmcblk0: error -123 sending status command, aborting >[ 4002.551516] mmcblk0: error -123 sending status command, retrying >[ 4002.551520] mmcblk0: error -123 sending status command, retrying >[ 4002.551523] mmcblk0: error -123 sending status command, aborting >[ 4002.552045] mmcblk0: error -123 sending status command, retrying >[ 4002.552049] mmcblk0: error -123 sending status command, retrying >[ 4002.552052] mmcblk0: error -123 sending status command, aborting >[ 4002.552556] mmcblk0: error -123 sending status command, retrying >[ 4002.552559] mmcblk0: error -123 sending status command, retrying >[ 4002.552562] mmcblk0: error -123 sending status command, aborting >[ 4002.553097] mmcblk0: error -123 sending status command, retrying >[ 4002.553100] mmcblk0: error -123 sending status command, retrying >[ 4002.553103] mmcblk0: error -123 sending status command, aborting >[ 4002.553718] mmcblk0: error -123 sending status command, retrying >[ 4002.553721] mmcblk0: error -123 sending status command, retrying >[ 4002.553724] mmcblk0: error -123 sending status command, aborting >[ 4002.554252] mmcblk0: error -123 sending status command, retrying >[ 4002.554255] mmcblk0: error -123 sending status command, retrying >[ 4002.554258] mmcblk0: error -123 sending status command, aborting >[ 4002.554878] mmcblk0: error -123 sending status command, retrying >[ 4002.554881] mmcblk0: error -123 sending status command, retrying >[ 4002.554884] mmcblk0: error -123 sending status command, aborting >[ 4002.555450] mmcblk0: error -123 sending status command, retrying >[ 4002.555453] mmcblk0: error -123 sending status command, retrying >[ 4002.555456] mmcblk0: error -123 sending status command, aborting >[ 4002.555991] mmcblk0: error -123 sending status command, retrying >[ 4002.555994] mmcblk0: error -123 sending status command, retrying >[ 4002.555997] mmcblk0: error -123 sending status command, aborting >[ 4002.556594] mmcblk0: error -123 sending status command, retrying >[ 4002.556598] mmcblk0: error -123 sending status command, retrying >[ 4002.556601] mmcblk0: error -123 sending status command, aborting >[ 4002.557180] mmcblk0: error -123 sending status command, retrying >[ 4002.557184] mmcblk0: error -123 sending status command, retrying >[ 4002.557187] mmcblk0: error -123 sending status command, aborting >[ 4002.557781] mmcblk0: error -123 sending status command, retrying >[ 4002.557784] mmcblk0: error -123 sending status command, retrying >[ 4002.557788] mmcblk0: error -123 sending status command, aborting >[ 4002.558363] mmcblk0: error -123 sending status command, retrying >[ 4002.558367] mmcblk0: error -123 sending status command, retrying >[ 4002.558370] mmcblk0: error -123 sending status command, aborting >[ 4002.558920] mmcblk0: error -123 sending status command, retrying >[ 4002.558923] mmcblk0: error -123 sending status command, retrying >[ 4002.558926] mmcblk0: error -123 sending status command, aborting >[ 4002.559495] mmcblk0: error -123 sending status command, retrying >[ 4002.559498] mmcblk0: error -123 sending status command, retrying >[ 4002.559501] mmcblk0: error -123 sending status command, aborting >[ 4002.560050] mmcblk0: error -123 sending status command, retrying >[ 4002.560053] mmcblk0: error -123 sending status command, retrying >[ 4002.560056] mmcblk0: error -123 sending status command, aborting >[ 4002.560615] mmcblk0: error -123 sending status command, retrying >[ 4002.560618] mmcblk0: error -123 sending status command, retrying >[ 4002.560621] mmcblk0: error -123 sending status command, aborting >[ 4002.561195] mmcblk0: error -123 sending status command, retrying >[ 4002.561199] mmcblk0: error -123 sending status command, retrying >[ 4002.561202] mmcblk0: error -123 sending status command, aborting >[ 4002.561728] mmcblk0: error -123 sending status command, retrying >[ 4002.561731] mmcblk0: error -123 sending status command, retrying >[ 4002.561734] mmcblk0: error -123 sending status command, aborting >[ 4002.562318] mmcblk0: error -123 sending status command, retrying >[ 4002.562321] mmcblk0: error -123 sending status command, retrying >[ 4002.562324] mmcblk0: error -123 sending status command, aborting >[ 4002.562909] mmcblk0: error -123 sending status command, retrying >[ 4002.562912] mmcblk0: error -123 sending status command, retrying >[ 4002.562915] mmcblk0: error -123 sending status command, aborting >[ 4002.563495] mmcblk0: error -123 sending status command, retrying >[ 4002.563498] mmcblk0: error -123 sending status command, retrying >[ 4002.563501] mmcblk0: error -123 sending status command, aborting >[ 4002.564110] mmcblk0: error -123 sending status command, retrying >[ 4002.564114] mmcblk0: error -123 sending status command, retrying >[ 4002.564117] mmcblk0: error -123 sending status command, aborting >[ 4002.564622] mmcblk0: error -123 sending status command, retrying >[ 4002.564625] mmcblk0: error -123 sending status command, retrying >[ 4002.564628] mmcblk0: error -123 sending status command, aborting >[ 4002.565172] mmcblk0: error -123 sending status command, retrying >[ 4002.565175] mmcblk0: error -123 sending status command, retrying >[ 4002.565178] mmcblk0: error -123 sending status command, aborting >[ 4002.565689] mmcblk0: error -123 sending status command, retrying >[ 4002.565692] mmcblk0: error -123 sending status command, retrying >[ 4002.565695] mmcblk0: error -123 sending status command, aborting >[ 4002.566225] mmcblk0: error -123 sending status command, retrying >[ 4002.566228] mmcblk0: error -123 sending status command, retrying >[ 4002.566232] mmcblk0: error -123 sending status command, aborting >[ 4002.566786] mmcblk0: error -123 sending status command, retrying >[ 4002.566790] mmcblk0: error -123 sending status command, retrying >[ 4002.566793] mmcblk0: error -123 sending status command, aborting >[ 4002.567395] mmcblk0: error -123 sending status command, retrying >[ 4002.567398] mmcblk0: error -123 sending status command, retrying >[ 4002.567401] mmcblk0: error -123 sending status command, aborting >[ 4002.567941] mmcblk0: error -123 sending status command, retrying >[ 4002.567944] mmcblk0: error -123 sending status command, retrying >[ 4002.567947] mmcblk0: error -123 sending status command, aborting >[ 4002.568531] mmcblk0: error -123 sending status command, retrying >[ 4002.568534] mmcblk0: error -123 sending status command, retrying >[ 4002.568537] mmcblk0: error -123 sending status command, aborting >[ 4002.569121] mmcblk0: error -123 sending status command, retrying >[ 4002.569125] mmcblk0: error -123 sending status command, retrying >[ 4002.569128] mmcblk0: error -123 sending status command, aborting >[ 4002.569649] mmcblk0: error -123 sending status command, retrying >[ 4002.569653] mmcblk0: error -123 sending status command, retrying >[ 4002.569656] mmcblk0: error -123 sending status command, aborting >[ 4002.570198] mmcblk0: error -123 sending status command, retrying >[ 4002.570201] mmcblk0: error -123 sending status command, retrying >[ 4002.570204] mmcblk0: error -123 sending status command, aborting >[ 4002.570724] mmcblk0: error -123 sending status command, retrying >[ 4002.570728] mmcblk0: error -123 sending status command, retrying >[ 4002.570731] mmcblk0: error -123 sending status command, aborting >[ 4002.571225] mmcblk0: error -123 sending status command, retrying >[ 4002.571229] mmcblk0: error -123 sending status command, retrying >[ 4002.571232] mmcblk0: error -123 sending status command, aborting >[ 4002.571775] mmcblk0: error -123 sending status command, retrying >[ 4002.571779] mmcblk0: error -123 sending status command, retrying >[ 4002.571782] mmcblk0: error -123 sending status command, aborting >[ 4002.572309] mmcblk0: error -123 sending status command, retrying >[ 4002.572313] mmcblk0: error -123 sending status command, retrying >[ 4002.572316] mmcblk0: error -123 sending status command, aborting >[ 4002.572897] mmcblk0: error -123 sending status command, retrying >[ 4002.572901] mmcblk0: error -123 sending status command, retrying >[ 4002.572904] mmcblk0: error -123 sending status command, aborting >[ 4002.573509] mmcblk0: error -123 sending status command, retrying >[ 4002.573512] mmcblk0: error -123 sending status command, retrying >[ 4002.573515] mmcblk0: error -123 sending status command, aborting >[ 4002.574073] mmcblk0: error -123 sending status command, retrying >[ 4002.574076] mmcblk0: error -123 sending status command, retrying >[ 4002.574079] mmcblk0: error -123 sending status command, aborting >[ 4002.574636] mmcblk0: error -123 sending status command, retrying >[ 4002.574639] mmcblk0: error -123 sending status command, retrying >[ 4002.574642] mmcblk0: error -123 sending status command, aborting >[ 4002.575242] mmcblk0: error -123 sending status command, retrying >[ 4002.575245] mmcblk0: error -123 sending status command, retrying >[ 4002.575248] mmcblk0: error -123 sending status command, aborting >[ 4002.575850] mmcblk0: error -123 sending status command, retrying >[ 4002.575853] mmcblk0: error -123 sending status command, retrying >[ 4002.575856] mmcblk0: error -123 sending status command, aborting >[ 4002.576523] mmcblk0: error -123 sending status command, retrying >[ 4002.576526] mmcblk0: error -123 sending status command, retrying >[ 4002.576529] mmcblk0: error -123 sending status command, aborting >[ 4002.577121] mmcblk0: error -123 sending status command, retrying >[ 4002.577125] mmcblk0: error -123 sending status command, retrying >[ 4002.577128] mmcblk0: error -123 sending status command, aborting >[ 4002.577659] mmcblk0: error -123 sending status command, retrying >[ 4002.577662] mmcblk0: error -123 sending status command, retrying >[ 4002.577665] mmcblk0: error -123 sending status command, aborting >[ 4002.578271] mmcblk0: error -123 sending status command, retrying >[ 4002.578275] mmcblk0: error -123 sending status command, retrying >[ 4002.578278] mmcblk0: error -123 sending status command, aborting >[ 4002.578829] mmcblk0: error -123 sending status command, retrying >[ 4002.578833] mmcblk0: error -123 sending status command, retrying >[ 4002.578836] mmcblk0: error -123 sending status command, aborting >[ 4002.579416] mmcblk0: error -123 sending status command, retrying >[ 4002.579420] mmcblk0: error -123 sending status command, retrying >[ 4002.579423] mmcblk0: error -123 sending status command, aborting >[ 4002.579941] mmcblk0: error -123 sending status command, retrying >[ 4002.579944] mmcblk0: error -123 sending status command, retrying >[ 4002.579947] mmcblk0: error -123 sending status command, aborting >[ 4002.580475] mmcblk0: error -123 sending status command, retrying >[ 4002.580478] mmcblk0: error -123 sending status command, retrying >[ 4002.580481] mmcblk0: error -123 sending status command, aborting >[ 4002.581026] mmcblk0: error -123 sending status command, retrying >[ 4002.581035] mmcblk0: error -123 sending status command, retrying >[ 4002.581037] mmcblk0: error -123 sending status command, aborting >[ 4002.581585] mmcblk0: error -123 sending status command, retrying >[ 4002.581589] mmcblk0: error -123 sending status command, retrying >[ 4002.581592] mmcblk0: error -123 sending status command, aborting >[ 4002.582173] mmcblk0: error -123 sending status command, retrying >[ 4002.582177] mmcblk0: error -123 sending status command, retrying >[ 4002.582179] mmcblk0: error -123 sending status command, aborting >[ 4002.582689] mmcblk0: error -123 sending status command, retrying >[ 4002.582692] mmcblk0: error -123 sending status command, retrying >[ 4002.582695] mmcblk0: error -123 sending status command, aborting >[ 4002.583243] mmcblk0: error -123 sending status command, retrying >[ 4002.583246] mmcblk0: error -123 sending status command, retrying >[ 4002.583249] mmcblk0: error -123 sending status command, aborting >[ 4002.583745] mmcblk0: error -123 sending status command, retrying >[ 4002.583748] mmcblk0: error -123 sending status command, retrying >[ 4002.583751] mmcblk0: error -123 sending status command, aborting >[ 4002.584334] mmcblk0: error -123 sending status command, retrying >[ 4002.584338] mmcblk0: error -123 sending status command, retrying >[ 4002.584341] mmcblk0: error -123 sending status command, aborting >[ 4002.584884] mmcblk0: error -123 sending status command, retrying >[ 4002.584887] mmcblk0: error -123 sending status command, retrying >[ 4002.584890] mmcblk0: error -123 sending status command, aborting >[ 4002.585422] mmcblk0: error -123 sending status command, retrying >[ 4002.585425] mmcblk0: error -123 sending status command, retrying >[ 4002.585428] mmcblk0: error -123 sending status command, aborting >[ 4002.586002] mmcblk0: error -123 sending status command, retrying >[ 4002.586022] mmcblk0: error -123 sending status command, retrying >[ 4002.586025] mmcblk0: error -123 sending status command, aborting >[ 4002.586696] mmcblk0: error -123 sending status command, retrying >[ 4002.586699] mmcblk0: error -123 sending status command, retrying >[ 4002.586702] mmcblk0: error -123 sending status command, aborting >[ 4002.587259] mmcblk0: error -123 sending status command, retrying >[ 4002.587262] mmcblk0: error -123 sending status command, retrying >[ 4002.587265] mmcblk0: error -123 sending status command, aborting >[ 4002.587793] mmcblk0: error -123 sending status command, retrying >[ 4002.587796] mmcblk0: error -123 sending status command, retrying >[ 4002.587799] mmcblk0: error -123 sending status command, aborting >[ 4002.588398] mmcblk0: error -123 sending status command, retrying >[ 4002.588401] mmcblk0: error -123 sending status command, retrying >[ 4002.588404] mmcblk0: error -123 sending status command, aborting >[ 4002.588964] mmcblk0: error -123 sending status command, retrying >[ 4002.588968] mmcblk0: error -123 sending status command, retrying >[ 4002.588970] mmcblk0: error -123 sending status command, aborting >[ 4002.589522] mmcblk0: error -123 sending status command, retrying >[ 4002.589526] mmcblk0: error -123 sending status command, retrying >[ 4002.589529] mmcblk0: error -123 sending status command, aborting >[ 4002.590091] mmcblk0: error -123 sending status command, retrying >[ 4002.590095] mmcblk0: error -123 sending status command, retrying >[ 4002.590098] mmcblk0: error -123 sending status command, aborting >[ 4002.590742] mmcblk0: error -123 sending status command, retrying >[ 4002.590745] mmcblk0: error -123 sending status command, retrying >[ 4002.590748] mmcblk0: error -123 sending status command, aborting >[ 4002.591309] mmcblk0: error -123 sending status command, retrying >[ 4002.591313] mmcblk0: error -123 sending status command, retrying >[ 4002.591316] mmcblk0: error -123 sending status command, aborting >[ 4002.591815] mmcblk0: error -123 sending status command, retrying >[ 4002.591818] mmcblk0: error -123 sending status command, retrying >[ 4002.591821] mmcblk0: error -123 sending status command, aborting >[ 4002.592491] mmcblk0: error -123 sending status command, retrying >[ 4002.592494] mmcblk0: error -123 sending status command, retrying >[ 4002.592497] mmcblk0: error -123 sending status command, aborting >[ 4002.593074] mmcblk0: error -123 sending status command, retrying >[ 4002.593078] mmcblk0: error -123 sending status command, retrying >[ 4002.593081] mmcblk0: error -123 sending status command, aborting >[ 4002.593618] mmcblk0: error -123 sending status command, retrying >[ 4002.593621] mmcblk0: error -123 sending status command, retrying >[ 4002.593624] mmcblk0: error -123 sending status command, aborting >[ 4002.594313] mmcblk0: error -123 sending status command, retrying >[ 4002.594317] mmcblk0: error -123 sending status command, retrying >[ 4002.594320] mmcblk0: error -123 sending status command, aborting >[ 4002.594840] mmcblk0: error -123 sending status command, retrying >[ 4002.594843] mmcblk0: error -123 sending status command, retrying >[ 4002.594846] mmcblk0: error -123 sending status command, aborting >[ 4002.595439] mmcblk0: error -123 sending status command, retrying >[ 4002.595442] mmcblk0: error -123 sending status command, retrying >[ 4002.595445] mmcblk0: error -123 sending status command, aborting >[ 4002.596053] mmcblk0: error -123 sending status command, retrying >[ 4002.596056] mmcblk0: error -123 sending status command, retrying >[ 4002.596059] mmcblk0: error -123 sending status command, aborting >[ 4002.596546] mmcblk0: error -123 sending status command, retrying >[ 4002.596550] mmcblk0: error -123 sending status command, retrying >[ 4002.596553] mmcblk0: error -123 sending status command, aborting >[ 4002.597192] mmcblk0: error -123 sending status command, retrying >[ 4002.597196] mmcblk0: error -123 sending status command, retrying >[ 4002.597198] mmcblk0: error -123 sending status command, aborting >[ 4002.597702] mmcblk0: error -123 sending status command, retrying >[ 4002.597706] mmcblk0: error -123 sending status command, retrying >[ 4002.597709] mmcblk0: error -123 sending status command, aborting >[ 4002.598249] mmcblk0: error -123 sending status command, retrying >[ 4002.598252] mmcblk0: error -123 sending status command, retrying >[ 4002.598255] mmcblk0: error -123 sending status command, aborting >[ 4002.598776] mmcblk0: error -123 sending status command, retrying >[ 4002.598779] mmcblk0: error -123 sending status command, retrying >[ 4002.598782] mmcblk0: error -123 sending status command, aborting >[ 4002.599312] mmcblk0: error -123 sending status command, retrying >[ 4002.599316] mmcblk0: error -123 sending status command, retrying >[ 4002.599319] mmcblk0: error -123 sending status command, aborting >[ 4002.599838] mmcblk0: error -123 sending status command, retrying >[ 4002.599841] mmcblk0: error -123 sending status command, retrying >[ 4002.599844] mmcblk0: error -123 sending status command, aborting >[ 4002.600364] mmcblk0: error -123 sending status command, retrying >[ 4002.600368] mmcblk0: error -123 sending status command, retrying >[ 4002.600371] mmcblk0: error -123 sending status command, aborting >[ 4002.600882] mmcblk0: error -123 sending status command, retrying >[ 4002.600885] mmcblk0: error -123 sending status command, retrying >[ 4002.600888] mmcblk0: error -123 sending status command, aborting >[ 4002.601422] mmcblk0: error -123 sending status command, retrying >[ 4002.601425] mmcblk0: error -123 sending status command, retrying >[ 4002.601428] mmcblk0: error -123 sending status command, aborting >[ 4002.601933] mmcblk0: error -123 sending status command, retrying >[ 4002.601937] mmcblk0: error -123 sending status command, retrying >[ 4002.601940] mmcblk0: error -123 sending status command, aborting >[ 4002.602474] mmcblk0: error -123 sending status command, retrying >[ 4002.602477] mmcblk0: error -123 sending status command, retrying >[ 4002.602480] mmcblk0: error -123 sending status command, aborting >[ 4002.602986] mmcblk0: error -123 sending status command, retrying >[ 4002.602989] mmcblk0: error -123 sending status command, retrying >[ 4002.602993] mmcblk0: error -123 sending status command, aborting >[ 4002.603599] mmcblk0: error -123 sending status command, retrying >[ 4002.603603] mmcblk0: error -123 sending status command, retrying >[ 4002.603606] mmcblk0: error -123 sending status command, aborting >[ 4002.604165] mmcblk0: error -123 sending status command, retrying >[ 4002.604169] mmcblk0: error -123 sending status command, retrying >[ 4002.604171] mmcblk0: error -123 sending status command, aborting >[ 4002.604721] mmcblk0: error -123 sending status command, retrying >[ 4002.604724] mmcblk0: error -123 sending status command, retrying >[ 4002.604727] mmcblk0: error -123 sending status command, aborting >[ 4002.605244] mmcblk0: error -123 sending status command, retrying >[ 4002.605248] mmcblk0: error -123 sending status command, retrying >[ 4002.605251] mmcblk0: error -123 sending status command, aborting >[ 4002.605781] mmcblk0: error -123 sending status command, retrying >[ 4002.605784] mmcblk0: error -123 sending status command, retrying >[ 4002.605787] mmcblk0: error -123 sending status command, aborting >[ 4002.606337] mmcblk0: error -123 sending status command, retrying >[ 4002.606340] mmcblk0: error -123 sending status command, retrying >[ 4002.606343] mmcblk0: error -123 sending status command, aborting >[ 4002.606877] mmcblk0: error -123 sending status command, retrying >[ 4002.606880] mmcblk0: error -123 sending status command, retrying >[ 4002.606882] mmcblk0: error -123 sending status command, aborting >[ 4002.607481] mmcblk0: error -123 sending status command, retrying >[ 4002.607484] mmcblk0: error -123 sending status command, retrying >[ 4002.607487] mmcblk0: error -123 sending status command, aborting >[ 4002.608067] mmcblk0: error -123 sending status command, retrying >[ 4002.608071] mmcblk0: error -123 sending status command, retrying >[ 4002.608073] mmcblk0: error -123 sending status command, aborting >[ 4002.608606] mmcblk0: error -123 sending status command, retrying >[ 4002.608609] mmcblk0: error -123 sending status command, retrying >[ 4002.608612] mmcblk0: error -123 sending status command, aborting >[ 4002.609188] mmcblk0: error -123 sending status command, retrying >[ 4002.609192] mmcblk0: error -123 sending status command, retrying >[ 4002.609195] mmcblk0: error -123 sending status command, aborting >[ 4002.609702] mmcblk0: error -123 sending status command, retrying >[ 4002.609705] mmcblk0: error -123 sending status command, retrying >[ 4002.609708] mmcblk0: error -123 sending status command, aborting >[ 4002.610268] mmcblk0: error -123 sending status command, retrying >[ 4002.610272] mmcblk0: error -123 sending status command, retrying >[ 4002.610275] mmcblk0: error -123 sending status command, aborting >[ 4002.610831] mmcblk0: error -123 sending status command, retrying >[ 4002.610835] mmcblk0: error -123 sending status command, retrying >[ 4002.610838] mmcblk0: error -123 sending status command, aborting >[ 4002.611424] mmcblk0: error -123 sending status command, retrying >[ 4002.611428] mmcblk0: error -123 sending status command, retrying >[ 4002.611431] mmcblk0: error -123 sending status command, aborting >[ 4002.612112] mmcblk0: error -123 sending status command, retrying >[ 4002.612116] mmcblk0: error -123 sending status command, retrying >[ 4002.612119] mmcblk0: error -123 sending status command, aborting >[ 4002.612875] mmcblk0: error -123 sending status command, retrying >[ 4002.612878] mmcblk0: error -123 sending status command, retrying >[ 4002.612881] mmcblk0: error -123 sending status command, aborting >[ 4002.613611] mmcblk0: error -123 sending status command, retrying >[ 4002.613615] mmcblk0: error -123 sending status command, retrying >[ 4002.613618] mmcblk0: error -123 sending status command, aborting >[ 4002.614362] mmcblk0: error -123 sending status command, retrying >[ 4002.614365] mmcblk0: error -123 sending status command, retrying >[ 4002.614368] mmcblk0: error -123 sending status command, aborting >[ 4002.615116] mmcblk0: error -123 sending status command, retrying >[ 4002.615119] mmcblk0: error -123 sending status command, retrying >[ 4002.615122] mmcblk0: error -123 sending status command, aborting >[ 4002.615731] mmcblk0: error -123 sending status command, retrying >[ 4002.615735] mmcblk0: error -123 sending status command, retrying >[ 4002.615738] mmcblk0: error -123 sending status command, aborting >[ 4002.616485] mmcblk0: error -123 sending status command, retrying >[ 4002.616489] mmcblk0: error -123 sending status command, retrying >[ 4002.616492] mmcblk0: error -123 sending status command, aborting >[ 4002.617160] mmcblk0: error -123 sending status command, retrying >[ 4002.617163] mmcblk0: error -123 sending status command, retrying >[ 4002.617166] mmcblk0: error -123 sending status command, aborting >[ 4002.617799] mmcblk0: error -123 sending status command, retrying >[ 4002.617802] mmcblk0: error -123 sending status command, retrying >[ 4002.617805] mmcblk0: error -123 sending status command, aborting >[ 4002.618513] mmcblk0: error -123 sending status command, retrying >[ 4002.618517] mmcblk0: error -123 sending status command, retrying >[ 4002.618519] mmcblk0: error -123 sending status command, aborting >[ 4002.619226] mmcblk0: error -123 sending status command, retrying >[ 4002.619230] mmcblk0: error -123 sending status command, retrying >[ 4002.619233] mmcblk0: error -123 sending status command, aborting >[ 4002.619790] mmcblk0: error -123 sending status command, retrying >[ 4002.619793] mmcblk0: error -123 sending status command, retrying >[ 4002.619796] mmcblk0: error -123 sending status command, aborting >[ 4002.620484] mmcblk0: error -123 sending status command, retrying >[ 4002.620487] mmcblk0: error -123 sending status command, retrying >[ 4002.620490] mmcblk0: error -123 sending status command, aborting >[ 4002.621131] mmcblk0: error -123 sending status command, retrying >[ 4002.621134] mmcblk0: error -123 sending status command, retrying >[ 4002.621137] mmcblk0: error -123 sending status command, aborting >[ 4002.621688] mmcblk0: error -123 sending status command, retrying >[ 4002.621691] mmcblk0: error -123 sending status command, retrying >[ 4002.621694] mmcblk0: error -123 sending status command, aborting >[ 4002.622268] mmcblk0: error -123 sending status command, retrying >[ 4002.622272] mmcblk0: error -123 sending status command, retrying >[ 4002.622275] mmcblk0: error -123 sending status command, aborting >[ 4002.622944] mmcblk0: error -123 sending status command, retrying >[ 4002.622947] mmcblk0: error -123 sending status command, retrying >[ 4002.622950] mmcblk0: error -123 sending status command, aborting >[ 4002.623633] mmcblk0: error -123 sending status command, retrying >[ 4002.623636] mmcblk0: error -123 sending status command, retrying >[ 4002.623639] mmcblk0: error -123 sending status command, aborting >[ 4002.624204] mmcblk0: error -123 sending status command, retrying >[ 4002.624208] mmcblk0: error -123 sending status command, retrying >[ 4002.624211] mmcblk0: error -123 sending status command, aborting >[ 4002.624856] mmcblk0: error -123 sending status command, retrying >[ 4002.624859] mmcblk0: error -123 sending status command, retrying >[ 4002.624862] mmcblk0: error -123 sending status command, aborting >[ 4002.625526] mmcblk0: error -123 sending status command, retrying >[ 4002.625530] mmcblk0: error -123 sending status command, retrying >[ 4002.625533] mmcblk0: error -123 sending status command, aborting >[ 4002.626131] mmcblk0: error -123 sending status command, retrying >[ 4002.626134] mmcblk0: error -123 sending status command, retrying >[ 4002.626137] mmcblk0: error -123 sending status command, aborting >[ 4002.626829] mmcblk0: error -123 sending status command, retrying >[ 4002.626832] mmcblk0: error -123 sending status command, retrying >[ 4002.626835] mmcblk0: error -123 sending status command, aborting >[ 4002.627419] mmcblk0: error -123 sending status command, retrying >[ 4002.627422] mmcblk0: error -123 sending status command, retrying >[ 4002.627425] mmcblk0: error -123 sending status command, aborting >[ 4002.627999] mmcblk0: error -123 sending status command, retrying >[ 4002.628024] mmcblk0: error -123 sending status command, retrying >[ 4002.628036] mmcblk0: error -123 sending status command, aborting >[ 4002.628766] mmcblk0: error -123 sending status command, retrying >[ 4002.628770] mmcblk0: error -123 sending status command, retrying >[ 4002.628773] mmcblk0: error -123 sending status command, aborting >[ 4002.629448] mmcblk0: error -123 sending status command, retrying >[ 4002.629452] mmcblk0: error -123 sending status command, retrying >[ 4002.629454] mmcblk0: error -123 sending status command, aborting >[ 4002.630116] mmcblk0: error -123 sending status command, retrying >[ 4002.630119] mmcblk0: error -123 sending status command, retrying >[ 4002.630122] mmcblk0: error -123 sending status command, aborting >[ 4002.630823] mmcblk0: error -123 sending status command, retrying >[ 4002.630827] mmcblk0: error -123 sending status command, retrying >[ 4002.630829] mmcblk0: error -123 sending status command, aborting >[ 4002.631624] mmcblk0: error -123 sending status command, retrying >[ 4002.631629] mmcblk0: error -123 sending status command, retrying >[ 4002.631632] mmcblk0: error -123 sending status command, aborting >[ 4002.632441] mmcblk0: error -123 sending status command, retrying >[ 4002.632444] mmcblk0: error -123 sending status command, retrying >[ 4002.632447] mmcblk0: error -123 sending status command, aborting >[ 4002.633243] mmcblk0: error -123 sending status command, retrying >[ 4002.633248] mmcblk0: error -123 sending status command, retrying >[ 4002.633251] mmcblk0: error -123 sending status command, aborting >[ 4002.633947] mmcblk0: error -123 sending status command, retrying >[ 4002.633951] mmcblk0: error -123 sending status command, retrying >[ 4002.633954] mmcblk0: error -123 sending status command, aborting >[ 4002.634754] mmcblk0: error -123 sending status command, retrying >[ 4002.634758] mmcblk0: error -123 sending status command, retrying >[ 4002.634761] mmcblk0: error -123 sending status command, aborting >[ 4002.635307] mmcblk0: error -123 sending status command, retrying >[ 4002.635310] mmcblk0: error -123 sending status command, retrying >[ 4002.635313] mmcblk0: error -123 sending status command, aborting >[ 4002.636169] mmcblk0: error -123 sending status command, retrying >[ 4002.636174] mmcblk0: error -123 sending status command, retrying >[ 4002.636177] mmcblk0: error -123 sending status command, aborting >[ 4002.636770] mmcblk0: error -123 sending status command, retrying >[ 4002.636773] mmcblk0: error -123 sending status command, retrying >[ 4002.636776] mmcblk0: error -123 sending status command, aborting >[ 4002.637454] mmcblk0: error -123 sending status command, retrying >[ 4002.637458] mmcblk0: error -123 sending status command, retrying >[ 4002.637461] mmcblk0: error -123 sending status command, aborting >[ 4002.638138] mmcblk0: error -123 sending status command, retrying >[ 4002.638141] mmcblk0: error -123 sending status command, retrying >[ 4002.638144] mmcblk0: error -123 sending status command, aborting >[ 4002.638798] mmcblk0: error -123 sending status command, retrying >[ 4002.638801] mmcblk0: error -123 sending status command, retrying >[ 4002.638804] mmcblk0: error -123 sending status command, aborting >[ 4002.639523] mmcblk0: error -123 sending status command, retrying >[ 4002.639527] mmcblk0: error -123 sending status command, retrying >[ 4002.639530] mmcblk0: error -123 sending status command, aborting >[ 4002.640150] mmcblk0: error -123 sending status command, retrying >[ 4002.640153] mmcblk0: error -123 sending status command, retrying >[ 4002.640156] mmcblk0: error -123 sending status command, aborting >[ 4002.640867] mmcblk0: error -123 sending status command, retrying >[ 4002.640870] mmcblk0: error -123 sending status command, retrying >[ 4002.640873] mmcblk0: error -123 sending status command, aborting >[ 4002.641535] mmcblk0: error -123 sending status command, retrying >[ 4002.641539] mmcblk0: error -123 sending status command, retrying >[ 4002.641541] mmcblk0: error -123 sending status command, aborting >[ 4002.642135] mmcblk0: error -123 sending status command, retrying >[ 4002.642139] mmcblk0: error -123 sending status command, retrying >[ 4002.642142] mmcblk0: error -123 sending status command, aborting >[ 4002.642847] mmcblk0: error -123 sending status command, retrying >[ 4002.642850] mmcblk0: error -123 sending status command, retrying >[ 4002.642853] mmcblk0: error -123 sending status command, aborting >[ 4002.643382] mmcblk0: error -123 sending status command, retrying >[ 4002.643386] mmcblk0: error -123 sending status command, retrying >[ 4002.643389] mmcblk0: error -123 sending status command, aborting >[ 4002.644084] mmcblk0: error -123 sending status command, retrying >[ 4002.644087] mmcblk0: error -123 sending status command, retrying >[ 4002.644090] mmcblk0: error -123 sending status command, aborting >[ 4002.644758] mmcblk0: error -123 sending status command, retrying >[ 4002.644761] mmcblk0: error -123 sending status command, retrying >[ 4002.644764] mmcblk0: error -123 sending status command, aborting >[ 4002.645381] mmcblk0: error -123 sending status command, retrying >[ 4002.645385] mmcblk0: error -123 sending status command, retrying >[ 4002.645388] mmcblk0: error -123 sending status command, aborting >[ 4002.646127] mmcblk0: error -123 sending status command, retrying >[ 4002.646131] mmcblk0: error -123 sending status command, retrying >[ 4002.646134] mmcblk0: error -123 sending status command, aborting >[ 4002.646836] mmcblk0: error -123 sending status command, retrying >[ 4002.646840] mmcblk0: error -123 sending status command, retrying >[ 4002.646842] mmcblk0: error -123 sending status command, aborting >[ 4002.647426] mmcblk0: error -123 sending status command, retrying >[ 4002.647429] mmcblk0: error -123 sending status command, retrying >[ 4002.647432] mmcblk0: error -123 sending status command, aborting >[ 4002.648109] mmcblk0: error -123 sending status command, retrying >[ 4002.648112] mmcblk0: error -123 sending status command, retrying >[ 4002.648115] mmcblk0: error -123 sending status command, aborting >[ 4002.648728] mmcblk0: error -123 sending status command, retrying >[ 4002.648731] mmcblk0: error -123 sending status command, retrying >[ 4002.648734] mmcblk0: error -123 sending status command, aborting >[ 4002.649279] mmcblk0: error -123 sending status command, retrying >[ 4002.649283] mmcblk0: error -123 sending status command, retrying >[ 4002.649286] mmcblk0: error -123 sending status command, aborting >[ 4002.649954] mmcblk0: error -123 sending status command, retrying >[ 4002.649958] mmcblk0: error -123 sending status command, retrying >[ 4002.649961] mmcblk0: error -123 sending status command, aborting >[ 4002.650563] mmcblk0: error -123 sending status command, retrying >[ 4002.650566] mmcblk0: error -123 sending status command, retrying >[ 4002.650569] mmcblk0: error -123 sending status command, aborting >[ 4002.651286] mmcblk0: error -123 sending status command, retrying >[ 4002.651289] mmcblk0: error -123 sending status command, retrying >[ 4002.651292] mmcblk0: error -123 sending status command, aborting >[ 4002.651862] mmcblk0: error -123 sending status command, retrying >[ 4002.651865] mmcblk0: error -123 sending status command, retrying >[ 4002.651868] mmcblk0: error -123 sending status command, aborting >[ 4002.652531] mmcblk0: error -123 sending status command, retrying >[ 4002.652534] mmcblk0: error -123 sending status command, retrying >[ 4002.652537] mmcblk0: error -123 sending status command, aborting >[ 4002.653205] mmcblk0: error -123 sending status command, retrying >[ 4002.653209] mmcblk0: error -123 sending status command, retrying >[ 4002.653212] mmcblk0: error -123 sending status command, aborting >[ 4002.653748] mmcblk0: error -123 sending status command, retrying >[ 4002.653751] mmcblk0: error -123 sending status command, retrying >[ 4002.653754] mmcblk0: error -123 sending status command, aborting >[ 4002.654344] mmcblk0: error -123 sending status command, retrying >[ 4002.654347] mmcblk0: error -123 sending status command, retrying >[ 4002.654350] mmcblk0: error -123 sending status command, aborting >[ 4002.654958] mmcblk0: error -123 sending status command, retrying >[ 4002.654962] mmcblk0: error -123 sending status command, retrying >[ 4002.654965] mmcblk0: error -123 sending status command, aborting >[ 4002.655600] mmcblk0: error -123 sending status command, retrying >[ 4002.655603] mmcblk0: error -123 sending status command, retrying >[ 4002.655606] mmcblk0: error -123 sending status command, aborting >[ 4002.656259] mmcblk0: error -123 sending status command, retrying >[ 4002.656263] mmcblk0: error -123 sending status command, retrying >[ 4002.656266] mmcblk0: error -123 sending status command, aborting >[ 4002.656955] mmcblk0: error -123 sending status command, retrying >[ 4002.656959] mmcblk0: error -123 sending status command, retrying >[ 4002.656962] mmcblk0: error -123 sending status command, aborting >[ 4002.657686] mmcblk0: error -123 sending status command, retrying >[ 4002.657690] mmcblk0: error -123 sending status command, retrying >[ 4002.657693] mmcblk0: error -123 sending status command, aborting >[ 4002.658417] mmcblk0: error -123 sending status command, retrying >[ 4002.658421] mmcblk0: error -123 sending status command, retrying >[ 4002.658424] mmcblk0: error -123 sending status command, aborting >[ 4002.659060] mmcblk0: error -123 sending status command, retrying >[ 4002.659064] mmcblk0: error -123 sending status command, retrying >[ 4002.659067] mmcblk0: error -123 sending status command, aborting >[ 4002.659739] mmcblk0: error -123 sending status command, retrying >[ 4002.659743] mmcblk0: error -123 sending status command, retrying >[ 4002.659746] mmcblk0: error -123 sending status command, aborting >[ 4002.660325] mmcblk0: error -123 sending status command, retrying >[ 4002.660329] mmcblk0: error -123 sending status command, retrying >[ 4002.660331] mmcblk0: error -123 sending status command, aborting >[ 4002.660875] mmcblk0: error -123 sending status command, retrying >[ 4002.660878] mmcblk0: error -123 sending status command, retrying >[ 4002.660881] mmcblk0: error -123 sending status command, aborting >[ 4002.661534] mmcblk0: error -123 sending status command, retrying >[ 4002.661538] mmcblk0: error -123 sending status command, retrying >[ 4002.661540] mmcblk0: error -123 sending status command, aborting >[ 4002.662186] mmcblk0: error -123 sending status command, retrying >[ 4002.662189] mmcblk0: error -123 sending status command, retrying >[ 4002.662193] mmcblk0: error -123 sending status command, aborting >[ 4002.662757] mmcblk0: error -123 sending status command, retrying >[ 4002.662760] mmcblk0: error -123 sending status command, retrying >[ 4002.662764] mmcblk0: error -123 sending status command, aborting >[ 4002.663460] mmcblk0: error -123 sending status command, retrying >[ 4002.663464] mmcblk0: error -123 sending status command, retrying >[ 4002.663467] mmcblk0: error -123 sending status command, aborting >[ 4002.664039] mmcblk0: error -123 sending status command, retrying >[ 4002.664042] mmcblk0: error -123 sending status command, retrying >[ 4002.664045] mmcblk0: error -123 sending status command, aborting >[ 4002.664681] mmcblk0: error -123 sending status command, retrying >[ 4002.664684] mmcblk0: error -123 sending status command, retrying >[ 4002.664687] mmcblk0: error -123 sending status command, aborting >[ 4002.665205] mmcblk0: error -123 sending status command, retrying >[ 4002.665209] mmcblk0: error -123 sending status command, retrying >[ 4002.665212] mmcblk0: error -123 sending status command, aborting >[ 4002.665881] mmcblk0: error -123 sending status command, retrying >[ 4002.665885] mmcblk0: error -123 sending status command, retrying >[ 4002.665888] mmcblk0: error -123 sending status command, aborting >[ 4002.666423] mmcblk0: error -123 sending status command, retrying >[ 4002.666426] mmcblk0: error -123 sending status command, retrying >[ 4002.666429] mmcblk0: error -123 sending status command, aborting >[ 4002.667103] mmcblk0: error -123 sending status command, retrying >[ 4002.667106] mmcblk0: error -123 sending status command, retrying >[ 4002.667109] mmcblk0: error -123 sending status command, aborting >[ 4002.667705] mmcblk0: error -123 sending status command, retrying >[ 4002.667709] mmcblk0: error -123 sending status command, retrying >[ 4002.667711] mmcblk0: error -123 sending status command, aborting >[ 4002.668359] mmcblk0: error -123 sending status command, retrying >[ 4002.668362] mmcblk0: error -123 sending status command, retrying >[ 4002.668366] mmcblk0: error -123 sending status command, aborting >[ 4002.668991] mmcblk0: error -123 sending status command, retrying >[ 4002.668994] mmcblk0: error -123 sending status command, retrying >[ 4002.668997] mmcblk0: error -123 sending status command, aborting >[ 4002.669560] mmcblk0: error -123 sending status command, retrying >[ 4002.669563] mmcblk0: error -123 sending status command, retrying >[ 4002.669566] mmcblk0: error -123 sending status command, aborting >[ 4002.670155] mmcblk0: error -123 sending status command, retrying >[ 4002.670160] mmcblk0: error -123 sending status command, retrying >[ 4002.670162] mmcblk0: error -123 sending status command, aborting >[ 4002.670860] mmcblk0: error -123 sending status command, retrying >[ 4002.670863] mmcblk0: error -123 sending status command, retrying >[ 4002.670866] mmcblk0: error -123 sending status command, aborting >[ 4002.671428] mmcblk0: error -123 sending status command, retrying >[ 4002.671431] mmcblk0: error -123 sending status command, retrying >[ 4002.671434] mmcblk0: error -123 sending status command, aborting >[ 4002.672102] mmcblk0: error -123 sending status command, retrying >[ 4002.672105] mmcblk0: error -123 sending status command, retrying >[ 4002.672108] mmcblk0: error -123 sending status command, aborting >[ 4002.672721] mmcblk0: error -123 sending status command, retrying >[ 4002.672724] mmcblk0: error -123 sending status command, retrying >[ 4002.672727] mmcblk0: error -123 sending status command, aborting >[ 4002.673284] mmcblk0: error -123 sending status command, retrying >[ 4002.673287] mmcblk0: error -123 sending status command, retrying >[ 4002.673290] mmcblk0: error -123 sending status command, aborting >[ 4002.673866] mmcblk0: error -123 sending status command, retrying >[ 4002.673870] mmcblk0: error -123 sending status command, retrying >[ 4002.673873] mmcblk0: error -123 sending status command, aborting >[ 4002.674429] mmcblk0: error -123 sending status command, retrying >[ 4002.674432] mmcblk0: error -123 sending status command, retrying >[ 4002.674435] mmcblk0: error -123 sending status command, aborting >[ 4002.675081] mmcblk0: error -123 sending status command, retrying >[ 4002.675084] mmcblk0: error -123 sending status command, retrying >[ 4002.675087] mmcblk0: error -123 sending status command, aborting >[ 4002.675693] mmcblk0: error -123 sending status command, retrying >[ 4002.675696] mmcblk0: error -123 sending status command, retrying >[ 4002.675699] mmcblk0: error -123 sending status command, aborting >[ 4002.676333] mmcblk0: error -123 sending status command, retrying >[ 4002.676337] mmcblk0: error -123 sending status command, retrying >[ 4002.676340] mmcblk0: error -123 sending status command, aborting >[ 4002.676950] mmcblk0: error -123 sending status command, retrying >[ 4002.676953] mmcblk0: error -123 sending status command, retrying >[ 4002.676956] mmcblk0: error -123 sending status command, aborting >[ 4002.677530] mmcblk0: error -123 sending status command, retrying >[ 4002.677534] mmcblk0: error -123 sending status command, retrying >[ 4002.677537] mmcblk0: error -123 sending status command, aborting >[ 4002.678201] mmcblk0: error -123 sending status command, retrying >[ 4002.678205] mmcblk0: error -123 sending status command, retrying >[ 4002.678208] mmcblk0: error -123 sending status command, aborting >[ 4002.678747] mmcblk0: error -123 sending status command, retrying >[ 4002.678750] mmcblk0: error -123 sending status command, retrying >[ 4002.678753] mmcblk0: error -123 sending status command, aborting >[ 4002.679436] mmcblk0: error -123 sending status command, retrying >[ 4002.679439] mmcblk0: error -123 sending status command, retrying >[ 4002.679442] mmcblk0: error -123 sending status command, aborting >[ 4002.680041] mmcblk0: error -123 sending status command, retrying >[ 4002.680044] mmcblk0: error -123 sending status command, retrying >[ 4002.680047] mmcblk0: error -123 sending status command, aborting >[ 4002.680789] mmcblk0: error -123 sending status command, retrying >[ 4002.680792] mmcblk0: error -123 sending status command, retrying >[ 4002.680795] mmcblk0: error -123 sending status command, aborting >[ 4002.681510] mmcblk0: error -123 sending status command, retrying >[ 4002.681513] mmcblk0: error -123 sending status command, retrying >[ 4002.681516] mmcblk0: error -123 sending status command, aborting >[ 4002.682124] mmcblk0: error -123 sending status command, retrying >[ 4002.682127] mmcblk0: error -123 sending status command, retrying >[ 4002.682130] mmcblk0: error -123 sending status command, aborting >[ 4002.682711] mmcblk0: error -123 sending status command, retrying >[ 4002.682714] mmcblk0: error -123 sending status command, retrying >[ 4002.682717] mmcblk0: error -123 sending status command, aborting >[ 4002.683284] mmcblk0: error -123 sending status command, retrying >[ 4002.683287] mmcblk0: error -123 sending status command, retrying >[ 4002.683290] mmcblk0: error -123 sending status command, aborting >[ 4002.683814] mmcblk0: error -123 sending status command, retrying >[ 4002.683817] mmcblk0: error -123 sending status command, retrying >[ 4002.683820] mmcblk0: error -123 sending status command, aborting >[ 4002.684368] mmcblk0: error -123 sending status command, retrying >[ 4002.684371] mmcblk0: error -123 sending status command, retrying >[ 4002.684374] mmcblk0: error -123 sending status command, aborting >[ 4002.684927] mmcblk0: error -123 sending status command, retrying >[ 4002.684930] mmcblk0: error -123 sending status command, retrying >[ 4002.684933] mmcblk0: error -123 sending status command, aborting >[ 4002.685526] mmcblk0: error -123 sending status command, retrying >[ 4002.685530] mmcblk0: error -123 sending status command, retrying >[ 4002.685533] mmcblk0: error -123 sending status command, aborting >[ 4002.686078] mmcblk0: error -123 sending status command, retrying >[ 4002.686081] mmcblk0: error -123 sending status command, retrying >[ 4002.686084] mmcblk0: error -123 sending status command, aborting >[ 4002.686656] mmcblk0: error -123 sending status command, retrying >[ 4002.686659] mmcblk0: error -123 sending status command, retrying >[ 4002.686662] mmcblk0: error -123 sending status command, aborting >[ 4002.687206] mmcblk0: error -123 sending status command, retrying >[ 4002.687209] mmcblk0: error -123 sending status command, retrying >[ 4002.687213] mmcblk0: error -123 sending status command, aborting >[ 4002.687743] mmcblk0: error -123 sending status command, retrying >[ 4002.687747] mmcblk0: error -123 sending status command, retrying >[ 4002.687750] mmcblk0: error -123 sending status command, aborting >[ 4002.688317] mmcblk0: error -123 sending status command, retrying >[ 4002.688320] mmcblk0: error -123 sending status command, retrying >[ 4002.688324] mmcblk0: error -123 sending status command, aborting >[ 4002.688861] mmcblk0: error -123 sending status command, retrying >[ 4002.688864] mmcblk0: error -123 sending status command, retrying >[ 4002.688867] mmcblk0: error -123 sending status command, aborting >[ 4002.689458] mmcblk0: error -123 sending status command, retrying >[ 4002.689462] mmcblk0: error -123 sending status command, retrying >[ 4002.689465] mmcblk0: error -123 sending status command, aborting >[ 4002.690097] mmcblk0: error -123 sending status command, retrying >[ 4002.690100] mmcblk0: error -123 sending status command, retrying >[ 4002.690103] mmcblk0: error -123 sending status command, aborting >[ 4002.690695] mmcblk0: error -123 sending status command, retrying >[ 4002.690698] mmcblk0: error -123 sending status command, retrying >[ 4002.690701] mmcblk0: error -123 sending status command, aborting >[ 4002.691278] mmcblk0: error -123 sending status command, retrying >[ 4002.691281] mmcblk0: error -123 sending status command, retrying >[ 4002.691284] mmcblk0: error -123 sending status command, aborting >[ 4002.691820] mmcblk0: error -123 sending status command, retrying >[ 4002.691823] mmcblk0: error -123 sending status command, retrying >[ 4002.691826] mmcblk0: error -123 sending status command, aborting >[ 4002.692397] mmcblk0: error -123 sending status command, retrying >[ 4002.692400] mmcblk0: error -123 sending status command, retrying >[ 4002.692403] mmcblk0: error -123 sending status command, aborting >[ 4002.692976] mmcblk0: error -123 sending status command, retrying >[ 4002.692979] mmcblk0: error -123 sending status command, retrying >[ 4002.692982] mmcblk0: error -123 sending status command, aborting >[ 4002.693531] mmcblk0: error -123 sending status command, retrying >[ 4002.693535] mmcblk0: error -123 sending status command, retrying >[ 4002.693538] mmcblk0: error -123 sending status command, aborting >[ 4002.694101] mmcblk0: error -123 sending status command, retrying >[ 4002.694104] mmcblk0: error -123 sending status command, retrying >[ 4002.694107] mmcblk0: error -123 sending status command, aborting >[ 4002.694656] mmcblk0: error -123 sending status command, retrying >[ 4002.694659] mmcblk0: error -123 sending status command, retrying >[ 4002.694662] mmcblk0: error -123 sending status command, aborting >[ 4002.695347] mmcblk0: error -123 sending status command, retrying >[ 4002.695351] mmcblk0: error -123 sending status command, retrying >[ 4002.695354] mmcblk0: error -123 sending status command, aborting >[ 4002.695981] mmcblk0: error -123 sending status command, retrying >[ 4002.695984] mmcblk0: error -123 sending status command, retrying >[ 4002.695987] mmcblk0: error -123 sending status command, aborting >[ 4002.696623] mmcblk0: error -123 sending status command, retrying >[ 4002.696626] mmcblk0: error -123 sending status command, retrying >[ 4002.696629] mmcblk0: error -123 sending status command, aborting >[ 4002.697302] mmcblk0: error -123 sending status command, retrying >[ 4002.697306] mmcblk0: error -123 sending status command, retrying >[ 4002.697309] mmcblk0: error -123 sending status command, aborting >[ 4002.697872] mmcblk0: error -123 sending status command, retrying >[ 4002.697875] mmcblk0: error -123 sending status command, retrying >[ 4002.697879] mmcblk0: error -123 sending status command, aborting >[ 4002.698469] mmcblk0: error -123 sending status command, retrying >[ 4002.698473] mmcblk0: error -123 sending status command, retrying >[ 4002.698476] mmcblk0: error -123 sending status command, aborting >[ 4002.699074] mmcblk0: error -123 sending status command, retrying >[ 4002.699078] mmcblk0: error -123 sending status command, retrying >[ 4002.699081] mmcblk0: error -123 sending status command, aborting >[ 4002.699637] mmcblk0: error -123 sending status command, retrying >[ 4002.699640] mmcblk0: error -123 sending status command, retrying >[ 4002.699643] mmcblk0: error -123 sending status command, aborting >[ 4002.700215] mmcblk0: error -123 sending status command, retrying >[ 4002.700218] mmcblk0: error -123 sending status command, retrying >[ 4002.700221] mmcblk0: error -123 sending status command, aborting >[ 4002.700844] mmcblk0: error -123 sending status command, retrying >[ 4002.700848] mmcblk0: error -123 sending status command, retrying >[ 4002.700851] mmcblk0: error -123 sending status command, aborting >[ 4002.701442] mmcblk0: error -123 sending status command, retrying >[ 4002.701446] mmcblk0: error -123 sending status command, retrying >[ 4002.701449] mmcblk0: error -123 sending status command, aborting >[ 4002.701971] mmcblk0: error -123 sending status command, retrying >[ 4002.701974] mmcblk0: error -123 sending status command, retrying >[ 4002.701978] mmcblk0: error -123 sending status command, aborting >[ 4002.702576] mmcblk0: error -123 sending status command, retrying >[ 4002.702579] mmcblk0: error -123 sending status command, retrying >[ 4002.702582] mmcblk0: error -123 sending status command, aborting >[ 4002.703179] mmcblk0: error -123 sending status command, retrying >[ 4002.703182] mmcblk0: error -123 sending status command, retrying >[ 4002.703185] mmcblk0: error -123 sending status command, aborting >[ 4002.703724] mmcblk0: error -123 sending status command, retrying >[ 4002.703727] mmcblk0: error -123 sending status command, retrying >[ 4002.703730] mmcblk0: error -123 sending status command, aborting >[ 4002.704318] mmcblk0: error -123 sending status command, retrying >[ 4002.704321] mmcblk0: error -123 sending status command, retrying >[ 4002.704324] mmcblk0: error -123 sending status command, aborting >[ 4002.704882] mmcblk0: error -123 sending status command, retrying >[ 4002.704885] mmcblk0: error -123 sending status command, retrying >[ 4002.704888] mmcblk0: error -123 sending status command, aborting >[ 4002.705511] mmcblk0: error -123 sending status command, retrying >[ 4002.705514] mmcblk0: error -123 sending status command, retrying >[ 4002.705517] mmcblk0: error -123 sending status command, aborting >[ 4002.706125] mmcblk0: error -123 sending status command, retrying >[ 4002.706128] mmcblk0: error -123 sending status command, retrying >[ 4002.706131] mmcblk0: error -123 sending status command, aborting >[ 4002.706738] mmcblk0: error -123 sending status command, retrying >[ 4002.706741] mmcblk0: error -123 sending status command, retrying >[ 4002.706744] mmcblk0: error -123 sending status command, aborting >[ 4002.707305] mmcblk0: error -123 sending status command, retrying >[ 4002.707308] mmcblk0: error -123 sending status command, retrying >[ 4002.707311] mmcblk0: error -123 sending status command, aborting >[ 4002.707983] mmcblk0: error -123 sending status command, retrying >[ 4002.707986] mmcblk0: error -123 sending status command, retrying >[ 4002.707989] mmcblk0: error -123 sending status command, aborting >[ 4002.708653] mmcblk0: error -123 sending status command, retrying >[ 4002.708657] mmcblk0: error -123 sending status command, retrying >[ 4002.708660] mmcblk0: error -123 sending status command, aborting >[ 4002.709222] mmcblk0: error -123 sending status command, retrying >[ 4002.709225] mmcblk0: error -123 sending status command, retrying >[ 4002.709228] mmcblk0: error -123 sending status command, aborting >[ 4002.709800] mmcblk0: error -123 sending status command, retrying >[ 4002.709803] mmcblk0: error -123 sending status command, retrying >[ 4002.709806] mmcblk0: error -123 sending status command, aborting >[ 4002.710432] mmcblk0: error -123 sending status command, retrying >[ 4002.710436] mmcblk0: error -123 sending status command, retrying >[ 4002.710439] mmcblk0: error -123 sending status command, aborting >[ 4002.711050] mmcblk0: error -123 sending status command, retrying >[ 4002.711053] mmcblk0: error -123 sending status command, retrying >[ 4002.711056] mmcblk0: error -123 sending status command, aborting >[ 4002.711729] mmcblk0: error -123 sending status command, retrying >[ 4002.711732] mmcblk0: error -123 sending status command, retrying >[ 4002.711735] mmcblk0: error -123 sending status command, aborting >[ 4002.712402] mmcblk0: error -123 sending status command, retrying >[ 4002.712405] mmcblk0: error -123 sending status command, retrying >[ 4002.712408] mmcblk0: error -123 sending status command, aborting >[ 4002.713096] mmcblk0: error -123 sending status command, retrying >[ 4002.713100] mmcblk0: error -123 sending status command, retrying >[ 4002.713103] mmcblk0: error -123 sending status command, aborting >[ 4002.713727] mmcblk0: error -123 sending status command, retrying >[ 4002.713730] mmcblk0: error -123 sending status command, retrying >[ 4002.713733] mmcblk0: error -123 sending status command, aborting >[ 4002.714350] mmcblk0: error -123 sending status command, retrying >[ 4002.714353] mmcblk0: error -123 sending status command, retrying >[ 4002.714357] mmcblk0: error -123 sending status command, aborting >[ 4002.715038] mmcblk0: error -123 sending status command, retrying >[ 4002.715042] mmcblk0: error -123 sending status command, retrying >[ 4002.715045] mmcblk0: error -123 sending status command, aborting >[ 4002.715576] mmcblk0: error -123 sending status command, retrying >[ 4002.715579] mmcblk0: error -123 sending status command, retrying >[ 4002.715583] mmcblk0: error -123 sending status command, aborting >[ 4002.716152] mmcblk0: error -123 sending status command, retrying >[ 4002.716156] mmcblk0: error -123 sending status command, retrying >[ 4002.716159] mmcblk0: error -123 sending status command, aborting >[ 4002.716679] mmcblk0: error -123 sending status command, retrying >[ 4002.716682] mmcblk0: error -123 sending status command, retrying >[ 4002.716685] mmcblk0: error -123 sending status command, aborting >[ 4002.717258] mmcblk0: error -123 sending status command, retrying >[ 4002.717261] mmcblk0: error -123 sending status command, retrying >[ 4002.717265] mmcblk0: error -123 sending status command, aborting >[ 4002.717976] mmcblk0: error -123 sending status command, retrying >[ 4002.717979] mmcblk0: error -123 sending status command, retrying >[ 4002.717983] mmcblk0: error -123 sending status command, aborting >[ 4002.718651] mmcblk0: error -123 sending status command, retrying >[ 4002.718654] mmcblk0: error -123 sending status command, retrying >[ 4002.718657] mmcblk0: error -123 sending status command, aborting >[ 4002.719342] mmcblk0: error -123 sending status command, retrying >[ 4002.719345] mmcblk0: error -123 sending status command, retrying >[ 4002.719348] mmcblk0: error -123 sending status command, aborting >[ 4002.720045] mmcblk0: error -123 sending status command, retrying >[ 4002.720049] mmcblk0: error -123 sending status command, retrying >[ 4002.720052] mmcblk0: error -123 sending status command, aborting >[ 4002.720699] mmcblk0: error -123 sending status command, retrying >[ 4002.720703] mmcblk0: error -123 sending status command, retrying >[ 4002.720706] mmcblk0: error -123 sending status command, aborting >[ 4002.721324] mmcblk0: error -123 sending status command, retrying >[ 4002.721328] mmcblk0: error -123 sending status command, retrying >[ 4002.721331] mmcblk0: error -123 sending status command, aborting >[ 4002.721953] mmcblk0: error -123 sending status command, retrying >[ 4002.721956] mmcblk0: error -123 sending status command, retrying >[ 4002.721960] mmcblk0: error -123 sending status command, aborting >[ 4002.722617] mmcblk0: error -123 sending status command, retrying >[ 4002.722621] mmcblk0: error -123 sending status command, retrying >[ 4002.722624] mmcblk0: error -123 sending status command, aborting >[ 4002.723307] mmcblk0: error -123 sending status command, retrying >[ 4002.723311] mmcblk0: error -123 sending status command, retrying >[ 4002.723314] mmcblk0: error -123 sending status command, aborting >[ 4002.723972] mmcblk0: error -123 sending status command, retrying >[ 4002.723975] mmcblk0: error -123 sending status command, retrying >[ 4002.723978] mmcblk0: error -123 sending status command, aborting >[ 4002.724664] mmcblk0: error -123 sending status command, retrying >[ 4002.724667] mmcblk0: error -123 sending status command, retrying >[ 4002.724670] mmcblk0: error -123 sending status command, aborting >[ 4002.725350] mmcblk0: error -123 sending status command, retrying >[ 4002.725353] mmcblk0: error -123 sending status command, retrying >[ 4002.725356] mmcblk0: error -123 sending status command, aborting >[ 4002.725935] mmcblk0: error -123 sending status command, retrying >[ 4002.725939] mmcblk0: error -123 sending status command, retrying >[ 4002.725942] mmcblk0: error -123 sending status command, aborting >[ 4002.726638] mmcblk0: error -123 sending status command, retrying >[ 4002.726642] mmcblk0: error -123 sending status command, retrying >[ 4002.726644] mmcblk0: error -123 sending status command, aborting >[ 4002.727241] mmcblk0: error -123 sending status command, retrying >[ 4002.727244] mmcblk0: error -123 sending status command, retrying >[ 4002.727247] mmcblk0: error -123 sending status command, aborting >[ 4002.727905] mmcblk0: error -123 sending status command, retrying >[ 4002.727909] mmcblk0: error -123 sending status command, retrying >[ 4002.727912] mmcblk0: error -123 sending status command, aborting >[ 4002.728462] mmcblk0: error -123 sending status command, retrying >[ 4002.728466] mmcblk0: error -123 sending status command, retrying >[ 4002.728469] mmcblk0: error -123 sending status command, aborting >[ 4002.729132] mmcblk0: error -123 sending status command, retrying >[ 4002.729136] mmcblk0: error -123 sending status command, retrying >[ 4002.729139] mmcblk0: error -123 sending status command, aborting >[ 4002.729785] mmcblk0: error -123 sending status command, retrying >[ 4002.729788] mmcblk0: error -123 sending status command, retrying >[ 4002.729791] mmcblk0: error -123 sending status command, aborting >[ 4002.730447] mmcblk0: error -123 sending status command, retrying >[ 4002.730451] mmcblk0: error -123 sending status command, retrying >[ 4002.730454] mmcblk0: error -123 sending status command, aborting >[ 4002.731079] mmcblk0: error -123 sending status command, retrying >[ 4002.731083] mmcblk0: error -123 sending status command, retrying >[ 4002.731086] mmcblk0: error -123 sending status command, aborting >[ 4002.731699] mmcblk0: error -123 sending status command, retrying >[ 4002.731702] mmcblk0: error -123 sending status command, retrying >[ 4002.731705] mmcblk0: error -123 sending status command, aborting >[ 4002.732371] mmcblk0: error -123 sending status command, retrying >[ 4002.732374] mmcblk0: error -123 sending status command, retrying >[ 4002.732377] mmcblk0: error -123 sending status command, aborting >[ 4002.732990] mmcblk0: error -123 sending status command, retrying >[ 4002.732993] mmcblk0: error -123 sending status command, retrying >[ 4002.732997] mmcblk0: error -123 sending status command, aborting >[ 4002.733570] mmcblk0: error -123 sending status command, retrying >[ 4002.733574] mmcblk0: error -123 sending status command, retrying >[ 4002.733577] mmcblk0: error -123 sending status command, aborting >[ 4002.734246] mmcblk0: error -123 sending status command, retrying >[ 4002.734250] mmcblk0: error -123 sending status command, retrying >[ 4002.734252] mmcblk0: error -123 sending status command, aborting >[ 4002.734942] mmcblk0: error -123 sending status command, retrying >[ 4002.734946] mmcblk0: error -123 sending status command, retrying >[ 4002.734948] mmcblk0: error -123 sending status command, aborting >[ 4002.735624] mmcblk0: error -123 sending status command, retrying >[ 4002.735628] mmcblk0: error -123 sending status command, retrying >[ 4002.735630] mmcblk0: error -123 sending status command, aborting >[ 4002.736169] mmcblk0: error -123 sending status command, retrying >[ 4002.736172] mmcblk0: error -123 sending status command, retrying >[ 4002.736175] mmcblk0: error -123 sending status command, aborting >[ 4002.736789] mmcblk0: error -123 sending status command, retrying >[ 4002.736792] mmcblk0: error -123 sending status command, retrying >[ 4002.736795] mmcblk0: error -123 sending status command, aborting >[ 4002.737445] mmcblk0: error -123 sending status command, retrying >[ 4002.737449] mmcblk0: error -123 sending status command, retrying >[ 4002.737451] mmcblk0: error -123 sending status command, aborting >[ 4002.738082] mmcblk0: error -123 sending status command, retrying >[ 4002.738085] mmcblk0: error -123 sending status command, retrying >[ 4002.738088] mmcblk0: error -123 sending status command, aborting >[ 4002.738695] mmcblk0: error -123 sending status command, retrying >[ 4002.738698] mmcblk0: error -123 sending status command, retrying >[ 4002.738702] mmcblk0: error -123 sending status command, aborting >[ 4002.739329] mmcblk0: error -123 sending status command, retrying >[ 4002.739332] mmcblk0: error -123 sending status command, retrying >[ 4002.739335] mmcblk0: error -123 sending status command, aborting >[ 4002.739912] mmcblk0: error -123 sending status command, retrying >[ 4002.739915] mmcblk0: error -123 sending status command, retrying >[ 4002.739918] mmcblk0: error -123 sending status command, aborting >[ 4002.740578] mmcblk0: error -123 sending status command, retrying >[ 4002.740581] mmcblk0: error -123 sending status command, retrying >[ 4002.740584] mmcblk0: error -123 sending status command, aborting >[ 4002.741333] mmcblk0: error -123 sending status command, retrying >[ 4002.741337] mmcblk0: error -123 sending status command, retrying >[ 4002.741340] mmcblk0: error -123 sending status command, aborting >[ 4002.741920] mmcblk0: error -123 sending status command, retrying >[ 4002.741923] mmcblk0: error -123 sending status command, retrying >[ 4002.741926] mmcblk0: error -123 sending status command, aborting >[ 4002.742609] mmcblk0: error -123 sending status command, retrying >[ 4002.742612] mmcblk0: error -123 sending status command, retrying >[ 4002.742615] mmcblk0: error -123 sending status command, aborting >[ 4002.743275] mmcblk0: error -123 sending status command, retrying >[ 4002.743279] mmcblk0: error -123 sending status command, retrying >[ 4002.743282] mmcblk0: error -123 sending status command, aborting >[ 4002.743920] mmcblk0: error -123 sending status command, retrying >[ 4002.743924] mmcblk0: error -123 sending status command, retrying >[ 4002.743927] mmcblk0: error -123 sending status command, aborting >[ 4002.744575] mmcblk0: error -123 sending status command, retrying >[ 4002.744579] mmcblk0: error -123 sending status command, retrying >[ 4002.744582] mmcblk0: error -123 sending status command, aborting >[ 4002.745283] mmcblk0: error -123 sending status command, retrying >[ 4002.745287] mmcblk0: error -123 sending status command, retrying >[ 4002.745290] mmcblk0: error -123 sending status command, aborting >[ 4002.745946] mmcblk0: error -123 sending status command, retrying >[ 4002.745949] mmcblk0: error -123 sending status command, retrying >[ 4002.745952] mmcblk0: error -123 sending status command, aborting >[ 4002.746560] mmcblk0: error -123 sending status command, retrying >[ 4002.746563] mmcblk0: error -123 sending status command, retrying >[ 4002.746567] mmcblk0: error -123 sending status command, aborting >[ 4002.747260] mmcblk0: error -123 sending status command, retrying >[ 4002.747264] mmcblk0: error -123 sending status command, retrying >[ 4002.747267] mmcblk0: error -123 sending status command, aborting >[ 4002.747901] mmcblk0: error -123 sending status command, retrying >[ 4002.747905] mmcblk0: error -123 sending status command, retrying >[ 4002.747908] mmcblk0: error -123 sending status command, aborting >[ 4002.748548] mmcblk0: error -123 sending status command, retrying >[ 4002.748552] mmcblk0: error -123 sending status command, retrying >[ 4002.748555] mmcblk0: error -123 sending status command, aborting >[ 4002.749178] mmcblk0: error -123 sending status command, retrying >[ 4002.749182] mmcblk0: error -123 sending status command, retrying >[ 4002.749185] mmcblk0: error -123 sending status command, aborting >[ 4002.749822] mmcblk0: error -123 sending status command, retrying >[ 4002.749825] mmcblk0: error -123 sending status command, retrying >[ 4002.749828] mmcblk0: error -123 sending status command, aborting >[ 4002.750523] mmcblk0: error -123 sending status command, retrying >[ 4002.750526] mmcblk0: error -123 sending status command, retrying >[ 4002.750529] mmcblk0: error -123 sending status command, aborting >[ 4002.751303] mmcblk0: error -123 sending status command, retrying >[ 4002.751308] mmcblk0: error -123 sending status command, retrying >[ 4002.751311] mmcblk0: error -123 sending status command, aborting >[ 4002.752073] mmcblk0: error -123 sending status command, retrying >[ 4002.752077] mmcblk0: error -123 sending status command, retrying >[ 4002.752079] mmcblk0: error -123 sending status command, aborting >[ 4002.752655] mmcblk0: error -123 sending status command, retrying >[ 4002.752658] mmcblk0: error -123 sending status command, retrying >[ 4002.752661] mmcblk0: error -123 sending status command, aborting >[ 4002.753333] mmcblk0: error -123 sending status command, retrying >[ 4002.753337] mmcblk0: error -123 sending status command, retrying >[ 4002.753340] mmcblk0: error -123 sending status command, aborting >[ 4002.753940] mmcblk0: error -123 sending status command, retrying >[ 4002.753944] mmcblk0: error -123 sending status command, retrying >[ 4002.753947] mmcblk0: error -123 sending status command, aborting >[ 4002.754582] mmcblk0: error -123 sending status command, retrying >[ 4002.754586] mmcblk0: error -123 sending status command, retrying >[ 4002.754589] mmcblk0: error -123 sending status command, aborting >[ 4002.755280] mmcblk0: error -123 sending status command, retrying >[ 4002.755283] mmcblk0: error -123 sending status command, retrying >[ 4002.755286] mmcblk0: error -123 sending status command, aborting >[ 4002.755873] mmcblk0: error -123 sending status command, retrying >[ 4002.755877] mmcblk0: error -123 sending status command, retrying >[ 4002.755879] mmcblk0: error -123 sending status command, aborting >[ 4002.756508] mmcblk0: error -123 sending status command, retrying >[ 4002.756512] mmcblk0: error -123 sending status command, retrying >[ 4002.756515] mmcblk0: error -123 sending status command, aborting >[ 4002.757136] mmcblk0: error -123 sending status command, retrying >[ 4002.757140] mmcblk0: error -123 sending status command, retrying >[ 4002.757143] mmcblk0: error -123 sending status command, aborting >[ 4002.757791] mmcblk0: error -123 sending status command, retrying >[ 4002.757795] mmcblk0: error -123 sending status command, retrying >[ 4002.757798] mmcblk0: error -123 sending status command, aborting >[ 4002.758429] mmcblk0: error -123 sending status command, retrying >[ 4002.758433] mmcblk0: error -123 sending status command, retrying >[ 4002.758436] mmcblk0: error -123 sending status command, aborting >[ 4002.759102] mmcblk0: error -123 sending status command, retrying >[ 4002.759106] mmcblk0: error -123 sending status command, retrying >[ 4002.759109] mmcblk0: error -123 sending status command, aborting >[ 4002.759735] mmcblk0: error -123 sending status command, retrying >[ 4002.759739] mmcblk0: error -123 sending status command, retrying >[ 4002.759742] mmcblk0: error -123 sending status command, aborting >[ 4002.760390] mmcblk0: error -123 sending status command, retrying >[ 4002.760394] mmcblk0: error -123 sending status command, retrying >[ 4002.760397] mmcblk0: error -123 sending status command, aborting >[ 4002.761076] mmcblk0: error -123 sending status command, retrying >[ 4002.761079] mmcblk0: error -123 sending status command, retrying >[ 4002.761082] mmcblk0: error -123 sending status command, aborting >[ 4002.761693] mmcblk0: error -123 sending status command, retrying >[ 4002.761697] mmcblk0: error -123 sending status command, retrying >[ 4002.761699] mmcblk0: error -123 sending status command, aborting >[ 4002.762386] mmcblk0: error -123 sending status command, retrying >[ 4002.762390] mmcblk0: error -123 sending status command, retrying >[ 4002.762393] mmcblk0: error -123 sending status command, aborting >[ 4002.762963] mmcblk0: error -123 sending status command, retrying >[ 4002.762967] mmcblk0: error -123 sending status command, retrying >[ 4002.762970] mmcblk0: error -123 sending status command, aborting >[ 4002.763647] mmcblk0: error -123 sending status command, retrying >[ 4002.763650] mmcblk0: error -123 sending status command, retrying >[ 4002.763653] mmcblk0: error -123 sending status command, aborting >[ 4002.764319] mmcblk0: error -123 sending status command, retrying >[ 4002.764323] mmcblk0: error -123 sending status command, retrying >[ 4002.764326] mmcblk0: error -123 sending status command, aborting >[ 4002.764856] mmcblk0: error -123 sending status command, retrying >[ 4002.764859] mmcblk0: error -123 sending status command, retrying >[ 4002.764862] mmcblk0: error -123 sending status command, aborting >[ 4002.765532] mmcblk0: error -123 sending status command, retrying >[ 4002.765535] mmcblk0: error -123 sending status command, retrying >[ 4002.765538] mmcblk0: error -123 sending status command, aborting >[ 4002.766211] mmcblk0: error -123 sending status command, retrying >[ 4002.766214] mmcblk0: error -123 sending status command, retrying >[ 4002.766217] mmcblk0: error -123 sending status command, aborting >[ 4002.766865] mmcblk0: error -123 sending status command, retrying >[ 4002.766868] mmcblk0: error -123 sending status command, retrying >[ 4002.766871] mmcblk0: error -123 sending status command, aborting >[ 4002.767457] mmcblk0: error -123 sending status command, retrying >[ 4002.767461] mmcblk0: error -123 sending status command, retrying >[ 4002.767464] mmcblk0: error -123 sending status command, aborting >[ 4002.768119] mmcblk0: error -123 sending status command, retrying >[ 4002.768123] mmcblk0: error -123 sending status command, retrying >[ 4002.768126] mmcblk0: error -123 sending status command, aborting >[ 4002.768781] mmcblk0: error -123 sending status command, retrying >[ 4002.768784] mmcblk0: error -123 sending status command, retrying >[ 4002.768787] mmcblk0: error -123 sending status command, aborting >[ 4002.769338] mmcblk0: error -123 sending status command, retrying >[ 4002.769342] mmcblk0: error -123 sending status command, retrying >[ 4002.769345] mmcblk0: error -123 sending status command, aborting >[ 4002.769944] mmcblk0: error -123 sending status command, retrying >[ 4002.769948] mmcblk0: error -123 sending status command, retrying >[ 4002.769951] mmcblk0: error -123 sending status command, aborting >[ 4002.770550] mmcblk0: error -123 sending status command, retrying >[ 4002.770553] mmcblk0: error -123 sending status command, retrying >[ 4002.770556] mmcblk0: error -123 sending status command, aborting >[ 4002.771192] mmcblk0: error -123 sending status command, retrying >[ 4002.771195] mmcblk0: error -123 sending status command, retrying >[ 4002.771198] mmcblk0: error -123 sending status command, aborting >[ 4002.771874] mmcblk0: error -123 sending status command, retrying >[ 4002.771877] mmcblk0: error -123 sending status command, retrying >[ 4002.771880] mmcblk0: error -123 sending status command, aborting >[ 4002.772484] mmcblk0: error -123 sending status command, retrying >[ 4002.772487] mmcblk0: error -123 sending status command, retrying >[ 4002.772490] mmcblk0: error -123 sending status command, aborting >[ 4002.773095] mmcblk0: error -123 sending status command, retrying >[ 4002.773098] mmcblk0: error -123 sending status command, retrying >[ 4002.773101] mmcblk0: error -123 sending status command, aborting >[ 4002.773762] mmcblk0: error -123 sending status command, retrying >[ 4002.773766] mmcblk0: error -123 sending status command, retrying >[ 4002.773769] mmcblk0: error -123 sending status command, aborting >[ 4002.774389] mmcblk0: error -123 sending status command, retrying >[ 4002.774393] mmcblk0: error -123 sending status command, retrying >[ 4002.774396] mmcblk0: error -123 sending status command, aborting >[ 4002.774920] mmcblk0: error -123 sending status command, retrying >[ 4002.774923] mmcblk0: error -123 sending status command, retrying >[ 4002.774926] mmcblk0: error -123 sending status command, aborting >[ 4003.449050] tifm_core: MMC/SD card detected in socket 0:1 >[ 4003.450797] ------------[ cut here ]------------ >[ 4003.450811] WARNING: CPU: 0 PID: 5257 at fs/fs-writeback.c:1197 __mark_inode_dirty+0x26d/0x270() >[ 4003.450813] bdi-block not registered >[ 4003.450815] Modules linked in: nls_utf8 isofs vfat fat rfcomm ccm ip6t_rpfilter ip6t_REJECT xt_conntrack bnep ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw fuse arc4 mmc_block powernow_k8 kvm_amd kvm edac_core edac_mce_amd ath5k ath mac80211 tifm_sd cfg80211 k8temp snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep sdhci_pci sdhci mmc_core btusb joydev serio_raw toshiba_acpi tifm_7xx1 tifm_core snd_seq sp5100_tco i2c_piix4 snd_seq_device snd_pcm sparse_keymap nfsd snd_timer snd soundcore >[ 4003.450882] toshiba_bluetooth video bluetooth 6lowpan_iphc rfkill wmi shpchp auth_rpcgss nfs_acl lockd binfmt_misc sunrpc ata_generic pata_acpi radeon firewire_ohci yenta_socket firewire_core crc_itu_t i2c_algo_bit usb_storage pata_atiixp drm_kms_helper ttm drm r8169 mii i2c_core >[ 4003.450908] CPU: 0 PID: 5257 Comm: dd Not tainted 3.14.4-200.fc20.x86_64 #1 >[ 4003.450911] Hardware name: TOSHIBA Satellite A215/IALAA, BIOS V2.30 01/15/2010 >[ 4003.450914] 0000000000000000 0000000022e27405 ffff8800b24a9ae8 ffffffff816ef1d2 >[ 4003.450920] ffff8800b24a9b30 ffff8800b24a9b20 ffffffff8108a1bd ffff88011b167830 >[ 4003.450924] ffff880036232e08 ffff880036233028 ffff880119e30800 0000000000000000 >[ 4003.450928] Call Trace: >[ 4003.450937] [<ffffffff816ef1d2>] dump_stack+0x45/0x56 >[ 4003.450944] [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0 >[ 4003.450948] [<ffffffff8108a23c>] warn_slowpath_fmt+0x5c/0x80 >[ 4003.450953] [<ffffffff81215d9d>] __mark_inode_dirty+0x26d/0x270 >[ 4003.450958] [<ffffffff8121bc84>] __set_page_dirty+0x74/0xc0 >[ 4003.450962] [<ffffffff8121bde1>] mark_buffer_dirty+0x61/0xd0 >[ 4003.450966] [<ffffffff8121c501>] __block_commit_write.isra.20+0x81/0xb0 >[ 4003.450972] [<ffffffff8121e126>] block_write_end+0x36/0x70 >[ 4003.450976] [<ffffffff8121f056>] ? block_write_begin+0x46/0x90 >[ 4003.450981] [<ffffffff81223740>] blkdev_write_end+0x20/0x40 >[ 4003.450986] [<ffffffff81174496>] generic_file_buffered_write+0x166/0x270 >[ 4003.450992] [<ffffffff81175e85>] __generic_file_aio_write+0x1d5/0x3e0 >[ 4003.450996] [<ffffffff81224099>] blkdev_aio_write+0x59/0xe0 >[ 4003.451001] [<ffffffff811e8ed7>] do_sync_write+0x67/0xa0 >[ 4003.451030] [<ffffffff811e969a>] vfs_write+0xba/0x1e0 >[ 4003.451034] [<ffffffff811e9574>] ? vfs_read+0xf4/0x160 >[ 4003.451038] [<ffffffff811ea0f5>] SyS_write+0x55/0xd0 >[ 4003.451044] [<ffffffff816ff569>] system_call_fastpath+0x16/0x1b >[ 4003.451046] ---[ end trace e70a297a9c00a96f ]--- >[ 4003.730775] mmc1: new SDHC card at address 1234 >[ 4003.731600] mmcblk0: mmc1:1234 SA16G 14.4 GiB >[ 4003.741124] mmcblk0: p1 p2
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1109435
: 908710