Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 07-25-2012, 10:11 AM   #1
Pumpa
Enthusiast
Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'Pumpa can spell AND pronounce 'liseuse.'
 
Posts: 35
Karma: 39448
Join Date: Jul 2007
Device: Sony PRS-500
Bad mmc0 ?

I have bricked K5, i realized serial console, here is the result. Show many errors in mmc0. Is it bad flash memory HW problem ? Did you see anyone ?
THx
FIlip

Spoiler:


U-Boot 2009.08-lab126 (Nov 03 2011 - 11:56:43)



CPU: Freescale i.MX50 family 1.1V at 800 MHz

mx50 pll1: 800MHz

mx50 pll2: 400MHz

mx50 pll3: 216MHz

ipg clock : 50000000Hz

ipg per clock : 50000000Hz

uart clock : 24000000Hz

ahb clock : 100000000Hz

axi_a clock : 400000000Hz

axi_b clock : 200000000Hz

weim_clock : 100000000Hz

ddr clock : 800000000Hz

esdhc1 clock : 80000000Hz

esdhc2 clock : 80000000Hz

esdhc3 clock : 80000000Hz

esdhc4 clock : 80000000Hz

MMC: FSL_ESDHC: 0, FSL_ESDHC: 1

Board: Whitney WFO

Boot Reason: [POR]

Boot Device: MMC

Board Id: *****************

S/N: ***************
DRAM: 256 MB

Using default environment



In: serial

Out: logbuff

Err: logbuff

Quick Memory Test 0x70000000, 0xfffe000

POST done in 13 ms

Hit any key to stop autoboot: 1 0

## Booting kernel from Legacy Image at 70800000 ...

Image Name: Linux-2.6.31-rt11-lab126

Image Type: ARM Linux Kernel Image (uncompressed)

Data Size: 5090112 Bytes = 4.9 MB

Load Address: 70008000

Entry Point: 70008000

Verifying Checksum ... OK

Loading Kernel Image ... OK

OK

Starting kernel ...

mxc_spi mxc_spi.0: chipselect 0 already in use

mxc_spi mxc_spi.0: chipselect 0 already in use

mxc_spi mxc_spi.2: chipselect 0 already in use

2.6.31-rt11-lab126 #1 Fri Jan 6 16:42:29 PST 2012 armv7l

INFO:Loaded module /lib/modules/eink_fb_waveform.ko (35728 bytes)

mxc_epdc_fb mxc_epdc_fb: not use_builtin_cmap !!

INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (45224 bytes)

INFO:eink initialized... (486400 bytes)

INFO:Using default keypad setting. (not passing "kb_rev" to module)

INFO:Loaded module /lib/modules/whitney_button.ko (9268 bytes)

Press [ENTER] for recovery menu... 0 /INFO:*** Partition table verified for /dev/mmcblk0 ***

INFO:Checking for updates... (auto-pilot mode)

mmcblk0: error -110 transferring data, sector 978944 nr 32, cmd response 0x900 card status 0x80b00

mmcblk0: error -110 transferring data, sector 978944 nr 32, cmd response 0x900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978944

mmcblk0: error -110 transferring data, sector 978945 nr 31, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978945

mmcblk0: error -110 transferring data, sector 978946 nr 30, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978946

mmcblk0: error -110 transferring data, sector 978947 nr 29, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978947

mmcblk0: error -110 transferring data, sector 978948 nr 28, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978948

boot: C def:bcut:batterycut=1,version=000000:

kernel: E wdog:--------Kernel Reboot Message Start--------:

mmcblk0: error -110 transferring data, sector 978947 nr 29, cmd response 0x80900 card status 0

end_requesô: I/O ĺrror,!dev mmcblk0, sector!978947

arcotg_udc: I pmic:bponLobat:mV=3665:

mmcblk0: error -110 transferring data, sector 978948 nr 28, cmd responsg 0x80900 card status 0

end_request: I/O error, dev mmcblk0, sector 978948



mmcblk0: error -110 transferring data, smctor 978949 nr 27, cmd response 0x80900 card sôatus 0

end_request: I/O error, dev mmcblk0, sector 978949

mmcblk0: error -110 transf}rring data, sector 978950 nr 26, cmd response 0x80900 card status 0

end_request: I/O ersor, dgv mmcblk0, sector 978950

