[OpenWrt-Devel] Frequent reboot WBMR & Lantiq
Hi, I've been running the Buffalo WBMR-HP-G300H routers for a while now, actually three of them on a bonded line, and in general they are working very well. On one of the lines I am seeing very frequent reboots (of the whole system, not just the DSL) every two or three hours, the other two lines seem to be stable (although I have seen reboots on the other lines, not for the last week or so). The "faulty" line is the one that seems to sync closer to it's limit (it has a smaller noise margin) but it's been stable with other DSL routers in the past. I am going to swap the hardware around, to make sure it's not something hardware related (they are all running the same firmware), although I suspect it's a panic caused by the lantiq driver when some situation happens on the line ... the same router stayed up for over 6 weeks with no DSL connected while I was puting the build together. Is there any way to get a crash dump configured in openwrt so I can get more info about the reboot cause? Thanks, Lee. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
On 21/02/12 09:17, lee.es...@nowonline.co.uk wrote: > Hi, > > I've been running the Buffalo WBMR-HP-G300H routers for a while now, > actually three of them on a bonded line, and in general they are working > very well. > > On one of the lines I am seeing very frequent reboots (of the whole > system, not just the DSL) every two or three hours, the other two lines > seem to be stable (although I have seen reboots on the other lines, not > for the last week or so). The "faulty" line is the one that seems to > sync closer to it's limit (it has a smaller noise margin) but it's been > stable with other DSL routers in the past. > > I am going to swap the hardware around, to make sure it's not something > hardware related (they are all running the same firmware), although I > suspect it's a panic caused by the lantiq driver when some situation > happens on the line ... the same router stayed up for over 6 weeks with > no DSL connected while I was puting the build together. > > Is there any way to get a crash dump configured in openwrt so I can get > more info about the reboot cause? > > Thanks, > > Lee. > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > crashlog is what you are looking for. ../o.git/build_dir/linux-lantiq_ar9/linux-3.1.9/patches/generic/930-crashlog.patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
On Tue, 21 Feb 2012 09:41:44 +0100, John Crispin wrote: On 21/02/12 09:17, lee.es...@nowonline.co.uk wrote: Hi, I've been running the Buffalo WBMR-HP-G300H routers for a while now, actually three of them on a bonded line, and in general they are working very well. On one of the lines I am seeing very frequent reboots (of the whole system, not just the DSL) every two or three hours, the other two lines seem to be stable (although I have seen reboots on the other lines, not for the last week or so). The "faulty" line is the one that seems to sync closer to it's limit (it has a smaller noise margin) but it's been stable with other DSL routers in the past. I am going to swap the hardware around, to make sure it's not something hardware related (they are all running the same firmware), although I suspect it's a panic caused by the lantiq driver when some situation happens on the line ... the same router stayed up for over 6 weeks with no DSL connected while I was puting the build together. Is there any way to get a crash dump configured in openwrt so I can get more info about the reboot cause? crashlog is what you are looking for. ../o.git/build_dir/linux-lantiq_ar9/linux-3.1.9/patches/generic/930-crashlog.patch Thanks John ... it was already configured and I had a reboot this morning, interestingly though it doesn't actually look like the lantiq driver ... the first backtrace I get once after boot, doesn't seem to be a problem, the second one is the Oops! So is the problem the "eth0: tx ring full"?? <4>[ 20.004000] Infineon CPE API Driver version: DSL CPE API V3.24.4.4 <6>[ 20.144000] ATM (A1) firmware version 1.0.19 <4>[ 20.148000] ifxmips_atm: ATM init succeed <6>[ 20.18] dwc_otg: version 2.60a 22-NOV-2006 <6>[ 20.784000] DWC_otg: Using DMA mode <6>[ 20.784000] dwc_otg dwc_otg.0: DWC OTG Controller <6>[ 20.788000] dwc_otg dwc_otg.0: new USB bus registered, assigned bus number 1 <6>[ 20.796000] dwc_otg dwc_otg.0: irq 62, io mem 0xbe101000 <6>[ 20.804000] DWC_otg: Init: Port Power? op_state=1 <6>[ 20.808000] DWC_otg: Init: Power Port (0) <6>[ 20.812000] hub 1-0:1.0: USB hub found <6>[ 20.816000] hub 1-0:1.0: 1 port detected <6>[ 20.844000] input: gpio-keys-polled as /devices/platform/gpio-keys-polled/input/input0 <4>[ 20.968000] DISCONNECTED PORT <6>[ 22.924000] device eth0 entered promiscuous mode <6>[ 22.976000] br-lan: port 1(eth0) entering forwarding state <6>[ 22.98] br-lan: port 1(eth0) entering forwarding state <6>[ 27.588000] device eth0 left promiscuous mode <6>[ 27.592000] br-lan: port 1(eth0) entering forwarding state <6>[ 27.976000] device eth0 entered promiscuous mode <6>[ 27.98] br-lan: port 1(eth0) entering forwarding state <6>[ 27.984000] br-lan: port 1(eth0) entering forwarding state <3>[ 55.30] [DSL_BSP_Showtime 916]: Datarate US intl = 448000, fast = 0 <4>[ 58.044000] [ cut here ] <4>[ 58.044000] WARNING: at kernel/softirq.c:159 0x80022258() <4>[ 58.044000] Modules linked in: gpio_keys_polled dwc_otg lantiq_atm drv_dsl_cpe_api lantiq_mei ledtrig_usbdev ip6t_REJECT ip6t_LOG ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xt_conntrack xt_CT xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack pppoe pppox pppoatm ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc button_hotplug br2684 atm ath9k ath9k_common ath9k_hw ath mac80211 usbcore nls_base crc_ccitt ipv6 cfg80211 compat arc4 aes_generic crypto_algapi <4>[ 58.044000] Call Trace:[<8022c144>] 0x8022c144 <4>[ 58.044000] [<8022c144>] 0x8022c144 <4>[ 58.044000] [<8001b96c>] 0x8001b96c <4>[ 58.044000] [<80022258>] 0x80022258 <4>[ 58.044000] [<8001b9b0>] 0x8001b9b0 <4>[ 58.044000] [<801943f4>] 0x801943f4 <4>[ 58.044000] [<831c437c>] 0x831c437c <4>[ 58.044000] [<80022258>] 0x80022258 <4>[ 58.044000] [<832e4640>] 0x832e4640 <4>[ 58.044000] [<80015c58>] 0x80015c58 <4>[ 58.044000] [<83281330>] 0x83281330 <4>[ 58.044000] [<8004f370>] 0x8004f370 <4>[ 58.044000] [<800309b8>] 0x800309b8 <4>[ 58.044000] [<8004f5b0>] 0x8004f5b0 <4>[ 58.044000] [<80051784>] 0x80051784 <4>[ 58.044000] [<8004ecf8>] 0x8004ecf8 <4>[ 58.044000] [<800079b4>] 0x800079b4 <4>[ 58.044000] [<800031c8>] 0x800031c8 <4>[ 58.044000] [<80022130>] 0x80022130 <4>[ 58.044000] [<80005ecc>] 0x80005ecc <4>[ 58.044000] [<800060a0>] 0x800060a0 <4>[ 58.044000] [<8001701c>] 0x8001701c <4>[ 58.044000] [<80007a10>] 0x80007a10 <4>[ 58.044000] [<800060c0>] 0x800060c0 <4>[ 58.044000] [<8028e8ec>] 0x8028e8ec <4>[ 58.044000] [<8028e230>] 0x8028e230 <4>[ 58.04
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
please build a kernel with KALLSYMS enable menuconfig -> Global build settings -> Compile the kernel with symbol table information and show us the output again. i assume this is annex-a ?! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
Al 21/02/2012 10:33, En/na lee.es...@nowonline.co.uk ha escrit: Thanks John ... it was already configured and I had a reboot this morning, interestingly though it doesn't actually look like the lantiq driver ... the first backtrace I get once after boot, doesn't seem to be a problem, the second one is the Oops! So is the problem the "eth0: tx ring full"?? I've seen this too once on a different lantiq router, adsl was not connected, I was just running iperf to test the throughput of the wifi adapter. Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
Al 21/02/2012 10:56, En/na John Crispin ha escrit: please build a kernel with KALLSYMS enable Does it work now? Last time I tried it, it didn't work, but it was a while ago http://pastebin.ca/2072861 Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
On 21/02/12 12:13, Luca Olivetti wrote: > Al 21/02/2012 10:56, En/na John Crispin ha escrit: >> please build a kernel with KALLSYMS enable > > Does it work now? > Last time I tried it, it didn't work, but it was a while ago > http://pastebin.ca/2072861 most likely a error your end ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
Al 21/02/2012 12:15, En/na John Crispin ha escrit: On 21/02/12 12:13, Luca Olivetti wrote: Al 21/02/2012 10:56, En/na John Crispin ha escrit: please build a kernel with KALLSYMS enable Does it work now? Last time I tried it, it didn't work, but it was a while ago http://pastebin.ca/2072861 most likely a error your end hints appreciated Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
On 21/02/12 12:36, Luca Olivetti wrote: > Al 21/02/2012 12:15, En/na John Crispin ha escrit: >> On 21/02/12 12:13, Luca Olivetti wrote: >>> Al 21/02/2012 10:56, En/na John Crispin ha escrit: please build a kernel with KALLSYMS enable >>> >>> Does it work now? >>> Last time I tried it, it didn't work, but it was a while ago >>> http://pastebin.ca/2072861 >> >> most likely a error your end > > hints appreciated > > Bye most likely you activated it in kernel_menuconfig and not menuconfig ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
Al 21/02/2012 12:38, En/na John Crispin ha escrit: On 21/02/12 12:36, Luca Olivetti wrote: Al 21/02/2012 12:15, En/na John Crispin ha escrit: On 21/02/12 12:13, Luca Olivetti wrote: Al 21/02/2012 10:56, En/na John Crispin ha escrit: please build a kernel with KALLSYMS enable Does it work now? Last time I tried it, it didn't work, but it was a while ago http://pastebin.ca/2072861 most likely a error your end hints appreciated Bye most likely you activated it in kernel_menuconfig and not menuconfig Thank you, I don't remember how I activated it at the time, but I'll try now with menuconfig. Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
On Tue, 21 Feb 2012 10:56:44 +0100, John Crispin wrote: please build a kernel with KALLSYMS enable menuconfig -> Global build settings -> Compile the kernel with symbol table information and show us the output again. i assume this is annex-a ?! OK, new kernel built and installed ... just waiting for a reboot now, hopefully in the next couple of hours. Yes, it is Annex-A. Regards, Lee. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
On Tue, 21 Feb 2012 12:55:41 +, lee.es...@nowonline.co.uk wrote: OK, new kernel built and installed ... just waiting for a reboot now, hopefully in the next couple of hours. Yes, it is Annex-A. Well, that didn't take long ... full log output below including the initial boot (just in case that helps.) I'm confused that the other two routers aren't seeing the same problem, the only difference I can think of is that this one is the default for locally generated traffic from my load balancer (openwrt also) so it gets a litte more traffic, but it's not a lot mainly just DNS traffic. Lee. Time: 1329832916.194484 Modules:gpio_keys_polled@82c7d000+864 dwc_otg@82c7+cf0f lantiq_atm@833a+c249drv_dsl_cpe_api@833c+1afb6 lantiq_mei@83398000+533bledtrig_usbdev@83393000+854 ip6t_REJECT@8338d000+9d4 ip6t_LOG@83388000+18f4 ip6t_rt@8337f000+5e4ip6t_hbh@83376000+504 ip6t_mh@83384000+2b4 ip6t_ipv6header@83379000+434 ip6t_frag@8338+354 ip6t_eui64@8335b000+2b4 ip6t_ah@8337b000+314 ip6table_raw@83373000+234 ip6_queue@8337a000+fb4 ip6table_mangle@8333+3d4ip6table_filter@8333e000+274 ip6_tables@8337+2606 nf_conntrack_ipv6@8335c000+1064 nf_defrag_ipv6@8334c000+1473 nf_nat_irc@83336000+364nf_conntrack_irc@83353000+a14 nf_nat_ftp@8333d000+424 nf_conntrack_ftp@8335+1234 ipt_MASQUERADE@8334b000+3f4iptable_nat@8334f000+8ba nf_nat@83338000+2894xt_conntrack@8334e000+854 xt_CT@8331f000+5d4 xt_NOTRACK@83317000+254 iptable_raw@8000+274 xt_state@83327000+2b4 nf_conntrack_ipv4@8331e000+fc7 nf_defrag_ipv4@83315000+2c7 nf_conntrack@8334+9e2b pppoe@83324000+2094 pppox@831d1000+4f0 pppoatm@831e3000+974 ipt_REJECT@83311000+724 xt_TCPMSS@831df000+af4 ipt_LOG@8314e000+17a4 xt_comment@830a1000+1d4xt_multiport@8330d000+494 xt_mac@831e2000+254 xt_limit@83309000+594 iptable_mangle@831d9000+374iptable_filter@83245000+2b4 ip_tables@831ec000+2450 xt_tcpudp@831e6000+684 x_tables@831d4000+29a4 ppp_async@83246000+1d44 ppp_generic@83318000+4e88 slhc@8330e000+12c3 button_hotplug@8330a000+ab4 br2684@83302000+18c4atm@831f+933c ath9k@832e+169ed ath9k_common@8313c000+589 ath9k_hw@8328+574b2 ath@83248000+3f8f mac80211@8320+402c7 usbcore@8316+19f87 nls_base@8312a000+12dc crc_ccitt@830b9000+3f4 ipv6@8318+3e3d2 cfg80211@8310+2349e compat@83064000+3f7 arc4@8307a000+344 aes_generic@83088000+75ea crypto_algapi@8308+26b7 0.052000] NET: Registered protocol family 16 <6>[0.064000] MIPS: machine is WBMR <6>[0.084000] bio: create slab at 0 <7>[0.096000] pci :00:0e.0: [168croot=/dev/mtdblock3rorootfstype=squashfsip=192.168.11.1:192.168.11.2eth0:onconsole=ttyS1,115200ethaddr=00:24:A5:BD:37:90phym=64Mmem=64Mpanic=1mtdparts=ifx_nor0:256k(uboot),128k(ubootconfig),1280k(kernel),30336k(rootfs),256k(firmware),128k(user_property),128k(fwdiag),128k(boardcfg),128k(calibration)init=/etc/preinitquiet: set to [mem 0£ð£ðð3£ðC£ðZCI address [0x1800-0x1800]) <6>[0.104000] Switching to clocksource MIPS <6>[0.112000] NET: Registered protocol family 2 <6>[0.116000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) <6>[0.124000] TCP established hash table entries: 2048 (order: 2, 16384 bytes) <6>[0.132000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes) <6>[0.136000] TCP: Hash tables configured (established 2048 bind 2048) <6>[0.144000] TCP reno registered <6>[0.148000] UDP hash table entries: 256 (order: 0, 4096 bytes) <6>[0.152000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) <6>[0.16] NET: Registered protocol family 1 <7>[0.164000] PCI: CLS 0 bytes, default 32 <6>[0.164000] gptu: totally 6 16-bit timers/counters <6>[0.168000] gptu: misc_register on minor 63 <6>[0.172000] gptu: succeeded to request irq 126 <6>[0.18] gptu: succeeded to request irq 127 <6>[0.184000] gptu: succeeded to request irq 128 <6>[0.188000] gptu: succeeded to request irq 129 <6>[0.192000] gptu: succeeded to request irq 130 <6>[0.196000] gptu: succeeded to request irq 131 <6>[0.204000] squashfs: version 4.0 (2009/01/31) Phillip Lougher <6>[0.212000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. <6>[0.224000] msgmni has been set to 120 <6>[0.224000] io scheduler noop registered <6>[0.228000] io scheduler deadline registered (default) <6>[0.236000] ltq_asc.0: ttyLTQ0 at MMIO 0x1e100400 (irq = 104) is a ltq_asc <6>[0.244000] ltq_asc.1: ttyLTQ1 at MMIO 0x1e100c00 (irq = 112) is a ltq_asc <6>[0.252000] console [ttyLTQ1] enabled, bootconsole disabled <6>[0.264000] ltq_nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0xc2 Chip ID 0x0
Re: [OpenWrt-Devel] Frequent reboot WBMR & Lantiq
Al 21/02/12 13:29, En/na Luca Olivetti ha escrit: > Al 21/02/2012 12:38, En/na John Crispin ha escrit: >> On 21/02/12 12:36, Luca Olivetti wrote: >>> Al 21/02/2012 12:15, En/na John Crispin ha escrit: On 21/02/12 12:13, Luca Olivetti wrote: > Al 21/02/2012 10:56, En/na John Crispin ha escrit: >> please build a kernel with KALLSYMS enable > > Does it work now? > Last time I tried it, it didn't work, but it was a while ago > http://pastebin.ca/2072861 most likely a error your end >>> >>> hints appreciated >>> >>> Bye >> >> >> most likely you activated it in kernel_menuconfig and not menuconfig > > Thank you, I don't remember how I activated it at the time, but I'll try now > with menuconfig. I tried and I had the exact same crash, then I tried with a make dirclean before make, and it doesn't crash now. Is there a way to avoid rebuilding everything? Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
