|
||||||||||
I'm running WRAP. Image 1.22. Have no idea how to test the hardware, besides POST card.... Im attaching log file, but as to me it doesn't have any error, besides strange time and battery error (wrap doesn't have battery) ---------------------------------------------------------------------------- Jan 1 00:00:18 /kernel: atapci0: <Generic PCI ATA controller> port 0xfc00-0xfc0f at device 18.2 on pci0 Jan 1 00:00:18 /kernel: ata0: at 0x1f0 irq 14 on atapci0 Jan 1 00:00:18 /kernel: pci0: <unknown card> (vendor=0x100b, dev=0x0503) at 18.3 Jan 1 00:00:18 /kernel: chip2: <PCI to Other bridge (vendor=100b device=0515)> port 0xf200-0xf23f at device 18.5 on pci0 Jan 1 00:00:18 /kernel: orm0: <Option ROM> at iomem 0xe0000-0xe7fff on isa0 Jan 1 00:00:18 /kernel: pmtimer0 on isa0 Jan 1 00:00:18 /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0 Jan 1 00:00:18 /kernel: sio0: type 16550A, console Jan 1 00:00:18 /kernel: RTC BIOS diagnostic error 80<clock_battery> Jan 1 00:00:18 /kernel: BRIDGE 020214 loaded Jan 1 00:00:18 /kernel: IPsec: Initialized Security Association Processing. Jan 1 00:00:18 /kernel: IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled Jan 1 00:00:18 /kernel: ad0: 122MB <Hitachi XX.V.3.4.0.0> [978/8/32] at ata0-master PIO4 Jan 1 00:00:18 /kernel: Mounting root from ufs:/dev/md0c Jan 1 00:00:18 dnsmasq[93]: started, version 2.27 cachesize 150 Jan 1 00:00:18 dnsmasq[93]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N Jan 1 00:00:18 dhcpd: Internet Systems Consortium DHCP Server V3.0.3 Jan 1 00:00:18 dnsmasq[93]: setting --bind-interfaces option because of OS limitations Jan 1 00:00:18 dnsmasq[93]: setting --bind-interfaces option because of OS limitations Jan 1 00:00:18 dhcpd: Copyright 2004-2005 Internet Systems Consortium. Jan 1 00:00:18 dnsmasq[93]: read /etc/hosts - 4 addresses Jan 1 00:00:18 dhcpd: All rights reserved. Jan 1 00:00:18 dnsmasq[93]: reading /etc/resolv.conf Jan 1 00:00:18 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Jan 1 00:00:19 /kernel: ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to accept, logging disabled Jan 1 00:00:19 dhclient: DHCPOFFER from 192.168.0.1 Jan 1 00:00:19 dhclient: DHCPREQUEST on sis1 to 255.255.255.255 port 67 Jan 1 00:00:19 dhclient: DHCPACK from 192.168.0.1 Jan 1 00:00:19 dhclient: New Network Number: 192.168.0.0 Jan 1 00:00:19 dhclient: New Broadcast Address: 192.168.0.255 Jan 1 00:00:20 dhclient: New IP Address (sis1): 192.168.0.102 Jan 1 00:00:20 dhclient: New Subnet Mask (sis1): 255.255.255.0 Jan 1 00:00:20 dhclient: New Broadcast Address (sis1): 192.168.0.255 Jan 1 00:00:20 dhclient: New Routers: 192.168.0.1 Jan 1 00:00:25 dhclient: bound to 192.168.0.102 -- renewal in 293847 seconds. Aug 21 03:43:33 dhclient: DHCPDISCOVER on sis1 to 255.255.255.255 port 67 interval 3 Aug 21 03:43:33 dhclient: DHCPOFFER from 192.168.0.1 Aug 21 03:43:33 dhclient: DHCPREQUEST on sis1 to 255.255.255.255 port 67 Aug 21 03:43:33 dhclient: DHCPACK from 192.168.0.1 Aug 21 03:43:34 dhclient: New Network Number: 192.168.0.0 Aug 21 03:43:34 dhclient: New Broadcast Address: 192.168.0.255 Aug 21 03:43:34 dhclient: New IP Address (sis1): 192.168.0.102 Aug 21 03:43:34 dhclient: New Subnet Mask (sis1): 255.255.255.0 Aug 21 03:43:34 dhclient: New Broadcast Address (sis1): 192.168.0.255 Aug 21 03:43:34 dhclient: New Routers: 192.168.0.1 Aug 21 03:43:34 dnsmasq[93]: reading /etc/resolv.conf Aug 21 03:43:34 dnsmasq[93]: using nameserver 192.168.0.1#53 Aug 21 03:43:37 dhclient: bound to 192.168.0.102 -- renewal in 285450 seconds. Aug 21 03:43:44 dnsmasq[93]: reading /etc/resolv.conf Aug 21 03:43:44 dnsmasq[93]: using nameserver 192.168.0.1#53 -----Original Message----- From: Lee Sharp [mailto:leesharp at hal dash pc dot org] Sent: Monday, August 21, 2006 11:31 AM To: m0n0wall at lists dot m0n0 dot ch Subject: Re: [m0n0wall] Debugin Mono Crash? How to DEBUG? On Sun, 20 Aug 2006 23:46:18 -0400 "Alex M" <radiussupport at lrcommunications dot net> wrote: > My mono just crashed, how can I debug what and why that happened? More detail helps. What hardware? Did you look at the console? What failed? If it was a failure, I would try the ultimate boot CD and run the memory tests first to make sure the hardware is solid. If that is not it, post details here. --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch |