Crash on Soerkis net6501



  • Hello,

    I don't know if my topic is appropriate here.

    My pfSense installation is crashing on a Soekris net6501. It is a kernel issue. I have redirected syslog message to an external syslog server. The crash occured at 13:27 and the gateway was restarted at 13:57.  Here are the logs :

    2013-07-18 13:57:13 info routeur daemon ppp [opt7] IPCP: state change Ack-Sent –> Opened
    2013-07-18 13:57:13 info routeur daemon ppp [opt7] IPADDR 92.156.241.103
    2013-07-18 13:57:13 info routeur daemon ppp [opt7] IPCP: rec'd Configure Ack #3 (Ack-Sent)
    2013-07-18 13:57:13 info routeur daemon ppp [opt7] IPCP: rec'd Configure Ack #3 (Ack-Sent)
    2013-07-18 13:27:05 crit routeur kern kernel = DP
    2013-07-18 13:27:05 crit routeur kern kernel code segment = base 0x0, limit 0xfffff, type 0x1b
    2013-07-18 13:27:05 crit routeur kern kernel frame pointer = 0x28:0xc5606a80
    2013-07-18 13:27:05 crit routeur kern kernel stack pointer = 0x28:0xc5606a80
    2013-07-18 13:27:05 crit routeur kern kernel instruction pointer = 0x20:0xc09ca708
    2013-07-18 13:27:05 crit routeur kern kernel ot present
    2013-07-18 13:27:05 crit routeur kern kernel fault code = supervisor read, page n
    2013-07-18 13:27:05 crit routeur kern kernel fault virtual address = 0x182
    2013-07-18 13:27:05 crit routeur kern kernel cpuid = 0; apic id = 00
    2013-07-18 13:27:05 crit routeur kern kernel Fatal trap 12: page fault while in kernel mode
    2013-07-18 13:27:05 crit routeur kern kernel ata2: hardware reset timeout
    2013-07-18 13:27:05 crit routeur kern kernel fd = 00000080
    2013-07-18 13:27:04 crit routeur kern kernel t
    2013-07-18 13:27:04 crit routeur kern kernel ata2: port is not ready (timeout 10000ms)
    2013-07-18 13:27:02 err routeur user apinger ALARM: WAN1(193.253.160.3) *** down ***
    2013-07-18 13:27:02 err routeur user apinger ALARM: WAN2(8.8.8.8) *** down ***
    2013-07-18 13:26:56 crit routeur kern kernel g_vfs_done():ad4s1a[WRITE(offset=192856064, length=16384)]error = 6
    2013-07-18 13:26:56 crit routeur kern kernel g_vfs_done():ad4s1a[WRITE(offset=192856064, length=16384)]error = 6
    [

    removed similar messages

    ]
    2013-07-18 13:26:42 crit routeur kern kernel g_vfs_dkone():ad4s1a[WRITE(offset=6144000, length=2048)]error = 6
    2013-07-18 13:26:42 crit routeur kern kernel ng_vfs_done():ad4s1a[WRITE(offset=65536, length=2048)]error = 6
    2013-07-18 13:26:42 crit routeur kern kernel g_vfs_done():ad4s1a[WRITE(offset=199290880, length=2048)]uerror = 6
    2013-07-18 13:26:42 crit routeur kern kernel ata2: hardware reset timeout
    2013-07-18 13:26:42 crit routeur kern kernel ata2: port is not ready (timeout 10000ms) tfd = 00000080
    2013-07-18 13:26:40 err routeur user apinger ALARM: WAN2(8.8.8.8) *** down ***
    2013-07-18 13:25:50 warning routeur user php : MONITOR: WAN1 has packet loss, removing from routing group
    2013-07-18 13:25:50 warning routeur user php : MONITOR: WAN1 has packet loss, removing from routing group
    2013-07-18 13:25:47 notice routeur user check_reload_status Reloading filter
    2013-07-18 13:25:37 err routeur user apinger ALARM: WAN1(193.253.160.3) *** loss ***
    2013-07-18 13:25:36 debug routeur user ps NSSWITCH(_nsdispatch): nis, passwd_compat, setpwent, not found, and no fallback provided
    2013-07-18 13:25:11 info routeur local7 dhcpd DHCPACK to 192.168.0.116 (00:25:22:5f:a9:70) via bridge0
    2013-07-18 13:25:11 info routeur local7 dhcpd DHCPINFORM from 192.168.0.116 via bridge0

    I am using 2.0.3-RELEASE (i386) built on Fri Apr 12 10:22:57 EDT 2013 FreeBSD 8.1-RELEASE-p13

    Do you think it is a hardware issue ?

    Regards.

    Éric



  • Some update :

    I am using net6501-70 with 2018 MB memory and a mSata (ad4: 3825MB <kingspec 120202="" ksm-msata.5-004sj="">at ata2-master UDMA100 SATA 3Gb/s).

    My /boot/loader.conf file content is :
    autoboot_delay="3"
    vm.kmem_size="435544320"
    vm.kmem_size_max="535544320"
    kern.ipc.nmbclusters="0"

    Does it worth increasing vm.kmem_size and vm.kmem_size_max ?

    Éric</kingspec>



  • @ebo2002fr:

    Does it worth increasing vm.kmem_size and vm.kmem_size_max ?

    Not likely.

    @ebo2002fr:

    Do you think it is a hardware issue ?

    Yes, your "hard drive" shouldn't be causing:
    @ebo2002fr:

    2013-07-18  13:27:05  crit  routeur  kern  kernel  ata2: hardware reset timeout
    2013-07-18  13:27:04  crit  routeur  kern  kernel  ata2: port is not ready (timeout 10000ms)
    2013-07-18 13:26:56 crit routeur kern kernel g_vfs_done():ad4s1a[WRITE(offset=192856064, length=16384)]error = 6
    2013-07-18 13:26:56 crit routeur kern kernel g_vfs_done():ad4s1a[WRITE(offset=192856064, length=16384)]error = 6
    2013-07-18 13:26:42 crit routeur kern kernel g_vfs_dkone():ad4s1a[WRITE(offset=6144000, length=2048)]error = 6
    2013-07-18 13:26:42 crit routeur kern kernel ng_vfs_done():ad4s1a[WRITE(offset=65536, length=2048)]error = 6
    2013-07-18 13:26:42 crit routeur kern kernel g_vfs_done():ad4s1a[WRITE(offset=199290880, length=2048)]uerror = 6
    2013-07-18 13:26:42 crit routeur kern kernel ata2: hardware reset timeout
    2013-07-18 13:26:42 crit routeur kern kernel ata2: port is not ready (timeout 10000ms) tfd = 00000080