Re: laying down tags
> > > I notice that in the last 6 months a change has occurred in how we use > > > our cvs tools, in that there's a great increase in the usage of tags. > > Would you mind giving one example where not having tags hurt us? Sure. When multiple developers are trying to work together as well as track -current, everything has to be done by hand. Case in point is the work that the VM guys want to do. It would be alot easier for both the developers *AND* the testers to share code this way. This also makes it much easier for the developer to 'merge' in changes made to the main branch, rather than having to hand-merge it in everytime, build diffs, and re-distribute them. The other developers then need to back-out the original diffs, re-apply the new diffs, which is alot more work. With CVS, this is done *ONCE* for each change (by CVS), hence the amount of work to help out is much less. What 'cheaper' way could this kind of easy integration be done, short of using the 'magic' branch tags in the FreeBSD CVS version that I don't if anyone has ever used because I don't think anyone knows exactly if it works, and how to make it work. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: laying down tags
On Mon, 21 Jun 1999, Nate Williams wrote: > > > > I notice that in the last 6 months a change has occurred in how we use > > > > our cvs tools, in that there's a great increase in the usage of tags. > > > > Would you mind giving one example where not having tags hurt us? > > > Sure. When multiple developers are trying to work together as well as > track -current, everything has to be done by hand. Case in point is the > work that the VM guys want to do. It would be alot easier for both the > developers *AND* the testers to share code this way. This also makes it > much easier for the developer to 'merge' in changes made to the main > branch, rather than having to hand-merge it in everytime, build diffs, > and re-distribute them. > > The other developers then need to back-out the original diffs, re-apply > the new diffs, which is alot more work. With CVS, this is done *ONCE* > for each change (by CVS), hence the amount of work to help out is much > less. > > What 'cheaper' way could this kind of easy integration be done, short of > using the 'magic' branch tags in the FreeBSD CVS version that I don't if > anyone has ever used because I don't think anyone knows exactly if it > works, and how to make it work. OK, now I see the light. I've had a lot of people responding, but all the other responses could be covered by the use of date checkouts. This makes sense. I get very stubborn when I'm given (what appears to me to be) a bogus argument, even if the ultimate conclusion is right. The reason given for the conclusion has to hold water. > > > > Nate > +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Remote serial gdb--status?
On Sun, 20 Jun 1999, Justin T. Gibbs wrote: > It looks like isa/sio.c still won't allow you to set a port as both > a low-level console and the gdb port. I could not get remote gdb > to work correctly after the sio probe without designating the port > for low-level console I/O. Now that I've done that, I can't debug > at 115200 any more. 38400 seems to work for me, but that is with > only minimal testing. Who broke remote debugging in sio? This > is a critical tool we can't afford to have broken... 8-( Kirk.. I had a differnt set of patches to do the sam ething, but he took a different approach. I'm sure th breakage is unintentional.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NFS Test patch.. Anyone tested it?
Matthew Dillon wrote: > > Here's the location: > > http://www.backplane.com/FreeBSD4/ > > It's in the 'NFS bugs first found by David E. Cross' section. > I've looked it over a bit and can't see any major problems.. and it definitly does fix some problems.. Has anyone tried it in a heavy server environment? if so, any problems? It's running ok here but it's only very lightly tested in our environment. I'd like to get it checked in if it really is an improvement julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS Test patch.. Anyone tested it?
I have not tested, but I also gave it a very good look, and it looks solid. I would certainly like to see it in -current for some real life testing and then MFC-ed at the earliest convience :). Currently we are running off of some patches that I have written... that scares me, alot :) I would love to put those to death.. On the other hand we are rapidly approaching 5 days of uptime (the average before was 1.54 days, usually the server woiuld hit arround 2.5 and then we would get a couple of reboots on the same day) -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 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: laying down tags
> I get very stubborn when I'm given (what appears to me to be) a bogus > argument, even if the ultimate conclusion is right. The reason given > for the conclusion has to hold water. I figured somebody else would jump on this one, which is why I never bothered to respond myself. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
what's different with AHC between -stable and -current?
I have 3 AHC devices that work great under -STABLE, but -CURRENT doesn't even acknowledge they exist. GENERIC kernels on both. Here is the boot information from the working -STABLE system: Probing for devices on PCI bus 1: ahc0: rev 0x00 int a irq 21 on pci1.4.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 22 on pci1.6.0 ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2: rev 0x03 int a irq 20 on pci1.8.0 ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs -CURRENT sees nothing. What additional information will I need to provide? -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 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: what's different with AHC between -stable and -current?
David E. Cross wrote... > I have 3 AHC devices that work great under -STABLE, but -CURRENT doesn't > even acknowledge they exist. GENERIC kernels on both. Here is the boot > information from the working -STABLE system: > > Probing for devices on PCI bus 1: > ahc0: rev 0x00 int a irq 21 on pci1.4.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc1: rev 0x00 int a irq 22 on pci1.6.0 > ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc2: rev 0x03 int a irq 20 on pci1.8.0 > ahc2: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs > > -CURRENT sees nothing. > > What additional information will I need to provide? I suspect this has something to do with devices on your second PCI bus not getting probed under -current. Perhaps your bridge chip isn't getting probed properly. Verbose dmesg output and the output of 'pciconf -l' mailed to the list might help folks figure out what's going on. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: audio-Device gone mute
Oliver Fromme <[EMAIL PROTECTED]> wrote: > This sounds like a bug in the device driver. If it is, then the driver succeeds into getting the card into a state it can't recover from. I rebooted and the problem persisted. It actually took a powercycle to make the card operational again. I'll see whether this repeats itself. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] carpe librum: books 'n' reviews http://www.carpe.com/buch/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP!: syscons update comming up
In the next few hours I will commit a bunch of changes to syscons console driver. This is the second phase of syscons reorganization. Here are some warnings :) 1) Because a few new files will be added to the source tree, you will need to run config(8) on your kernel configuration file before compiling a new kernel. Most of you don't need to update the kernel configuration file itself. However, some of you may have to add the following options. options SC_PIXEL_MODE Syscons has supported the raster console mode (VESA 800x600) by default. This is now an optional feature, and must be explicitly enabled by SC_PIXEL_MODE. If you have been using this mode, add the above option. options SC_DFLT_FONT makeoptions "SC_DFLT_FONT=_font_name_" This new option replaces the existing STD8X16FONT option which loads the specified 16-line font. The new option will load not only 16-line font, but also 14- and 8- line font. 2) Recompile all screen savers and splash screen modules, because some header files will be changed. 3) Optionally update kbdcontrol and vidcontrol. If you regularly do "make world", you will be Ok. This is not mandatory because old binaries will still work with the new kernel. That's all. If you find any difficulties or problems, please report in the -current mailing list. Kazu [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS Test patch.. Anyone tested it?
Julian Elischer writes: > Matthew Dillon wrote: > > > > Here's the location: > > > > http://www.backplane.com/FreeBSD4/ > > > > It's in the 'NFS bugs first found by David E. Cross' section. > > > > > I've looked it over a bit and can't see any major problems.. > and it definitly does fix some problems.. > > Has anyone tried it in a heavy server environment? > if so, any problems? It's running ok here but it's only > very lightly tested in our environment. > > I'd like to get it checked in if it really is an improvement > > julian I'm in the process of deploying a box with these patches. It will be used to serve a large "scratch" filesystem to a large number of heterogenous clients. I anticipate that it should get beaten on fairly hard. In a few days, I'll let you (and Matt) know how its going. 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: ROOTDEVNAME error in conf/LINT
Doug White schrieb: > > Some PC BIOSes won't boot a disk without a MS partition table. Try > booting a dangerously dedicated disk on a Phoenix machine and you'll see > what I mean. Hmm, I remember having exact this problem with a machine (Phoenix BIOS). After some hacks to the secondary boot I was able to boot from the dangerous dedicated disk, though. Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NFS Test patch.. Anyone tested it?
Julian Elischer writes:
> Matthew Dillon wrote:
> >
> > Here's the location:
> >
> > http://www.backplane.com/FreeBSD4/
> >
> > It's in the 'NFS bugs first found by David E. Cross' section.
> >
>
>
> I've looked it over a bit and can't see any major problems..
> and it definitly does fix some problems..
>
> Has anyone tried it in a heavy server environment?
> if so, any problems? It's running ok here but it's only
> very lightly tested in our environment.
>
> I'd like to get it checked in if it really is an improvement
>
OK. First minor problem & fix:
Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3
mount of an nfs server with these patches applied. V2 mounts still
seem to work.
It turns out that this is because when a solaris 2.7 host does an
NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug
in nfssvc_nfsd. The following patch, applied in addtion to the diffs
above, corrects the problem:
Index: nfs_syscalls.c
===
RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v
retrieving revision 1.49
diff -u -b -B -r1.49 nfs_syscalls.c
--- nfs_syscalls.c 1999/04/27 11:17:52 1.49
+++ nfs_syscalls.c 1999/06/22 19:32:26
@@ -651,7 +651,7 @@
slp, nfsd->nfsd_procp, &mreq);
if (mreq == NULL)
break;
- if (error) {
+ if (error != 0 && error != NFSERR_RETVOID) {
if (nd->nd_procnum != NQNFSPROC_VACATED)
nfsstats.srv_errs++;
nfsrv_updatecache(nd, FALSE, mreq);
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: NFS Test patch.. Anyone tested it?
Ok I 've incorporated that into the patch set I have ready to commit..
I've also been playing in 3.x
The patches apply almost cleanly there, except for 3 small problems that
I'm fixing by hand..
I'll then make a 3.x version of the patches available.
Hopefully people can start testing that..
julian
On Tue, 22 Jun 1999, Andrew Gallatin wrote:
>
> Julian Elischer writes:
> > Matthew Dillon wrote:
> > >
> > > Here's the location:
> > >
> > > http://www.backplane.com/FreeBSD4/
> > >
> > > It's in the 'NFS bugs first found by David E. Cross' section.
> > >
> >
> >
> > I've looked it over a bit and can't see any major problems..
> > and it definitly does fix some problems..
> >
> > Has anyone tried it in a heavy server environment?
> > if so, any problems? It's running ok here but it's only
> > very lightly tested in our environment.
> >
> > I'd like to get it checked in if it really is an improvement
> >
>
> OK. First minor problem & fix:
>
> Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3
> mount of an nfs server with these patches applied. V2 mounts still
> seem to work.
>
> It turns out that this is because when a solaris 2.7 host does an
> NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug
> in nfssvc_nfsd. The following patch, applied in addtion to the diffs
> above, corrects the problem:
>
> Index: nfs_syscalls.c
> ===
> RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v
> retrieving revision 1.49
> diff -u -b -B -r1.49 nfs_syscalls.c
> --- nfs_syscalls.c 1999/04/27 11:17:52 1.49
> +++ nfs_syscalls.c 1999/06/22 19:32:26
> @@ -651,7 +651,7 @@
> slp, nfsd->nfsd_procp, &mreq);
> if (mreq == NULL)
> break;
> - if (error) {
> + if (error != 0 && error != NFSERR_RETVOID) {
> if (nd->nd_procnum != NQNFSPROC_VACATED)
> nfsstats.srv_errs++;
> nfsrv_updatecache(nd, FALSE, mreq);
>
>
>
> Cheers,
>
> Drew
> --
> Andrew Gallatin, Sr Systems Programmerhttp://www.cs.duke.edu/~gallatin
> Duke University Email: [EMAIL PROTECTED]
> Department of Computer SciencePhone: (919) 660-6590
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: NFS Test patch.. Anyone tested it?
I'll be happy to test a 3.2-STABLE version of the patches as soon as they
become available.
Tom
On Tue, 22 Jun 1999, Julian Elischer wrote:
> Ok I 've incorporated that into the patch set I have ready to commit..
> I've also been playing in 3.x
>
> The patches apply almost cleanly there, except for 3 small problems that
> I'm fixing by hand..
>
> I'll then make a 3.x version of the patches available.
> Hopefully people can start testing that..
>
> julian
>
>
> On Tue, 22 Jun 1999, Andrew Gallatin wrote:
>
> >
> > Julian Elischer writes:
> > > Matthew Dillon wrote:
> > > >
> > > > Here's the location:
> > > >
> > > > http://www.backplane.com/FreeBSD4/
> > > >
> > > > It's in the 'NFS bugs first found by David E. Cross' section.
> > > >
> > >
> > >
> > > I've looked it over a bit and can't see any major problems..
> > > and it definitly does fix some problems..
> > >
> > > Has anyone tried it in a heavy server environment?
> > > if so, any problems? It's running ok here but it's only
> > > very lightly tested in our environment.
> > >
> > > I'd like to get it checked in if it really is an improvement
> > >
> >
> > OK. First minor problem & fix:
> >
> > Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3
> > mount of an nfs server with these patches applied. V2 mounts still
> > seem to work.
> >
> > It turns out that this is because when a solaris 2.7 host does an
> > NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug
> > in nfssvc_nfsd. The following patch, applied in addtion to the diffs
> > above, corrects the problem:
> >
> > Index: nfs_syscalls.c
> > ===
> > RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v
> > retrieving revision 1.49
> > diff -u -b -B -r1.49 nfs_syscalls.c
> > --- nfs_syscalls.c 1999/04/27 11:17:52 1.49
> > +++ nfs_syscalls.c 1999/06/22 19:32:26
> > @@ -651,7 +651,7 @@
> > slp, nfsd->nfsd_procp, &mreq);
> > if (mreq == NULL)
> > break;
> > - if (error) {
> > + if (error != 0 && error != NFSERR_RETVOID) {
> > if (nd->nd_procnum != NQNFSPROC_VACATED)
> > nfsstats.srv_errs++;
> > nfsrv_updatecache(nd, FALSE, mreq);
> >
> >
> >
> > 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
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: NFS Test patch.. Anyone tested it?
As I said on -hackers..
>
> There is a backported version of MAtt's NFS fixes at:
>
> ftp://ftp.whistle.com/pub/julian/nfs-3.diffs
>
> These include Andrew's fix to the fix
>
> results apreciated.
> If you've been having NFS server side problems on 3.x check these out..
>
> julian
>
>
On Tue, 22 Jun 1999, Tom Bartol wrote:
>
> I'll be happy to test a 3.2-STABLE version of the patches as soon as they
> become available.
>
> Tom
>
>
> On Tue, 22 Jun 1999, Julian Elischer wrote:
>
> > Ok I 've incorporated that into the patch set I have ready to commit..
> > I've also been playing in 3.x
> >
> > The patches apply almost cleanly there, except for 3 small problems that
> > I'm fixing by hand..
> >
> > I'll then make a 3.x version of the patches available.
> > Hopefully people can start testing that..
> >
> > julian
> >
> >
> > On Tue, 22 Jun 1999, Andrew Gallatin wrote:
> >
> > >
> > > Julian Elischer writes:
> > > > Matthew Dillon wrote:
> > > > >
> > > > > Here's the location:
> > > > >
> > > > > http://www.backplane.com/FreeBSD4/
> > > > >
> > > > > It's in the 'NFS bugs first found by David E. Cross' section.
> > > > >
> > > >
> > > >
> > > > I've looked it over a bit and can't see any major problems..
> > > > and it definitly does fix some problems..
> > > >
> > > > Has anyone tried it in a heavy server environment?
> > > > if so, any problems? It's running ok here but it's only
> > > > very lightly tested in our environment.
> > > >
> > > > I'd like to get it checked in if it really is an improvement
> > > >
> > >
> > > OK. First minor problem & fix:
> > >
> > > Solaris 2.7 (5.7 Generic_106541-04 sun4u sparc) hosts cannot do a V3
> > > mount of an nfs server with these patches applied. V2 mounts still
> > > seem to work.
> > >
> > > It turns out that this is because when a solaris 2.7 host does an
> > > NFSv3 mount, it calls the null procedure & Matt's diffs expose a bug
> > > in nfssvc_nfsd. The following patch, applied in addtion to the diffs
> > > above, corrects the problem:
> > >
> > > Index: nfs_syscalls.c
> > > ===
> > > RCS file: /home/ncvs/src/sys/nfs/nfs_syscalls.c,v
> > > retrieving revision 1.49
> > > diff -u -b -B -r1.49 nfs_syscalls.c
> > > --- nfs_syscalls.c 1999/04/27 11:17:52 1.49
> > > +++ nfs_syscalls.c 1999/06/22 19:32:26
> > > @@ -651,7 +651,7 @@
> > > slp, nfsd->nfsd_procp, &mreq);
> > > if (mreq == NULL)
> > > break;
> > > - if (error) {
> > > + if (error != 0 && error != NFSERR_RETVOID) {
> > > if (nd->nd_procnum != NQNFSPROC_VACATED)
> > > nfsstats.srv_errs++;
> > > nfsrv_updatecache(nd, FALSE, mreq);
> > >
> > >
> > >
> > > Cheers,
> > >
> > > Drew
> > > --
> > > Andrew Gallatin, Sr Systems Programmerhttp://www.cs.duke.edu/~gallatin
> > > Duke University Email: [EMAIL PROTECTED]
> > > Department of Computer SciencePhone: (919) 660-6590
> > >
> >
> >
> >
> > 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
vinum in -current
The recent patches include a reference to "strerr()" in kernel mode... there is no such beast. -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 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: vinum in -current
On Tuesday, 22 June 1999 at 17:14:29 -0400, David E. Cross wrote: > The recent patches include a reference to "strerr()" in kernel mode... there > is no such beast. Ugh. Fixed. That's what you get for compiling before I've enabled it. Greg -- See complete headers for address, home page and phone numbers finger [EMAIL PROTECTED] for PGP public key To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vinum in -current
Ok, now that you have fixed the strerr() bug, I have another -current vinum dilema... I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var, 2048M /usr, 512M swap. each of da1 and da2 have 512M swap. I have a vinum config similiar to: disk drive1 /dev/da0s1h disk drive2 /dev/da1s1h disk drive3 /dev/da2s1h volume data plex org striped 4m sd len 5000m drive drive1 sd len 5000m drive drive2 sd len 5000m drive drive3 plex org striped 4m sd len 2000m drive drive2 sd len 2000m drive drive3 When I "vinum create" this the last plex (doesn't matter if I reverse the order of the plexes in the file, it is the last defined plex that this refers to) is always in "status: initializing", and never leaves, the sd-s of that plex are listed "empty". Also, it lists the size of the volume as 15G... *NOT* 19G. This is true even if the 15G is listed second and is in the "initializing" status. This is -CURRENT as of today. Any ideas? -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 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: vinum in -current
On Tuesday, 22 June 1999 at 22:14:55 -0400, David E. Cross wrote: > Ok, now that you have fixed the strerr() bug, I have another -current > vinum dilema... > > I have 3 disks... da0, da1, and da2. da0 has a 100M /, 200M /var, > 2048M /usr, 512M swap. each of da1 and da2 have 512M swap. > I have a vinum config similiar to: > > disk drive1 /dev/da0s1h > disk drive2 /dev/da1s1h > disk drive3 /dev/da2s1h > > volume data > plex org striped 4m > sd len 5000m drive drive1 > sd len 5000m drive drive2 > sd len 5000m drive drive3 > plex org striped 4m > sd len 2000m drive drive2 > sd len 2000m drive drive3 > > When I "vinum create" this the last plex (doesn't matter if I reverse the > order of the plexes in the file, it is the last defined plex that this > refers to) is always in "status: initializing", and never leaves, the sd-s > of that plex are listed "empty". This is a feature, not a bug, and it's described in vinum(8): setupstate When creating a multi-plex volume, assume that the contents of all the plexes are consistent. This is normally not the case, and correctly you should use the init command to first bring them to a consistent state. In the case of striped and concatenated plexes, however, it does not normally cause problems to leave them inconsistent: when using a volume for a file system or a swap partition, the previous contents of the disks are not of interest, so they may be ignored. If you want to take this risk, use this keyword. It will only apply to the plexes defined immediately after the volume in the configuration file. If you add plexes to a volume at a later time, you must integrate them. > Also, it lists the size of the volume as 15G... *NOT* 19G. That's correct. > This is true even if the 15G is listed second and is in the > "initializing" status. This is -CURRENT as of today. Any ideas? I think you misunderstand what this config does. Each plex replicates the entire address space of the volume, so this gives you a 16 GB volume with the first 4 GB mirrored. I suspect that you're trying to get a non-mirrored, striped volume with a total of 19 GB. Unfortunately, you currently can't do that in a sensible manner with drives of unequal sizes. One possibility would be: disk drive1 /dev/da0h disk drive2 /dev/da1h disk drive3 /dev/da2h volume data plex org striped 512k sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive1 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive2 sd len 1000m drive drive3 sd len 1000m drive drive2 sd len 1000m drive drive3 You'll note that I've changed the stripe size from 4m to 512k; there are some indications that a larger stripe size is not beneficial, though I currently can't say why. I've also changed the names of the drives. With the old ones, you won't be able to start the volume after a reboot. To quote vinum(8): drive name option Define a drive. The option must be: device devicename Specify the device on which the drive resides. devicename must be the name of a disk compati- bility partition, for example /dev/da1e or /dev/wd3h, and it should be of type vinum. Do not use the c partition, which is reserved for the complete disk, and should be of type unused. It is currently possible to create drives on other disk devices, for example /dev/da0s1 or /dev/da0s1e, but it will not be
Re: vinum in -current
Hello Greg, If I may intrude in this discussion, I was wondering what is the correct syntax for naming vinum drives in rc.conf. I've got two drives merged and striped with vinum, but I'm not sure what to put in rc.conf vinum_conf : drive drive1 device /dev/wd1s1h drive drive2 device /dev/wd2s1h volume initial plex org striped 512b sd length 19806208b drive drive1 sd length 19806208b drive drive2 in rc.conf : Is the following correct : vinum_drives="/dev/wd1s1h /dev/wd2s1h" or should it be vinum_drives="/dev/wd1h /dev/wd2h" Big kudos for vinum TfH Greg Lehey wrote: > [SNIP] > I've also changed the names of the drives. With the old ones, you > won't be able to start the volume after a reboot. To quote vinum(8): > > drive name option > >Define a drive. The option must be: > >device devicename Specify the device on which the drive resides. >devicename must be the name of a disk compati- >bility partition, for example /dev/da1e or >/dev/wd3h, and it should be of type vinum. Do >not use the c partition, which is reserved for >the complete disk, and should be of type >unused. It is currently possible to create >drives on other disk devices, for example >/dev/da0s1 or /dev/da0s1e, but it will not be >possible to start these drives after a reboot. > > Greg > -- > See complete headers for address, home page and phone numbers > finger [EMAIL PROTECTED] for PGP public key > > 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: vinum in -current
On Wednesday, 23 June 1999 at 7:33:35 +0200, Thierry Herbelot wrote: > Greg Lehey wrote: >> > > [SNIP] > >> I've also changed the names of the drives. With the old ones, you >> won't be able to start the volume after a reboot. To quote vinum(8): >> >> drive name option >> >>Define a drive. The option must be: >> >>device devicename Specify the device on which the drive resides. >>devicename must be the name of a disk compati- >>bility partition, for example /dev/da1e or >>/dev/wd3h, and it should be of type vinum. Do >>not use the c partition, which is reserved for >>the complete disk, and should be of type >>unused. It is currently possible to create >>drives on other disk devices, for example >>/dev/da0s1 or /dev/da0s1e, but it will not be >>possible to start these drives after a reboot. > > Hello Greg, > > If I may intrude in this discussion, I was wondering what is the correct > syntax for naming vinum drives in rc.conf. > I've got two drives merged and striped with vinum, but I'm not sure what > to put in rc.conf > vinum_conf : > drive drive1 device /dev/wd1s1h > drive drive2 device /dev/wd2s1h As the man page excerpt that you quoted above shows, this is wrong. It should be /dev/wd1h and /dev/wd2h. > volume initial > plex org striped 512b > sd length 19806208b drive drive1 > sd length 19806208b drive drive2 > > in rc.conf : > Is the following correct : > vinum_drives="/dev/wd1s1h /dev/wd2s1h" > or should it be > vinum_drives="/dev/wd1h /dev/wd2h" In fact, it should be vinum_drives="" start_vinum=YES That way, vinum will start all drives. > Big kudos for vinum Thanks. Greg -- See complete headers for address, home page and phone numbers finger [EMAIL PROTECTED] for PGP public key To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vinum in -current
Neither is correct, you want to leave the parition identifier ("h") off of
it. When vinum starts it scans all the partitions by attempting to add
one of [abdefgh] to the end of whatever you give it. If you give it
"wd0s1h" it will look for "wd0s1ha ... wd0s1hh" and never find it.
--
David Cross | email: [EMAIL PROTECTED]
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
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: vinum in -current
On Wednesday, 23 June 1999 at 1:50:19 -0400, David E. Cross wrote:
> Neither is correct, you want to leave the parition identifier ("h") off of
> it. When vinum starts it scans all the partitions by attempting to add
> one of [abdefgh] to the end of whatever you give it. If you give it
> "wd0s1h" it will look for "wd0s1ha ... wd0s1hh" and never find it.
I assume this is a reply to Thierry's question:
> Is the following correct :
> vinum_drives="/dev/wd1s1h /dev/wd2s1h"
> or should it be
> vinum_drives="/dev/wd1h /dev/wd2h"
I stated that the correct answer was to set the start_vinum variable,
but there are reasons to use vinum_drives (otherwise it wouldn't be
there). You use vinum_drives to specify that you want to start only
certain drives, not all of them. In this case, yes, it should be
/dev/wd1 and /dev/wd2 (or /dev/wd1s1 and /dev/wd2s1 if you insist).
There should be no partition letter at the end. Note also that vinum
will not use partition c.
Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ktrace causes kernel panic
Using a recent (few days) -current I had a process lock up on me last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a while. When I issued a 'ktrace -C' in another screen, everything froze and the kernel panic'ed. I dropped to the debugger on the console and it was definintely ktrace that caused the panic. There are at least two possibilities I can think of for this problem, one being that ktrace.out filled up the root partition (although I'm 99% sure that I was in the expansive /usr fs at the time) or it's also very possible that the process I was tracing exited while I was trace'ing it. However to my mind this shoudln't have caused the kernel to panic either way. If this is a known problem I won't mess with it any more, since the circumstance that caused the problem would be near impossible to reproduce. However if it's something that needs to be tracked down I'll do what I can to help. Thanks, Doug PS, it's a multi-processor system with an SMP kernel if that makes any difference. -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New ATA stuff, questions and comment
First a question, namely what is the current state of the ATA drivers in -current? Are they reliable (where "reliable" goes by -current terms obviously)? I finally am in a position to test them with a new workstation that has IDE disks, so I thought I'd give it a go. Also, I was trying to set up the CD player on this workstation and had a difficult time with the "atapicd" vs. "acd" stuff, so I finally just went back to the old w* stuff. Basically, LINT mentions atapicd0, but both devices.i386 and majors.i386, as well as /dev/MAKEDEV mention acd. Any comments or insights are welcome. Thanks, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On Wed, 23 Jun 1999, Doug wrote: > First a question, namely what is the current state of the ATA > drivers in -current? Are they reliable (where "reliable" goes by -current > terms obviously)? I finally am in a position to test them with a new > workstation that has IDE disks, so I thought I'd give it a go. For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, I'm happy with the atapi-fd driver :) See: ata-pci0: irq 0 at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ta0: master: setting up UDMA2 mode on Aladdin chip OK ad0: ATA-4 disk at ata0 as master ad0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: master: setting up WDMA2 mode on Aladdin chip OK ad1: ATA-? disk at ata1 as master ad1: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=-1 ad1: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata0 as slave acd0: drive speed 2067KB/sec, 128KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata1 as slave afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: Medium: Unknown media (0x0) > > Also, I was trying to set up the CD player on this workstation and > had a difficult time with the "atapicd" vs. "acd" stuff, so I finally just > went back to the old w* stuff. Basically, LINT mentions atapicd0, but both > devices.i386 and majors.i386, as well as /dev/MAKEDEV mention acd. A device name isn't necessarily the same as a device node, you know. > > Any comments or insights are welcome. > > Thanks, > > Doug > -- > On account of being a democracy and run by the people, we are the only > nation in the world that has to keep a government four years, no matter > what it does. > -- Will Rogers > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On Wed, 23 Jun 1999, Brian F. Feldman wrote: > On Wed, 23 Jun 1999, Doug wrote: > > > First a question, namely what is the current state of the ATA > > drivers in -current? Are they reliable (where "reliable" goes by -current > > terms obviously)? I finally am in a position to test them with a new > > workstation that has IDE disks, so I thought I'd give it a go. > > For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, > I'm happy with the atapi-fd driver :) See: Great news, thanks. > A device name isn't necessarily the same as a device node, you know. Actually I do know that, but I've never come across a situation in freebsd where I would call something one thing in my kernel config file and something else in /dev. If you are saying that I ought to include atapicd in my kernel config and use the acdN device node, that's all I need to know, but it does bring up the question of why the two things are different. It seems like unecessary obfuscation to me. Thanks for your response, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On Wed, 23 Jun 1999, Doug wrote: > On Wed, 23 Jun 1999, Brian F. Feldman wrote: > > > On Wed, 23 Jun 1999, Doug wrote: > > > > > First a question, namely what is the current state of the ATA > > > drivers in -current? Are they reliable (where "reliable" goes by -current > > > terms obviously)? I finally am in a position to test them with a new > > > workstation that has IDE disks, so I thought I'd give it a go. > > > > For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, > > I'm happy with the atapi-fd driver :) See: > > Great news, thanks. > > > A device name isn't necessarily the same as a device node, you know. > > Actually I do know that, but I've never come across a situation in > freebsd where I would call something one thing in my kernel config file > and something else in /dev. If you are saying that I ought to include > atapicd in my kernel config and use the acdN device node, that's all I > need to know, but it does bring up the question of why the two things are > different. It seems like unecessary obfuscation to me. atapi-cd, atapi-fd, atapi-disk are more descriptive (self-explanatory) for the config file. acd, afd, and ad are shorter, in the concise "/dev/node" way. Complain to Soren if you don't like it ;) > > Thanks for your response, > > Doug > -- > On account of being a democracy and run by the people, we are the only > nation in the world that has to keep a government four years, no matter > what it does. > -- Will Rogers > > Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ktrace causes kernel panic
On Wed, 23 Jun 1999, Doug wrote: > Using a recent (few days) -current I had a process lock up on me > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > while. When I issued a 'ktrace -C' in another screen, everything froze and > the kernel panic'ed. I dropped to the debugger on the console and it was > definintely ktrace that caused the panic. To add excitement to this, I worked on it for a while (in part because I still need to ktrace this process, and in part because I wanted to see if I could reproduce the crash) and ktrace is not performing the way I remember it. The last time I used ktrace (which was about a year ago) all I had to do was 'ktrace -p pid#' and it would attach to that process, and not let go till I killed it, or the process died. In my current attempt at it, each time I do the ktrace command it dumps about 1.8M worth of ktrace.out, then ktrace exits, even though the process is still alive and kicking. I don't see anything that I might be missing from the man page, so any insight would be appreciated. Otherwise I will call this a bug and send a PR. Thanks, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
>For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, >I'm happy with the atapi-fd driver :) See: UDMA mode 2 is normal 33 MB/sec UDMA mode and has been supported by the old driver for about 2 years now (although not for all chipsets). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On Thu, 24 Jun 1999, Bruce Evans wrote: > >For me, it's very reliable. It even supports Ultra DMA 2 mode! And of course, > >I'm happy with the atapi-fd driver :) See: > > UDMA mode 2 is normal 33 MB/sec UDMA mode and has been supported by the > old driver for about 2 years now (although not for all chipsets). I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being very nice :) The old driver never did any form of DMA for me, much less UDMA, so I'm very glad to have the ATA drivers. > > Bruce > Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ktrace causes kernel panic
On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote: > Using a recent (few days) -current I had a process lock up on me > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > while. When I issued a 'ktrace -C' in another screen, everything froze and > the kernel panic'ed. I dropped to the debugger on the console and it was > definintely ktrace that caused the panic. So where's the dump? A stack trace would be informative. Greg -- See complete headers for address, home page and phone numbers finger [EMAIL PROTECTED] for PGP public key To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ktrace causes kernel panic
On Thu, 24 Jun 1999, Greg Lehey wrote: > On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote: > > Using a recent (few days) -current I had a process lock up on me > > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a > > while. When I issued a 'ktrace -C' in another screen, everything froze and > > the kernel panic'ed. I dropped to the debugger on the console and it was > > definintely ktrace that caused the panic. > > So where's the dump? A stack trace would be informative. Sorry, forgot to mention that I didn't have time to write down the trace because the boss was breathing down my neck to get the thing back on line. I remember distinctly that the second to last function was ktrace() if that's any help. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ktrace causes kernel panic
On Wednesday, 23 June 1999 at 18:11:21 -0700, Doug wrote: > On Thu, 24 Jun 1999, Greg Lehey wrote: > >> On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote: >>> Using a recent (few days) -current I had a process lock up on me >>> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a >>> while. When I issued a 'ktrace -C' in another screen, everything froze and >>> the kernel panic'ed. I dropped to the debugger on the console and it was >>> definintely ktrace that caused the panic. >> >> So where's the dump? A stack trace would be informative. > > Sorry, forgot to mention that I didn't have time to write down the > trace because the boss was breathing down my neck to get the thing back on > line. I remember distinctly that the second to last function was ktrace() > if that's any help. Not much. You'll need to get a dump. Greg -- See complete headers for address, home page and phone numbers finger [EMAIL PROTECTED] for PGP public key To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCM sound problems
I have a problem with the way my soundcard behaves. It stutters when using mpg123, where a small segment of music is played a number of time before moving onto the next segment. Looking at the code, I see that the DMA is set up in auto mode. I can only surmise that interrupts are not being serviced - perhaps we're sleeping at too high a priority? My machine's bios is set up believing that it has a PnP aware OS, resource allocation is automatic and all IRQs are available for Pnp/PCI. My dmesg output is below, as is my machine config file Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Jun 24 00:29:17 WST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/bloop Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 399666517 Hz CPU: AMD-K6(tm) 3D processor (399.67-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping=12 Features=0x8021bf real memory = 67043328 (65472K bytes) FreeBSD Kernel Configuration Utility - Version 1.2 Type "help" for help. config> pnp 1 0 os enable port0 0x534 port2 0x220 irq0 9 drq1 3 config> quit sio0: system console avail memory = 62095360 (60640K bytes) Preloaded elf kernel "kernel" at 0xc02fe000. Probing for PnP devices: CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0x Comp ID: @@@ [0x] mss_attach 1 at 0x530 irq 9 dma 0:3 flags 0x13 pcm1 (CS423x/Yamaha/AD1816 sn 0x) at 0x530-0x537 irq 9 drq 0 flags 0x13 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: irq 11 at device 7.2 on pci0 usb0: on uhci0 uhub0 at usb0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: at device 7.3 on pci0 rl0: irq 5 at device 9.0 on pci0 rl0: Ethernet address: 00:00:e8:53:a2:3e rl0: autoneg complete, link status good (half-duplex, 10Mbps) 3DFX Voodoo 1 has mem at phys 0xe400, vir 0xc3d9b000 type 0x1, vendor 0x121a voodoo0: <3DFX Voodoo 1> at device 10.0 on pci0 vga-pci0: irq 12 at device 11.0 on pci0 ncr0: irq 10 at device 12.0 on pci0 isa0: on motherboard atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Winbond chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 ata1: unwanted interrupt 1 status = ff ds0 XXX: driver didn't set ifq_maxlen ata0: master: setting up generic WDMA2 mode OK ad0: ATA-4 disk at ata0 as master ad0: 6179MB (12656448 sectors), 12556 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: unwanted interrupt 2 status = 50 acd0: CDROM drive at ata1 as slave acd0: drive speed 687 - 6875KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 6 seconds for SCSI devices to settle sa0 at ncr0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers changing root device to wd0s4a tsleep returns 4 machine "i386" ident bloop maxusers10 options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" options PQ_LARGECACHE # color for 512k/16k cache #optionsPQ_HUGECACHE# color for 1024k/16k cache options INCLUDE_CONFIG_FILE # Include this file in kernel #config kernel root on ad0 dumps on ad0 cpu "I486_CPU" cpu "I586_CPU" # aka Pentium(tm) cpu "I686_CPU" # aka Pentium Pro(tm) options "CPU_WT_ALLOC" options "NO_F00F_HACK" options "COMPAT_43" options USER_LDT#allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options DDB options KTRACE #kernel tracing options INVARIANTS options INVARIANT_SUPPORT options PERFMON options UCONSOLE options USERCONFIG #boot -c editor options INET#Internet communications protocols pseudo-device ether #Gene
Re: PCM sound problems
Oops, forgot my pnpinfo output Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CSC4236 (0x3642630e), Serial Number 0x PnP Version 1.0, Vendor Version 5 Device Description: Crystal Codec Logical Device ID: CSC 0x630e #0 Device Description: WSS/SB TAG Start DF Good Configuration DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 - only one type (true/edge) I/O Range 0x534 .. 0x534, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x220, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Acceptable Configuration DMA: channel(s) 1 3 8-bit, not a bus master, count by byte, , Type A DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x260, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type A IRQ: 5 7 9 11 12 15 - only one type (true/edge) I/O Range 0x534 .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x388 .. 0x3f8, alignment 0x8, len 0x4 [16-bit addr] I/O Range 0x220 .. 0x300, alignment 0x20, len 0x10 [16-bit addr] TAG End DF Logical Device ID: CSC0001 0x0100630e #1 Device Description: GAME TAG Start DF Good Configuration I/O Range 0x200 .. 0x200, alignment 0x8, len 0x8 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x208 .. 0x208, alignment 0x8, len 0x8 [16-bit addr] TAG End DF Logical Device ID: CSC0010 0x1000630e #2 Device Description: CTRL I/O Range 0x120 .. 0xff8, alignment 0x8, len 0x8 [16-bit addr] Logical Device ID: CSC0003 0x0300630e #3 Device Description: MPU TAG Start DF Good Configuration IRQ: 9 - only one type (true/edge) I/O Range 0x330 .. 0x330, alignment 0x8, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 9 11 12 15 - only one type (true/edge) I/O Range 0x330 .. 0x360, alignment 0x8, len 0x2 [16-bit addr] TAG Start DF Sub-optimal Configuration I/O Range 0x330 .. 0x3e0, alignment 0x8, len 0x2 [16-bit addr] TAG End DF End Tag Successfully got 46 resources, 4 logical fdevs -- card select # 0x0001 CSN CSC4236 (0x3642630e), Serial Number 0x Logical device #0 IO: 0x0534 0x 0x0220 0x 0x 0x 0x 0x IRQ 9 0 DMA 0 3 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #2 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #3 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 # -- 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
Make world doesn't get past dhclient
Maybe I didn't get all the changes. I'm going to cvsup again and check. Thanks, ed cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o tables.o tree.o upf.o packet.o: In function `assemble_hw_header': packet.o(.text+0x8c): undefined reference to `assemble_ethernet_header' packet.o: In function `decode_hw_header': packet.o(.text+0x1b4): undefined reference to `decode_ethernet_header' *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
recent pkg_install commit
Can some one back out the recent commits in usr.sbin/pkg_install that adds ? to getopt(3) optarg string? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sc0 and serial console broken?
>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried every variation of the kernel I can think of, including GENERIC, and same thing. I finally changed to vt0 and it booted up fine. I am using the standard sio0 config with the 0x10 flag and a /boot.config file with "-h". Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.7 640/64512kB ([EMAIL PROTECTED], Wed Jun 23 22:54:06 CDT 1999) Loading /boot/defaults/loader.conf /kernel text=0x10bf98 data=0x1c27c+0x1a26c syms=[0x4+0x1c4f0+0x4+0x1efb9] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Thu Jun 24 01:19:25 CDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/TIM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 179629198 Hz CPU: Pentium Pro (179.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff real memory = 67108864 (65536K bytes) config> di zp0 No such device: zp0 Invalid command or syntax. Type `?' for help. config> di ze0 No such device: ze0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ex0 No such device: ex0 Invalid command or syntax. Type `?' for help. config> di ep0 No such device: ep0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di wt0 No such device: wt0 Invalid command or syntax. Type `?' for help. config> di scd0 No such device: scd0 Invalid command or syntax. Type `?' for help. config> di mcd0 No such device: mcd0 Invalid command or syntax. Type `?' for help. config> di matcdc0 No such device: matcdc0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> en ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> po ed0 0x300 No such device: ed0 Invalid command or syntax. Type `?' for help. config> ir ed0 5 No such device: ed0 Invalid command or syntax. Type `?' for help. config> iom ed0 0xd8000 No such device: ed0 Invalid command or syntax. Type `?' for help. config> f ed0 0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> q avail memory = 62644224 (61176K bytes) Preloaded elf kernel "kernel" at 0xc028. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028009c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 Correcting Natoma config for non-SMP Correcting Natoma config for non-SMP chip0: at device 0.0 on pci0 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 fxp0: irq 10 at device 18.0 on pci0 fxp0: Ethernet address 00:a0:c9:a0:32:ee fxp1: irq 12 at device 19.0 on pci0 fxp1: Ethernet address 00:90:27:75:59:f1 vga-pci0: irq 5 at device 20.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 1204MB (2467584 sectors), 2448 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sc0 and serial console broken?
Grrr, forgot the trap information: >From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried every variation of the kernel I can think of, including GENERIC, and same thing. I finally changed to vt0 and it booted up fine. I am using the standard sio0 config with the 0x10 flag and a /boot.config file with "-h". Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.7 640/64512kB ([EMAIL PROTECTED], Wed Jun 23 22:54:06 CDT 1999) Loading /boot/defaults/loader.conf /kernel text=0x10bf98 data=0x1c27c+0x1a26c syms=[0x4+0x1c4f0+0x4+0x1efb9] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Thu Jun 24 01:19:25 CDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/TIM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 179629198 Hz CPU: Pentium Pro (179.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff real memory = 67108864 (65536K bytes) config> di zp0 No such device: zp0 Invalid command or syntax. Type `?' for help. config> di ze0 No such device: ze0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ex0 No such device: ex0 Invalid command or syntax. Type `?' for help. config> di ep0 No such device: ep0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di wt0 No such device: wt0 Invalid command or syntax. Type `?' for help. config> di scd0 No such device: scd0 Invalid command or syntax. Type `?' for help. config> di mcd0 No such device: mcd0 Invalid command or syntax. Type `?' for help. config> di matcdc0 No such device: matcdc0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> en ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> po ed0 0x300 No such device: ed0 Invalid command or syntax. Type `?' for help. config> ir ed0 5 No such device: ed0 Invalid command or syntax. Type `?' for help. config> iom ed0 0xd8000 No such device: ed0 Invalid command or syntax. Type `?' for help. config> f ed0 0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> q avail memory = 62644224 (61176K bytes) Preloaded elf kernel "kernel" at 0xc028. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028009c. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 Correcting Natoma config for non-SMP Correcting Natoma config for non-SMP chip0: at device 0.0 on pci0 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 fxp0: irq 10 at device 18.0 on pci0 fxp0: Ethernet address 00:a0:c9:a0:32:ee fxp1: irq 12 at device 19.0 on pci0 fxp1: Ethernet address 00:90:27:75:59:f1 vga-pci0: irq 5 at device 20.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 1204MB (2467584 sectors), 2448 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa fault code = supervisor read, page not present instruction pointer = 0x8:0xc01df028 stack pointer = 0x10:0xc0294eec frame pointer = 0x10:0xc0294ef8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam kernel: type 12 trap, code=0 Stopped at sc_get_softc+0x34: testb $0x1,0xa(%eax) db> trace sc_get_softc(0,0,0,0,0) at sc_get_softc+0x34 scinit(0,0,c0979f40,0,c0964800) at scinit+0x74 sc_attach_unit(0,0,9,0,c0294f60) at sc_attach_unit+0x2b scattach(c0979f40,c0979f40,c0294f78,c01481bb,c0979f40) at scattach+0x35 DEVICE_ATTACH(c0979f40,c0979f40,c02289f0,299000,c0294f88) at DEVICE_ATTACH+0x33 de
Re: sc0 and serial console broken?
>>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried
>every variation of the kernel I can think of, including GENERIC, and same
>thing. I finally changed to vt0 and it booted up fine.
A bug was found earlier today in syscons_isa.c. Apply the following
patch to /sys/isa/syscons_isa.c and see if it works.
Kazu
Index: syscons_isa.c
===
RCS file: /src/CVS/src/sys/isa/syscons_isa.c,v
retrieving revision 1.5
diff -u -r1.5 syscons_isa.c
--- syscons_isa.c 1999/06/22 14:13:41 1.5
+++ syscons_isa.c 1999/06/24 01:24:22
@@ -79,7 +79,7 @@
static driver_t sc_driver = {
SC_DRIVER_NAME,
sc_methods,
- 1, /* XXX */
+ sizeof(sc_softc_t),
};
static sc_softc_t main_softc = { 0, 0, 0, -1, NULL, -1, NULL, };
@@ -125,7 +125,7 @@
main_softc.unit = unit;
return &main_softc;
} else {
- sc = (sc_softc_t *)devclass_get_softc(sc_devclass, unit);
+ sc = (sc_softc_t *)device_get_softc(devclass_get_device(sc_devclass,
+unit));
if (!(sc->flags & SC_INIT_DONE)) {
sc->unit = unit;
sc->keyboard = -1;
@@ -148,7 +148,7 @@
return sc;
units = devclass_get_maxunit(sc_devclass);
for (i = 0; i < units; ++i) {
- sc = (sc_softc_t *)devclass_get_softc(sc_devclass, i);
+ sc = (sc_softc_t *)device_get_softc(devclass_get_device(sc_devclass,
+i));
if (sc == NULL)
continue;
if (((adp == NULL) || (adp == sc->adp))
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: sc0 and serial console broken?
That fixed it. Thanks! Tim On Thu, Jun 24, 1999 at 04:44:50PM +0900, Kazutaka YOKOTA wrote: > >>From source cvsup on 6/23/99, the kernel traps on boot near sc0. I tried > >every variation of the kernel I can think of, including GENERIC, and same > >thing. I finally changed to vt0 and it booted up fine. > > A bug was found earlier today in syscons_isa.c. Apply the following > patch to /sys/isa/syscons_isa.c and see if it works. > > Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On Wed, 23 Jun 1999 14:16:23 MST, Doug wrote: > If you are saying that I ought to include atapicd in my kernel config > and use the acdN device node, that's all I need to know, but it does > bring up the question of why the two things are different. It seems > like unecessary obfuscation to me. It's necessary because the new ATA stuff is intended to replace the old wd/acd stuff, eventually. We don't want to use a new name for atapi-cd and you can't use both drivers, so why confuse the issue? :-) Having said that, it _is_ a confusing state of affairs if you haven't followed the history of IDE and ATAPI support in FreeBSD. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
Doug <[EMAIL PROTECTED]> writes: > On Wed, 23 Jun 1999, Brian F. Feldman wrote: > > A device name isn't necessarily the same as a device node, you know. > Actually I do know that, but I've never come across a situation in > freebsd where I would call something one thing in my kernel config file > and something else in /dev. man bpf DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
"Brian F. Feldman" <[EMAIL PROTECTED]> writes: > I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being > very nice :) The old driver never did any form of DMA for me, much less UDMA, so > I'm very glad to have the ATA drivers. controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff Will enable DMA mode with the old driver. It doesn't support UDMA on all chipsets (e.g. ALI), and in some cases may give very poor performance when using UDMA disks, but normal DMA mode should work. If you have UDMA disks but can't get UDMA to work, just disable UDMA in the BIOS setup utility and it will use normal DMA instead. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world doesn't get past dhclient
Hi Ed, > > cc -nostdinc -O -pipe > -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes > -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp > -I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o > dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o > icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o > print.o raw.o socket.o tables.o tree.o upf.o > packet.o: In function `assemble_hw_header': > packet.o(.text+0x8c): undefined reference to `assemble_ethernet_header' > packet.o: In function `decode_hw_header': > packet.o(.text+0x1b4): undefined reference to `decode_ethernet_header' > *** Error code 1 > > Stop. > *** Error code 1 > I just had this problem. I got around it by adding "ethernet.c" to the sources line in the file: /usr/src/sbin/dhclient/Makefile All of the code is there, Make just doesn't know to make it... Bruce -- --- Bruce Burden[EMAIL PROTECTED] Tandem Computers Inc. 512-432-8944Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Make world doesn't get past ifconfig
Hi all, Has this problem been fixed? ===> sbin/ifconfig cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I.. -c /omni/usr/src/sbin/ifconfig/ifconfig.c /omni/usr/src/sbin/ifconfig/ifconfig.c: In function `status': /omni/usr/src/sbin/ifconfig/ifconfig.c:723: storage size of `ifs' isn't known /omni/usr/src/sbin/ifconfig/ifconfig.c:806: `SIOCGIFSTATUS' undeclared (first use this function) /omni/usr/src/sbin/ifconfig/ifconfig.c:806: (Each undeclared identifier is reported only once /omni/usr/src/sbin/ifconfig/ifconfig.c:806: for each function it appears in.) /omni/usr/src/sbin/ifconfig/ifconfig.c:723: warning: unused variable `ifs' *** Error code 1 This is from a buildworld after an early morning (shortly after midnight CDT) cvsup on 24 June 1999. I can't find a definition for SIOCGIFSTATUS of "ifstat", of which 'ifs' is declared to be a type of. Thank you, Bruce -- --- Bruce Burden[EMAIL PROTECTED] Tandem Computers Inc. 512-432-8944Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
Dag-Erling Smorgrav wrote: > > Doug <[EMAIL PROTECTED]> writes: > > On Wed, 23 Jun 1999, Brian F. Feldman wrote: > > > A device name isn't necessarily the same as a device node, you know. > > Actually I do know that, but I've never come across a situation in > > freebsd where I would call something one thing in my kernel config file > > and something else in /dev. > > man bpf Yes the confusion that the two different names causes (and the consequent volume of -questions mail on the topic) is an excellent example of why it's a bad idea. Thanks for the support. :) Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world doesn't get past ifconfig
Make sure you install the include files. In message <[EMAIL PROTECTED]>, Bruce Burden write s: > > Hi all, > > Has this problem been fixed? > >===> sbin/ifconfig >cc -O -pipe -DUSE_IF_MEDIA -DUSE_VLANS -DNS -Wall -Wmissing-prototypes -Wcast-qual >-Wwrite-strings -Wnested-externs -I.. -c /omni/usr/src/sbin/ifconfig/ifconfig.c >/omni/usr/src/sbin/ifconfig/ifconfig.c: In function `status': >/omni/usr/src/sbin/ifconfig/ifconfig.c:723: storage size of `ifs' isn't known >/omni/usr/src/sbin/ifconfig/ifconfig.c:806: `SIOCGIFSTATUS' undeclared (first use >this function) >/omni/usr/src/sbin/ifconfig/ifconfig.c:806: (Each undeclared identifier is reported >only once >/omni/usr/src/sbin/ifconfig/ifconfig.c:806: for each function it appears in.) >/omni/usr/src/sbin/ifconfig/ifconfig.c:723: warning: unused variable `ifs' >*** Error code 1 > > This is from a buildworld after an early morning (shortly after > midnight CDT) cvsup on 24 June 1999. I can't find a definition for > SIOCGIFSTATUS of "ifstat", of which 'ifs' is declared to be a type of. > > Thank you, > Bruce >-- >--- > Bruce Burden[EMAIL PROTECTED] Tandem Computers Inc. > 512-432-8944Network Verification 14231 Tandem Blvd. > Auto answer(4 rings) Austin, TX 78726 > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
place of logfile for cron (PR 7682)
The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log. The FreeBSD style is to put those things in /var/log (/var/log/cron). Anyone any opinions on this? Which scripts depend on that location? Nick http://www.freebsd.org/cgi/query-pr.cgi?pr=7682 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On 24 Jun 1999, Dag-Erling Smorgrav wrote: > "Brian F. Feldman" <[EMAIL PROTECTED]> writes: > > I didn't mean that mode 2 was special, but Ultra DMA mode 2 in its entirety being > > very nice :) The old driver never did any form of DMA for me, much less UDMA, so > > I'm very glad to have the ATA drivers. > > controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > > Will enable DMA mode with the old driver. It doesn't support UDMA on > all chipsets (e.g. ALI), and in some cases may give very poor > performance when using UDMA disks, but normal DMA mode should work. If > you have UDMA disks but can't get UDMA to work, just disable UDMA in > the BIOS setup utility and it will use normal DMA instead. Actually, I couldn't disable UDMA in the BIOS, and UDMA didn't work. So, the old driver did _not_ do DMA for me. Of course, I knew about the wdc flags. > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] > Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD on Merced
> Are there any plans to port FreeBSD to the IA-64 architecture when it comes > out? The docs have recently been released There have been plans to do this for as long as Intel has had plans to make the processor. :) The question will simply come down to hardware availability and documentation. Once enough of us have access to both, something will no doubt happen. > It'll be a shame to see FreeBSD for Intel go with the last x86 processor. Unless a meteor strikes the earth and ends all life here first, I seriously doubt that this will happen. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD on Merced
It seems Jordan K. Hubbard wrote: > > Are there any plans to port FreeBSD to the IA-64 architecture when it comes > > out? The docs have recently been released > > There have been plans to do this for as long as Intel has had plans to > make the processor. :) > > The question will simply come down to hardware availability and > documentation. Once enough of us have access to both, something will > no doubt happen. > > > It'll be a shame to see FreeBSD for Intel go with the last x86 processor. > > Unless a meteor strikes the earth and ends all life here first, I > seriously doubt that this will happen. :) Just get one of those Merced boxen on my table, and I'll do what I can to make it happen... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
>controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > >Will enable DMA mode with the old driver. It doesn't support UDMA on >all chipsets (e.g. ALI), and in some cases may give very poor Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken). >performance when using UDMA disks, but normal DMA mode should work. If Which cases? Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On Fri, 25 Jun 1999, Bruce Evans wrote: > >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > > > >Will enable DMA mode with the old driver. It doesn't support UDMA on > >all chipsets (e.g. ALI), and in some cases may give very poor > > Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken). > Guess so. > >performance when using UDMA disks, but normal DMA mode should work. If > > Which cases? ALi Aladdin-V chipset. I already pasted the dmesg's relevant parts. > > Bruce > Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
Bruce Evans <[EMAIL PROTECTED]> writes: > >controller wdc0 at isa? port IO_WD1 irq 14 flags 0xa0ffa0ff > > > >Will enable DMA mode with the old driver. It doesn't support UDMA on > >all chipsets (e.g. ALI), and in some cases may give very poor > > Not e.g. ALI (Aladdin IV/V) (unless the ALI support is broken). Excerpts from dmesg on an ASUSTek Super Socket 7 motherboard with a 350 MHz AMD K6-2, running yesterday's -CURRENT: pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 chip1: at device 3.0 on pci0 ide_pci0: irq 0 at device 15.0 on pci0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 9641MB (19746720 sectors), 19590 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa0 wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S The IBM disk is an UDMA model. UDMA is disabled in the BIOS setup utility because of symptoms previously described on -current. It works fine in UDMA mode with sos' new atapi driver, btw. The Seagate drive is an old DMA-only (no UDMA) model. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
You misunderstand. I _cannot_ disable UDMA in my BIOS. Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
"Brian F. Feldman" <[EMAIL PROTECTED]> writes: > You misunderstand. I _cannot_ disable UDMA in my BIOS. I know. The mail you answered wasn't addressed to you. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CTM's still down :-(
Hello, Sorry for being annoying but is there still anything wrong with CTM generation? The last src-cur delta was from 8th of June. Regards, Vladimir ===|=== Vladimir Kushnir | [EMAIL PROTECTED], |Powered by FreeBSD [EMAIL PROTECTED] | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
please review: patch for PR kern/12265
I'm working on a fix to PR kern/12265 (panic when trying to RTM_GET
the default route while there is none).
The problem is that in route_output(), in that case, rn_lookup()
returns the root node of the radix table (he got it from rn_match()),
while the code expects NULL or a node with an AF_INET address
family. Later, rtfree() gets very confused and panics because the
route node to be freed doesn't have the right address family.
>From TCP/IP Illustrated vol. 2, it seems that rtalloc1() is written
to expect that from rn_match(): it explicitly checks if the returned
node is the root node.
So there are two solutions:
- fix rn_match() to return NULL when it currently returns
the root node;
- fix RTM_GET and friends, and scan for the same kind of error
elsewhere, to trap for this same condition.
I'm testing the first approach with the following patch on my
machine and there seems to be no ill-effect.
Unless someone thinks the second solution or another approach is
better, I'll commit this patch.
--- radix.c.origThu Jun 24 23:26:04 1999
+++ radix.c Thu Jun 24 23:26:26 1999
@@ -261,7 +261,7 @@
* This extra grot is in case we are explicitly asked
* to look up the default. Ugh!
*/
- if ((t->rn_flags & RNF_ROOT) && t->rn_dupedkey)
+ if (t->rn_flags & RNF_ROOT)
t = t->rn_dupedkey;
return t;
on1:
--
Pierre Beyssac[EMAIL PROTECTED] [EMAIL PROTECTED]
{Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher
Free domains: http://www.eu.org/ or mail [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
On 24 Jun 1999, Dag-Erling Smorgrav wrote: > "Brian F. Feldman" <[EMAIL PROTECTED]> writes: > > You misunderstand. I _cannot_ disable UDMA in my BIOS. > > I know. The mail you answered wasn't addressed to you. *apologies*. However, many Award BIOSes (all?) do not allow you to turn off UDMA. > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
>*apologies*. However, many Award BIOSes (all?) do not allow you to turn >off UDMA. All Award BIOSes that I have (for 5 working systems) support it if the hardware supports it (2 systems). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM's still down :-(
On Fri, 25 Jun 1999, Vladimir Kushnir wrote: > Hello, > Sorry for being annoying but is there still anything wrong with CTM > generation? The last src-cur delta was from 8th of June. I know, we're waiting until Ulf gets the new disk up and spinning. It's taking some time, but I think he's having some problems with it. > > Regards, > Vladimir > > ===|=== > Vladimir Kushnir| > [EMAIL PROTECTED], |Powered by FreeBSD > [EMAIL PROTECTED] | > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > +--- Chuck Robey | Interests include any kind of voice or data [EMAIL PROTECTED] | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
a few comments on make release
1) a cross-reference to http://www.freebsd.org/FAQ/FAQ243.html#246 in the docs in /usr/src/release is useful! how about adding one to the Makefile 2) you can't always do a make release without 1:1 agreement between your runtime state and the CVS and /usr/src repositaries being used to do make release as an example, the re-integration of vinum exposed a Make failure copying nonexistant vinum.ko into the release build. re-cvsupping, and then make buildworld/installworld before make release should fix it. 3) now that CDburners are 10 a penny, pointers to how to cut the outcomes of make release to CD (even if pitifully simple) would be useful. cheers -George To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: place of logfile for cron (PR 7682)
On 24 Jun, Nick Hibma wrote: > > The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log. > The FreeBSD style is to put those things in /var/log (/var/log/cron). > > Anyone any opinions on this? Which scripts depend on that location? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=7682 I agree with you. I submitted a similiar PR in January: http://www.freebsd.org/cgi/query-pr.cgi?pr=9292 Whatever the decision, if your PR is closed, this one should be also. -- Stephen J. Roznowski([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CTM machine (chi.Alameda.net)
The machine itself is back up. Services are being restored currently. The machine has now a 12GB vinum filesystem for /ctm and should not run out of space so fast again. -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Intel Pro 100+ Server Adapter
I recently purchased a Intel Pro 100+ Server Adapter for my FreeBSD machine (3.1), but I can't find any information if it is supported, or not... I'm also not sure which driver I would use for it.. Intel's site, and the FreeBSD site have no information regarding this adaptor's compatibility with FreeBSD... Anyone's help would be greatly appreciated... I need to install this adapter or get another one by Monday... I currently use a Intel Etherexpress 10/100... If these would be the same, I should have no problems... Thanks guys... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
KLD cdev example doesn't work anymore
After a long absence, I was just about to get into my new joystick drivers when it now fails to compile. What's the recommended change? 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: New ATA stuff, questions and comment
> On Wed, 23 Jun 1999, Doug wrote: > > > First a question, namely what is the current state of the ATA > > drivers in -current? Are they reliable (where "reliable" goes by -current > > terms obviously)? I finally am in a position to test them with a new > > workstation that has IDE disks, so I thought I'd give it a go. > I am using the new ATA-drivers for quite some time now. On a home-PC they work great. On my Laptop (Omnibook 5700) they only work if I change the code to not switch-on Generic DMA-Support. Basically I change the code in ata-dma.c::ata_dmainit at the very to NOT switch on generic DMA-mode even if the drive claims that it could do DMA. The Notebook has an "TOSHIBA MK2101MAN/B1.06 D" / piomode=4, dmamode=2, udmamode=1. The old wd-driver DMA did not work for this machine, but fortunately it was not switched on by default. This needs to be configurable before the the new ATA-drivers are made the default! Otherwise I am very happy with these drivers. Michael ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division Phone: +49 7031 14-3707 Fax:+49 7031 14-4196 ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KLD cdev example doesn't work anymore
find /usr/src -name \*.c | xargs grep DEV_DRIVER_MODULE
and check the changes on that file.
For your reference, the changes that have recently been made to ugen.c
with respect to the cdevsw thingies:
RCS file: /home/ncvs/src/sys/dev/usb/ugen.c,v
retrieving revision 1.12
retrieving revision 1.16
diff -u -r1.12 -r1.16
--- ugen.c 1999/04/16 21:22:00 1.12
+++ ugen.c 1999/05/30 16:51:46 1.16
@@ -1,5 +1,5 @@
/* $NetBSD: ugen.c,v 1.11 1999/01/08 11:58:25 augustss Exp $
*/
-/* $FreeBSD: src/sys/dev/usb/ugen.c,v 1.12 1999/04/16 21:22:00
peter Exp $*
/
+/* $FreeBSD: src/sys/dev/usb/ugen.c,v 1.16 1999/05/30 16:51:46 phk
Exp $ *
/
/*
* Copyright (c) 1998 The NetBSD Foundation, Inc.
@@ -121,10 +121,25 @@
#define UGEN_CDEV_MAJOR114
static struct cdevsw ugen_cdevsw = {
- ugenopen, ugenclose, ugenread, ugenwrite,
- ugenioctl, nostop, nullreset, nodevtotty,
- ugenpoll, nommap, nostrat,
- "ugen", NULL, -1
+ /* open */ ugenopen,
+ /* close */ ugenclose,
+ /* read */ ugenread,
+ /* write */ ugenwrite,
+ /* ioctl */ ugenioctl,
+ /* stop */ nostop,
+ /* reset */ noreset,
+ /* devtotty */ nodevtotty,
+ /* poll */ ugenpoll,
+ /* mmap */ nommap,
+ /* strategy */ nostrategy,
+ /* name */ "ugen",
+ /* parms */ noparms,
+ /* maj */ UGEN_CDEV_MAJOR,
+ /* dump */ nodump,
+ /* psize */ nopsize,
+ /* flags */ 0,
+ /* maxio */ 0,
+ /* bmaj */ -1
};
#endif
@@ -141,8 +156,8 @@
usbd_status ugen_set_interface __P((struct ugen_softc *, int, int));
int ugen_get_alt_index __P((struct ugen_softc *sc, int ifaceidx));
-#define UGENUNIT(n) (((n) >> 4) & 0xf)
-#define UGENENDPOINT(n) ((n) & 0xf)
+#define UGENUNIT(n) ((minor(n) >> 4) & 0xf)
+#define UGENENDPOINT(n) (minor(n) & 0xf)
USB_DECLARE_DRIVER(ugen);
@@ -997,6 +1012,6 @@
return 0;
}
-CDEV_DRIVER_MODULE(ugen, uhub, ugen_driver, ugen_devclass,
- UGEN_CDEV_MAJOR, ugen_cdevsw, usbd_driver_load,
0);
+DEV_DRIVER_MODULE(ugen, uhub, ugen_driver, ugen_devclass,
+ UGEN_CDEV_MAJOR, NOMAJ, ugen_cdevsw, usbd_driver_load,
0);
#endif
Nick
On Fri, 25 Jun 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
> After a long absence, I was just about to get into my new joystick drivers
> when it now fails to compile. What's the recommended change?
>
>
> 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
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: New ATA stuff, questions and comment
It seems Michael Class wrote: > > On Wed, 23 Jun 1999, Doug wrote: > > > > > First a question, namely what is the current state of the ATA > > > drivers in -current? Are they reliable (where "reliable" goes by -current > > > terms obviously)? I finally am in a position to test them with a new > > > workstation that has IDE disks, so I thought I'd give it a go. > > > > I am using the new ATA-drivers for quite some time now. On a home-PC > they work great. On my Laptop (Omnibook 5700) they only work if I > change the code to not switch-on Generic DMA-Support. Basically I > change the code in ata-dma.c::ata_dmainit at the very to NOT switch > on generic DMA-mode even if the drive claims that it could do DMA. > The Notebook has an > "TOSHIBA MK2101MAN/B1.06 D" / piomode=4, dmamode=2, udmamode=1. > > The old wd-driver DMA did not work for this machine, but fortunately > it was not switched on by default. This needs to be configurable before > the the new ATA-drivers are made the default! That an area that I havn't quite decided on yet, but I'm aware of the potential problems (in fact I chose the default to find out how severe a problem this might be). > Otherwise I am very happy with these drivers. Thanks! -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Microsoft performance (was: ...) (fwd)
Some interesting comments from an interesting source. BTW. I'd appreciate it if everyone noticed how friendly and helpful Linus is and Not find some thing to rag on linux about with this. The aim of this thread is to improve FreeBSD in any way we see as being a real improvement. Don't cc him back into the topic. I'm sure he has enough to worry about. This is FYI only ok? -- Forwarded message -- Date: Fri, 25 Jun 1999 00:51:10 -0700 (PDT) From: Linus Torvalds <[EMAIL PROTECTED]> To: Sean Eric Fagan <[EMAIL PROTECTED]> Cc: Julian Elischer <[EMAIL PROTECTED]> Subject: Re: Microsoft performance (was: ...) On Thu, 24 Jun 1999, Sean Eric Fagan wrote: > > Not sure if you've seen this stuff before; thought you might find it > interesting if not. (This is not intended to be anything other than, "NT > performs surprisingly well" :).) Indeed (Julian cc'd). We had this taught to us the hard way with the mindcraft benchmark. NT scales VERY well for netbench. It became pretty obvious pretty quickly that it's one of their basic benchmarks, and it's what they have optimized NT and IIS for. Fair enough - netbench may not be the best benchmark out there, but there isn't anything better. Julian, feel free to forward my comments to anybody, for whatever they are worth. > Ok well here are some real numbers for you.. > Win NT 4processors 1GB ram + raid array + IIS > webbench... 4000 transactions per second... > > FreeBSD.. Identical hardware.. > 1450 transactions per seccond > Linux: 2000 per second > Solaris86 6000 per second The major problem with webbench is apache, although the OS _does_ matter. The webbench overhead is largely the socket timeouts and you have to do accept() right scalability-wise. I suspect NT just doesn't do the timewait stuff at all, but I could be wrong. We ended up doing the accept() thing in Linux (waking up just one thread), even though I personally think it doesn't have that big an impact in real life. It was easy enough to do. Once you get over that, the numbers seem to be just purely about scaling the fs and network, but I never got interested enough to check more into it. The netbench load was more interesting in that area, and we ended up having a benchmark that didn't have the apache overhead so it was a "purer" benchmark anyway. AND it was what NT did really well on, so.. The apache guys are definitely looking at a new threading model, you might try to approach Dean Gaudet and ask him what he's up to. That, together with the scalaibility stuff, should hopefully be enough. NT didn't do _that_ well on this one. And btw, if you're feeling bad about the numbers above: C'T in Germany did a similar kind of benchmark which was more UNIX-oriented, with perl CGI scripts etc, and NT did really badly on it. Another case of NT being optimized for one thing, and one thing only. Oh, except that if you do the "MS CGI" (whetever they call they built-in modules), NT actually does that pretty well - built in to IIS. So it's not even "dynamic content" - it's really about what _kind_ of CGI you do. > With Netbench: > NT blows us away. Netbench is the big thing for NT. And the numbers you quote are the "bad" NT numbers (ie bad enough that Linux actually was able to inch ahead of NT). The _good_ NT numbers are three times as good, but they are done with (a) NT running FATFS, (b) w98 clients exclusively. > (we're talking an order of magnitude faster) > I'm not going ot give real numbers as I don't have them readily at hand > but they are something like 12MB/Sec for FreeBSD vs 90 MB/sec for NT and > 120MB/sec for linux. Matt has some patches that raise the 12 to 35 and > kirk has some changes that may raise the numbers to 70 or more, > and John has some patches that may add more again, but it's all theory, > and some of the patches have had less results than we expected. Qutoe frankly, to get close to NT, you have to scale really well to four CPU's. We've had the core "deep SMP people" working on this for the last month, and we _finally_ have a system that seems to scale pretty well: well enough that we think we can beat the _good_ NT numbers too. Or at least come so close as to not matter any more. When I say scale really well, I mean it. You need to (a) make sure your disk never does anything at all, and (b) make sure that you get almost perfect scaling for cached reads and writes. That's what NT comes pretty close to doing, it seems. The new Linux code has a per-page lock on the page cache, and pretty much nothing else. And I don't think you can beat NT with anything less. > With Uniprocessor things are a lot more equal. > but we still suck on netbench. If you suck on netbench even on UP, the most likely reason is just that you're doing too much IO. You can make a noticeable portion of the load go away by trying to keep dirty state in memory, and making sure that unlink() removes the dirty state without ever writing it out. That doesn't get rid of the problem (the n
UPDATE9: ATA/ATAPI driver new version available.
Nine'th update to the new ATA/ATAPI driver: The atapi subsystem has gotten better error handeling and timeouts, it also tries a REQUEST SENSE command when devices returns errors, to give a little more info as to what went wrong. It might be a little verbose for now, but I'm interested in as much feedback on errors as possible, especially timeouts, as I'm a bit in doubt if I've chosen resonable default values everywhere. The disk driver has been changed a bit to prepare for tagged queing, which is next on my list. The disk driver has grown a dump routine, I got one implementation from Darrell Anderson <[EMAIL PROTECTED]> which also did partial dumps (usefull on big memory machines) I left out the partial stuff for now, and changed the rest alot to fit into the new ad_request framework. Some minor cleanups and rearrangements as well. As usual USE AT YOUR OWN RISK!!, this is still pre alpha level code. Especially the DMA support can hose your disk real bad if anything goes wrong, again you have been warned :) Notebook owners should be carefull that their machines dont suspend as this might cause trouble... But please tell me how it works for you! Enjoy! -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel Pro 100+ Server Adapter
On Thu, Jun 24, 1999 at 07:42:59PM -0700, JMS Internet <[EMAIL PROTECTED]> wrote: > I recently purchased a Intel Pro 100+ Server Adapter > for my FreeBSD machine (3.1), but I can't find any information if it is > supported, > or not... I'm also not sure which driver I would use for it.. Intel's > site, and the FreeBSD It's probably an 82559 chip based card. The management features aren't supported I guess but otherwise works well with fxp driver. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD on Merced
[EMAIL PROTECTED] wrote: > >Are there any plans to port FreeBSD to the IA-64 architecture when it >comes out? The docs have recently been released > http://developer.intel.com/design/ia64/architecture.htm >so I was wondering if anyone had a chance to look at the stuff. When I looked a couple of weeks ago they had not yet released docs on the OS parts of the processor -- memory management, privileged modes, etc. Tony. -- f.a.n.finch [EMAIL PROTECTED] [EMAIL PROTECTED] Winner, International Obfuscated C Code Competition 1998 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: a few comments on make release
> 1) a cross-reference to http://www.freebsd.org/FAQ/FAQ243.html#246
>in the docs in /usr/src/release is useful!
>
> how about adding one to the Makefile
>
> 2) you can't always do a make release without 1:1 agreement between
>your runtime state and the CVS and /usr/src repositaries being used
>to do make release
>
> as an example, the re-integration of vinum exposed a Make failure
> copying nonexistant vinum.ko into the release build.
>
> re-cvsupping, and then make buildworld/installworld before
> make release should fix it.
>
> 3) now that CDburners are 10 a penny, pointers to how to cut the outcomes
>of make release to CD (even if pitifully simple) would be useful.
Assuming you are doing a make release, how about:
#!/bin/sh -e
export SNAP=3.2-RELEASE
export SNAP=4.0-19990622-SNAP
export RUN_MAKECDFS=YES
cd /cdwork && rm -rf disc1
cd /pub/FreeBSD/${SNAP}/cdrom && \
tar -cf - disc1 | (cd /cdwork && tar -xvf -)
cd /cdwork/disc1 && mkdir XF86333
cd /pub/FreeBSD/${SNAP}/XF86333 && \
tar -cf - . | (cd /cdwork/disc1/XF86333 && tar -xvf -)
if [ ${RUN_MAKECDFS} = "YES" ]; then
#
# Create a bootable cdrom containing the distribution
#
cd /cdwork && rm -f cd1.image
sh /usr/share/examples/worm/makecdfs.sh \
-b "${SNAP}" /cdwork/disc1 /cdwork/cd1.image \
"${SNAP} (c) FreeBSD"
fi
#
# Burn it
#
#cd /cdwork && cdrecord dev=6,0 speed=4 -v -prcap -dummy cd1.image
>
> cheers
> -George
>
>
> 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
Changing the semantics of splsoftclock()
I've come across several instances where I need to fiddle with state that is also touched by a timeout handler. From a naming standpoint, splsoftclock() sounds like the correct spl routine to use for protecting these activities. Unfortunately this only holds true if splsoftclock() is used in a process context where the fact that it may actually lower the ipl to softclock is not an issue. As it currently stands, in most cases you can rely on the fact that any spl level will also block callouts, but this seems risky. What I'd like to see happen is for either the semantics of splsoftclock() to change, or to have a new spl introduced (splcallout()??). The hope is to provide a consistent interface across all *BSDs which is why I've addressed this to all of the *BSD projects. I look forward to you input on this proposal. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Changing the semantics of splsoftclock()
I've come across several instances where I need to fiddle with state that is also touched by a timeout handler. From a naming standpoint, splsoftclock() sounds like the correct spl routine to use for protecting these activities. Unfortunately this only holds true if splsoftclock() is used in a process context where the fact that it may actually lower the ipl to softclock is not an issue. As it currently stands, in most cases you can rely on the fact that any spl level will also block callouts, but this seems risky. What I'd like to see happen is for either the semantics of splsoftclock() to change, or to have a new spl introduced (splcallout()??). The hope is to provide a consistent interface across all *BSDs which is why I've addressed this to all of the *BSD projects. I look forward to you input on this proposal. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Changing the semantics of splsoftclock()
[ Sorry for the duplicate message for some of you. I botched the headers on the original mail. ] I've come across several instances where I need to fiddle with state that is also touched by a timeout handler. From a naming standpoint, splsoftclock() sounds like the correct spl routine to use for protecting these activities. Unfortunately this only holds true if splsoftclock() is used in a process context where the fact that it may actually lower the ipl to softclock is not an issue. As it currently stands, in most cases you can rely on the fact that any spl level will also block callouts, but this seems risky. What I'd like to see happen is for either the semantics of splsoftclock() to change, or to have a new spl introduced (splcallout()??). The hope is to provide a consistent interface across all *BSDs which is why I've addressed this to all of the *BSD projects. I look forward to you input on this proposal. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Changing the semantics of splsoftclock()
Why have splr semantics? That is, it raises to splsoftclock if current priority is lower, else doesn't fiddle with it. On Fri, 25 Jun 1999, Justin T. Gibbs wrote: > I've come across several instances where I need to fiddle with state that > is also touched by a timeout handler. From a naming standpoint, > splsoftclock() sounds like the correct spl routine to use for protecting > these activities. Unfortunately this only holds true if splsoftclock() > is used in a process context where the fact that it may actually lower > the ipl to softclock is not an issue. As it currently stands, in most > cases you can rely on the fact that any spl level will also block callouts, > but this seems risky. What I'd like to see happen is for either the > semantics of splsoftclock() to change, or to have a new spl introduced > (splcallout()??). The hope is to provide a consistent interface across > all *BSDs which is why I've addressed this to all of the *BSD projects. > I look forward to you input on this proposal. > > -- > Justin > > > > 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: UPDATE9: ATA/ATAPI driver new version available.
Trying the updated driver, I notice that the first time I try to mount the cdrom drive, it hangs, I hit ^C and get this error: atapi_error: PREVENT_ALLOW - timeout error = 00 After that, I can mount it fine. This system is all SCSI except for the cdrom, which is a generic 6x IDE cdrom drive. Here is the relevant probes (dmesg | grep ata): ata-pci0: at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata_command: timeout waiting for interrupt On Fri, 25 Jun 1999, Soren Schmidt wrote: > Nine'th update to the new ATA/ATAPI driver: > -- Neal Westfall | mailto:[EMAIL PROTECTED] | http://www.odc.net/~nwestfal "What is today a matter of academic speculation begins tomorrow to move armies and pull down empires. In that second stage, it has gone too far to be combatted; the time to stop it was when it was still a matter of impassionate debate." -- J. Gresham Machen, "Christianity and Culture" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Changing the semantics of splsoftclock()
[ I've dropped [EMAIL PROTECTED] based on a request from Theo since he cannot post back to some of these lists. ] >Why have splr semantics? That is, it raises to splsoftclock if current >priority is lower, else doesn't fiddle with it. This is what I meant to suggest, but if this is not doable, create a new spl. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATE9: ATA/ATAPI driver new version available.
It seems Neal Westfall wrote: > Trying the updated driver, I notice that the first time I try > to mount the cdrom drive, it hangs, I hit ^C and get this > error: > > atapi_error: PREVENT_ALLOW - timeout error = 00 > > After that, I can mount it fine. This system is all SCSI except > for the cdrom, which is a generic 6x IDE cdrom drive. Hmm, that is a little wierd since: > Here is the relevant probes (dmesg | grep ata): > > ata-pci0: at device 1.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > ata_command: timeout waiting for interrupt It also failed here in the probe, hmm... Does it work reliably ever after then ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATE9: ATA/ATAPI driver new version available.
On Fri, 25 Jun 1999, Soren Schmidt wrote: > > atapi_error: PREVENT_ALLOW - timeout error = 00 > > > > After that, I can mount it fine. This system is all SCSI except > > for the cdrom, which is a generic 6x IDE cdrom drive. > > Hmm, that is a little wierd since: > > > Here is the relevant probes (dmesg | grep ata): > > > > ata-pci0: at device 1.1 on pci0 > > ata-pci0: Busmastering DMA supported > > ata0 at 0x01f0 irq 14 on ata-pci0 > > acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master > > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked > > ata_command: timeout waiting for interrupt > > It also failed here in the probe, hmm... > > Does it work reliably ever after then ?? Seems to. I was able to tar off a directory on the cdrom to the hard drive with no errors at all. Neal -- Neal Westfall | mailto:[EMAIL PROTECTED] | http://www.odc.net/~nwestfal "What is today a matter of academic speculation begins tomorrow to move armies and pull down empires. In that second stage, it has gone too far to be combatted; the time to stop it was when it was still a matter of impassionate debate." -- J. Gresham Machen, "Christianity and Culture" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATE9: ATA/ATAPI driver new version available.
Here is the complete output of dmesg in case it is helpful: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #106: Fri Jun 25 10:00:44 PDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/MILLENNIUM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199309909 Hz CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xf9ff real memory = 134217728 (131072K bytes) avail memory = 127590400 (124600K bytes) Preloaded elf kernel "kernel" at 0xc02ea000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: OPT0931 [0x3109143e] Serial 0x Comp ID: @@@ [0x] AD_WAIT_INIT FAILED 1002 0xff mss_attach 1 at 0x530 irq 10 dma 3:5 flags 0x15 pcm1 (OPTi931 sn 0x) at 0x530-0x537 irq 10 drq 3 flags 0x15 on isa npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 isab0: at device 1.0 on pci0 ata-pci0: at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 de0: irq 9 at device 10.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:36:73:56 vga-pci0: irq 12 at device 12.0 on pci0 ncr0: irq 15 at device 13.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: W83877F chipset (NIBBLE-only) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE/ECP/ECP_RLE Probing for PnP devices on ppbus0: ppbus0: PJL,MLC,PCL,PCLXL plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 acd0: < ICD-900AT/ A01> CDROM drive at ata0 as master acd0: drive speed 1367KB/sec, 120KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked de0: enabling 100baseTX port ata_command: timeout waiting for interrupt Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) atapi_error: PREVENT_ALLOW - timeout error = 00 cd9660: RockRidge Extension cd9660: RockRidge Extension cd9660: RockRidge Extension The atapi_error was when I tried to mount it the first time after boot, and then I mounted/unmounted it 3 times with no problem. Neal To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: place of logfile for cron (PR 7682)
On Thu, 24 Jun 1999, Stephen J. Roznowski wrote: > On 24 Jun, Nick Hibma wrote: > > > > The logfile for CRON is in the wrong place IMHO. It's in /var/cron/log. > > The FreeBSD style is to put those things in /var/log (/var/log/cron). > > > > Anyone any opinions on this? Which scripts depend on that location? > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=7682 > > I agree with you. I submitted a similiar PR in January: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=9292 > > Whatever the decision, if your PR is closed, this one should be also. Don't forget to update newsyslog.conf since newsyslog babysits the cron log. Doug White Internet: [EMAIL PROTECTED]| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
'make all' in /sys/i386/boot fails
I was working on my com console stuff and when I went into /sys/i386/boot and did a 'make all install clean' to rebuild my boot blocks (after changing /etc/make.conf) it fails due to an error in the netboot sub directory. I don't need netboot so I just deleted it temporarily in the makefile, but I thought that y'all would want to know. If I get no comments on this I'll file a PR. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
boot -P AND autoboot possible?
I set up a serial console on my -current box and putting "-P" in /boot.config worked just fine, but I'd really like to use the new loader and such, plus according to the man page for loader /boot.config is deprecated. The only problem is I couldn't figure out where exactly this option should go. I tried a lot of things, none of which worked. In an ideal world what I'd like to have is the autoboot prompt with a delay, and then boot -P. Is this even possible? And is there any move to improving the documentation for the new loader stuff, or is it still in transition? I can submit patches for the man page(s) if I can get a grip on what's happening where (and when). :-/ What I'd really like to see is a chronological listing, like: First, foo happens Here are the options for "foo," they go in the "foo.conf" file Next, bar happens Here are the options for "bar," they go in the "bar.conf" file, but can be overriden with the "bar.rc" file... Etc. The current man pages come close to this, but I still get lost going back and forth between the various pages. Any comments, pointers to docs, etc. welcome. Thanks, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: a few comments on make release
[cd image making code removed] Bewdiful. just what the docter ordered. thanks! -George To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: traceroute breakage in -current
John Polstra wrote: > > I just noticed that traceroute in -current is starting its probes > with port 1 instead of 33435 as it is supposed to do: > > tcpdump: listening on fxp0 > 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1] > > It broke in revision 1.9 of "src/contrib/traceroute/traceroute.c". Thanks! - I thought I was going mad! - I've been out the office recently, so I've not had time to chase it up, but I noticed _exacltly_ the same thing... This results in my -current machine not being able to traceroute through our firewall, whereas the 2.2.X / 3.X boxes can... -Kp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: traceroute breakage in -current
Karl Pielorz writes: > > I just noticed that traceroute in -current is starting its probes > > with port 1 instead of 33435 as it is supposed to do: > > > > tcpdump: listening on fxp0 > > 09:05:03.527313 206.213.73.12.38947 > 204.216.27.21.1: udp 12 [ttl 1] > > > > It broke in revision 1.9 of "src/contrib/traceroute/traceroute.c". > > Thanks! - I thought I was going mad! - I've been out the office recently, so > I've not had time to chase it up, but I noticed _exacltly_ the same thing... > This results in my -current machine not being able to traceroute through our > firewall, whereas the 2.2.X / 3.X boxes can... I just fixed this, so see if it works for you now. Sorry about that. -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make all' in /sys/i386/boot fails
> I was working on my com console stuff and when I went into > /sys/i386/boot and did a 'make all install clean' to rebuild my boot > blocks (after changing /etc/make.conf) it fails due to an error in the > netboot sub directory. I don't need netboot so I just deleted it > temporarily in the makefile, but I thought that y'all would want to know. > If I get no comments on this I'll file a PR. sys/i386/boot is deprecated. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: .: Out of file descriptors ??
> > >Hi all, > >I did a cvsup on the night of June 24/25, got the world built, >installed, /etc updated, the kernel config file updated, built >the kernel, updated it, and when I attempt to boot, I get the >following error: > > .: Out of file descriptors You copied /etc/defaults/rc.conf to /etc/rc.conf, in spite of the clear warning in this file not to do that. Don't do that. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Out of file descriptors ??
From: Bruce Burden <[EMAIL PROTECTED]>
>I did a cvsup on the night of June 24/25, got the world built,
>installed, /etc updated, the kernel config file updated, built
>the kernel, updated it, and when I attempt to boot, I get the
>following error:
>
> .: Out of file descriptors
>
Check the bottom of your /etc/rc.conf file for:
for i in ${rc_conf_files}; do
if [ -f $i ]; then
. $i
fi
done
What is happening is /etc/defaults/rc.conf pulls in /etc/rc.conf, which then
pulls in /etc/rc.conf repeat until we run out of file descriptors.
You need to remove the above code from the /etc/rc.conf file.
Scot
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: boot -P AND autoboot possible?
On Fri, 25 Jun 1999 13:13:20 MST, Doug wrote: > I can submit patches for the man page(s) if I can get a grip on what's > happening where (and when). :-/ What I'd really like to see is a > chronological listing, like: I think you're reading the wrong manpage. I've just had a look at loader(8) and can't really see what you'd want to improve. Can you confirm that your loader.8 DESCRIPTION starts with "The program called loader is the third stage of FreeBSD's three stage bootstrap. It is a BTX client linked statically to libstand(3) and usually located in the directory /boot." If so, then did you try the autoboot_delay option? Have you noticed the loader.conf(5) manpage? I'm pretty sure Mr Sobral's done a fairly good job with the documentation for the new boot loader. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make all' in /sys/i386/boot fails
On Fri, 25 Jun 1999 18:46:05 MST, Doug wrote: > Where would I go if I wanted to rebuild my boot blocks to make the > com console run at a different speed, or is this something I could set > with one of the voluminous conf files in /boot, or?? Try src/sys/boot ? Tip for the future: When you next make world, copy the output to a file so that you can grep it to find out where stuff is installed out of: make world 2>&1 | tee /some/place/make_world.log Or whatever. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make all' in /sys/i386/boot fails
Sheldon Hearn wrote: > > On Fri, 25 Jun 1999 18:46:05 MST, Doug wrote: > > > Where would I go if I wanted to rebuild my boot blocks to make the > > com console run at a different speed, or is this something I could set > > with one of the voluminous conf files in /boot, or?? > > Try src/sys/boot ? Well that certainly looks like the right answer. Are you uncertain about it, or just being rhetorical? Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'make all' in /sys/i386/boot fails
On Sat, 26 Jun 1999 01:05:31 MST, Doug wrote: > Well that certainly looks like the right answer. Are you > uncertain about it, or just being rhetorical? The expanded version was Try src/sys/boot, which is where I found what looked very much like the new boot loader. I've now checked and it's _definitely_ src/sys/boot . Have fun. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NT vs Linux benchmark saga continues (fwd)
And to follow up on this topic: the german magazine c't has an article in their current issue, where they compare a real-world setup measuring web-server performance for NT an Linux both for an SMP and non-SMP setup. Linux was - depending on the setup and application - a bit to much faster ... hellmuth -- Hellmuth MichaelisTel +49 40 559747-70 HCS Hanseatischer Computerservice GmbHFax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
