Bug 679

Summary: The dmesg log looks like abnormally on routerstationpro with Laverne build 20110121
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Liang Wang <liangliang.wang>
Component: coreAssignee: Saul Wold <sgw>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Low CC: jiajun.xu, liang.li2, liangliang.wang, meta.mr.watcher, meta.watcher, yi.zhao
Version: 0.9   
Target Milestone: ---   
Hardware: Routerstationpro   
OS: mips   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Liang Wang 2011-01-28 01:14:36 UTC 
Testing Environment
===============================
Host: routerstationpro
Kernel: Linux routerstationpro 2.6.34.7-wr-standard-08672-g2ec2eda

Image location: http://autobuilder.pokylinux.org/nightly/20110121-1/machines/routerstationpro/mips/


Steps
===============================
1. Boot up the routerstationpro with sdk image
2. run 'dmesg' on target 


Observed Result
===============================
There isn't have bootup message display.

root@routerstationpro:~# dmesg
mode
eth0: processing TX ring
eth0: 0 packets sent out
eth0: processing RX ring
eth0: rx packets, limit=64, curr=40309, dirty=40309
eth0: 1 rx descriptors refilled
eth0: rx finish, curr=40310, dirty=40310, done=1
eth0: disable polling mode, rx=1, tx=0,limit=64
eth0: packet injected into TX queue
eth0: raw intr=00000001 TXPS 

...

eth0: 1 packets sent out
eth0: processing RX ring
eth0: rx packets, limit=64, curr=40597, dirty=40597
eth0: 0 rx descriptors refilled
eth0: rx finish, curr=40597, dirty=40597, done=0
eth0: disable polling mode, rx=0, tx=1,limit=64
eth0: raw intr=00000010 RXPR 
eth0: enable polling mode
eth0: processing TX ring
eth0: 0 packets sent out
eth0: processing RX ring
eth0: rx packets, limit=64, curr=40597, dirty=40597
eth0: 1 rx descriptors refilled
eth0: rx finish, curr=40598, dirty=40598, done=1
eth0: disable polling mode, rx=1, tx=0,limit=64
root@routerstationpro:~#
Comment 1 Saul Wold 2011-01-31 09:16:57 UTC 
These appear to messages from the ethernet driver. It could be that the driver included with this release has more debug enabled.