Re: SVN r325728 breaks build
On Sat, Nov 11, 2017 at 07:15:35PM -0500, Michael Butler wrote:
> As follows:
>
> --- zfs.o ---
> In file included from /usr/src/lib/libprocstat/zfs.c:51:
> In file included from /usr/obj/usr/src/amd64.amd64/tmp/usr/include/kvm.h:39:
> /usr/obj/usr/src/amd64.amd64/tmp/usr/include/vm/vm.h:111:13: error:
> typedef redefinition with different types ('int' vs 'enum boolean_t')
> typedef int boolean_t;
> ^
> /usr/src/sys/cddl/compat/opensolaris/sys/types.h:84:34: note: previous
> definition is here
> typedef enum { B_FALSE, B_TRUE }boolean_t;
> ^
> imb
I have a patch being tested, will fix shortly. Thanks.
--
wca
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
geom_part: support < 128 GPT partition entries
Hi, I'd appreciate a review for: https://reviews.freebsd.org/D6900 Summary: This change is useful primarily for using GPT on embedded boards like the pine64 (and others using an Allwinner SoC) that want a firmware image loaded below sector 34 (8K in that instance). Note that because this changes g_part_scheme, it breaks the ABI. Thanks! -- wca signature.asc Description: PGP signature
Re: mergemaster failing with read-only /usr/src
On Sun, May 3, 2015 at 1:11 PM, Garrett Cooper yaneurab...@gmail.com wrote: Well, I do build on that machine directly, and /usr/obj is mounted r/w, only /usr/src is a read-only mount. Trying the workaround on the machine istself does not help, unfortunately: while the make buildenv does work without a problem, mergemaster still fails in the same way. I was going to move it to etc/tests soon since it wasn’t really testing /etc/rc.d/, but it makes more sense (with the issue above), just to create .../tests/etc, and move things there. I wish etc/ wasn’t such a special butterfly... I'm not sure which is the better approach. I guess you could argue that etc/rc.d tests like this are technically kernel tests (and only incidentally test the relevant rc.d script), and therefore belong in tests/etc, the same way the kernel tests are in tests/sys. --Will. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CURRENT] r277641 fails to installworld: routing_test: No such file or directory
On Sat, Jan 24, 2015 at 01:54:43PM +0100, Matthias Apitz wrote: El día Saturday, January 24, 2015 a las 01:49:58PM +0100, O. Hartmann escribió: Most recent sources fail to install with the error below. CURRENT is amd64 and at r277641: === etc/tests/rc.d (install) install -o root -g wheel -m 555 routing_test /usr/tests/etc/rc.d/routing_test install: /usr/tests/etc/rc.d/routing_test: No such file or directory *** Error code 71 I'm facing right now (13:52 CET) the same with creating the jail for poudriere with poudriere jail -c -j freebsd-head -m svn+http -v head after 2 hours all is rolled back :-( not even the checked out tree is left :-( This is fixed in r277650. My apologies. -- wca pgpVBLgNsUfIx.pgp Description: PGP signature
Re: Head not buildin in zfs.c
On Wed, Jan 21, 2015 at 02:47:57AM -0800, Garrett Cooper wrote: On Jan 21, 2015, at 2:17, Willem Jan Withagen w...@digiware.nl wrote: … Right, picky nasty compilers being fussy. ;) I did in look in the svn log of both .h files, but overlooked what you just found. Need more coffee. I'll be waiting the the fix in the tree.. Fixed in r277484 — thanks! Thanks! Sorry for the noise. --Will. pgpdmFn4VHM6f.pgp Description: PGP signature
Re: Revision 248649 - causes panic during boot
A stack trace would be helpful. Thanks, --Will. On Tue, Mar 26, 2013 at 4:27 PM, AN a...@neu.net wrote: Hello: I have identified svn Revision 248649 as causing my system to panic during boot up. http://svnweb.freebsd.org/**base?view=revisionrevision=**248649http://svnweb.freebsd.org/base?view=revisionrevision=248649 I have verified this by doing the following: svn up -r 248648 - buildkernel, installkernel, reboot = boot successful svn up -r 248649 - buildkernel, installkernel, reboot = causes panic The panic happens just after the line that says: Entropy harvesting interrupts: Ethernet point to point, then Fatal Trap 9 General Protection Fault, and then an automatic reboot. Here is some system info: FreeBSD 10.0-CURRENT #49 r248648: Tue Mar 26 14:55:28 CDT 2013 root@FBSD10:/usr/obj/usr/src/**sys/MYKERNEL amd64 FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 CPU: AMD Phenom(tm) II X6 1045T Processor (2700.05-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x100fa0 Family = 0x10 Model = 0xa Stepping = 0 Features=0x178bfbffFPU,VME,**DE,PSE,TSC,MSR,PAE,MCE,CX8,** APIC,SEP,MTRR,PGE,MCA,CMOV,**PAT,PSE36,CLFLUSH,MMX,FXSR,**SSE,SSE2,HTT Features2=0x802009SSE3,MON,**CX16,POPCNT AMD Features=0xee500800SYSCALL,**NX,MMX+,FFXSR,Page1GB,RDTSCP,** LM,3DNow!+,3DNow! AMD Features2=0x37ffLAHF,CMP,SVM,**ExtAPIC,CR8,ABM,SSE4A,MAS,** Prefetch,OSVW,IBS,SKINIT,WDT TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 15951269888 (15212 MB) Event timer LAPIC quality 400 ACPI APIC Table: HPQOEM SLIC-CPC FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs FreeBSD/SMP: 1 package(s) x 6 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x/0x1 (20130214/tbfadt-626) ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 ctl: CAM Target Layer loaded acpi0: HPQOEM SLIC-CPC on motherboard acpi0: Power Button (fixed) acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fec1, 20 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, c7f0 (3) failed cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 cpu4: ACPI CPU on acpi0 cpu5: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 450 Event timer HPET1 frequency 14318180 Hz quality 450 Event timer HPET2 frequency 14318180 Hz quality 450 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 The following is the last commit that works: # cd /usr/src # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/**head http://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-**001c23d0bc1f Revision: 248648 Node Kind: directory Schedule: normal Last Changed Author: des Last Changed Rev: 248648 Last Changed Date: 2013-03-23 09:52:31 -0500 (Sat, 23 Mar 2013) Would you please review the commit for anything that may cause a panic during boot up. Let me know if there is any more info that I should provide. Should I file a PR? Thank you in advance for reviewing this. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Exactly that commit (was Re: Latest -current 100% hang at the late boot stage)
Hi Andrey, On Mon, Jun 20, 2011 at 5:46 AM, Andrey Chernov a...@freebsd.org wrote: As the second message in the thread states, I try first even 223296 with the same hang and the same xpt_action_default: CCB type 0xe not supported As I think, DDB's 'ps' indicates that kernel waits something from geom and geom waits something from ccb_scan forever, just raw guess. I will be glad to issue more specific DDB commands and upload corresponding photos. BTW, pluging and unplugging USB devides works in that stage. Please try this patch: http://people.freebsd.org/~will/patches/ata_xpt_add_advinfo.0.diff Thanks. --Will. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Western Digital WD360GD SATA disk on -CURRENT
On Sun, Nov 30, 2003 at 01:49:14AM -0500, Joe Marcus Clarke wrote: I have a host controller with the same chipset. I was having frequent data corruption problems, so I asked about it on current@ a few days ago. so@ offered a patch (which has now been comitted), but it didn't help. Bottom line, he said to get a Promise SATA card. Since I don't want to mess around with this anymore, I went to Amazon, and ordered one. In looking at this output, I doubt the patch would even affect you since you're using the new hardware revision. For more details, check the archives for current@ for a thread with the subject, Recent ATA drivers giving problems with SATA. Yeah, that's what I figured. When I looked at the change, the fix only appears to affect rev 0x00, but my SiI3112A is 0x02. :( Well, I can tell you that people aren't gonna be happy when their brand new motherboard that comes with SiI SATA builtin doesn't work with their SATA disks (or well, just this one?). Since SiI's are so cheap (and fairly common), I'd consider this a showstopper as far as SATA goes. This thing used to work, it should be fixed. Besides, I simply don't have the money to spend on another SATA controller for my main workstation just so it can run up-to-date -CURRENT. :( Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Western Digital WD360GD SATA disk on -CURRENT
On Sun, Nov 30, 2003 at 01:07:30AM -0600, Derek Ragona wrote: I have a server that uses the same chipset with a maxtor drive, no RAID just a single drive. My hardware exact hardware is: Adaptec SATA 1210SA (SiI 3112 SATA150 controller in non RAID mode with a single drive) and a Maxtor 6Y120M0 120 GB drive It is probed correctly with the ISO mini 5.2 beta, but it was still having data problems with larger IO in multiuser. The error I get is: ad4: timeout sending command=ca ad4: error issuing DMA command I will try the 11/29 snapshot and see if that is any better. Well, you're not using the same card or drive that I am, but thanks for your feedback. I am fully aware that there are many people who have (semi-)working SATA configs in recent -CURRENT. :) Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Western Digital WD360GD SATA disk on -CURRENT
On Sun, Nov 30, 2003 at 02:11:59AM -0500, Will Andrews wrote: Well, you're not using the same card or drive that I am, but thanks for your feedback. I am fully aware that there are many people who have (semi-)working SATA configs in recent -CURRENT. :) I should say, mine is completely broken. The SATA controller probes. The disk does not probe at all. Between September 1 and ~October 15 (can't remember exactly), it used to probe, but incorrectly. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Western Digital WD360GD SATA disk on -CURRENT
Hi, Ever since I found the set of commits which broke probing this disk on/about September 1, I have attempted to boot a JPSNAP about once a week. Up to this day, on which I tried 5.2-BETA (official ISO), it has never again probed this drive correctly. I'm using it with a: [EMAIL PROTECTED]:6:0: class=0x018000 card=0x31121095 chip=0x31121095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SiI 3112 SATARaid Controller' class= mass storage (note, no RAID has been configured, only one disk is attached) Has anyone had better luck? Thanks. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem on a laptop with current
On Mon, Nov 10, 2003 at 09:17:07AM -0800, Doug White wrote: (broadcom 4401). Broadcom wireless cards are not supported in -CURRENT. That's not a wireless card. It's an el cheapo 10/100 chipset. Linux supports it now, and it's found in some Athlon motherboards (such as the one powering cvsup12.freebsd.org) as well as some newer laptops. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suddenly bind and access to NNTP server (localhost) doesn't work
On Mon, Nov 03, 2003 at 01:47:06PM +0100, Andreas Klemm wrote: Since about 2 days I can't make dns queries via local nameserver. To get dns requests I need to add my forwarders in /etc/resolv.conf. I've noticed this before (on FreeBSD 4.8), then realized my ISP was blocking 53/TCP. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [security-advisories@freebsd.org: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-03:17.procfs]
On Fri, Oct 03, 2003 at 09:45:27PM -0400, Barney Wolff wrote: I'm finally motivated to ask, why don't security advisories contain the equivalent revs for -head? Surely I can't be the only person following -current who doesn't build every day. Simply because the SO does not support -CURRENT. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [security-advisories@freebsd.org: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-03:17.procfs]
On Fri, Oct 03, 2003 at 10:10:41PM -0400, Barney Wolff wrote: Does this mean that the situation can ever arise where a security bug is corrected in the advisory's announced releases but not in -current? Or, can we assume that as of the time of the security announcement the vulnerability has *always* been corrected in -current? No. Yes. The rule is that changes are always committed to -CURRENT first, unless they do not apply. This rule is rarely broken in FreeBSD, and certainly never broken for security issues. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI3112 SATA controller problems - status
On Tue, Sep 30, 2003 at 10:06:40PM +0200, Soren Schmidt wrote: I have now found a way to reproduce the DMA problems some setups seems to be having with the SiI3112A SATA chip. Now, if I use real SATA drives, (and I mean real SATA drives, the WD Raptor fx is not a real SATA device but just a PATA device with a build in PATA-SATA converter chip) it works just fine no matter what I try. Interesting. SATA is also a power spec, right? I use a normal SATA cable but also an ATX power connector. I'm guessing that's what you mean by the Raptor not being a real SATA drive. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI3112 SATA controller problems - status
On Tue, Sep 30, 2003 at 10:22:33PM +0200, Soren Schmidt wrote: No what I mean is that the Raptor is a PATA device fitted with a marvell PATA-SATA converter on board, its not a pure SATA design, but just the old stuff they used to make with the marvell chip kludged on the back :) The power connector is uninteresting in this context. Interesting, since no one's made any PATA drives that spin at 10,000 RPM as far as I know. For some reason I thought the interface change allowed for this (but couldn't come up with a good reason why it would make a difference). :) Thanks for your work, btw. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI3112 SATA controller problems - status
On Tue, Sep 30, 2003 at 06:15:58PM -0500, David Leimbach wrote: Yeah... I feel somewhat betrayed. Time to switch to a different drive brand :) I should have bought a Maxtor 10K III U160 SCSI drive instead. :) Getting an appropriate controller would have been more expensive, but the drive's about the same... ;-\ Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
On Mon, Sep 29, 2003 at 09:13:48PM +0200, Soren Schmidt wrote: First off, there is ONLY support for Promise and HPT soft RAID in the ATA driver, other vendors products are *not* supported (yet). Second, there seem to be a problem with some sil3112 setups where timeouts and what not ruins the lunch, but so far I've not been able to reproduce.. I am still unable to use my SATA drive, it's probed incorrectly as I posted earlier. Reverting to the August 10th 00:00 UTC kernel fixes this problem, so I concluded that ATAng broke this. If it makes any difference, my model is a SiI3112 RAID controller, but I only have one drive and it probes as ad4... the situation doesn't improve any if I add ataraid. But maybe ATAng doesn't take into account the difference between a normal and a RAID SiI 3112, if any? Here are my dmesg's again (Sep 18th, Aug 10th kernels): http://csociety.org/~will/dmesg.badATAng http://csociety.org/~will/dmesg.Aug10.preATAng The problem shown in the first dmesg still showed itself when I tried a new kernel on Sep 25th. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
On Mon, Sep 29, 2003 at 04:05:11PM -0500, David Leimbach wrote: I'd have to reboot and see how recent my FreeBSD stuff is... I have been rather distracted by the job which pays me salary :). If you can do that, I'll check out a copy of the kernel from that day and try to narrow down when the SiI3112A/WD Raptor probe broke. Hopefully that will be of more use to Soren. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiL3112 SATA (RAID) Controller drives aren't working at all.
On Mon, Sep 29, 2003 at 05:42:24PM -0500, David Leimbach wrote: Ok... I built mine on Thu Sep 18 22:42:16 CDT 2003. I think that's post ATAng commit. WTF?!?! My problem is for Sep 18 kernel and later. I'll have to try Sep 15 or something just to see... Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
SiI 3112A doesn't probe, take two: found the commit that broke it
Hi, http://lists.freebsd.org/pipermail/cvs-src/2003-September/009918.html src/sys/dev/ata/ata-all.c, rev 1.188 src/sys/dev/ata/ata-lowlevel.c, rev 1.8 After an exhaustive binary search, I've found this is the commit that broke probing for my SATA disk. Merely reverting the change on the latest kernel doesn't compile, however. :-\ Hope this is more helpful, Soren... I'll just stick with the Sep 1 00:00 UTC kernel for now. If you have any patches you think will fix this problem feel free to ask me to test. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE 3.1.4 on 5.1-CURRENT fixes for PTHREAD_LIBS
Hello, With the help of Adriaan de Groot, Andy Fawcett, and Lauri Watts, I've successfully built KDE on 5.1-CURRENT as of 2003/09/19. The following patch can be applied: http://www.fruitsalad.org/patches/kde314-fixpth.diff using: cd /usr/ports patch kde314-fixpth.diff Please test this. Followups to [EMAIL PROTECTED], flames to /dev/null. Thanks for your time. Note1: At the moment KDE hasn't been built on axp* for 4.9R, so this patch won't be committed in the meantime. Note2: Yes, we know -pthread was temporarily put back. It will be removed again soon. Note3: There are several ports that use KDE's configure scripts but are not maintained by us. These ports are most likely still broken. Some of them use our Makefile.kde code, and for those, I've added a line to ignore our pthfix since they will need their own. Note4: Patch has been applied to KDE HEAD to resolve the same issues. Therefore, this patch will be removed when 3.2 is released. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Initial list of ports that fail due to -pthread
On Wed, Sep 24, 2003 at 01:34:13AM -0400, Michael Edenfield wrote: One very important group of ports that should get looked at when this gets worked out is KDE. Apparently, Qt uses a different means of determining wether to use threading, than the ports that depend on it. The qt-using ports appear to check for -lpthread, then c++ -pthread, and if neither of those checks pass, disable threading: I have been working with KDE-FreeBSD to make a patch to fix this problem since last week. I am nearly done testing it, so please bear with me and I will get it committed soon. We expect to remove it with the release of KDE 3.2 in a few months as it will be committed to HEAD in KDE. Also, I believe I fixed qt32 on 18 September 2003. It certainly built and works fine on my 5.1-CURRENT 2003/09/19 box. It's just KDE that needs fixing at the moment. I'm typing this in KDE 3.1.4 on said machine. Thanks. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Mon, Sep 22, 2003 at 10:35:10PM -0600, Scott Long wrote: [...] Scott said it all for me. Seriously. The whole idea of breaking backwards de-facto compatibility is bad, bad, bad. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote: OK, here's what we can do to fix this: 1) Put back -pthread in -current so all the ports don't fail 2) I will build a full set of -current packages with the -pthread error still in place, to determine the list of packages that need to be fixed (in fact I already have this, see http://dosirak.kr.freebsd.org/errorlogs). 3) You, John Birrell, and whoever else is interested in fixing these ports can work on them at your own pace without disrupting life for the rest of the users. Once they're all fixed, we can turn the error back on or make it a NOP or do whatever else is decided to be appropriate. 4) It is likely that steps 2 and 3 will need to be iterated several times, because there are dozens of ports that need to be fixed, and many of them are hiding other ports that depend on them and also need to be fixed. I don't know if there is much point to #1 at this point since it's been gone for about 2 weeks now. #2/3/4 sounds fine to me. In the meantime KF is working on a patch to properly support PTHREAD_LIBS in KDE's configure scripts. We plan to commit it when the freeze lifts, pending PR #55325. I suggest that people not build ports on -CURRENT for a few weeks until things get sorted out, unless they're going to fix the problems with specific ports. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Sun, Sep 21, 2003 at 02:12:55AM -0400, Daniel Eischen wrote: Because when things break, people fix them. There is no motivation (as seen in the last 2+ years) to fix something that isn't broken. Please also see: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=321307+0+archive/2003/freebsd-ports/20030601.freebsd-ports my posting to ports@ in May of this year. I wish you'd pushed the issue a bit more aggressively. Sometimes people don't pay close enough attention, and I am definitely one of those people. My apologies for missing that message. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fixing -pthreads (Re: ports and -current)
On Sun, Sep 21, 2003 at 03:17:28AM -0400, Daniel Eischen wrote: From what I've recently read, the freeze should be lifting this week. Can we hold off till then? Is a few more days going to matter? If the freeze continues longer than expected, I'll back the change out until it's over. I think we are going to extend it to allow more fixes for 4.9 since it's going to be delayed. But I'm not positive. Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 09/18 -CURRENT does not boot off SATA
On Thu, Sep 18, 2003 at 08:48:57PM -0700, Will Andrews wrote:
My -CURRENT workstation won't boot off the WD Raptor 36GB disk,
which is on a SiI 3112A SATA-150 controller. This was working
with a kernel in early July. {build,install}{world,kernel}
completed. Fortunately, it seems I can still boot with the
older kernel. I guess ATAng problems still haven't been fleshed
out or I'm missing something?
Anyway, the disk is probed but is not correctly identified. It
says something like:
ad4: 32MB * * * * * * * * * * * * * * * * * * * * [65537/1/1] at ata2-master WDMA0
where * appears to be a smiley face. Strange.
Anyone seen anything like this? Thanks in advance.
So, having received no response to this, I decided to bootstrap
the machine using a PATA disk. Funny that, the machine won't
boot off the PATA disk directly. Hilarity ensues. For details,
see: http://csociety.org/~will/dmesg.badATAng
which is the output of dmesg -a where I booted -v.
Regards,
--
wca
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
09/18 -CURRENT does not boot off SATA
Hi,
My -CURRENT workstation won't boot off the WD Raptor 36GB disk,
which is on a SiI 3112A SATA-150 controller. This was working
with a kernel in early July. {build,install}{world,kernel}
completed. Fortunately, it seems I can still boot with the
older kernel. I guess ATAng problems still haven't been fleshed
out or I'm missing something?
Anyway, the disk is probed but is not correctly identified. It
says something like:
ad4: 32MB * * * * * * * * * * * * * * * * * * * * [65537/1/1] at ata2-master WDMA0
where * appears to be a smiley face. Strange.
Anyone seen anything like this? Thanks in advance.
Regards,
--
wca
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup sites are all at capacity?
On Tue, Sep 16, 2003 at 04:01:39PM -0600, Andrew Lankford wrote: I've tried various cvsup sites (normally cvsup2 or cvsup16 ) and each site returns this message: Rejected by server: Access limit exceeded; try again later I've gotten that before but never with all of the hosts out there. Is everyone and their brother doing a make world today, are the sites down for maintenance, or is something sinister going on? Mine (cvsup12) is still below capacity (28 max clients): http://paloalto.csociety.org/mrtg-sanmateo/ (mrtg) It never got above 10 clients before today. How about a few people switch to my server for regular updates? Thanks. :) Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: D-Link DGE-500T support
On Tue, Aug 05, 2003 at 08:49:50AM -0500, Nick H. - Network Operations wrote: I attempted to use a D-Link DGE-500T card this weekend on 5.1-RELEASE (and -CURRENT) with no success. It is unable to probe the device and find a proper driver for it. My question is: are there any plans currently to provide support for this card? If there is already support for it (which may be the case) then which driver is it using? I tried a GENERIC kernel with all the default drivers, but it diddnt work with them. I can eventually get dmesg output again, but I'd need to bring the server down to put the card back in. Any help is more than welcome. Thank you! This card's chipset is the NatSemi gigE chipset, which is supported by the nge(4) driver. However, as nge(4) cards are relatively uncommon, support is not enabled by default in the GENERIC kernel. You can load the if_nge module, however. kldload if_nge In fact, the only gigE chipset common enough to make it into GENERIC is the Broadcom, supported by bge(4). Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc related -current upgrade problems
On Fri, Jul 25, 2003 at 05:45:10PM -0700, Scott M. Likens wrote: These issues have been addressed in KDE 3.1.3 if you're patient enough for Will to work out the kinks the ports will be updated in a week or less. Much more likely someone else on kde-freebsd is going to solve those problems, if they aren't already. regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GBDE automation scripts?
On Wed, Mar 12, 2003 at 05:39:01PM -0800, Lucky Green wrote: I am writing a section for the Handbook on how to use gbde. Currently, using gbde is a rather manual process. Each time a host reboots, the admin needs to attach the gbde device(s), enter any required passphrases, manually fsck the partition, and mount it. I suspect some subscribers to this mailing list have scripts in place to at least partially automate the process. If you have such a script, could you please get in touch with me for inclusion of the script in the Handbook? I suggest getting it added to the ports tree, or perhaps the base system itself. PHK might have a preference along these lines. Putting it in the Handbook isn't my idea of being a good place to maintain actual programs. Just a thought. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Amanda backups, or dump(8) broken?
Hi, Is anyone else here backing up -CURRENT machines using AMANDA? I've been noticing that the backups for these machines have what appear to be bad backups. That is to say, amverify gives things like this: [...] firepipe-3 (ganymede._.20030304.1): amrestore: 0: skipping start of tape: date 20030304 label firepipe-3 amrestore: 1: restoring ganymede._.20030304.1 gzip: stdin: decompression OK, trailing garbage ignored amrestore: 2: reached end of information cannot open /dev/tty: Device not configured Tape is not a dump tape 64+0 in 64+0 out firepipe-3 (oberon._usr.20030304.2): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring oberon._usr.20030304.2 gzip: stdin: decompression OK, trailing garbage ignored amrestore: 1: reached end of information cannot open /dev/tty: Device not configured Tape is not a dump tape 64+0 in 64+0 out [...] ganymede: FreeBSD ganymede.firepipe.net 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sun Mar 2 22:01:40 EST 2003 [EMAIL PROTECTED]:/net/ganymede/src/sys/i386/compile/GANYMEDE i386 oberon: FreeBSD oberon.firepipe.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Jan 14 01:19:15 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/sparc64/compile/OBERON sparc64 Ganymede runs Amanda 2.4.3 while oberon is running Amanda 2.4.4b1 due to 64-bit safeness fixes in that version. Note that I also back up three other machines (two 4.x/i386 and one Linux/mipsel) without a peep from amverify. Anyone know if maybe the dump format has been changed to the extent that it breaks Amanda or something? In fact, based on the 64+0 it appears that the header or something similar may have been broken. Or maybe Amanda is broken. I'm just looking for someone else who has already seen this behavior. Preferably someone else that knows what the issue is and how it might be fixed... Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Amanda backups, or dump(8) broken?
On Tue, Mar 04, 2003 at 11:57:34AM -0800, Brooks Davis wrote: I've seen reports that dump compatability was broken. I'm dumping two 5.0 boxes and one 4-STABLE box to one of the 5.0 boxes and the amverify I'm current running doesn't seem to have any problem. Thus, I'd tend to suspect we need to fix restore in 4.x. What about non FreeBSD Amanda servers? Are they going to be able to verify a FreeBSD-CURRENT dump? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VM_METER no longer defined?
On Sat, Jan 18, 2003 at 04:02:00PM -0500, Joe Marcus Clarke wrote: Ok, I agree that the naming could cause confusion since there is a vmmeter struct and a vmtotal struct. However, the Release Engineering policy that was set out at the start of RELENG_5_0 is that public API changes need review. I'm not saying that those reviews won't be approved, but we want to keep the pain involved in 5.0-5.1 as low as possible. This is causing pain with several high-profile ports. In my opinion, the inconsistency in VM_METER was annoying, but not enough to justify breaking an interface that has been existence since _1994_. Dude, that is _9_ years. If you'd like the name to change, lets hold of for RELENG_5 to happen. Please back out the name change. Scott, the API change does not exist in RELENG_5_0. This change only went into HEAD. ...which will later become 5.1 and RELENG_5, yes? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: wifi drivers error - 5.0-CURRENT
On Sat, Jan 18, 2003 at 10:14:47PM -0600, Nick H. -- Technical Support Engineer wrote: Got this today after cvsup'ing earlier this morning: Read src/UPDATING. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VM_METER no longer defined?
On Fri, Jan 17, 2003 at 01:02:07PM -0500, Joe Marcus Clarke wrote: It looks like Matt did this to fix vm.vmtotal. From sys/vm/vm_param.h: Make 'sysctl vm.vmtotal' work properly using updated patch from Hiten. (the patch in the PR was stale). It looks to have been replaced by VM_TOTAL. I fixed libgtop[2] by checking for VM_TOTAL, and using that instead of VM_METER. This seems to work. Of course, these things can be fixed. But I consider this change gratuitous and it breaks standard compatability rules: deprecate for one major version and remove in the second. I haven't seen any reason why this couldn't be added to vm/vm_param.h: #define VM_METER VM_TOTAL for compatability purposes. This change is way too sudden in an external API (if it's supposed to be internal, then protect it with an #ifdef _KERNEL already!). Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: x11/kdebase3 build?
On Thu, Jan 16, 2003 at 03:14:25PM -0600, Sean Kelly wrote: I'm not entirely sure this belongs on -CURRENT, but I couldn't find any KDE specific list similar to -gnome and I seem to recall that the building of KDE3 was a desired goal for FreeBSD 5.0. That said, I apologize in advance if this is the wrong place to take this. There is. See http://lists.csociety.org/listinfo/kde-freebsd/ which is where [EMAIL PROTECTED] sends mail to. Is it just me, or does x11/kdebase3 (3.0.5) not build on 5.0-STABLE? 5.0-STABLE? What's that? :) Seriously, KDE built fine for me on -CURRENT but I haven't tested a recent one. Perhaps this problem might be because of a recent change to -CURRENT. I notice that VM_METER is not defined in my latest upgrade. So I looked on a 4-STABLE box and found it in vm/vm_param.h. Then I found it in src/sys/vm/vm_param.h. According to the cvs log, Matt Dillon changed the name of the variable. Sigh. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __sF
On Sat, Nov 02, 2002 at 10:10:31AM -0800, Steve Kargl wrote: This will break some commercially available software that can't easily replaced. kargl[248] f95 -V a.f90 NAGWare Fortran 95 compiler Release 4.2(468) Copyright 1990-2002 The Numerical Algorithms Group Ltd., Oxford, U.K. f95comp version is 4.2(468) /usr/local/lib/NAGWare/libf96.so: undefined reference to `__sF' collect2: ld returned 1 exit status I seriously doubt that NAG will support both a 4.x and 5.x version of their compiler. That's why we have compat libs. compat4x should handle this unless I'm mistaken. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdrtools doesn't build on -current
On Fri, Oct 18, 2002 at 05:37:22PM -0400, Long, Scott wrote: No, the systems people do do stuff wrong. It's been plainly pointed out many times recently when someone does something wrong. However, what's wrong with a little cooperation? If a port breaks because of a system change, the maintainer of the port is certainly welcome to raise a stink over it. All I'm asking is that ports maintainers make an effort to maintain their ports. Will's accertation that it's an all or nothing issue is certainly not productive, and neither is the 'us versus them' inuendo here. You need to re-read my message. I merely said it shouldn't be a total effort on the part of ports developers, as you imply. That is counter-productive (since it's unfair to assume they all know exactly what the change results in). All I'm asking for is a little foresight on the part of those that break things in -CURRENT. It's much easier just to leave (a) port(s) broken for a couple months while the dust settles in -CURRENT, as developers there continue to leave ports people in the dark on the effects of their changes and common approaches to fixing the problems. Only when that is resolved is it reasonable to expect *all* ports maintainers to keep up. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdrtools doesn't build on -current
On Fri, Oct 18, 2002 at 02:20:59PM -0700, Kent Stewart wrote: In 40 years of using computers, nothing has changed. The system's people are still primadona's and do nothing wrong. Get used to it :). Unfortunately!! People don't install OSes because of the OS as much as the codes they can run on it. The importance tree is inverted. The people that think they are the most important are only there to provide improved tools to the people that users depend on. Whatever you say, dude. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdrtools doesn't build on -current
On Fri, Oct 18, 2002 at 01:37:02AM -0600, Scott Long wrote: The ports collection is one of the crown jewels of FreeBSD. Unfortunately, even as more ports committers are added, more and more ports break or become harder to build. On top of that, pkg_add has become close to worthless now that the -r feature is so fragile. If 5.0 goes out and popular ports don't build, it will hurt the image of FreeBSD. Please, take a break from adding new ports and/or maintaining your pet ports and fix some of the broken-ness. So, just to make sure I get this straight: 1) Somebody commits a patch to -CURRENT without doing the slightest bit of analysis of its damage to ports, discussing it with the ports list, or even a HEADS UP or patch suggestions. 2) Tons of ports break. 3) Therefore, ports people should fix the breakage. Yah, right. Exactly why I don't use -CURRENT for much of anything nowadays. Too many people breaking stuff without bothering to fix it themselves in any way. So, why don't you encourage -CURRENT developers to treat ports like the crown jewel it is instead of pestering ports developers to fix their breakage? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where to get -current pkgs?
On Thu, Oct 17, 2002 at 01:01:59PM -0500, David W. Chapman Jr. wrote: bento should have them but I dont' know how up to date it is. Bento is returning to 5-CURRENT builds in lieu of DP2 and hopefully 5.0-RELEASE, now that 4.7-RELEASE is out. I believe we will do 4-STABLE builds less frequently than 5-CURRENT for some time. In any case, the latest packages available publically are posted on the FTP mirrors, but also on bento (check the webpages). regards -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI instability on Sony VAIOs?
Hi, Is anyone else seeing -CURRENT unable to boot on Sony VAIOs running the newest -CURRENT? I get panics when it goes anywhere near ACPI, and it drops into the debugger. Moving acpi.ko out of the way allows it to go further, but then it hangs after it loads the keyboard controller... atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 The last time I tried to upgrade this machine (and it worked) is apparently March 29, 2002. It badly needs an upgrade, and since we need to make -current more usable for 5.0R, if any ACPI or whatever hackers can tell me what they need I'll get it. I can attach a serial console on the laptop if necessary. Thanks in advance. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI instability on Sony VAIOs?
On Mon, Oct 14, 2002 at 05:49:31AM -0700, Will Andrews wrote: The last time I tried to upgrade this machine (and it worked) is apparently March 29, 2002. It badly needs an upgrade, and since we need to make -current more usable for 5.0R, if any ACPI or whatever hackers can tell me what they need I'll get it. I can attach a serial console on the laptop if necessary. For shits and grins, I set up a serial debugging line, built a GDB/DDB debugging kernel, and all that stuff. The remote debugger connection seems to be working okay, but this is all I'm getting from GDB: (kgdb) bt #0 0xc0399eb4 in ?? () #1 0xc0234d0b in ?? () #2 0xc02291b1 in ?? () #3 0xc05ad049 in ?? () #4 0xc05abe4b in ?? () #5 0xc05abff4 in ?? () #6 0xc05ac8d5 in ?? () #7 0xc05a828a in ?? () #8 0xc05a8da0 in ?? () #9 0xc02478f0 in ?? () #10 0xc0248328 in ?? () #11 0xc05a23f4 in ?? () #12 0xc05a1d27 in ?? () #13 0xc02478f0 in ?? () #14 0xc0248328 in ?? () #15 0xc03a485c in ?? () #16 0xc02478f0 in ?? () #17 0xc0249868 in ?? () #18 0xc0396cd5 in ?? () #19 0xc0210775 in ?? () (kgdb) The only thing suspicious is, GDB says at the start: --- 1 3760-0 (8:06:13) [will@puck ~]% gdb -k kernel.debug GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd...Deprecated bfd_read called at /net/puck/stable/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dwarf2read.c line 3049 in dwarf2_read_section Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. --- Ok, then I figured, this is probably an old GDB problem. So I started GDB 5.2 instead... --- 1 3767-0 (8:21:07) [will@puck ~]% gdb52 kernel.debug GNU gdb 5.2 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-portbld-freebsd4.7... (gdb) target remote /dev/cuaa0 Remote debugging using /dev/cuaa0 Debugger (msg=0x2a ) at ../../../i386/i386/db_interface.c:323 323 ../../../i386/i386/db_interface.c: No such file or directory. in ../../../i386/i386/db_interface.c warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. warning: shared library handler failed to enable breakpoint (gdb) bt #0 Debugger (msg=0x2a ) at ../../../i386/i386/db_interface.c:323 #1 0xc03a339b in init386 (first=42) at ../../../i386/i386/machdep.c:1807 (gdb) continue Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. Debugger (msg=0x12 Address 0x12 out of bounds) at atomic.h:260 260 atomic.h: No such file or directory. in atomic.h (gdb) bt #0 Debugger (msg=0x12 Address 0x12 out of bounds) at atomic.h:260 #1 0xc0234d0b in panic (fmt=0x0) at ../../../kern/kern_shutdown.c:494 #2 0xc02291b1 in free (addr=0xc05ad021, type=0xc05b5580) at ../../../kern/kern_malloc.c:222 #3 0xc05ad049 in ?? () #4 0xc05abe4b in ?? () #5 0xc05abff4 in ?? () #6 0xc05ac8d5 in ?? () #7 0xc05a828a in ?? () #8 0xc05a8da0 in ?? () #9 0xc02478f0 in device_probe_and_attach (dev=0xa) at device_if.h:39 #10 0xc0248328 in bus_generic_attach (dev=0x12) at ../../../kern/subr_bus.c:1725 #11 0xc05a23f4 in ?? () #12 0xc05a1d27 in ?? () #13 0xc02478f0 in device_probe_and_attach (dev=0x4) at device_if.h:39 #14 0xc0248328 in bus_generic_attach (dev=0x12) at ../../../kern/subr_bus.c:1725 #15 0xc03a485c in nexus_attach (dev=0xc0effc80) at ../../../i386/i386/nexus.c:231 #16 0xc02478f0 in device_probe_and_attach (dev=0xc0effc80) at device_if.h:39 #17 0xc0249868 in root_bus_configure () at ../../../kern/subr_bus.c:2241 #18 0xc0396cd5 in configure (dummy=0x0) at ../../../i386/i386/autoconf.c:144 #19 0xc0210775 in mi_startup () at ../../../kern/init_main.c:214 (gdb) --- Seems to be OK. Guess I need to have the source tree on the debugging machine, not the target. :-] I'll get to that later I guess. Comments appreciated. Is there any way to use the same serial line to obtain the kernel messages printed on the console (as it's an x86 box)? regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI instability on Sony VAIOs?
On Mon, Oct 14, 2002 at 02:40:18PM -0400, John Baldwin wrote: *sigh*, this is not related to his problem. I think the ACPI PCI link code has a bug in that it tries to free memory it has not allocated (including actual error messages and a trace from ddb() could help verify this) and has nothing to do with the TLB on the CPU. In fact, that is what appears to be the problem (panic() freeing memory that doesn't exist), but I can't get a traceback without the debugger on a remote system... unless I manually copy it... Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI instability on Sony VAIOs?
On Mon, Oct 14, 2002 at 04:08:59PM -0400, John Baldwin wrote: DDB over a serial console and 'tr'? You can also get the dmesg up to the point in question with the serial console as well which would help. I'm assuming you can setup the serial console since you are doing remote gdb. :) Yes, but I couldn't find any documentation to tell the kernel to send console kernel messages over the serial line... well, anyway, until now... http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html I don't have time to set it up right now, guess I'll do it tomorrow probably. regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: addport b0rken in current
On Tue, Oct 08, 2002 at 06:15:38PM +0300, Maxim Sobolev wrote: Any progress on this??? It's PITA that I can't use my -current development box to commit new ports. Sorry, I hadn't even started to look at this. It seems to be a -CURRENT cvs(1) problem judging by your log, in that it ignores the EDITOR passed to it when committing. What happens is that addport constructs the log before committing, and overrides cvs(1)'s default of using an editor to edit the log by doing EDITOR=cp /path/to/generated/log cvs ... Seems like, if it is using vi, something is not right w/ cvs. Log message unchanged or not specified a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs Action: (continue) ex/vi: Vi's standard input and output must be a terminal cvs server: warning: editor session failed Log message unchanged or not specified a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs Action: (continue) Unknown input Log message unchanged or not specified a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs cvs server: cannot read from stdin: No such file or directory I'm upgrading my x86 -CURRENT box and will have a look at this more directly RSN... regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GEOM -CURRENT on sparc64
Works just fine. dmesg output: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #3: Sat Aug 17 16:48:56 EDT 2002 [EMAIL PROTECTED]:/usr/src/sys/sparc64/compile/OBERON Preloaded elf kernel /boot/kernel/kernel at 0xc040a000. Timecounter tick frequency 50200 Hz cpu0: Sun Microsystems UltraSparc-IIe Processor (502.00 MHZ CPU) nexus0: OpenFirmware Nexus device pcib0: U2P UPA-PCI bridge on nexus0 pcib0: sabre: impl 0, version 0: ign 7c0 DVMA map: 0xc000 to 0xdfff device 0/12/0: latency timer 64 - 82 pcib0: ofw_pci_init: no interrupt mapping found for 0/12/0 (preset 0) pcib0: ofw_pci_init: no interrupt mapping found for 0/7/0 (preset 0) device 0/12/1: latency timer 64 - 82 pcib0: ofw_pci_init: mapping intr for 0/12/1 to 6 (preset was 0) device 0/12/2: latency timer 64 - 82 pcib0: ofw_pci_init: mapping intr for 0/12/2 to 28 (preset was 0) device 0/12/3: latency timer 64 - 82 pcib0: ofw_pci_init: mapping intr for 0/12/3 to 36 (preset was 0) pcib0: ofw_pci_init: no interrupt mapping found for 0/3/0 (preset 0) device 0/8/0: latency timer 64 - 16 pcib0: ofw_pci_init: mapping intr for 0/8/0 to 35 (preset was 0) device 0/13/0: latency timer 64 - 16 pcib0: ofw_pci_init: mapping intr for 0/13/0 to 12 (preset was 0) PCI-PCI bridge at 0/5/0: setting bus #s to 0/1/1 pcib0: ofw_pci_init: descending to subordinate PCI bus device 0/19/0: latency timer 64 - 66 pcib0: ofw_pci_init: mapping intr for 0/19/0 to 15 (preset was 15) pci0: PCI bus on pcib0 pci0: old, non-VGA display device at device 3.0 (no driver attached) pcib1: PCI-PCI bridge at device 5.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 pci0: multimedia, audio at device 8.0 (no driver attached) ebus0: revision 0x01 ebus0: idprom: incomplete ebus0: PCI-EBus3 bridge mem 0xf100-0xf17f,0xf000-0xf0ff at dev ice 12.0 on pci0 ebus0: flashprom addr 0-0xf (no driver attached) eeprom0: EBus EEPROM/clock addr 0x1-0x11fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 809fd225 gem0: Sun ERI 10/100 Ethernet Adaptor mem 0x40-0x41 irq 6 at device 12 .1 on pci0 miibus0: MII bus on gem0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: Ethernet address: 08:00:20:9f:d2:25, 2KB RX fifo, 2KB TX fifo using internal phy pci0: serial bus, FireWire at device 12.2 (no driver attached) pci0: serial bus, USB at device 12.3 (no driver attached) atapci0: AcerLabs Aladdin ATA66 controller port 0xa20-0xa2f,0xa08-0xa0b,0xa10- 0xa17,0xa18-0xa1b,0xa00-0xa07 irq 12 at device 13.0 on pci0 ata2: at 0xa00 on atapci0 ata3: at 0xa10 on atapci0 pci0: display, VGA at device 19.0 (no driver attached) Timecounters tick every 10.000 msec Initializing GEOMetry subsystem ad0: 19092MB ST320011A [38792/16/63] at ata2-master UDMA66 ad1: 38172MB MAXTOR 6L040J2 [77557/16/63] at ata3-master UDMA66 Mounting root from ufs:/dev/ad1a Invalid time in real time clock. Check and reset the date immediately! regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM -CURRENT on sparc64
On Thu, Oct 03, 2002 at 03:41:41PM -0700, Will Andrews wrote: FreeBSD 5.0-CURRENT #3: Sat Aug 17 16:48:56 EDT 2002 [EMAIL PROTECTED]:/usr/src/sys/sparc64/compile/OBERON As some of you might have been able to tell, this is an old kernel. For whatever reason, the kernel wasn't getting built (even though its dependent objects were), so when I ran make install it installed the older kernel... Here's the actual dmesg from a recent -CURRENT... Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Thu Oct 3 22:10:30 EST 2002 [EMAIL PROTECTED]:/usr/src/sys/sparc64/compile/OBERON Preloaded elf kernel /boot/kernel/kernel at 0xc040a000. Timecounter tick frequency 50200 Hz cpu0: Sun Microsystems UltraSparc-IIe Processor (502.00 MHZ CPU) nexus0: OpenFirmware Nexus device pcib0: U2P UPA-PCI bridge on nexus0 pcib0: sabre: impl 0, version 0: ign 7c0 DVMA map: 0xc000 to 0xdfff device 0/12/0: latency timer 64 - 82 pcib0: ofw_pci_init: no interrupt mapping found for 0/12/0 (preset 0) pcib0: ofw_pci_init: no interrupt mapping found for 0/7/0 (preset 0) device 0/12/1: latency timer 64 - 82 pcib0: ofw_pci_init: mapping intr for 0/12/1 to 6 (preset was 0) device 0/12/2: latency timer 64 - 82 pcib0: ofw_pci_init: mapping intr for 0/12/2 to 28 (preset was 0) device 0/12/3: latency timer 64 - 82 pcib0: ofw_pci_init: mapping intr for 0/12/3 to 36 (preset was 0) pcib0: ofw_pci_init: no interrupt mapping found for 0/3/0 (preset 0) device 0/8/0: latency timer 64 - 16 pcib0: ofw_pci_init: mapping intr for 0/8/0 to 35 (preset was 0) device 0/13/0: latency timer 64 - 16 pcib0: ofw_pci_init: mapping intr for 0/13/0 to 12 (preset was 0) PCI-PCI bridge at 0/5/0: setting bus #s to 0/1/1 pcib0: ofw_pci_init: descending to subordinate PCI bus device 0/19/0: latency timer 64 - 66 pcib0: ofw_pci_init: mapping intr for 0/19/0 to 15 (preset was 15) pci0: PCI bus on pcib0 pci0: old, non-VGA display device at device 3.0 (no driver attached) pcib1: PCI-PCI bridge at device 5.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 pci0: multimedia, audio at device 8.0 (no driver attached) ebus0: revision 0x01 ebus0: idprom: incomplete ebus0: PCI-EBus3 bridge mem 0xf100-0xf17f,0xf000-0xf0ff at dev ice 12.0 on pci0 ebus0: flashprom addr 0-0xf (no driver attached) eeprom0: EBus EEPROM/clock addr 0x1-0x11fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 809fd225 gem0: Sun ERI 10/100 Ethernet Adaptor mem 0x40-0x41 irq 6 at device 12 .1 on pci0 miibus0: MII bus on gem0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: Ethernet address: 08:00:20:9f:d2:25, 2KB RX fifo, 2KB TX fifo using internal phy pci0: serial bus, FireWire at device 12.2 (no driver attached) pci0: serial bus, USB at device 12.3 (no driver attached) atapci0: AcerLabs Aladdin ATA66 controller port 0xa20-0xa2f,0xa08-0xa0b,0xa10- 0xa17,0xa18-0xa1b,0xa00-0xa07 irq 12 at device 13.0 on pci0 ata2: at 0xa00 on atapci0 ata3: at 0xa10 on atapci0 pci0: display, VGA at device 19.0 (no driver attached) Timecounters tick every 10.000 msec Initializing GEOMetry subsystem ad0: 19092MB ST320011A [38792/16/63] at ata2-master UDMA66 ad1: 38172MB MAXTOR 6L040J2 [77557/16/63] at ata3-master UDMA66 Mounting root from ufs:/dev/ad1a regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GEOM and -CURRENT
Hi Poul et al, I have been unable to test GEOM on my Sparc64 box on the latest -CURRENT due to the rstat.h breakage for the last two days. Please hold off your GEOM-being-standard commit until that's been fixed. BTW, why the heck are people not fixing code that breaks world in 24 hours, let alone COMPILE TESTING IT BEFORE THEY COMMIT?! === libexec/rpc.rstatd cc -O -pipe-Wformat=2 -Wno-format-extra-args -Werror -c /usr/src/libexec/rpc.rstatd/rstatd.c cc -O -pipe-Wformat=2 -Wno-format-extra-args -Werror -c /usr/src/libexec/rpc.rstatd/rstat_proc.c /usr/src/libexec/rpc.rstatd/rstat_proc.c:87: conflicting types for `havedisk' /usr/obj/usr/src/sparc64/usr/include/rpcsvc/rstat.h:88: previous declaration of `havedisk' *** Error code 1 Stop in /usr/src/libexec/rpc.rstatd. *** Error code 1 regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current.freebsd.org points to japanese site?
On Sun, Sep 22, 2002 at 03:33:24PM -0400, Kenneth Culver wrote: Why does current.freebsd.org point to the japanese snapshot site snapshots.jp.freebsd.org? I'm just wondering because I am trying to install -CURRENT on one of my machines. Because it's the only reliable current snapshot building site? regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KDE broken on CURRENT (with gcc3.2)
On Tue, Sep 03, 2002 at 11:30:02PM +0200, Martin Blapp wrote: ports/devel/fam --- c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\/usr/lo cal/etc/fam.conf\-O -pipe -c RPC_TCP_Connector.c++ c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\/usr/lo cal/etc/fam.conf\-O -pipe -c Scanner.c++ c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\/usr/lo cal/etc/fam.conf\-O -pipe -c Scheduler.c++ Scheduler.c++:37: uninitialized const member `Scheduler::IOTypeInfo::iotype' Scheduler.c++:38: uninitialized const member `Scheduler::IOTypeInfo::iotype' gmake[2]: *** [Scheduler.o] Error 1 gmake[2]: Leaving directory `/usr/ports/devel/fam/work/fam-2.6.8/fam' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/fam/work/fam-2.6.8' gmake: *** [all-recursive-am] Error 2 *** Error code 2 Is still broken. That's not KDE domain, though. We only depend on FAM. regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 02:56:26PM -0700, David O'Brien wrote: This update has been *DEMANDED* in both -current and -ports for months now. Yes, GCC 3.1 prerelease bites, big time, k thx. Better to fix it now than later, when people will actually expect it to work. I also dislike the apparent general policy of using prereleases for our compiler in FreeBSD. regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 03:23:58PM -0700, David O'Brien wrote: This is the same as using RELENG_4_6 (ie, 4.6-SECURE) in something. We get bug fixes (that must work on *all* supported GCC arches). The risk is _well_ mitigated. Why is everyone second guessing Kan on this import??? It will be a wonder if we get another import done by him. Oh, I think GCC 3.2.1 prerelease knocks the socks off 3.1 prerelease. But any time someone is using a FreeBSD -RELEASE, gcc -v should say release in it. That's just MHO. Part of the reason I say this is because the gcc31 port uses the release version and is not subject to the same bugs that the *prerelease* 3.1 compiler that was in -CURRENT was. regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Still no XFree86-4?
On Tue, Jul 16, 2002 at 11:39:41PM -0600, Eric Anholt wrote: I thought the whole point of Wraphelp.c was that the person who runs the machine (whatever machine X is being installed on) has to obtain that file, so they would have to explicitly verify that they -- personally -- have the right to use it. Mind you, I did that once about seven years ago, and I just keep copying that Wraphelp.c around to wherever I need it. I have no idea what the current requirement is... :-) It used to be that way. Then within the last year (iirc) our ports changed to auto-downloading Wraphelp.c and defaulting to HasXdmAuth YES. I don't know what exactly changed legally. I noted that at least NetBSD has a Wraphelp.c in their CVS repos of X-3 and X-4. My changes do make the file required by all of the miniports that could use it, though it only gets used if HasXdmAuth is set to YES by imake-4 (it's default). If you'll read the commit log which made this change, you'll see that I was the one who changed this. I did so after consulting with core regarding the current export rules of the USA. The BXA (Bureau of Export Administration) loosened their rules for cryptographical software export last year (or the year before, I don't remember exactly), and so open source software is only required to register with the BXA if they export cryptographic software. FreeBSD did that many years ago, so I removed the need for somebody to fetch that file if they want XDM-AUTHORIZATION-1. I'd like to point out that Wraphelp.c performs DES encryption, and we have already done that out of the box for quite some time. See http://www.bxa.doc.gov/ for more info. [Seems they changed their name to Bureau of Industry and Security...] regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: When was soundcard.h moved?
On Fri, Jun 14, 2002 at 10:05:52AM +0200, Sheldon Hearn wrote: When was soundcard.h moved from machine to sys? A large number of ports expect to find it in machine, and I can't find a __FreeBSD_version bump supporting the change. So I need to find out when it happened and piggy-back on the nearest __FreeBSD_version bump. :-( Actually, if you don't care about 3.x, you can just change it to sys/soundcard.h (which seems a little more standardized judging by where other OSs put it). 4.x and on have had sys/soundcard.h synchronized with machine/soundcard.h. And 5.x recently only has sys/soundcard.h. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The great perl rewrite - progress report
On Thu, Jun 06, 2002 at 05:31:12PM +0100, Mark Murray wrote: /usr/sbin/sysinstall * - fix - * What part of this uses perl?? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/kern kern_tc.c src/sys/sys timepps.h timetc.h
On Thu, May 02, 2002 at 03:30:40PM -0700, Brooks Davis wrote: I haven't tryed backing the commits out yet, but I'm seeing similar behavior on my HP Omnibook 500. In my case, it's actually not quite hung. What appears to be happening is that nothing is causing the console buffer to actually flush. The system is up (sort of), but the only way to see the console output is to cause a kernel printf, say be breaking in to the debugger. The system is basicaly useless at that point and you can't shutdown cleanly. Similar behavior manifests itself on my -current laptop dated before April 27. I.O.W. it appears to freeze but will flush the console if you break to the debugger then hit 'c'. I believe this was caused by an earlier change to the timecounter code. Unfortunately I didn't have time to investigate further. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: plug aue ethernet goes to panic
On Mon, Apr 15, 2002 at 11:11:36AM +0200, Nick Hibma wrote: device_set_ivars is always called (in usbd_probe_and_attach) with as an argument a stack variable. Also, the ivar is not stored or anything in the if_aue.c driver. So this problem sounds like a problem in revisions of various files. Please check that your kernel modules kernel are in sync. Do this by rebuilding the kernel and the modules from scratch. Also, after you've installed your kernel check that all your kernel files have been updated. Do you by any chance have a stale /modules or /boot/modules directory lying around? You should have only kernel modules in /boot/kernel*/ and NOT in /modules* or /boot/modules*. If the problem persists, please mail me the output of ident /sys/dev/usb/*.[ch] find /modules /boot -type f -ls Nick, You really should talk to Joe Karthauser. He's already confirmed that it *is* an issue in the code (and not any kind of misconfiguration on my part). I've already spent enough time debugging the problem. I recently MFC'd the support for my device to -stable so I could use the machine on the network without it panicking on me. However, when Joe fixes the problem I will give it another shot [same machine has -CURRENT on another partition that I use for occasional hacking]. Thanks for the suggestions, though. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mouse in Xfree86 4.2.0
On Mon, Apr 15, 2002 at 03:25:12PM -0700, David O'Brien wrote: I have requested of both the XFree86-4 Server and of Portmgr to make the default mouse device /dev/sysmouse. But my emails have gone unanswered. They did not go unanswered. I said it was a good idea and that I would do it, but due to lack of time I haven't done it yet. This does not stop you from doing. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: plug aue ethernet goes to panic
On Sat, Apr 13, 2002 at 12:44:36PM -0400, John Baldwin wrote: Can you get a backtrace in ddb? It looks like a null pointer dereference, and knowing where it happened would help. Finding the file and line of the instruction pointer using addr2line on kernel.debug would be helpful as well. It *is* a null pointer deref. Joe and I looked at this problem, and it seems a function called device_get_ivars() isn't doing its job in sys/dev/usb/usb_port.h. So the variable is getting filled with a NULL pointer for the iface element and is later deref'd. That's the limit of my debugging, and Joe is looking into the problem actively. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: usbd(8) doesn't attach aue(4) device properly?
On Sat, Mar 30, 2002 at 01:33:13PM +, Josef Karthauser wrote: It's more likely that it's a new device that isn't included in usbdevs or the driver. What's the product id that you get with 'usbdevs -v'. Check that they're in the usbdevs file and in the driver code. Good call. Here's the info: 1 1105-0 (15:44:40) [will@altair ~]% sudo usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: full speed, power 156 mA, config 1, DSB-650TX USB Ethernet(0x400b), D-Link Corp.(0x2001), rev 1.01 port 2 powered According to sys/dev/usbdevs: /* D-Link products */ /*product DLINK DSBS25 0x0100 DSB-S25 serial adapter*/ product DLINK DSB650C 0x4000 10Mbps ethernet adapter product DLINK DSB650TX 0x4002 10/100 ethernet adapter product DLINK DSB650TX_PNA 0x4003 1/10/100 ethernet adapter product DLINK DSB6500xABC1 10/100 ethernet adapter So, like I said, you're right. :) Is this the only place I need to put information in? Somehow I doubt it. Please provide a patch so I can learn... :) BTW, I tried to override the default behavior found here by adding this information to /etc/usbd.conf but that doesn't work.. Thanks! -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
usbd(8) doesn't attach aue(4) device properly?
Hi, I'm trying to hook my new D-Link DSB-650TX up to a laptop with USB on a March ~26 -CURRENT. However, it's failing miserably: uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xfce0-0xfcff irq 11 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: D-Link Corp. DSB-650TX USB Ethernet, rev 1.10/1.01, addr 2 if_aue.ko is being loaded by the loader at boot time, so this should be working.. but the device is attaching to ugen(4) instead of aue(4). Ideas? The only thing I could think of was /etc/usbd.conf was out of date, but a mergemaster didn't fix this problem. Thanks, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with ssh
On Thu, Mar 28, 2002 at 12:03:17PM -0800, David O'Brien wrote: That is NOT a fix. Some of us want S/Key (OPIE) support. This is a temperary work around. And some of us want passphrase support. :-) SSH should just be fixed to DTRT when one doesn't have S/Key setup on the server... however, it continues to break POLA, several months after the change which caused this was committed. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: turning off malloc's AJ by default
On Sat, Mar 23, 2002 at 06:40:21PM -0800, Steve Kargl wrote: Surely, you're joking. No wonder it's a PITA to convince a 3rd party vendor to release a FreeBSD product. Please don't misinterpret David's words. 3rd party apps are not our *primary* concern, FreeBSD is. And note that in this thread we are talking about turning the default off. This does not stop someone from turning AJ back on and using them to debug/fix a program. :-) Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/sys acct.h acl.h bio.h buf.h callout.h conf.h cons.h disk.h disklabel.h diskslice.h domain.h errno.h event.h eventhandler.h exec.h fcntl.h file.h filedesc.h imgact.h imgact_aout.h imgact_elf.h inflate.h interrupt.h ioccom.h ipc.h ...
On Fri, Mar 22, 2002 at 06:50:55AM -0700, M. Warner Losh wrote: : At least in the case of 'ioccom.h' this commit breaks : the XFree86-server building in the 'drm/kernel' directory. : : The problem is in the '#define ioctl(a,b,c) xf86ioctl(a,b,c)' : which is used by the XFree86 and the __P somehow makes it possible : to build 'xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/xf86drm.c' : and now it stops here. Yes. That's likely the case. I'd kicked off a build of X11 after alfred did these changes, but it died due to lack of disk space before I got to this point and I let the matter sit there for a while. A patch to X11 will be needed. The OpenBSD folks hit this same problem a few days ago when they removed it and committed patches to their repo to fix this problem. Please send it to me as soon as you figure out what it should be and I'll speed it to the tree w/ other patches I have. Please try to make a patch that also works on -stable. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86-4.2.0 ioctl question [-current ioccom.h __P related]
On Fri, Mar 22, 2002 at 01:01:57AM -0600, Eric Liedtke wrote: While trying to build the XFree86-4-Server port this evening(cvsuped today around 1PM CST) the build died due to a redefinition of xf86ioctl. The file /usr/ports/x11-servers/XFree86-4-Server/work/xc/programs/Xserver/include/xf86_ansic.h Yes, this is a problem recently identified on the -current mailing list that someone else is looking into. When they have a patch, I will integrate it ASAP. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/sys acct.h acl.h bio.h buf.h callout.h conf.h cons.h disk.h disklabel.h diskslice.h domain.h errno.h event.h eventhandler.h exec.h fcntl.h file.h filedesc.h imgact.h imgact_aout.h imgact_elf.h inflate.h interrupt.h ioccom.h ipc.h ...
On Fri, Mar 22, 2002 at 08:28:36AM -0700, M. Warner Losh wrote: Ummm, I'm not going to be doing patches for X11 for at least a few more days, if then. I don't have the time to do it until sometime next week. Well if someone else does it, they need to send me the patch. :) Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree86 4.2.0 with G200 fail to start with signal 10
On Wed, Mar 20, 2002 at 11:29:46AM +0100, Riccardo Torrini wrote: With last update of world and ports I'm unable to start XFree86. I have a matrox G200 (agp) and I have tryed with and without the WITH_MATROX_GXX_DRIVER=yes but I got only a signal 10, core dump when starting X. At the same time I switched my MoBo from tyan trinity with k6 to a asus p2b-ds dual processor p3/500. I have a recent system (fresh compile with SMP enabled): What is your pkg_info -Ia? I committed an updated version of the Matrox driver for XFree86-4-Server, maybe you don't have that? BTW, it's not very well tested and I certainly can't test it myself w/o Matrox hardware. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cdrecord for ATAPI burners available..
On Wed, Mar 20, 2002 at 12:00:43AM +0100, Thomas Quinot wrote: These utils are ATA only (as the name implies), if our ports people wants to merge it into whats already there I wont complain :) That said I think the ATA only version covers more than a significant percentage of our userbase Speaking as a ports person, I don't like the idea of having to backport these changes repeatedly over the course of a product's lifetime, and a local hack for FreeBSD is gross. In which case I'll be more than happy to continue maintaining ATAPI/CAM as an alternative solution, which addresses 100% of our user base and does not impose any additional work upon application authors or port maintainers. On the other hand, I think Thomas' approach is more maintainable. I do not understand why ATA/CAM people won't cooperate on this, but then I'm just a ports person... what do I know about maintenance? Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 05:54:40PM -0800, Alex Zepeda wrote: As far as Qt goes, rip out that objprelink crap. Without it Qt will build and work just fine. At least Qt 3.whatever works for me. I don't know why objprelink isn't working correctly for Qt, but I don't really care. For me disabling WITNESS does more than enough to make KDE useable on my -current box (2xP2-450). Um.. objprelink is disabled if OSVERSION = 500029. So it is already ripped out for -current. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: This isn't good: http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log building TenDRA-4.1.2 on gohan17 in directory /x/tmp/5/chroot/31459 with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA maintained by: [EMAIL PROTECTED] build started at Sat Mar 9 00:37:43 GMT 2002 ... Operating system version = 4.4-STABLE I thought uname was faked out to return the proper value. I wonder if things like this could be one of the problems. More like, the port builds in a chroot which contains the environment of a 5.0 world. So the chroot tarball for 5.0 being used here must be the wrong one, or it's screwed up. Thanks for pointing this out. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 07:30:21PM -0500, Robert Watson wrote: uname extracts the various strings it can report from the running kernel using sysctl. Unless you have a faked uname, it will return the properties of the host non-chroot environment, rather than the chroot environment. Increasingly, it's going to be harder and harder to run 5.0 in a 4.x chroot, due to divergence in system calls, especially once threaded applications start using KSE. Running 4.x in a 5.0 chroot should (hopefully) continue to work fine. You are right. I made a thinko, and later realized it while talking to Kris. I was hoping nobody would notice... :) We are screwed if anybody uses sysctl() or sysctlbyname(), unless someone decides to allow us to change kernel variables and the like inside chroot() (or perhaps jail()).. -- wca dunce cap To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote: currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. Hmm. My impression was that the libpng stuff had been fixed, could you confirm that KDE still doesn't build on 5.0-CURRENT? Its not related to libpng, I believe that has been fixed, but I cannot tell for sure because kde cannot be compiled under -current. I'm not the only one that is experiencing it either, here is what I was told by Alan Eldridge [EMAIL PROTECTED] You said binutils upgrade broke KDE -- the quoted mail has nothing to do with binutils. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Preparing innocent users for -current
On Fri, Mar 08, 2002 at 02:58:40PM -0500, Michael G. Petry wrote: Per Doug's note, is there a schedule to pull the XFree86-4 back up to 4.2.0? Since it was pulled back because of the 4.5 release, it would be a shame for it to be also held back by a -current snapshot. Yes, I am handling that. I've been testing a version of the upgrade on 2 of my machines for several weeks, but haven't had time to fix a few more things, which is the reason for the delay, aside from the fact that I was previously waiting on the people who actually wrote the patch to commit it. However, since my midterms are over and spring break is upon me, I will focus a large part of the next few days getting the upgrade done and committed. It should be done by Saturday, March 9 at the earliest and Saturday, March 16 at the latest, and probably on Sunday or Monday. Thanks, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI timecounter help needed!
On Mon, Feb 25, 2002 at 10:59:16AM +0100, Poul-Henning Kamp wrote: Machines with ACPI timecounters will now print 10 lines at boot when the timer is tested. You should mention that this requires bootverbose. If you are lucky you will see ten times something like: ACPI timer looks GOOD min = 3, max = 3, width = 1 That means that you have well implemented ACPI timer. If you are unlucky, one, several or all 10 lines will be marked as BAD. Please send me an email with these 10 lines and the output of pciconf -l -v for your machine. I'm am interested in reports both from good and bad machines. I will send you mine as soon as I can figure out how to extract the information usefully as the machine behaves VERY badly with the ACPI timecounter -- the only way I can see output on the syscons console is if I break into DDB repeatedly. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD unfinished NIS+ implementation in Linux ?
On Sun, Feb 17, 2002 at 03:57:59PM +0100, Martin Blapp wrote: Bill, did you ever allowed them to make it GPL only ? Looking at the code it should be possible to import some things and make a NIS+ client available. But only if it's not GPL'd. Interesting. I looked as nisgrep/nisgrep.c and noticed that the code structure was basically the same, but the variables were just slightly different... -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MODULES_WITH_WORLD=true means no modules?
On Thu, Feb 07, 2002 at 09:57:47PM +0100, BOUWSMA Beery wrote: Maybe... I've changed my /etc/make.conf from the default, to be MODULES_WITH_WORLD=true # do not build modules when building kernel ^^^ ...you need to read the option you enabled? since I find myself often building new kernels (plus identical modules) without updating the rest of the source, taking extra time. Regards. -- wca 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: current.freebsd.org down?
On Thu, Feb 07, 2002 at 04:44:36PM +0100, Miguel Mendez wrote: I know this is probably offtopic but is there any problem with current.freebsd.org at the moment? I've been unable to log in for almost an hour, the ftp daemon is up, it just doesn't allow me in and I was about to load -CURRENT on my laptop. Jordan announced recently that Qwest is upgrading the hardware and that there would be intermittent problems with the server for a certain period (a few days as I recall). Regards -- wca 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: current.freebsd.org down?
On Thu, Feb 07, 2002 at 04:44:36PM +0100, Miguel Mendez wrote: I know this is probably offtopic but is there any problem with current.freebsd.org at the moment? I've been unable to log in for almost an hour, the ftp daemon is up, it just doesn't allow me in and I was about to load -CURRENT on my laptop. Jordan announced recently that Qwest is upgrading the hardware and that there would be intermittent problems with the server for a certain period (a few days as I recall). Regards -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: chinput can't work on KDE2.2.2
On Tue, Jan 22, 2002 at 08:56:13AM +, Liu Siwei wrote: This question is not appropriate for the -current list. I'm expanding this to include the maintainers of the KDE ports to see if anyone else has an idea what's going on. I have a question about FreeBSD's locale. I use the zh_CN.EUC locale to let my FreeBSD support Simplied Chinese. It's all right in gnome 1.4. But in recent version of KDE(aka. KDE-2.2.2), I can't set zh_CN.EUC locale for it. For I have select the country is Asia-China, language is Simplied Chinese, code is gb2312.1980. I need not set any locale in my environment to display Simplied Chinese at all. But for I have not set locale, I can't use chinput in KDE. So I set my locale to zh_CN.EUC in my $HOME/.xinitrc. But when I restart my KDE, it can't display Chinese word proper! in kedit, kwrite, etc, I can use chinput through I can't input any Chinese word proper. If I set my locale to zh_CN.GB2312, zh_CN.GBK or nothing, the KDE can display Chinese word proper, but I can't use chinput. So, how to set ocale to let chinput work under KDE2.2.2? A very inportant QUESTION is: why FreeBSD want zh_CN.EUC while KDE is not? My machine is AMD-K7 700, FreeBSD-current,all software are installed from ports(sources). I'm sorry but I can't help with this specific problem since I do not use any locale other than the default. :( -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Fix for pam_nologin.so runtime error
On Thu, Oct 18, 2001 at 03:02:49PM -0701, Jos Backus wrote: Forgot to mention, I had to make kcheckpass setuid root to make kcheckpass itself work (just verified this on -stable). Uh.. that's documented. See ports/x11/kdebase2/Makefile rev 1.77. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Fix for pam_nologin.so runtime error
On Thu, Oct 18, 2001 at 03:15:58PM -0701, Jos Backus wrote: Really? I just checked 1.77 and I don't see it. Can you tell me what to look for? Oops.. rev 1.78 in conjunction with pkg-message :) http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/kdebase2/Makefile.diff?r1=1.77r2=1.78 http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/kdebase2/pkg-message?rev=1.1content-type=text/x-cvsweb-markup :) -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Deadline for .biz .info approaches!!
Dear Registrant, The most anticipated event since the first release of the dotcoms is here! If you haven't already done so it's time to pre-register your .biz and .info 'Top Level Domain Names' and stake your claim in what is fast becoming a LAND RUSH, larger than the .com phenomena. With the deadline to pre-register your .biz Sept 17, 2001 and Sept 12, 2001 for .info domains approaching (your only real opportunity to secure a great .biz and/or .info) you must act now secure your trading or generic name(s). At the close of these periods all pre-registrations will be processed first. Up for grabs are names like; news.biz, show.biz and adult.info because of the 'Round Robin' [Not First Come First Serve] selection method adopted by ICANN, the release has effectively become The Worlds Largest Lottery. We offer you [but only until September 18th 2001] to pre-register your selection of great names with three of the largest biz .info registrars [Our Channel Partners] in a 3-5 minute process for one low price [as low as US$3.50 per name] this is the lowest price available anywhere including The Registrars Themselves. Heres how it works! Pre-register with one, two or all three of our channel partners at the same time and increase your chances of securing names like 'show.biz or easy.info' up to 300%. Pre-register as many names as you like and save up to 50% with volume discounts. Free.biz! Want to pre-register names like adult.biz for FREE. Easy.biz, simply go to www.drawcard.com enter in your email address at our affiliate page and I will send you an email, with your unique ID that can be forward to all in your address book then all who enter the site by way of that link will earn you US$1.00 per pre-registration. We have people registering 100+ names at a time. Now that's a good.biz! Any and all names you decide to register can come directly off your earnings or if you prefer I will send you a cheque! More_Free.info · For every 20 names or more you pre-register we will give you free for one year a sub-domain name from the very best of our 'channels partners' like '[EMAIL PROTECTED]', '[EMAIL PROTECTED]'. · Free home page with every account. · Free email with every account. This is your very best opportunity to secure 'yourfuture.biz'. But you must Pre-Register and you must do it NOW. Want to see more: http://www.drawcard.com (If this link is not working please cut and paste the link into your browser) If you have received this mailing in error, or do not wish to receive any further mailings from us, simply click here put in your email address and add Remove to the subject line: http://www.drawcard.com/index.cfm?fuseaction=CompanyInfo Damian Andrews MD Drawcard.com
Re: What's touching my executables?
On Thu, Aug 02, 2001 at 06:28:59PM +, Christian Weisgerber ([EMAIL PROTECTED]) wrote: An increasing number of executables on that box are sporting ever newer mtimes. This appears to have been going on ever since the Jul 25 update. There is no clear pattern which executables are touched. md5 comparisons with previous backup levels (using a Jul 13 copy of md5) suggest that the executables have not been changed. For various reasons I consider it unlikely that I'm dealing with a security issue here, although I'm looking into that as well. Can anybody think of a technical explanation? Probably the recent change (IIRC) that someone turned running an executable into a mtime change. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rm -rf question
On Wed, May 23, 2001 at 05:51:40AM -0500, Storms of Perfection wrote: gary@trouble:~$ rm -rf /home/gary/public_html/mrtg/david/ Display all 2275 possibilities? (y or n) gary@trouble:~$ rm -rf /home/gary/public_html/mrtg/david/* bash: /bin/rm: Argument list too long Is this a bug with rm? I've never come accross this on -CURRENT or -STABLE for that matter.. No. It's a safety feature to prevent your shell from using too much memory to do the globbing you asked for (the *). This has nothing whatsoever to do with rm(1). -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvsup trouble
On Mon, May 21, 2001 at 09:49:19PM +0200, The Unicorn wrote: Delete ports/www/jakarta-tomcat/files Updater failed: Cannot delete /usr/ports/www/jakarta-tomcat/files: Directory not empty As posted before: rm -rf /usr/ports/www/jakarta-tomcat re-cvsup -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: world broken yet again
On Thu, May 17, 2001 at 06:36:01AM -0500, Michael Harnois wrote: Are you telling me this error had something to do with optimizations? No. But they can affect compiles in bizarre ways (believe me, in the four years that I've compiled world, I've seen several). If you compile with optimizations, you need to be wary of any failed buildworlds your machine gives. If you are compiling a world that you KNOW works, and optimizations give a problem, then you have a bona fide optimization problem. Sometimes it's correctable, sometimes not. However, in this case, you ran into a bona fide breakage. It was fixed awhile ago, so re-cvsup and re-make world. :) -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make installworld runs out of space on / ...
On Sat, May 12, 2001 at 12:47:30AM -0300, The Hermit Hacker wrote: My / directory, right now, has 12Meg free on it ... if I do a make installworld, it will fail due to no space left on device ... Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on /dev/da1s1a 63503460151240879%1858 1401212% / Has anyone run into this one? Is there a way of fixing it? I can't find anything on / that isn't supposed to be there, or is relatively large ;( rm -rf /var/tmp/install.* -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: LINT and NOTES
On Thu, Apr 19, 2001 at 10:23:02AM -0700, Jens Schweikhardt wrote: I just wanted to close http://www.freebsd.org/cgi/query-pr.cgi?pr=25030 by frobbing NOTES. While 4.2-R LINT has option USER_LDT, NOTES doesn't have it anymore. Can anybody clue me in why it disappeared? Can I simply resurrect it? Because peter eliminated it by making the relevant code mandatory about 2 months ago. Check out the cvs logs for NOTES. BTW, is this the right list to ask such a question? Nope. current@ would be. -- wca PGP signature
Anoncvs support (was Re: NO MORE '-BETA')
On Mon, Mar 19, 2001 at 12:32:13AM -0800, David O'Brien wrote: CVSup's checkout mode has been around longer than FreeBSD has offered anoncvs service. A service which, IMO, is still not very well supported. That's probably one reason why it's hard to get new developers (not everyone feels like syncing the entire repo). But then again, I wonder how much load there is on anoncvs.freebsd.org. Still, would be nice to have more than one anoncvs server, since not everyone's in the U.S.A. -- wca PGP signature
Re: cvs commit: src/lib/libc/gen glob.c
On Fri, Mar 16, 2001 at 11:05:20AM -0800, Jonathan Lemon wrote: Log: Bump MAX_GLOBENTRIES up to 16384, so it is a power of two. Add some comments explaining that this is an arbitrary limit. Why shouldn't this be tunable via sysctl? -- wca PGP signature
Re: cvs commit: src/lib/libc/gen glob.c
On Fri, Mar 16, 2001 at 02:58:31PM -0600, Jonathan Lemon wrote: Uh, because this is user space, not kernel space? Oh yeah, never mind. =) -- wca PGP signature
Re: if_ef module broken in -current
On Thu, Mar 15, 2001 at 12:15:24PM +0200, John Hay wrote: Maybe somebody broke make? The if_ef Makefile is .for and .if statements. You're right. I've backed this out until I can figure out how to properly fix the bug "fixed" in rev 1.27 of parse.c. Thanks. -- wca PGP signature
Re: cvs commit: src/usr.bin/make suff.c
On Wed, Mar 07, 2001 at 04:55:08PM -0800, Thomas Moestl wrote: Log: Fix two bugs in null suffix handling. Both occured only after the suffix list was cleared. Rules with null suffixes would not be rebuilt when the suffixes were added again. Adding null suffix rules would fail when a rule for the same source was declared before the suffix list was cleared. PR: 23328, 24102 Reviewed by:will Approved by:rwatson Thanks. Remember to MFC this after 4.3-RELEASE, unless jkh objects to MFC'ing it now? -- wca PGP signature
Re: make(1) benchmarks [WAS: Re: cvs commit: src/gnu/usr.bin/binutils/ar Makefile src/gnu/usr.bin/binutils/as Makefile.inc0 ...]
On Tue, Mar 06, 2001 at 08:37:35PM +0200, Maxim Sobolev wrote: Any updates? My quick test involving running pkg_version on a system with 92 installed ports, which is very make-intensive operation if ports have origin recorded, as pkg_version(1) runs `make -V' for each port, shown that statically-compiled make is about 15% faster than dynamically-compiled. Sound like a reasonable speed gain for 100k binary size increase. What do people think? Err, sorry, I forgot to do it on the weekend, and have no time right now. Next weekend I will (but someone probably needs to remind me). -- wca PGP signature
Re: cvs commit: src/gnu/usr.bin/binutils/ar Makefile src/gnu/usr.bin/binutils/as Makefile.inc0 src/gnu/usr.bin/binutils/ld Makefile src/gnu/usr.bin/binutils/ranlib Makefile
[ cc's trimmed, moved to -current ] On Wed, Feb 28, 2001 at 09:51:08AM -0700, Warner Losh wrote: So long as it is not forced unconditionally to be static. I agree. b) I've not seen the numbers for this. If it is only 1% faster, it doesn't make sense, even though it sounds good on paper. I will perform careful benchmarks and publish results. Can people wait until that is done before moving forward please? Give me until Saturday. -- wca PGP signature
