搜索
bottom↓
回复: 19

各位帮看看Mini2440开发板Linux移植一直未成功?

[复制链接]

出0入0汤圆

发表于 2014-8-10 10:33:35 | 显示全部楼层 |阅读模式
在MINI2440开发板上移植Linux,搞了一个多星期了,一直未成功!
最后使用Linux 2.6.32.63里自带的支持MINI2440的配置来编译,结果
还是出现下面的错误,板的中没有ROOT文件系统,似乎启动过程都没有完成!
这种问题真是无从下手啊!有经验的DD们给点建议吧!

U-Boot 2014.01 (Aug 06 2014 - 10:48:00)

CPUID: 32440001
FCLK:      400 MHz
HCLK:      100 MHz
PCLK:       50 MHz
DRAM:  64 MiB
WARNING: Caches not enabled
Flash: 2 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   dm9000
DREAM2440 # tftpboot 30008000 zImage.img
dm9000 i/o: 0x20000000, id: 0x90000a46
DM9000: running in 16 bit mode
MAC: 00:00:00:00:00:00
Bad MAC address (uninitialized EEPROM?), randomizing
MAC: 3a:03:63:5b:74:86
operating at unknown: 0 mode
Using dm9000 device
TFTP from server 192.168.1.10; our IP address is 192.168.1.11
Filename 'zImage.img'.
Load address: 0x30008000
Loading: T T #############################T T ####################################
         #################################################################
         #########
         77.1 KiB/s
done
Bytes transferred = 2037740 (1f17ec hex)
DREAM2440 # bootm 30008000
## Booting kernel from Legacy Image at 30008000 ...
   Image Name:   chong
   Created:      2014-08-10   2:25:28 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2037676 Bytes = 1.9 MiB
   Load Address: 30008000
   Entry Point:  30008040
   Verifying Checksum ... OK
   XIP Kernel Image ... OK

Starting kernel ...

