Jetway J7F4K1G2ES reboots every 12 hours on 1.2.3-RELEASE
-
So I ordered a JetWay J7F4K1G2ES (VIA C7 1.2Ghz) with dual Realtek Gigabit interfaces. The system was running well but it's been rebooting randomly every 12 hours. I am trying to figure out if this is a hardware problem or a FreeBSD 7.2 related driver issue. Here is the dmesg:
Copyright
1992-2009 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 7.2-RELEASE-p5 #0: Mon Dec 7 20:20:43 EST 2009
sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.7.i386
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: VIA Eden Processor 1200MHz (1200.01-MHz 686-class CPU)
Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0
Features=0xa7c9baff <fpu,vme,de,pse,tsc,msr,pae,mce,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>Features2=0x4181 <sse3,est,tm2,xtpr>VIA Padlock Features=0xffcc <rng,aes,aes-ctr,sha1,sha256,rsa>real memory = 518914048 (494 MB)
avail memory = 493891584 (471 MB)
ACPI APIC Table: <cn700 awrdacpi="">ioapic0 <version 0.3="">irqs 0-23 on motherboard
wlan: mac acl policy registered
cryptosoft0: <software crypto="">on motherboard
padlock0: <aes-cbc,sha1,sha256>on motherboard
acpi0: <cn700 awrdacpi="">on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 1ede0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_button0: <power button="">on acpi0
pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
pci0: <acpi pci="" bus="">on pcib0
pcib1: <pci-pci bridge="">at device 1.0 on pci0
pci1: <pci bus="">on pcib1
vgapci0: <vga-compatible display="">mem 0xf4000000-0xf7ffffff,0xfb000000-0xfbffffff irq 16 at device 0.0 on pci1
re0: <realtek 8169sc="" 8110sc="" single-chip="" gigabit="" ethernet="">port 0xf600-0xf6ff mem 0xfdfff000-0xfdfff0ff irq 18 at device 9.0 on pci0
re0: Chip rev. 0x18000000
re0: MAC rev. 0x00000000
miibus0: <mii bus="">on re0
rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
re0: Ethernet address: 00:30:18:a8:86:46
re0: [FILTER]
re1: <realtek 8169sc="" 8110sc="" single-chip="" gigabit="" ethernet="">port 0xf800-0xf8ff mem 0xfdffe000-0xfdffe0ff irq 19 at device 11.0 on pci0
re1: Chip rev. 0x18000000
re1: MAC rev. 0x00000000
miibus1: <mii bus="">on re1
rgephy1: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus1
rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
re1: Ethernet address: 00:30:18:a8:86:47
re1: [FILTER]
atapci0: <via 8237="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.0 on pci0
ata0: <ata 0="" channel="">on atapci0
ata0: [ITHREAD]
ata1: <ata 1="" channel="">on atapci0
ata1: [ITHREAD]
isab0: <pci-isa bridge="">at device 17.0 on pci0
isa0: <isa bus="">on isab0
acpi_tz0: <thermal zone="">on acpi0
speaker0: <pc speaker="">port 0x61 on acpi0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A, console
sio0: [FILTER]
cpu0: <acpi cpu="">on acpi0
acpi_perf0: <acpi cpu="" frequency="" control="">on cpu0
acpi_throttle0: <acpi cpu="" throttling="">on cpu0
orm0: <isa option="" rom="">at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0
ppc0: parallel port not found.
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
Timecounter "TSC" frequency 1200013147 Hz quality 800
Timecounters tick every 10.000 msec
IPsec: Initialized Security Association Processing.
ad0: 3847MB <cf card="" 4gb="" ver2.19k="">at ata0-master PIO4
WARNING: Expected rawoffset 0, found 63
WARNING: Expected rawoffset 0, found 63
Trying to mount root from ufs:/dev/ufs/pfsense0
pflog0: promiscuous mode enabled
re1: link state changed to UPSo after about 12-14 hours of uptime I get this:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0a4a709
stack pointer = 0x28:0xc2e2a8c8
frame pointer = 0x28:0xc2e2a8dc
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 14 (swi5: +)
trap number = 12
panic: page fault
Uptime: 14h27m57s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting…I tried swapping the 1 Gig module with another 512mb module I had and it did the same thing.
I'm about ready to RMA this whole thing and get an alix board.
Please advise if you have any clues.
Thanks!</cf></isa></acpi></acpi></acpi></pc></thermal></isa></pci-isa></ata></ata></via></rtl8169s></mii></realtek></rtl8169s></mii></realtek></vga-compatible></pci></pci-pci></acpi></acpi></power></cn700></aes-cbc,sha1,sha256></software></version></cn700 ></rng,aes,aes-ctr,sha1,sha256,rsa></sse3,est,tm2,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>
-
I noticed another thread now that all VIA based systems seem to be rebooting with 1.2.3. For what it's worth, I have a permanent IPSec tunnel running from my home to my colo using AES. This would most likely use the padlock driver since I never see the warning about IPSec using the software random number generator. I will try an older build tonight to see if that helps at all.
-
Hey guys I just had a thought. Should us VIA Padlock users be disabling the glxsb KLD?
Please advise.
Thanks!
-
Is it too late to say friends don't let friends run VIA? ;D
-
Is it too late to say friends don't let friends run VIA? ;D
I ended up RMA'ing the board and ordered a netgate alix kit instead. Uptime is already 2.5 days and it's just as fast as the VIA box was. :)
-
I'm running a Via board here, J7F41G2.
DO NOT use REALTEK onboard NIC's. (they don't play nice with padlock code!, even with other OS-es)
I use a dual intel nic pci-x card.
Uptime : 72 days, 14:34 and counting…Copyright (c) 1992-2009 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 7.2-RELEASE-p5 #0: Sun Dec 6 22:57:48 EST 2009 sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: VIA Esther processor 1200MHz (1200.01-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x6a9 Stepping = 9 Features=0xa7c9baff <fpu,vme,de,pse,tsc,msr,pae,mce,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>Features2=0x181 <sse3,est,tm2>VIA Padlock Features=0x3fcc <rng,aes,aes-ctr,sha1,sha256,rsa>real memory = 1055784960 (1006 MB) avail memory = 1019252736 (972 MB) ACPI APIC Table: <cn700 awrdacpi=""> ioapic0 <version 0.3=""> irqs 0-23 on motherboard wlan: mac acl policy registered kbd1 at kbdmux0 cryptosoft0: <software crypto=""> on motherboard padlock0: <aes-cbc,sha1,sha256> on motherboard acpi0: <cn700 awrdacpi=""> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3ede0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_hpet0: <high precision="" event="" timer=""> iomem 0xfe800000-0xfe8003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 acpi_button0: <power button=""> on acpi0 pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0 pci0: <acpi pci="" bus=""> on pcib0 pcib1: <pci-pci bridge=""> at device 1.0 on pci0 pci1: <pci bus=""> on pcib1 vgapci0: <vga-compatible display=""> mem 0xf4000000-0xf7ffffff,0xfb000000-0xfbffffff irq 16 at device 0.0 on pci1 em0: <intel(r) 1000="" pro="" network="" connection="" 6.9.6=""> port 0xff00-0xff3f mem 0xfdfc0000-0xfdfdffff,0xfdf40000-0xfdf7ffff irq 17 at device 8.0 on pci0 em0: [FILTER] em0: Ethernet address: 00:1b:21:2b:6f:00 em1: <intel(r) 1000="" pro="" network="" connection="" 6.9.6=""> port 0xfe00-0xfe3f mem 0xfdfa0000-0xfdfbffff,0xfdf00000-0xfdf3ffff irq 18 at device 8.1 on pci0 em1: [FILTER] em1: Ethernet address: 00:1b:21:2b:6f:01 atapci0: <via 8237="" udma133="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 15.0 on pci0 ata0: <ata 0="" channel=""> on atapci0 ata0: [ITHREAD] ata1: <ata 1="" channel=""> on atapci0 ata1: [ITHREAD] isab0: <pci-isa bridge=""> at device 17.0 on pci0 isa0: <isa bus=""> on isab0 acpi_tz0: <thermal zone=""> on acpi0 speaker0: <pc speaker=""> port 0x61 on acpi0 atkbdc0: <keyboard controller="" (i8042)=""> port 0x60,0x64 irq 1 on acpi0 atkbd0: <at keyboard=""> irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] cpu0: <acpi cpu=""> on acpi0 est0: <enhanced speedstep="" frequency="" control=""> on cpu0 p4tcc0: <cpu frequency="" thermal="" control=""> on cpu0 acpi_hpet0: <high precision="" event="" timer=""> iomem 0xfe800000-0xfe8003ff on acpi0 device_attach: acpi_hpet0 attach returned 12 pmtimer0 on isa0 orm0: <isa option="" rom=""> at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0 sc0: <system console=""> at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: <generic isa="" vga=""> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1200007247 Hz quality 800 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 14324MB <wdc wd150bb-60bna1="" 18.20d18=""> at ata0-master UDMA33 acd0: CDROM <cd-rom 52x="" akh="" a64=""> at ata0-slave UDMA33 WARNING: Expected rawoffset 0, found 63 Trying to mount root from ufs:/dev/ad0s1a pflog0: promiscuous mode enabled</cd-rom></wdc></generic></system></isa></high></cpu></enhanced></acpi></at></keyboard></pc></thermal></isa></pci-isa></ata></ata></via></intel(r)></intel(r)></vga-compatible></pci></pci-pci></acpi></acpi></power></high></cn700></aes-cbc,sha1,sha256></software></version></cn700></rng,aes,aes-ctr,sha1,sha256,rsa></sse3,est,tm2></fpu,vme,de,pse,tsc,msr,pae,mce,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>
-
Thats very interesting, is there a way to disable the padlock feature for those of us that use the padlock feature?
-
The beta release candidates for 1.2.3 had padlock not included in the kernel.
Maybe you look around on how to disable the kernel modules. See if it will helps with the realtek nics.
/boot/kernel/*.ko
-
I just got a Jetway J74K1G5S-LF with dual Realtek Lan ports running 1.2.3 and had trouble with the firewall becoming non responsive at random intervals, the symptoms being no internet access and could not log on to the firewall via the web GUI. I resolved the issue by disabling Hardware Checksum Unloading on the Advanced functions web GUI page near the bottom of the page. This has resolved the issue and now everything works fine
-
I just got a Jetway J74K1G5S-LF with dual Realtek Lan ports running 1.2.3 and had trouble with the firewall becoming non responsive at random intervals, the symptoms being no internet access and could not log on to the firewall via the web GUI. I resolved the issue by disabling Hardware Checksum Unloading on the Advanced functions web GUI page near the bottom of the page. This has resolved the issue and now everything works fine
Thanks for the tip "Hardware Checksum Unloading" sounds a lot like the padlock feature!
I'm planning to upgrade my J7F4K1G2ES machine from 1.2.1 to 1.2.3 next week and I'll definitely try to disable that feature if the machine starts locking up.
