- 浏览: 461691 次
-
文章分类
最新评论
log
U-Boot 2009.08-00177-gb12fc1b (Jan 26 2011 - 08:57:00) CPU: Freescale i.MX51 family 3.0V at 800 MHz mx51 pll1: 800MHz mx51 pll2: 665MHz mx51 pll3: 216MHz ipg clock : 66500000Hz ipg per clock : 665000000Hz uart clock : 54000000Hz cspi clock : 54000000Hz axi_a clock : 166250000Hz axi_b clock : 133000000Hz emi_slow clock: 83125000Hz ddr clock : 166250000Hz esdhc clock : 216000000Hz Board: MX51 BABBAGE 3.0 [POR] Boot Device: MMC I2C: ready DRAM: 512 MB MMC: FSL_ESDHC: 0, FSL_ESDHC: 1 In: serial Out: serial Err: serial PMIC Mode: SPI Detecting HOME+POWER key for recovery ... Net: FEC0 [PRIME] Hit any key to stop autoboot: 0 MMC read: dev # 0, block # 2048,count 8192 ... 8192 blocks read: OK MMC read: dev # 0, block # 12288,count 768 ... 768 blocks read: OK ## Booting kernel from Legacy Image at 90800000 ... Image Name: Linux-2.6.31 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2694136 Bytes = 2.6 MB Load Address: 90008000 Entry Point: 90008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 90c00000 ... Image Name: Android Root Filesystem Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 212993 Bytes = 208 kB Load Address: 90308000 Entry Point: 90308000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Linux version 2.6.31 (tted@tted-desktop) (gcc version 4.4.0 (GCC) ) #19 PREEMPT Mon May 16 16:49:22 CST 2011 CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Freescale MX51 Babbage Board Memory policy: ECC disabled, Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 109728 Kernel command line: console=ttymxc0,115200 androidboot.console=ttymxc0 init=/init di1_primary calibration Unknown boot option `androidboot.console=ttymxc0': ignoring PID hash table entries: 2048 (order: 11, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 432MB = 432MB total Memory: 430584KB available (6268K code, 913K data, 168K init, 0K highmem) SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:368 MXC IRQ initialized MXC_Early serial console at MMIO 0x73fbc000 (options '115200') console [ttymxc0] enabled Console: colour dummy device 80x30 Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok regulator: core version 0.5 NET: Registered protocol family 16 i.MX IRAM pool: 128 KB@0xdb840000 IRAM READY CPU is i.MX51 Revision 3.0 MXC GPIO hardware Using SDMA I.API MXC DMA API initialized bio: create slab at 0 SCSI subsystem initialized CSPI: mxc_spi-0 probed Freescale USB OTG Driver loaded, $Revision: 1.55 $ usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb MXC I2C driver MXC I2C driver MXC HS I2C driver IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) Bluetooth: Core ver 2.15 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized mc13892 Rev 2.0 FinVer 2 detected Initializing regulators for Babbage. regulator: SW1: 600 <--> 1375 mV regulator: SW2: 900 <--> 1850 mV regulator: SW3: 1100 <--> 1850 mV regulator: SW4: 1100 <--> 1850 mV regulator: SWBST: 0 mV regulator: VIOHI: 0 mV regulator: VPLL: 1050 <--> 1800 mV regulator: VDIG: 1650 mV regulator: VSD: 1800 <--> 3150 mV regulator: VUSB2: 2400 <--> 2775 mV regulator: VVIDEO: 2775 mV regulator: VAUDIO: 2300 <--> 3000 mV regulator: VCAM: 2500 <--> 3000 mV fast normal regulator: VGEN1: 1200 mV regulator: VGEN2: 1200 <--> 3150 mV regulator: VGEN3: 1800 <--> 2900 mV regulator: VUSB: 0 mV regulator: GPO1: 0 mV regulator: GPO2: 0 mV regulator: GPO3: 0 mV regulator: GPO4: 0 mV Device spi1.0 probed NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... Freeing initrd memory: 208K LPMode driver module loaded Static Power Management for Freescale i.MX5 PM driver module loaded sdram autogating driver module loaded Bus freq driver module loaded DI1 is primary mxc_dvfs_core_probe DVFS driver module loaded i.MXC CPU frequency driver DVFS PER driver module loaded ashmem: initialized msgmni has been set to 841 alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) mxc_ipu mxc_ipu: Channel already disabled 9 mxc_ipu mxc_ipu: Channel already uninitialized 9 Console: switching to colour frame buffer device 100x30 fbcvt: 1024x768@60: CVT Name - .786M3 regulator: get() with no identifier regulator: get() with no identifier regulator: get() with no identifier mxci2c_wait_writefifo:wait error Serial: MXC Internal UART driver mxcintuart.0: ttymxc0 at MMIO 0x73fbc000 (irq = 31) is a Freescale i.MX console handover: boot [ttymxc0] -> real [ttymxc0] mxcintuart.1: ttymxc1 at MMIO 0x73fc0000 (irq = 32) is a Freescale i.MX mxcintuart.2: ttymxc2 at MMIO 0x7000c000 (irq = 33) is a Freescale i.MX brd: module loaded loop: module loaded pmem_adsp: 1 init pmem_gpu: 3 init FEC Ethernet Driver fec_enet_mii_bus: probed IEEE1588: ptp-timer is unavailable PPP generic driver version 2.4.2 libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman mxc_dataflash spi1.1: at45db321d (1000 KBytes) pagesize 512 bytes (OTP) Creating 2 MTD partitions on "mxc_dataflash": 0x000000000000-0x000000100000 : "bootloader" 0x000000100000-0x000000400000 : "kernel" MXC MTD nand Driver 3.0 i.MX GPMI NFC ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 fsl-ehci fsl-ehci.0: irq 18, io base 0x73f80000 fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 fsl-ehci fsl-ehci.1: irq 14, io base 0x73f80200 fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver usbserial USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic usbserial: USB Serial Driver core USB Serial support registered for GSM modem (1-port) usbcore: registered new interface driver option option: v0.7.2:USB Driver for GSM modems ARC USBOTG Device Controller driver (1 August 2005) mice: could not register psaux device, error: -16 mice: PS/2 mouse device common for all mice MXC keypad loaded clk: Unable to get requested clock: kpp_clk input: mxckpd as /devices/virtual/input/input0 mc13892 rtc probe start pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc0 mc13892 rtc probe succeed i2c /dev entries driver Linux video capture interface: v2.00 mxc_v4l2_output mxc_v4l2_output.0: Registered device video1 usbcore: registered new interface driver uvcvideo USB Video Class driver (v0.1.0) APM Battery Driver i2c-adapter i2c-1: ACK not received MXC WatchDog Driver 2.0 clk: Unable to get requested clock: wdog_clk MXC Watchdog # 0 Timer: initial timeout 60 sec device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com Bluetooth: Virtual HCI driver ver 1.3 Bluetooth: Generic Bluetooth USB driver ver 0.5 usbcore: registered new interface driver btusb usb 2-1: new high speed USB device using fsl-ehci and address 2 pmic_battery: probe of pmic_battery.1 failed with error -1 VPU initialized mxsdhci: MXC Secure Digital Host Controller Interface driver mxsdhci: MXC SDHCI Controller Driver. mmc0: SDHCI detect irq 128 irq 1 INTERNAL DMA mxsdhci: MXC SDHCI Controller Driver. mmc1: SDHCI detect irq 134 irq 2 INTERNAL DMA Registered led device: pmic_ledsr Registered led device: pmic_ledsg Registered led device: pmic_ledsb usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver logger: created 64K log 'log_main' logger: created 256K log 'log_events' logger: created 64K log 'log_radio' logger: created 64K log 'log_system' Advanced Linux Sound Architecture Driver Version 1.0.20. regulator: Unable to get requested regulator: VDDD sgtl5000-i2c 1-000a: SGTL5000 revision 17 usb 2-1: configuration #1 chosen from 1 choice hub 2-1:1.0: USB hub found hub 2-1:1.0: 7 ports detected No device for DAI imx-ssi-1-0 No device for DAI imx-ssi-1-1 No device for DAI imx-ssi-2-0 No device for DAI imx-ssi-2-1 DMA Sound Buffers Allocated:UseIram=1 buf->addr=1fff6000 buf->area=db856000 size=24576 DMA Sound Buffers Allocated:UseIram=1 buf->addr=a9118000 buf->area=fa321000 size=24576 asoc: SGTL5000 <-> imx-ssi-2-0 mapping ok mmc0: new SDHC card at address d80c mmcblk0: mmc0:d80c SD04G 3.69 GiB mmcblk0: p1 p2 p3 < p5 p6 > p4 ALSA device list: #0: imx-3stack (SGTL5000) TCP cubic registered NET: Registered protocol family 10 IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 Bluetooth: L2CAP ver 2.13 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized hcd_bus_suspend ehci_bus_suspend OTG wakeup irq is enabled OTG phy lowpower enable USB Host suspended Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 RPC: Registered udp transport module. RPC: Registered tcp transport module. lib80211: common routines for IEEE802.11 drivers <6>DVI device plug-out VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 regulator_init_complete: disabling GPO4 regulator_init_complete: disabling GPO3 regulator_init_complete: disabling GPO2 regulator_init_complete: disabling GPO1 regulator_init_complete: disabling VGEN1 regulator_init_complete: disabling VCAM regulator_init_complete: disabling VAUDIO regulator_init_complete: disabling VSD regulator_init_complete: disabling SWBST android init android_probe pdata: c0684dfc usb 2-1.1: new high speed USB device using fsl-ehci and address 3 android_bind mass_storage_function_add android_usb gadget: Number of LUNs=3 adb_function_add android_usb gadget: android_usb ready Suspend udc for OTG auto detect OTG wakeup irq is enabled udc resume OTG wakeup irq disable OTG phy lowpower disable OTG wakeup irq is enabled OTG phy lowpower enable dr_controller_run: udc enter low power mode USB Gadget resumed fsl-usb2-udc: bind to driver android_usb input: mxc_ts as /devices/virtual/input/input1 mxc input touchscreen loaded pmic_rtc pmic_rtc.1: setting system clock to 1970-01-01 17:07:39 UTC (61659) Freeing init memory: 168K usb 2-1.1: configuration #1 chosen from 1 choice uvcvideo: Found UVC 1.00 device (046d:09a4) input: UVC Camera (046d:09a4) as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.0/input/input2 init: cannot open '/initlogo.rle' EXT4-fs (mmcblk0p2): barriers enabled kjournald2 starting: pid 2081, dev mmcblk0p2:8, commit interval 5 seconds EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended EXT4-fs (mmcblk0p2): internal journal on mmcblk0p2:8 EXT4-fs (mmcblk0p2): delayed allocation enabled EXT4-fs: mballoc enabled EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode EXT4-fs (mmcblk0p5): barriers enabled kjournald2 starting: pid 2082, dev mmcblk0p5:8, commit interval 5 seconds EXT4-fs (mmcblk0p5): warning: maximal mount count reached, running e2fsck is recommended EXT4-fs (mmcblk0p5): internal journal on mmcblk0p5:8 EXT4-fs (mmcblk0p5): delayed allocation enabled EXT4-fs: mballoc enabled EXT4-fs (mmcblk0p5): recovery complete EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode EXT4-fs (mmcblk0p6): barriers enabled kjournald2 starting: pid 2083, dev mmcblk0p6:8, commit interval 5 seconds EXT4-fs (mmcblk0p6): warning: maximal mount count reached, running e2fsck is recommended EXT4-fs (mmcblk0p6): internal journal on mmcblk0p6:8 EXT4-fs (mmcblk0p6): delayed allocation enabled EXT4-fs: mballoc enabled EXT4-fs (mmcblk0p6): recovery complete EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' enabling adb adb_open # usb 2-1.6: new high speed USB device using fsl-ehci and address 4 warning: `wpa_supplicant' uses 32-bit capabilities (legacy support in use) usb 2-1.6: configuration #1 chosen from 1 choice scsi0 : SCSI emulation for USB Mass Storage devices otg is idle for some times,so we close the clock 9203120 close otg clk ok scsi 0:0:0:0: Direct-Access USB TO I DE/SATA Device 0009 PQ: 0 ANSI: 0 sd 0:0:0:0: [sda] Attached SCSI disk pmem: request for physical address of pmem region from process 2172. request_suspend_state: wakeup (3->0) at 26356584907 (1970-01-01 17:08:03.106718244 UTC) Not all allocated memory blocks were freed. Doing it now. Freeing list entry #0, gpuaddr=ab300000 Freeing list entry #1, gpuaddr=ab301000 Freeing list entry #2, gpuaddr=ab311000 Freeing list entry #3, gpuaddr=ab343000 Freeing list entry #6, gpuaddr=ab364000 Freeing list entry #7, gpuaddr=ab366000 Freeing list entry #8, gpuaddr=ab386000 Freeing list entry #132, gpuaddr=abb46000
相关推荐
log4cplus是C++编写的开源的日志系统,功能非常全面,用到自己开发的工程中会比较专业的,:),本文介绍了log4cplus基本概念,以及如何安装,配置。 ### 简介 ### log4cplus是C++编写的开源的日志系统,前身是java...
Log4j和Log4j2的区别 Log4j和Log4j2是两个常用的日志记录工具,它们都来自Apache开源项目。虽然它们都是日志记录工具,但是它们之间有很多区别。下面我们将从配置文件类型、核心JAR包、文件渲染和Log调用四个方面来...
5. 关键配置来了:`<param name="DatePattern" value="'.'yyyy-MM-dd'.txt'" />`,这将使日志文件名为`log.yyyy-MM-dd.txt`的形式,便于识别和清理。 6. 最后,添加`...
Log4j是一个广泛使用的Java日志记录框架,它允许开发者在应用程序中轻松地记录各种级别的日志信息,如DEBUG、INFO、WARN、ERROR等。在2021年底,一个重大的安全漏洞(CVE-2021-44228)被发现在Log4j2的早期版本中,...
**log4cplus日志封装log** 在软件开发过程中,日志记录是一项至关重要的任务,它可以帮助开发者追踪程序运行状态,定位错误,以及进行性能分析。`log4cplus`是一个专门为C++设计的开源日志系统,它提供了一种高效、...
分别有disruptor-3.3.4.jar(Log4j2异步日志的底层实现)、log4j-api-2.19.0.jar(log4j门面)、log4j-core-2.19.0.jar(log4j实现)、log4j-slf4j-impl-2.19.0.jar(SLF4J与Log4j绑定)、slf4j-api-1.7.30.jar(SLF...
Log4cxx是Apache软件基金会的一个开源项目,它是C++版的log4j,提供了一套强大的日志处理机制。本文将详细讨论如何将log4cxx封装为通用LOG宏,以及其配置文件的详细内容。 首先,让我们了解log4cxx的基本概念。Log4...
Log4perl是Perl编程语言中一个强大的日志记录框架,其设计灵感来源于Java的Log4j库。在Perl社区中,Log4perl被广泛应用于各种项目,为开发者提供了灵活、可扩展的日志处理机制。"Log-Log4perl-1.36.tar.gz"这个...
针对Log4j 2 远程代码执行漏洞,需要用到的升级资源包,适用于maven资源库,包括log4j,log4j-core,log4j-api,log4j-1.2-api,log4j-jpa等全套2.15.0 maven资源库jar包。如果是maven本地仓库使用,需要将zip包解压...
`LogFileAppender`将日志信息写入名为`log-file.txt`的文件,`ConsoleAppender`则将日志输出到控制台。日志格式由`PatternLayout`定义,可以自定义显示内容。`LevelRangeFilter`用于过滤日志级别,只允许`DEBUG`至`...
### Log4j2简介 Log4j2是Apache软件基金会推出的日志框架,它是Log4j 1.x的重构版本,旨在提供更为高效且灵活的日志解决方案。与Log4j 1.x相比,Log4j2在设计上进行了重大改进,并解决了Logback等其他日志框架中...
Log4j、Log4j2和Fastjson是Java开发中常用的三个库,它们在软件开发中扮演着重要的角色。Log4j是Apache的一个开源项目,主要用于日志记录,提供了灵活的日志配置,允许开发者根据需求调整日志输出的级别和格式。Log4...
自己编译好的log4cpp的DLL 和 LIB 封装了一个使用类,从本地读取配置log级别等信息,可输出多个种类的日志文件,输出示例如下 [2017-02-20 16:09:51.910](NOTICE)Sys : 进入了CPfy_log4cppDlg::OnBnClickedButton1...
Apache log4j2零日漏洞,根据 log4j-2.15.0-rc2 版本编译生成log4j-api-2.15.0.jar 1.解压你的jar jar xvf XXX.jar 2. 删除旧版本jar cd ./BOOT-INF/lib rm -rf log4j-api-*.jar 3. 上传新版本log4j-api-2.15.0....
《log4j-2.18.0:修复重大安全漏洞的紧急更新》 在IT领域,安全性始终是首要关注的问题。近期,一个名为“log4j2”的严重安全漏洞引发了广泛关注,它影响了所有log4j2版本,从2.0开始直到2.18.0版本之前。这个漏洞...
`log4z`提供了丰富的日志级别,包括`LOG_TRACE`、`LOG_DEBUG`、`LOG_INFO`、`LOG_WARNING`、`LOG_ERROR`和`LOG_FATAL`。根据项目需求,可以选择性地开启或关闭不同级别的日志。 ```cpp #include "log4z.h" void ...
Apache log4j2零日漏洞,根据 log4j-2.15.0-rc2 版本编译生成log4j-api-2.15.0.jar 1.解压你的jar jar xvf XXX.jar 2. 删除旧版本jar cd ./BOOT-INF/lib rm -rf log4j-api-*.jar 3. 上传新版本log4j-api-...
Log4j是Java编程语言中最常用的日志记录框架之一,由Apache软件基金会开发。它提供了灵活的日志记录功能,使得开发者能够轻松地控制日志信息的输出格式、输出位置以及输出级别。此次提及的`log4j-api-2.12.4.jar`和`...
本教程将详细阐述如何使用四个关键组件——Maven、SpringMVC、MyBatis和Log4j——来搭建一个强大的Web应用框架,旨在提高开发效率并优化项目管理。 **Maven** 是一个流行的项目管理和综合工具,它通过统一的构建...
Log4j和Log4j2是两种广泛使用的Java日志框架,它们提供了灵活的日志配置和高性能的日志处理能力。本文将详细介绍如何在SpringBoot项目中配置Log4j和Log4j2。 ### SpringBoot与Log4j Log4j是Apache的一个开源项目,...