Syslog

[lfbb]

Updating RT-N66U to NVRAM 64K... Lets see the results

Update link:


Jan 1 00:00:09 syslogd started: BusyBox v1.17.4
Jan 1 00:00:09 kernel: klogd started: BusyBox v1.17.4 (2012-05-14 08:33:01 CST)
Jan 1 00:00:09 kernel: Linux version 2.6.22.19 (root@asus) (gcc version 4.2.4) #2 Mon May 14 08:42:52 CST 2012
Jan 1 00:00:09 kernel: CPU revision is: 00019749
Jan 1 00:00:09 kernel: Determined physical RAM map:
Jan 1 00:00:09 kernel: memory: 07fff000 @ 00000000 (usable)
Jan 1 00:00:09 kernel: memory: 08000000 @ 87fff000 (usable)
Jan 1 00:00:09 kernel: Zone PFN ranges:
Jan 1 00:00:09 kernel: Normal 0 -> 131072
Jan 1 00:00:09 kernel: HighMem 131072 -> 589823
Jan 1 00:00:09 kernel: early_node_map[2] active PFN ranges
Jan 1 00:00:09 kernel: 0: 0 -> 32767
Jan 1 00:00:09 kernel: 0: 557055 -> 589823
Jan 1 00:00:09 syslog: module ledtrig-usbdev not found in modules.dep
Jan 1 00:00:09 syslog: module leds-usb not found in modules.dep
Jan 1 00:00:09 kernel: Built 1 zonelists. Total pages: 65535
Jan 1 00:00:09 kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
Jan 1 00:00:09 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Jan 1 00:00:09 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Jan 1 00:00:09 kernel: Synthesized TLB refill handler (20 instructions).
Jan 1 00:00:09 kernel: Synthesized TLB load handler fastpath (32 instructions).
Jan 1 00:00:09 kernel: Synthesized TLB store handler fastpath (32 instructions).
Jan 1 00:00:09 kernel: Synthesized TLB modify handler fastpath (31 instructions).

http://forums.smallnetbuilder.com/showthread.php?t=6714&page=78

Jan 1 00:00:06 syslogd started: BusyBox v1.17.4
Jan 1 00:00:06 kernel: klogd started: BusyBox v1.17.4 (2012-10-23 23:11:05 EDT)
Jan 1 00:00:06 kernel: Linux version 2.6.22.19 (root@asus) (gcc version 4.2.4) #1 Tue Oct 23 23:37:39 EDT 2012
Jan 1 00:00:06 kernel: CPU revision is: 00019749
Jan 1 00:00:06 kernel: Determined physical RAM map:
Jan 1 00:00:06 kernel: memory: 07fff000 @ 00000000 (usable)
Jan 1 00:00:06 kernel: memory: 08000000 @ 87fff000 (usable)
Jan 1 00:00:06 kernel: Built 1 zonelists. Total pages: 585216
Jan 1 00:00:06 kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
Jan 1 00:00:06 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Jan 1 00:00:06 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Jan 1 00:00:06 kernel: Synthesized TLB refill handler (20 instructions).
Jan 1 00:00:06 syslog: module ledtrig-usbdev not found in modules.dep
Jan 1 00:00:06 syslog: module leds-usb not found in modules.dep
Jan 1 00:00:06 kernel: Synthesized TLB load handler fastpath (32 instructions).
Jan 1 00:00:06 kernel: Synthesized TLB store handler fastpath (32 instructions).
Jan 1 00:00:06 kernel: Synthesized TLB modify handler fastpath (31 instructions).

The first log is from a SNB user's router and the second is mine. As you can see, the lines in bold don't appear in my log, is this normal?

- lfbb

 

[lfbb]

Come on guys, I'm getting paranoid on this. Just tell me if it's normal!

- lfbb

