Re: Broadcom BCM5701 / HP NC6770
I've been muddling around in src/sys/dev on the old system and the new system and there appear to be rather major changes to MII and bge, possibly the whole stack? There are a number of things that seem to have been merged with other parts of the network stack, or perhaps written into the individual drivers (someone working on the net stack would have to verify that). For instance, some files called in 5.3-REL seem to have gone away completely, and in the new (unpatched) version of if_bge.c under 7.3-REL, calls to these modules are gone: - #include /* for vtophys */ - #include /* for vtophys */ - #include /* for DELAY */ - #include - #include (called but something changed in here) - #include (ditto above) It appears that the checksum features have been completely rewritten, and some of the ring settings have changed. It's interesting that the driver only fills 256 of the rx rings in the hopes that the cpu is "fast enough to keep up with the NIC". Would a subroutine here to grab the cpu clock and count (number of procs/pipelines) be more trouble than it's worth to "automagically" increase the number of rx rings the driver fills based on the system in which it's installed? Something also changed in pci/pcireg.h and pci/pcivar.h, but I haven't had the time to hunt down and expand the source tree from the 5.3-REL branch yet. I have other machines with copper nics utilizing the bge driver, and there are no issues at all. Perhaps I'm getting ahead of things, but since this seems to have been broken through several releases, would it make any sense to split the support between the BCM5701KHB chipset and the more recent BCM chipset to avoid causing issues with cards/systems not currently experiencing troubles? Erich M. Jenkins Fuujin Group Limited "You should never, never doubt what no one is sure about." -- Gene Wilder ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Panic with VIMAGE and pf
Hello, I was trying to enable VIMAGE (for use with jails) but stumbled upon the following panic: Fatal trap 12: page fault while in kernel mode fault virtual address: 0x28 current proceess = 38 (pfctl) db> bt pfil_head_get() at +0x41 pfioctl() at +0x11f2 devfs_ioctl_f() at +0x77 kern_ioctl() at +0xf6 ioctl() at +0xf0 syscall() +0x137 I can easily reproduce this in single user mode using: # kldload pf # pfctl -f /etc/pf.conf I disabled VIMAGE and the panic didn't occur anymore. I'm running amd64 stable/8; r206458. (I also tried this 3 weeks ago; but had the same problem) I'm not able to get a dump; the memory dump-thing stalls after printing the first mark. -- Jille ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Panic with VIMAGE and pf
On Sun, 11 Apr 2010, Jille Timmermans wrote: Hi, I was trying to enable VIMAGE (for use with jails) but stumbled upon the following panic: Fatal trap 12: page fault while in kernel mode fault virtual address: 0x28 current proceess = 38 (pfctl) db> bt pfil_head_get() at +0x41 pfioctl() at +0x11f2 devfs_ioctl_f() at +0x77 kern_ioctl() at +0xf6 ioctl() at +0xf0 syscall() +0x137 I can easily reproduce this in single user mode using: # kldload pf # pfctl -f /etc/pf.conf I disabled VIMAGE and the panic didn't occur anymore. I'm running amd64 stable/8; r206458. (I also tried this 3 weeks ago; but had the same problem) I'm not able to get a dump; the memory dump-thing stalls after printing the first mark. This is a FAQ. pf hasn't been virtulaized (in-tree) yet. See http://lists.freebsd.org/pipermail/freebsd-virtualization/2010-February/000449.html for how far it is and how to get it. That might, btw., be the better list to ask VIMAGE questions;) /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/116837: [tun] [panic] [patch] ifconfig tunX destroy: panic
Synopsis: [tun] [panic] [patch] ifconfig tunX destroy: panic Responsible-Changed-From-To: freebsd-net->bz Responsible-Changed-By: bz Responsible-Changed-When: Sun Apr 11 18:49:46 UTC 2010 Responsible-Changed-Why: Take at least temporary. http://www.freebsd.org/cgi/query-pr.cgi?pr=116837 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -> crash
Old Synopsis: BGE watchdog timeout --resetting -> crash New Synopsis: [bge] [panic] bge watchdog timeout --resetting -> crash Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Apr 12 01:56:25 UTC 2010 Responsible-Changed-Why: This does not sound i386-specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=145621 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
