Network performance-problem

Hello, i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM 3CCFE575CT Lancard (pc-cardbus) using the xl-driver. It goes as follows: I am using the 3COM-card in a 10MB-switched network. Occasionally someone is doing big network installs via multicast IP-packets. This is done with

dev/acpica/acpi.c - minor patch for cleaner poweroff

Hi, I think you're the main maintainer of the ACPICA codebase (and yes, I know that parts of it is imported from Intel). Attached is a trivial patch which makes for cleaner testing for RB_POWEROFF in acpi_shutdown_final() - I've had various kernel/userland routines invoke reboot sequences where

Re: Is compatibility for old aout binaries broken?

On Monday, 18th December 2000, "Donald J . Maddox" wrote: On Mon, Dec 18, 2000 at 04:41:17PM +1000, Stephen McKay wrote: I expected some build tool expert to say "Just compile with these options". But they haven't. So I'll see if the bits have rotted, or whether we can keep building ld.so

Re: Is compatibility for old aout binaries broken?

On Tuesday, 19th December 2000, Stephen McKay wrote: But it might be just as easy to copy it off the 3.3 CD every time. Oops! As I wrote earlier, 3.3 and onward have the broken ld.so. Good copies are found on 3.0 though to 3.2. Sorry for veering off the road there. :-) Stephen. To

$B>/$7$N$*6b$GBg6b$,<j$KF~$k!*!*(B

$BFMA3$N%a!<%k$9$_$^$;$s(B $B:G=i$G:G8e$G$9!#=EJ#$7$?J}$O!"K\Ev$K?=$7Lu$4$6$$$^$;$s!#(B $B$"$kF|;d$N=j$K0J2<$h$&$J!V(B4000$B1_$GBg6b$,

HEADSUP: Linksys cards need flag.

Hi folks, for mobile users. Linksys Fast Ethernet PCCARD cards supported by the ed driver now require the addition of flag 0x8 to their config line in pccard.conf(5). This flag is not optional. These Linksys cards will not be recognized without it. The old code tried to automatically

Re: test/review: /dev/console logging patch

On 18-Dec-00 Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], John Baldwin writes: On 17-Dec-00 Poul-Henning Kamp wrote: This patch is for the printf(9), log(9) /dev/console stuff. The result is that you can watch the output from /etc/rc in your /var/log/messages. Poul-Henning

debug build of libc_r

Hi, I'm seeing a crash related to libc_r. Could someone please instruct me as to how to build a debug version. Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Is compatibility for old aout binaries broken?

On Tue, Dec 19, 2000 at 01:00:28AM +1000, Stephen McKay wrote: So we could in principle build ld.so for every release. I would say "no". The building of a.out bits is getting harder as more and more framework pieces are removed. I don't quite fully understand the problem yet. Do you have a

Re: Is compatibility for old aout binaries broken?

You don't need a CDROM... You can get it from: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/commerce/games/SimCity/SimCity-3.6b.tgz On Mon, Dec 18, 2000 at 10:03:15AM -0800, David O'Brien wrote: On Tue, Dec 19, 2000 at 01:00:28AM +1000, Stephen McKay wrote: So we could in principle

Re: debug build of libc_r

On Mon, Dec 18, 2000 at 12:01:19PM -0600, Peter Schultz wrote: Hi, I'm seeing a crash related to libc_r. Could someone please instruct me as to how to build a debug version. cd /usr/src/lib/libc_r make clean DEBUG_FLAGS=-g3 make make install Jason To Unsubscribe: send mail to [EMAIL

Kernel Buffer overwrite debugging

I am having a problem with a device driver that uses physio to transfer data to a SCSI adapter. Some times the after passing the buffer to the CAM system, via xpt_action, the buffer contents are modified. I've traced my driver and cannot determine how this could be happening. I am running on a

Re: Is compatibility for old aout binaries broken?

The generated ld.so has bloated a bit :-) but works fine. So we could in principle build ld.so for every release. It's just a question of whether we should. I think we should. But it might be just as easy to copy it off the 3.3 CD every time. It's dead end stuff after all. Does the

Re: Bridging NT4 subnets

On Wed, 13 Dec 2000, John Miller wrote: I am having trouble setting up bridge between 2 subnets with NT4 servers on either side. Both subnets are behind different firewalls for external access. Static Routes have been setup on each subnets firewalls to route traffic through the bridge.

Re: Network performance-problem

In message [EMAIL PROTECTED] Michael Class writes: : xl0: no carrier - transceiver cable problem? : Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas? My 3CCFE575CT doesn't have this problem, except when I'm using it with a bad cable. Maybe that's the problem? Warner To

Re: HEADSUP: Linksys cards need flag.

In message [EMAIL PROTECTED] Toshihiko ARAI writes: : Linksys Fast Ethernet PCCARD cards supported by the ed driver now : require the addition of flag 0x8 to their config line in : pccard.conf(5). This flag is not optional. These Linksys cards will : not be recognized without it. I've

subscribe

To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Is compatibility for old aout binaries broken?

On Monday, 18th December 2000, Jordan Hubbard wrote: The generated ld.so has bloated a bit :-) but works fine. So we could in principle build ld.so for every release. It's just a question of whether we should. I think we should. But it might be just as easy to copy it off the 3.3 CD

Re: Network performance-problem

Michael Class wrote: Hello, i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM 3CCFE575CT Lancard (pc-cardbus) using the xl-driver. [snip] Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas? Make sure you are running with the TCP/IP NewReno

Re: Is compatibility for old aout binaries broken?

On Tue, Dec 19, 2000 at 03:08:25PM +1000, Stephen McKay wrote: Our current problem is that an older ld.so has somehow been made part of compat22. I'm now attempting to determine whether the ld.so on the 3.2 CD contains the fix in rev 1.57 of rtld-aout/rtld.c, and if so I'll just commit it in

Recent -CURRENT kernel build problem...

Dear all... Has anyone noticed this problem? Or is it just happening to me? On make buildkernel (with -CURRENT just cvsuped a few minutes ago) and the generic config KERNEL; make depend; make; cycle, the kernel build failed with this message: -- cc -c -O -pipe -Wall -Wredundant-decls