Re: watchdog network card
Hi all, JoaoBR wrote: On Tuesday 10 April 2007 01:24, Andrew Reilly wrote: Wow. Somehow we've slipped through a one-year timewarp: On Tue, Mar 28, 2006 at 07:47:54AM -0300, JoaoBR wrote: On Tuesday 28 March 2006 07:40, Andrew Reilly wrote: After the last rebuild on my amd64-x2 box, both the nve ethernet on the motherboard and the dc ethernet that I had been using to work around other problems in the nve driver stopped working in this way. DEVICE_POLLING and ifconfig...polling has got me going again. I thoroughly recommend it. nve does not run polling mode but dc does I guess you have an IRQ conflict, nve and dc on the same hw interrupt, and that setting dc in polling mode worked around this problem then you could check vmstat -i with and without polling enabled to see it Thanks for the tip. I haven't been running dc or nve for about a year, now :-) Nfe has been working beautifully for me, without polling. I guess that I should have a look to see if nve has improved in the interim, but it's difficult to make oneself mess with something that isn't broken... nfe appears to work much better (also with polling) and flawless. I tried one and another time nve but nfe is what works, at least on amd64 and newer hardware so probably you don't need to waste your time ;) I noticed before few months that something changed in freebsd and now nfe is not very stable :( I said in freebsd because In the beginning I updated only freebsd and not the drivert itself. I thought getting latest nfe source will help but it doesn't. Anyway nfe is still lot better then nve, nve for me was useless best uptime for my network card with nve was few minutes. nfe0: watchdog timeout (missed Tx interrupts) -- recovering interrupt total rate irq1: atkbd06660 0 irq12: psm0 153054 0 irq15: ata1 778797 1 irq16: pcm0 2735727 7 irq17: skc0115669786296 irq18: nvidia0 24802500 63 irq21: ohci0+2418887 6 irq22: nfe0 ehci0 92319117236 cpu0: timer780827522 2000 Total 1019712050 2612 FreeBSD 6.2-STABLE i386 nfe0: NVIDIA nForce4 CK804 MCP9 Networking Adapter port 0xb000-0xb007 mem 0xd500-0xd5000fff irq 22 at device 10.0 on pci0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: watchdog network card
On Wed, Apr 11, 2007 at 11:53:24AM +0300, Stefan Lambrev wrote: Hi all, JoaoBR wrote: On Tuesday 10 April 2007 01:24, Andrew Reilly wrote: Wow. Somehow we've slipped through a one-year timewarp: On Tue, Mar 28, 2006 at 07:47:54AM -0300, JoaoBR wrote: On Tuesday 28 March 2006 07:40, Andrew Reilly wrote: After the last rebuild on my amd64-x2 box, both the nve ethernet on the motherboard and the dc ethernet that I had been using to work around other problems in the nve driver stopped working in this way. DEVICE_POLLING and ifconfig...polling has got me going again. I thoroughly recommend it. nve does not run polling mode but dc does I guess you have an IRQ conflict, nve and dc on the same hw interrupt, and that setting dc in polling mode worked around this problem then you could check vmstat -i with and without polling enabled to see it Thanks for the tip. I haven't been running dc or nve for about a year, now :-) Nfe has been working beautifully for me, without polling. I guess that I should have a look to see if nve has improved in the interim, but it's difficult to make oneself mess with something that isn't broken... nfe appears to work much better (also with polling) and flawless. I tried one and another time nve but nfe is what works, at least on amd64 and newer hardware so probably you don't need to waste your time ;) I noticed before few months that something changed in freebsd and now nfe is not very stable :( I said in freebsd because In the beginning I updated only freebsd and not the drivert itself. I thought getting latest nfe source will help but it doesn't. Anyway nfe is still lot better then nve, nve for me was useless best uptime for my network card with nve was few minutes. nfe0: watchdog timeout (missed Tx interrupts) -- recovering According to the above message, it seems that you use new nfe(4). :-) interrupt total rate irq1: atkbd06660 0 irq12: psm0 153054 0 irq15: ata1 778797 1 irq16: pcm0 2735727 7 irq17: skc0115669786296 irq18: nvidia0 24802500 63 irq21: ohci0+2418887 6 irq22: nfe0 ehci0 92319117236 ^^ You are using shared interrut so it's possible to get occasional watchdog timeouts. polling(4) should fix your issue here. cpu0: timer780827522 2000 Total 1019712050 2612 FreeBSD 6.2-STABLE i386 nfe0: NVIDIA nForce4 CK804 MCP9 Networking Adapter port 0xb000-0xb007 mem 0xd500-0xd5000fff irq 22 at device 10.0 on pci0 nfe(4) should be teached to use MSI/MSI-X for PCI-Express/PCI-X based adapters but it's not done yet. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: watchdog network card
Hi, -cut- I thought getting latest nfe source will help but it doesn't. -cut- nfe0: watchdog timeout (missed Tx interrupts) -- recovering According to the above message, it seems that you use new nfe(4). :-) Yes this is is with latest nfe, but I've got watchdog timeouts with previous version of this driver too. interrupt total rate irq1: atkbd06660 0 irq12: psm0 153054 0 irq15: ata1 778797 1 irq16: pcm0 2735727 7 irq17: skc0115669786296 irq18: nvidia0 24802500 63 irq21: ohci0+2418887 6 irq22: nfe0 ehci0 92319117236 ^^ You are using shared interrut so it's possible to get occasional watchdog timeouts. polling(4) should fix your issue here. I'll try this, and test :), It wasn't hard to generate generate watchdog timeout. But isn't polling bad under heavy load and busy CPU(s) ? cpu0: timer780827522 2000 Total 1019712050 2612 FreeBSD 6.2-STABLE i386 nfe0: NVIDIA nForce4 CK804 MCP9 Networking Adapter port 0xb000-0xb007 mem 0xd500-0xd5000fff irq 22 at device 10.0 on pci0 nfe(4) should be teached to use MSI/MSI-X for PCI-Express/PCI-X based adapters but it's not done yet. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: watchdog network card
On Wed, Apr 11, 2007 at 01:05:12PM +0300, Stefan Lambrev wrote: Hi, -cut- I thought getting latest nfe source will help but it doesn't. -cut- nfe0: watchdog timeout (missed Tx interrupts) -- recovering According to the above message, it seems that you use new nfe(4). :-) Yes this is is with latest nfe, but I've got watchdog timeouts with previous version of this driver too. Without polling(4) on shared interrupt system it's expected one. interrupt total rate irq1: atkbd06660 0 irq12: psm0 153054 0 irq15: ata1 778797 1 irq16: pcm0 2735727 7 irq17: skc0115669786296 irq18: nvidia0 24802500 63 irq21: ohci0+2418887 6 irq22: nfe0 ehci0 92319117236 ^^ You are using shared interrut so it's possible to get occasional watchdog timeouts. polling(4) should fix your issue here. I'll try this, and test :), It wasn't hard to generate generate watchdog timeout. But isn't polling bad under heavy load and busy CPU(s) ? Could be. YMMV. You couldn't also get best performance if interrupt is shared with other devices. cpu0: timer780827522 2000 Total 1019712050 2612 FreeBSD 6.2-STABLE i386 nfe0: NVIDIA nForce4 CK804 MCP9 Networking Adapter port 0xb000-0xb007 mem 0xd500-0xd5000fff irq 22 at device 10.0 on pci0 nfe(4) should be teached to use MSI/MSI-X for PCI-Express/PCI-X based adapters but it's not done yet. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: bundirty (nfs related)
Hello all,
We're running into regular panics on our webserver after upgrading
from 4.x to 6.2-stable:
# kgdb kernel.debug /usr/local/var/crash/vmcore.3
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
# Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
panic: bundirty: buffer 0xdc408bc0 still on queue 1
cpuid = 0
Uptime: 13h5m38s
Dumping 3326 MB (2 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 3327MB (851552 pages) 3311 3295 3279 3263 3247 3231 3215 3199
3183 3167 3151 3135 3119 3103 3087 3071 3055 3039 3023 3007 2991 2975 2959
2943 2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719
2703 2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479
2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239
2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999
1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759
1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519
1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279
1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039
1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751
735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463
447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175
159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06708e8 in boot (howto=260) at ../../../kern/kern_shutdown.c:409
#2 0xc0670bca in panic (
fmt=0xc08f7fec bundirty: buffer %p still on queue %d)
at ../../../kern/kern_shutdown.c:565
#3 0xc06b3409 in bundirty (bp=0xdc408bc0) at ../../../kern/vfs_bio.c:1036
#4 0xc06b3d6c in brelse (bp=0xdc408bc0) at ../../../kern/vfs_bio.c:1351
#5 0xc075e18e in nfs_writebp (bp=0xdc408bc0, force=1, td=0xcaa0e000)
at ../../../nfsclient/nfs_vnops.c:2982
#6 0xc075e3f8 in nfs_bwrite (bp=0xdc408bc0) at pcpu.h:162
#7 0xc06b5b7d in getblk (vp=0xc9908440, blkno=8438, size=6037, slpflag=256,
slptimeo=0, flags=0) at buf.h:412
#8 0xc0751299 in nfs_getcacheblk (vp=0xc9908440, bn=8438, size=6037,
td=0xcaa0e000) at ../../../nfsclient/nfs_bio.c:1253
#9 0xc0750e62 in nfs_write (ap=0x0) at ../../../nfsclient/nfs_bio.c:1069
#10 0xc08894f2 in VOP_WRITE_APV (vop=0xc097fc00, a=0xec2babf4)
at vnode_if.c:698
#11 0xc06cea9a in vn_write (fp=0xd01ec360, uio=0xec2bacbc,
active_cred=0xc8e71900, flags=0, td=0xcaa0e000) at vnode_if.h:372
#12 0xc0692867 in dofilewrite (td=0xcaa0e000, fd=5, fp=0xd01ec360,
auio=0xec2bacbc, offset=Unhandled dwarf expression opcode 0x93
) at file.h:252
#13 0xc069270b in kern_writev (td=0xcaa0e000, fd=5, auio=0xec2bacbc)
at ../../../kern/sys_generic.c:402
#14 0xc0692631 in write (td=0xcaa0e000, uap=0x0)
at ../../../kern/sys_generic.c:326
#15 0xc087842f in syscall (frame=
{tf_fs = 136970299, tf_es = 1210646587, tf_ds = -1078001605, tf_edi =
#136986624, tf_esi = 1210674680, tf_ebp = -1077942696, tf_isp = -332681884,
tf_ebx = 1210584448, tf_edx = 4096, tf_ecx = 0, tf_eax = 4, tf_trapno = 0,
#tf_err = 2, tf_eip = 1210524463, tf_cs = 51, tf_eflags = 530, tf_esp =
-1077942724, tf_ss = 59}) at ../../../i386/i386/trap.c:983
#16 0xc08649ef in Xint0x80_syscall () at ../../../i386/i386/exception.s:200
#17 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
dmesg of one of the hosts having this problem:
FreeBSD 6.2-RELEASE-p3 #2: Thu Apr 5 14:15:19 CEST 2007
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/SMP-DEBUG
WARNING: DIAGNOSTIC option enabled, expect reduced performance.
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU5130 @ 2.00GHz (2000.08-MHz 686-class CPU)
Origin = GenuineIntel Id = 0x6f6 Stepping = 6
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
Features2=0x4e33dSSE3,RSVD2,MON,DS_CPL,VMX,TM2,b9,CX16,b14,b15,b18
AMD Features=0x2010NX,LM
AMD Features2=0x1LAHF
Cores per package: 2
real memory = 3489005568 (3327 MB)
avail memory = 3414216704 (3256 MB)
ACPI APIC Table: PTLTD APIC
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 6
cpu3 (AP): APIC ID: 7
ioapic0 Version 2.0 irqs 0-23 on motherboard
ioapic1 Version 2.0 irqs 24-47 on motherboard
ixgb no go
Greetz! I happen to have ixgb hardware. Using the driver in FreeBSD 6.2/amd64 as well as the one at: http://downloadfinder.intel.com/scripts-df-external/Detail_Desc.aspx?agr=YInst=YesProductID=2245DwnldID=10958strOSs=AllOSFullName=All%20Operating%20Systemslang=eng just gives me: ixgb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:03:ba:31:8d:15 media: Ethernet autoselect status: no carrier ^ # pciconf -lv ... [EMAIL PROTECTED]:1:0: class=0x02 card=0x7036108e chip=0x10488086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82597EX 10 Gigabit Ethernet Controller' class= network subclass = ethernet ... # dmesg ... ixgb0: Intel(R) PRO/10GbE Network Driver, Version - 6.1.0 port 0xac00-0xac1f mem 0xfc4f8000-0xfc4f irq 28 at device 1.0 on pci2 ixgb0: Copyright (c) 2001-2006 Intel Corporation. ixgb0: Ethernet address: 00:03:ba:31:8d:15 ... This is on a SunFire x4100 connected end-to-end on another x4100. Solaris10 on both the same hardware (connected end-to-end) works. Am i left in the cold? :-( Thanks. cheers mars ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
create archive of system
Hello List, I apologize if this is not the correct place to ask this. What is the best way to create an archive of a FreeBSD system so yoy can take it to another computer and unarchive and have a runnable system, assuming the other systems disk had already been formatted with the appropriate filesystems. In other words I want to move all the files and have them keep all their attributes, permissions, ownership, chflags etc. Thanks, Steve -- They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety. (Ben Franklin) The course of history shows that as a government grows, liberty decreases. (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: create archive of system
On Wed, 11 Apr 2007 13:56:15 +0200, Stephen Clark [EMAIL PROTECTED] wrote: Hello List, I apologize if this is not the correct place to ask this. What is the best way to create an archive of a FreeBSD system so yoy can take it to another computer and unarchive and have a runnable system, assuming the other systems disk had already been formatted with the appropriate filesystems. In other words I want to move all the files and have them keep all their attributes, permissions, ownership, chflags etc. Thanks, Steve The list freebsd-questions is a better place for this question I think. But you can use dump/restore or tar. There are a lot of examples out there on the internet. Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
atacontrol panic
Hallo, the sequence #atacontrol detach ata2 #atacontrol reinit ata2 panics my 6.2-RELEASE-p3 system. I know, the simple solution is don't do that. But it would be nice if it could be fixed. I can't get a dump at the moment and I can't try a more recent -STABLE or -CURRENT to see if it is already fixed. I'm not sure if I should submit a PR without this. Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: create archive of system
Stephen Clark wrote: Hello List, I apologize if this is not the correct place to ask this. What is the best way to create an archive of a FreeBSD system so yoy can take it to another computer and unarchive and have a runnable system, assuming the other systems disk had already been formatted with the appropriate filesystems. In other words I want to move all the files and have them keep all their attributes, permissions, ownership, chflags etc. Thanks, Steve dump and restore will probably be the most popular opinion for this. This is my setup for this: http://mikestammer.com/dokuwiki/bsd:dumprestore ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: create archive of system
On Wed, Apr 11, 2007 at 02:11:02PM +0200, Ronald Klop wrote: The list freebsd-questions is a better place for this question I think. But you can use dump/restore or tar. There are a lot of examples out there on the internet. If the two systems are very similar you might also try a ghosting solution, especially if you would want to store the entire disc, including partitions/slices. For example Ghost4Unix http://www.feyrer.de/g4u/ --Regards, John -- SDF Public Access UNIX System - http://sdf.lonestar.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Portsnap with (broken) transparent proxy on 6.2
Colin,
Normally I would contact you directly (off-list) with this report,
however I had tried searching Google for these symptoms and found no
resolutions, so I'm copying -stable for archival purposes in case
someone runs into a similar problem.
I recently decided to try out portsnap on a few machines. So far so
good, except for a few. There are several systems that I maintain which
are behind a transparent proxy (that I don't control and don't even
really know what it is). It seems this proxy doesn't correctly support
HTTP pipelining, and so the metadata updates fail.
It looks like this:
Fetching 2 metadata files... /usr/sbin/portsnap: cannot open
26700e16d411367c92b53d1aa48ab460fc64c4796b7aa15915e5de39eedab1cc.gz: No
such file or directory
metadata is corrupt.
The debug output doesn't add much to it other than
phttpget: Connection failure
It looks like it does successfully get the first file each time, but
loses the connection afterward. It would take a lot of invocations of
portsnap to get them all :)
I looked through the portsnap / phttpget source and didn't see an easy
way to disable pipelining. Perhaps some sort of override could be
added in the future to work around broken proxies? In the meantime, I
have replaced /usr/libexec/phttpget with the following shell script and
now everything is working fine:
---
#!/bin/sh
SERVER=$1
shift
for x in $@; do
fetch http://${SERVER}/${x};
done
---
Craig
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WOL question
On 10/04/07, Jack Vogel [EMAIL PROTECTED] wrote: I am hoping someone here who has more familiarity with the ACPI code can enlighten me I have an internal bug filed complaining that FreeBSD disables wake-on-lan on the hardware. This means that if you boot, say, Linux, even Knoppix as a quickie, and then shutdown, if the hardware supports it, it will be left in a state where a magic-packet wakeup will work. However, even if I boot up a FreeBSD kernel with NO em driver, and then shutdown, it undoes the WOL setup. Now, I would like to have explicit WOL support added into the em driver, but before I even worry about that I need to understand where the kernel turns this off without the driver even needed. I've looked around at the dev/acpi and arch/acpi code and at least so far I'm having a hard time getting an adequate picture to know how it happens. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] This isnt specific to em, it also happens on other ethernet cards (rl(8) fxp(8)) that support WOL/MagicPacket. Might be idea to check PR database see if someone has same problem, maybe fix? it was nice installing ports/net/wol and getting a computer to fire up remotely, but as soon as it rebooted from FreeBSD, WOL stopped :( -- Kimi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WOL question
In message [EMAIL PROTECTED], Kimi Ostro writes: On 10/04/07, Jack Vogel [EMAIL PROTECTED] wrote: I am hoping someone here who has more familiarity with the ACPI code can enlighten me I have an internal bug filed complaining that FreeBSD disables wake-on-lan on the hardware. Now, I would like to have explicit WOL support added into the em driver, but before I even worry about that I need to understand where the kernel turns this off without the driver even needed. This isnt specific to em, it also happens on other ethernet cards (rl(8) fxp(8)) that support WOL/MagicPacket. Might be idea to check PR database see if someone has same problem, maybe fix? it was nice installing ports/net/wol and getting a computer to fire up remotely, but as soon as it rebooted from FreeBSD, WOL stopped :( Hi, FreeBSD isn't disabling WOL. It needs to be enabled on shutdown for most cards. I have patches for ifconfig, and the xl driver to enable WOL. It should be possible to add support to other drivers, but it's different for each card. You should be able to find a diff against 5-stable in the archives. Changes against -CURRENT aren't _that_ different. - marcel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WOL question
On 4/11/07, Anne Marcel Roorda [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Kimi Ostro writes: On 10/04/07, Jack Vogel [EMAIL PROTECTED] wrote: I am hoping someone here who has more familiarity with the ACPI code can enlighten me I have an internal bug filed complaining that FreeBSD disables wake-on-lan on the hardware. Now, I would like to have explicit WOL support added into the em driver, but before I even worry about that I need to understand where the kernel turns this off without the driver even needed. This isnt specific to em, it also happens on other ethernet cards (rl(8) fxp(8)) that support WOL/MagicPacket. Might be idea to check PR database see if someone has same problem, maybe fix? it was nice installing ports/net/wol and getting a computer to fire up remotely, but as soon as it rebooted from FreeBSD, WOL stopped :( Hi, FreeBSD isn't disabling WOL. It needs to be enabled on shutdown for most cards. I have patches for ifconfig, and the xl driver to enable WOL. It should be possible to add support to other drivers, but it's different for each card. You should be able to find a diff against 5-stable in the archives. Changes against -CURRENT aren't _that_ different. So, why isnt this in 6.X then? I've now had email with Nate Lawson about ACPI and think I know how to make it work properly, of course I havent yet tested the theory, if it works like it sounds then its not going to be too hard to do this. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
