Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.ckern_prot.c kern_sig.c
On Thu, 6 Apr 2000, Matthew Dillon wrote:
>
> :The version of Linux kernel source that I have uses the first:
> :
> :asmlinkage long sys_getppid(void)
> :{
> : int pid;
> : struct task_struct * me = current;
> : struct task_struct * parent;
> :
> : parent = me->p_opptr;
> : for (;;) {
> : pid = parent->pid;
> :#if __SMP__
> :{
> : struct task_struct *old = parent;
> : mb();
> : parent = me->p_opptr;
> : if (old != parent)
> : continue;
> :}
> :#endif
> : break;
> : }
> : return pid;
> :}
> :
> :I like it. mb() is most certainly a "memory barrier" inline to
> :force ordering constraints. interesting how they don't use
> :volatile for the pointer though:
>
> mb() just prevents the compiler from optimizing access to the
> structural fields (otherwise it might move the accesses outside
> the for() loop and you would get an infinite loop. From the
> compiler's point of view, mb() is a subroutine call (I assume
> in the headers it's a volatile __asm).
>
> We can either use an mb() type of thing, or we can declare the structural
> field volatile, or we can cast the access to be volatile.
It also forces the cpu to drain writes and prevents reads from being
re-ordered before the mb(). This is mainly a hint for alpha processors but
I think it is relavent to other architectures.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Versions of gas that support 3dnow!?
I've been following the GLX stuff for Matrox G400s and noticed that there's now a version of gas that supports 3dnow! instructions without bugs. It's one of the snapshots by H.J. Lu - 2.9.5.0.34, found at ftp://ftp.varesearch.com/pub/support/hjl/binutils/ Any chance of this making its way into current? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Versions of gas that support 3dnow!?
On Fri, Apr 07, 2000 at 03:56:52PM +0800, Stephen Hocking-Senior Programmer PGS SPS Perth wrote: > now a version of gas that supports 3dnow! instructions without bugs. It's one The base Binutils (which includes gas) is being upgraded. There are several groups that need to be addressed in the upgrade, so I don't yet know which version will be used in the upgrade. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: ports Makefiles being updated soon (forwarded)
FYI. -PW === From: [EMAIL PROTECTED] (Satoshi Asami) Subject: HEADS UP: ports Makefiles being updated soon To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Date: Fri, 7 Apr 2000 01:15:16 -0700 (PDT) Message-Id: <[EMAIL PROTECTED]> Hello world, As we have been discussing on the ports list, we have decided to introduce a slight syntax change to the port Makefiles regarding DISTNAME and PKGNAME. This change will be done this weekend. I will freeze the ports tree Friday night (U.S. Pacific Time) and a small group of volunteers will convert the entire tree in one pass. I will then unfreeze the tree and we can go back to business. I don't expect anything to break but since we are talking about over 3,000 ports, I can't guarantee that everything will go smooth. If you haven't cvsupped ports for a while, you may want to do it now. After the conversion, "old style" ports will no longer be accepted. Please read the handbook's porting section at, for instance, http://www.FreeBSD.org/handbook/porting.html#PORTING-SAMPLEM for details. (The above page seems to be still showing the old version -- the documentation change was committed today, so please check back later.) Also, make sure that you have the latest ports/Mk/bsd.port.mk if you are using anything from ports-current. This means, if you are cvsupping individual ports collections, you need to have "ports-base" in your cvsupfile. Thanks, Satoshi (and the friendly ports team) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth 6df833c4 unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ports Makefiles being updated soon (forwarded)
Satoshi Asami wrote: > After the conversion, "old style" ports will no longer be accepted. How about those unlucky, which are patiently waiting for their destiny in the PR database? I personally have several and would like to know if any activity from my side is reqired. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
At 12:57 AM -0400 2000/4/7, Alexander N. Kabaev wrote: > I am perfectly aware of the way OpenBSD builds contrib software. I am just > making a point that they have found perl 5.6.0 is stable enough to be > included into their OS. It's my understanding that we already have a better and cleaner way of handling international versus US crypto issues with OpenSSH than they do, thanks to the stubs that were put into place in the libraries. Given this, and given the level of tight integration we have elsewhere with those things that we have taken the somewhat unusual step of integrating into FreeBSD, I don't take their inclusion of Perl 5.6.0 to be a necessary and sufficient condition for us to do the same. Just because someone else jumped off a bridge and has survived (so far), does this necessarily mean it's a good idea for us to try to follow suit at this stage? -- These are my opinions -- not to be taken as official Skynet policy == Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
On Fri, Apr 07, 2000 at 12:57:16AM -0400, Alexander N. Kabaev wrote: > I am perfectly aware of the way OpenBSD builds contrib software. I am > just making a point that they have found perl 5.6.0 is stable enough > to be included into their OS. It is an issue of personal relationships and politics, not the technical one. Tom Christiansen uses OpenBSD and advocates Perl to it (and other way around). Cheers, -- Anton Berezin <[EMAIL PROTECTED]> The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB To Do list
If've put up a list of things that need to be done still in the FreeBSD USB stack. The list is _big_. I'll be adding things as they come up. http://www.etla.net/~n_hibma/usb/usb.pl A lot of the items are not that difficult to do and if you feel like taking up a little project, start working on something and send patches/source as you work through them. It might change the short term priority list a bit to include your toy :-) The Todo list is included below. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Do list for the USB project: Let meknow if you would like to participate in any way, or you have done one of the items below! - Short term priority list - Finish off the import of the urio driver. Update the license in rio500_usb.h. - Finish the synchronisation with NetBSD - Split umass into two parts: wire (BBB, CBI) and command protocols - Investigate panic on close of interrupt pipe with low frequency. - Finally checkout the umodem driver and include it in the tree. - USB base stack and general items. - Fix/check suspend on UHCI and OHCI controllers, especially on laptops. - Use a kthread to handle the 'Done Queue'. - OHCI connection problems - Check out the manpages available. Add new ones where appropriate. - Generic driver should be available for all devices, not only for the ones that nothing else attaches to. - Possibility of locking pipes, interfaces & devices to make sure no concurrent accesses are done (confusing a device, e.g. e-shuttle USB) - Implement poll/select for generic device. Idea: When select is called for reading and no read is in progress a read for MaxPacketSize with SHORT PACKET OK set is initiated. Select for writing always succeeds. - One shot transfers on interrupt pipes (needed for 'bulk' outs on low speed devices for example). - USB userland utility (usbcontrol) - The word 'class' is used in usb.h. This is a problem for c++ compilers. Change the whole interface for usbdevs/usbd to something sensible. - Create a usbcontrol util combining all the functionality of usb_dump.c, usbdevs and the usb*something* utility in NetBSD into one. - USB Serial port driver (usio) driver (by Doug Ambrisko) - Check out the version of sdcc that is in ports nowadays. - Check out which dongles the usio driver works with - Usio manpage. - USB Mass Storage (umass) driver - Check out the file system corruption problems under heavy load / added load of a USB ethernet dongle. - Check out support for ATAPI devices. - Convert Read/Write_6 to Read/Write_10 in transform. This avoids having to quirk every single UFI compliant device. - USB Keyboards - Keyboard in DDB debugger does not work. - USB printer port support - Bi-directional support - Is the manual page up to date? Does it specify all the flags you can set on the device minor number? - Related: - PCI/USB/PCCard/PCMCIA/other vendor, product and revision Id matching code should be made generic, so that drivers can match in a more generic way. The ID's should be collected into one location to make the addition of new Id's more generic. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [usb-bsd] USB To Do list
>To Do list for the USB project: > >Let meknow if you would like to participate in any way, or you have >done one of the items below! [...] >- USB Keyboards >- Keyboard in DDB debugger does not work. In what configuration does it not work? I can use my USB keyboard in DDB without problems on a dual PPro box (4.0-STABLE) with a UHCI controller (VIA 83c572) card and a Pentium box (3.4-STABLE) with Intel PIIX3 here... Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
We want to update our system perl5. It'll take some work. If you want to do the work, your patches will be greatly appreciated by our perl5 maintainer, Mark Murray <[EMAIL PROTECTED]>. Since nobody here has offered to do any _work_ on incorporating perl 5.6.0 into FreeBSD 5.0-CURRENT, please would you all just shut up about it? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMP problem? (was: Re: [usb-bsd] USB To Do list)
>To Do list for the USB project: [...] >- USB base stack and general items. I am currently having trouble with Gigabyte GA-6BXD, dual Pentium III motherboard. If I boot a UP kernel (5.0-CURRENT), the PIIX4 USB controller works fine. If I boot a SMP kernel (the only difference from the UP kernel is support for SMP), the kernel seems unable to communicate with the USB device. When I plug a USB keyboard, I get uhci_timeout: ii=0xc0a601c0 uhci_timeout: ii=0xc0a601c0 uhci_timeout: ii=0xc0a601c0 usbd_new_device: addr=2, getting first desc failed uhub_explore: usb_new_device failed, error=TIMEOUT uhub0: device problem, disabling port 1 I vaguely remember someone also reported similar problems with the SMP kernel in the past Interesting thing is that I have another SMP box, and its USB works fine. The version is 4.0-STABLE. The USB controller is VIA 83c572. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [usb-bsd] USB To Do list
> >- USB Keyboards > >- Keyboard in DDB debugger does not work. > > In what configuration does it not work? I can use my USB keyboard in > DDB without problems on a dual PPro box (4.0-STABLE) with a UHCI > controller (VIA 83c572) card and a Pentium box (3.4-STABLE) with Intel > PIIX3 here... I've seen it run away like mad (like pressing Return a hundred times a second). Maybe that was just a glitch (on UHCI hardware). I've seen this same behaviour on an iMac running NetBSD. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP problem? (was: Re: [usb-bsd] USB To Do list)
What does it say before this info? Shared interrupt? USB does work on SMP (or at least in some cases). > uhci_timeout: ii=0xc0a601c0 > uhci_timeout: ii=0xc0a601c0 > uhci_timeout: ii=0xc0a601c0 > usbd_new_device: addr=2, getting first desc failed > uhub_explore: usb_new_device failed, error=TIMEOUT > uhub0: device problem, disabling port 1 > > I vaguely remember someone also reported similar problems with the SMP > kernel in the past > > Interesting thing is that I have another SMP box, and its USB works fine. > The version is 4.0-STABLE. The USB controller is VIA 83c572. > > Kazu > > > @Backup- Protect and Access your data any time, any where on the net. > Try @Backup FREE and recieve 300 points from mypoints.com Install now: > http://click.egroups.com/1/2345/6/_/85983/_/955110182/ > > > > -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: ports Makefiles being updated soon (forwarded)
Thus spake Maxim Sobolev ([EMAIL PROTECTED]): > How about those unlucky, which are patiently waiting for their destiny in the > PR database? I personally have several and would like to know if any activity > from my side is reqired. Let the committers do that. It's a trivial fix. If you change stuff anyway (e.g. new version has been made available in the meanwhile), you can correct this in the new PR. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Overwhelming messages from /sys/netinet/if_ether.c
Since I started using a cable modem and dhclient, my system has been
literally overwhelmed with messages like:
/kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
Man, these messages were pouring out of syslogd like mad, and my
/var/log/messages* files had to be deleted, because they were growing
so huge. There were literally hundreds of these messages pouring out
via syslogd per second, and they were coming non-stop. There were so
many messages coming out, my hard drive was overwhelmed until dhclient
finally obtain/ed a lease. That said, I suggest we make the following
patch to /sys/netinet/if_ether.c:
--- if_ether.c.orig Wed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea->arp_sha, ":", inet_ntoa(isaddr));
+ ea->arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
- Donn
--- if_ether.c.orig Wed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea->arp_sha, ":", inet_ntoa(isaddr));
+ ea->arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
RE: Overwhelming messages from /sys/netinet/if_ether.c
The message in question can be extremely useful in case there is IP address
clash on the local network. I suggest we just change the code in question to
ignore clashes over 0.0.0.0 address only.
On 07-Apr-00 Donn Miller wrote:
> Since I started using a cable modem and dhclient, my system has been
> literally overwhelmed with messages like:
>
> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
>
> Man, these messages were pouring out of syslogd like mad, and my
> /var/log/messages* files had to be deleted, because they were growing
> so huge. There were literally hundreds of these messages pouring out
> via syslogd per second, and they were coming non-stop. There were so
> many messages coming out, my hard drive was overwhelmed until dhclient
> finally obtain/ed a lease. That said, I suggest we make the following
> patch to /sys/netinet/if_ether.c:
>
> --- if_ether.c.orig Wed Mar 29 02:50:39 2000
> +++ if_ether.c Fri Apr 7 11:24:54 2000
> @@ -554,9 +554,9 @@
> return;
> }
> if (isaddr.s_addr == myaddr.s_addr) {
> - log(LOG_ERR,
> + /* log(LOG_ERR,
>"arp: %6D is using my IP address %s!\n",
> - ea->arp_sha, ":", inet_ntoa(isaddr));
> + ea->arp_sha, ":", inet_ntoa(isaddr)); */
> itaddr = myaddr;
> goto reply;
> }
>
>
> - Donn
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 07-Apr-00
Time: 11:49:33
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
On Apr 07, Donn Miller wrote: > Since I started using a cable modem and dhclient, my system has been > literally overwhelmed with messages like: > > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > I haven't tried this but how about changing the /sbin/dhclient-script to not use 0.0.0.0 as the address that wakes up the interface. --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
In article <[EMAIL PROTECTED]>, Alexander N. Kabaev <[EMAIL PROTECTED]> wrote: > The message in question can be extremely useful in case there is IP address > clash on the local network. I suggest we just change the code in question to > ignore clashes over 0.0.0.0 address only. I agree. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
Trivial patch attached :) On 07-Apr-00 John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Alexander N. Kabaev <[EMAIL PROTECTED]> wrote: >> The message in question can be extremely useful in case there is IP address >> clash on the local network. I suggest we just change the code in question to >> ignore clashes over 0.0.0.0 address only. > > I agree. > > John > -- > John Polstra [EMAIL PROTECTED] > John D. Polstra & Co., Inc.Seattle, Washington USA > "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa if_ether.diff
Re: HEADS UP: ports Makefiles being updated soon (forwarded)
On Fri, 7 Apr 2000, Maxim Sobolev wrote: > > After the conversion, "old style" ports will no longer be accepted. > > How about those unlucky, which are patiently waiting for their destiny in the > PR database? I personally have several and would like to know if any activity > from my side is reqired. I think Satoshi was just referring to newly-submitted ports. Existing queued ones won't need to be changed. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new device/bus stuff
Is there a howto on how to convert drivers from the old to new form? for example if_sr.c no longer shows up (or is even probed) in 4.0-stable. I've looked here and there but I can't figure out if there is some ISA_SHIM option needed (it's not in LINT if so). There seemes to be lotsa complicated man pages but I haven't found a brief "here's what you probably need to do" doc.. I'm looking for something that doesn't require rewriting the whole thing.. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
Could we stop this nonsense thread now? No one is against it. The only reason why it is not in the tree is that no one has the time to actually implement the change. If someone wants it in the tree, do the work and submit it to the current maintainer of Perl in FreeBSD. Thanks in advance. Nick On Thu, 6 Apr 2000, Alexander N. Kabaev wrote: > According to OpenBSD ournal site, OpenBSD-current has perl 5.6.0 in it's source > tree already. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new device/bus stuff
On Fri, 7 Apr 2000, Julian Elischer wrote: > Is there a howto on how to convert drivers from the old to new > form? > > for example if_sr.c no longer shows up (or is even probed) in > 4.0-stable. I've looked here and there but I can't figure out if there > is some ISA_SHIM option needed (it's not in LINT if so). COMPAT_OLDISA? > > There seemes to be lotsa complicated man pages but I haven't found > a brief "here's what you probably need to do" doc.. > > I'm looking for something that doesn't require rewriting the whole > thing.. > > > -- > __--_|\ Julian Elischer > / \ [EMAIL PROTECTED] > ( OZ) World tour 2000 > ---> X_.---._/ presently in: Perth > v > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
> The message in question can be extremely useful in case there is IP address
> clash on the local network. I suggest we just change the code in question to
> ignore clashes over 0.0.0.0 address only.
No, don't do that, anyone arping 0.0.0.0 on any network around here
I sure as heck want to know about it asap! Someone someplace on
that stupid telco's DSL bridged network is mis-configured and
sending out arp messages for the 0 addresses. Easy enough to
cause though:
ifconfig xx0 0.0.0.0 up
should do the trick...
> On 07-Apr-00 Donn Miller wrote:
> > Since I started using a cable modem and dhclient, my system has been
> > literally overwhelmed with messages like:
> >
> > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
> >
> > Man, these messages were pouring out of syslogd like mad, and my
> > /var/log/messages* files had to be deleted, because they were growing
> > so huge. There were literally hundreds of these messages pouring out
> > via syslogd per second, and they were coming non-stop. There were so
> > many messages coming out, my hard drive was overwhelmed until dhclient
> > finally obtain/ed a lease. That said, I suggest we make the following
> > patch to /sys/netinet/if_ether.c:
> >
> > --- if_ether.c.orig Wed Mar 29 02:50:39 2000
> > +++ if_ether.c Fri Apr 7 11:24:54 2000
> > @@ -554,9 +554,9 @@
> > return;
> > }
> > if (isaddr.s_addr == myaddr.s_addr) {
> > - log(LOG_ERR,
> > + /* log(LOG_ERR,
> >"arp: %6D is using my IP address %s!\n",
> > - ea->arp_sha, ":", inet_ntoa(isaddr));
> > + ea->arp_sha, ":", inet_ntoa(isaddr)); */
> > itaddr = myaddr;
> > goto reply;
> > }
> >
> >
> > - Donn
>
> --
> E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
> Date: 07-Apr-00
> Time: 11:49:33
> --
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT in order to bring interface up. Windows seems to do that as well or there is no sane explanation for the relatively big number of these nasty messages I am getting every time MediaOne network goes down and several PCs sharing the same cable network segment attempt to renew their lease at the same time. On 07-Apr-00 Rodney W. Grimes wrote: >> The message in question can be extremely useful in case there is IP address >> clash on the local network. I suggest we just change the code in question to >> ignore clashes over 0.0.0.0 address only. > > No, don't do that, anyone arping 0.0.0.0 on any network around here > I sure as heck want to know about it asap! Someone someplace on > that stupid telco's DSL bridged network is mis-configured and > sending out arp messages for the 0 addresses. Easy enough to > cause though: > > ifconfig xx0 0.0.0.0 up > > should do the trick... > -- E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]> Date: 07-Apr-00 Time: 14:35:14 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
> > The message in question can be extremely useful in case there is IP address > > clash on the local network. I suggest we just change the code in question to > > ignore clashes over 0.0.0.0 address only. > > No, don't do that, anyone arping 0.0.0.0 on any network around here > I sure as heck want to know about it asap! Then use a tool designed for the job. You'll only get this message on a system that's a DHCP client and currently trying to get a lease. I don't think that you would ever get any utility from the code as it stands, so the change is not going to affect you. (Note that if you were to configure a system to listen on 0.0.0.0 in order to use this message, you would then be arping for 0.0.0.0, which would appear to defeat your purpose.) Can I kindly suggest that you go find a bridge or a dam or some gun-control law to go oppose for a few months? This random sniper activity is pretty irritating. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
I have seen that situation before as well
and there may be more slight tolerance-style improvements
that could be made but I can't think of any at the moment.
In message <[EMAIL PROTECTED]>, Donn Miller writes:
>This is a multi-part message in MIME format.
>--ABD696746D33D54680111FE2
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Since I started using a cable modem and dhclient, my system has been
>literally overwhelmed with messages like:
>
>/kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
>
>Man, these messages were pouring out of syslogd like mad, and my
>/var/log/messages* files had to be deleted, because they were growing
>so huge. There were literally hundreds of these messages pouring out
>via syslogd per second, and they were coming non-stop. There were so
>many messages coming out, my hard drive was overwhelmed until dhclient
>finally obtain/ed a lease. That said, I suggest we make the following
>patch to /sys/netinet/if_ether.c:
>
>--- if_ether.c.orig Wed Mar 29 02:50:39 2000
>+++ if_ether.c Fri Apr 7 11:24:54 2000
>@@ -554,9 +554,9 @@
>return;
>}
>if (isaddr.s_addr == myaddr.s_addr) {
>- log(LOG_ERR,
>+ /* log(LOG_ERR,
> "arp: %6D is using my IP address %s!\n",
>- ea->arp_sha, ":", inet_ntoa(isaddr));
>+ ea->arp_sha, ":", inet_ntoa(isaddr)); */
>itaddr = myaddr;
>goto reply;
>}
>
>
>- Donn
>--ABD696746D33D54680111FE2
>Content-Type: text/plain; charset=us-ascii;
> name="if_ether.diff"
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline;
> filename="if_ether.diff"
>
>--- if_ether.c.origWed Mar 29 02:50:39 2000
>+++ if_ether.c Fri Apr 7 11:24:54 2000
>@@ -554,9 +554,9 @@
> return;
> }
> if (isaddr.s_addr == myaddr.s_addr) {
>- log(LOG_ERR,
>+ /* log(LOG_ERR,
> "arp: %6D is using my IP address %s!\n",
>- ea->arp_sha, ":", inet_ntoa(isaddr));
>+ ea->arp_sha, ":", inet_ntoa(isaddr)); */
> itaddr = myaddr;
> goto reply;
> }
>
>--ABD696746D33D54680111FE2--
>
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
No... In message <[EMAIL PROTECTED]>, Mathew Kanner writes: >On Apr 07, Donn Miller wrote: >> Since I started using a cable modem and dhclient, my system has been >> literally overwhelmed with messages like: >> >> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! >> > > I haven't tried this but how about changing the >/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes up >the interface. > > --Mat > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
I say with 99% certainty that assigning 0.0.0.0 to the interface is a requirement of dhcp. You can't stop using it and expect dhcp to work. In message <[EMAIL PROTECTED]>, "Alexander N. Kabaev" writes: >FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT >in order to bring interface up. Windows seems to do that as well or >there is no sane explanation for the relatively big number of these nasty >messages I am getting every time MediaOne network goes down and several PCs >sharing the same cable network segment attempt to renew their lease at the sam >e >time. > > >On 07-Apr-00 Rodney W. Grimes wrote: >>> The message in question can be extremely useful in case there is IP address >>> clash on the local network. I suggest we just change the code in question t >o >>> ignore clashes over 0.0.0.0 address only. >> >> No, don't do that, anyone arping 0.0.0.0 on any network around here >> I sure as heck want to know about it asap! Someone someplace on >> that stupid telco's DSL bridged network is mis-configured and >> sending out arp messages for the 0 addresses. Easy enough to >> cause though: >> >> ifconfig xx0 0.0.0.0 up >> >> should do the trick... >> >-- >E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]> >Date: 07-Apr-00 >Time: 14:35:14 >-- > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
I have the same impression fom reading dhclient sources. On 07-Apr-00 David Holloway wrote: > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. > -- E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]> Date: 07-Apr-00 Time: 15:44:39 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
> FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT > in order to bring interface up. Windows seems to do that as well or > there is no sane explanation for the relatively big number of these nasty > messages I am getting every time MediaOne network goes down and several PCs > sharing the same cable network segment attempt to renew their lease at the same > time. Ahhh... then perhaps a better fix is to change the gratitious arp routine to _not_ emit the bogus arp who-has arp-i-am when an interface is ifconfig'ed to 0.0.0.0 rather than cause the error logging code to be disabled? > > > On 07-Apr-00 Rodney W. Grimes wrote: > >> The message in question can be extremely useful in case there is IP address > >> clash on the local network. I suggest we just change the code in question to > >> ignore clashes over 0.0.0.0 address only. > > > > No, don't do that, anyone arping 0.0.0.0 on any network around here > > I sure as heck want to know about it asap! Someone someplace on > > that stupid telco's DSL bridged network is mis-configured and > > sending out arp messages for the 0 addresses. Easy enough to > > cause though: > > > > ifconfig xx0 0.0.0.0 up > > > > should do the trick... > > > -- > E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]> > Date: 07-Apr-00 > Time: 14:35:14 > -- > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Perl 5.6.0
Mark, I had some free time today so I started converting perl 5.6.0 to bmake. So far, I've gotten libperl to build and plan to keep at the rest of it. Given my schedule, it will probably take me another week to get the build right and another week or so to test its integration with build/installworld. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville [EMAIL PROTECTED] PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
> > > The message in question can be extremely useful in case there is IP address > > > clash on the local network. I suggest we just change the code in question to > > > ignore clashes over 0.0.0.0 address only. > > > > No, don't do that, anyone arping 0.0.0.0 on any network around here > > I sure as heck want to know about it asap! > > Then use a tool designed for the job. You'll only get this message on a > system that's a DHCP client and currently trying to get a lease. I don't > think that you would ever get any utility from the code as it stands, so > the change is not going to affect you. I get plenty of utility from it as it stands. Any time I see one of these in a syslog I go track it down and shoot the cause. > (Note that if you were to configure a system to listen on 0.0.0.0 in > order to use this message, you would then be arping for 0.0.0.0, which > would appear to defeat your purpose.) My use of the message has nothing to do with wanting to use 0.0.0.0, it's another part of the diagnostics used in maintaining networks for people. Knowing that someone is arping 0.0.0.0 lets me know someone has jacked into one of the networks and trying to either use DHCP or has mis-configured thier box, or is trying to hack. I won't object to the change if a sysctl knob is put around it, that defaults to the way things are now, if someone doesn't care to see these messages due to being on borked networks, fine, let them turn it off. > Can I kindly suggest that you go find a bridge or a dam or some > gun-control law to go oppose for a few months? This random sniper > activity is pretty irritating. 8( It is not random sniper activity. I've been on this list since it was created. I respond when I have something to say and am silent when I have nothing to say. Also that comment is un-called for, it's on the edge of policy violation, and I expect to be respected, no matter how much you may dislike me. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
> No... Yes... that is just the type of thing the link local RFC reserved address space is for. > In message <[EMAIL PROTECTED]>, Mathew Kanner writes: > >On Apr 07, Donn Miller wrote: > >> Since I started using a cable modem and dhclient, my system has been > >> literally overwhelmed with messages like: > >> > >> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > >> > > > > I haven't tried this but how about changing the > >/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes up > >the interface. > > > > --Mat > > > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] > >with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new device/bus stuff
> Is there a howto on how to convert drivers from the old to new
> form?
Hmmm, I would be interested too. I would like to convert the if_ar
and if_sr drivers, but they are not as straight foward as the "normal"
drivers, because a chip can have two channels and a card can have two
chips. Or maybe I'm just thinking too complicated about it?
>
> for example if_sr.c no longer shows up (or is even probed) in
> 4.0-stable. I've looked here and there but I can't figure out if there
> is some ISA_SHIM option needed (it's not in LINT if so).
Oops, I forgot about the if_sr driver. Just change the line
struct isa_driver srdriver = {srprobe, srattach_isa, "src"};
to
struct isa_driver srdriver = {srprobe, srattach_isa, "sr"};
I'll do it when I remove all the frame relay hooks out of the driver.
It has never been used outside SDL and they are not interested in
make it available. If anyone want to use frame relay they can use
the netgraph stuff.
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
4.0 problems...
Ciao! I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev and new /etc but now I'm getting these errors: rey:~/Sources/gnustep/core/base> uname -a FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03 CEST 2000 [EMAIL PROTECTED]:/mnt/amy/lpub/freebsd/usr/obj/mnt/amy/lpub/freebsd/usr/src/sys/rey i386 rey:/usr/home/mirko> top top: nlist failed rey:/usr/home/mirko> vmstat vmstat: undefined symbols: _cp_time _kmemstatistics _bucket _zlist Any ideas ? Thanks. -- Bye, Mirko <[EMAIL PROTECTED]> (NeXTmail, MIME) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl 5.6.0?
In message <[EMAIL PROTECTED]> Anton Berezin writes: : It is an issue of personal relationships and politics, not the technical : one. Tom Christiansen uses OpenBSD and advocates Perl to it (and other : way around). tchrist lives in Boulder, as does millert (Todd Miller) and the high tech comminuty here is tight nit. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new device/bus stuff
In message <[EMAIL PROTECTED]> Julian Elischer writes: : Is there a howto on how to convert drivers from the old to new : form? Not completely. Just look at ep or ed drivers and do it the same way :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 problems...
You wrote: > > rey:/usr/home/mirko> top > > top: nlist failed > > rey:/usr/home/mirko> vmstat > > vmstat: undefined symbols: > > _cp_time _kmemstatistics _bucket _zlist > > I heard rumors that this problem occurs when you doesn't use /boot/loader to > boot your > kernel. If so, it is bad practice and totally unsupported. Some day you > wouldn't be able even boot it this way. Hmmm... Here the only not standard thing is the mbr that comes from NeXT. If I remember correctly the only time I have updated the loader was at the beginning of the 3.0 era. -- Bye, Mirko <[EMAIL PROTECTED]> (NeXTmail, MIME) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 problems...
I had this problem a week ago. It was caused by my booting the kernel directly. 0:da(0,a)/kernel Using 0:da(0,a)/boot/loader cures the symptoms. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
"Rodney W. Grimes" <[EMAIL PROTECTED]> wrote: >David Holloway <[EMAIL PROTECTED]> wrote: >>>Mathew Kanner wrote: >>>I haven't tried this but how about changing the >>>/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes >>>up the interface. >> >> No... > >Yes... that is just the type of thing the link local RFC reserved address >space is for. No... IP address 0 is reserved for "me" so its use in DHCP makes sense. Tony. -- f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED] 393 dirt clods in your fuel rods To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
lockd-0.2 released!
I apologize profusely for the delay of this, but lockd-0.2 is out. The URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2.tar.gz A couple of notes on this release: 1) the statd hooks to lockd are not yet done (or started) 2) you need a patched libc (for XDR64 types). I have included the xdr patch as part of this release, you need to do the following to apply it: > cd /usr/src/lib/libc/xdr > patch -- David Cross | email: [EMAIL PROTECTED] Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
On Fri, 7 Apr 2000, David Holloway wrote: > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. Yes, RFC2131 clause 4.1 says: DHCP messages broadcast by a client prior to that client obtaining its IP address must have the source address field in the IP header set to 0. RFC951 clause 7.1 says the same thing for BOOTP (though BOOTP and DHCP are really the same protocol). However, this isn't really an excuse for issuing ARP with a source address of zero: the initial DHCP exchange is done with broadcasts (so doesn't need ARP), and after that the address is known. The problem presumably arises due to other traffic trying to go out while DHCP is still configuring the interface. This is analgous to the situation with PPP and dynamic assignment - and there isn't an easy solution because by the time you have a packet in your hand it is much too late to fix everything (you've probably got a socket bound to the bogus address, for example). On Fri, 7 Apr 2000, Rodney W. Grimes wrote: > > Ahhh... then perhaps a better fix is to change the gratitious arp > routine to _not_ emit the bogus arp who-has arp-i-am when an interface > is ifconfig'ed to 0.0.0.0 rather than cause the error logging code to be > disabled? The fix you suggest appears to have been implemented long ago: === RCS file: /repository/src/sys/netinet/if_ether.c,v retrieving revision 1.39 retrieving revision 1.40 diff -r1.39 -r1.40 34c34 < * $Id$ --- > * $Id: if_ether.c,v 1.39 1997/02/22 09:41:24 peter Exp $ 633,634c633,635 < arprequest(ac, &(IA_SIN(ifa)->sin_addr.s_addr), < &(IA_SIN(ifa)->sin_addr.s_addr), ac->ac_enaddr); --- > if (ntohl(IA_SIN(ifa)->sin_addr.s_addr) != INADDR_ANY) > arprequest(ac, &(IA_SIN(ifa)->sin_addr.s_addr), >&(IA_SIN(ifa)->sin_addr.s_addr), ac->ac_enaddr); It is still appropriate to fix the error logging code: saying "xxx is using the same address as me" when the address in question is 0.0.0.0 is not useful: this _isn't_ a general catch for people ARP-ing for zero - it only serves that purpose when the local machine is also mis-configured. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
> > On Fri, 7 Apr 2000, David Holloway wrote: > > > I say with 99% certainty that assigning 0.0.0.0 to > > the interface is a requirement of dhcp. > > > > You can't stop using it and expect dhcp to work. > > Yes, RFC2131 clause 4.1 says: > >DHCP messages broadcast by a client prior to that client obtaining >its IP address must have the source address field in the IP header >set to 0. > > RFC951 clause 7.1 says the same thing for BOOTP (though BOOTP and DHCP are > really the same protocol). > > > However, this isn't really an excuse for issuing ARP with a source address > of zero: the initial DHCP exchange is done with broadcasts (so doesn't > need ARP), and after that the address is known. The problem presumably > arises due to other traffic trying to go out while DHCP is still > configuring the interface. If you look at the original error message, you'll note that it's actually due to seeing another packet which claims the same Ip address. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lockd-0.2 released!
This might be a bit touchy, but I'm rather curious -- how will the BSDI merger affect your lockd work? It seems like your work on lockd (esp. client side & statd interoperation issues) could be speeded up if you had access to the BSDI sources.. Cheers, Drew -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 problems...
On Fri, 7 Apr 2000, Thomas D. Dean wrote: > I had this problem a week ago. > > It was caused by my booting the kernel directly. > > 0:da(0,a)/kernel > > Using > > 0:da(0,a)/boot/loader > > cures the symptoms. Ohhh!! This explains why i get the same top: nlist failed error in 5.0. That machine's BIOS won't boot the hdd for some reason (beats the heck out o me, worked a few days ago), so i use a boot disk to boot FreeBSD 5.0 and Win2k. I just use 0:ad(0,a)/kernel. No wonder :) martin. -- Martin Minkus aka DiSKiLLeR Email: [EMAIL PROTECTED] Web: http://www.diskiller.net I live in a world of paradox... my willingness to destroy is your chance for improvement, my hate is your faith, my failure is your victory - a victory that won't last. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 problems...
Thomas D. Dean wrote: > > I had this problem a week ago. > > It was caused by my booting the kernel directly. > > 0:da(0,a)/kernel > > Using > > 0:da(0,a)/boot/loader > > cures the symptoms. There's a PR on it, including a patch. See http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17422 The patch works for me just fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP problem? (was: Re: [usb-bsd] USB To Do list)
>What does it say before this info? In dmesg.boot (after `boot -v' at the loader prompt): uhci0: port 0xe000-0xe01f irq 15 at device 7.2 on pci0 uhci0: LegSup = 0x0010 uhci_run: setting run=0 uhci_run: done cmd=0x80 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Both uhci and usb drivers are statically linked to the kernel. When I connected a USB keyboard, I got the messages in my previous mail below. >Shared interrupt? No shared interrupt. Both IDE channels are disabled by BIOS, thus, irq 15 is free. After all, The USB drivers work if I run a UP kernel on the same machine. >USB does work on SMP (or at least in some cases). I know. It works on my another SMP box running 4.0-STABLE ;-< Kazu >> uhci_timeout: ii=0xc0a601c0 >> uhci_timeout: ii=0xc0a601c0 >> uhci_timeout: ii=0xc0a601c0 >> usbd_new_device: addr=2, getting first desc failed >> uhub_explore: usb_new_device failed, error=TIMEOUT >> uhub0: device problem, disabling port 1 >> >> I vaguely remember someone also reported similar problems with the SMP >> kernel in the past >> >> Interesting thing is that I have another SMP box, and its USB works fine. >> The version is 4.0-STABLE. The USB controller is VIA 83c572. >> >> Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
> I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. The Linux folks stopped doing it: 2.0 supported the net interface 0.0.0.0 IP address convention (meaning the kernel should accept all IP packets). 2.[12] don't, hence things like many bootp/dhcp configurations which used this feature break. The proper fix is to modify bootp/dhcp clients to accomplish the same thing using raw sockets instead. I think dhcpcd (http://www.phystech.com/download/dhcpcd.html>) already works this way, but bootpc hasn't been updated yet. --message from David Wragg ([EMAIL PROTECTED]) at http://www.tux.org/hypermail/linux-kernel/1999week05/0601.html __ Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 problems...
[EMAIL PROTECTED] wrote: > Ciao! > > I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev > and new /etc but now I'm getting these errors: > > rey:~/Sources/gnustep/core/base> uname -a > FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03 > CEST 2000 > >[EMAIL PROTECTED]:/mnt/amy/lpub/freebsd/usr/obj/mnt/amy/lpub/freebsd/usr/src/sys/rey > i386 > > rey:/usr/home/mirko> top > top: nlist failed > rey:/usr/home/mirko> vmstat > vmstat: undefined symbols: > _cp_time _kmemstatistics _bucket _zlist Hi, I heard rumors that this problem occurs when you doesn't use /boot/loader to boot your kernel. If so, it is bad practice and totally unsupported. Some day you wouldn't be able even boot it this way. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
lockd-0.2a released!
Oops, I seem to have made a mistake in the XDR patch that I included with lockd-0.2. I have re-rolled the patch with a corrected patch. As such, and to avoid confusion, I have re-labeled this as lockd-0.2a. Once again, the URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2a.tar.gz Have fun. -- David Cross | email: [EMAIL PROTECTED] Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