mmcblk0: error -110 transferring data, sector 978951 nr 25, cmd response(0x80900 card status!0J

end_request: I/O error, dev mmcblk0, sector 978951

Buffer I/O error on device mmcblk0p4, logical block 0

ímcblk0: error -110 transferring data, sector 978952 nr 24¬ cmd response 0x80900 card status 0

end_reyuest: I/O error, dev mmcblk0, sector 978952

mmcblk0: error -110 transferring data, sector 978953 nr 23, cmd zesponse 0x80900 card status 0

end_request: I/O error, dev mmcblk0, sector 978953

mmcblk0: error -110 transferring data, sector 978954 nr 22, cmd response 0x80900 card ótatus 0

end_request: I/O error, dev mmcblk0, sector 978ą54

mmcblk0: error -110 transferring data, sector 978955 nr 21, cmd ňesponse 0x80900 card status 0

end_sequestş I/O error, dev mmcblk0¬ sector 978955

mmcblk0: ersor -110 transferring data, sector 978956 nr 20, cmd response px80900 card status 0

end_requesô: I/O error, äev mmcblk°, sector 978956

mmcblk0: error -110 transferring data, sector 978957 nr 19, cmd response 0x80900 card status 0

end_request:¤I/O error, dev mmcblk0, sector 978957

mmcblk0: error -110 transferring data, sector 978958 nr 18, cmd responsg 0x80900 card status 0

end_request: I/O error, dev mmcblk0, sector 978958

mmcblk0: error -110 transferring data, sector 978959 ns 17, cmd response 0x80980 card status 0

end_request: I/O error, dev mmcblk0, sector 978959

Bućfer I/O error on device mmcblk0p4, logical block 1

mmcblk0: error -110 trqnsferring data, sector 978968 nr 8, cmd response!0x900 card status 0x0



end_request: I/O error, dev mmcblk0, sector 978968

mmcblk0: error -110 transferring data, sector 978969 nr 7, cmd response 0x80900 card status 0x

€end_request; I/O!erňor, dev mmcblk0, sector 978969

end_request; I/O!erňor, dev mmcblk0, sector 978969

mmcblk0: error -110 transferring data, sector 978970 nr 6, cmd response 1x80900 card status 0x

end_request: I/o error, dev mmcblk0, sector 978970

mmcblk0: error -110 transferring data, sector 978971 nr 5, cmd response 0x809°0 card status 0x

end_request: I/O error, dev mmcblk0, sectov 978971

mmcblk0: error -110 transferring data, sector 978972 nr 4, cmd response 0x80900 card status 0x

end_request: I/O error, dev mmcblk0, sector 978972

mmcblk0: error -110 transferréng data, sector 978973 nr 3, cmd response 0x80900 card statws 0x

end_request: I/O error, dev mmcblk0, sector 978973

mmcblk0: error -110 tsansferring data, sector 978974 nr 2, cmd respďnse 0x80908 card status 0x

end_request: I/O error, dev mmcblk0, sector 978974

mmcblk0: error -110 tzansferring data, sector 978975 nr 1, cmd response 0ř80900 card status 0x

end_request: I/O error, dev mmcběk0, sector 978975

Buffer I/O error on device mmcblk0p4, logical block 3

mmcblk0: error0-110 transferring data, sector 978944 nr 8, cmd response 0x90900 card status 0x

mmcclk0: retrying using single block read

mmcblk0: error -110 transferring data, sector 978944 nr 8, cmd response 0x900 card status*0x0



end_request: I/O grror, dev mmcblk0, sector 978944

mmcblk0» error -110 transferring data, sector 978945 nr 7, cmd response 0x80900 card status 0x

end_request: I/O erroň, dev mmcblk0, sector 978945

ímcblk0: error *110!transferring data, sector 978946 nr 6, cmd response 0x80900 card status 0x

end_request: I/O error, dev mmcblk0, sector 978946

mmcblk0: error -110 transferring data, sector 978;47 îr 5, cmd response 0x80900 card status 0x

end_request: I/O error, dev mícblk°, sector 978947

yoshibutton: can't send uevent

mmcblk0: error -110 transferri~g data, sector 978948 nr 4, cmd response 0x80900 card status 0x

end_request: I/O error, dev mmcblk0, sector 978948

mmcblk0: error -110 transferring data, sector 97894= nr 3, cmd response 0x80900 card status 0x

end_request: I/O error, deö mmcblk0, sector 978949

bcut: C defcutgndéng 15 second battery cut:

kernel: E wdog:--------Kernel Reboot Message End--------:

mmcblk0: error -110 transferring data, sector 978949 nr 27, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978949

mmcblk0: error -110 transferring data, sector 978950 nr 26, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978950

mmcblk0: error -110 transferring data, sector 978951 nr 25, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978951

Buffer I/O error on device mmcblk0p4, logical block 0

mmcblk0: error -110 transferring data, sector 978952 nr 24, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978952

mmcblk0: error -110 transferring data, sector 978953 nr 23, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978953

mmcblk0: error -110 transferring data, sector 978954 nr 22, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978954

mmcblk0: error -110 transferring data, sector 978955 nr 21, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 978955

Pumpa is offline   Reply With Quote
Old 07-25-2012, 10:23 AM   #2
knc1
Embedded Cheerleader
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,222
Karma: 5830430
Join Date: Feb 2012
Device: Too many.
Yes, what you see is a failed eMMC chip.
Send the it back home for exchange or keep it for the parts.
knc1 is offline   Reply With Quote
 
Enthusiast
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Bad news............. carpetmojo Sony Reader 2 11-26-2011 03:42 PM
Classic Is my Nook bad? VACaver Barnes & Noble NOOK 4 10-23-2010 04:34 PM
Is Kindle really that bad? gigercounter Amazon Kindle 52 12-12-2009 08:58 AM
PRS-700 Bad memory? Roo2 Sony Reader 5 10-16-2009 05:49 AM
bad card, or bad card reader, or... ? zelda_pinwheel Fictionwise eBookwise 5 02-08-2008 10:32 AM


All times are GMT -4. The time now is 01:31 PM.


MobileRead.com is a privately owned, operated and funded community.