freebsd-current Digest, Vol 327, Issue 7
ps81 at mail.ru
ps81 at mail.ru
Thu Jan 21 16:38:18 UTC 2010
Çäðàâñòâóéòå, Freebsd-current-request.
Âû ïèñàëè 21 ÿíâàðÿ 2010 ã., 4:47:19:
> Send freebsd-current mailing list submissions to
> freebsd-current at freebsd.org
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> or, via email, send a message with subject or body 'help' to
> freebsd-current-request at freebsd.org
> You can reach the person managing the list at
> freebsd-current-owner at freebsd.org
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-current digest..."
> Today's Topics:
> 1. Re: Pack of CAM improvements (Henri Hennebert)
> 2. stacked unionfs freeze and crash FreeBSD (David Naylor)
> 3. Re: Pack of CAM improvements (James R. Van Artsdalen)
> 4. Re: bce(4) on IBM BladeCenter HS22 (Oliver Fromme)
> 5. Re: stacked unionfs freeze and crash FreeBSD (Gary Jennejohn)
> 6. Buildworld failure with -j24 and ZFS on GPT on Core i7-860
> system (Matt Thyer)
> 7. Re: stacked unionfs freeze and crash FreeBSD (David Naylor)
> 8. Re: stacked unionfs freeze and crash FreeBSD (David Naylor)
> 9. Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system (Dan Nelson)
> 10. 8.0-STABLE r200182: weird behaviour of a service in a jail (K.R.)
> 11. Re: stacked unionfs freeze and crash FreeBSD (Andriy Gapon)
> 12. Re: [FreeBSD 8/9] USB webcamd and video4bsd: Call for testing
> [SEC=UNCLASSIFIED] (Hans Petter Selasky)
> 13. Re: [FreeBSD 8/9] USB webcamd and video4bsd: Call for testing
> (Hans Petter Selasky)
> 14. Re: [FreeBSD 8/9] USB webcamd and video4bsd: Call for testing
> (Hans Petter Selasky)
> 15. HEADSUP: BSDL bc/dc in head [Was: svn commit: r202719 - in
> head: . gnu/usr.bin usr.bin usr.bin/bc usr.bin/bc/USD.doc
> usr.bin/dc usr.bin/dc/USD.doc] (Gabor Kovesdan)
> 16. Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system (Matt Thyer)
> 17. Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system (Dan Nelson)
> 18. Re: multimedia/libv4l/ (video4bsd.ko) -> Fatal trap 12: page
> fault while in kernel mode [SEC=UNCLASSIFIED] (Wilkinson, Alex)
> 19. cvsup crashing (Pav Lucistnik)
> 20. Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system (Matt Thyer)
> 21. Re: cvsup crashing (Sean C. Farley)
> 22. Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system (Daniel Eischen)
> ----------------------------------------------------------------------
> Message: 1
> Date: Wed, 20 Jan 2010 14:34:07 +0100
> From: Henri Hennebert <hlh at restart.be>
> Subject: Re: Pack of CAM improvements
> To: Alexander Motin <mav at freebsd.org>
> Cc: FreeBSD-Current <freebsd-current at freebsd.org>, FreeBSD Stable
> <freebsd-stable at freebsd.org>
> Message-ID: <4B57064F.9060704 at restart.be>
> Content-Type: text/plain; charset=KOI8-R; format=flowed
> On 01/19/2010 17:12, Alexander Motin wrote:
>> Hi.
>>
>> I've made a patch, that should solve set of problems of CAM ATA and CAM
>> generally. I would like to ask for testing and feedback.
>>
>> What patch does:
>> - It unifies bus reset/probe sequence. Whenever bus attached at boot or
>> later, CAM will automatically reset and scan it. It allows to remove
>> duplicate code from many drivers.
>> - Any bus, attached before CAM completed it's boot-time initialization,
>> will equally join to the process, delaying boot if needed.
>> - New kern.cam.boot_delay loader tunable should help controllers that
>> are still unable to register their buses in time (such as slow USB/
>> PCCard/ CardBus devices).
> With kern.cam.boot_delay=15000 (I suppose that it was in ms) I can now
> boot from my sim card reader.
> Thanks
> Henri
>> - To allow synchronization between different CAM levels, concept of
>> requests priorities was extended. Priorities now split between several
>> "run levels". Device can be freezed at specified level, allowing higher
>> priority requests to pass. For example, no payload requests allowed,
>> until PMP driver enable port. ATA XPT negotiate transfer parameters,
>> periph driver configure caching and so on.
>> - Frozen requests are no more counted by request allocation scheduler.
>> It fixes deadlocks, when frozen low priority payload requests occupying
>> slots, required by higher levels to manage theit execution.
>> - Two last changes were holding proper ATA reinitialization and error
>> recovery implementation. Now it is done: SATA controllers and Port
>> Multipliers now implement automatic hot-plug and should correctly
>> recover from timeouts and bus resets.
>>
>> Patch can be found here:
>> http://people.freebsd.org/~mav/cam-ata.20100119.patch
>>
>> Feedback as always welcome.
>>
> ------------------------------
> Message: 2
> Date: Wed, 20 Jan 2010 15:43:12 +0200
> From: David Naylor <naylor.b.david at gmail.com>
> Subject: stacked unionfs freeze and crash FreeBSD
> To: freebsd-current at freebsd.org
> Message-ID: <201001201543.15818.naylor.b.david at gmail.com>
> Content-Type: text/plain; charset="us-ascii"
> Skipped content of type multipart/mixed-------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 196 bytes
> Desc: This is a digitally signed message part.
> Url :
> http://lists.freebsd.org/pipermail/freebsd-current/attachments/20100120/d55be9ea/attachment-0001.pgp
> ------------------------------
> Message: 3
> Date: Wed, 20 Jan 2010 07:55:24 -0600
> From: "James R. Van Artsdalen" <james-freebsd-current at jrv.org>
> Subject: Re: Pack of CAM improvements
> Cc: Alexander Motin <mav at freebsd.org>, FreeBSD-Current
> <freebsd-current at freebsd.org>
> Message-ID: <4B570B4C.9000203 at jrv.org>
> Content-Type: text/plain; charset=ISO-8859-1
> Scott Long wrote:
>> I've fought many times against delay values like this. They never
>> work well enough.
> At some point I hope to add support for staggered spin-ups, perhaps a
> loader.conf setting for people with more than 20-30 disks. At the
> 100-120 disk level it seems unlikely that any reasonable fixed delay
> would be reasonable.
> ------------------------------
> Message: 4
> Date: Wed, 20 Jan 2010 15:02:01 +0100 (CET)
> From: Oliver Fromme <olli at lurza.secnetix.de>
> Subject: Re: bce(4) on IBM BladeCenter HS22
> To: freebsd-current at FreeBSD.ORG, pyunyh at gmail.com
> Message-ID: <201001201402.o0KE21oc010264 at lurza.secnetix.de>
> Content-Type: text/plain; charset=ISO-8859-1
> Pyun YongHyeon wrote:
>> On Tue, Jan 19, 2010 at 08:23:13PM +0100, Oliver Fromme wrote:
>> > Pyun YongHyeon <pyunyh at gmail.com> wrote:
>> > > Thanks for the detailed information. I vaguely guess bce(4) used
>> > > wrong PHY address for controller. How about attached patch?
>> > > The patch just reset the PHY address to 1, it's not correct way to
>> > > set it but just wants to know whether brgphy(4) is attached to the
>> > > PHY.
>> >
>> > Unfortunately, it produces almost the same output,
>> > except the registers now read 0xffff instead of 0x0000:
>> >
>> :-(
>>
>> Ok, could you remove the safety belt of bce_miibus_read_reg() to
>> allow accessing all PHY address? You can comment out
>> sc->bce_phy_addr check in bce_miibus_read_reg() to allow
>> mii_phy_probe try to read all 32 possible PHY addresses.
>> Does mii(4) probe manage to read something?
> No luck, I'm afraid (as was expected). No PHY can be found
> on any of the addresses. The PHY addresses 2 and 31 return
> 0x0000, all others return 0xffff.
> While debugging and searching I found this message from
> David Christensen:
> http://lists.freebsd.org/pipermail/freebsd-net/2009-August/022648.html
> It seems that the PHY on the 5709S is different from the
> others and requires some non-trivial code to be written. :-(
> I posted a follow-up in the freebsd-net list and copied
> David. Maybe he has some news.
> This whole issue is quite important. IBM is phasing out
> the previous blade generation (HS21), so all new blades
> are HS22 which have the BCM5709S interfaces. As it stands
> now, FreeBSD cannot be used on IBM blades.
> Best regards
> Oliver
> --
> Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
> Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
> secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
> chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
> FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
> "If you aim the gun at your foot and pull the trigger, it's
> UNIX's job to ensure reliable delivery of the bullet to
> where you aimed the gun (in this case, Mr. Foot)."
> -- Terry Lambert, FreeBSD-hackers mailing list.
> ------------------------------
> Message: 5
> Date: Wed, 20 Jan 2010 16:28:21 +0100
> From: Gary Jennejohn <gary.jennejohn at freenet.de>
> Subject: Re: stacked unionfs freeze and crash FreeBSD
> To: David Naylor <naylor.b.david at gmail.com>
> Cc: freebsd-current at freebsd.org
> Message-ID: <20100120162821.3f53af6a at ernst.jennejohn.org>
> Content-Type: text/plain; charset=US-ASCII
> On Wed, 20 Jan 2010 15:43:12 +0200
> David Naylor <naylor.b.david at gmail.com> wrote:
>> Hi,
>>
>> The attached script, that uses stacked unionfs, causes FreeBSD-9 (cvsup
>> yesterday) to freeze and FreeBSD-8 (cvsup two days ago) to crash:
>>
>> Fatal double fault
>> rip-0xffffffff81e4c1
>> rsp=0xffffff80b133ef50
>> rbp=0xffffff80b133f150
>> cupid = 2; apic id = 02
>> panic: double fault
>> cpuid = 2
>> uptime: 1h44m35s
>> cannot dump. Device not defined or unavailable
>>
>>
>> Both systems use the stock GENERIC kernel, i.e. -9 had full diagnostics built
>> in (and was run under VirtualBox) and -8 had no diagnostics (and was run
>> native).
>>
>> A LOR is produces prior to freezing under -9 (quiet a time prior). See
>> kern/141950.
>>
>> The script uses unionfs to build ports (in an attempt to create a tinderbox
>> without the need to delete and/or extract packages). To use the script to:
>>
>> # mkdir /tmp/localbase /tmp/builddir
>> # env LOCALBASE=/tmp/localbase BUILDDIR=/tmp/builddir ./ports-union-builder.sh
>>
> Is your /tmp big enough?
>> This will try build everything for x11/xorg.
>> Is it possible that VirtualBox is interfering in getting usable diagnostics
>> for -9
>>
> Who knows? You might try posting your shell script so others can give
> it a whirl on a "real" 9-current system.
>> and how can I setup a dump device for -8. Currently I have:
>>
>> # swapinfo
>> Device 1K-blocks Used Avail Capacity
>> /dev/ad4s1b 8388608 0 8388608 0%
>> /dev/ad8s1b 8388608 0 8388608 0%
>> Total 16777216 0 16777216 0%
>>
> Do you have dumpdev defined in /etc/rc.conf and/or do you see
> /dev/dumpdev? Having /dev/dumpdev indicates that dumpon succeeded.
> Do you have less than 8GB of memory? See dumpon(8) for restrictions.
> ---
> Gary Jennejohn
> ------------------------------
> Message: 6
> Date: Thu, 21 Jan 2010 01:39:38 +1030
> From: Matt Thyer <matt.thyer at gmail.com>
> Subject: Buildworld failure with -j24 and ZFS on GPT on Core i7-860
> system
> To: current at freebsd.org
> Message-ID:
> <fa58e4891001200709s10933634g5ef2820533ed8bc6 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> I typically buildworld with a parallel make of hw.ncpu * 3 which results in
> -j24 on my new system (Intel Core i7-860, 8GB RAM).
> I've not been able to buildworld natively on this new system (with ZFS - I
> have not tried non-ZFS natively yet) but have been able to buildworld in a
> virtual machine under Windows 7 64bit VMware Server 2.0.2 with 2 virtual
> CPUs (hence -j6 for buildworld).
> Both 8-STABLE 32bit (this VM is non-ZFS) and CURRENT 64bit (a ZFS system)
> will build as a VM (-j6) but a native 64bit FreeBSD CURRENT (ZFS) fails.
> The CURRENT 64bit systems were installed from the allbsd.org JPSNAP DVD of
> 18 Jan 2010 and both can successfully buildworld with -j1 (Virtual and
> native).
> Build failure is:
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 asn1_err.h
> /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/heim_asn1.h
> cms_asn1.h rfc2459_asn1.h krb5_asn1.h pkinit_asn1.h pkcs8_asn1.h
> pkcs9_asn1.h pkcs12_asn1.h digest_asn1.h kx509_asn1.h
> /usr/obj/usr/src/tmp/usr/include
> sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libasn1.so.10
> /usr/obj/usr/src/tmp/usr/lib
> ln -fs libasn1.so.10 /usr/obj/usr/src/tmp/usr/lib/libasn1.so
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
> I guess this is a FreeBSD ZFS bug of some kind.
> I have not yet prepared another non-ZFS hard disk for native testing (though
> I do have a spare hard disk available and will test this soon).
> ------------------------------
> Message: 7
> Date: Wed, 20 Jan 2010 18:05:54 +0200
> From: David Naylor <naylor.b.david at gmail.com>
> Subject: Re: stacked unionfs freeze and crash FreeBSD
> To: gary.jennejohn at freenet.de
> Cc: freebsd-current at freebsd.org
> Message-ID: <201001201805.57798.naylor.b.david at gmail.com>
> Content-Type: text/plain; charset="us-ascii"
> Skipped content of type multipart/mixed-------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 196 bytes
> Desc: This is a digitally signed message part.
> Url :
> http://lists.freebsd.org/pipermail/freebsd-current/attachments/20100120/b81ceda1/attachment-0001.pgp
> ------------------------------
> Message: 8
> Date: Wed, 20 Jan 2010 18:34:45 +0200
> From: David Naylor <naylor.b.david at gmail.com>
> Subject: Re: stacked unionfs freeze and crash FreeBSD
> To: gary.jennejohn at freenet.de
> Cc: freebsd-current at freebsd.org
> Message-ID: <201001201834.48466.naylor.b.david at gmail.com>
> Content-Type: text/plain; charset="us-ascii"
> On Wednesday 20 January 2010 18:05:54 David Naylor wrote:
>> On Wednesday 20 January 2010 17:28:21 Gary Jennejohn wrote:
>> > On Wed, 20 Jan 2010 15:43:12 +0200 David Naylor wrote:
>> > > Hi,
>> > >
>> > > The attached script, that uses stacked unionfs, causes FreeBSD-9 (cvsup
>> > > yesterday) to freeze and FreeBSD-8 (cvsup two days ago) to crash:
>> > >
>> > > Fatal double fault
>> > > rip-0xffffffff81e4c1
>> > > rsp=0xffffff80b133ef50
>> > > rbp=0xffffff80b133f150
>> > > cupid = 2; apic id = 02
>> > > panic: double fault
>> > > cpuid = 2
>> > > uptime: 1h44m35s
>> > > cannot dump. Device not defined or unavailable
>> > >
>> > >
>> > > Both systems use the stock GENERIC kernel, i.e. -9 had full diagnostics
>> > > built in (and was run under VirtualBox) and -8 had no diagnostics (and
>> > > was run native).
>> > >
>> > > A LOR is produces prior to freezing under -9 (quiet a time prior). See
>> > > kern/141950.
>> > >
>> > > The script uses unionfs to build ports (in an attempt to create a
>> > > tinderbox without the need to delete and/or extract packages). To use
>> > > the script to:
>> > >
>> > > # mkdir /tmp/localbase /tmp/builddir
>> > > # env LOCALBASE=/tmp/localbase BUILDDIR=/tmp/builddir
>> > > ./ports-union-builder.sh
>> >
>> > Is your /tmp big enough?
>>
>> I was actually using /home, didn't think people wanted to contaminate that
>> directory. Plenty of space.
>>
>> > > This will try build everything for x11/xorg.
>> > >
>> > > Is it possible that VirtualBox is interfering in getting usable
>> > > diagnostics for -9
>> >
>> > Who knows? You might try posting your shell script so others can give
>> > it a whirl on a "real" 9-current system.
>>
>> I did attach the script. Guess mailer ate it, again. I'll try again...
>>
>> > > and how can I setup a dump device for -8. Currently I have:
>> > >
>> > > # swapinfo
>> > > Device 1K-blocks Used Avail Capacity
>> > > /dev/ad4s1b 8388608 0 8388608 0%
>> > > /dev/ad8s1b 8388608 0 8388608 0%
>> > > Total 16777216 0 16777216 0%
>> >
>> > Do you have dumpdev defined in /etc/rc.conf and/or do you see
>> > /dev/dumpdev? Having /dev/dumpdev indicates that dumpon succeeded.
>>
>> No I haven't and no I don't. I thought it automatically used swap?
>>
>> I'll 'activate' it and post the results.
> Here it is. If anyone ones the full core.txt just shout.
> #0 doadump () at pcpu.h:223
> 223 pcpu.h: No such file or directory.
> in pcpu.h
> (kgdb) #0 doadump () at pcpu.h:223
> #1 0xffffffff80589ba9 in boot (howto=260)
> at /usr/src/sys/kern/kern_shutdown.c:416
> #2 0xffffffff80589fdc in panic (fmt=0xffffffff8098bd81 "double fault")
> at /usr/src/sys/kern/kern_shutdown.c:579
> #3 0xffffffff8086e546 in dblfault_handler (frame=Variable "frame" is not
> available.)
> at /usr/src/sys/amd64/amd64/trap.c:884
> #4 0xffffffff808557fc in Xdblfault ()
> at /usr/src/sys/amd64/amd64/exception.S:278
> #5 0xffffffff81e464c1 in unionfs_statfs (mp=Variable "mp" is not available.)
> at
> /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vfsops.c:428
> Previous frame inner to this frame (corrupt stack?)
> (kgdb)
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 196 bytes
> Desc: This is a digitally signed message part.
> Url :
> http://lists.freebsd.org/pipermail/freebsd-current/attachments/20100120/c0325656/attachment-0001.pgp
> ------------------------------
> Message: 9
> Date: Wed, 20 Jan 2010 10:23:26 -0600
> From: Dan Nelson <dnelson at allantgroup.com>
> Subject: Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system
> To: Matt Thyer <matt.thyer at gmail.com>
> Cc: current at freebsd.org
> Message-ID: <20100120162326.GD50360 at dan.emsphone.com>
> Content-Type: text/plain; charset=us-ascii
> In the last episode (Jan 21), Matt Thyer said:
>> I typically buildworld with a parallel make of hw.ncpu * 3 which results
>> in -j24 on my new system (Intel Core i7-860, 8GB RAM).
>>
>> I've not been able to buildworld natively on this new system (with ZFS - I
>> have not tried non-ZFS natively yet) but have been able to buildworld in a
>> virtual machine under Windows 7 64bit VMware Server 2.0.2 with 2 virtual
>> CPUs (hence -j6 for buildworld).
>>
>> Both 8-STABLE 32bit (this VM is non-ZFS) and CURRENT 64bit (a ZFS system)
>> will build as a VM (-j6) but a native 64bit FreeBSD CURRENT (ZFS) fails.
>>
>> The CURRENT 64bit systems were installed from the allbsd.org JPSNAP DVD of
>> 18 Jan 2010 and both can successfully buildworld with -j1 (Virtual and
>> native).
>>
>> Build failure is:
>>
>> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 asn1_err.h
>> /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/heim_asn1.h
>> cms_asn1.h rfc2459_asn1.h krb5_asn1.h pkinit_asn1.h pkcs8_asn1.h
>> pkcs9_asn1.h pkcs12_asn1.h digest_asn1.h kx509_asn1.h
>> /usr/obj/usr/src/tmp/usr/include
>> sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libasn1.so.10
>> /usr/obj/usr/src/tmp/usr/lib
>> ln -fs libasn1.so.10 /usr/obj/usr/src/tmp/usr/lib/libasn1.so
>> 1 error
>> *** Error code 2
>> 1 error
>> *** Error code 2
>> 1 error
>> *** Error code 2
>> 1 error
> It's much more likely to be a Makefile dependency problem than a ZFS bug.
> You will need to look much farther up in your log to see the real error
> message. Make will wait for the other 23 jobs to finish before returning,
> so what you posted was the output of one of the other jobs, plus the output
> of each parent make as it exits with an error code.
> --
> Dan Nelson
> dnelson at allantgroup.com
> ------------------------------
> Message: 10
> Date: Wed, 20 Jan 2010 20:03:22 +0300
> From: "K.R." <spambox at haruhiism.net>
> Subject: 8.0-STABLE r200182: weird behaviour of a service in a jail
> To: FreeBSD Current <freebsd-current at freebsd.org>
> Message-ID: <4B57375A.4000309 at haruhiism.net>
> Content-Type: text/plain; charset=UTF-8
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
> I'm running FreeBSD 8.0-STABLE #0 r200182: Mon Dec 7 03:32:18 JST
> 2009 SMP (4 cores) with an uptime of ~44 days and starting about 1.5
> weeks ago, I've noticed a weird behaviour with a jailed ircd (a hybrid
> spin-off); it listens on a cloned address on lo0 and the connections
> to it are redirected by pf. Everything was fine until once I noticed
> that I (and other users, of course) cannot connect to the irc server -
> the connection is established but then it just hangs indefinitely.
> This problem has never manifested itself on 7.0-STABLE and 7.2-STABLE
> on a single core system (ircd was also running inside a jail there).
> It looks like this from the outside:
> % telnet irc.server.here 6667
> Trying (ip address here)...
> Connected to irc.server.here.
> Escape character is '^]'.
> And that's it; normally I'd get "439 * :Please wait while we process
> your connection."
> Same with another - server link - port.
> If I attempt to connect to the server's "real" listening IP from the
> machine running ircd, however, I get
> % telnet irc.server.here 6667
> Trying (ip address here)...
> Connected to irc.server.here.
> Escape character is '^]'.
> Connection closed by foreign host. (immediately, with no pause)
> And on the server link port, it's still the same indefinite wait.
> Amusingly enough, a simple REHASH - which resets ircd's listening
> sockets - fixes the problem. The developers of the ircd state that
> this behaviour is unexpected and there's nothing wrong with the source
> code on their end (which I can believe). The ircd uses kqueue, if it
> matters.
> There are no abnormalities with sshd and sendmail in the same jail. No
> problems ever arised in the 5 other jails running HTTP, SMTP and other
> services; but that might be because ircd's load is much bigger in
> terms of total number of established connections.
> How should I debug this issue? For now, I've moved the jail to an
> external IP address to see if the problem persists.
> - --
> Kamigishi Rei
> KREI-RIPE
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
>
> iQEcBAEBAgAGBQJLVzdTAAoJEPAgyqbDpP+efJUIAKB9MJgLiTnlQYkPnLXCqroG
> fQqSilPODsztqkRc9MbbDLhUjk0PtBO/hFEIUrv2fUqOBbbf/H8TSRn7BdQuYUVU
> 6PsBrl+/e/jhP6y8wRsNudijlE1cQfxsjFJoNnoEHFKBY//6SedvMwMvxTy96CHf
> WOkBnNJVUt/YB/Fq/DdZtNUlZpOWxxtGWHf/C75q5IdGfjk6R3uLABazUhIGHJoK
> We/3gG2IVTf3zzKgCPwDaj3sLYQ1wkP4rOoAQjU+3pLynnR3xnQzv3XG2MtX3xEf
> bFh2RrN/0ufoNgUDJeEVptJDveTYbpHIzCm9iVkETM7Tv0A/CSzIwy6QMbB/eIU=
> =y1oH
> -----END PGP SIGNATURE-----
> ------------------------------
> Message: 11
> Date: Wed, 20 Jan 2010 19:16:59 +0200
> From: Andriy Gapon <avg at icyb.net.ua>
> Subject: Re: stacked unionfs freeze and crash FreeBSD
> To: David Naylor <naylor.b.david at gmail.com>
> Cc: freebsd-current at freebsd.org
> Message-ID: <4B573A8B.8080306 at icyb.net.ua>
> Content-Type: text/plain; charset=ISO-8859-1
> on 20/01/2010 18:34 David Naylor said the following:
>>
>> Here it is. If anyone ones the full core.txt just shout.
>>
>> #0 doadump () at pcpu.h:223
>> 223 pcpu.h: No such file or directory.
>> in pcpu.h
>> (kgdb) #0 doadump () at pcpu.h:223
>> #1 0xffffffff80589ba9 in boot (howto=260)
>> at /usr/src/sys/kern/kern_shutdown.c:416
>> #2 0xffffffff80589fdc in panic (fmt=0xffffffff8098bd81 "double fault")
>> at /usr/src/sys/kern/kern_shutdown.c:579
>> #3 0xffffffff8086e546 in dblfault_handler (frame=Variable "frame" is not
>> available.)
>> at /usr/src/sys/amd64/amd64/trap.c:884
>> #4 0xffffffff808557fc in Xdblfault ()
>> at /usr/src/sys/amd64/amd64/exception.S:278
>> #5 0xffffffff81e464c1 in unionfs_statfs (mp=Variable "mp" is not available.)
>> at /usr/src/sys/modules/unionfs/../../fs/unionfs/union_vfsops.c:428
>> Previous frame inner to this frame (corrupt stack?)
>> (kgdb)
> Double-fault could indicate stack overflow.
> --
> Andriy Gapon
> ------------------------------
> Message: 12
> Date: Wed, 20 Jan 2010 18:51:50 +0100
> From: Hans Petter Selasky <hselasky at c2i.net>
> Subject: Re: [FreeBSD 8/9] USB webcamd and video4bsd: Call for testing
> [SEC=UNCLASSIFIED]
> To: freebsd-usb at freebsd.org
> Cc: freebsd-current at freebsd.org, "Wilkinson, Alex"
> <alex.wilkinson at dsto.defence.gov.au>
> Message-ID: <201001201851.50069.hselasky at c2i.net>
> Content-Type: Text/Plain; charset="iso-8859-1"
> On Wednesday 20 January 2010 07:46:20 Wilkinson, Alex wrote:
>> And works dam well.
>>
> Thanks.
>> What apps could i expect this to work with in the future ? skype ?
> Basically all V4L appllications.
> --HPS
> ------------------------------
> Message: 13
> Date: Wed, 20 Jan 2010 18:56:34 +0100
> From: Hans Petter Selasky <hselasky at c2i.net>
> Subject: Re: [FreeBSD 8/9] USB webcamd and video4bsd: Call for testing
> To: Henry Hu <henry.hu.sh at gmail.com>
> Cc: freebsd-multimedia at freebsd.org, freebsd-current at freebsd.org,
> freebsd-usb at freebsd.org
> Message-ID: <201001201856.35002.hselasky at c2i.net>
> Content-Type: Text/Plain; charset="iso-8859-1"
> Hi,
> On Tuesday 19 January 2010 18:33:14 Henry Hu wrote:
>> There are some problems, however. First, when I start pwcview with an
>> unsupported mode, the content of the window is green, and I cannot
>> kill the process. Only after terminating webcamd can I terminate the
>> process.
> I know what the problem is, and I will try to fix it in the next release of
> webcamd.
>> Second, I cannot restart pwcview without restarting webcamd. At the
>> second time I start pwcview with -s vga, the window is green, and I
>> cannot kill it. The situation is similar to unsupported size.
>>
>> I've also tried applications such as pidgin, skype and mplayer.
>> However no one successfully played from the webcam. I doubt it needs
>> some extra work.
> You need to recompile these applications after installing libv4l. I have vlc
> working with the new stuff.
>>
>> Thanks again for the great work! It never caused any kernel panic, and
>> the programs are fairly stable.
> Thanks!
> --HPS
> ------------------------------
> Message: 14
> Date: Wed, 20 Jan 2010 18:59:30 +0100
> From: Hans Petter Selasky <hselasky at c2i.net>
> Subject: Re: [FreeBSD 8/9] USB webcamd and video4bsd: Call for testing
> To: vova at fbsd.ru
> Cc: freebsd-multimedia at freebsd.org, freebsd-current at freebsd.org,
> freebsd-usb at freebsd.org
> Message-ID: <201001201859.30886.hselasky at c2i.net>
> Content-Type: Text/Plain; charset="koi8-r"
> On Tuesday 19 January 2010 21:12:32 Vladimir Grebenschikov wrote:
>> Hi
>>
>> I've tested with recent ports.
>>
>> pwcview works fine, both vga and sif
>>
>> but skype still sees /dev/video0 but fails to play anything from it,
>> multimedia/cheese even does not sees webcam.
>>
>> Is it supposed, or I am so unlucky ?
> Yes it is supposed to work, but you maybe need to tweak/rebuild the gstreamer
> V4L2 code.
> --HPS
> ------------------------------
> Message: 15
> Date: Wed, 20 Jan 2010 22:39:27 +0100
> From: Gabor Kovesdan <gabor at FreeBSD.org>
> Subject: HEADSUP: BSDL bc/dc in head [Was: svn commit: r202719 - in
> head: . gnu/usr.bin usr.bin usr.bin/bc usr.bin/bc/USD.doc usr.bin/dc
> usr.bin/dc/USD.doc]
> To: FreeBSD Current <freebsd-current at freebsd.org>
> Message-ID: <4B57780F.4070907 at FreeBSD.org>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Hi all,
> I've just committed the BSDL versions of bc/dc ported from OpenBSD.
> Thanks goes to Erwin for the exp-run and to Google for sponsoring my
> work on text processing tools back in 2008. It is one of the results of
> that summer. Unfortunately, it took a bit long because there were more
> complicated problems with grep but the work I started that time hasn't
> got lost and further pieces are supposed to come slowly as they are ready.
> For now, the GNU version is still there in head but detached from the
> build. I'll add ports of GNU bc/dc and if BSDL bc/dc does fine I'll
> remove those form HEAD. Please report if you see any regressions or if
> you just have comments.
> Regards,
> Gabor
> -------- Mensaje original --------
> Asunto: svn commit: r202719 - in head: . gnu/usr.bin usr.bin usr.bin/bc
> usr.bin/bc/USD.doc usr.bin/dc usr.bin/dc/USD.doc
> Fecha: Wed, 20 Jan 2010 21:30:52 +0000 (UTC)
> De: Gabor Kovesdan <gabor at FreeBSD.org>
> Para: src-committers at freebsd.org, svn-src-all at freebsd.org,
> svn-src-head at freebsd.org
> Author: gabor (doc,ports committer)
> Date: Wed Jan 20 21:30:52 2010
> New Revision: 202719
> URL: http://svn.freebsd.org/changeset/base/202719
> Log:
> Replace GNU bc/dc with BSDL versions ported from OpenBSD. They have a good
> compatibility level with the GNU counterparts and have shown to be mature
> enough. For now, the GNU versions aren't removed from the tree, just detached
> from the build.
> Sponsored by: Google Summer of Code 2008
> Portbuild run by: erwin
> Approved by: delphij
> Added:
> head/usr.bin/bc/
> head/usr.bin/bc/Makefile (contents, props changed)
> head/usr.bin/bc/USD.doc/
> head/usr.bin/bc/USD.doc/Makefile (contents, props changed)
> head/usr.bin/bc/USD.doc/bc (contents, props changed)
> head/usr.bin/bc/bc.1 (contents, props changed)
> head/usr.bin/bc/bc.library (contents, props changed)
> head/usr.bin/bc/bc.y (contents, props changed)
> head/usr.bin/bc/extern.h (contents, props changed)
> head/usr.bin/bc/pathnames.h (contents, props changed)
> head/usr.bin/bc/scan.l (contents, props changed)
> head/usr.bin/dc/
> head/usr.bin/dc/Makefile (contents, props changed)
> head/usr.bin/dc/USD.doc/
> head/usr.bin/dc/USD.doc/Makefile (contents, props changed)
> head/usr.bin/dc/USD.doc/dc (contents, props changed)
> head/usr.bin/dc/bcode.c (contents, props changed)
> head/usr.bin/dc/bcode.h (contents, props changed)
> head/usr.bin/dc/dc.1 (contents, props changed)
> head/usr.bin/dc/dc.c (contents, props changed)
> head/usr.bin/dc/extern.h (contents, props changed)
> head/usr.bin/dc/inout.c (contents, props changed)
> head/usr.bin/dc/mem.c (contents, props changed)
> head/usr.bin/dc/stack.c (contents, props changed)
> Modified:
> head/ObsoleteFiles.inc
> head/gnu/usr.bin/Makefile
> head/usr.bin/Makefile
> Modified: head/ObsoleteFiles.inc
> ==============================================================================
> --- head/ObsoleteFiles.inc Wed Jan 20 21:12:30 2010 (r202718)
> +++ head/ObsoleteFiles.inc Wed Jan 20 21:30:52 2010 (r202719)
> @@ -14,6 +14,13 @@
> # The file is partitioned: OLD_FILES first, then OLD_LIBS and OLD_DIRS last.
> #
> +# 20100120: replacing GNU bc/dc with BSDL versions
> +OLD_FILES+=usr/share/examples/bc/ckbook.b
> +OLD_FILES+=usr/share/examples/bc/pi.b
> +OLD_FILES+=usr/share/examples/bc/primes.b
> +OLD_FILES+=usr/share/examples/bc/twins.b
> +OLD_FILES+=usr/share/info/dc.info.gz
> +OLD_DIRS+=usr/share/examples/bc
> # 20100114: removal of ttyslot(3)
> OLD_FILES+=usr/share/man/man3/ttyslot.3.gz
> # 20100113: remove utmp.h, replace it by utmpx.h
> Modified: head/gnu/usr.bin/Makefile
> ==============================================================================
> --- head/gnu/usr.bin/Makefile Wed Jan 20 21:12:30 2010 (r202718)
> +++ head/gnu/usr.bin/Makefile Wed Jan 20 21:30:52 2010 (r202719)
> @@ -2,12 +2,10 @@
> .include<bsd.own.mk>
> -SUBDIR= bc \
> - ${_binutils} \
> +SUBDIR= ${_binutils} \
> ${_cc} \
> ${_cpio} \
> ${_cvs} \
> - dc \
> dialog \
> diff \
> diff3 \
> Modified: head/usr.bin/Makefile
> ==============================================================================
> --- head/usr.bin/Makefile Wed Jan 20 21:12:30 2010 (r202718)
> +++ head/usr.bin/Makefile Wed Jan 20 21:30:52 2010 (r202719)
> @@ -18,6 +18,7 @@ SUBDIR= alias \
> awk \
> banner \
> basename \
> + bc \
> ${_biff} \
> ${_bluetooth} \
> brandelf \
> @@ -49,6 +50,7 @@ SUBDIR= alias \
> ${_csup} \
> ${_ctags} \
> cut \
> + dc \
> ${_dig} \
> dirname \
> du \
> Added: head/usr.bin/bc/Makefile
> ==============================================================================
> --- /dev/null 00:00:00 1970 (empty, because file is newly added)
> +++ head/usr.bin/bc/Makefile Wed Jan 20 21:30:52 2010 (r202719)
> @@ -0,0 +1,17 @@
> +# $FreeBSD$
> +# $OpenBSD: Makefile,v 1.4 2006/06/30 19:02:28 otto Exp $
> +
> +PROG= bc
> +SRCS= bc.y scan.l
> +CFLAGS+= -I. -I${.CURDIR}
> +WARNS?= 6
> +#SUBDIR+= USD.doc
> +
> +FILES+= bc.library
> +FILESDIR= ${SHAREDIR}/misc
> +
> +#beforeinstall:
> +# install -c -o ${BINOWN} -g ${BINGRP} -m 444 ${.CURDIR}/bc.library \
> +# ${DESTDIR}/usr/share/misc
> +
> +.include<bsd.prog.mk>
> Added: head/usr.bin/bc/USD.doc/Makefile
> ==============================================================================
> --- /dev/null 00:00:00 1970 (empty, because file is newly added)
> +++ head/usr.bin/bc/USD.doc/Makefile Wed Jan 20 21:30:52 2010 (r202719)
> @@ -0,0 +1,13 @@
> +# $FreeBSD$
> +# $OpenBSD: Makefile,v 1.3 2004/02/01 15:18:01 jmc Exp $
> +
> +DOC= bc
> +DIR= usd/06.bc
> +SRCS= bc
> +MACROS= -ms
> +BINDIR= /usr/share/doc/papers
> +
> +paper.txt: ${SRCS}
> + ${ROFF} -Tascii ${SRCS}> ${.TARGET}
> +
> +.include<bsd.doc.mk>
> Added: head/usr.bin/bc/USD.doc/bc
> ==============================================================================
> --- /dev/null 00:00:00 1970 (empty, because file is newly added)
> +++ head/usr.bin/bc/USD.doc/bc Wed Jan 20 21:30:52 2010 (r202719)
> @@ -0,0 +1,1241 @@
> +.\" $FreeBSD$
> +.\" $OpenBSD: bc,v 1.9 2004/07/09 10:23:05 jmc Exp $
> +.\"
> +.\" Copyright (C) Caldera International Inc. 2001-2002.
> +.\" All rights reserved.
> +.\"
> +.\" Redistribution and use in source and binary forms, with or without
> +.\" modification, are permitted provided that the following conditions
> +.\" are met:
> +.\" 1. Redistributions of source code and documentation must retain the above
> +.\" copyright notice, this list of conditions and the following disclaimer.
> +.\" 2. Redistributions in binary form must reproduce the above copyright
> +.\" notice, this list of conditions and the following disclaimer in the
> +.\" documentation and/or other materials provided with the distribution.
> +.\" 3. All advertising materials mentioning features or use of this software
> +.\" must display the following acknowledgement:
> +.\" This product includes software developed or owned by Caldera
> +.\" International, Inc.
> +.\" 4. Neither the name of Caldera International, Inc. nor the names of other
> +.\" contributors may be used to endorse or promote products derived from
> +.\" this software without specific prior written permission.
> +.\"
> +.\" USE OF THE SOFTWARE PROVIDED FOR UNDER THIS LICENSE BY CALDERA
> +.\" INTERNATIONAL, INC. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
> +.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
> +.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
> +.\" IN NO EVENT SHALL CALDERA INTERNATIONAL, INC. BE LIABLE FOR ANY DIRECT,
> +.\" INDIRECT INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> +.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> +.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
> +.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
> +.\" IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
> +.\" POSSIBILITY OF SUCH DAMAGE.
> +.\"
> +.\" @(#)bc 6.2 (Berkeley) 4/17/91
> +.\"
> +.if n \{\
> +.po 5n
> +.ll 70n
> +.\}
> +.EH 'USD:6-%''BC \- An Arbitrary Precision Desk-Calculator Language'
> +.OH 'BC \- An Arbitrary Precision Desk-Calculator Language''USD:6-%'
> +.\".RP
> +.TL
> +BC \- An Arbitrary Precision Desk-Calculator Language
> +.AU
> +Lorinda Cherry
> +.AU
> +Robert Morris
> +.AI
> +.\" .MH
> +.AB
> +BC is a language and a compiler for doing arbitrary precision arithmetic
> +on the PDP-11 under the
> +.UX
> +time-sharing
> +system. The output of the compiler is interpreted and executed by
> +a collection of routines which can input, output, and do
> +arithmetic on indefinitely large integers and on scaled fixed-point
> +numbers.
> +.PP
> +These routines are themselves based on a dynamic storage allocator.
> +Overflow does not occur until all available core storage
> +is exhausted.
> +.PP
> +The language has a complete control structure as well as immediate-mode
> +operation. Functions can be defined and saved for later execution.
> +.PP
> +Two five hundred-digit numbers can be multiplied to give a
> +thousand digit result in about ten seconds.
> +.PP
> +A small collection of library functions is also available,
> +including sin, cos, arctan, log, exponential, and Bessel functions of
> +integer order.
> +.PP
> +Some of the uses of this compiler are
> +.IP \-
> +to do computation with large integers,
> +.IP \-
> +to do computation accurate to many decimal places,
> +.IP \-
> +conversion of numbers from one base to another base.
> +.AE
> +.PP
> +.SH
> +Introduction
> +.PP
> +BC is a language and a compiler for doing arbitrary precision
> +arithmetic on the
> +.UX
> +time-sharing system [1].
> +The compiler was written to make conveniently available a
> +collection of routines (called DC [5]) which are capable of doing
> +arithmetic on integers of arbitrary size. The compiler
> +is by no means intended to provide a complete programming
> +language.
> +It is a minimal language facility.
> +.PP
> +There is a scaling provision that permits the
> +use of decimal point notation.
> +Provision is made for input and output in bases other than
> +decimal. Numbers can be converted from decimal to octal by
> +simply setting the output base to equal 8.
> +.PP
> +The actual limit on the number of digits that can
> +be handled depends on the amount of storage available on the machine.
> +Manipulation of numbers with many hundreds of digits
> +is possible even on the smallest versions of
> +.UX .
> +.PP
> +The syntax of BC has been deliberately selected to agree
> +substantially with the C language [2]. Those who
> +are familiar with C will find few surprises in this language.
> +.SH
> +Simple Computations with Integers
> +.PP
> +The simplest kind of statement is an arithmetic expression
> +on a line by itself.
> +For instance, if you type in the line:
> +.DS
> +.ft B
> +142857 + 285714
> +.ft P
> +.DE
> +the program responds immediately with the line
> +.DS
> +.ft B
> +428571
> +.ft P
> +.DE
> +The operators \-, *, /, %, and ^ can also be used; they
> +indicate subtraction, multiplication, division, remaindering, and
> +exponentiation, respectively. Division of integers produces an
> +integer result truncated toward zero.
> +Division by zero produces an error
> +comment.
> +.PP
> +Any term in an expression may be prefixed by a minus sign to
> +indicate that it is to be negated (the `unary' minus sign).
> +The expression
> +.DS
> +.ft B
> +7+\-3
> +.ft P
> +.DE
> +is interpreted to mean that \-3 is to be added to 7.
> +.PP
> +More complex expressions with several operators and with
> +parentheses are interpreted just as in
> +Fortran, with ^ having the greatest binding
> +power, then * and % and /, and finally + and \-.
> +Contents of parentheses are evaluated before material
> +outside the parentheses.
> +Exponentiations are
> +performed from right to left and the other operators
> +from left to right.
> +The two expressions
> +.DS
> +.ft B
> +a^b^c and a^(b^c)
> +.ft P
> +.DE
> +are equivalent, as are the two expressions
> +.DS
> +.ft B
> +a*b*c and (a*b)*c
> +.ft P
> +.DE
> +BC shares with Fortran and C the undesirable convention that
> +.DS
> +\fBa/b*c\fP is equivalent to \fB(a/b)*c\fP
> +.ft P
> +.DE
> +.PP
> +Internal storage registers to hold numbers have single lower-case
> +letter names. The value of an expression can be assigned to
> +a register in the usual way. The statement
> +.DS
> +.ft B
> +x = x + 3
> +.ft P
> +.DE
> +has the effect of increasing by three the value of the contents of the
> +register named x.
> +When, as in this case, the outermost operator is an =, the
> +assignment is performed but the result is not printed.
> +Only 26 of these named storage registers are available.
> +.PP
> +There is a built-in square root function whose
> +result is truncated to an integer (but see scaling below).
> +The lines
> +.DS
> +.ft B
> +x = sqrt(191)
> +x
> +.ft P
> +.DE
> +produce the printed result
> +.DS
> +.ft B
> +13
> +.ft P
> +.DE
> +.SH
> +Bases
> +.PP
> +There are special internal quantities, called `ibase' and `obase'.
> +The contents of `ibase', initially set to 10,
> +determines the base used for interpreting numbers read in.
> +For example, the lines
> +.DS
> +.ft B
> +ibase = 8
> +11
> +.ft P
> +.DE
> +will produce the output line
> +.DS
> +.ft B
> +9
> +.ft P
> +.DE
> +and you are all set up to do octal to decimal conversions.
> +Beware, however of trying to change the input base back
> +to decimal by typing
> +.DS
> +.ft B
> +ibase = 10
> +.ft P
> +.DE
> +Because the number 10 is interpreted as octal, this statement will
> +have no effect.
> +For those who deal in hexadecimal notation,
> +the characters A\-F are permitted in numbers
> +(no matter what base is in effect)
> +and are
> +interpreted as digits having values 10\-15 respectively.
> +The statement
> +.DS
> +.ft B
> +ibase = A
> +.ft P
> +.DE
> +will change you back to decimal input base no matter what the
> +current input base is.
> +Negative and large positive input bases are
> +permitted but useless.
> +No mechanism has been provided for the input of arbitrary
> +numbers in bases less than 1 and greater than 16.
> +.PP
> +The contents of `obase', initially set to 10, are used as the base for output
> +numbers. The lines
> +.DS
> +.ft B
> +obase = 16
> +1000
> +.ft P
> +.DE
> +will produce the output line
> +.DS
> +.ft B
> +3E8
> +.ft P
> +.DE
> +which is to be interpreted as a 3-digit hexadecimal number.
> +Very large output bases are permitted, and they are sometimes useful.
> +For example, large numbers can be output in groups of five digits
> +by setting `obase' to 100000.
> +Strange (i.e. 1, 0, or negative) output bases are
> +handled appropriately.
> +.PP
> +Very large numbers are split across lines with 70 characters per line.
> +Lines which are continued end with \\.
> +Decimal output conversion is practically instantaneous, but output
> +of very large numbers (i.e., more than 100 digits) with other bases
> +is rather slow.
> +Non-decimal output conversion of
> +a one hundred digit number takes about
> +three seconds.
> +.PP
> +It is best to remember that `ibase' and `obase' have no effect
> +whatever on the course of internal computation or
> +on the evaluation of expressions, but only affect input and
> +output conversion, respectively.
> +.SH
> +Scaling
> +.PP
> +A third special internal quantity called `scale' is
> +used to determine the scale of calculated
> +quantities.
> +Numbers may have
> +up to a specific number of decimal digits after the decimal point.
> +This fractional part is retained in further computations.
> +We refer to the number of digits after the decimal point of
> +a number as its scale.
> +The current implementation allows scales to be as large as can be
> +represented by a 32-bit unsigned number minus one.
> +This is a non-portable extension.
> +The original implementation allowed for a maximum scale of 99.
> +.PP
> +When two scaled numbers are combined by
> +means of one of the arithmetic operations, the result
> +has a scale determined by the following rules. For
> +addition and subtraction, the scale of the result is the larger
> +of the scales of the two operands. In this case,
> +there is never any truncation of the result.
> +For multiplications, the scale of the result is never
> +less than the maximum of the two scales of the operands,
> +never more than the sum of the scales of the operands
> +and, subject to those two restrictions,
> +the scale of the result is set equal to the contents of the internal
> +quantity `scale'.
> +The scale of a quotient is the contents of the internal
> +quantity `scale'. The scale of a remainder is
> +the sum of the scales of the quotient and the divisor.
> +The result of an exponentiation is scaled as if
> +the implied multiplications were performed.
> +An exponent must be an integer.
> +The scale of a square root is set to the maximum of the scale
> +of the argument and the contents of `scale'.
> +.PP
> +All of the internal operations are actually carried out in terms
> +of integers, with digits being discarded when necessary.
> +In every case where digits are discarded, truncation and
> +not rounding is performed.
> +.PP
> +The contents of
> +`scale' must be no greater than
> +4294967294 and no less than 0. It is initially set to 0.
> +.PP
> +The internal quantities `scale', `ibase', and `obase' can be
> +used in expressions just like other variables.
> +The line
> +.DS
> +.ft B
> +scale = scale + 1
> +.ft P
> +.DE
> +increases the value of `scale' by one, and the line
> +.DS
> +.ft B
> +scale
> +.ft P
> +.DE
> +causes the current value of `scale' to be printed.
> +.PP
> +The value of `scale' retains its meaning as a
> +number of decimal digits to be retained in internal
> +computation even when `ibase' or `obase' are not equal to 10.
> +The internal computations (which are still conducted in decimal,
> +regardless of the bases) are performed to the specified number
> +of decimal digits, never hexadecimal or octal or any
> +other kind of digits.
> +.SH
> +Functions
> +.PP
> +The name of a function is a single lower-case letter.
> +Function names are permitted to collide with simple
> +variable names.
> +Twenty-six different defined functions are permitted
> +in addition to the twenty-six variable names.
> +The line
> +.DS
> +.ft B
> + define a(x){
> +.ft P
> +.DE
> +begins the definition of a function with one argument.
> +This line must be followed by one or more statements,
> +which make up the body of the function, ending
> +with a right brace }.
> +Return of control from a function occurs when a return
> +statement is executed or when the end of the function is reached.
> +The return statement can take either
> +of the two forms
> +.DS
> +.ft B
> +return
> +return(x)
> +.ft P
> +.DE
> +In the first case, the value of the function is 0, and in
> +the second, the value of the expression in parentheses.
> +.PP
> +Variables used in the function can be declared as automatic
> +by a statement of the form
> +.DS
> +.ft B
> +auto x,y,z
> +.ft P
> +.DE
> +There can be only one `auto' statement in a function and it must
> +be the first statement in the definition.
> +These automatic variables are allocated space and initialized
> +to zero on entry to the function and thrown away on return. The
> +values of any variables with the same names outside the function
> +are not disturbed.
> +Functions may be called recursively and the automatic variables
> +at each level of call are protected.
> +The parameters named in a function definition are treated in
> +the same way as the automatic variables of that function
> +with the single exception that they are given a value
> +on entry to the function.
> +An example of a function definition is
> +.DS
> +.ft B
> + define a(x,y){
> + auto z
> + z = x*y
> + return(z)
> + }
> +.ft P
> +.DE
> +The value of this function, when called, will be the
> +product of its
> +two arguments.
> +.PP
> +A function is called by the appearance of its name
> +followed by a string of arguments enclosed in
> +parentheses and separated by commas.
> +The result
> +is unpredictable if the wrong number of arguments is used.
> +.PP
> +Functions with no arguments are defined and called using
> +parentheses with nothing between them: b().
> +.PP
> +If the function
> +.ft I
> +a
> +.ft
> +above has been defined, then the line
> +.DS
> +.ft B
> +a(7,3.14)
> +.ft P
> +.DE
> +would cause the result 21.98 to be printed and the line
> +.DS
> +.ft B
> +x = a(a(3,4),5)
> +.ft P
> +.DE
> +would cause the value of x to become 60.
> +.SH
> +Subscripted Variables
> +.PP
> +A single lower-case letter variable name
> +followed by an expression in brackets is called a subscripted
> +variable (an array element).
> +The variable name is called the array name and the expression
> +in brackets is called the subscript.
> +Only one-dimensional arrays are
> +permitted. The names of arrays are permitted to
> +collide with the names of simple variables and function names.
> +Any fractional
> +part of a subscript is discarded before use.
> +Subscripts must be greater than or equal to zero and
> +less than or equal to 2047.
> +.PP
> +Subscripted variables may be freely used in expressions, in
> +function calls, and in return statements.
> +.PP
> +An array name may be used as an argument to a function,
> +or may be declared as automatic in
> +a function definition by the use of empty brackets:
> +.DS
> +.ft B
> +f(a[\|])
> +define f(a[\|])
> +auto a[\|]
> +.ft P
> +.DE
> +When an array name is so used, the whole contents of the array
> +are copied for the use of the function, and thrown away on exit
> +from the function.
> +Array names which refer to whole arrays cannot be used
> +in any other contexts.
> +.SH
> +Control Statements
> +.PP
> +The `if', the `while', and the `for' statements
> +may be used to alter the flow within programs or to cause iteration.
> +The range of each of them is a statement or
> +a compound statement consisting of a collection of
> +statements enclosed in braces.
> +They are written in the following way
> +.DS
> +.ft B
> +if(relation) statement
> +if(relation) statement else statement
> +while(relation) statement
> +for(expression1; relation; expression2) statement
> +.ft P
> +.DE
> +or
> +.DS
> +.ft B
> +if(relation) {statements}
> +if(relation) {statements} else {statements}
> +while(relation) {statements}
> +for(expression1; relation; expression2) {statements}
> +.ft P
> +.DE
> +.PP
> +A relation in one of the control statements is an expression of the form
> +.DS
> +.ft B
+x>>y
> +.ft P
> +.DE
> +where two expressions are related by one of the six relational
> +operators `<', `>', `<=', `>=', `==', or `!='.
> +The relation `=='
> +stands for `equal to' and `!=' stands for `not equal to'.
> +The meaning of the remaining relational operators is
> +clear.
> +.PP
> +BEWARE of using `=' instead of `==' in a relational. Unfortunately,
> +both of them are legal, so you will not get a diagnostic
> +message, but `=' really will not do a comparison.
> +.PP
> +The `if' statement causes execution of its range
> +if and only if the relation is true.
> +Then control passes to the next statement in sequence.
> +If an `else' branch is present, the statements in this branch are
> +executed if the relation is false.
> +The `else' keyword is a non-portable extension.
> +.PP
> +The `while' statement causes execution of its range
> +repeatedly as long as the relation
> +is true. The relation is tested before each execution
> +of its range and if the relation
> +is false, control passes to the next statement beyond the range
> +of the while.
> +.PP
> +The `for' statement begins
> +by executing `expression1'. Then the relation is tested
> +and, if true, the statements in the range of the `for' are executed.
> +Then `expression2' is executed. The relation is tested, and so on.
> +The typical use of the `for' statement is for a controlled iteration,
> +as in the statement
> +.DS
> +.ft B
> +for(i=1; i<=10; i=i+1) i
> +.ft P
> +.DE
> +which will print the integers from 1 to 10.
> +Here are some examples of the use of the control statements.
> +.DS
> +.ft B
> +define f(n){
> +auto i, x
> +x=1
> +for(i=1; i<=n; i=i+1) x=x*i
> +return(x)
> +}
> +.ft P
> +.DE
> +The line
> +.DS
> +.ft B
> + f(a)
> +.ft P
> +.DE
> +will print
> +.ft I
> +a
> +.ft
> +factorial if
> +.ft I
> +a
> +.ft
> +is a positive integer.
> +Here is the definition of a function which will
> +compute values of the binomial coefficient
> +(m and n are assumed to be positive integers).
> +.DS
> +.ft B
> +define b(n,m){
> +auto x, j
> +x=1
> +for(j=1; j<=m; j=j+1) x=x*(n\-j+1)/j
> +return(x)
> +}
> +.ft P
> +.DE
> +The following function computes values of the exponential function
> +by summing the appropriate series
> +without regard for possible truncation errors:
> +.DS
> +.ft B
> +scale = 20
> +define e(x){
> + auto a, b, c, d, n
> + a = 1
> + b = 1
> + c = 1
> + d = 0
> + n = 1
> + while(1==1){
> + a = a*x
> + b = b*n
> + c = c + a/b
> + n = n + 1
> + if(c==d) return(c)
> + d = c
> + }
> +}
> +.ft P
> +.DE
> +.SH
> +Some Details
> +.PP
> +There are some language features that every user should know
> +about even if he will not use them.
> +.PP
> +Normally statements are typed one to a line. It is also permissible
> +to type several statements on a line separated by semicolons.
> +.PP
> +If an assignment statement is parenthesized, it then has
> +a value and it can be used anywhere that an expression can.
> +For example, the line
> +.DS
> +.ft B
> +(x=y+17)
> +.ft P
> +.DE
> +not only makes the indicated assignment, but also prints the
> +resulting value.
> +.PP
> +Here is an example of a use of the value of an
> +assignment statement even when it is not parenthesized.
> +.DS
> +.ft B
> +x = a[i=i+1]
> +.ft P
> +.DE
> +causes a value to be assigned to x and also increments i
> +before it is used as a subscript.
> +.PP
> +The following constructs work in BC in exactly the same manner
> +as they do in the C language. Consult the appendix or the
> +C manuals [2] for their exact workings.
> +.DS
> +.ft B
> +.ta 2i
> +x=y=z is the same as x=(y=z)
> +x += y x = x+y
> +x \-= y x = x\-y
> +x *= y x = x*y
> +x /= y x = x/y
> +x %= y x = x%y
> +x ^= y x = x^y
> +x++ (x=x+1)\-1
> +x\-\- (x=x\-1)+1
> +++x x = x+1
> +\-\-x x = x\-1
> +.ft P
> +.DE
> +Even if you don't intend to use the constructs,
> +if you type one inadvertently, something correct but unexpected
> +may happen.
> +.SH
> +Three Important Things
> +.PP
> +1. To exit a BC program, type `quit'.
> +.PP
> +2. There is a comment convention identical to that of C and
> +of PL/I. Comments begin with `/*' and end with `*/'.
> +As a non-portable extension, comments may also start with a `#' and end with
> +a newline.
> +The newline is not part of the comment.
> +.PP
> +3. There is a library of math functions which may be obtained by
> +typing at command level
> +.DS
> +.ft B
> +bc \-l
> +.ft P
> +.DE
> +This command will load a set of library functions
> +which, at the time of writing, consists of sine (named `s'),
> +cosine (`c'), arctangent (`a'), natural logarithm (`l'),
> +exponential (`e') and Bessel functions of integer order
> (`j(n,x)'). Doubtless more functions will be added
> +in time.
> +The library sets the scale to 20. You can reset it to something
> +else if you like.
> +The design of these mathematical library routines
> +is discussed elsewhere [3].
> +.PP
> +If you type
> +.DS
> +.ft B
> +bc file ...
> +.ft P
> +.DE
> +BC will read and execute the named file or files before accepting
> +commands from the keyboard. In this way, you may load your
> +favorite programs and function definitions.
> +.SH
> +Acknowledgement
> +.PP
> +The compiler is written in YACC [4]; its original
> +version was written by S. C. Johnson.
> +.SH
> +References
> +.IP [1]
> +K. Thompson and D. M. Ritchie,
> +.ft I
> +UNIX Programmer's Manual,
> +.ft
> +Bell Laboratories,
> +1978.
> +.IP [2]
> +B. W. Kernighan and
> +D. M. Ritchie,
> +.ft I
> +The C Programming Language,
> +.ft
> +Prentice-Hall, 1978.
> +.IP [3]
> +R. Morris,
> +.ft I
> +A Library of Reference Standard Mathematical Subroutines,
> +.ft
> +Bell Laboratories internal memorandum, 1975.
> +.IP [4]
> +S. C. Johnson,
> +.ft I
> +YACC \(em Yet Another Compiler-Compiler.
> +.ft
> +Bell Laboratories Computing Science Technical Report #32, 1978.
> +.IP [5]
> +R. Morris and L. L. Cherry,
> +.ft I
> +DC \- An Interactive Desk Calculator.
> +.ft
> +.LP
> +.bp
> +.ft B
> +.DS C
> +Appendix
> +.DE
> +.ft
> +.NH
> +Notation
> +.PP
> +In the following pages syntactic categories are in \fIitalics\fP;
> +literals are in \fBbold\fP; material in brackets [\|] is optional.
> +.NH
> +Tokens
> +.PP
> +Tokens consist of keywords, identifiers, constants, operators,
> +and separators.
> +Token separators may be blanks, tabs or comments.
> +Newline characters or semicolons separate statements.
> +.NH 2
> +Comments
> +.PP
> +Comments are introduced by the characters /* and terminated by
> +*/.
> +As a non-portable extension, comments may also start with a # and
> +end with a newline.
> +The newline is not part of the comment.
> +.NH 2
> +Identifiers
> +.PP
> +There are three kinds of identifiers \- ordinary identifiers, array identifiers
> +and function identifiers.
> +All three types consist of single lower-case letters.
> +Array identifiers are followed by square brackets, possibly
> +enclosing an expression describing a subscript.
> +Arrays are singly dimensioned and may contain up to 2048
> +elements.
> +Indexing begins at zero so an array may be indexed from 0 to 2047.
> +Subscripts are truncated to integers.
> +Function identifiers are followed by parentheses, possibly enclosing arguments.
> +The three types of identifiers do not conflict;
> +a program can have a variable named \fBx\fP,
> +an array named \fBx\fP and a function named \fBx\fP, all of which are separate and
> +distinct.
> +.NH 2
> +Keywords
> +.PP
> +The following are reserved keywords:
> +.ft B
> +.ta .5i 1.0i
> +.nf
> + ibase if
> + obase break
> + scale define
> + sqrt auto
> + length return
> + while quit
> + for continue
> + else last
> + print
> +.fi
> +.ft
> +.NH 2
> +Constants
> +.PP
> +Constants consist of arbitrarily long numbers
> +with an optional decimal point.
> +The hexadecimal digits \fBA\fP\-\fBF\fP are also recognized as digits with
> +values 10\-15, respectively.
> +.NH 1
> +Expressions
> +.PP
> +The value of an expression is printed unless the main
> +operator is an assignment.
> +The value printed is assigned to the special variable \fBlast\fP.
> +A single dot may be used as a synonym for \fBlast\fP.
> +This is a non-portable extension.
> +Precedence is the same as the order
> +of presentation here, with highest appearing first.
> +Left or right associativity, where applicable, is
> +discussed with each operator.
> +.bp
> +.NH 2
> +Primitive expressions
> +.NH 3
> +Named expressions
> +.PP
> +Named expressions are
> +places where values are stored.
> +Simply stated,
> +named expressions are legal on the left
> +side of an assignment.
> +The value of a named expression is the value stored in the place named.
> +.NH 4
> +\fIidentifiers\fR
> +.PP
> +Simple identifiers are named expressions.
> +They have an initial value of zero.
> +.NH 4
> +\fIarray-name\fP\|[\|\fIexpression\fP\|]
> +.PP
> +Array elements are named expressions.
> +They have an initial value of zero.
> +.NH 4
> +\fBscale\fR, \fBibase\fR and \fBobase\fR
> +.PP
> +The internal registers
> +\fBscale\fP, \fBibase\fP and \fBobase\fP are all named expressions.
> +\fBscale\fP is the number of digits after the decimal point to be
> +retained in arithmetic operations.
> +\fBscale\fR has an initial value of zero.
> +\fBibase\fP and \fBobase\fP are the input and output number
> +radix respectively.
> +Both \fBibase\fR and \fBobase\fR have initial values of 10.
> +.NH 3
> +Function calls
> +.NH 4
> +\fIfunction-name\fB\|(\fR[\fIexpression\fR\|[\fB,\|\fIexpression\|\fR.\|.\|.\|]\|]\fB)
> +.PP
> +A function call consists of a function name followed by parentheses
> +containing a comma-separated list of
> +expressions, which are the function arguments.
> +A whole array passed as an argument is specified by the
> +array name followed by empty square brackets.
> +All function arguments are passed by
> +value.
> +As a result, changes made to the formal parameters have
> +no effect on the actual arguments.
> +If the function terminates by executing a return
> +statement, the value of the function is
> +the value of the expression in the parentheses of the return
> +statement or is zero if no expression is provided
> +or if there is no return statement.
> +.NH 4
> +sqrt\|(\|\fIexpression\fP\|)
> +.PP
> +The result is the square root of the expression.
> +The result is truncated in the least significant decimal place.
> +The scale of the result is
> +the scale of the expression or the
> +value of
> +.ft B
> +scale,
> +.ft
> +whichever is larger.
> +.NH 4
> +length\|(\|\fIexpression\fP\|)
> +.PP
> +The result is the total number of significant decimal digits in the expression.
> +The scale of the result is zero.
> +.NH 4
> +scale\|(\|\fIexpression\fP\|)
> +.PP
> +The result is the scale of the expression.
> +The scale of the result is zero.
> +.NH 3
> +Constants
> +.PP
> +Constants are primitive expressions.
> +.NH 3
> +Parentheses
> +.PP
> +An expression surrounded by parentheses is
> +a primitive expression.
> +The parentheses are used to alter the
> +normal precedence.
> +.NH 2
> +Unary operators
> +.PP
> +The unary operators
> +bind right to left.
> +.NH 3
> +\-\|\fIexpression\fP
> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
> _______________________________________________
> svn-src-all at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/svn-src-all
> To unsubscribe, send any mail to "svn-src-all-unsubscribe at freebsd.org"
> ------------------------------
> Message: 16
> Date: Thu, 21 Jan 2010 09:50:14 +1030
> From: Matt Thyer <matt.thyer at gmail.com>
> Subject: Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system
> To: Dan Nelson <dnelson at allantgroup.com>
> Cc: current at freebsd.org
> Message-ID:
> <fa58e4891001201520i32122f7eob37b410c79db21e8 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 2010/1/21 Dan Nelson <dnelson at allantgroup.com>
>> In the last episode (Jan 21), Matt Thyer said:
>> > I typically buildworld with a parallel make of hw.ncpu * 3 which results
>> > in -j24 on my new system (Intel Core i7-860, 8GB RAM).
>>
> [snip]
>> > Build failure is:
>> >
>> > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 asn1_err.h
>> >
>> /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/heim_asn1.h
>> > cms_asn1.h rfc2459_asn1.h krb5_asn1.h pkinit_asn1.h pkcs8_asn1.h
>> > pkcs9_asn1.h pkcs12_asn1.h digest_asn1.h kx509_asn1.h
>> > /usr/obj/usr/src/tmp/usr/include
>> > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libasn1.so.10
>> > /usr/obj/usr/src/tmp/usr/lib
>> > ln -fs libasn1.so.10 /usr/obj/usr/src/tmp/usr/lib/libasn1.so
>> > 1 error
>> > *** Error code 2
>> > 1 error
>> > *** Error code 2
>> > 1 error
>> > *** Error code 2
>> > 1 error
>>
>> It's much more likely to be a Makefile dependency problem than a ZFS bug.
>> You will need to look much farther up in your log to see the real error
>> message. Make will wait for the other 23 jobs to finish before returning,
>> so what you posted was the output of one of the other jobs, plus the output
>> of each parent make as it exits with an error code.
>>
> This was my first thought so I grepped my log for "error" in a case
> insensitive way and found nothing.
> That's why I think that it may be a file system issue as the line prior to
> the link is the installation of the "libasn1.so.10" shared library. I have
> now installed the same JPSNAP on another identical hard disk (300GB Seagate
> SATA) in a UFS only system and will test again shortly.
>> --
>> Dan Nelson
>> dnelson at allantgroup.com
>>
> ------------------------------
> Message: 17
> Date: Wed, 20 Jan 2010 17:50:24 -0600
> From: Dan Nelson <dnelson at allantgroup.com>
> Subject: Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system
> To: Matt Thyer <matt.thyer at gmail.com>
> Cc: current at freebsd.org
> Message-ID: <20100120235024.GE50360 at dan.emsphone.com>
> Content-Type: text/plain; charset=us-ascii
> In the last episode (Jan 21), Matt Thyer said:
>> 2010/1/21 Dan Nelson <dnelson at allantgroup.com>
>> > In the last episode (Jan 21), Matt Thyer said:
>> > > I typically buildworld with a parallel make of hw.ncpu * 3 which
>> > > results in -j24 on my new system (Intel Core i7-860, 8GB RAM).
> [...]
>> > > Build failure is:
>> > >
>> > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 asn1_err.h
>> > > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/heim_asn1.h
>> > > cms_asn1.h rfc2459_asn1.h krb5_asn1.h pkinit_asn1.h pkcs8_asn1.h
>> > > pkcs9_asn1.h pkcs12_asn1.h digest_asn1.h kx509_asn1.h
>> > > /usr/obj/usr/src/tmp/usr/include
>> > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libasn1.so.10
>> > > /usr/obj/usr/src/tmp/usr/lib
>> > > ln -fs libasn1.so.10 /usr/obj/usr/src/tmp/usr/lib/libasn1.so
>> > > 1 error
>> > > *** Error code 2
>> > > 1 error
>> > > *** Error code 2
>> > > 1 error
>> > > *** Error code 2
>> > > 1 error
>> >
>> > It's much more likely to be a Makefile dependency problem than a ZFS
>> > bug. You will need to look much farther up in your log to see the real
>> > error message. Make will wait for the other 23 jobs to finish before
>> > returning, so what you posted was the output of one of the other jobs,
>> > plus the output of each parent make as it exits with an error code.
>>
>> This was my first thought so I grepped my log for "error" in a case
>> insensitive way and found nothing. That's why I think that it may be a
>> file system issue as the line prior to the link is the installation of the
>> "libasn1.so.10" shared library. I have now installed the same JPSNAP on
>> another identical hard disk (300GB Seagate SATA) in a UFS only system and
>> will test again shortly.
> Since the ln command didn't print an error message itself, it's unlikely to
> have caused the build to fail. Try searching for "***" or ":" instead.
> You can try adding -v or -P to your initial make commandline; either will
> add extra lines to parallel builds that make it easier to tell exactly what
> make target caused a failure. I don't know if they will cause issues with
> the buildworld framework, though. Try running "make -j2", "make -v -j2",
> and "make -P -j2" on the following Makefile to see what the flags do:
> ( indented lines have leading tabs )
> test: test1 test2
> test1:
> @sleep 1
> @false
> test2:
> @echo "hi I'm a successful target"
>
> --
> Dan Nelson
> dnelson at allantgroup.com
> ------------------------------
> Message: 18
> Date: Thu, 21 Jan 2010 08:51:12 +0800
> From: "Wilkinson, Alex" <alex.wilkinson at dsto.defence.gov.au>
> Subject: Re: multimedia/libv4l/ (video4bsd.ko) -> Fatal trap 12: page
> fault while in kernel mode [SEC=UNCLASSIFIED]
> To: freebsd-current at freebsd.org, freebsd-usb at freebsd.org
> Message-ID: <20100121005111.GB48329 at stlux503.dsto.defence.gov.au>
> Content-Type: text/plain; charset="us-ascii"
> 0n Wed, Jan 20, 2010 at 10:13:07AM +0100, Hans Petter Selasky wrote:
> >On Wednesday 20 January 2010 09:37:26 Wilkinson, Alex wrote:
> >> The following ports initially installed and worked fine:
> >>
> >> multimedia/libv4l
> >> multimedia/webcamd
> >> multimedia/pwcview
> >>
> >> however, after a reboot video4bsd.ko panic'd my machine and i was unable to
> >> boot. I had to use the LiveFS to rescue the box. Here is the bt from DDB:
> >
> >This issue is fixed. Just update the ports.
> Ah, yep. Updating multimedia/video4bsd-kmod/ fixed this issue. Thanks!
> -Alex
> IMPORTANT: This email remains the property of the Australian
> Defence Organisation and is subject to the jurisdiction of section
> 70 of the CRIMES ACT 1914. If you have received this email in
> error, you are requested to contact the sender and delete the email.
> ------------------------------
> Message: 19
> Date: Thu, 21 Jan 2010 01:42:16 +0100
> From: Pav Lucistnik <pav at FreeBSD.org>
> Subject: cvsup crashing
> To: current at FreeBSD.org
> Message-ID: <1264034536.1541.113.camel at hood.oook.cz>
> Content-Type: text/plain; charset="iso-8859-2"
> We updated -CURRENT on pointyhat to r202579M: Tue Jan 19 08:43:56 UTC
> 2010 and now cvsup is catching SIGILL on every run updating ports
> checkout, in gmtime_r(). Any insights?
> --
> Pav Lucistnik <pav at oook.cz>
> <pav at FreeBSD.org>
> Angband in action! Constant escalation to new depths to find angrier,
> meaner letters and more punctuation!
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 196 bytes
> Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
> =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?=
> =?ISO-8859-1?Q?_zpr=E1vy?=
> Url :
> http://lists.freebsd.org/pipermail/freebsd-current/attachments/20100121/cc88b46d/attachment-0001.pgp
> ------------------------------
> Message: 20
> Date: Thu, 21 Jan 2010 11:48:58 +1030
> From: Matt Thyer <matt.thyer at gmail.com>
> Subject: Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system
> To: Dan Nelson <dnelson at allantgroup.com>
> Cc: current at freebsd.org
> Message-ID:
> <fa58e4891001201718q4928617ve5959eb15e51472d at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 2010/1/21 Dan Nelson <dnelson at allantgroup.com>
>> In the last episode (Jan 21), Matt Thyer said:
>> > 2010/1/21 Dan Nelson <dnelson at allantgroup.com>
>> > > In the last episode (Jan 21), Matt Thyer said:
>> > > > I typically buildworld with a parallel make of hw.ncpu * 3 which
>> > > > results in -j24 on my new system (Intel Core i7-860, 8GB RAM).
>> [...]
>> > > > Build failure is:
>> > > >
>> > > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 asn1_err.h
>> > > >
>> /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/heim_asn1.h
>> > > > cms_asn1.h rfc2459_asn1.h krb5_asn1.h pkinit_asn1.h pkcs8_asn1.h
>> > > > pkcs9_asn1.h pkcs12_asn1.h digest_asn1.h kx509_asn1.h
>> > > > /usr/obj/usr/src/tmp/usr/include
>> > > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444
>> libasn1.so.10
>> > > > /usr/obj/usr/src/tmp/usr/lib
>> > > > ln -fs libasn1.so.10 /usr/obj/usr/src/tmp/usr/lib/libasn1.so
>> > > > 1 error
>> > > > *** Error code 2
>> > > > 1 error
>> > > > *** Error code 2
>> > > > 1 error
>> > > > *** Error code 2
>> > > > 1 error
>> > >
>> > > It's much more likely to be a Makefile dependency problem than a ZFS
>> > > bug. You will need to look much farther up in your log to see the real
>> > > error message. Make will wait for the other 23 jobs to finish before
>> > > returning, so what you posted was the output of one of the other jobs,
>> > > plus the output of each parent make as it exits with an error code.
>> >
>> > This was my first thought so I grepped my log for "error" in a case
>> > insensitive way and found nothing. That's why I think that it may be a
>> > file system issue as the line prior to the link is the installation of
>> the
>> > "libasn1.so.10" shared library. I have now installed the same JPSNAP on
>> > another identical hard disk (300GB Seagate SATA) in a UFS only system and
>> > will test again shortly.
>>
>> Since the ln command didn't print an error message itself, it's unlikely to
>> have caused the build to fail. Try searching for "***" or ":" instead.
> [...]
> You are correct. I missed the error the first time. It is:
> make: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libmd.a. Stop
> *** Error code 2
> ------------------------------
> Message: 21
> Date: Wed, 20 Jan 2010 19:29:45 -0600 (CST)
> From: "Sean C. Farley" <scf at FreeBSD.org>
> Subject: Re: cvsup crashing
> To: Pav Lucistnik <pav at FreeBSD.org>
> Cc: current at FreeBSD.org
> Message-ID: <alpine.BSF.2.00.1001201928570.12771 at thor.farley.org>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
> On Thu, 21 Jan 2010, Pav Lucistnik wrote:
>> We updated -CURRENT on pointyhat to r202579M: Tue Jan 19 08:43:56 UTC
>> 2010 and now cvsup is catching SIGILL on every run updating ports
>> checkout, in gmtime_r(). Any insights?
> Is it anything similar to this thread[1]?
> Sean
> 1.
> http://lists.freebsd.org/pipermail/freebsd-current/2009-December/013946.html
> --
> scf at FreeBSD.org
> ------------------------------
> Message: 22
> Date: Wed, 20 Jan 2010 20:26:44 -0500 (EST)
> From: Daniel Eischen <deischen at freebsd.org>
> Subject: Re: Buildworld failure with -j24 and ZFS on GPT on Core
> i7-860 system
> To: Matt Thyer <matt.thyer at gmail.com>
> Cc: Dan Nelson <dnelson at allantgroup.com>, current at freebsd.org
> Message-ID: <Pine.GSO.4.64.1001202026010.25041 at sea.ntplx.net>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
> On Thu, 21 Jan 2010, Matt Thyer wrote:
>> 2010/1/21 Dan Nelson <dnelson at allantgroup.com>
>>
>>>
>>> Since the ln command didn't print an error message itself, it's unlikely to
>>> have caused the build to fail. Try searching for "***" or ":" instead.
>>
>>
>> [...]
>>
>> You are correct. I missed the error the first time. It is:
>>
>> make: don't know how to make /usr/obj/usr/src/tmp/usr/lib/libmd.a. Stop
>> *** Error code 2
> It happens with -j8 also (amd64, UFS).
--
Ñ óâàæåíèåì,
Ps81 mailto:ps81 at mail.ru
More information about the freebsd-current
mailing list