Uncompressing Linux............................................................................................................................... done, booting the kernel.
Linux version 2.6.32.63 (chong@debian) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #2 Sun Aug 10 10:01:14 CST 2014
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: MINI2440
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd console=ttySAC0 initcall_debug=1
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60676KB available (3548K code, 417K data, 128K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:85
irq: clearing subpending status 00000003
irq: clearing subpending status 00000002
Console: colour dummy device 80x30
console [ttySAC0] enabled
Calibrating delay loop... 199.47 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
calling  spawn_ksoftirqd+0x0/0x50 @ 1
initcall spawn_ksoftirqd+0x0/0x50 returned 0 after 499 usecs
calling  spawn_softlockup_task+0x0/0x70 @ 1
initcall spawn_softlockup_task+0x0/0x70 returned 0 after 476 usecs
calling  relay_init+0x0/0x8 @ 1
initcall relay_init+0x0/0x8 returned 0 after 8 usecs
calling  init_mmap_min_addr+0x0/0x20 @ 1
initcall init_mmap_min_addr+0x0/0x20 returned 0 after 12 usecs
calling  net_ns_init+0x0/0x118 @ 1
initcall net_ns_init+0x0/0x118 returned 0 after 22 usecs
calling  ptrace_break_init+0x0/0x24 @ 1
initcall ptrace_break_init+0x0/0x24 returned 0 after 12 usecs
calling  consistent_init+0x0/0xb8 @ 1
initcall consistent_init+0x0/0xb8 returned 0 after 81 usecs
calling  s3c24xx_gpiolib_init+0x0/0x30 @ 1
initcall s3c24xx_gpiolib_init+0x0/0x30 returned 0 after 73 usecs
calling  s3c2442_core_init+0x0/0xc @ 1
initcall s3c2442_core_init+0x0/0xc returned 0 after 1183 usecs
calling  s3c2440_core_init+0x0/0xc @ 1
initcall s3c2440_core_init+0x0/0xc returned 0 after 1214 usecs
calling  s3c24xx_dma_sysclass_init+0x0/0x28 @ 1
initcall s3c24xx_dma_sysclass_init+0x0/0x28 returned 0 after 1209 usecs
calling  sysctl_init+0x0/0x3c @ 1
initcall sysctl_init+0x0/0x3c returned 0 after 977 usecs
calling  ksysfs_init+0x0/0xa0 @ 1
initcall ksysfs_init+0x0/0xa0 returned 0 after 186 usecs
calling  async_init+0x0/0x60 @ 1
initcall async_init+0x0/0x60 returned 0 after 516 usecs
calling  init_jiffies_clocksource+0x0/0xc @ 1
initcall init_jiffies_clocksource+0x0/0xc returned 0 after 19 usecs
calling  pm_init+0x0/0x3c @ 1
initcall pm_init+0x0/0x3c returned 0 after 151 usecs
calling  init_zero_pfn+0x0/0x30 @ 1
initcall init_zero_pfn+0x0/0x30 returned 0 after 11 usecs
calling  filelock_init+0x0/0x40 @ 1
initcall filelock_init+0x0/0x40 returned 0 after 60 usecs
calling  init_script_binfmt+0x0/0x10 @ 1
initcall init_script_binfmt+0x0/0x10 returned 0 after 13 usecs
calling  init_elf_binfmt+0x0/0x10 @ 1
initcall init_elf_binfmt+0x0/0x10 returned 0 after 10 usecs
calling  debugfs_init+0x0/0x60 @ 1
initcall debugfs_init+0x0/0x60 returned 0 after 129 usecs
calling  random32_init+0x0/0x78 @ 1
initcall random32_init+0x0/0x78 returned 0 after 15 usecs
calling  cpuidle_init+0x0/0x24 @ 1
initcall cpuidle_init+0x0/0x24 returned 0 after 107 usecs
calling  sock_init+0x0/0x70 @ 1
initcall sock_init+0x0/0x70 returned 0 after 699 usecs
calling  netlink_proto_init+0x0/0x1ec @ 1
NET: Registered protocol family 16
initcall netlink_proto_init+0x0/0x1ec returned 0 after 3234 usecs
calling  bdi_class_init+0x0/0x4c @ 1
initcall bdi_class_init+0x0/0x4c returned 0 after 1515 usecs
calling  kobject_uevent_init+0x0/0x68 @ 1
initcall kobject_uevent_init+0x0/0x68 returned 0 after 106 usecs
calling  gpiolib_sysfs_init+0x0/0x88 @ 1
initcall gpiolib_sysfs_init+0x0/0x88 returned 0 after 13899 usecs
calling  lcd_class_init+0x0/0x58 @ 1
initcall lcd_class_init+0x0/0x58 returned 0 after 1241 usecs
calling  backlight_class_init+0x0/0x70 @ 1
initcall backlight_class_init+0x0/0x70 returned 0 after 1276 usecs
calling  video_output_class_init+0x0/0x14 @ 1
initcall video_output_class_init+0x0/0x14 returned 0 after 1266 usecs
calling  tty_class_init+0x0/0x3c @ 1
initcall tty_class_init+0x0/0x3c returned 0 after 1267 usecs
calling  vtconsole_class_init+0x0/0xd8 @ 1
initcall vtconsole_class_init+0x0/0xd8 returned 0 after 2739 usecs
calling  spi_init+0x0/0x8c @ 1
initcall spi_init+0x0/0x8c returned 0 after 2619 usecs
calling  i2c_init+0x0/0x70 @ 1
initcall i2c_init+0x0/0x70 returned 0 after 2964 usecs
calling  customize_machine+0x0/0x24 @ 1
MINI2440: Option string mini2440=0tb
MINI2440: 't' ignored, touchscreen not compiled in
MINI2440: LCD [0:240x320] 1:800x480 2:1024x768
initcall customize_machine+0x0/0x24 returned 0 after 38046 usecs
calling  init_atags_procfs+0x0/0xf8 @ 1
initcall init_atags_procfs+0x0/0xf8 returned 0 after 107 usecs
calling  s3c2440_pm_drvinit+0x0/0x14 @ 1
initcall s3c2440_pm_drvinit+0x0/0x14 returned 0 after 22 usecs
calling  s3c2440_irq_init+0x0/0x14 @ 1
initcall s3c2440_irq_init+0x0/0x14 returned 0 after 13 usecs
calling  s3c24xx_clk_driver+0x0/0x14 @ 1
initcall s3c24xx_clk_driver+0x0/0x14 returned 0 after 14 usecs
calling  s3c2440_dma_init+0x0/0x14 @ 1
initcall s3c2440_dma_init+0x0/0x14 returned 0 after 13 usecs
calling  s3c2442_irq_init+0x0/0x14 @ 1
initcall s3c2442_irq_init+0x0/0x14 returned 0 after 16 usecs
calling  s3c2440_irq_init+0x0/0x14 @ 1
initcall s3c2440_irq_init+0x0/0x14 returned 0 after 13 usecs
calling  s3c2442_clk_init+0x0/0x14 @ 1
initcall s3c2442_clk_init+0x0/0x14 returned 0 after 14 usecs
calling  s3c2440_clk_init+0x0/0x14 @ 1
initcall s3c2440_clk_init+0x0/0x14 returned 0 after 12 usecs
calling  adc_init+0x0/0x30 @ 1
initcall adc_init+0x0/0x30 returned 0 after 1588 usecs
calling  s3c_arch_init+0x0/0x4c @ 1
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4808000, irq 33
DMA channel 1 at c4808040, irq 34
DMA channel 2 at c4808080, irq 35
DMA channel 3 at c48080c0, irq 36
S3C244X: Clock Support, DVS off
initcall s3c_arch_init+0x0/0x4c returned 0 after 30498 usecs
calling  pwm_init+0x0/0x8c @ 1
initcall pwm_init+0x0/0x8c returned 0 after 1425 usecs
calling  topology_init+0x0/0x24 @ 1
initcall topology_init+0x0/0x24 returned 0 after 1607 usecs
calling  param_sysfs_init+0x0/0x208 @ 1
initcall param_sysfs_init+0x0/0x208 returned 0 after 101797 usecs
calling  default_bdi_init+0x0/0xb4 @ 1
initcall default_bdi_init+0x0/0xb4 returned 0 after 2719 usecs
calling  init_bio+0x0/0xf4 @ 1
bio: create slab <bio-0> at 0
initcall init_bio+0x0/0xf4 returned 0 after 2723 usecs
calling  fsnotify_init+0x0/0xc @ 1
initcall fsnotify_init+0x0/0xc returned 0 after 19 usecs
calling  fsnotify_notification_init+0x0/0xa4 @ 1
initcall fsnotify_notification_init+0x0/0xa4 returned 0 after 98 usecs
calling  cryptomgr_init+0x0/0xc @ 1
initcall cryptomgr_init+0x0/0xc returned 0 after 16 usecs
calling  blk_settings_init+0x0/0x38 @ 1
initcall blk_settings_init+0x0/0x38 returned 0 after 9 usecs
calling  blk_ioc_init+0x0/0x3c @ 1
initcall blk_ioc_init+0x0/0x3c returned 0 after 43 usecs
calling  blk_softirq_init+0x0/0x2c @ 1
initcall blk_softirq_init+0x0/0x2c returned 0 after 12 usecs
calling  blk_iopoll_setup+0x0/0x2c @ 1
initcall blk_iopoll_setup+0x0/0x2c returned 0 after 9 usecs
calling  genhd_device_init+0x0/0x80 @ 1
initcall genhd_device_init+0x0/0x80 returned 0 after 2124 usecs
calling  blk_dev_integrity_init+0x0/0x3c @ 1
initcall blk_dev_integrity_init+0x0/0x3c returned 0 after 60 usecs
calling  gpiolib_debugfs_init+0x0/0x38 @ 1
initcall gpiolib_debugfs_init+0x0/0x38 returned 0 after 115 usecs
calling  fbmem_init+0x0/0xa8 @ 1
initcall fbmem_init+0x0/0xa8 returned 0 after 1566 usecs
calling  misc_init+0x0/0xbc @ 1
initcall misc_init+0x0/0xbc returned 0 after 1418 usecs
calling  usb_init+0x0/0x1ac @ 1
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
initcall usb_init+0x0/0x1ac returned 0 after 11480 usecs
calling  serio_init+0x0/0x88 @ 1
initcall serio_init+0x0/0x88 returned 0 after 1894 usecs
calling  input_init+0x0/0x150 @ 1
initcall input_init+0x0/0x150 returned 0 after 1646 usecs
calling  rtc_init+0x0/0x74 @ 1
initcall rtc_init+0x0/0x74 returned 0 after 1351 usecs
calling  i2c_adap_s3c_init+0x0/0xc @ 1
s3c-i2c s3c2440-i2c: slave address 0x10
s3c-i2c s3c2440-i2c: bus frequency set to 97 KHz
s3c-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
initcall i2c_adap_s3c_init+0x0/0xc returned 0 after 12797 usecs
calling  hwmon_init+0x0/0x48 @ 1
initcall hwmon_init+0x0/0x48 returned 0 after 1413 usecs
calling  mmc_init+0x0/0x88 @ 1
initcall mmc_init+0x0/0x88 returned 0 after 4942 usecs
calling  leds_init+0x0/0x48 @ 1
initcall leds_init+0x0/0x48 returned 0 after 1338 usecs
calling  proto_init+0x0/0xc @ 1
initcall proto_init+0x0/0xc returned 0 after 97 usecs
calling  net_dev_init+0x0/0x134 @ 1
initcall net_dev_init+0x0/0x134 returned 0 after 3501 usecs
calling  neigh_init+0x0/0x84 @ 1
initcall neigh_init+0x0/0x84 returned 0 after 20 usecs
calling  fib_rules_init+0x0/0xb0 @ 1
initcall fib_rules_init+0x0/0xb0 returned 0 after 33 usecs
calling  genl_init+0x0/0x98 @ 1
initcall genl_init+0x0/0x98 returned 0 after 235 usecs
calling  wireless_nlevent_init+0x0/0xc @ 1
initcall wireless_nlevent_init+0x0/0xc returned 0 after 15 usecs
calling  sysctl_init+0x0/0x4c @ 1
initcall sysctl_init+0x0/0x4c returned 0 after 18 usecs
calling  alignment_init+0x0/0xdc @ 1
initcall alignment_init+0x0/0xdc returned 0 after 118 usecs
calling  clocksource_done_booting+0x0/0x4c @ 1
initcall clocksource_done_booting+0x0/0x4c returned 0 after 12 usecs
calling  init_pipe_fs+0x0/0x48 @ 1
initcall init_pipe_fs+0x0/0x48 returned 0 after 176 usecs
calling  eventpoll_init+0x0/0xb0 @ 1
initcall eventpoll_init+0x0/0xb0 returned 0 after 150 usecs
calling  anon_inode_init+0x0/0x110 @ 1
initcall anon_inode_init+0x0/0x110 returned 0 after 172 usecs
calling  blk_scsi_ioctl_init+0x0/0xdc @ 1
initcall blk_scsi_ioctl_init+0x0/0xdc returned 0 after 13 usecs
calling  chr_dev_init+0x0/0xc0 @ 1
initcall chr_dev_init+0x0/0xc0 returned 0 after 14177 usecs
calling  firmware_class_init+0x0/0x6c @ 1
initcall firmware_class_init+0x0/0x6c returned 0 after 1416 usecs
calling  sysctl_core_init+0x0/0x38 @ 1
initcall sysctl_core_init+0x0/0x38 returned 0 after 241 usecs
calling  inet_init+0x0/0x1e8 @ 1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
initcall inet_init+0x0/0x1e8 returned 0 after 26296 usecs
calling  af_unix_init+0x0/0x54 @ 1
NET: Registered protocol family 1
initcall af_unix_init+0x0/0x54 returned 0 after 3287 usecs
calling  init_sunrpc+0x0/0x58 @ 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
initcall init_sunrpc+0x0/0x58 returned 0 after 11690 usecs
calling  populate_rootfs+0x0/0x224 @ 1
initcall populate_rootfs+0x0/0x224 returned 0 after 821 usecs
calling  timer_init_sysfs+0x0/0x34 @ 1
initcall timer_init_sysfs+0x0/0x34 returned 0 after 2723 usecs
calling  proc_execdomains_init+0x0/0x34 @ 1
initcall proc_execdomains_init+0x0/0x34 returned 0 after 102 usecs
calling  ioresources_init+0x0/0x54 @ 1
initcall ioresources_init+0x0/0x54 returned 0 after 81 usecs
calling  uid_cache_init+0x0/0xa4 @ 1
initcall uid_cache_init+0x0/0xa4 returned 0 after 110 usecs
calling  init_posix_timers+0x0/0x16c @ 1
initcall init_posix_timers+0x0/0x16c returned 0 after 96 usecs
calling  init_posix_cpu_timers+0x0/0xfc @ 1
initcall init_posix_cpu_timers+0x0/0xfc returned 0 after 20 usecs
calling  nsproxy_cache_init+0x0/0x3c @ 1
initcall nsproxy_cache_init+0x0/0x3c returned 0 after 89 usecs
calling  timekeeping_init_device+0x0/0x28 @ 1
initcall timekeeping_init_device+0x0/0x28 returned 0 after 2724 usecs
calling  init_clocksource_sysfs+0x0/0x50 @ 1
initcall init_clocksource_sysfs+0x0/0x50 returned 0 after 2876 usecs
calling  init_timer_list_procfs+0x0/0x38 @ 1
initcall init_timer_list_procfs+0x0/0x38 returned 0 after 206 usecs
calling  futex_init+0x0/0x6c @ 1
initcall futex_init+0x0/0x6c returned 0 after 57 usecs
calling  proc_modules_init+0x0/0x34 @ 1
initcall proc_modules_init+0x0/0x34 returned 0 after 73 usecs
calling  kallsyms_init+0x0/0x34 @ 1
initcall kallsyms_init+0x0/0x34 returned 0 after 73 usecs
calling  crash_save_vmcoreinfo_init+0x0/0x3b4 @ 1
initcall crash_save_vmcoreinfo_init+0x0/0x3b4 returned 0 after 235 usecs
calling  crash_notes_memory_init+0x0/0x50 @ 1
initcall crash_notes_memory_init+0x0/0x50 returned 0 after 15 usecs
calling  hung_task_init+0x0/0x50 @ 1
initcall hung_task_init+0x0/0x50 returned 0 after 595 usecs
calling  utsname_sysctl_init+0x0/0x18 @ 1
initcall utsname_sysctl_init+0x0/0x18 returned 0 after 249 usecs
calling  init_per_zone_wmark_min+0x0/0x68 @ 1
initcall init_per_zone_wmark_min+0x0/0x68 returned 0 after 606 usecs
calling  kswapd_init+0x0/0x18 @ 1
initcall kswapd_init+0x0/0x18 returned 0 after 595 usecs
calling  setup_vmstat+0x0/0x8c @ 1
initcall setup_vmstat+0x0/0x8c returned 0 after 148 usecs
calling  mm_sysfs_init+0x0/0x38 @ 1
initcall mm_sysfs_init+0x0/0x38 returned 0 after 128 usecs
calling  proc_vmalloc_init+0x0/0x34 @ 1
initcall proc_vmalloc_init+0x0/0x34 returned 0 after 71 usecs
calling  procswaps_init+0x0/0x34 @ 1
initcall procswaps_init+0x0/0x34 returned 0 after 72 usecs
calling  slab_proc_init+0x0/0x34 @ 1
initcall slab_proc_init+0x0/0x34 returned 0 after 72 usecs
calling  slab_sysfs_init+0x0/0xec @ 1
initcall slab_sysfs_init+0x0/0xec returned 0 after 91457 usecs
calling  fasync_init+0x0/0x3c @ 1
initcall fasync_init+0x0/0x3c returned 0 after 358 usecs
calling  proc_filesystems_init+0x0/0x34 @ 1
initcall proc_filesystems_init+0x0/0x34 returned 0 after 118 usecs
calling  dnotify_init+0x0/0x84 @ 1
initcall dnotify_init+0x0/0x84 returned 0 after 385 usecs
calling  inotify_setup+0x0/0x14 @ 1
initcall inotify_setup+0x0/0x14 returned 0 after 9 usecs
calling  inotify_user_setup+0x0/0xb8 @ 1
initcall inotify_user_setup+0x0/0xb8 returned 0 after 511 usecs
calling  aio_setup+0x0/0x80 @ 1
initcall aio_setup+0x0/0x80 returned 0 after 916 usecs
calling  proc_locks_init+0x0/0x34 @ 1
initcall proc_locks_init+0x0/0x34 returned 0 after 128 usecs
calling  init_mbcache+0x0/0x18 @ 1
initcall init_mbcache+0x0/0x18 returned 0 after 18 usecs
calling  proc_cmdline_init+0x0/0x34 @ 1
initcall proc_cmdline_init+0x0/0x34 returned 0 after 71 usecs
calling  proc_cpuinfo_init+0x0/0x34 @ 1
initcall proc_cpuinfo_init+0x0/0x34 returned 0 after 71 usecs
calling  proc_devices_init+0x0/0x34 @ 1
initcall proc_devices_init+0x0/0x34 returned 0 after 73 usecs
calling  proc_interrupts_init+0x0/0x34 @ 1
initcall proc_interrupts_init+0x0/0x34 returned 0 after 70 usecs
calling  proc_loadavg_init+0x0/0x34 @ 1
initcall proc_loadavg_init+0x0/0x34 returned 0 after 71 usecs
calling  proc_meminfo_init+0x0/0x34 @ 1
initcall proc_meminfo_init+0x0/0x34 returned 0 after 72 usecs
calling  proc_stat_init+0x0/0x34 @ 1
initcall proc_stat_init+0x0/0x34 returned 0 after 70 usecs
calling  proc_uptime_init+0x0/0x34 @ 1
initcall proc_uptime_init+0x0/0x34 returned 0 after 81 usecs
calling  proc_version_init+0x0/0x34 @ 1
initcall proc_version_init+0x0/0x34 returned 0 after 73 usecs
calling  proc_softirqs_init+0x0/0x34 @ 1
initcall proc_softirqs_init+0x0/0x34 returned 0 after 81 usecs
calling  proc_kmsg_init+0x0/0x34 @ 1
initcall proc_kmsg_init+0x0/0x34 returned 0 after 80 usecs
calling  proc_page_init+0x0/0x54 @ 1
initcall proc_page_init+0x0/0x54 returned 0 after 91 usecs
calling  init_devpts_fs+0x0/0x48 @ 1
initcall init_devpts_fs+0x0/0x48 returned 0 after 193 usecs
calling  init_ext3_fs+0x0/0x80 @ 1
initcall init_ext3_fs+0x0/0x80 returned 0 after 4105 usecs
calling  journal_init+0x0/0xbc @ 1
initcall journal_init+0x0/0xbc returned 0 after 6853 usecs
calling  init_cramfs_fs+0x0/0x2c @ 1
initcall init_cramfs_fs+0x0/0x2c returned 0 after 223 usecs
calling  init_ramfs_fs+0x0/0xc @ 1
initcall init_ramfs_fs+0x0/0xc returned 0 after 14 usecs
calling  init_fat_fs+0x0/0x60 @ 1
initcall init_fat_fs+0x0/0x60 returned 0 after 4065 usecs
calling  init_vfat_fs+0x0/0xc @ 1
initcall init_vfat_fs+0x0/0xc returned 0 after 39 usecs
calling  init_msdos_fs+0x0/0xc @ 1
initcall init_msdos_fs+0x0/0xc returned 0 after 13 usecs
calling  init_nfs_fs+0x0/0x134 @ 1
initcall init_nfs_fs+0x0/0x134 returned 0 after 9180 usecs
calling  init_nlm+0x0/0x2c @ 1
initcall init_nlm+0x0/0x2c returned 0 after 251 usecs
calling  init_jffs2_fs+0x0/0xd4 @ 1
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
initcall init_jffs2_fs+0x0/0xd4 returned 0 after 10710 usecs
calling  init_romfs_fs+0x0/0x90 @ 1
ROMFS MTD (C) 2007 Red Hat, Inc.
initcall init_romfs_fs+0x0/0x90 returned 0 after 4558 usecs
calling  init_autofs_fs+0x0/0xc @ 1
initcall init_autofs_fs+0x0/0xc returned 0 after 26 usecs
calling  init_autofs4_fs+0x0/0x20 @ 1
initcall init_autofs4_fs+0x0/0x20 returned -16 after 18 usecs
initcall init_autofs4_fs+0x0/0x20 returned with error code -16
calling  ipc_init+0x0/0x24 @ 1
msgmni has been set to 118
initcall ipc_init+0x0/0x24 returned 0 after 2369 usecs
calling  ipc_sysctl_init+0x0/0x18 @ 1
initcall ipc_sysctl_init+0x0/0x18 returned 0 after 362 usecs
calling  init_mqueue_fs+0x0/0xb0 @ 1
initcall init_mqueue_fs+0x0/0xb0 returned 0 after 2430 usecs
calling  key_proc_init+0x0/0x44 @ 1
initcall key_proc_init+0x0/0x44 returned 0 after 140 usecs
calling  crypto_wq_init+0x0/0x44 @ 1
initcall crypto_wq_init+0x0/0x44 returned 0 after 558 usecs
calling  crypto_algapi_init+0x0/0x10 @ 1
initcall crypto_algapi_init+0x0/0x10 returned 0 after 302 usecs
calling  skcipher_module_init+0x0/0x1c @ 1
initcall skcipher_module_init+0x0/0x1c returned 0 after 10 usecs
calling  chainiv_module_init+0x0/0xc @ 1
initcall chainiv_module_init+0x0/0xc returned 0 after 27 usecs
calling  eseqiv_module_init+0x0/0xc @ 1
initcall eseqiv_module_init+0x0/0xc returned 0 after 23 usecs
calling  hmac_module_init+0x0/0xc @ 1
initcall hmac_module_init+0x0/0xc returned 0 after 27 usecs
calling  md5_mod_init+0x0/0xc @ 1
initcall md5_mod_init+0x0/0xc returned 0 after 1272 usecs
calling  crypto_ecb_module_init+0x0/0xc @ 1
initcall crypto_ecb_module_init+0x0/0xc returned 0 after 31 usecs
calling  crypto_cbc_module_init+0x0/0xc @ 1
initcall crypto_cbc_module_init+0x0/0xc returned 0 after 20 usecs
calling  des_generic_mod_init+0x0/0x38 @ 1
initcall des_generic_mod_init+0x0/0x38 returned 0 after 2999 usecs
calling  aes_init+0x0/0xc @ 1
initcall aes_init+0x0/0xc returned 0 after 1662 usecs
calling  arc4_init+0x0/0xc @ 1
initcall arc4_init+0x0/0xc returned 0 after 1341 usecs
calling  michael_mic_init+0x0/0xc @ 1
initcall michael_mic_init+0x0/0xc returned 0 after 1142 usecs
calling  krng_mod_init+0x0/0xc @ 1
alg: No test for stdrng (krng)
initcall krng_mod_init+0x0/0xc returned 0 after 3132 usecs
calling  proc_genhd_init+0x0/0x54 @ 1
initcall proc_genhd_init+0x0/0x54 returned 0 after 166 usecs
calling  noop_init+0x0/0x18 @ 1
io scheduler noop registered
initcall noop_init+0x0/0x18 returned 0 after 2482 usecs
calling  as_init+0x0/0x18 @ 1
io scheduler anticipatory registered (default)
initcall as_init+0x0/0x18 returned 0 after 4026 usecs
calling  deadline_init+0x0/0x18 @ 1
io scheduler deadline registered
initcall deadline_init+0x0/0x18 returned 0 after 2894 usecs
calling  cfq_init+0x0/0xac @ 1
io scheduler cfq registered
initcall cfq_init+0x0/0xac returned 0 after 2681 usecs
calling  fb_console_init+0x0/0x154 @ 1
initcall fb_console_init+0x0/0x154 returned 0 after 1583 usecs
calling  platform_lcd_init+0x0/0xc @ 1
initcall platform_lcd_init+0x0/0xc returned 0 after 1566 usecs
calling  pwm_backlight_init+0x0/0xc @ 1
initcall pwm_backlight_init+0x0/0xc returned 0 after 1696 usecs
calling  display_class_init+0x0/0x88 @ 1
initcall display_class_init+0x0/0x88 returned 0 after 1339 usecs
calling  rand_initialize+0x0/0x2c @ 1
initcall rand_initialize+0x0/0x2c returned 0 after 204 usecs
calling  tty_init+0x0/0x104 @ 1
Unable to handle kernel paging request at virtual address 30c39280
pgd = c0004000
[30c39280] *pgd=00000000
Internal error: Oops: 5 [#1]
last sysfs file:
Modules linked in:
CPU: 0    Not tainted  (2.6.32.63 #2)
PC is at kmem_cache_alloc+0x30/0x88
LR is at con_insert_unipair+0x34/0xdc
pc : [<c008715c>]    lr : [<c019bd4c>]    psr: 20000093
sp : c3823f00  ip : 0000005f  fp : 00000003
r10: c0417c34  r9 : c03d3644  r8 : 00000001
r7 : 000000d0  r6 : 00000080  r5 : a0000013  r4 : 30c39280
r3 : 00000000  r2 : a0000093  r1 : 000000d0  r0 : c03bc40c
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Control: c000717f  Table: 30004000  DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc3822270)
Stack: (0xc3823f00 to 0xc3824000)
3f00: c03bc40c 000000d0 0000005f 0000f804 c3929600 0000005f 0000001f c019bd4c
3f20: c03d364a c3801000 c3929600 0000005f 00000000 c019c940 0000005f c03d364a
3f40: 00000014 00000000 00000014 c0418010 c00187b4 00000000 c3822030 00000000
3f60: 00000000 c0018f48 00000000 00000000 c0417d34 c00193b8 c036a2b4 c016b278
3f80: 20000013 c04178a0 00000000 c03e34c0 c00187b4 c0018884 c03477cf 00000002
3fa0: 00a10e78 00a10e78 00000002 c002837c 000000cc 00000000 00a10e78 00000002
3fc0: 00000054 c00219dc c0021b9c 00000000 00000000 00000000 00000000 c00089b0
3fe0: 00000000 00000000 c000890c 00000000 00000000 c00296f4 ffffffff ffffffff
[<c008715c>] (kmem_cache_alloc+0x30/0x88) from [<c019bd4c>] (con_insert_unipair+0x34/0xdc)
[<c019bd4c>] (con_insert_unipair+0x34/0xdc) from [<c019c940>] (con_set_default_unimap+0xc4/0x14c)
[<c019c940>] (con_set_default_unimap+0xc4/0x14c) from [<c0018f48>] (console_map_init+0x38/0x4c)
[<c0018f48>] (console_map_init+0x38/0x4c) from [<c00193b8>] (vty_init+0x120/0x15c)
[<c00193b8>] (vty_init+0x120/0x15c) from [<c0018884>] (tty_init+0xd0/0x104)
[<c0018884>] (tty_init+0xd0/0x104) from [<c002837c>] (do_one_initcall+0x5c/0x190)
[<c002837c>] (do_one_initcall+0x5c/0x190) from [<c00089b0>] (kernel_init+0xa4/0x110)
[<c00089b0>] (kernel_init+0xa4/0x110) from [<c00296f4>] (kernel_thread_exit+0x0/0x8)
Code: e5904080 e5906090 e3540000 1590308c (17943103)
---[ end trace e06eb57aa385dd0b ]---
Kernel panic - not syncing: Attempted to kill init!
[<c002d598>] (unwind_backtrace+0x0/0xcc) from [<c02c2f48>] (panic+0x3c/0x110)
[<c02c2f48>] (panic+0x3c/0x110) from [<c003d534>] (do_exit+0x60/0x5b8)
[<c003d534>] (do_exit+0x60/0x5b8) from [<c002c39c>] (die+0x150/0x174)
[<c002c39c>] (die+0x150/0x174) from [<c02c2e5c>] (__do_kernel_fault.part.3+0x54/0x64)
[<c02c2e5c>] (__do_kernel_fault.part.3+0x54/0x64) from [<c002e558>] (do_page_fault+0x1c4/0x1dc)
[<c002e558>] (do_page_fault+0x1c4/0x1dc) from [<c0028220>] (do_DataAbort+0x34/0x98)
[<c0028220>] (do_DataAbort+0x34/0x98) from [<c00288e0>] (__dabt_svc+0x40/0x60)
Exception stack(0xc3823eb8 to 0xc3823f00)
3ea0:                                                       c03bc40c 000000d0
3ec0: a0000093 00000000 30c39280 a0000013 00000080 000000d0 00000001 c03d3644
3ee0: c0417c34 00000003 0000005f c3823f00 c019bd4c c008715c 20000093 ffffffff
[<c00288e0>] (__dabt_svc+0x40/0x60) from [<c008715c>] (kmem_cache_alloc+0x30/0x88)
[<c008715c>] (kmem_cache_alloc+0x30/0x88) from [<c019bd4c>] (con_insert_unipair+0x34/0xdc)
[<c019bd4c>] (con_insert_unipair+0x34/0xdc) from [<c019c940>] (con_set_default_unimap+0xc4/0x14c)
[<c019c940>] (con_set_default_unimap+0xc4/0x14c) from [<c0018f48>] (console_map_init+0x38/0x4c)
[<c0018f48>] (console_map_init+0x38/0x4c) from [<c00193b8>] (vty_init+0x120/0x15c)
[<c00193b8>] (vty_init+0x120/0x15c) from [<c0018884>] (tty_init+0xd0/0x104)
[<c0018884>] (tty_init+0xd0/0x104) from [<c002837c>] (do_one_initcall+0x5c/0x190)
[<c002837c>] (do_one_initcall+0x5c/0x190) from [<c00089b0>] (kernel_init+0xa4/0x110)
[<c00089b0>] (kernel_init+0xa4/0x110) from [<c00296f4>] (kernel_thread_exit+0x0/0x8)

出0入0汤圆

发表于 2014-8-10 10:44:52 | 显示全部楼层
建议你把一些没有用的东西都关掉,比如dm9000,tftp,首先让整个内核完整的跑起来,这是最重要的,等内核跑起来,再尝试添加根文件系统,这样才完整,反正就一句话,一开始能跑起来最小系统就行了,其他的都是后续的东西。

出0入0汤圆

 楼主| 发表于 2014-8-10 11:08:09 | 显示全部楼层
my二月兰 发表于 2014-8-10 10:44
建议你把一些没有用的东西都关掉,比如dm9000,tftp,首先让整个内核完整的跑起来,这是最重要的,等内核跑 ...

因为刚接触LINUX,所以有些东西不是很懂,你的意思是不是只要在make menuconfig中把不需的驱动去掉即可,对于源码来说需要修改吗?

出0入0汤圆

发表于 2014-8-10 11:31:28 | 显示全部楼层
electrlife 发表于 2014-8-10 11:08
因为刚接触LINUX,所以有些东西不是很懂,你的意思是不是只要在make menuconfig中把不需的驱动去掉即可, ...

对的,没有必要的驱动,都不要加,这样减少错误的,对于源码来说,可以先不要修改,我觉得内核内加入的mini2440的板级支持,应该不需要怎么改的

出0入0汤圆

发表于 2014-8-10 11:35:58 | 显示全部楼层
还有一点忘了,你的mtd分区要看一下啊,根你的uboot中对比下啊,然后还有参数的传递问题,也要注意

出0入0汤圆

发表于 2014-8-10 11:55:24 | 显示全部楼层
你没有文件系统,移植成功了也启动不了linux。

出0入0汤圆

 楼主| 发表于 2014-8-10 12:26:37 | 显示全部楼层
wangcjishu 发表于 2014-8-10 11:55
你没有文件系统,移植成功了也启动不了linux。

目前仅处在学习LINUX开发流程上面,想先移植linux,再制作rootfs,然后形成一个完整的可开发的内核,以了解linux开发流程。
在完成以上两步骤的基本上,深入学习驱动开发!我希望能通过一年的时间看看能不能转到linux上开发!

出0入0汤圆

 楼主| 发表于 2014-8-10 12:28:11 | 显示全部楼层
my二月兰 发表于 2014-8-10 11:35
还有一点忘了,你的mtd分区要看一下啊,根你的uboot中对比下啊,然后还有参数的传递问题,也要注意 ...

目前只求能启动起来,即可,还没做rootfs,参数也很简,noinitrd console=ttySAC0 initcall_debug=1

出0入0汤圆

发表于 2014-8-10 12:54:36 | 显示全部楼层
electrlife 发表于 2014-8-10 12:26
目前仅处在学习LINUX开发流程上面,想先移植linux,再制作rootfs,然后形成一个完整的可开发的内核,以了 ...

建议首先利用mini2440自动的内核和文件系统能跑起来,之后再替换自己的内核使系统能跑起来。

出0入0汤圆

 楼主| 发表于 2014-8-10 15:25:23 | 显示全部楼层
wangcjishu 发表于 2014-8-10 12:54
建议首先利用mini2440自动的内核和文件系统能跑起来,之后再替换自己的内核使系统能跑起来。 ...

嗯,现在利用是官方下的kernel.org上下的内核,自带的支持mini2440,我试着编译了下,同样的一个bin,有时可以启动起来,有时却不可以!
如下所示:

calling  net_secret_init+0x0/0x1c @ 1
initcall net_secret_init+0x0/0x1c returned 0 after 183 usecs
calling  tcp_congestion_default+0x0/0xc @ 1
initcall tcp_congestion_default+0x0/0xc returned 0 after 20 usecs
calling  ip_auto_config+0x0/0xe84 @ 1
initcall ip_auto_config+0x0/0xe84 returned 0 after 147 usecs
calling  initialize_hashrnd+0x0/0x1c @ 1
initcall initialize_hashrnd+0x0/0x1c returned 0 after 76 usecs
async_waiting @ 1
async_continuing @ 1 after 15 usec
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.

VFS: Cannot open root device "<NULL>" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00             256 mtdblock0 (driver?)
1f01             128 mtdblock1 (driver?)
1f02            5120 mtdblock2 (driver?)
1f03          256640 mtdblock3 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<c002e598>] (unwind_backtrace+0x0/0xcc) from [<c02c6070>] (panic+0x3c/0x110)
[<c02c6070>] (panic+0x3c/0x110) from [<c0008d64>] (mount_block_root+0x1bc/0x1fc)
[<c0008d64>] (mount_block_root+0x1bc/0x1fc) from [<c0009100>] (prepare_namespace+0x158/0x1ac)
[<c0009100>] (prepare_namespace+0x158/0x1ac) from [<c00089ec>] (kernel_init+0xe0/0x110)
[<c00089ec>] (kernel_init+0xe0/0x110) from [<c002a6f4>] (kernel_thread_exit+0x0/0x8)

出0入0汤圆

发表于 2014-8-10 16:06:57 | 显示全部楼层
你的启动参数没有设好,这个东西千万不要想一下成功的,别急,首先看看你的uboot中的对于nandflash分区情况,是否和你的kernel中分区一样的,这个必须是一样的才行,然后,你的kernel中的启动参数问题,是uboot传参数,还是用kernel中自己设定的参数,这个也要做好,如果做好这两点,我觉的应该可以起来的。

出0入0汤圆

发表于 2014-8-10 16:11:43 | 显示全部楼层
electrlife 发表于 2014-8-10 15:25
嗯,现在利用是官方下的kernel.org上下的内核,自带的支持mini2440,我试着编译了下,同样的一个bin,有 ...

从打印出来的信息看,是缺文件系统了,你改一下启动参数,为linuxrc,尝试挂一下文件系统试试。

出0入0汤圆

 楼主| 发表于 2014-8-10 16:58:18 | 显示全部楼层
本帖最后由 electrlife 于 2014-8-10 17:00 编辑
my二月兰 发表于 2014-8-10 16:11
从打印出来的信息看,是缺文件系统了,你改一下启动参数,为linuxrc,尝试挂一下文件系统试试。 ...


是的,目前还没有做rootfs,我只是想先跑起来,上面的确实已经跑起来了,但是不稳定,
同时的代码,我不停上电运行,结果有时跑不起来! 会停在下面的位置:
initcall chainiv_module_init+0x0/0xc returned 0 after 25 usecs
calling  eseqiv_module_init+0x0/0xc @ 1
initcall eseqiv_module_init+0x0/0xc returned 0 after 26 usecs
calling  hmac_module_init+0x0/0xc @ 1
initcall hmac_module_init+0x0/0xc returned 0 after 27 usecs
calling  md5_mod_init+0x0/0xc @ 1
initcall md5_mod_init+0x0/0xc returned 0 after 1270 usecs
calling  crypto_ecb_module_init+0x0/0xc @ 1
initcall crypto_ecb_module_init+0x0/0xc returned 0 after 34 usecs
calling  crypto_cbc_module_init+0x0/0xc @ 1
initcall crypto_cbc_module_init+0x0/0xc returned 0 after 20 usecs
calling  des_generic_mod_init+0x0/0x38 @ 1
initcall des_generic_mod_init+0x0/0x38 returned 0 after 3021 usecs
calling  aes_init+0x0/0xc @ 1
initcall aes_init+0x0/0xc returned 0 after 1644 usecs
calling  arc4_init+0x0/0xc @ 1
initcall arc4_init+0x0/0xc returned 0 after 1578 usecs
calling  michael_mic_init+0x0/0xc @ 1
initcall michael_mic_init+0x0/0xc returned 0 after 1151 usecs
calling  krng_mod_init+0x0/0xc @ 1
alg: No test for stdrng (krng)
initcall krng_mod_init+0x0/0xc returned 0 after 2853 usecs
calling  proc_genhd_init+0x0/0x54 @ 1
initcall proc_genhd_init+0x0/0x54 returned 0 after 171 usecs
calling  noop_init+0x0/0x18 @ 1
io scheduler noop registered
initcall noop_init+0x0/0x18 returned 0 after 2466 usecs
calling  as_init+0x0/0x18 @ 1
io scheduler anticipatory registered (default)
initcall as_init+0x0/0x18 returned 0 after 4024 usecs
calling  deadline_init+0x0/0x18 @ 1
io scheduler deadline registered
initcall deadline_init+0x0/0x18 returned 0 after 2797 usecs
calling  cfq_init+0x0/0xac @ 1
io scheduler cfq registered
initcall cfq_init+0x0/0xac returned 0 after 3005 usecs
calling  fb_console_init+0x0/0x154 @ 1
initcall fb_console_init+0x0/0x154 returned 0 after 1731 usecs
calling  platform_lcd_init+0x0/0xc @ 1
initcall platform_lcd_init+0x0/0xc returned 0 after 1711 usecs
calling  pwm_backlight_init+0x0/0xc @ 1
initcall pwm_backlight_init+0x0/0xc returned 0 after 1428 usecs
calling  display_class_init+0x0/0x88 @ 1
initcall display_class_init+0x0/0x88 returned 0 after 1308 usecs
calling  s3c2410fb_init+0x0/0x28 @ 1
死在这里,什么信息也没有了

出0入0汤圆

发表于 2014-8-11 09:03:13 | 显示全部楼层
electrlife 发表于 2014-8-10 15:25
嗯,现在利用是官方下的kernel.org上下的内核,自带的支持mini2440,我试着编译了下,同样的一个bin,有 ...

不要用kernel.org的去试,你用mini2440光盘自带的去试,首先保证能用光盘的里跑起来

出0入0汤圆

 楼主| 发表于 2014-8-11 19:50:57 | 显示全部楼层
wangcjishu 发表于 2014-8-11 09:03
不要用kernel.org的去试,你用mini2440光盘自带的去试,首先保证能用光盘的里跑起来 ...

泪奔啊,用MINI2440自带的光盘中的zImage,烧进去结果和我自己移植的一样,有时可以启动起来,有时失败,基本是50%的概率。
硬件我觉得不会有问题,难道和我移植的U-BOOT有关系,请教下Kernel解压运行后还和U-BOOT有关系吗?

出0入0汤圆

发表于 2014-8-11 23:01:27 | 显示全部楼层
估计你的文件系统中的lib和当前的内核不兼容,你编译完内核后
#make modules_install INSTALL_MOD_PATH=你的文件系统lib的路径
你试一试吧,以前我也遇到内核在启动时就崩溃的问题,就是用这种方法解决的

出0入0汤圆

发表于 2014-8-12 08:51:56 | 显示全部楼层
electrlife 发表于 2014-8-11 19:50
泪奔啊,用MINI2440自带的光盘中的zImage,烧进去结果和我自己移植的一样,有时可以启动起来,有时失败, ...

我觉得是硬件问题,你换成友善的bootloader,再引导内核看看,如果还是有时成功,有时不成功,差不多就是硬件问题了。

出0入0汤圆

发表于 2014-8-12 09:15:19 | 显示全部楼层
electrlife 发表于 2014-8-11 19:50
泪奔啊,用MINI2440自带的光盘中的zImage,烧进去结果和我自己移植的一样,有时可以启动起来,有时失败, ...

uboot调用kernel后,所有的控制权都交给uboot了,就像XP的启动滚动条在运行时,你是回不到bois一个道理
有可能uboot中哪些驱动配置不对,但kernel一般都会重新配置相应的硬件驱动,所有由uboot引起内核崩溃的概率应该是很小的

出0入0汤圆

 楼主| 发表于 2014-8-12 21:05:12 | 显示全部楼层
nculibin 发表于 2014-8-11 23:01
估计你的文件系统中的lib和当前的内核不兼容,你编译完内核后
#make modules_install INSTALL_MOD_PATH=你 ...

没听明白,内核启动时应该不需文件系统的吧?
是在还没有加载ROOTFS时就崩溃了!
能否再说详细些!谢谢!

出0入0汤圆

发表于 2014-8-15 22:26:29 | 显示全部楼层
electrlife 发表于 2014-8-12 21:05
没听明白,内核启动时应该不需文件系统的吧?
是在还没有加载ROOTFS时就崩溃了!
能否再说详细些!谢谢! ...

从你给的日志来说明,
回复有的说是文件系统缺失,有的是驱动问题
这个也不太好说,关键你的给一个正确的日志来,这样才能分析出问题
你先试着把内核跑到文件系统再说吧,先把驱动弄好了
回帖提示: 反政府言论将被立即封锁ID 在按“提交”前,请自问一下:我这样表达会给举报吗,会给自己惹麻烦吗? 另外:尽量不要使用Mark、顶等没有意义的回复。不得大量使用大字体和彩色字。【本论坛不允许直接上传手机拍摄图片,浪费大家下载带宽和论坛服务器空间,请压缩后(图片小于1兆)才上传。压缩方法可以在微信里面发给自己(不要勾选“原图),然后下载,就能得到压缩后的图片】。另外,手机版只能上传图片,要上传附件需要切换到电脑版(不需要使用电脑,手机上切换到电脑版就行,页面底部)。
您需要登录后才可以回帖 登录 | 注册

本版积分规则

手机版|Archiver|amobbs.com 阿莫电子技术论坛 ( 粤ICP备2022115958号, 版权所有:东莞阿莫电子贸易商行 创办于2004年 (公安交互式论坛备案:44190002001997 ) )

GMT+8, 2024-4-19 11:33

© Since 2004 www.amobbs.com, 原www.ourdev.cn, 原www.ouravr.com

快速回复 返回顶部 返回列表