Call for FreeBSD 2013-Q1 status reports!
Hi all, On behalf of monthly@, I would like to inform you that the next submission date for the January to March quarterly status reports is April 21st, 2013 - less than a month away. They don't have to be very long - anything that lets people know what is going on inside FreeBSD is useful. Note that submission of reports is not restricted to committers - anyone who is doing anything interesting and FreeBSD-related can write one! The preferred and easiest submission method is to use the XML generator linked to from http://www.freebsd.org/news/status/status.html, with the result emailed as an attachment to mont...@freebsd.org. On that page, there is also a link to an XML template which can be filled out manually and attached if preferred. To enable compilation and publication of the Q1 report as soon as possible after the April 21st deadline, please be prompt with any report submissions you may have. I look forward to compiling the report for 2013 Q1. Many thanks, Isabell. (Hat: monthly@) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9-STABLE buildworld compile error
When I put MALLOC_PRODUCTION=yes in /etc/make/conf, make buildworld hangs with error /usr/src/lib/libc/stdlib/ malloc.c:126:1: error: "MALLOC_PRODUCTION" redefined : error: this is the location of the previous definition This is a patch, which avoid this error --- /usr/src/lib/libc/stdlib/Makefile.inc.orig2012-12-04 11:53:28.0 +0200 +++ /usr/src/lib/libc/stdlib/Makefile.inc2013-04-02 14:14:35.0 +0300 @@ -51,7 +51,3 @@ malloc.3 realloc.3 malloc.3 reallocf.3 malloc.3 malloc_usable_size.3 MLINKS+=tsearch.3 tdelete.3 tsearch.3 tfind.3 tsearch.3 twalk.3 -.if defined(MALLOC_PRODUCTION) -CFLAGS+=-DMALLOC_PRODUCTION -.endif - ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9-STABLE buildworld compile error
On Tue, 2013-04-02 at 14:28 +0300, Dmitry Luhtionov wrote: > When I put MALLOC_PRODUCTION=yes in /etc/make/conf, make buildworld hangs > with error > /usr/src/lib/libc/stdlib/ > malloc.c:126:1: error: "MALLOC_PRODUCTION" redefined > : error: this is the location of the previous definition > > This is a patch, which avoid this error > > --- /usr/src/lib/libc/stdlib/Makefile.inc.orig2012-12-04 > 11:53:28.0 +0200 > +++ /usr/src/lib/libc/stdlib/Makefile.inc2013-04-02 14:14:35.0 > +0300 > @@ -51,7 +51,3 @@ > malloc.3 realloc.3 malloc.3 reallocf.3 malloc.3 malloc_usable_size.3 > MLINKS+=tsearch.3 tdelete.3 tsearch.3 tfind.3 tsearch.3 twalk.3 > > -.if defined(MALLOC_PRODUCTION) > -CFLAGS+=-DMALLOC_PRODUCTION > -.endif > - That's because MALLOC_PRODUCTION is already defined in -stable. The right fix would be to remove it from your make.conf, because it's no longer necessary in -current either -- the performance problems that originally led to the advice to put MALLOC_PRODUCTION in make.conf for -current have been fixed. -- Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Any objections/comments on axing out old ATA stack?
Am 31.03.2013 23:02, schrieb Scott Long: > So what I hear you and Matthias saying, I believe, is that it should be > easier to > force disks to fall back to non-NCQ mode, and/or have a more responsive > black-list for problematic controllers. Would this help the situation? It's > hard to > justify holding back overall forward progress because of some bad controllers; > we do several Tbps off of AHCI controllers with NCQ enabled on FreeBSD 9.x, > enough to make up a sizable percentage of the internet's traffic, and we see > no > problems. How can we move forward but also take care of you guys with > problematic hardware? Well, I am running the driver fine off of my WD Caviar RE3 disk, and the problematic drive also works just fine with Windows and Linux, so it must be something between the problematic drive and the FreeBSD driver. I would like to see any of this, in decreasing order of precedence: - debugged driver - assistance/instructions on helping how to debug the driver/trace NCQ stuff/... (as in Jeremy Chadwick's followup in this same thread - this helps, I will attempt to procure the required information; "back then", reducing the number of tags to 31 was ineffective, including an error message and getting a value of 32 when reading the setting back) - "user-space" contingency features, such as letting camcontrol limit the number of open NCQ tags, or disable NCQ, either on a per-drive basis I am capable of debugging C - mostly with gdb command-line, and graphical Windows IDEs - but am unfamiliar with FreeBSD kernel debugging. If necessary, I can pull up a second console, but the PC that is affected is legacy-free, so serial port only works through a serial/USB converter. signature.asc Description: OpenPGP digital signature
Re: Any objections/comments on axing out old ATA stack?
Am 01.04.2013 17:07, schrieb Stefan Esser: > Am 01.04.2013 15:14, schrieb Victor Balada Diaz: >> Being able to configure quirks from loader.conf for disks AND controllers >> would be great >> and is not hard to do. If you want i can do a patch in two weeks and send it >> to you. That >> way it's easy to test disabling NCQ and/or other things in case of hitting a >> bug. Also >> being able to modify the configuration without a kernel recompile would be a >> big >> improvement because we could still use freebsd-update to keep systems >> updated. > > Something like: > > kern.cam.ada.0.quirks=1 > > to force 4KB sectors? > > No need to implement that, it is in -CURRENT (did not check -STABLE). > But there is no quirk, that disables NCQ, currently, although it is > easy to implement. See the places where "ADA_FLAG_CAN_NCQ" is set and > make that value depend on a new quirk flag being unset ... > > But instead of setting that flag in the loader, it would be good to > collect drive signatures that need it and to add quirk entries for > them in ata_da.c ... Before we can do that, we need to know if it's really the drive's fault or if the driver is wrong. We need to debug that. If we have relevant parameters exposed through the CAM interface (rather than loader variables), that would also help expedite the debugging. signature.asc Description: OpenPGP digital signature
Re: [patch] IPMI KCS can drop the lock while servicing a request
On Saturday, March 23, 2013 11:11:20 pm Eric van Gyzen wrote: > At work, we discovered that our application's IPMI thread would often > use a lot of CPU time. The KCS thread uses DELAY to wait for the BMC, > so it can run without sleeping for a "long" time with a slow BMC. It > also holds the ipmi_softc.ipmi_lock during this time. When using > adaptive mutexes, an application thread that wants to operate on the > ipmi_pending_requests list will also spin during this same time. > > We see no reason that the KCS thread needs to hold the lock while > servicing a request. We've been running with the attached patch for a > few months, with no ill effects. The lock protects against concurrent access to the registers themselves (though the thread sort of does this already). However, even with a slow BMC it shouldn't be waiting but so long. I had some other comments about this patch in my reply to when it was committed. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: gptzfsboot: error 4 lba 30
On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote: > Hi. > > On one of my fresh installed servers I am seeing the following output during boot: > > gptzfsboot: error 4 lba 30 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 30 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 > gptzfsboot: error 4 lba 31 Humm, do you have disks that the BIOS sees that are small? An error code of 4 means 'sector not found' or 'read error'. It would be interesting to see the output of 'lsdev -v' from the loader prompt. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [patch] IPMI KCS can drop the lock while servicing a request
On 23 March 2013 20:11, Eric van Gyzen wrote: > At work, we discovered that our application's IPMI thread would often use a > lot of CPU time. The KCS thread uses DELAY to wait for the BMC, so it can > run without sleeping for a "long" time with a slow BMC. It also holds the > ipmi_softc.ipmi_lock during this time. When using adaptive mutexes, an > application thread that wants to operate on the ipmi_pending_requests list > will also spin during this same time. > > We see no reason that the KCS thread needs to hold the lock while servicing > a request. We've been running with the attached patch for a few months, > with no ill effects. Typically holding a lock is to serialise both program state and hardware state. The whole "unlock; do blocking work or sleep; lock" thing needs to be very carefully thought out. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: problem building world on 9.1 stable after changing 100% to svn
Finally have all working as expected. I finally just erased sources and ports, rebuilt and restarted freebsd and I'm finally ok. Lowell, thanks for your support and suggestions. I will now try to forget all csup, cvsup, etc. Thank goodness that portmaster still handles ports as always and svn is working fine. ed On Sat, Mar 30, 2013 at 4:10 PM, Edwin L. Culp W. wrote: > > > On Sat, Mar 30, 2013 at 3:47 PM, Lowell Gilbert < > freebsd-stable-lo...@be-well.ilk.org> wrote: > >> "Edwin L. Culp W." writes: >> >> > On Sat, Mar 30, 2013 at 3:23 PM, Lowell Gilbert < >> > freebsd-stable-lo...@be-well.ilk.org> wrote: >> >> It's possible you're building with the wrong set of headers, but every >> >> case I can think of would have given you an error earlier than this. >> >> Do you get any output from: >> >> # cd /usr/src/usr.bin/xinstall/ && svn status xinstall.c >> >> by any chance? >> >> >> >> What command did you use for your initial source checkout from >> SubVersion? >> >> >> > >> > I did it twice. >> > >> > # cd /usr/src/usr.bin/xinstall/ && svn status xinstall.c >> > M xinstall.c >> > # cd /usr/src/usr.bin/xinstall/ && svn status xinstall.c >> > M xinstall.c >> > >> > Hopefully you will find something there. >> >> Yup, that's clearly wrong. For the moment I'll assume you did the >> initial checkout correctly. Or at least in some wrong way that doesn't >> require you to remove the whole tree and check it out again (which >> definitely is what you should have done the first time, by the way). >> > > If the below instructions don't solve it, I'll remover the tree. It is > the same tree that I was updating with cvsup daily for years. It could be > causing the problem. > > >> I'm guessing the revert part is what you really need, but go to the >> /usr/src directory and try: >> # svn cleanup >> or >> # svn revert -R * >> >> and if you're still lost, >> # svn status . >> will tell you what is in your tree that is different from a pristine one. >> > > Thanks a lot, > > This will keep me busy and should solve the problem, if not erase and > restart ;) I'm sure that will do it. > > Enjoy what is left of Easter if you live where it is celebrated. > > ed > -- Bienes Raíces in Coatepec, Veracruz, Mexico http://www.facebook.com/pages/Inmobiliaria-Bienes-Raices-httpEcoManiainfo/102249989850215?sk=photos_albums ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: problem building world on 9.1 stable after changing 100% to svn
On Tue, Apr 02, 2013 at 08:15:40PM -0500, Edwin L. Culp W. wrote: > Finally have all working as expected. I finally just erased sources and > ports, rebuilt and restarted freebsd and I'm finally ok. > > Lowell, thanks for your support and suggestions. I will now try to forget > all csup, cvsup, etc. Thank goodness that portmaster still handles ports > as always and svn is working fine. Don't forget to: - rm -fr /usr/sup if you've used cvsup on the system - rm -fr /var/db/sup/* if you've used csup on the system -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: gptzfsboot: error 4 lba 30
On Tue, 2 Apr 2013 17:07:14 -0400 John Baldwin wrote: > On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote: > > Hi. > > > > On one of my fresh installed servers I am seeing the following > > output during > boot: > > > > gptzfsboot: error 4 lba 30 ... > > gptzfsboot: error 4 lba 31 > > Humm, do you have disks that the BIOS sees that are small? An error > code of 4 means 'sector not found' or 'read error'. It would be > interesting to see the output of 'lsdev -v' from the loader prompt. > by the way, where I can find a transcript of codes? -- wbr, tiger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: gptzfsboot: error 4 lba 30
on 03/04/2013 09:12 Sergey V. Dyatko said the following: > On Tue, 2 Apr 2013 17:07:14 -0400 > John Baldwin wrote: > >> On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote: >>> Hi. >>> >>> On one of my fresh installed servers I am seeing the following >>> output during >> boot: >>> >>> gptzfsboot: error 4 lba 30 > ... >>> gptzfsboot: error 4 lba 31 >> >> Humm, do you have disks that the BIOS sees that are small? An error >> code of 4 means 'sector not found' or 'read error'. It would be >> interesting to see the output of 'lsdev -v' from the loader prompt. >> > > by the way, where I can find a transcript of codes? In the BIOS Int 13h documentation. E.g.: http://stanislavs.org/helppc/int_13-2.html http://www.bioscentral.com/misc/biosint13.htm -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
