search

AbhinavDS / 0xdroid

Automatically exported from code.google.com/p/0xdroid
0 stars 1 forks source link

test android kernel 2.6.32 and 0xlab android 2.6.32 error mounting ext 3 #144

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
I test kernelat first boot 
mmc0: new high speed MMC card at address 0001
mmcblk0: mmc0:0001 000000 980 MiB 
 mmcblk0: p1 p2
kjournald starting.  Commit interval 5 seconds
mmcblk0: error -84 transferring data, sector 401625, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 401625
Buffer I/O error on device mmcblk0p2, logical block 0
lost page write due to I/O error on mmcblk0p2
EXT3 FS on mmcblk0p2, internal journal
EXT3-fs: mounted filesystem with writeback data mode.
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 140K
Warning: unable to open an initial console.
# input: Fake Touchscreen as /devices/virtual/input/input0
warning: `rild' uses 32-bit capabilities (legacy support in use)
mmcblk0: error -84 transferring data, sector 403945, nr 40, card status 0x900
end_request: I/O error, dev mmcblk0, sector 403945
end_request: I/O error, dev mmcblk0, sector 403953
end_request: I/O error, dev mmcblk0, sector 403961
end_request: I/O error, dev mmcblk0, sector 403969
end_request: I/O error, dev mmcblk0, sector 403977
mmcblk0: error -84 transferring data, sector 403865, nr 72, card status 0x900
end_request: I/O error, dev mmcblk0, sector 403865
end_request: I/O error, dev mmcblk0, sector 403873
end_request: I/O error, dev mmcblk0, sector 403881
end_request: I/O error, dev mmcblk0, sector 403889
end_request: I/O error, dev mmcblk0, sector 403897
end_request: I/O error, dev mmcblk0, sector 403905
end_request: I/O error, dev mmcblk0, sector 403913
end_request: I/O error, dev mmcblk0, sector 403921
end_request: I/O error, dev mmcblk0, sector 403929
mmcblk0: error -84 transferring data, sector 403841, nr 16, card status 0x900
end_request: I/O error, dev mmcblk0, sector 403841
end_request: I/O error, dev mmcblk0, sector 403849
Aborting journal on device mmcblk0p2.
ext3_abort called.
EXT3-fs error (device mmcblk0p2): ext3_journal_start_sb: Detected aborted 
journal
Remounting filesystem read-only
init: untracked pid 682 exited
init: untracked pid 721 exited
init: untracked pid 737 exited
init: untracked pid 753 exited
init: untracked pid 769 exited
init: untracked pid 785 exited
init: untracked pid 801 exited
init: untracked pid 817 exited

after reboot ext3 file system Error loading journal
-------------------------------------
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
omapfb omapfb: failed to allocate framebuffer
omapfb omapfb: failed to allocate fbmem
omapfb omapfb: failed to setup omapfb
omapfb: probe of omapfb failed with error -12
twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:05:44 UTC 
(946685144)
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed MMC card at address 0001
mmcblk0: mmc0:0001 000000 980 MiB 
 mmcblk0: p1 p2
JBD: no valid journal superblock found
EXT3-fs: error loading journal.
List of all partitions:
1f00             512 mtdblock0 (driver?)
1f01            1920 mtdblock1 (driver?)
1f02             128 mtdblock2 (driver?)
1f03            4096 mtdblock3 (driver?)
1f04          255488 mtdblock4 (driver?)
b300         1003520 mmcblk0 driver: mmcblk
  b301          200781 mmcblk0p1
  b302          795217 mmcblk0p2
No filesystem could mount root, tried:  ext3 vfat
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

What is the image version having this issue? You can see that from
"/version.txt" in the image.
Version:

What is the date of your image built?
Date:

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by greatma...@gmail.com on 11 Aug 2010 at 12:41

GoogleCodeExporter commented 8 years ago 
( kernel 2.6.32)I think that default mount root (ro)  kernel can't write but 
(kernel 2.6.29) default mount root (rw) please  tell me about  default mount 
root  config  in kernel

thank you for suggestion

Original comment by greatma...@gmail.com on 11 Aug 2010 at 1:32

GoogleCodeExporter commented 8 years ago 
init: untracked pid 682 exited
init: untracked pid 721 exited
init: untracked pid 737 exited
init: untracked pid 753 exited
init: untracked pid 769 exited
init: untracked pid 785 exited
init: untracked pid 801 exited
init: untracked pid 817 exited

analysis
above process is zygote can't start

Original comment by greatma...@gmail.com on 11 Aug 2010 at 1:57

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
i have omapfb error..........

my condition

Linux version 2.6.32.9-gd4f5a36 (root@no-desktop) (gcc version 4.3.3 (Sourcery 
G++ Lite 2009q1-203) ) #1 Mon Nov 8 09:20:45 CST 2010
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Devkit8000
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 rw 
rootfstype=ext3 rootdelay=3 omap-dss.def_disp=lcd init=/init
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 123676KB available (4820K code, 999K data, 140K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/266/500 MHz
Reprogramming SDRC clock to 266000000 Hz
dpll3_m2_clk rate change failed: -22------------------------------------?first 
error
......

and 

omapfb omapfb: failed to allocate framebuffer
omapfb omapfb: failed to allocate fbmem
omapfb omapfb: failed to setup omapfb
omapfb: probe of omapfb failed with error 
-12--------------------------------------? second error
regulator_init_complete: incomplete constraints, leaving VDAC on
twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 UTC 
(946684800)
Waiting 3sec before mounting root device...

i use 「logcat」

have third error

I/ServiceManager(  773): serviceinit: untracked pid 779 exited
 'media.audio_flinger' died
I/ServiceManager(  773): service 'media.player' died
I/ServiceManager(  773): service 'media.camera' died
I/ServiceManager(  773): service 'media.audio_policy' died

i don't how to set bootargs is currect or other problem?

Original comment by suhanj...@gmail.com on 9 Nov 2010 at 12:00

GoogleCodeExporter commented 8 years ago 
Maybe this is because of physical storage error?

Original comment by jserv.tw@gmail.com on 9 Nov 2010 at 7:11

GoogleCodeExporter commented 8 years ago 
I resolve this problem....

u-boot setenv

setenv bootargs console=ttyS2,115200n8  noinitrd root=/dev/mmcblk0p2 rw 
rootfstype=ext3 rootdelay=3 vram=12M omapdss.def_disp=lcd 
omapfb.mode=lcd:480x272 omapfb.rotate=1 init=/init

Original comment by suhanj...@gmail.com on 10 Nov 2010 at 1:07

GoogleCodeExporter commented 8 years ago

Original comment by jserv.tw@gmail.com on 12 Nov 2010 at 6:13