Re: vmware fails on -current
HM == Hellmuth Michaelis [EMAIL PROTECTED] writes: HM After this, vmware comes up and then complains about not able to use HM /dev/rtc (/dev/rtc is present in /compat/linux and is kld-loaded) but HM then continues to start up and runs. Hmm.. I have experienced another problem(-current of 19 Nov.) with vmware. When it runs it comes up with the following dialog: Encountered an error while initializing the ethernet address. You probably have an old vnet driver. Try installing a newer version Failed to configure ethernet0 vmnet1 is host-only configuration. my vmware didn't complain about /dev/rtc... rtc-2001.09.16.1 is installed. HM hellmuth -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [sleeping now]http://www.kr.FreeBSD.org/~cjh [while sleeping] cjh @ kr.FreeBSD.ORG cjh @ FreeBSD.ORG cjh @ wdb.co.kr Korea FreeBSD Users Group www.kr.FreeBSD.org Web Data Bankwww.wdb.co.kr To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Lock order reversal while playing mp3s
I get the following lock order reversal when playing mp3s on my Vaio PCG-F807K laptop: lock order reversal 1st 0xc399a840 pcm0:play:0 @ /usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/dsp.c:936 2nd 0xc399ad80 pcm0 @ /usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/sound.c:132 simond@laptop:~$ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: Yamaha DS-1E (YMF744) at memory 0xfedf8000 irq 9 (4p/2r/0v channels duplex default) My dmesg is attached. -- Simon Dick [EMAIL PROTECTED] Why do I get this urge to go bowling everytime I see Tux? Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Thu Nov 15 16:31:01 GMT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOT Preloaded elf kernel /boot/kernel/kernel at 0xc04d5000. Preloaded elf module /boot/kernel/acpi.ko at 0xc04d50a8. Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (730.81-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 1073676288 (1048512K bytes) avail memory = 1040375808 (1015992K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 lock order reversal 1st 0xc03f7760 allproc @ /usr/src/sys/kern/kern_fork.c:343 2nd 0xc03b87b0 pool mutex @ /usr/src/sys/kern/kern_sx.c:329 lock order reversal 1st 0xc03f76e0 proctree @ /usr/src/sys/kern/kern_fork.c:573 2nd 0xc03b8750 pool mutex @ /usr/src/sys/kern/kern_sx.c:329 lock order reversal 1st 0xc03b77e0 fork list @ /usr/src/sys/kern/kern_fork.c:646 2nd 0xc03b8810 pool mutex @ /usr/src/sys/kern/kern_sx.c:204 Pentium Pro MTRR support enabled VESA: v3.0, 32768k memory, flags:0x1, mode table:0xc00c5477 (c0005477) VESA: Matrox Graphics Inc. Using $PIR table, 8 entries at 0xc00f7100 apm: Other PM system enabled. npx0: math processor on motherboard npx0: INT 16 interface acpi0: AMIINT on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686 ATA66 controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: VIA 83C572 USB controller port 0xc800-0xc81f irq 9 at device 7.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: VIA 83C572 USB controller port 0xcc00-0xcc1f irq 9 at device 7.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ichsmb0: SMBus controller at device 7.4 on pci0 device_probe_and_attach: ichsmb0 attach returned 6 ahc0: Adaptec 2940A Ultra SCSI adapter port 0xdc00-0xdcff mem 0xd000-0xdfff irq 10 at device 9.0 on pci0 aic7860: Ultra Single Channel A, SCSI Id=7, 3/255 SCBs ed0: NE2000 PCI Ethernet (VIA VT86C926) port 0xd000-0xd01f irq 5 at device 10.0 on pci0 ed0: address 08:00:39:01:2b:90, type NE2000 (16 bit) pcm0: Creative CT5880-C port 0xd400-0xd43f irq 9 at device 11.0 on pci0 tx0: SMC EtherPower II 10/100 port 0xd800-0xd8ff mem 0xdfffe000-0xdfffefff irq 11 at device 12.0 on pci0 miibus0: MII bus on tx0 qsphy0: QS6612 10/100 media interface on miibus0 qsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto tx0: address 00:e0:29:0b:d5:31, type SMC9432TX acpi_button1: Sleep Button on acpi0 atspeaker0 port 0x61 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: NEC 72065B or clone port 0x3f7,0x3f2-0x3f5 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 on acpi0 ppc0: SMC-like chipset
Re: Lock order reversal while playing mp3s
On Wed, Nov 21, 2001 at 09:37:43AM +, Simon Dick wrote: I get the following lock order reversal when playing mp3s on my Vaio PCG-F807K laptop: lock order reversal 1st 0xc399a840 pcm0:play:0 @ /usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/dsp.c:936 2nd 0xc399ad80 pcm0 @ /usr/src/sys/modules/sound/pcm/../../../dev/sound/pcm/sound.c:132 simond@laptop:~$ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: Yamaha DS-1E (YMF744) at memory 0xfedf8000 irq 9 (4p/2r/0v channels duplex default) My dmesg is attached. And now my *real* dmesg is attached :) -- Simon Dick [EMAIL PROTECTED] Why do I get this urge to go bowling everytime I see Tux? Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Tue Nov 20 17:30:10 GMT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP Preloaded elf kernel /boot/kernel/kernel at 0xc04fe000. Preloaded elf module /boot/kernel/cd9660.ko at 0xc04fe0a8. Preloaded elf module /boot/kernel/msdosfs.ko at 0xc04fe154. Preloaded elf module /boot/kernel/ntfs.ko at 0xc04fe200. Preloaded elf module /boot/kernel/procfs.ko at 0xc04fe2ac. Preloaded elf module /boot/kernel/md.ko at 0xc04fe358. Preloaded elf module /boot/kernel/linux.ko at 0xc04fe400. Preloaded elf module /boot/kernel/ipfw.ko at 0xc04fe4ac. Preloaded elf module /boot/kernel/if_wi.ko at 0xc04fe558. Preloaded elf module /boot/kernel/snd_ds1.ko at 0xc04fe604. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04fe6b0. Preloaded elf module /boot/kernel/usb.ko at 0xc04fe75c. Preloaded elf module /boot/kernel/ugen.ko at 0xc04fe804. Preloaded elf module /boot/kernel/uhid.ko at 0xc04fe8b0. Preloaded elf module /boot/kernel/ums.ko at 0xc04fe95c. Preloaded elf module /boot/kernel/umass.ko at 0xc04fea04. Preloaded elf module /boot/kernel/agp.ko at 0xc04feab0. Preloaded elf module /boot/kernel/atspeaker.ko at 0xc04feb58. Preloaded elf module /boot/kernel/nfsclient.ko at 0xc04fec08. Preloaded elf module /boot/kernel/fdc.ko at 0xc04fecb8. Preloaded elf module /boot/kernel/if_ed.ko at 0xc04fed60. Preloaded elf module /boot/kernel/miibus.ko at 0xc04fee0c. Preloaded elf module /boot/kernel/snp.ko at 0xc04feeb8. Preloaded elf module /boot/kernel/nmdm.ko at 0xc04fef60. Preloaded elf module /boot/kernel/acpi.ko at 0xc04ff00c. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 645207024 Hz CPU: Pentium III/Pentium III Xeon/Celeron (645.21-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268369920 (262080K bytes) avail memory = 255623168 (249632K bytes) Pentium Pro MTRR support enabled VESA: v2.0, 8128k memory, flags:0x0, mode table:0xc0328842 (122) VESA: ATI MACH64 Using $PIR table, 8 entries at 0xc00fdf40 npx0: math processor on motherboard npx0: INT 16 interface acpi0: SONY K2 on motherboard Timecounter ACPI frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0x4000-0x40ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xfca0-0xfcbf irq 9 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: Intel 82371AB Power management controller port 0x1040-0x104f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 1040 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped 8000 pci0: serial bus, FireWire at device 8.0 (no driver attached) pcm0: Yamaha DS-1E (YMF744) port 0xfc8c-0xfc8f,0xfcc0-0xfcff mem 0xfedf8000-0xfedf irq 9 at device 9.0 on pci0 pci0: simple comms at device 10.0 (no driver attached) acpi_pcib0: device is routed to IRQ 9 pcic0: Ricoh RL5C478 PCI-CardBus Bridge irq 9 at device 12.0 on pci0 pcic0: PCI Memory allocated: 0x4400 pccard0: PC Card bus (classic) on pcic0 acpi_pcib0: device is routed to IRQ 9 pcic1: Ricoh RL5C478 PCI-CardBus Bridge irq 9 at device 12.1 on pci0 pcic1: PCI Memory allocated: 0x44001000 pccard1: PC Card bus (classic) on pcic1 atspeaker0
Re: vmware fails on -current
In message [EMAIL PROTECTED], CHOI Junho writes: Hmm.. I have experienced another problem(-current of 19 Nov.) with vmware. When it runs it comes up with the following dialog: Encountered an error while initializing the ethernet address. You probably have an old vnet driver. Try installing a newer version Failed to configure ethernet0 Hi, could you try to get a ktrace of what it is doing just before this happens? Run ktrace -i vmware as root (you may need to copy your ~/.vmware to ~root first). Then use linux_kdump -n (/usr/ports/devel/linux_kdump) and look for any ioctls that it does immediately before giving that error message. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vmware fails on -current
ID == Ian Dowse [EMAIL PROTECTED] writes: ID In message [EMAIL PROTECTED], CHOI Junho writes: Hmm.. I have experienced another problem(-current of 19 Nov.) with vmware. When it runs it comes up with the following dialog: Encountered an error while initializing the ethernet address. You probably have an old vnet driver. Try installing a newer version Failed to configure ethernet0 ID Hi, could you try to get a ktrace of what it is doing just before ID this happens? Run ID ktrace -i vmware ID as root (you may need to copy your ~/.vmware to ~root first). Then ID use linux_kdump -n (/usr/ports/devel/linux_kdump) and look for ID any ioctls that it does immediately before giving that error message. I'll try. Oh, I forget to say I appiled des's linux_ioctl patch. http://people.freebsd.org/~des/software/ ID Ian -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [sleeping now]http://www.kr.FreeBSD.org/~cjh [while sleeping] cjh @ kr.FreeBSD.ORG cjh @ FreeBSD.ORG cjh @ wdb.co.kr Korea FreeBSD Users Group www.kr.FreeBSD.org Web Data Bankwww.wdb.co.kr To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vmware fails on -current
In message [EMAIL PROTECTED], CHOI Junho writes: I'll try. Oh, I forget to say I appiled des's linux_ioctl patch. Ah, that's different then. I assumed from the error that you had revision 1.76 of linux_ioctl.c, but if that patch applied then you don't. Try updating your sources again; revision 1.76 is des's patch with a few problems fixed. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
damaged file system despite unmounts
For a while I was noticing my largest FS reported as not unmounted cleanly on boot. Today I decided to unmount it myself and check it with fsck. Here are the results. Notice, that the first fsck had to mark the FS clean. Notice that the second fsck found something else to do, and only the third one was happy. What's happening? Thanks, -mi root@aldan:/opt/etc (174) umount /ccd root@aldan:/opt/etc (175) fsck -y /ccd ** /dev/ccd0c ** Last Mounted on /ccd ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes SUMMARY INFORMATION BAD SALVAGE? yes BLK(S) MISSING IN BIT MAPS SALVAGE? yes 463041 files, 12031814 used, 46114496 free (100184 frags, 5751789 blocks, 0.2% fragmentation) * FILE SYSTEM MARKED CLEAN * * FILE SYSTEM WAS MODIFIED * root@aldan:/opt/etc (176) fsck -y /ccd ** /dev/ccd0c ** Last Mounted on /ccd ** Phase 1 - Check Blocks and Sizes load: 0.09 cmd: fsck_ufs 60803 [physstr] 7.79u 1.72s 0% 11408k /dev/ccd0c: phase 1: cyl group 1001 of 1790 (55%) load: 0.08 cmd: fsck_ufs 60803 [physstr] 9.66u 2.11s 0% 12032k /dev/ccd0c: phase 1: cyl group 1307 of 1790 (73%) ** Phase 2 - Check Pathnames load: 0.14 cmd: fsck_ufs 60803 [physstr] 12.90u 2.78s 0% 12884k /dev/ccd0c: phase 2: dir 1355 of 54568 (2%) ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes SUMMARY INFORMATION BAD SALVAGE? yes ALLOCATED FRAG 174736 MARKED FREE BLK(S) MISSING IN BIT MAPS SALVAGE? yes 463041 files, 12031814 used, 46114495 free (100183 frags, 5751789 blocks, 0.2% fragmentation) * FILE SYSTEM WAS MODIFIED * root@aldan:/opt/etc (177) fsck -y /ccd ** /dev/ccd0c ** Last Mounted on /ccd ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 463041 files, 12031814 used, 46114495 free (100183 frags, 5751789 blocks, 0.2% fragmentation) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Sysinstall is still horribly broken.
matusita If it seems fine for me, I'll post a patch. OK, a patch is attached below. I've also made boot floppies (use 5-current code as of Nov/21/2001) for anyone who try to find out that this problem is gone away. http://people.FreeBSD.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs/boot.flp http://people.FreeBSD.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs/kern.flp http://people.FreeBSD.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs/mfsroot.flp MD5 checksums are: MD5 (boot.flp) = 88105fdd57ac68d1b2f9e7c3e067e30f MD5 (kern.flp) = ba73babdfc4cad42abfcdafa7f1fd74b MD5 (mfsroot.flp) = 8bf6b1c898b99bc549933c578dca3743 Any good or bad results are welcome. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: KYLIX/Delphi on FreeBSD 4.4 boxes
On Wed, 21 Nov 2001, Martin Blapp wrote:
We do not have any machine running FBSD 5.0-CURRENT, sorry ...
maybe here is someone out who's already 5.0? You can obtain a
Kylix Open-Version image from their webpage (I have mine
got from their, also) (KYLIX 2).
:
:Hi,
:
:linux: 'ioctl' fd=8, cmd=0x7201 ('r',1) not implemented
:
:Can you start your programm with ktrace and use linux_kdump
:to see exactly what ioctl's are missing ?
:
:Then maybe we can implement them. CURRENT has some advanced Linux ioctl
:support. Maybe kylix does work there ?
:
:Martin
:
:Martin Blapp, [EMAIL PROTECTED]
:--
:Improware AG, UNIX solution and service provider
:Zurlindenstrasse 29, 4133 Pratteln, Switzerland
:Phone: +41 061 826 93 00: +41 61 826 93 01
:PGP Fingerprint: 57E 7CCD 2769 E7AC C5FA DF2C 19C6 DCD1 1B3A EC9C
:--
:
:
--
MfG
O. Hartmann
[EMAIL PROTECTED]
IT-Administration des Institutes fuer Physik der Atmosphaere (IPA)
Johannes Gutenberg Universitaet Mainz
Becherweg 21
55099 Mainz
Tel: +496131/3924662 (Maschinenraum)
Tel: +496131/3924144
FAX: +496131/3923532
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
send_packet: No buffer space available
This is a long-standing problem which is getting more and more annoying (or so I feel, might be just an impression). I was wondering if anybody might be interested in helping me debug and fix it. I can repeat this at will using Tivoli Storage Manager for Linux to backup my -CURRENT laptop. Basically, after a few minutes I start getting these messages; at that point networking is basically hosed until I kill TSM. First of all, is this just an application misbehaving and it should be fixed only by tuning some sysctl, or is it an OS bug proper? Note that -STABLE doesn't exhibit this problem. netstat -m output is as follow: mbuf usage: GEN list: 0/0 (in use/in pool) CPU #0 list:71/144 (in use/in pool) Total: 71/144 (in use/in pool) Maximum number allowed on each CPU list: 512 Maximum possible: 18432 Allocated mbuf types: 46 mbufs allocated to data 25 mbufs allocated to packet headers 0% of mbuf map consumed mbuf cluster usage: GEN list: 0/0 (in use/in pool) CPU #0 list:20/66 (in use/in pool) Total: 20/66 (in use/in pool) Maximum number allowed on each CPU list: 128 Maximum possible: 9216 0% of cluster map consumed 168 KBytes of wired memory reserved (34% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Relevant parts of vmstat -m: Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) mbufmgr6531K 32K 31594K 2687850 0 16,32,64,128,8K,32K What else is needed to diagnose this? It's been baffling me for much too long... Bye, Andrea -- Tagline generated by 'gensig' mail-client-independent .signature generator. Get your copy at http://www.geeks.com/~robf/gensig/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvsup-devel port build problem (pm3-base)
I sent John Polstra a similar patch some time ago Any news about getting this committed John (P) ? Hi, I ran into some problems building the cvsup-devel port. In one of it's dependants, the c file is attempting to include nfs/nfs.h which is nolonger valid. /usr/ports/lang/pm3-base/work/pm3-1.1.15/boot-FreeBSD4/m3core/FreeBSD4/RTHeapDepC.c As a quick fix I symlinked nfs.h - ../nfsclient/nfs.h which allowed the compile to complete. The following more generic/correct fix could probably be dropped into the files directory as patch-XX: --- RTHeapDepC.c.orig Mon Nov 19 00:27:30 2001 +++ RTHeapDepC.cMon Nov 19 00:28:21 2001 @@ -98,7 +98,11 @@ #include sys/time.h #include nfs/rpcv2.h #include nfs/nfsproto.h +#if __FreeBSD__ = 5 +#include nfsclient/nfs.h +#else #include nfs/nfs.h +#endif #include ufs/ufs/ufsmount.h #endif -John ps: I also ran into problems with libutil.h but I haven't determined where the actual problem is coming from. Copying /usr/src/lib/libutil/libutil.h to /usr/include avoids the immediate problem. -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Panic on boot of today's -CURRENT
A couple of weeks ago, I finally(!) got around to setting up a serial console for my build machine, and it only took me another week or so to figure out that while the default behavior works admirably under -STABLE (if the keyboard is removed prior to boot), -CURRENT needs a /boot.config file created with -P in it to accomplish the same behavior. :-) [Or maybe there are other ways to accomplish this; I know that without the /boot.config, the serial console wasn't really a console, in that it didn't get anything written to it until the login: prompt from the completion of the multi-user boot.] Anyway, I now have my first panic on boot from -CURRENT since setting up the serial console; modulo cut/paste damage, the following ought to be fairly accurate. :-} Sources are as of about 3:50 AM PST (8 hrs. west of GMT), from cvsup14. Here are the boot messages, which start showing some strange ugliness down near the end: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #50: Wed Nov 21 07:13:06 PST 2001 [EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST Preloaded elf kernel /boot/kernel/kernel at 0xc044. Preloaded elf module /boot/kernel/acpi.ko at 0xc04400a8. Calibrating clock(s) ... TSC clock: 876472249 Hz, i8254 clock: 1193291 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium III/Pentium III Xeon/Celeron (876.40-MHz 686-class CPU) Origin = GenuineIntel Id = 0x68a Stepping = 10 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 536805376 (524224K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0046a000 - 0x1ffe7fff, 532144128 bytes (129918 pages) avail memory = 518021120 (505880K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 SMP: CPU0 apic_initialize(): lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178011, at 0xfec0 bios32: Found BIOS32 Service Directory header at 0xc00faf20 bios32: Entry = 0xfb390 (c00fb390) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb3c0 pnpbios: Found PnP BIOS data at 0xc00fbde0 pnpbios: Entry = f:be10 Rev = 1.0 Other BIOS signatures found: null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled random: entropy source Math emulator present SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff pci_open(1):mode 1 addr port (0x0cf8) is 0x8060 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=30911106) Using $PIR table, 8 entries at 0xc00fde30 npx0: math processor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: physical bus=0 map[10]: type 3, range 32, base d900, size 23, enabled found- vendor=0x1106, dev=0x3091, revid=0x01 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 powerspec 2 supports D0 D3 current D0 found- vendor=0x1106, dev=0xb091, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 IOAPIC #0 intpin 11 - irq 2 Freeing (NOT implemented) redirected PCI irq 11. map[10]: type 4, range 32, base c000, size 7, enabled map[14]: type 1, range 32, base d980, size 7, enabled found- vendor=0x10ec, dev=0x8129, revid=0x00 bus=0, slot=9, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=2 IOAPIC #0 intpin 12 - irq 5 Freeing (NOT implemented) redirected PCI irq 12. map[10]: type 4, range 32, base c400, size 8, enabled found- vendor=0x13f6, dev=0x0111, revid=0x10 bus=0, slot=14, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base c800, size 3, enabled map[14]: type 4, range 32, base cc00, size 2, enabled map[18]: type 4, range 32, base d000, size 3, enabled map[1c]: type 4, range 32, base d400, size 2, enabled
Re: cvsup-devel port build problem (pm3-base)
In article [EMAIL PROTECTED], Brian Somers [EMAIL PROTECTED] wrote: I sent John Polstra a similar patch some time ago Any news about getting this committed John (P) ? There is already an open PR with a patch. I think Mark Murray is working on committing it. I don't have the systems needed to test it myself at the moment. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvsup-devel port build problem (pm3-base)
John Polstra [EMAIL PROTECTED] wrote:
In article [EMAIL PROTECTED],
Brian Somers [EMAIL PROTECTED] wrote:
I sent John Polstra a similar patch some time ago Any news about
getting this committed John (P) ?
There is already an open PR with a patch. I think Mark Murray is
working on committing it. I don't have the systems needed to test
it myself at the moment.
Mark, any news on this ? FWIW, I've attached the patch that makes
things work here.
John
--
John Polstra
John D. Polstra Co., Inc.Seattle, Washington USA
Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa
Cheers.
--
Brian [EMAIL PROTECTED][EMAIL PROTECTED]
http://www.freebsd-services.com/brian@[uk.]FreeBSD.org
Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org
Index: patch-l1
===
RCS file: /home/ncvs/ports/lang/pm3-base/files/patch-l1,v
retrieving revision 1.1
diff -u -r1.1 patch-l1
--- patch-l121 Jul 2001 21:07:55 - 1.1
+++ patch-l111 Oct 2001 00:01:13 -
@@ -1,6 +1,18 @@
libs/m3core/src/runtime/FreeBSD4/RTHeapDepC.c.old Thu Jun 1 02:54:33 2000
-+++ libs/m3core/src/runtime/FreeBSD4/RTHeapDepC.c Tue Jun 12 14:07:31 2001
-@@ -693,7 +693,9 @@
+--- libs/m3core/src/runtime/FreeBSD4/RTHeapDepC.c.orig Thu Oct 11 00:59:24 2001
libs/m3core/src/runtime/FreeBSD4/RTHeapDepC.c Thu Oct 11 01:00:50 2001
+@@ -98,7 +98,11 @@
+ #include sys/time.h
+ #include nfs/rpcv2.h
+ #include nfs/nfsproto.h
++#if __FreeBSD_version = 500024
++#include nfsclient/nfs.h
++#else
+ #include nfs/nfs.h
++#endif
+ #include ufs/ufs/ufsmount.h
+ #endif
+
+@@ -693,7 +697,9 @@
void *data;
{ int result;
struct ufs_args *u_data;
@@ -10,7 +22,7 @@
struct nfs_args *n_data;
ENTER_CRITICAL;
-@@ -704,11 +706,13 @@
+@@ -704,11 +710,13 @@
MAKE_READABLE(u_data);
MAKE_READABLE(u_data-fspec);
result = syscall(SYS_mount, type, dir, flags, data);
Index: patch-l2
===
RCS file: /home/ncvs/ports/lang/pm3-base/files/patch-l2,v
retrieving revision 1.2
diff -u -r1.2 patch-l2
--- patch-l210 Sep 2001 21:37:26 - 1.2
+++ patch-l211 Oct 2001 00:04:58 -
@@ -1,6 +1,18 @@
libs/m3core/src/runtime/FBSD_ALPHA/RTHeapDepC.c.old Thu Jun 1 02:54:33 2000
-+++ libs/m3core/src/runtime/FBSD_ALPHA/RTHeapDepC.c Tue Jun 12 14:07:31 2001
-@@ -693,7 +693,9 @@
+--- libs/m3core/src/runtime/FBSD_ALPHA/RTHeapDepC.c.orig Wed May 31 18:54:24
+2000
libs/m3core/src/runtime/FBSD_ALPHA/RTHeapDepC.cThu Oct 11 00:29:03 2001
+@@ -98,7 +98,11 @@
+ #include sys/time.h
+ #include nfs/rpcv2.h
+ #include nfs/nfsproto.h
++#if __FreeBSD_version = 500024
++#include nfsclient/nfs.h
++#else
+ #include nfs/nfs.h
++#endif
+ #include ufs/ufs/ufsmount.h
+ #endif
+
+@@ -693,7 +697,9 @@
void *data;
{ int result;
struct ufs_args *u_data;
@@ -10,7 +22,7 @@
struct nfs_args *n_data;
ENTER_CRITICAL;
-@@ -704,11 +706,13 @@
+@@ -704,11 +710,13 @@
MAKE_READABLE(u_data);
MAKE_READABLE(u_data-fspec);
result = syscall(SYS_mount, type, dir, flags, data);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
buildkernel fails for advansys device
Installed 4.4 Release then pullded in the CURRENT source via cvsup yesterday (11/20). Building a kernel (after a buildworld) with device adv fails with the info below... linking kernel advansys.o: In function `adv_action': advansys.o(.text+0x246): undefined reference to `xpt_freeze_simq' advansys.o(.text+0x4fe): undefined reference to `xpt_done' advansys.o(.text+0x534): undefined reference to `xpt_done' advansys.o(.text+0x5dc): undefined reference to `xpt_done' advansys.o(.text+0x5f0): undefined reference to `xpt_done' advansys.o: In function `adv_execute_ccb': advansys.o(.text+0x614): undefined reference to `xpt_path_sim' advansys.o(.text+0x7b1): undefined reference to `xpt_freeze_simq' advansys.o(.text+0x806): undefined reference to `xpt_done' advansys.o: In function `adv_timeout': advansys.o(.text+0x8f2): undefined reference to `xpt_path_sim' advansys.o(.text+0x901): undefined reference to `xpt_print_path' advansys.o(.text+0x942): undefined reference to `xpt_freeze_simq' advansys.o(.text+0x976): undefined reference to `xpt_print_path' advansys.o(.text+0x9bd): undefined reference to `xpt_print_path' advansys.o: In function `adv_done': advansys.o(.text+0x11b5): undefined reference to `xpt_print_path' advansys.o(.text+0x12e1): undefined reference to `xpt_print_path' advansys.o(.text+0x1329): undefined reference to `xpt_freeze_devq' advansys.o(.text+0x1356): undefined reference to `xpt_done' advansys.o: In function `adv_attach': advansys.o(.text+0x14bd): undefined reference to `cam_simq_alloc' advansys.o(.text+0x14eb): undefined reference to `cam_sim_alloc' advansys.o(.text+0x150b): undefined reference to `xpt_bus_register' advansys.o(.text+0x1528): undefined reference to `xpt_create_path' advansys.o(.text+0x153f): undefined reference to `xpt_setup_ccb' advansys.o(.text+0x155d): undefined reference to `xpt_action' advansys.o(.text+0x1570): undefined reference to `xpt_bus_deregister' advansys.o(.text+0x157b): undefined reference to `cam_sim_free' advlib.o: In function `advasync': advlib.o(.text+0x39): undefined reference to `scsi_inquiry_match' advlib.o(.text+0x4b): undefined reference to `cam_quirkmatch' advlib.o(.text+0xb8): undefined reference to `xpt_path_target_id' advlib.o(.text+0xd3): undefined reference to `xpt_path_target_id' advlib.o: In function `adv_isr_chip_halted': advlib.o(.text+0xb12): undefined reference to `xpt_freeze_devq' advlib.o(.text+0xc1e): undefined reference to `xpt_freeze_devq' advlib.o: In function `adv_set_syncrate': advlib.o(.text+0xdb0): undefined reference to `xpt_setup_ccb' advlib.o(.text+0xdbf): undefined reference to `xpt_async' advlib.o: In function `adv_reset_bus': advlib.o(.text+0x1efc): undefined reference to `xpt_async' *** Error code 1 Stop in /usr/obj/usr/src/sys/MOXIE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Darren Henderson [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Observations on upgrading from 4.4-RELEASE to 5.0-CURRENT
Upgrading from a fresh 4.4-RELEASE install to 5.0-CURRENT is remarkably simple at this point in time, a couple of observations however... I did have to do an installworld before I could install a new kernel. Trying to do an installkernel first fails for lack of kldxref. Perhaps that could be committed to STABLE to make going from STABLE to CURRENT a bit simpler if it doesn't carry a huge number of dependencies? That and the lack of a /boot/device.hints file are the only complications I saw while doing the upgrade. Not a major concern obviously, just thinking in terms of when folks move from 4.x-STABLE to 5.0-RELEASE in the future. Things will of course change by then I'm sure. Something else... it seems to me that just a few weeks ago I was able to install CURRENT directly from current.freebsd.org with sysinstall after setting the release option to point to one of the 5.0 snaps, can't do that now as you can't log into that system as anonymous. Broken? No longer available? Just a fluke that I was able to do it before? Darren Henderson [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic on boot of today's -CURRENT
Date: Wed, 21 Nov 2001 08:05:18 -0800 (PST) From: David Wolfskill [EMAIL PROTECTED] Anyway, I now have my first panic on boot from -CURRENT since setting up the serial console; modulo cut/paste damage, the following ought to be fairly accurate. :-} Eh, well... my laptop came up OK after building today's -CURRENT from what ought to be the same sources. And trying to go ahead force a re-boot on the build system from my (remote) serial console didn't work too well: db panic panic: from debugger cpuid = 1; lapic.id = 0100 Debugger(panic) Stopped at 0xc03618d8: addb%al,0(%eax) db panic panic: from debugger cpuid = 1; lapic.id = 0100 boot() called on cpu#1 Uptime: 15s Automatic reboot in 15 seconds - press a key on the console to abort -- Press a key on the console to reboot -- Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs timeout stopping cpus cpu_reset: Restarting BSP cpu_reset: Failed to restart BSP and it doesn't appear to be responsive at this point. But since the laptop is up runnning: m133[1] uname -a FreeBSD m133.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #178: Wed Nov 21 09:16:17 PST 2001 root@localhost:/common/S3/obj/usr/src/sys/LAPTOP_30W i386 m133[2] it seems that the problem is much less likely of general interest. Sorry for the noise, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Observations on upgrading from 4.4-RELEASE to 5.0-CURRENT
On Wed, Nov 21, 2001 at 12:53:55PM -0500, Darren Henderson wrote: Upgrading from a fresh 4.4-RELEASE install to 5.0-CURRENT is remarkably simple at this point in time, a couple of observations however... Thanks. :-) I did have to do an installworld before I could install a new kernel. Trying to do an installkernel first fails for lack of kldxref. Perhaps that could be committed to STABLE to make going from STABLE to CURRENT a bit simpler if it doesn't carry a huge number of dependencies? Hmm, this shouldn't be a problem as of src/sys/modules/Makefile,v 1.202 failure to run kldxref(8) is not considered fatal, and kldxref is only run once after all modules are installed. That and the lack of a /boot/device.hints file are the only complications I saw while doing the upgrade. You're supposed to read src/UPDATING when doing a source upgrade. It has all the necessary info on the topic under the ``To upgrade from 4.x-stable to current'' section, including the step to setup /boot/device.hints file. [snip] Cheers, -- Ruslan Ermilov Oracle Developer/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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: buildkernel fails for advansys device
On 21-Nov-01 Darren Henderson wrote: Installed 4.4 Release then pullded in the CURRENT source via cvsup yesterday (11/20). Building a kernel (after a buildworld) with device adv fails with the info below... Do you have 'device scbus'? -- 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: buildkernel fails for advansys device
On Wed, 21 Nov 2001, John Baldwin wrote: Building a kernel (after a buildworld) with device adv fails with the info below... Do you have 'device scbus'? No, I didn't... I hate it when I miss the obvious like that. All is well now. Thanks for the respones. Darren Henderson [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: send_packet: No buffer space available
From the netstat output, it looks more like an application-level problem having to do with exhausting socket buffer space. Whatever the cause of the problem, it certainly isn't a lack of mbufs and/or clusters. Try verifying what is generating the messages. It could be coming from a syscall or, it may be that the application is printing them. If it is the latter (you should find the string in the application code), then it's fairly trivial to figure the rest out. If not, I'd check the network card driver you're using next. On Wed, Nov 21, 2001 at 05:01:16PM +0100, Andrea Campi wrote: This is a long-standing problem which is getting more and more annoying (or so I feel, might be just an impression). I was wondering if anybody might be interested in helping me debug and fix it. I can repeat this at will using Tivoli Storage Manager for Linux to backup my -CURRENT laptop. Basically, after a few minutes I start getting these messages; at that point networking is basically hosed until I kill TSM. First of all, is this just an application misbehaving and it should be fixed only by tuning some sysctl, or is it an OS bug proper? Note that -STABLE doesn't exhibit this problem. netstat -m output is as follow: mbuf usage: GEN list: 0/0 (in use/in pool) CPU #0 list:71/144 (in use/in pool) Total: 71/144 (in use/in pool) Maximum number allowed on each CPU list: 512 Maximum possible: 18432 Allocated mbuf types: 46 mbufs allocated to data 25 mbufs allocated to packet headers 0% of mbuf map consumed mbuf cluster usage: GEN list: 0/0 (in use/in pool) CPU #0 list:20/66 (in use/in pool) Total: 20/66 (in use/in pool) Maximum number allowed on each CPU list: 128 Maximum possible: 9216 0% of cluster map consumed 168 KBytes of wired memory reserved (34% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Relevant parts of vmstat -m: Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) mbufmgr6531K 32K 31594K 2687850 0 16,32,64,128,8K,32K What else is needed to diagnose this? It's been baffling me for much too long... Bye, Andrea -- Tagline generated by 'gensig' mail-client-independent .signature generator. Get your copy at http://www.geeks.com/~robf/gensig/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Bosko Milekic [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vmware fails on -current
ID == Ian Dowse [EMAIL PROTECTED] writes: ID In message [EMAIL PROTECTED], CHOI Junho writes: I'll try. Oh, I forget to say I appiled des's linux_ioctl patch. ID Ah, that's different then. I assumed from the error that you had ID revision 1.76 of linux_ioctl.c, but if that patch applied then you ID don't. Try updating your sources again; revision 1.76 is des's ID patch with a few problems fixed. You're right. I am happy with -current(21 Nov.)!. But, rtc device doesn't come up. There is no /dev/rtc entry...(there is /compat/linux/dev/rtc, but I think it is not working now..) rtc package should be updated with recent linuxulator change? ID Ian -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [sleeping now]http://www.kr.FreeBSD.org/~cjh [while sleeping] cjh @ kr.FreeBSD.ORG cjh @ FreeBSD.ORG cjh @ wdb.co.kr Korea FreeBSD Users Group www.kr.FreeBSD.org Web Data Bankwww.wdb.co.kr To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
libfetch kqueue patch
Hello - This patch converts libfetch to use kqueue instead of select. Thanks David Hill fetch-common.c.patch Description: Binary data
ACPI hangs on boot
The build and all goes well, but after a reboot. the kernel boots and just hangs on the acpi_cpu and refuses to go further. deleting the acpi.ko in /boot/kernel solves the problem for me. Is there any way to _disable_ acpi all together? I tried doing it from the boot menu (using unload and disable-module), rummaging through the /boot forth scripts also yielded no success, but it still gets loaded. Eventually just deleting the module made my box boot on. My CURRENT machine is a Compaq Presario 17XL380 laptop. Is the ACPI on that machine broken or misfeatured? Any info I can provide to help? Cheers, Emiel -- Spark's Sixth Rule for Managers: If a subordinate asks you a pertinent question, look at him as if he had lost his senses. When he looks down, paraphrase the question back at him. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI hangs on boot
The build and all goes well, but after a reboot. the kernel boots and just hangs on the acpi_cpu and refuses to go further. deleting the acpi.ko in /boot/kernel solves the problem for me. Is there any way to _disable_ acpi all together? I tried doing it from the boot menu (using unload and disable-module), rummaging through the /boot forth scripts also yielded no success, but it still gets loaded. Eventually just deleting the module made my box boot on. Answers to this question can be found (with minimal effort) in the list archives. My CURRENT machine is a Compaq Presario 17XL380 laptop. Is the ACPI on that machine broken or misfeatured? Any info I can provide to help? It's possible that it is; please post what details you have to the ACPI working list at [EMAIL PROTECTED], and we'll see what can be done to get you going. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
awk warning and MASTER_SORT_REGEX
Hi, About two weeks ago(maybe after -current awk updates), awk warns when I try to install any ports: /usr/ports/deskutils/dailystrips# make install clean dailystrips-1.0.20.tar.gz doesn't seem to exist in /usr/ports/distfiles/. awk: cmd. line:1: warning: escape sequence `\.' treated as plain `.' And I have the following enties in /etc/make.conf: MASTER_SORT_REGEX=^file: ://[^/]*\.kr/ ://[^/]*\.kr\. ^ftp://ftp\.FreeBSD\.org/pub/FreeBSD/ports/local-distfiles/ It doesn't affect ports process(ports works well), but I think it can be removed for cleaner output... -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho [sleeping now]http://www.kr.FreeBSD.org/~cjh [while sleeping] cjh @ kr.FreeBSD.ORG cjh @ FreeBSD.ORG cjh @ wdb.co.kr Korea FreeBSD Users Group www.kr.FreeBSD.org Web Data Bankwww.wdb.co.kr To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: damaged file system despite unmounts
I recently [this week] had to revert to a tape backup of an out-of-sync /var because yet again, /var got mangled on 'shutdown -r now', this time, and I reported this to the list the first time this happened, is the second time I have had to do this, so this seems to be an ongoing issue. I have also receieved a lot of master superblock bad notices and had to manually fix those in between the two occurrances [the first was several months ago], anyhow, just like the first time, I got the master superblock bad warning, as well as the invalid label message. For some reason this always happens with /var, yet with no other filesystem. This time I newfs'ed without softupdates. We'll see what happens. David W. Chapman Jr. wrote: On Wed, Nov 21, 2001 at 09:17:13AM -0500, Mikhail Teterin wrote: For a while I was noticing my largest FS reported as not unmounted cleanly on boot. Today I decided to unmount it myself and check it with fsck. Here are the results. Notice, that the first fsck had to mark the FS clean. Notice that the second fsck found something else to do, and only the third one was happy. What's happening? Thanks, -mi I noticed this a while ago on -current. I haven't checked recently, but I do remember having this problem jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - Religious fundamentalism is the biggest threat to international security that exists today. United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: damaged file system despite unmounts
I have softupdates, wc and tags enabled, just FYI I recently [this week] had to revert to a tape backup of an out-of-sync /var because yet again, /var got mangled on 'shutdown -r now', this time, and I reported this to the list the first time this happened, is the second time I have had to do this, so this seems to be an ongoing issue. I have also receieved a lot of master superblock bad notices and had to manually fix those in between the two occurrances [the first was several months ago], anyhow, just like the first time, I got the master superblock bad warning, as well as the invalid label message. For some reason this always happens with /var, yet with no other filesystem. This time I newfs'ed without softupdates. We'll see what happens. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: damaged file system despite unmounts
On Wed, Nov 21, 2001 at 09:17:13AM -0500, Mikhail Teterin wrote: For a while I was noticing my largest FS reported as not unmounted cleanly on boot. Today I decided to unmount it myself and check it with fsck. Here are the results. Notice, that the first fsck had to mark the FS clean. Notice that the second fsck found something else to do, and only the third one was happy. What's happening? Thanks, -mi I noticed this a while ago on -current. I haven't checked recently, but I do remember having this problem -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
