RC 2.2 crash on Asus eepc



  • I upgraded one of my full install PC few thousand miles away from 2.1.5 to 2.2 and after around 30 mins or so it crashed and would keep rebooting until the web GUI stopped working and kept saying service unavailable. This machine has a single gigabit nic and I use multiple vlans for LAN and wan. I submitted the crash report around 2-3 times so can anyone look into it what's causing this, the report was to large to post here and out of deaspiration I had to revert to 2.1.5 as this machine was a production one and too far to be able to reach locally.



  • same problem?

    After the restart operation

    Trying to mount root from ufs:/dev/ada0s1a [rw]…
    WARNING: / was not properly dismounted


  • Rebel Alliance Developer Netgate

    In order to track down the crash report we need to know the IP address from which it was submitted and the approximate time.



  • well that machines uses 2 static ip addresses so can i PM it to u?



  • after the upgrade it worked all fine for around 20mins and then crashed and rebooted, since then the web gui stopped working so i did a clean install and restore the config and then after 20mins again it crashed

    time would be between 7:30 PM to 10 PM Indian standard time, 10th Jan



  • 117.218.167.x - default gateway - would have come from this
    116.74.97.x - secondary wan link, if not above then would have come from this


  • Rebel Alliance Developer Netgate

    I don't show any submitted reports from any IP near either of those blocks, unfortunately.
    Could it have submitted over IPv6? You can PM me just the IP. It would be the IP on the default gateway interface.



  • PM sent, ipv6 is not enabled on pfsense or isp so thats not possible, i submitted the report 2-3 times and each time it said sending and sent and then the link to delete it from system.

    what i remember was the crash report said something about the HDD on ada0s1a or something like that and then a huge report with things at the end with something that said sockbuffer or something like that. I would guess it would be the nic or something relating to the HDD, although the HDD works fine now once reverted to 2.1.5.

    dmesg on 2.1.5 says the below and working all good on same hardware from past 2 years or so

    $ dmesg
    Copyright (c) 1992-2012 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    	The Regents of the University of California. All rights reserved.
    FreeBSD is a registered trademark of The FreeBSD Foundation.
    FreeBSD 8.3-RELEASE-p16 #0: Mon Aug 25 08:25:41 EDT 2014
        root@pf2_1_1_i386.pfsense.org:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: Intel(R) Atom(TM) CPU N270   @ 1.60GHz (1608.02-MHz 686-class CPU)
      Origin = "GenuineIntel"  Id = 0x106c2  Family = 6  Model = 1c  Stepping = 2
      Features=0xbfe9fbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x40c39d <sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,xtpr,pdcm,movbe>AMD Features=0x100000 <nx>AMD Features2=0x1 <lahf>TSC: P-state invariant
    real memory  = 2147483648 (2048 MB)
    avail memory = 2073751552 (1977 MB)
    ACPI APIC Table: <a_m_i_ oemapic="">
    FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
    FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads
     cpu0 (BSP): APIC ID:  0
     cpu1 (AP/HT): APIC ID:  1
    ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000820/0x0 (20101013/tbfadt-655)
    ACPI Warning: Invalid length for Pm2ControlBlock: 0, using default 8 (20101013/tbfadt-707)
    ioapic0: Changing APIC ID to 2
    ioapic0 <version 2.0=""> irqs 0-23 on motherboard
    wlan: mac acl policy registered
    ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_bss_fw, 0xc07c1560, 0) error 1
    ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc07c1600, 0) error 1
    ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc07c16a0, 0) error 1
    kbd1 at kbdmux0
    cryptosoft0: <software crypto=""> on motherboard
    padlock0: No ACE support.
    acpi0: <a_m_i_ oemrsdt=""> on motherboard
    acpi0: [ITHREAD]
    acpi0: Power Button (fixed)
    acpi0: reservation of 0, a0000 (3) failed
    acpi0: reservation of 100000, 7f700000 (3) failed
    Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
    acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
    cpu0: <acpi cpu=""> on acpi0
    cpu1: <acpi cpu=""> on acpi0
    pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0
    pci0: <acpi pci="" bus=""> on pcib0
    vgapci0: <vga-compatible display=""> port 0xec80-0xec87 mem 0xfeb80000-0xfebfffff,0xd0000000-0xdfffffff,0xfeb40000-0xfeb7ffff irq 16 at device 2.0 on pci0
    agp0: <intel 945gme="" svga="" controller=""> on vgapci0
    agp0: aperture size is 256M, detected 7932k stolen memory
    vgapci1: <vga-compatible display=""> mem 0xfea80000-0xfeafffff at device 2.1 on pci0
    pci0: <multimedia, hda=""> at device 27.0 (no driver attached)
    pcib1: <acpi pci-pci="" bridge=""> irq 16 at device 28.0 on pci0
    pci4: <acpi pci="" bus=""> on pcib1
    re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" pcie="" gigabit="" ethernet=""> port 0xdc00-0xdcff mem 0xfe8ff000-0xfe8fffff,0xbfef0000-0xbfefffff irq 16 at device 0.0 on pci4
    re0: Using 1 MSI-X message
    re0: Chip rev. 0x3c000000
    re0: MAC rev. 0x00400000
    miibus0: <mii bus=""> on re0
    rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface=""> PHY 1 on miibus0
    rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
    re0: [ITHREAD]
    pcib2: <acpi pci-pci="" bridge=""> irq 17 at device 28.1 on pci0
    pci3: <acpi pci="" bus=""> on pcib2
    pci3: <network> at device 0.0 (no driver attached)
    pcib3: <acpi pci-pci="" bridge=""> irq 18 at device 28.2 on pci0
    pci1: <acpi pci="" bus=""> on pcib3
    uhci0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a=""> port 0xe480-0xe49f irq 23 at device 29.0 on pci0
    uhci0: [ITHREAD]
    uhci0: LegSup = 0x2f00
    usbus0: <intel 82801g="" (ich7)="" usb="" controller="" usb-a=""> on uhci0
    uhci1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b=""> port 0xe800-0xe81f irq 19 at device 29.1 on pci0
    uhci1: [ITHREAD]
    uhci1: LegSup = 0x2f00
    usbus1: <intel 82801g="" (ich7)="" usb="" controller="" usb-b=""> on uhci1
    uhci2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c=""> port 0xe880-0xe89f irq 18 at device 29.2 on pci0
    uhci2: [ITHREAD]
    uhci2: LegSup = 0x2f00
    usbus2: <intel 82801g="" (ich7)="" usb="" controller="" usb-c=""> on uhci2
    uhci3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d=""> port 0xec00-0xec1f irq 16 at device 29.3 on pci0
    uhci3: [ITHREAD]
    uhci3: LegSup = 0x2f00
    usbus3: <intel 82801g="" (ich7)="" usb="" controller="" usb-d=""> on uhci3
    ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller=""> mem 0xfeb3fc00-0xfeb3ffff irq 23 at device 29.7 on pci0
    ehci0: [ITHREAD]
    usbus4: EHCI version 1.0
    usbus4: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller=""> on ehci0
    pcib4: <acpi pci-pci="" bridge=""> at device 30.0 on pci0
    pci5: <acpi pci="" bus=""> on pcib4
    isab0: <pci-isa bridge=""> at device 31.0 on pci0
    isa0: <isa bus=""> on isab0
    atapci0: <intel ich7m="" sata150="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.2 on pci0
    ata0: <ata channel=""> at channel 0 on atapci0
    ata0: [ITHREAD]
    ata1: <ata channel=""> at channel 1 on atapci0
    ata1: [ITHREAD]
    pci0: <serial bus,="" smbus=""> at device 31.3 (no driver attached)
    acpi_button0: <power button=""> on acpi0
    atrtc0: <at realtime="" clock=""> port 0x70-0x71 irq 8 on acpi0
    acpi_hpet0: <high precision="" event="" timer=""> iomem 0xfed00000-0xfed003ff on acpi0
    Timecounter "HPET" frequency 14318180 Hz quality 900
    pmtimer0 on isa0
    sc0: <system console=""> at flags 0x100 on isa0
    sc0: VGA <16 virtual consoles, flags=0x300>
    vga0: <generic isa="" vga=""> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    atkbdc0: <keyboard controller="" (i8042)=""> at port 0x60,0x64 on isa0
    atkbd0: <at keyboard=""> irq 1 on atkbdc0
    kbd0 at atkbd0
    atkbd0: [GIANT-LOCKED]
    atkbd0: [ITHREAD]
    ppc0: parallel port not found.
    est0: <enhanced speedstep="" frequency="" control=""> on cpu0
    p4tcc0: <cpu frequency="" thermal="" control=""> on cpu0
    est1: <enhanced speedstep="" frequency="" control=""> on cpu1
    p4tcc1: <cpu frequency="" thermal="" control=""> on cpu1
    Timecounters tick every 1.000 msec
    IPsec: Initialized Security Association Processing.
    usbus0: 12Mbps Full Speed USB v1.0
    usbus1: 12Mbps Full Speed USB v1.0
    usbus2: 12Mbps Full Speed USB v1.0
    usbus3: 12Mbps Full Speed USB v1.0
    usbus4: 480Mbps High Speed USB v2.0
    ad0: 152627MB <seagate st9160310as="" 0303=""> at ata0-master UDMA100 SATA
    ugen0.1: <intel> at usbus0
    uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
    ugen1.1: <intel> at usbus1
    uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus1
    ugen2.1: <intel> at usbus2
    uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus2
    ugen3.1: <intel> at usbus3
    uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus3
    ugen4.1: <intel> at usbus4
    uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus4
    uhub0: 2 ports with 2 removable, self powered
    uhub1: 2 ports with 2 removable, self powered
    uhub2: 2 ports with 2 removable, self powered
    uhub3: 2 ports with 2 removable, self powered
    uhub4: 8 ports with 8 removable, self powered
    ugen0.2: <vendor 0x04d9=""> at usbus0
    ukbd0: <vendor 0="" 2="" 0x04d9="" usb="" keyboard,="" class="" 0,="" rev="" 1.10="" 3.10,="" addr=""> on usbus0
    kbd2 at ukbd0
    ugen4.2: <generic> at usbus4
    umass0: <bulk-in, bulk-out,="" interface=""> on usbus4
    umass0:  SCSI over Bulk-Only; quirks = 0x4000
    umass0:0:0:-1: Attached to scbus0
    (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
    (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
    (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
    (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
    uhid0: <vendor 0="" 2="" 0x04d9="" usb="" keyboard,="" class="" 0,="" rev="" 1.10="" 3.10,="" addr=""> on usbus0
    da0 at umass-sim0 bus 0 scbus0 target 0 lun 0SMP: AP CPU #1 Launched!
    da0: 
     <generic- multi-card="" 1.00="">Removable Direct Access SCSI-0 device 
    da0: 40.000MB/s transfers
    da0: Attempt to query device size failed: NOT READY, Medium not present
    Trying to mount root from ufs:/dev/ad0s1a
    ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable,
                add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
    ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
                 Consider tuning vm.kmem_size and vm.kmem_size_max
                 in /boot/loader.conf.
    ZFS filesystem version 5
    ZFS storage pool version 28
    coretemp0: <cpu on-die="" thermal="" sensors=""> on cpu0
    coretemp1: <cpu on-die="" thermal="" sensors=""> on cpu1
    ng0: changing name to 'pppoe1'
    re0: link state changed to UP
    re0_vlan50: link state changed to UP
    re0_vlan20: link state changed to UP
    re0_vlan40: link state changed to UP
    re0_vlan10: link state changed to UP
    re0_vlan30: link state changed to UP
    pflog0: promiscuous mode enabled
    ugen0.2: <vendor 0x04d9=""> at usbus0 (disconnected)
    ukbd0: at uhub0, port 1, addr 2 (disconnected)
    uhid0: at uhub0, port 1, addr 2 (disconnected)</vendor></cpu></cpu></generic-></vendor></bulk-in,></generic></vendor></vendor></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></seagate></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></high></at></power></serial></ata></ata></intel></isa></pci-isa></acpi></acpi></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></acpi></acpi></network></acpi></acpi></rtl8169s></mii></realtek></acpi></acpi></multimedia,></vga-compatible></intel></vga-compatible></acpi></acpi></acpi></acpi></a_m_i_></software></version></a_m_i_></lahf></nx></sse3,dtes64,mon,ds_cpl,est,tm2,ssse3,xtpr,pdcm,movbe></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>
    

  • Rebel Alliance Developer Netgate

    Hmm, still nothing on the crash reporter server from those IP Addresses.

    Did you happen to copy/paste and save the report locally somewhere?

    The knobs to disable DMA and write caching changed between 2.1.x and 2.2 so it's possible if you had something tweaked in loader.conf/loader.conf.local for that it wouldn't have carried over.

    https://doc.pfsense.org/index.php/Boot_Troubleshooting#pfSense_2.2_and_later



  • Well I didn't change anything in the loader conf and sorry but I didn't copy paste the report as it was a production system with few web servers running so I had to get it running asap. If you didn't get the report then I guess it would be network related because dhcp server also stopped working at that time as well as ssh and web GUI.

    Let me see if I can try once more and get you the report.



  • there is nothing custom in the loader.conf but in the system tunable section i noticed these 3 custom values

    hw.ata.wc = 0
    
    hw.usb.no_shutdown_wait = 1
    
    vfs.read_max  = 128
    

    i never had any DMA related errors on 2.1.5 so im assuming it wouldnt cause issues on 2.2 as well



  • I have a Jetway Atom-D525-based board that has trouble with FreeBSD 10.1 (and thus pfSense 2.2) but is working fine on FreeBSD 8.3 pfSense 2.1.5. There are some things that changed around FreeBSD 9.? and for some hardware there seem to be regressions (or just simply that some new driver subsystem that was "swapped-in" to FreeBSD does not work well with all older hardware).

    I doubt you are in a position to do it, but trying FreeBSD 8.3, 9.* and 10.1 on the Asus EeePC will show if it works or not.



  • well im not that good with freebsd as well as this box is in a remote location and in production so i guess im not able to test the different freebsd versions but i can manage to get hold of a similar hardware and provide remote access if anyone needs to test a few things.

    2.1.5 works all good on this box and so did older versions.


  • Rebel Alliance Developer Netgate

    The write cache tunable (hw.ata.wc) was renamed to kern.cam.ada.write_cache, so try changing that to kern.cam.ada.write_cache=0



  • the reason i used to use that was at times due to power failure things used to go corrupt but do u think that can be the cause of a crash after few mins and not right away.

    i mean there was no power failure and it upgraded also just fine and was working all good then crashes and reboots


  • Rebel Alliance Developer Netgate

    It's difficult to say for sure. DMA is more likely, if it's disk related. Not enough information to go by though.



  • ok give me some time, during idle time ill try and recreate the crash and get u the report.

    any tunable to disable DMA and test?


Log in to reply