ASUSWRT RT-N66U_3.0.0.4 Wed Oct 24 03:11:07 UTC 2012
admin@RT-N66U:/tmp/home/root# dmesg
Linux version 2.6.22.19 (root@asus) (gcc version 4.2.4) #1 Tue Oct 23 23:37:39 EDT 2012
CPU revision is: 00019749
Determined physical RAM map:
memory: 07fff000 @ 00000000 (usable)
memory: 08000000 @ 87fff000 (usable)
On node 0 totalpages: 589823
Normal zone: 1024 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 130048 pages, LIFO batch:31
HighMem zone: 3583 pages used for memmap
HighMem zone: 455168 pages, LIFO batch:31
Built 1 zonelists. Total pages: 585216
Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 2048 (order: 11, 8192 bytes)
CPU: BCM5300 rev 1 pkg 0 at 600 MHz
Using 300.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 238736k/131068k available (2440k kernel code, 22456k reserved, 491k data, 192k init, 131072k highmem)
Calibrating delay loop... 299.82 BogoMIPS (lpj=1499136)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Initializing host
PCI: Reset RC
PCI: Initializing host
PCI: Reset RC
PCI: Fixing up bus 0
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.0 to 64
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.1 to 64
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
PCI/PCIe coreunit 1 is set to bus 2.
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:02:00.0 to 64
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:02:00.1 to 64
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
PCI: Fixing up bus 2
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
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
highmem bounce pool size: 64 pages
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
io scheduler noop registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0xb8000300 (irq = 8) is a 16550A
serial8250: ttyS1 at MMIO 0xb8000400 (irq = 8) is a 16550A
PPP generic driver version 2.4.2
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V0.18.3
PPTP driver version 0.8.5
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
Physically mapped flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Flash device: 0x2000000 at 0x1c000000
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "pmon"
0x00040000-0x01fe0000 : "linux"
0x00167e70-0x017c0000 : "rootfs"
0x01fe0000-0x02000000 : "nvram"
0x017c0000-0x01fe0000 : "jffs2"
Found an serial flash with 0 0KB blocks; total size 0MB
sflash: found no supported devices
dev_nvram_init: _nvram_init
_nvram_init: allocat header: 2183725056, size= 65536
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
u32 classifier
OLD policer on
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (2048 buckets, 16384 max)
ipt_time loading
ip_tables: (C) 2000-2006 Netfilter Core Team
net/ipv4/netfilter/tomato_ct.c [Oct 23 2012 23:36:59]
NET: Registered protocol family 1
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
All bugs added by David S. Miller <[email protected]>
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 192k freed
Warning: unable to open an initial console.
ctf: module license 'Proprietary' taints kernel.
et_module_init: passivemode set to 0x0
PCI: Setting latency timer of device 0000:00:01.0 to 64
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.20
wl_module_init: passivemode set to 0x0
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:01:01.0 to 64
eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:02:01.0 to 64
eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Algorithmics/MIPS FPU Emulator v1.5
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
SCSI subsystem initialized
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ufsd: driver (8.6 U86_r187446_b122, LBD=ON, acl, ioctl, rwm, ws, sd) loaded at c0227000
NTFS (with native replay) support included
optimized: speed
Build_for__asus_n66u_2011-10-27_U86_r187446_b122
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
PCI: Setting latency timer of device 0000:00:04.1 to 64
ehci_hcd 0000:00:04.1: EHCI Host Controller
ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:04.1: EHCI Fastpath: New EHCI driver starting
ehci_hcd 0000:00:04.1: irq 6, io mem 0x18004000
ehci_hcd 0000:00:04.1: USB 0.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: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
PCI: Setting latency timer of device 0000:00:04.0 to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:04.0: irq 6, io mem 0x18009000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usbcore: registered new interface driver asix
usb 1-1: new high speed USB device using ehci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver zaurus
br0: starting userspace STP failed, staring kernel STP
vlan1: add 33:33:00:00:00:01 mcast address to master interface
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: dev_set_promiscuity(master, 1)
device eth0 entered promiscuous mode
device vlan1 entered promiscuous mode
usb 1-1.4: new high speed USB device using ehci_hcd and address 3
device eth1 entered promiscuous mode
usb 1-1.4: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
device eth2 entered promiscuous mode
br0: port 3(eth2) entering listening state
br0: port 2(eth1) entering listening state
br0: port 1(vlan1) entering listening state
br0: port 3(eth2) entering learning state
br0: port 2(eth1) entering learning state
br0: port 1(vlan1) entering learning state
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
vlan1: del 33:33:00:00:00:01 mcast address from vlan interface
vlan1: del 33:33:00:00:00:01 mcast address from master interface
br0: port 1(vlan1) entering disabled state
vlan1: dev_set_promiscuity(master, 1)
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: add 33:33:00:00:00:01 mcast address to master interface
br0: port 1(vlan1) entering listening state
br0: port 1(vlan1) entering learning state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
nf_conntrack_rtsp v0.6.21 loading
nf_nat_rtsp v0.6.21 loading
scsi 0:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] Attached SCSI removable disk
sd 0:0:0:0: Attached scsi generic sg0 type 0

 

[RMerlin]

This is all very low-level kernel stuff that happens before the firmware itself gets run. Only a Linux kernel engineer would be able to tell you exactly what each of these entries mean. They are usually merely information as to what is happening, meant for debugging. I wouldn't worry about any of it.

 

[koan00]

The two logs appear to be from different fimrware versions. I wouldn't expect them to match..