Re: Status of file locking over NFS
On Thu, Dec 05, 2002 at 11:59:31PM -0500, Anthony Volodkin wrote: > According to release notes for 4.7, server-side NFS locking is supposed > to be functional. 5.0-DP2's release notes say that client-side as well > as server-side locking is functional. So in theory, I should not be > having the above issues. You need to run rpc.lockd on both sides. Kris msg48201/pgp0.pgp Description: PGP signature
Re: ACPI errors
In message <[EMAIL PROTECTED]>, Hongbo Li wrot e: >I installed FBSD-current on my laptop(IBM Thinkpad >A21m). These were some error messages about ACPI in >dmesg: > >system power profile changed to 'economy' >ACPI-0432: *** Error: Handler for >[EmbeddedControl] returned AE_ERROR >ACPI-1287: *** Error: Method execution failed, >AE_ERROR >ACPI-0432: *** Error: Handler for >[EmbeddedControl] returned AE_ERROR >ACPI-1287: *** Error: Method execution failed, >AE_ERROR Try specifying hw.acpi.ec.event_driven="1" in device.hints . To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors
I installed FBSD-current on my laptop(IBM Thinkpad A21m). These were some error messages about ACPI in dmesg: system power profile changed to 'economy' ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3c575
I installed win2000 and freebsd-current on my box(IBM Thinkpad A21m),using grub as the multibooting manager. The pccard used by the box is a 3CXFE575CT. When I first entered win2000,then rebooted the box to FBSD,the pccard can't work. The error in dmesg was: cbb1: Unknown card voltage cbb1: CardBus card activation failed If I powered on the box and entered to fbsd, the pccard worked well. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Status of file locking over NFS
Hi, Recently, I've been playing with booting a 5.0-CURRENT FreeBSD-sparc64 machine via tftp/nfsroot. The problem that I encountered was that the machine was unable to lock files in it's / nfs-mounted partition, and thus I would miss a large amount of functionality (such as having users :)) divine# passwd Changing local password for root New Password: Retype New Password: passwd: could not lock the passwd file: : Operation not supported My NFS server is a 4.7-RELEASE machine running the following daemons in order to perform NFS: portmap nfsd -u -t -n 4 mountd -r rpc.statd rpc.lockd According to release notes for 4.7, server-side NFS locking is supposed to be functional. 5.0-DP2's release notes say that client-side as well as server-side locking is functional. So in theory, I should not be having the above issues. Does anyone have a working setup with NFS locking tested and working? Can anyone offer any advice on this? Sincerely, Anthony Volodkin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build failure: ata_boot_attach() references ata_raid_attach()
In the last episode (Dec 05), Marcel Moolenaar said: > Gang, > > Anyone seen the following build failure? > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes >-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi >-g -nostdinc -I- -I. -I/nfs/freebsd/5.x/src/sys -I/nfs/freebsd/5.x/src/sys/dev >-I/nfs/freebsd/5.x/src/sys/contrib/dev/acpica >-I/nfs/freebsd/5.x/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h >-fno-common -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata >-ffreestanding -Werror vers.c > linking kernel.debug > ata-all.o: In function `ata_boot_attach': > /nfs/freebsd/5.x/src/sys/dev/ata/ata-all.c:614: undefined reference to >`ata_raid_attach' > *** Error code 1 > > Stop in /usr/obj/nfs/freebsd/5.x/src/sys/ITANIUM. > *** Error code 1 Soeren knows about this; the fix is to wrap the call to ata_raid_attach inside an #ifdef DEV_ATADISK. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
2nd ether device wont config
With DP-2 my 2nd ether won't config ( but I've got other FreeBSDs right in the past with 2 ether cards. the mail gate on another box, relaying this mail has DSL+ether & Internal net+ether) Any know why some devices get conf'd as inet6 + inet & some just as inet6 ? Could that be part of the problem ? If I boot with /etc/rc.conf ifconfig_fxp0="inet 192.168.53.47 netmask 255.255.255.0" # ifconfig_ed1="inet 192.168.53.39 netmask 255.255.255.0" # network_interfaces="auto" # default I see: ifconfig -a fxp0: flags=8843 mtu 1500 inet 192.168.53.47 netmask 0xff00 broadcast 192.168.53.255 inet6 fe80::2a0:c9ff:fe9c:e0a5%fxp0 prefixlen 64 scopeid 0x1 ether 00:a0:c9:9c:e0:a5 media: Ethernet autoselect (10baseT/UTP) status: active lp0: flags=8810 mtu 1500 ed1: flags=8802 mtu 1500 ether 00:00:b4:36:a5:04 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ifconfig ed1 inet 192.168.53.39 ifconfig: ioctl (SIOCAIFADDR): File exists ifconfig ed1 192.168.53.39 ifconfig: ioctl (SIOCAIFADDR): File exists ifconfig lp0 10.0.0.1 10.0.0.2 works ok If I boot with /etc/rc.conf ifconfig_fxp0="inet 192.168.53.47 netmask 255.255.255.0" ifconfig_ed1="inet 192.168.53.39 netmask 255.255.255.0" I see: ifconfig -a fxp0: flags=8843 mtu 1500 inet 192.168.53.47 netmask 0xff00 broadcast 192.168.53.255 inet6 fe80::2a0:c9ff:fe9c:e0a5%fxp0 prefixlen 64 scopeid 0x1 ether 00:a0:c9:9c:e0:a5 media: Ethernet autoselect (10baseT/UTP) status: active lp0: flags=8810 mtu 1500 ed1: flags=8843 mtu 1500 inet6 fe80::200:b4ff:fe36:a504%ed1 prefixlen 64 scopeid 0x3 ether 00:00:b4:36:a5:04 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 If I boot with /etc/rc.conf ifconfig_ed1="inet 192.168.53.47 netmask 255.255.255.0" ifconfig_fxp0="inet 192.168.53.39 netmask 255.255.255.0" I see: ifconfig -a fxp0: flags=8843 mtu 1500 inet 192.168.53.39 netmask 0xff00 broadcast 192.168.53.255 inet6 fe80::2a0:c9ff:fe9c:e0a5%fxp0 prefixlen 64 scopeid 0x1 ether 00:a0:c9:9c:e0:a5 media: Ethernet autoselect (10baseT/UTP) status: active lp0: flags=8810 mtu 1500 ed1: flags=8843 mtu 1500 inet6 fe80::200:b4ff:fe36:a504%ed1 prefixlen 64 scopeid 0x3 ether 00:00:b4:36:a5:04 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 It could be my BIOS isnt right (as the ed1 is an ISA card), dmesg: ed1: at port 0x240-0x25f iomem 0xc-0xc3fff irq 10 on isa0 ed1: address 00:00:b4:36:a5:04, type NE2000 (16 bit) bios: irq 10 allocated to ISA bus, PNP OS was off. tried on, made no difference. But I think even if the BIOS is wrong somewhere, there's perhaps more to fix on FreeBSD side ? Any Ideas ? PS I'ts not actually using 192.168.53 but 192.168.??, but changed for email to protect `the innoocent` :-) Julian Stacey jhs @ berklix.com Computer Systems Engineer, Unix & Net Consultant, Munich. Ihr Rauchen => mein allergischer Kopfschmerz ! Schnupftabak probieren. Munich BSD Conference:http://berklix.org/conf/ Spam phrases triggering deletion: http://berklix.com/jhs/mail/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade of port audio/id3lib - stdc++ wchar support missing
From: "Kris Kennaway" <[EMAIL PROTECTED]> On Fri, Nov 08, 2002 at 09:54:11AM +0100, Jens Rehsack wrote: > David O'Brien wrote: > >On Thu, Nov 07, 2002 at 07:44:43PM +1100, Tim Robbins wrote: > > > >>You could try the patch I've attached: > >> > >>cd /usr/src > >>zcat c++-wchar.diff.gz | patch > >>cd gnu/lib/libstdc++ > >>make > >>make install > > > > > >Can you ask Kris to try this on the ports cluster before we commit it? > >I wonder how many ports this could break. > > Cause I'm the pain in the neck who asks for this - I'm rebuilding all my > ports today to check if it works with this patch (cvsup of /usr/src > yesterday). > Oops, the ports cluster is finally free to test this patch, but now I > can't seem to find it (only mails that refer to it) :-( Can someone > email it to me again? > Attached is the patch Scot c++-wchar.diff.gz Description: GNU Zip compressed data
Re: backgroud fsck is still locking up system (fwd)
Kirk McKusick wrote: > Does the background fsck process continue to run, or does the whole > system come to a halt? If the fsck process continues to run, what > happens when it eventually finishes? Is the system still dead, or > does it come back to life? If the system does not come back to life > can you get me the output of `ps axl'? If not, can you break into > the debugger and get a ps output? (You will need to have the DDB > option specified in your config file). I didn't notice whether it was running or not... of course the only way to tell would be to look at the HDD light. I didn't wait more than several minutes so not sure if it would ever finish. I'll try the other stuff tomorrow as I'm away from the office now. -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Build failure: ata_boot_attach() references ata_raid_attach()
Gang,
Anyone seen the following build failure?
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I/nfs/freebsd/5.x/src/sys -I/nfs/freebsd/5.x/src/sys/dev
-I/nfs/freebsd/5.x/src/sys/contrib/dev/acpica
-I/nfs/freebsd/5.x/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h
-fno-common -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata
-ffreestanding -Werror vers.c
linking kernel.debug
ata-all.o: In function `ata_boot_attach':
/nfs/freebsd/5.x/src/sys/dev/ata/ata-all.c:614: undefined reference to
`ata_raid_attach'
*** Error code 1
Stop in /usr/obj/nfs/freebsd/5.x/src/sys/ITANIUM.
*** Error code 1
\begin{ITANIUM}
machine ia64
cpu ITANIUM
ident ITANIUM
maxusers0
makeoptions DEBUG=-g
options ATA_STATIC_ID
options CD9660
options COMPAT_43
options COMPAT_FREEBSD4
options DDB
options FFS
options INET
options KBD_INSTALL_CDEV
options KTRACE
options MSDOSFS
options NFSCLIENT
options PROCFS
options PSEUDOFS
options ROOTDEVNAME=\"ufs:da0p2\"
options SCSI_DELAY=3000
options SOFTUPDATES
options SYSVMSG
options SYSVSEM
options SYSVSHM
options UFS_DIRHASH
options _KPOSIX_PRIORITY_SCHEDULING
device acpi
device ata
device atapicd
device atapifd
device atkbd
device atkbdc
device bpf
device da
device ether
device fxp
device ichsmb
device isa
device isp
device loop
device lpt
device md
device miibus
device pass
device pci
device pcm
device ppbus
device ppc
device psm
device pty
device random
device sc
device scbus
device sio
device smbus
device vga
\end{ITANIUM}
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
5.0-DP2 disk1.iso cannot boot on my laptop
Hi, I tried 5.0-DP2 on my SHARP PC-MJ100M on which FreeBSD 4.7-STABLE runs well. From sharp's information, it has Intel 440MX chipset, which is detected as 82443MX by FreeBSD and MS Windows2000. When acpi_load is set, this machine stalls after acpi0 is detected. When acpi_load is unset and hint.acpi.0.disable=1, it hangs up after uhci0 is detected. I tried yesterday's snapshot built by myself, and the result is exactly same. And I also tried to upgrade from 4.7-STABLE. Buildworld, buildkernel and installkernel succeeded. But current-kernel cannot boot when /boot/device.hints is created from 4.7-STABLE's kernel configuration. Does this mean that some kind of hardware cannot use 5.0 world? If no, what should I check? Thanks in advance. Here's dmesg.boot of 4.7-STABLE: 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 4.7-STABLE #0: Wed Dec 4 12:45:54 JST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MEBIUS4 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (398.20-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201261056 (196544K bytes) avail memory = 192131072 (187628K bytes) Preloaded elf kernel "kernel" at 0xc0387000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 5 entries at 0xc00fe840 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: (vendor=0x8086, dev=0x7195) at 0.1 irq 11 pci0: (vendor=0x8086, dev=0x7196) at 0.2 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1100-0x110f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: irq 9 at device 7.2 on pci0 uhci0: Could not map ports device_probe_and_attach: uhci0 attach returned 6 chip1: port 0x1400-0x140f at device 7.3 on pci0 pcic0: irq 10 at device 8.0 on pci0 pcic0: PCI Memory allocated: 0x8800 pcic0: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq] pccard0: on pcic0 pci0: at 9.0 rl0: port 0x3e00-0x3eff mem 0xe910-0xe91000ff irq 9 at device 10.0 on pci0 rl0: Ethernet address: 00:40:d0:10:a6:35 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: at iomem 0xc-0xc,0xf1000-0xf1fff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 RTC BIOS diagnostic error 20 ad0: DMA limited to UDMA33, non-ATA66 cable or device ad0: 11513MB [23392/16/63] at ata0-master UDMA33 acd0: CDROM at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s3a And kernel configration, some lines are deleted from GENERIC: machine i386 cpu I386_CPU cpu I486_CPU cpu I586_CPU cpu I686_CPU ident MEBIUS maxusers0 options MATH_EMULATE#Support for x87 emulation options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM
Re: SED regression
On Thu, Dec 05, 2002 at 11:49:01PM +0900, FUJISHIMA Satsuki wrote: > Does anyone see this? > both -CURRENT and -STABLE fail at the same place. > > note: GNU sed 3.02 from ports passed this test. > > /usr/src/tools/regression/usr.bin/sed$ make > Running test G > PASS: Test G detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test P > PASS: Test P detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test psl > PASS: Test psl detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test bcb > PASS: Test bcb detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test y > --- regress.y.out Fri Jun 28 01:07:51 2002 > +++ - Thu Dec 5 23:26:19 2002 > @@ -1 +1 @@ > -fOO > \ No newline at end of file > +fOO > FAIL: Test y failed: regression detected. See above. (in >/usr/src/tools/regression/usr.bin/sed) > *** Error code 1 > > Stop in /usr/src/tools/regression/usr.bin/sed. Our current behaviour is correct according to the relevant standards, but it is not what a user might expect. The problem was that sed previously stored the last newline of a space (pattern/hold), but now it is implicit. This makes it easier to implement many of the commands that were wrong in earlier releases of FreeBSD and were hacked around (see process.c revision 1.4, for example). We do need to restore support for missing newlines at EOF, though, but it's not a very high priority. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: backgroud fsck is still locking up system (fwd)
Does the background fsck process continue to run, or does the whole system come to a halt? If the fsck process continues to run, what happens when it eventually finishes? Is the system still dead, or does it come back to life? If the system does not come back to life can you get me the output of `ps axl'? If not, can you break into the debugger and get a ps output? (You will need to have the DDB option specified in your config file). Kirk McKusick =-=-=-=-=-= From: Archie Cobbs <[EMAIL PROTECTED]> Subject: Re: backgroud fsck is still locking up system (fwd) In-Reply-To: <[EMAIL PROTECTED]> To: Kirk McKusick <[EMAIL PROTECTED]> Date: Thu, 5 Dec 2002 16:22:20 -0800 (PST) CC: Archie Cobbs <[EMAIL PROTECTED]>, Robert Watson <[EMAIL PROTECTED]>, [EMAIL PROTECTED] X-ASK-Info: Confirmed by User Kirk McKusick wrote: > Just rebuilt -current this morning. Background fsck is still > causing a "soft lockup". I thought the conclusion was we were > going to disable it for 5.0. > > What do you mean by background fsck causing a "soft lockup"? > Is it failing? Is it deadlocking the system? Do you have a > specific test case that shows the problem? Needless to say > it is working fine on my system and on my regression tests. > The only problem that I am having with 5.0 as of last night > is getting login to work on my console. What happens is that at first I can login, but the system seems slow. I then got as far as running 'top' but it never refreshed its display and subsequently all keystrokes were ignored. Changing virtual terminals still works OK, but they are effectively dead too. I'm imagining processes getting stuck on some lock one by one. Top did get as far as showing the background fsck process, which had a priority of -6 or something. The previous time it didn't even spit out a login prompt, but that may just be due to experimental noise. For me, it appears easy to reproduce... 1. Boot -current system 2. Pull the power cable out 3. Put the power cable back in 4. Let the box boot; it notes backgroud fsck 5. Login and try to do something I can give you more details about my system separately if you like. Thanks, -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: backgroud fsck is still locking up system (fwd)
Kirk McKusick wrote: > Just rebuilt -current this morning. Background fsck is still > causing a "soft lockup". I thought the conclusion was we were > going to disable it for 5.0. > > What do you mean by background fsck causing a "soft lockup"? > Is it failing? Is it deadlocking the system? Do you have a > specific test case that shows the problem? Needless to say > it is working fine on my system and on my regression tests. > The only problem that I am having with 5.0 as of last night > is getting login to work on my console. What happens is that at first I can login, but the system seems slow. I then got as far as running 'top' but it never refreshed its display and subsequently all keystrokes were ignored. Changing virtual terminals still works OK, but they are effectively dead too. I'm imagining processes getting stuck on some lock one by one. Top did get as far as showing the background fsck process, which had a priority of -6 or something. The previous time it didn't even spit out a login prompt, but that may just be due to experimental noise. For me, it appears easy to reproduce... 1. Boot -current system 2. Pull the power cable out 3. Put the power cable back in 4. Let the box boot; it notes backgroud fsck 5. Login and try to do something I can give you more details about my system separately if you like. Thanks, -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Creating bootsector file for W2k boot menu
[EMAIL PROTECTED] wrote, On 12/05/02 17:06: On 2002-12-05 00:22, Tomi Vainio - Sun Finland - wrote: > I've used Windows NT boot menu for years to boot FreeBSD from the > second disk on my machines. I've used bootpart DOS program to do this > but now I can't find correct way to do FreeBSD boot block for it. > Earlier there was a diskid definition in some Makefile to change. How > should I do this now? ... # dd if=/dev/ad0s1 of=/root/bsdboot.bin bs=512 count=1 Then copy bsdboot.bin to a Windows partition, say in C:\BSDBOOT.BIN and add the following to the C:\BOOT.INI file: C:\BSDBOOT.BIN="FreeBSD on ad0s1" That should be all... Just use /boot/boot1 ( NOT /boot/boot0 !) instead of extracting this file by dd ... Dan -- Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206 root of FIONet, KolejNET, webmaster of www.freebsd.cz AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: backgroud fsck is still locking up system (fwd)
Date: Thu, 5 Dec 2002 15:22:27 -0800 (PST) From: Archie Cobbs <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: backgroud fsck is still locking up system Just rebuilt -current this morning. Background fsck is still causing a "soft lockup". I thought the conclusion was we were going to disable it for 5.0. Not trying to rush anyone, just pointing out that this still needs to be done.. -Archie __ Archie Cobbs*Packet Design*http://www.packetdesign.com What do you mean by background fsck causing a "soft lockup"? Is it failing? Is it deadlocking the system? Do you have a specific test case that shows the problem? Needless to say it is working fine on my system and on my regression tests. The only problem that I am having with 5.0 as of last night is getting login to work on my console. Kirk McKusick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
On Fri, 2002-12-06 at 10:04, Darryl Okahata wrote: > > I have motherboards where this fix doesn't work :( > > You have tried -current, right? (I assume that you have, but I > just want to make sure.) Cliff mentioned that -current works for him, > but 4.7 doesn't. Hmm, no.. It wasn't really an option at the time.. Now I've replaced the boards with other ones which work fine. > I haven't searched the archives very hard, but I could only find a > reference to the "VIA patch" being applied to -current (Soren's post > of around December 26, 2001). I haven't tried rummaging through the CVS > logs. I've always assumed that the VIA patch was MFC'd, but I can't any > verification of this. It was MFC'd - I ended up hand MFC'ing it to try out, but it wasn't successful :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems building GENERIC with DP2 on ThinkPad 600E
> Date: Thu, 5 Dec 2002 10:44:07 -0800 (PST) > From: Nate Lawson <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > echo hint.acpi.0.disabled=\"1\" >> /boot/device.hints > See if this changes anything. Sigh. Some days my brain actually works...honest! It is clearly acpi that is crashing my system. I just realized that GENERIC contains only a kernel and no modules including acpi.ko, so that GENERIC never TRYS to use ACPI. It's not an compiler issue. Guess I'll try using apm until such time as I can cvsup and grab a copy of the latest ACPI code. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA/ATAPI related panic
On Thu, Dec 05, 2002 at 10:52:11AM -0800, Nate Lawson wrote: > Do you also use ahc(4) or ahd(4)? A bug was recently fixed where it would > corrupt timeout handlers. If not, please build "options DDB" into your > kernel and report what it says when you type "trace" after the panic. At the time of the problems, I was using the GENERIC kernel with ahc and ahd compiled in. I have since used todays snapshot, recompiled with minimal drivers, and I've not had another panic. What I have found, though, is that when I tell my BIOS I've got drives on the secondary controller (either Auto or ATAPI device) I get a few of the timeout/resetting messages. Since there's no point in the BIOS knowing about them, I've disabled them - FreeBSD now runs perectly. The only other panic I've seen was a wakeup from acpi sleep mode 2, that was fixed by the patch committed yesterday, and although mode 4 doesn't work, I realise that the ACPI project has a lot of new code combined with buggy hardware to figure out, and it's an amazing implementation of ACPI FreeBSD is getting. -- Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote: > > Many (most? all?) KT133A-based motherboards have a known issue with > > the PCI bus that often results in an IDE transfer problem. However, > > this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe > > earlier). [ Hmmm. You're probably seeing another problem with 4.7. ] > > I have motherboards where this fix doesn't work :( You have tried -current, right? (I assume that you have, but I just want to make sure.) Cliff mentioned that -current works for him, but 4.7 doesn't. I haven't searched the archives very hard, but I could only find a reference to the "VIA patch" being applied to -current (Soren's post of around December 26, 2001). I haven't tried rummaging through the CVS logs. I've always assumed that the VIA patch was MFC'd, but I can't any verification of this. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Financial freedom in 24 days or less
Hello, Would you like to make $100,000 a year online? If so, then this is your magical email to the kingdom of financial freedom. Think about how life would be WITHOUT an alarm clock waking you up every morning. Or sitting in traffic all morning. Are you frustrated that you belong to the corporate world? IMAGINE your daily commute taking 20 seconds as you walk to your computer! Is this just a dream? Many people think so but they are ABSOLUTELY WRONG. Financial freedom is given to people who jump at the opportunity, not to those who hesitate. 2 years ago I was just like you, I was making $12 an hour working my butt off struggling to pay my bills. One day, a friend of mine introduced me to the GREATEST business ever created online. Within 6 months of working just an hour a day, I was able to quit my full time job and leave the corporate world FOREVER. Now I would like to share this opportunity with you. It is MY DUTY to help you get to the places you dream about, and I'm about to do just that. Normally, there is a $29.99 charge associated with joining this business. But for the next 48 hours, you can sign up, ABSOLUTELY FREE. Even if this isn't the opportunity of a lifetime, how can you afford to pass up this chance? You have nothing to lose! No credit card required, Nothing! All you have to do is click on the link below to learn more about this AMAZING business. http://www.product-galore.com/affiliate.htm Thank you and have a great day! Dan Meadows Jr. 0863al5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
backgroud fsck is still locking up system
Just rebuilt -current this morning. Background fsck is still causing a "soft lockup". I thought the conclusion was we were going to disable it for 5.0. Not trying to rush anyone, just pointing out that this still needs to be done.. -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade of port audio/id3lib - stdc++ wchar support missing
Kris Kennaway wrote: On Fri, Nov 08, 2002 at 09:54:11AM +0100, Jens Rehsack wrote: David O'Brien wrote: On Thu, Nov 07, 2002 at 07:44:43PM +1100, Tim Robbins wrote: You could try the patch I've attached: cd /usr/src zcat c++-wchar.diff.gz | patch cd gnu/lib/libstdc++ make make install Can you ask Kris to try this on the ports cluster before we commit it? I wonder how many ports this could break. Cause I'm the pain in the neck who asks for this - I'm rebuilding all my ports today to check if it works with this patch (cvsup of /usr/src yesterday). Hmm... at some point in time it may perhaps just make perfect sense to replace the libstdc++ by the STLport library as the standard C++ library? The gnu libstdc++ is really somehoe hopeless. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: NVidia binary driver on 5.0-DP2
w00t, thanks Cliff :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Cliff L. Biffle Sent: donderdag 5 december 2002 21:21 To: [EMAIL PROTECTED] Subject: NVidia binary driver on 5.0-DP2 Hey, for the curious... We've gotten NVidia's binary drivers for the GeForce cards up and running on 5.0-DP2. Once five or so lines in nv-freebsd.h that disabled support on 5.0 were removed...it works beautifully. :-) Patch follows. This is Chris Lee's work, not mine, but he's not on the list, since he's still having trouble admitting to running anything other than Gentoo. :-) (Yes, 5.0-DP2 is bringing in converts from the cold left and right here in Tempe!) -Cliff L. Biffle --- src/nv-freebsd.h Wed Oct 30 07:30:58 2002 +++ src/nv-freebsd.hThu Dec 5 05:09:33 2002 @@ -27,12 +27,6 @@ * active development and also unsupported. */ -#if __FreeBSD_version >= 50 -#error This driver does not support FreeBSD 5.0/-CURRENT! -#elif __FreeBSD_version < 47 -#error This driver requires FreeBSD 4.7 or later! -#endif - #include #include #include 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: USB issues with Apollo KT133A mobo
On Fri, 2002-12-06 at 02:48, Darryl Okahata wrote: > > a rock under 5.0-DP2, which is why I'm sticking with it despite other > > potential bugs. I can burn CDs now! > > Many (most? all?) KT133A-based motherboards have a known issue with > the PCI bus that often results in an IDE transfer problem. However, > this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe > earlier). [ Hmmm. You're probably seeing another problem with 4.7. ] I have motherboards where this fix doesn't work :( According to the board vendor you're supposed to use the latest Via drivers (ahahaha..) Tinkering with various PCI and AGP options (eg turning features off) makes it more stable, but they still hang :( I have other KT133 based boards which work flawlessly because the BIOS does the fix. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade of port audio/id3lib - stdc++ wchar support missing
On Fri, Nov 08, 2002 at 09:54:11AM +0100, Jens Rehsack wrote: > David O'Brien wrote: > >On Thu, Nov 07, 2002 at 07:44:43PM +1100, Tim Robbins wrote: > > > >>You could try the patch I've attached: > >> > >>cd /usr/src > >>zcat c++-wchar.diff.gz | patch > >>cd gnu/lib/libstdc++ > >>make > >>make install > > > > > >Can you ask Kris to try this on the ports cluster before we commit it? > >I wonder how many ports this could break. > > Cause I'm the pain in the neck who asks for this - I'm rebuilding all my > ports today to check if it works with this patch (cvsup of /usr/src > yesterday). Oops, the ports cluster is finally free to test this patch, but now I can't seem to find it (only mails that refer to it) :-( Can someone email it to me again? Kris msg48177/pgp0.pgp Description: PGP signature
panic: ffs_vfree: range: dev = ad4s1c, ino = -1690809896, fs = /mnt2
I got this on a recent -current (kernel built Dec 1). The filesystem
was under heavy disk load at the time (cvsup of CVS repo, make
installworld, and cvs update of the src tree from a sparc64 NFS
client). When it rebooted there was minor FS corruption (a few files
lost/truncated).
Kris
panic: bremfree: bp 0xce65cf00 not locked
panic messages:
---
panic: ffs_vfree: range: dev = ad4s1c, ino = -1690809896, fs = /mnt2
syncing disks, buffers remaining... panic: bremfree: bp 0xce65cf00 not locked
Uptime: 3d12h58m21s
Dumping 511 MB
ata0: resetting devices ..
done
16 32[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] 48
64[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] 80 96 112
128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448
464 480 496
---
#0 doadump () at ../../../kern/kern_shutdown.c:232
232 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:232
#1 0xc01e10d5 in boot (howto=260) at ../../../kern/kern_shutdown.c:364
#2 0xc01e1323 in panic () at ../../../kern/kern_shutdown.c:517
#3 0xc0221ad7 in bremfree (bp=0xce65cf00) at ../../../kern/vfs_bio.c:632
#4 0xc02244d0 in getblk (vp=0xc4156000, blkno=352, size=16384, slpflag=0,
slptimeo=0) at ../../../kern/vfs_bio.c:2344
#5 0xc0221c0a in breadn (vp=0xc4156000, blkno=0, size=0, rablkno=0x0,
rabsize=0x0, cnt=0, cred=0x0, bpp=0x0) at ../../../kern/vfs_bio.c:690
#6 0xc0221bbc in bread (vp=0x0, blkno=0, size=0, cred=0x0, bpp=0x0)
at ../../../kern/vfs_bio.c:672
#7 0xc02b0878 in ffs_update (vp=0xc44fa5dc, waitfor=0)
at ../../../ufs/ffs/ffs_inode.c:102
#8 0xc02c49df in ffs_fsync (ap=0xdc06a864) at ../../../ufs/ffs/ffs_vnops.c:315
#9 0xc02c3b4e in ffs_sync (mp=0xc4032600, waitfor=2, cred=0xc150af00,
td=0xc038ac80) at vnode_if.h:612
#10 0xc0235a78 in sync (td=0xc038ac80, uap=0x0)
at ../../../kern/vfs_syscalls.c:138
#11 0xc01e0d1c in boot (howto=256) at ../../../kern/kern_shutdown.c:273
#12 0xc01e1323 in panic () at ../../../kern/kern_shutdown.c:517
#13 0xc02acc0b in ffs_freefile (fs=0xc4304800, devvp=0xc44fbce4,
ino=2604157400, mode=16832) at ../../../ufs/ffs/ffs_alloc.c:1899
#14 0xc02bd124 in handle_workitem_freefile (freefile=0xc7e53120)
at ../../../ufs/ffs/ffs_softdep.c:3389
#15 0xc02bb48b in softdep_freefile (pvp=0x0, ino=2604157400, mode=0)
at ../../../ufs/ffs/ffs_softdep.c:2338
#16 0xc02aca3e in ffs_vfree (pvp=0x0, ino=0, mode=16832)
at ../../../ufs/ffs/ffs_alloc.c:1864
#17 0xc02aa604 in ffs_valloc (pvp=0xc7b0ea8c, mode=16832, cred=0xc710fe80,
vpp=0xdc06aa54) at ../../../ufs/ffs/ffs_alloc.c:864
#18 0xc02d0028 in ufs_mkdir (ap=0xdc06abbc)
at ../../../ufs/ufs/ufs_vnops.c:1375
#19 0xc02d18e8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2796
#20 0xc023a866 in kern_mkdir (td=0xc7b9fd20, path=---Can't read userspace from dump,
or kernel process---
) at vnode_if.h:757
#21 0xc023a629 in mkdir (td=0x0, uap=0x0) at ../../../kern/vfs_syscalls.c:2882
#22 0xc0325dee in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 134594432, tf_ebp =
-1077939272, tf_isp = -603542156, tf_ebx = 134539156, tf_edx = 134536583, tf_ecx =
-1077939536, tf_eax = 136, tf_trapno = 0, tf_err = 2, tf_eip = 671871219, tf_cs = 31,
tf_eflags = 514, tf_esp = -1077939412, tf_ss = 47})
at ../../../i386/i386/trap.c:1033
#23 0xc031602d in Xint0x80_syscall () at {standard input}:140
---Can't read userspace from dump, or kernel process---
msg48176/pgp0.pgp
Description: PGP signature
Re: dump(8) + UFS2
Hello :-) I just (20:00 CET) did a new 'make world' on my current-slice and I'm happy to report that dump(8) is working perfectly now, even on UFS2. It's performing 'snapshots' on mounted filesystems for backup and additionally seems to be somewhat (at least) faster... Great Job! Thanks a lot! -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Creating bootsector file for W2k boot menu
Giorgos Keramidas writes: > > I have FreeBSD installed on two primary slices of my machine, as you > can see from the df(1) output below. I can boot FreeBSD fine, if I > copy the boot record of the slice my root partition lives in: > > # df / > Filesystem 1K-blocksUsedAvail Capacity Mounted on > /dev/ad0s1a498078 85920 37231219%/ > > # dd if=/dev/ad0s1 of=/root/bsdboot.bin bs=512 count=1 > > Then copy bsdboot.bin to a Windows partition, say in C:\BSDBOOT.BIN > and add the following to the C:\BOOT.INI file: > > C:\BSDBOOT.BIN="FreeBSD on ad0s1" > > That should be all... > Hi, Your idea is correct but this gives just "Boot error". I need to make a boot sector which contains information that I'm booting from third physical disk. I think normally there is a value of 0x80 which means first disk. Old Makefile option changed just this value. Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SED regression
* De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2002-12-05 ] [ Subjecte: Re: SED regression ] > But I'm pretty confident that what we do now is correct, and it seems to > be in agreement with POSIX.1-2001, which says: Feel free to regenerate regress.y.out or whatnot then... Really should add a "regenerate" thing to the regression stuff some time, wouldn't be hard... Thanks, juli. -- Juli Mallett <[EMAIL PROTECTED]> OpenDarwin, Mono, FreeBSD Developer. ircd-hybrid Developer, EFnet addict. FreeBSD on MIPS-Anything on FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NVidia binary driver on 5.0-DP2
Hey, for the curious... We've gotten NVidia's binary drivers for the GeForce cards up and running on 5.0-DP2. Once five or so lines in nv-freebsd.h that disabled support on 5.0 were removed...it works beautifully. :-) Patch follows. This is Chris Lee's work, not mine, but he's not on the list, since he's still having trouble admitting to running anything other than Gentoo. :-) (Yes, 5.0-DP2 is bringing in converts from the cold left and right here in Tempe!) -Cliff L. Biffle --- src/nv-freebsd.h Wed Oct 30 07:30:58 2002 +++ src/nv-freebsd.hThu Dec 5 05:09:33 2002 @@ -27,12 +27,6 @@ * active development and also unsupported. */ -#if __FreeBSD_version >= 50 -#error This driver does not support FreeBSD 5.0/-CURRENT! -#elif __FreeBSD_version < 47 -#error This driver requires FreeBSD 4.7 or later! -#endif - #include #include #include To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 won't stay powered off
On Thu, Dec 05, 2002 at 10:37:49AM -0800, Nate Lawson wrote: > On Thu, 5 Dec 2002, Mathew Kanner wrote: > > I've noticed some odd behavior when I installed DP2 on my > > machine last night. When I "shutdown -p now", the machine will turn > > itself back-on in about twenty minutes. This would be nice feature if > > I had asked for it. > > Can everyone with the auto power on problem report the output of "sysctl > hw.acpi"? > > -Nate > For me it was every five minutes but I'm in the process of updating to see if that solves the issue(given the changes in the last few days) hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3382 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 95 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 Machine is an IBM Thinkpad A20m --kit -- whois -h whois.gandi.net KM78-GANDI To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup Delete failures
Michael Sierchio writes: | Forrest Aldrich wrote: | > FYI, over the last few days, I've been seeing this error while doing a | > CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: | > | > Delete src/contrib/gcc/INSTALL | > Cannot delete "/usr/local/src/freebsd/5.0/src/contrib/gcc/INSTALL": | > Directory not empty The problem seems to be an INSTALL directory now in HEAD and a file in Attic/INSTALL. cvs co of -stable is also barfing on this conflict of the old file and new directory.o U src/contrib/gcc/xcoffout.c U src/contrib/gcc/xcoffout.h cvs [checkout aborted]: could not chdir to src/contrib/gcc/INSTALL: Not a directory a21p% Removing the INSTALL directory in my local repo fixes the issue for -stable. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 won't stay powered off
On Dec 05, Nate Lawson wrote: > On Thu, 5 Dec 2002, Mathew Kanner wrote: > > I've noticed some odd behavior when I installed DP2 on my > > machine last night. When I "shutdown -p now", the machine will turn > > itself back-on in about twenty minutes. This would be nice feature if > > I had asked for it. > > Can everyone with the auto power on problem report the output of "sysctl > hw.acpi"? hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 2 hw.acpi.cpu.current_speed: 2 hw.acpi.cpu.performance_speed: 2 hw.acpi.cpu.economy_speed: 1 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3247 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3482 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3482 hw.acpi.thermal.tz0._ACx: 3482 -1 -1 -1 -1 -1 -1 -1 -1 -1 --Mat -- Mr. T (On Late Night with Conan O'Brian): "Fools will come to my house to ask me not to pity them. But I won't be home, and it will be raining, so I will continue to pity them!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA/ATAPI related panic
On Thu, 5 Dec 2002, Bruce Cran wrote: > On Tue, Dec 03, 2002 at 10:40:03AM -0800, Nate Lawson wrote: > > On Tue, 3 Dec 2002, Bruce Cran wrote: > > > I've had a problem with my DVD and CDRW drives under FreeBSD from 4.5 > > > onwards. In released prior to 4.7 I used to get panics, I think when the >system had heavy I/O loads, such as when building world - I thought this may have >been due to the VIA controller. I installed DP2, and on one of the > > > boots, got: > > > > > > acd0: REQUEST_SENSE command timeout - resetting > > > ata1: resetting devices > > > > > > Fatal trap 12: page fault while in kernel mode > > > fault trap address = 0x0 > > > fault code = Supervisor read, page not present > > > instruction pointer = 0x8:0xc0151ca2 > > > stack pointer = 0x10:0xd68e3c5c > > > frame pointer = 0x10:0xd68e3c70 > > > code segment = base 0x0, limit 0xf, type = 0x16 > > > = DPL 0, pres 1, def32 l, gran 1 > > > > > > processor eflags = interrupt enable resume, IOPL=0 > > > current process = 13 (swi6:clock) > > > trap number = 12 > > > panic : page fault > > > > This is a null ptr deref, most likely in the kern proc that calls > > the timeout handlers (since curproc is clock int.) No idea what would > > cause this. > > Is there anything I could do to help diagnose the problem? I don't > think it's a problem with my hardware because both Linux and Windows run > perfectly with no errors. I'd really love to make FreeBSD 5 my main > OS, but if it's going to be like 4.5 and 4.6 where I kept getting > panics, reboots and error messages, I'm not going to be able to. Do you also use ahc(4) or ahd(4)? A bug was recently fixed where it would corrupt timeout handlers. If not, please build "options DDB" into your kernel and report what it says when you type "trace" after the panic. As far as your OS choice, we're doing our best. 5-CURRENT has been very solid for me on a few boxes and unstable on others. There are a lot of edge cases in pc hw and we have a lot of new code to deal with. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup Delete failures
On Thu, 05 Dec 2002 13:03:09 -0500 Forrest Aldrich <[EMAIL PROTECTED]> wrote: > FYI, over the last few days, I've been seeing this error while doing a > > CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: > > Delete src/contrib/gcc/INSTALL > Cannot delete "/usr/local/src/freebsd/5.0/src/contrib/gcc/INSTALL": > Directory not empty > > If I manually delete that directory, it gets recreated, and then this > error pops back on the next run. Permissions on the directories > aren't the issue, that I can tell -- nothing really changes manually > here in the src directories. FWIW, this is a "me too." I cvsup-ed the sources yesterday and got complaints about the same directory. I manually deleted it and re-cvsup-ed and the directory and all its contents were restored as before. Run again and the complaints still happened. I saw a couple of other reports of this behavior as well so I think it's unlikely that this is local to your setup or that we all just happened to make the same *exact* mistake somewhere along the line. Just for fun, I ran 'make buildworld' anyway and everything went without a hitch, so this anomoly doesn't seem to affect building/installing the system. -Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems building GENERIC with DP2 on ThinkPad 600E
On Thu, 5 Dec 2002, Kevin Oberman wrote: > When boot the new kernel it seems to be OK for a few seconds, but any > attempt to login produces a crash: > Fatal trap 12: page fault in kernel mode > fault virtual address = 0x3f6 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc067ffc0 > stack pointer = 0x10:0xcsc13bec > frame pointer = 0x10:0xcsc13bec > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 22 (acpi_thermal) > kernel: type 12 trap code=0 > stopped at AcpiNsMapHandleToNode+0x20: cmpb$0xa,0(%edx) > db> > > Shortly prior to the crash, I get: > ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR > ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR > ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR > ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR echo hint.acpi.0.disabled=\"1\" >> /boot/device.hints See if this changes anything. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 won't stay powered off
Here's mine. I purposely disabled the lid_switch_state and tried disabling the power_button_state thinking that might solve the problem but to no avail. hw.acpi.power_button_state: NONE hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3182 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 98 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 * Nate Lawson ([EMAIL PROTECTED]) [021205 10:40]: > On Thu, 5 Dec 2002, Mathew Kanner wrote: > > I've noticed some odd behavior when I installed DP2 on my > > machine last night. When I "shutdown -p now", the machine will turn > > itself back-on in about twenty minutes. This would be nice feature if > > I had asked for it. > > Can everyone with the auto power on problem report the output of "sysctl > hw.acpi"? > > -Nate > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- Greg Rumple [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 won't stay powered off
On Thu, 5 Dec 2002, Mathew Kanner wrote: > I've noticed some odd behavior when I installed DP2 on my > machine last night. When I "shutdown -p now", the machine will turn > itself back-on in about twenty minutes. This would be nice feature if > I had asked for it. Can everyone with the auto power on problem report the output of "sysctl hw.acpi"? -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unable to use boot0cfg
David Wolfskill writes: | 0:ad(0,1,a)/boot/loader ... or put that in /boot.config on the / that boot0 defaults to boot. a21p% cat /boot.config 0:ad(0,2,a)/boot/loader a21p% ls -l /boot.co* Then just change it. It does mean that in my setup if I'm running -current I have to edit /stable/boot.config since boot0 always boots my -stable area. | (to boot from slice 1) -- ref. "man boot". Your welcome. I submitted that man page update to ru after finding that secret feature in the source code. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup Delete failures
Forrest Aldrich wrote: FYI, over the last few days, I've been seeing this error while doing a CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: Delete src/contrib/gcc/INSTALL Cannot delete "/usr/local/src/freebsd/5.0/src/contrib/gcc/INSTALL": Directory not empty If I manually delete that directory, it gets recreated, and then this error pops back on the next run. Permissions on the directories aren't the issue, that I can tell -- nothing really changes manually here in the src directories. Not permissions, but likely it's the flags (schg on some files). See if chflags -R noschg /usr/local/src/freebsd/5.0 does the trick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CVSup Delete failures
FYI, over the last few days, I've been seeing this error while doing a CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: Delete src/contrib/gcc/INSTALL Cannot delete "/usr/local/src/freebsd/5.0/src/contrib/gcc/INSTALL": Directory not empty If I manually delete that directory, it gets recreated, and then this error pops back on the next run. Permissions on the directories aren't the issue, that I can tell -- nothing really changes manually here in the src directories. F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA/ATAPI related panic
On Tue, Dec 03, 2002 at 10:40:03AM -0800, Nate Lawson wrote: > On Tue, 3 Dec 2002, Bruce Cran wrote: > > I've had a problem with my DVD and CDRW drives under FreeBSD from 4.5 > > onwards. In released prior to 4.7 I used to get panics, I think when the system >had heavy I/O loads, such as when building world - I thought this may have been due >to the VIA controller. I installed DP2, and on one of the > > boots, got: > > > > acd0: REQUEST_SENSE command timeout - resetting > > ata1: resetting devices > > > > Fatal trap 12: page fault while in kernel mode > > fault trap address = 0x0 > > fault code = Supervisor read, page not present > > instruction pointer = 0x8:0xc0151ca2 > > stack pointer = 0x10:0xd68e3c5c > > frame pointer = 0x10:0xd68e3c70 > > code segment = base 0x0, limit 0xf, type = 0x16 > > = DPL 0, pres 1, def32 l, gran 1 > > > > processor eflags = interrupt enable resume, IOPL=0 > > current process = 13 (swi6:clock) > > trap number = 12 > > panic : page fault > > This is a null ptr deref, most likely in the kern proc that calls > the timeout handlers (since curproc is clock int.) No idea what would > cause this. Is there anything I could do to help diagnose the problem? I don't think it's a problem with my hardware because both Linux and Windows run perfectly with no errors. I'd really love to make FreeBSD 5 my main OS, but if it's going to be like 4.5 and 4.6 where I kept getting panics, reboots and error messages, I'm not going to be able to. > > > Another possible bug I've found is in df. I compiled a kernel then, > > before overwriting the old backup, I tried running cp -ivR kernel.old > > kernel.old.orig, forgetting that /boot wouldn't have enough free space. > > When I next ran 'df -h' /boot was reporting -6MB free. I deleted > > /boot/kernel.old.orig and the free space was correctly reported again, > > but is this a bug in df? My filesytem is UFS1. > > No, this is correct since there is space reserved for root (see tunefs > minfree) Thanks, that does make sense, since I've often seen messages saying space has been reserved for root's use. I didn't expect it to show up as negative free space, though - it's a nice feature. > > > how would I go about throttling it? Are there any IOCTLs, or is this > > feature only for laptops where they automatically get throttled when > > running on batteries? I know it probably doesn't make sense on a > > desktop computer, but I'm interested - ACPI support seems brilliant, and > > although hibernation doesn't seem to work, all the other features work > > perfectly. > > man acpi, see also sysctl hw.acpi > I've had a good look through acpi, acpiconf and hw.acpi, but haven't found any method to throttle the CPU manually, or automatically on a desktop PC. This is because the sysctl for the current speed is read-only, and the only writeable sysctl set the speeds for full-speed and economy modes, with no apparent way to switch between them. Does FreeBSD handle throttling automatically depending on load, or is there some user-space program which I can use? -- Bruce Cran To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem [gcc-3.2.1 commit problem?]
On Fri, Dec 06, 2002 at 01:18:57AM +0800, leafy wrote: > On Thu, Dec 05, 2002 at 07:13:23PM +0200, Giorgos Keramidas wrote: > > > Been there, done that - several times :) > > > > Hmmm, try a different cvsup server then. I just updated from > > cvsup.gr.freebsd.org and all seems fine. The files are still there, > > but nothing breaks... > Connected to cvsup.gr.freebsd.org > Updating collection src-all/cvs > Delete src/contrib/gcc/INSTALL > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > You will get it eventually :) > cvsup3.freebsd.org and cvsup7.freebsd.org also give the the error message. However, Giorgos is right in that "nothing breaks" because of this problem. cvsup complete and I suspect "make buildworld" will succeed because the contents of src/contrib/gcc/INSTALL are not used. I also suspect that David accidentally committed the html files. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems building GENERIC with DP2 on ThinkPad 600E
I have been trying to install DP2 on my old ThinkPad 600E. It almost works, but I can't build a new kernel. I'd like to build a custom kernel, but don't seem to be able to do so. The system has a 366 Mhz PII, and the kernel is compiled with -mcpu=pentiumpro. I have no /etc/make.conf at this time. Disturbingly, if I try to boot a kernel built with only "cpu I686_CPU", I get a message at boot time telling me that the system is not a 686. ??? When it boots GENERIC, it claims: CPU: Pentium II/Pentium II Xeon/Celeron (363.96-MHz 686-class CPU) I have always built FreeBSD on this system for a 686. When boot the new kernel it seems to be OK for a few seconds, but any attempt to login produces a crash: Fatal trap 12: page fault in kernel mode fault virtual address = 0x3f6 fault code = supervisor read, page not present instruction pointer = 0x8:0xc067ffc0 stack pointer = 0x10:0xcsc13bec frame pointer = 0x10:0xcsc13bec code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 22 (acpi_thermal) kernel: type 12 trap code=0 stopped at AcpiNsMapHandleToNode+0x20: cmpb$0xa,0(%edx) db> Shortly prior to the crash, I get: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR At various points in the boot I get the following (from the top): [...] Timecounter "ACPI_safe" frequency 3579545 Hz ACPI-0351: *** Error: Could not install PciConfig handler for PCI0, AE_ALREADY_EXISTS [...] ad0: 11509MB
Re: DP-2 and Nvidia Geforce 4
> > Ok, here is the error message. The server never even gets past go: > > "Symbol vgaHWUnmapMem from module > /usr/X11R6/lib/modules/drivers/nv_drv.o is unresolved!" > Fatal server error: > Caught signal 11. Server aborting. > > Rob. > > -- I got rid of the first error message by loading "vgahw" module. Now I just get Signal 11. I also went back and recompiled my X11 with no optimizations except -pipe -o, getting rid of the -march=athlon-xp, but no joy. Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On Thu, Dec 05, 2002 at 07:13:23PM +0200, Giorgos Keramidas wrote: > > Been there, done that - several times :) > > Hmmm, try a different cvsup server then. I just updated from > cvsup.gr.freebsd.org and all seems fine. The files are still there, > but nothing breaks... Connected to cvsup.gr.freebsd.org Updating collection src-all/cvs Delete src/contrib/gcc/INSTALL Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty You will get it eventually :) JY To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On 2002-12-06 00:14, leafy <[EMAIL PROTECTED]> wrote: > On Thu, Dec 05, 2002 at 05:22:50PM +0200, Giorgos Keramidas wrote: > > Remove your src/contrib/gcc/INSTALL directory and try cvsup'ing again. > > The files in that directory were imported yesterday, and I think that > > David O'Brien didn't mean to import them at all: > > Been there, done that - several times :) Hmmm, try a different cvsup server then. I just updated from cvsup.gr.freebsd.org and all seems fine. The files are still there, but nothing breaks... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
DP2 won't stay powered off
Hello, I've noticed some odd behavior when I installed DP2 on my machine last night. When I "shutdown -p now", the machine will turn itself back-on in about twenty minutes. This would be nice feature if I had asked for it. I've never seen this before with -current (which I haven't visited in about six months) or -stable with apm. The machine is an abit bp6, dual celeron. I've never updated the bios, and I assume this is an acpi problem. -current isn't booted at the moment but more specific information can be provided. Thanks, --Mat -- Brain: Moo. We are a cow. Take us to China. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
"Cliff L. Biffle" <[EMAIL PROTECTED]> wrote: > Could be. The ATA controller was also flaking out under 4.7, but is solid as > a rock under 5.0-DP2, which is why I'm sticking with it despite other > potential bugs. I can burn CDs now! Many (most? all?) KT133A-based motherboards have a known issue with the PCI bus that often results in an IDE transfer problem. However, this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe earlier). [ Hmmm. You're probably seeing another problem with 4.7. ] > In the discussion link you sent me, they discuss the controller disabling the > port due to excessive current draw...would it re-enable the port when I > simply un/replug the mouse? Normally I'd expect that to require a reboot. > (The mouse does come back when I remove it and reinsert it, and generally X > doesn't even notice.) I don't know how FreeBSD handles it. Under Windows, a dialog box pops up when an overcurrent situation occurs, and the box contains a button that'll reset and re-enable the bus. > The KT133 discussion suggests it's a hardware problem, which wouldn't surprise > me...this particular mobo is a very early Athlon board, and the chipset may > be buggy. Motherboards using the VIA KT133A chipset generally do not have a good reputation. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On Thu, Dec 05, 2002 at 05:22:50PM +0200, Giorgos Keramidas wrote: > > Remove your src/contrib/gcc/INSTALL directory and try cvsup'ing again. > The files in that directory were imported yesterday, and I think that > David O'Brien didn't mean to import them at all: > > Giorgos. > Been there, done that - several times :) JY To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Creating bootsector file for W2k boot menu
On 2002-12-05 00:22, Tomi Vainio - Sun Finland - <[EMAIL PROTECTED]> wrote: > I've used Windows NT boot menu for years to boot FreeBSD from the > second disk on my machines. I've used bootpart DOS program to do this > but now I can't find correct way to do FreeBSD boot block for it. > Earlier there was a diskid definition in some Makefile to change. How > should I do this now? I have FreeBSD installed on two primary slices of my machine, as you can see from the df(1) output below. I can boot FreeBSD fine, if I copy the boot record of the slice my root partition lives in: # df / Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad0s1a498078 85920 37231219%/ # dd if=/dev/ad0s1 of=/root/bsdboot.bin bs=512 count=1 Then copy bsdboot.bin to a Windows partition, say in C:\BSDBOOT.BIN and add the following to the C:\BOOT.INI file: C:\BSDBOOT.BIN="FreeBSD on ad0s1" That should be all... Giorgos. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On Thu, Dec 05, 2002 at 06:20:05PM +0300, Sergey A. Osokin wrote: > Updating collection src-all/cvs > Edit src/bin/sh/bltin/echo.1 > Add delta 1.11 2002.12.05.08.49.59 ru > Delete src/contrib/gcc/INSTALL > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > Edit src/lib/libc/gen/uname.3 > > Looks like really something wrong with CVS... > > -- > > Rgdz,/"\ ASCII RIBBON CAMPAIGN > Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL > http://ozz.pp.ru/ X AND NEWS > / \ Welcome to the new world :) Here is an excerpt from my checkouts.cvs: D src/contrib/gcc/INSTALL C src/contrib/gcc/INSTALL/README,v . . 2#871#110#10390149783#6843#444 1.1.1.1 20 02.12.04.15.10.39 2#871#110#10390146393#2613#644 C src/contrib/gcc/INSTALL/binaries.html,v . . 2#871#110#10390149784#30183#444 1. 1.1.1 2002.12.04.15.10.40 2#871#110#10390146404#25953#644 C src/contrib/gcc/INSTALL/build.html,v . . 2#871#110#10390149785#104683#444 1.1. 1.1 2002.12.04.15.10.40 2#871#110#10390146405#100453#644 C src/contrib/gcc/INSTALL/configure.html,v . . 2#871#110#10390149785#302913#444 1.1.1.1 2002.12.04.15.10.40 2#871#110#10390146405#298683#644 C src/contrib/gcc/INSTALL/download.html,v . . 2#871#110#10390149784#24843#444 1. 1.1.1 2002.12.04.15.10.40 2#871#110#10390146404#20613#644 C src/contrib/gcc/INSTALL/finalinstall.html,v . . 2#871#110#10390149784#48553#44 4 1.1.1.1 2002.12.04.15.10.40 2#871#110#10390146404#44283#644 C src/contrib/gcc/INSTALL/gfdl.html,v . . 2#871#110#10390149785#195223#444 1.1.1 .1 2002.12.04.15.10.40 2#871#110#10390146405#190993#644 C src/contrib/gcc/INSTALL/index.html,v . . 2#871#110#10390149784#35293#444 1.1.1 .1 2002.12.04.15.10.39 2#871#110#10390146394#31063#644 C src/contrib/gcc/INSTALL/old.html,v . . 2#871#110#10390149785#275053#444 1.1.1. 1 2002.12.04.15.10.40 2#871#110#10390146405#270803#644 C src/contrib/gcc/INSTALL/specific.html,v . . 2#871#110#10390149785#895913#444 1 .1.1.1 2002.12.04.15.10.40 2#871#110#10390146405#891613#644 C src/contrib/gcc/INSTALL/test.html,v . . 2#871#110#10390149784#68953#444 1.1.1. 1 2002.12.04.15.10.40 2#871#110#10390146404#64713#644 U src/contrib/gcc/INSTALL 2#861#11#01#0 c src/contrib/gcc/INSTALL,v . . 2#871#110#10339284636#1127343#444 JY To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On 2002-12-05 21:33, leafy <[EMAIL PROTECTED]> wrote: > On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote: > > > Delete src/contrib/gcc/INSTALL > > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > > > > > It's weird... Remove your src/contrib/gcc/INSTALL directory and try cvsup'ing again. The files in that directory were imported yesterday, and I think that David O'Brien didn't mean to import them at all: keramida@gothmog:/a/freebsd/src/contrib/gcc/INSTALL> lcvs -qR log | logsort 11 entries. 2002.12.04.15.10.39 README 1.1.1.1 obrien 2002.12.04.15.10.39 index.html 1.1.1.1 obrien 2002.12.04.15.10.40 build.html 1.1.1.1 obrien 2002.12.04.15.10.40 configure.html 1.1.1.1 obrien 2002.12.04.15.10.40 download.html 1.1.1.1 obrien 2002.12.04.15.10.40 finalinstall.html 1.1.1.1 obrien 2002.12.04.15.10.40 gfdl.html 1.1.1.1 obrien 2002.12.04.15.10.40 binaries.html 1.1.1.1 obrien 2002.12.04.15.10.40 old.html 1.1.1.1 obrien 2002.12.04.15.10.40 specific.html 1.1.1.1 obrien 2002.12.04.15.10.40 test.html 1.1.1.1 obrien Note that the date of all the files is 2002.12.04 (Dec 4, 2002) :) The fact that their versions are 1.1.1.1 is also a hint that they were imported (i.e. brought initially in the FreeBSD source tree) yesterday. > Actually I have the INSTALL dir and the corresponding files, just > that cvsup insisted on deleting it, which I don't know why I seem to have them too. But I haven't run cvsup since yesterday. Soon, I'll update my local sources. I expect they will go away. Giorgos. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lock order reversals in sys_pipe.c and kern_sig.c
On 04-Dec-2002 Alfred Perlstein wrote:
> * Lars Eggert <[EMAIL PROTECTED]> [021204 15:04] wrote:
>>
>> FYI, just got a similar one yesterday on an up-to-date -current:
>>
>> lock order reversal
>> 1st 0xc784d700 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
>> 2nd 0xc0513840 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2225
>
> Since no one has given me the traceback based on the patch I posted
> earlier I have ceased to care about the "problem". If someone
> seriously cares they will run with my patch and post a backtrace.
Your patch doesn't work because it makes a bogus assumption. A better
try would be this:
Index: subr_witness.c
===
RCS file: /usr/cvs/src/sys/kern/subr_witness.c,v
retrieving revision 1.130
diff -u -r1.130 subr_witness.c
--- subr_witness.c 11 Nov 2002 16:36:20 - 1.130
+++ subr_witness.c 18 Nov 2002 20:42:35 -
@@ -205,6 +205,9 @@
{ "uidinfo hash", &lock_class_mtx_sleep },
{ "uidinfo struct", &lock_class_mtx_sleep },
{ NULL, NULL },
+ { "sigio lock", &lock_class_mtx_sleep },
+ { "pipe mutex", &lock_class_mtx_sleep },
+ { NULL, NULL },
/*
* spin locks
*/
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: setfacl requirements?
On Thu, 5 Dec 2002, kai ouyang wrote:
> Hi, everybody,
> >From Robert N M Watson
> >(1) UFS_ACL isn't enabled
> Yes, I am sure that in my kernel config:
> options UFS_ACL
> options UFS_EXTATTR
> options UFS_EXTATTR_AUTOSTART
Ok, looks good.
> >(2) Extended attributes aren't available on the file system (shouldn't
> >happen for UFS2, but might happen for UFS1 if you don't have
> >UFS_EXTATTR and appropriate configuration of EAs)
> I do as the "README.alcs"
> mkdir -p /usr/.attribute/system
> cd /.attribute/system
> extattrctl initattr -p /usr/ 388 posix1e.acl_access
> extattrctl initattr -p /usr/ 388 posix1e.acl_default
Followed by a reboot, right?
> >(3) The file system isn't mounted with the ACL option: either -o acls (or
> >acls in the fstab file), or more reliably, setting the "tunefs -a
> >enable" flag in the file system configuration.
> >For better or for worse, POSIX.1e defines that getfacl() will print the
> >current file permissions as an ACL if ACLs aren't available on the file
> >system. As such, you're probably just seeing the results of stat()
> >printed in an ACL form.
> I use UFS1. In DP1, the ACL works nice. But in DP2, I have never succeeded.
> in DP1, there is no need to add the 'acls' to 'fstab'. Anyway, I also add
> the 'acls' flag to 'fstab', but it fails, too.
> The system always say:
> Current#cd /usr/
> Current#setfacl -m u:oyk:r src
> setfacl: acl_get_file() failed: Operation not supported
If you run mount, does it show the "acls" flag for /usr? I generally
recommend that the tunefs flag be used to start ACLs on a file system
rather than the fstab flag, since that will prevent races and issues with
re-mounting for /. Try the following:
tunefs -a enable /dev/{deviceof/usr}
then unmount and remount the file system (probably by rebooting). Here's
the procedure I use to test ACLs locally when I don't want to mess with a
live file system:
alsvid# mdconfig -a -t malloc -s4m
md0
alsvid# newfs /dev/md0
/dev/md0: 4.0MB (8192 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 1.02MB, 65 blks, 256 inodes.
super-block backups (for fsck -b #) at:
32, 2112, 4192, 6272
alsvid# mount /dev/md0 /mnt
alsvid# cd /mnt
alsvid# mkdir -p .attribute/system
alsvid# cd .attribute/system/
alsvid# extattrctl initattr -p . 388 posix1e.acl_access
alsvid# extattrctl initattr -p . 388 posix1e.acl_default
alsvid# cd /mnt
alsvid# setfacl -m u:robert:r .
setfacl: acl_get_file() failed: Operation not supported
alsvid# cd /
alsvid# umount /mnt
alsvid# tunefs -a enable /dev/md0
tunefs: ACLs set
alsvid# mount /dev/md0 /mnt
alsvid# mount
/dev/ad0s1a on / (ufs, NFS exported, local, soft-updates)
devfs on /dev (devfs, local, multilabel)
/dev/md0 on /mnt (ufs, local, acls)
alsvid# setfacl -m u:robert:r .
alsvid# ls -la
total 5
drwxr-xr-x+ 3 root wheel 512 Dec 5 10:40 .
drwxr-xr-x 20 root wheel 1024 Nov 29 16:00 ..
drwxr-xr-x 3 root wheel 512 Dec 5 10:40 .attribute
alsvid# getfacl .
#file:.
#owner:0
#group:0
user::rwx
user:robert:r--
group::r-x
mask::r-x
other::r-x
Try using tunefs and see how things go. BTW, we're generally recommending
the use of UFS2 with ACLs because the extended attribute support is
substantially faster and more reliable.
It looks like there may be a problem with the processing of the "acls"
flag as an argument of the mount command. I'll investigate locally and
see if that's the cause -- if so, that would result in what you're seeing.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SED regression
On Thu, Dec 05, 2002 at 11:49:01PM +0900, FUJISHIMA Satsuki wrote: > Does anyone see this? > both -CURRENT and -STABLE fail at the same place. > > note: GNU sed 3.02 from ports passed this test. > > /usr/src/tools/regression/usr.bin/sed$ make > Running test G > PASS: Test G detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test P > PASS: Test P detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test psl > PASS: Test psl detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test bcb > PASS: Test bcb detected no regression. (in /usr/src/tools/regression/usr.bin/sed) > Running test y > --- regress.y.out Fri Jun 28 01:07:51 2002 > +++ - Thu Dec 5 23:26:19 2002 > @@ -1 +1 @@ > -fOO > \ No newline at end of file > +fOO > FAIL: Test y failed: regression detected. See above. (in >/usr/src/tools/regression/usr.bin/sed) > *** Error code 1 > > Stop in /usr/src/tools/regression/usr.bin/sed. > The usr.bin/sed/process.c,v 1.21 change is responsible for the "breakage": : revision 1.21 : date: 2002/06/22 01:42:26; author: tjr; state: Exp; lines: +10 -11 : Don't store newlines at the end of each line in the hold/pattern spaces, : instead add the newline when the pattern space is printed. Make the `G' and : `H' commands add a newline to the space before the data, remove bogus : addition of newline from `x' command. : : PR: 29790, 38195 But I'm pretty confident that what we do now is correct, and it seems to be in agreement with POSIX.1-2001, which says: : In default operation, sed cyclically shall append a line of input, : less its terminating , into the pattern space. : ... : Whenever the pattern space is written to standard output or a named : file, sed shall immediately follow it with a . (This regression test turned into a failure only after a contrib/diff/util.c,v 1.5 commit.) Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg48149/pgp0.pgp Description: PGP signature
Re: cvsup weird problem
On Thu, Dec 05, 2002 at 09:33:45PM +0800, leafy wrote: > On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote: > > > Delete src/contrib/gcc/INSTALL > > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > > > > > It's weird... > > > > Looks like a strange, yesterday i'm successfuly cvsuped my 5.0 box > > (in vmware under 4.7-S). > > -rw-r--r-- 1 root wheel 89161 Dec 4 18:10 specific.html > > -rw-r--r-- 1 root wheel 6471 Dec 4 18:10 test.html > > > > Today i rebuild my 5.0 box and now install new version. > > -- > > > > Rgdz,/"\ ASCII RIBBON CAMPAIGN > > Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL > Actually I have the INSTALL dir and the corresponding files, just that cvsup > insisted on deleting it, which I don't know why Oops... Here is a new resup: Updating collection src-all/cvs Edit src/bin/sh/bltin/echo.1 Add delta 1.11 2002.12.05.08.49.59 ru Delete src/contrib/gcc/INSTALL Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty Edit src/lib/libc/gen/uname.3 Looks like really something wrong with CVS... -- Rgdz,/"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SED regression
Does anyone see this? both -CURRENT and -STABLE fail at the same place. note: GNU sed 3.02 from ports passed this test. /usr/src/tools/regression/usr.bin/sed$ make Running test G PASS: Test G detected no regression. (in /usr/src/tools/regression/usr.bin/sed) Running test P PASS: Test P detected no regression. (in /usr/src/tools/regression/usr.bin/sed) Running test psl PASS: Test psl detected no regression. (in /usr/src/tools/regression/usr.bin/sed) Running test bcb PASS: Test bcb detected no regression. (in /usr/src/tools/regression/usr.bin/sed) Running test y --- regress.y.out Fri Jun 28 01:07:51 2002 +++ - Thu Dec 5 23:26:19 2002 @@ -1 +1 @@ -fOO \ No newline at end of file +fOO FAIL: Test y failed: regression detected. See above. (in /usr/src/tools/regression/usr.bin/sed) *** Error code 1 Stop in /usr/src/tools/regression/usr.bin/sed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ia64 tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- ===> gnu/usr.bin/binutils/libbfd elf64-ia64.c: In function `elf64_ia64_size_dynamic_sections': elf64-ia64.c:2744: `ELF_DYNAMIC_INTERPRETER' undeclared (first use in this function) elf64-ia64.c:2744: (Each undeclared identifier is reported only once elf64-ia64.c:2744: for each function it appears in.) *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc and fd
In article <[EMAIL PROTECTED]> Takahashi Yoshihiro <[EMAIL PROTECTED]> writes: > After recent your changes of the ahc driver, the fd driver can't work > on my pc98 box. It never return from the open(2) syscall. I don't > know that this problem is only pc98 or not. The following changes solve this problem. Thank you. > scottl 2002/12/04 14:51:29 PST > > Modified files: > sys/dev/aic7xxx ahd_pci.c aic79xx.reg aic79xx_osm.h > aic79xx_pci.c aic7xxx_osm.h aic7xxx_pci.c > Log: > Last minute fixes to ahc and ahd: --- TAKAHASHI Yoshihiro <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On Thu, Dec 05, 2002 at 04:32:01PM +0300, Sergey A. Osokin wrote: > > Delete src/contrib/gcc/INSTALL > > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > > > It's weird... > > Looks like a strange, yesterday i'm successfuly cvsuped my 5.0 box > (in vmware under 4.7-S). > -rw-r--r-- 1 root wheel 89161 Dec 4 18:10 specific.html > -rw-r--r-- 1 root wheel 6471 Dec 4 18:10 test.html > > Today i rebuild my 5.0 box and now install new version. > -- > > Rgdz,/"\ ASCII RIBBON CAMPAIGN > Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL Actually I have the INSTALL dir and the corresponding files, just that cvsup insisted on deleting it, which I don't know why To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On Thu, Dec 05, 2002 at 09:21:09PM +0800, leafy wrote: > On Thu, Dec 05, 2002 at 11:25:14AM +0800, JY wrote: > > I did as you suggested and it's still complaining :( > > > > JY > I was cvsupping from cvsup2.freebsd.org. At first it complains about > gcc/INSTALL not being empty, so I manually deleted everything under it, but > not the dir itself. > > Then I cvsupped: > Connected to cvsup2.FreeBSD.org > Updating collection src-all/cvs > Checkout src/contrib/gcc/INSTALL/README > Checkout src/contrib/gcc/INSTALL/binaries.html > Checkout src/contrib/gcc/INSTALL/build.html > Checkout src/contrib/gcc/INSTALL/configure.html > Checkout src/contrib/gcc/INSTALL/download.html > Checkout src/contrib/gcc/INSTALL/finalinstall.html > Checkout src/contrib/gcc/INSTALL/gfdl.html > Checkout src/contrib/gcc/INSTALL/index.html > Checkout src/contrib/gcc/INSTALL/old.html > Checkout src/contrib/gcc/INSTALL/specific.html > Checkout src/contrib/gcc/INSTALL/test.html > Delete src/contrib/gcc/INSTALL > Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty > > It's weird... Looks like a strange, yesterday i'm successfuly cvsuped my 5.0 box (in vmware under 4.7-S). $ ls -la /usr/src/contrib/gcc/INSTALL/ total 207 drwxr-xr-x 2 root wheel512 Dec 5 12:21 . drwxr-xr-x 11 root wheel 8704 Dec 5 12:21 .. -rw-r--r-- 1 root wheel261 Dec 4 18:10 README -rw-r--r-- 1 root wheel 2595 Dec 4 18:10 binaries.html -rw-r--r-- 1 root wheel 10045 Dec 4 18:10 build.html -rw-r--r-- 1 root wheel 29868 Dec 4 18:10 configure.html -rw-r--r-- 1 root wheel 2061 Dec 4 18:10 download.html -rw-r--r-- 1 root wheel 4428 Dec 4 18:10 finalinstall.html -rw-r--r-- 1 root wheel 19099 Dec 4 18:10 gfdl.html -rw-r--r-- 1 root wheel 3106 Dec 4 18:10 index.html -rw-r--r-- 1 root wheel 27080 Dec 4 18:10 old.html -rw-r--r-- 1 root wheel 89161 Dec 4 18:10 specific.html -rw-r--r-- 1 root wheel 6471 Dec 4 18:10 test.html Today i rebuild my 5.0 box and now install new version. -- Rgdz,/"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup weird problem
On Thu, Dec 05, 2002 at 11:25:14AM +0800, JY wrote: > I did as you suggested and it's still complaining :( > > JY I was cvsupping from cvsup2.freebsd.org. At first it complains about gcc/INSTALL not being empty, so I manually deleted everything under it, but not the dir itself. Then I cvsupped: Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Checkout src/contrib/gcc/INSTALL/README Checkout src/contrib/gcc/INSTALL/binaries.html Checkout src/contrib/gcc/INSTALL/build.html Checkout src/contrib/gcc/INSTALL/configure.html Checkout src/contrib/gcc/INSTALL/download.html Checkout src/contrib/gcc/INSTALL/finalinstall.html Checkout src/contrib/gcc/INSTALL/gfdl.html Checkout src/contrib/gcc/INSTALL/index.html Checkout src/contrib/gcc/INSTALL/old.html Checkout src/contrib/gcc/INSTALL/specific.html Checkout src/contrib/gcc/INSTALL/test.html Delete src/contrib/gcc/INSTALL Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty It's weird... JY To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVS broken? (buildworld fails when cleaning tar)
hi, there! On Thu, Dec 05, 2002 at 01:43:38PM +0300, Denis N. Peplin wrote: > > > I'm trying this: > > > # cd /usr > > > # rm -rf src obj > > > # cvs -R co src > > > > use co -P (prune empty directories). > Thanks, i will use it. > But two weeks ago building world was succeseful w/o any additional options to > cvs... -P is not an additional option. You should always use -P (put it into your ~/.cvsrc). This is how cvs directory removals are handled in cvs. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Any ideas at all about network problem?
Brad Knowles wrote: > Other than that, you should try swapping out as much hardware as > you can -- the cards, the cables, etc If possible, you should > also test with other computers (in case the problem is with one > specific machine when it is running 5.0). Swapping 5.0 out for 4.7 will also work. 8-). Seriously: go through the intermediate versions of FreeBSD. Do you have a local CVS tree? Have you ever played the guessing game "higher or lower"? It only takes you at most log2(N)+1 "guesses", and you will have the day the change was made. Then you "cvs diff -r -r", and you will have the code that changed that day. Revert the change in the bus, rl, or other code that's in the code path, and you have your fix. Very easy. > Just because something appears to work perfectly in another OS is > not an indication that there is not anything wrong with that setup. Only with the second OS, when it fails to workaround the problem that the first OS works around without being asked... > However, since there are many potential software components that > could be involved, while testing each component individually between > now and then should theoretically be doable in 10 tests (as > previously mentioned), the combinatorial explosion will be > exceptionally nasty. You only need the delta for the day it was introduced, vs. the day before. Unless it was the KSE import that did it, it's very likely that it will be very obvious, in context. On an 800MHz box, you are talking 6 hours to do this, including all the tests that you have to run. If you have a fast box, you can cut this in half. Or if you have three fast boxes (so you can do branch prediction up and down on two while testing on the third), you can cut this to about 40 minutes. That's less than an hour, and far less time than it's taken the original poster to post messages in this thread, describing the problem. BTW: Good reason to buy hardware for your senior engineers there, and not complain when they ask for it, isn't it? 8-) 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVS broken? (buildworld fails when cleaning tar)
On Thursday 05 December 2002 13:16, Kris Kennaway wrote: > On Thu, Dec 05, 2002 at 12:11:36PM +0300, Denis N. Peplin wrote: > > I'm trying this: > > # cd /usr > > # rm -rf src obj > > # cvs -R co src > > use co -P (prune empty directories). Thanks, i will use it. But two weeks ago building world was succeseful w/o any additional options to cvs... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Any ideas at all about network problem?
At 10:33 PM -0500 2002/12/04, Craig Reyenga wrote: Unfortunately, I have no extra hardware available to me, so I can't experiment with switches and whatnot. Also, wouldn't some sort of software experimentation be more appropriate, considering that my existing setup works _perfetcly_ in 4.7? At the very least, try hard-wiring the configuration at both ends to be 100Mbps full-duplex. There's a chance that 4.7 and 5.0 will handle auto-negotiation differently. Other than that, you should try swapping out as much hardware as you can -- the cards, the cables, etc If possible, you should also test with other computers (in case the problem is with one specific machine when it is running 5.0). Just because something appears to work perfectly in another OS is not an indication that there is not anything wrong with that setup. If that was the case, there would never be a need for any replacement for any Microsoft OSes, because many vendors stop trying to debug the problem when they can prove that things work just fine under Windows. I'm not sure what to do; should I be trying various versions of if_rl.c? Or is there something else that I should be trying? If you really want to try swapping software, you'll have to do a binary search on each potential piece of software involved. However, since there are many potential software components that could be involved, while testing each component individually between now and then should theoretically be doable in 10 tests (as previously mentioned), the combinatorial explosion will be exceptionally nasty. -- Brad Knowles, <[EMAIL PROTECTED]> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVS broken? (buildworld fails when cleaning tar)
On Thu, Dec 05, 2002 at 12:11:36PM +0300, Denis N. Peplin wrote: > I'm trying this: > # cd /usr > # rm -rf src obj > # cvs -R co src use co -P (prune empty directories). Kris msg48137/pgp0.pgp Description: PGP signature
CVS broken? (buildworld fails when cleaning tar)
I'm trying this: # cd /usr # rm -rf src obj # cvs -R co src # cd src # make buildworld rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> gnu/usr.bin/tar rm -f tar addext.o argmatch.o backupfile.o basename.o dirname.o error.o exclude.o full-write.o getdate.o getline.o getopt.o getopt1.o getstr.o hash.o human.o mktime.o modechange.o prepargs.o print-copyr.o quotearg.o safe-read.o save-cwd.o savedir.o unicodeio.o xgetcwd.o xmalloc.o xstrdup.o xstrtoul.o xstrtoumax.o buffer.o compare.o create.o delete.o extract.o incremen.o list.o mangle.o misc.o names.o rtapelib.o tar.o update.o tar.1.gz tar.1.cat.gz rm: tar: is a directory *** Error code 1 Stop in /usr/src/gnu/usr.bin/tar. *** Error code 1 Stop in /usr/src/gnu/usr.bin/tar. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Then I try to solve problem (remove gnu/usr.bin/tar/tar directory) # rm -rf gnu/usr.bin/tar/tar # make buildworld Success!!! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ia64 tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- ===> gnu/usr.bin/binutils/libbfd elf64-ia64.c: In function `elf64_ia64_size_dynamic_sections': elf64-ia64.c:2744: `ELF_DYNAMIC_INTERPRETER' undeclared (first use in this function) elf64-ia64.c:2744: (Each undeclared identifier is reported only once elf64-ia64.c:2744: for each function it appears in.) *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
