RE: gcc -O broken in CURRENT
Hello... isn't anyone workin on this prob? Or do i have a leak in my mailbox? Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jan Stocker Sent: Wednesday, March 06, 2002 9:15 AM To: Martin Blapp; [EMAIL PROTECTED] Subject: RE: gcc -O broken in CURRENT This can be reproduced on my system and it may be a big problem. I installed everthing from source with -O set in make.conf and some proggys running fine under 4.4 wont unter -current. Recompiling the proggys without -O dont fix it but maybe it is caused by some libs... Is anyone examining this problem? Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Blapp Sent: Monday, March 04, 2002 9:02 PM To: [EMAIL PROTECTED] Subject: gcc -O broken in CURRENT Hi all, Unfortunatly I have a example from the ports, needed by OpenOffice port (work in progress) cd /usr/ports/devel/stlport/ make install cd /usr/ports/devel/stlport/work/STLport-4.5.3/test/eh gmake -f gcc-freebsd.mak [vector] :testing n-size constructor (const) ... 95 try successful [vector] :testing pointer range constructor (const) ... Bus error - core dumped Then remove the three -O from gcc-freebsd.mak and run it again. You will see that all tests are successfully done. [...] [hash_multiset] :testing default constructor (const) ... 2 try successful [hash_multiset] :testing iterator range n-size constructor (const) ... 127 try successful [hash_multiset] :testing copy constructor (const) ... 54 try successful [hash_multiset] :testing assignment operator (weak) ... 53 try successful [...] [string] :testing copy constructor (const) ... 2 try successful [string] :testing assignment operator (weak) ... 1 try successful EH test : Done Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ping with usec resolution
I'm looking for a ping with usec (microsecond) resolution (as Redhat 7.2 is using). Could FreeBSD have it too? Anyone got the source for it? We want to build up a small experiment for students to measure the speed of light using ping. Found this neat story on the net btw. http://ftp.arl.mil/~mike/ping.html -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ping with usec resolution
I'm looking for a ping with usec (microsecond) resolution (as Redhat 7.2 is using). Could FreeBSD have it too? Anyone got the source for it? FreeBSD's ping has had microsecond resolution since version 1. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com President, Download Technologies, Inc. - http://www.downloadtech.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ping with usec resolution
On Mon, Mar 11, 2002 at 02:11:51AM -0800, David Greenman wrote: I'm looking for a ping with usec (microsecond) resolution (as Redhat 7.2 is using). Could FreeBSD have it too? Anyone got the source for it? FreeBSD's ping has had microsecond resolution since version 1. Oh yeah. Sorry. I totally overlooked. Its just the format that changes (dynamically to usec when it falls below 1 ms) in the linux version. Thanks. -- -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com President, Download Technologies, Inc. - http://www.downloadtech.com Pave the road of life with opportunities. -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
4-5 REL - 5.0 CUR
I tried to install a new current from a minimal installed 4.5 RELEASE and cvsuped source tree. $ cd /usr/src $ make -DNOPROFILE=true -DNO_WERROR buildworld ... $ make buildkernel KERNCONF=GENERIC ... $ make installkernel KERNCONF=GENERIC ... install -c -o root -g wheel -m 555 vesa.ko /boot/kernel/ === wi install -c -o root -g wheel -m 555 if_wi.ko /boot/kernel/ === xe install -c -o root -g wheel -m 555 if_xe.ko /boot/kernel/ kldxref /boot/kernel kldxref:No such file or directory *** Error code 1 (ignored) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4-5 REL - 5.0 CUR
On Mon, Mar 11, 2002 at 12:32:26PM +0100, Jan Stocker wrote: I tried to install a new current from a minimal installed 4.5 RELEASE and cvsuped source tree. $ cd /usr/src $ make -DNOPROFILE=true -DNO_WERROR buildworld ... $ make buildkernel KERNCONF=GENERIC ... $ make installkernel KERNCONF=GENERIC ... install -c -o root -g wheel -m 555 vesa.ko /boot/kernel/ === wi install -c -o root -g wheel -m 555 if_wi.ko /boot/kernel/ === xe install -c -o root -g wheel -m 555 if_xe.ko /boot/kernel/ kldxref /boot/kernel kldxref:No such file or directory *** Error code 1 (ignored) make can't find kldxref, because kldxref is part of 5.0, not 4.X Man page of kldxref online: http://www.FreeBSD.org/cgi/man.cgi?query=kldxrefapropos=0sektion=0manpath=FreeBSD+5.0-currentformat=html If you don't like this bug: 1st way: touch /usr/sbin/kldxref 2nd way: 1) install libc.so.5 into /usr/lib 2) ldconfig -m /usr/lib 3) install kldxref from /usr/src/usr.sbin/kldxref after 1st or 2nd way try to install kernel one more time. -- Rgdz,/\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN [EMAIL PROTECTED]X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can someone explain this change to bsd.lib.mk ?
On Fri, Mar 08, 2002 at 11:13:46AM -0800, Luigi Rizzo wrote:
The attached portion of the 1.100 - 1.101 patch to src/share/mk/bsd.lib.mk
(and a similar one in bsd.prog.mk 1.103 - 1.104) broke cross builds
of PicoBSD, specifically preventing the cross-environment header
files to be found when building libraries/programs. You can reproduce
this by doing
picobsd --src HEAD/src --init -n -v
on a recently cvsupped HEAD tree.
I wonder, how does a make world get around this problem
(so i can try to reproduce the 'fix' in the picobsd script) ?
@@ -37,11 +37,6 @@ SHLIB_NAME?= lib${LIB}.so.${SHLIB_MAJOR}
.endif
.endif
-.if defined(DESTDIR) !defined(BOOTSTRAPPING)
-CFLAGS+= -I${DESTDIR}/usr/include
-CXXINCLUDES+= -I${DESTDIR}/usr/include/g++
-.endif
-
.if defined(DEBUG_FLAGS)
CFLAGS+= ${DEBUG_FLAGS}
.endif
DESTDIR has been abused for build purposes for a long time while, by design,
it should have only affected the installation. `buildworld' builds special
(cross) versions of compiler and tools that look things up under TOOLS_PREFIX.
As indicated in the commitlog for a relevant change to Makefile.inc1,v 1.240:
: (Attempt to move the -nostdinc -I... part of CFLAGS into the new CINCLUDES
: (modeled after a similar CXXINCLUDES) eventually failed because hard-coding
: ${WORLDTMP}/usr/include to be the first in the include list does not always
: work, e.g. lib/libbind.)
Because building of special versions of compiler and tools may not be easy
in picobsd, the following patch works around the problem in libbind and
should make things happy again:
Index: release/picobsd/build/picobsd
===
RCS file: /home/ncvs/src/release/picobsd/build/picobsd,v
retrieving revision 1.22
diff -u -p -r1.22 picobsd
--- release/picobsd/build/picobsd 8 Mar 2002 02:24:21 - 1.22
+++ release/picobsd/build/picobsd 11 Mar 2002 12:29:38 -
@@ -151,15 +151,15 @@ create_includes_and_libraries() {
mkdir -p ${l_usrtree}/share/misc # a few things go here
mkdir -p ${l_usrtree}/lib # libraries
mkdir -p ${l_usrtree}/sbin # some binaries
-(cd ${SRC}; INCOWN=`id -un` BINOWN=`id -un` DESTDIR=${SRC}/.. \
+(cd ${SRC}; INCOWN=`id -un` BINOWN=`id -un` DESTDIR=${l_usrtree}/.. \
make -m ${SRC}/share/mk includes ) || fail $? includes
-# libraries already have the include path in the Makefile
-CFLAGS=-nostdinc ; export CFLAGS
+# Pick up the correct headers for libraries.
+CFLAGS=-nostdinc -I${l_usrtree}/include ; export CFLAGS
(cd ${SRC}
# $e is the invocation of make with correct environment
e=MAKEOBJDIRPREFIX=${l_objtree}/picobsd/libraries \
- INCOWN=`id -un` BINOWN=`id -un` DESTDIR=${SRC}/.. \
+ INCOWN=`id -un` BINOWN=`id -un` DESTDIR=${l_usrtree}/.. \
make -m ${SRC}/share/mk \
-DNOHTML -DNOINFO -DNOMAN -DNOSHARE -DNOFSCHG
# need to 'make obj' in a few places. This is very
Index: lib/libbind/Makefile
===
RCS file: /home/ncvs/src/lib/libbind/Makefile,v
retrieving revision 1.5
diff -u -p -r1.5 Makefile
--- lib/libbind/Makefile30 Nov 1999 04:40:54 - 1.5
+++ lib/libbind/Makefile11 Mar 2002 12:29:38 -
@@ -2,9 +2,6 @@
BIND_DIR=${.CURDIR}/../../contrib/bind
-# contrib/bind/include/* must not override any real system includes
-CFLAGS+= -I${BIND_DIR}/port/freebsd/include -I${BIND_DIR}/include
-
LIB= bind
WANT_IRS= for now
@@ -86,3 +83,6 @@ NOPIC=true
INTERNALSTATICLIB= true
.include bsd.lib.mk
+
+# XXX contrib/bind/include/* must not override any real system includes
+CFLAGS:= -I${BIND_DIR}/port/freebsd/include -I${BIND_DIR}/include ${CFLAGS}
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
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RE: 4-5 REL - 5.0 CUR
ops of cource copied the hints file too -Original Message- From: Jan Stocker [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 12:32 PM To: freebsd-current@FreeBSD. ORG Subject: 4-5 REL - 5.0 CUR I tried to install a new current from a minimal installed 4.5 RELEASE and cvsuped source tree. $ cd /usr/src $ make -DNOPROFILE=true -DNO_WERROR buildworld ... $ make buildkernel KERNCONF=GENERIC ... $ make installkernel KERNCONF=GENERIC ... install -c -o root -g wheel -m 555 vesa.ko /boot/kernel/ === wi install -c -o root -g wheel -m 555 if_wi.ko /boot/kernel/ === xe install -c -o root -g wheel -m 555 if_xe.ko /boot/kernel/ kldxref /boot/kernel kldxref:No such file or directory *** Error code 1 (ignored) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can someone explain this change to bsd.lib.mk ?
On Sat, Mar 09, 2002 at 12:43:16AM -0800, Luigi Rizzo wrote: On Fri, Mar 08, 2002 at 12:26:16PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Luigi Rizzo writes: : The attached portion of the 1.100 - 1.101 patch to src/share/mk/bsd.lib.mk ... : I wonder, how does a make world get around this problem : (so i can try to reproduce the 'fix' in the picobsd script) ? Make world gets around this problem by doing things in stages so that the build tools are built first using the host environment, then the target binaries are built using the host tools. you mean the newly built tools, right ? Yep. -- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrading to 5-CURRENT via sources
On Sat, Mar 09, 2002 at 05:16:48PM -0800, Lamont Granquist wrote: So, I've got a CVS checkout of 5-CURRENT on my 4.5-STABLE box and I'd like to upgrade to a spare partition that I have on the machine (making it dual boot). Can I just do: make world DESTDIR=/mnt/tmp And then build + drop the kernel into place + reboot? Yes. -- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4-5 REL - 5.0 CUR
jstocker kldxref /boot/kernel jstocker kldxref:No such file or directory jstocker *** Error code 1 (ignored) See the message (ignored). It is the intentional behavior. If you don't like this, make NO_XREF=YES installkernel will help you. Check src/sys/conf/kmod.mk for more details. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage - NOT ONLY
On Sat, 9 Mar 2002, Vallo Kallaste wrote: - On Sat, Mar 09, 2002 at 09:42:07PM +0100, Olivier Houchard [EMAIL PROTECTED] wrote: - Tried without XIM support only, then without multibyte, fontset and - XIM support, no joy. Exactly same linkage happens. Perhaps I should - also note that using Motif for GUI will not change anything. I have a very similar problem with windowmaker, xv and perhaps few other X11 applications. I also have a window manager compiled from x11-wM/phluid port. They all dump core attempting to dlopen(): (example from phluid) #0 0x280530be in reloc_non_plt () /usr/libexec/ld-elf.so.1 #1 0x28050b00 in find_symdef () from /usr/libexec/ld-elf.so.1 #2 0x28051097 in dlopen () from /usr/libexec/ld-elf.so.1 #3 0x28252bbb in sys_dl_open () from /usr/local/lib/libltdl.so.1 #4 0x2825313e in tryall_dlopen () from /usr/local/lib/libltdl.so.1 #5 0x282540c0 in lt_dlopen () from /usr/local/lib/libltdl.so.1 #6 0x28254395 in lt_dlopenext () from /usr/local/lib/libltdl.so.1 #7 0x28076558 in __imlib_ProduceLoader () from /usr/X11R6/lib/libImlib2.so.1 #8 0x28076bf7 in __imlib_LoadAllLoaders () from /usr/X11R6/lib/libImlib2.so.1 #9 0x28076b69 in __imlib_RescanLoaders () from /usr/X11R6/lib/libImlib2.so.1 #10 0x28076f28 in __imlib_LoadImage () from /usr/X11R6/lib/libImlib2.so.1 #11 0x28084d64 in imlib_load_image () from /usr/X11R6/lib/libImlib2.so.1 #12 0x804b167 in imlib_context_set_color () #13 0x80496e6 in imlib_context_set_color () #14 0x804963d in imlib_context_set_color () This is current installed from scratch from one of the late february snaphots, with world updated every so-often (2-3 days max). New make buildworld with -g in progress now. I even recompiled XFree86-4 (4.1.0 port) and it didn't help. -- Marcin Cielak // [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gvim weird linkage - NOT ONLY
The stack trace below shows exactly the symptoms of the binutils DT_TEXTREL bug, which has been fixed by the latest vendor import. Rebuilding world IS NOT ENOUGH to solve the problem. You will need to rebuild all the incorrect libraries which have been built with broken binutils before. Libpng is the only such library I found so far. Programs, linked with imlib are crashing when trying to dynamically load libppng, most likely. #0 0x280530be in reloc_non_plt () /usr/libexec/ld-elf.so.1 #1 0x28050b00 in find_symdef () from /usr/libexec/ld-elf.so.1 #2 0x28051097 in dlopen () from /usr/libexec/ld-elf.so.1 #3 0x28252bbb in sys_dl_open () from /usr/local/lib/libltdl.so.1 #4 0x2825313e in tryall_dlopen () from /usr/local/lib/libltdl.so.1 #5 0x282540c0 in lt_dlopen () from /usr/local/lib/libltdl.so.1 #6 0x28254395 in lt_dlopenext () from /usr/local/lib/libltdl.so.1 #7 0x28076558 in __imlib_ProduceLoader () from /usr/X11R6/lib/libImlib2.so.1#8 0x28076bf7 in __imlib_LoadAllLoaders () from /usr/X11R6/lib/libImlib2.so.1#9 0x28076b69 in __imlib_RescanLoaders () from /usr/X11R6/lib/libImlib2.so.1#10 0x28076f28 in __imlib_LoadImage () from /usr/X11R6/lib/libImlib2.so.1#11 0x28084d64 in imlib_load_image () from /usr/X11R6/lib/libImlib2.so.1#12 0x804b167 in imlib_context_set_color ()#13 0x80496e6 in imlib_context_set_color () #14 0x804963d in imlib_context_set_color () To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On 08-Mar-02 Wilko Bulte wrote: On Fri, Mar 08, 2002 at 01:35:47PM -0800, Matthew Jacob wrote: And FWIW, alpha kernels on some Uniprocessor boxes freeze up. Yes. Or panic. See my posts earlier this week. I managed to get 2 buildworlds without accidents, but all make release attempts either paniced or froze. We should turn preemption back off again. :-/ -- 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: ping with usec resolution
Christoph Kukulies wrote: On Mon, Mar 11, 2002 at 02:11:51AM -0800, David Greenman wrote: I'm looking for a ping with usec (microsecond) resolution (as Redhat 7.2 is using). Could FreeBSD have it too? Anyone got the source for it? FreeBSD's ping has had microsecond resolution since version 1. Oh yeah. Sorry. I totally overlooked. Its just the format that changes (dynamically to usec when it falls below 1 ms) in the linux version. This would make it harder to write scripts that process the output in mixed formats. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can someone explain this change to bsd.lib.mk ?
In message: [EMAIL PROTECTED] Luigi Rizzo [EMAIL PROTECTED] writes: : On Fri, Mar 08, 2002 at 12:26:16PM -0700, Warner Losh wrote: : In message [EMAIL PROTECTED] Luigi Rizzo writes: : : The attached portion of the 1.100 - 1.101 patch to src/share/mk/bsd.lib.mk : ... : : I wonder, how does a make world get around this problem : : (so i can try to reproduce the 'fix' in the picobsd script) ? : : Make world gets around this problem by doing things in stages so that : the build tools are built first using the host environment, then the : target binaries are built using the host tools. : : you mean the newly built tools, right ? Yes. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panics with CardBus
I get panics for about 2 weeks (last tested with todays current - it's more unstable than friday's build - it crashed only when boot_verbose was set, now it sometimes crashes several times in a row). The panics occur on 2 places - on detection/insertion in device_get_parent() or bus_deactivate_resource() and on removal in bus_deactivate_resource(). I can provide more info as needed (don't know what to look for and don't want to make the mail even longer). Sorry for inappropriate linewrap and long email. Trimmed dmesg output (without the card in slot): - Preloaded elf kernel /boot/kernel/kernel at 0xc043f000. Preloaded elf module /boot/kernel/acpi.ko at 0xc043f0a8. Calibrating clock(s) ... TSC clock: 365868380 Hz, i8254 clock: 1193211 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 Timecounter TSC frequency 365861690 Hz CPU: Pentium II/Pentium II Xeon/Celeron (365.86-MHz 686-class CPU) Origin = GenuineIntel Id = 0x66a Stepping = 10 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00466000 - 0x07fe7fff, 129507328 bytes (31618 pages) avail memory = 125992960 (123040K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fa000 bios32: Entry = 0xf (c00f) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x478 pnpbios: Found PnP BIOS data at 0xc00f5a70 pnpbios: Entry = f:5a9e Rev = 1.0 pnpbios: Event flag at f5a96 pnpbios: OEM ID 30b1110e Other BIOS signatures found: null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 22 00 00 01 7f 00 00 01 0b 01 00 01 21 01 00 01 2a 01 00 01 00 01 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 05 01 16 01 17 01 18 01 07 01 19 01 VESA: 40 mode(s) found VESA: v2.0, 8128k memory, flags:0x0, mode table:0xc038a662 (122) VESA: ATI MACH64 VESA: ATI Technologies Inc. MACH64RM 01.00 pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) Using $PIR table, 268435454 entries at 0xc00f0970 npx0: math processor on motherboard npx0: INT 16 interface acpi0: COMPAQ RSDB130 on motherboard acpi0: power button is handled as a fixed feature programming model. ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 2, max = 6, width = 5 ACPI timer looks BAD min = 1, max = 6, width = 6 ACPI timer looks BAD min = 2, max = 16777187, width = 16777186 ACPI timer looks BAD min = 2, max = 16777197, width = 16777196 ACPI timer looks BAD min = 1, max = 16777214, width = 16777214 Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x5008-0x500b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_acad0: AC adapter on acpi0 unknown: not probed (disabled) sage repeated 19 times pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: physical bus=0 map[10]: type 3, range 32, base 5000, size 26, enabled found- vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 found- vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 map[10]: type 1, range 32, base 7fffe000, size 12, enabled found- vendor=0x104c, dev=0xac1b, revid=0x03 bus=0, slot=4, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 7000, size 12, enabled found- vendor=0x104c, dev=0xac1b, revid=0x03 bus=0, slot=4, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 found- vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-80-00, hdrtype=0x00, mfdev=1 map[20]: type 4, range 32, base 3820, size 4, enabled found- vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 map[20]: type 4, range 32, base 3800, size 5, enabled found- vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 intpin=d, irq=11 map[90]: type 4, range 32, base 4000, size 4, enabled found- vendor=0x8086, dev=0x7113, revid=0x02 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 map[10]: type 4, range 32, base 3000, size 8, enabled found- vendor=0x125d, dev=0x1978, revid=0x10 bus=0, slot=8, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 intpin=a, irq=11
Re: panics with CardBus
On Mon, 11 Mar 2002, Michal Mertl wrote: I get panics for about 2 weeks (last tested with todays current - it's more unstable than friday's build - it crashed only when boot_verbose was set, now it sometimes crashes several times in a row). I was about to post about the same problems. I am using -CURRENT as of last week, and have three different PCMCIA cards which cause me problems. The first is also a Xircom 10/100 RBE-100 cardbus card (though mine has no serial port) If bootverbose=0, no panic occurs. (though the dc driver still fails to attach it, being unable to find a PHY). With bootverbose=1, inserting the card will panic the machine. pci_print_verbose() calls pci_read_config while cfg-dev=0x0, and so device_get_parent() blows up. The second card I have, GlobalVillage Powerport Platinum Pro A390 combined modem and ethernet card, will panic upon insert with a page fault in pccard_scan_cis with a page fault. The page fault is caused by trying to read memory location zero through pccard_cis_read_1 (/usr/src/sys/dev/pccard/pccard_cis.c v1.18 line 155) The third card I have, a Hayes PCMCIA modem, will hang the laptop solid after being detected correctly and after printing the sio4: line. As a possible datapoint, the latter two cards have no problem under -STABLE. I am happy to supply the vmcore and kernel files to people who contact me off list, and am also able to post the cards to anyone who I know as a FreeBSD developer as long as I get them back... Thanks, Gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Warnings in my bootup (dmesg.boot)
Hi all, I updated my kernel two days ago, and I am having some weird warnings, which I haven't seen before. Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Mar 9 18:43:51 GMT 2002 [EMAIL PROTECTED]:/c1/obj/data/dev/src/sys/CURRENT5 Preloaded elf kernel /boot/kernel/kernel at 0xc03be000. Preloaded elf module /boot/kernel/acpi.ko at 0xc03be0a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 730807620 Hz CPU: Pentium III/Pentium III Xeon/Celeron (730.81-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE WARNING: Driver mistake: make_dev(perfmon) called before SI_SUB_DRIVERS -- I have configured my kernel with the PERFMON option. -- real memory = 536870912 (524288K bytes) avail memory = 516808704 (504696K bytes) Pentium Pro MTRR support enabled VESA: v3.0, 32768k memory, flags:0x1, mode table:0xc031fb02 (122) VESA: NVidia Using $PIR table, 8 entries at 0xc00f7100 ACPI-0161: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES -- does the above mean ACPI is having problems? -- rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:10:a7:04:d7:91 -- Why would it be unstable in autoselect mode? -- And also, what does kernel profiling (profile option) really mean, and what would be the use of it? Thanks, -- Hiten Pandya http://jfs4bsd.sf.net - JFS for FreeBSD (JFS4BSD) http://www.FreeBSD.org - The Power to Serve msg35958/pgp0.pgp Description: PGP signature
Re: Warnings in my bootup (dmesg.boot)
Hiten Pandya wrote: I updated my kernel two days ago, and I am having some weird warnings, which I haven't seen before. [ ... ] WARNING: Driver mistake: make_dev(perfmon) called before SI_SUB_DRIVERS -- I have configured my kernel with the PERFMON option. -- This means that it's trying to register a driver with a subsystem that has not yet been initialized. You probably need to split it off, and initialize it seperately ysing a SYSINIT in the SI_SUB_DRIVERS, SI_ORDER_ANY. If you have trouble doing this, let me know, and I can take a look at it for you (it's going to be a bit of a pain if it's allowed to be loaded later; if so, the easiest thing to do is to simply load it later, e.g. in /etc/rc.local). Using $PIR table, 8 entries at 0xc00f7100 ACPI-0161: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES -- does the above mean ACPI is having problems? -- Probably; if you can break this out as a seperate problem report and Cc: Mike Smith, it's much more likely to be fixed; he owns the ACPI stuff. rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:10:a7:04:d7:91 -- Why would it be unstable in autoselect mode? -- Because Realtek adapters with that chipset are known to have problems with autoselect. The easiest fix is to ignore it (if you don't have problems) or specify the settings on the ifconfig line (if you do). And also, what does kernel profiling (profile option) really mean, and what would be the use of it? If you have to ask, you should probably disable it. 8-). See the handbook for more information on kernel profiling, if you are curious. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Warnings in my bootup (dmesg.boot)
On Mon, Mar 11, 2002 at 11:55:34AM -0800, Terry Lambert wrote: This means that it's trying to register a driver with a subsystem that has not yet been initialized. You probably need to split it off, and initialize it seperately ysing a SYSINIT in the SI_SUB_DRIVERS, SI_ORDER_ANY. If you have trouble doing this, let me know, and I can take a look at it for you (it's going to be a bit of a pain if it's allowed to be loaded later; if so, the easiest thing to do is to simply load it later, e.g. in /etc/rc.local). Hmm. AFAIK, All I did was to add the PERFMON driver to the kernel configuration file, and when I compiled and installed the kernel, and booted ofcourse, it came up with the error. Because Realtek adapters with that chipset are known to have problems with autoselect. The easiest fix is to ignore it (if you don't have problems) or specify the settings on the ifconfig line (if you do). Already done. Thanks. :) Also, I am going to CC the ACPI stuff to Mike Smith sometime today (after I eat). :) Regards, -- Hiten Pandya http://jfs4bsd.sf.net - JFS for FreeBSD (JFS4BSD) http://www.FreeBSD.org - The Power to Serve msg35960/pgp0.pgp Description: PGP signature
rtld messing up?
Hi Here is kaffe (from ports) post mortem after an at-load blowup. #0 0x280520ee in reloc_non_plt (obj=0x28064500, obj_rtld=0x280604a0) at /usr/src/libexec/rtld-elf/i386/reloc.c:196 196 *where += (Elf_Addr) obj-relocbase; (gdb) where #0 0x280520ee in reloc_non_plt (obj=0x28064500, obj_rtld=0x280604a0) at /usr/src/libexec/rtld-elf/i386/reloc.c:196 #1 0x2804fb30 in relocate_objects (first=0x28064000, bind_now=0 '\000') at /usr/src/libexec/rtld-elf/rtld.c:1398 #2 0x2804e663 in _rtld (sp=0xbfbffa58, exit_proc=0xbfbffa50, objp=0xbfbffa54) at /usr/src/libexec/rtld-elf/rtld.c:380 Other ports (like QT2) are also doing this. Any ideas? M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn #application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf #text/plain; name=cv.txt [Mark Murray CV Plain Text] cv.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Serial break into debugger broken from 'cu' on -CURRENT?
Bruce Evans [EMAIL PROTECTED] wrote: The -current cu is a crock of tip. It has more missing features, compared to the Taylor version, like the unability to run an external program with stdin and stdout piped to the remote end simultaneously (like a local sz Z-modem program), plus it has this annoying startup message can't open log file /var/log/aculog (why should it be able to open it at all?). I wish the Taylor version hadn't been thrown overboard at all. We used to have two alternatives, cu and tip. Now we only have tip and tip. :( (I doubt tip has actually less security bugs than Taylor cu. If we threw out all the BSD-originating programs that once experienced a security problem, we would rather quickly end up with a skeleton that could hardly be named `Unix' anymore...) This is bug for bug compatible with the V7 cu except for the unusably slow speed of 9600. For perfect brokenness, the default speed should be 300. *ROTFL* -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
the zlib double free bug: Belived harmless with phkmalloc
---BeginMessage---
I just sent this to security-officer.
Please notice that if you have ports or applications linked with
other allocators than the libc malloc from FreeBSD this statement
does not apply.
Poul-Henning
--- Forwarded Message
To: [EMAIL PROTECTED]
Subject: the zlib double free bug
From: Poul-Henning Kamp [EMAIL PROTECTED]
Date: Mon, 11 Mar 2002 23:13:57 +0100
Message-ID: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
As author of our malloc(3) it is my opinion that we are not vulnerable to
this (kind of) bug.
Most mallocs keep their housekeeping data right next to the allocated
range. This gives rise to all sorts of unpleassant situations if
programs stray outside the dotted line, free(3) things twice or
free(3) modified pointers.
phkmalloc(3) does not store housekeeping next to allocated data,
and in particular it has code that detects and complains about
exactly the kind of double free this advisory talks about:
critter phk cat a.c
main()
{
char *p;
p = malloc(256);
p = malloc(256);
free(p);
free(p);
}
critter phk make a
cc -O -pipe a.c -o a
a.c: In function `main':
a.c:7: warning: assignment makes pointer from integer without a cast
a.c:8: warning: assignment makes pointer from integer without a cast
critter phk ./a
a in free(): error: chunk is already free
Abort (core dumped)
critter phk
The malloc flag 'A' determines if the situation is just warned about
or if the program should call abort(3).
- --
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
--- End of Forwarded Message
---End Message---
Re: Serial break into debugger broken from 'cu' on -CURRENT?
On Mon, Mar 11, 2002 at 10:43:22PM +0100, Joerg Wunsch wrote: Bruce Evans [EMAIL PROTECTED] wrote: used to have two alternatives, cu and tip. Now we only have tip and tip. :( (I doubt tip has actually less security bugs than Taylor cu. If we threw out all the BSD-originating programs that once experienced a security problem, we would rather quickly end up with a skeleton that could hardly be named `Unix' anymore...) This is bug for bug compatible with the V7 cu except for the unusably slow speed of 9600. For perfect brokenness, the default speed should be 300. *ROTFL* Duh... goes hunting for the ASR33 to verify this. Strange that it isn't 110baud :-P -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM code ready for testing
Hi, On Mon, 2002-03-11 at 06:34, Poul-Henning Kamp wrote: The GEOM code is now ready for early testing: Would GEOM support accessing a device via multiple paths? (ie could we write a method that would do that?) My current situation is that I have a couple of IBM ESS F20 Sharks each with 3 fibre channel cards hooked to 3 brocade switches. When I allocate a LUN out of either shark it appears as 3 separate devices. IBM ship software called SDD that provides a single virtual device VPATH on NT, Solaris and AIX and load balances. At the moment when I hook up a FreeBSD box I just select one of the devices and ignore the others. Mildly annoying and I have to bring down the FreeBSD boxes when we upgrade the microcode on the shark. Carl. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Call for UMA (allocator) testers.
I have received a few reports of panics when loading modules. If you're going to run it you may want to staticly compile in pseudofs/procfs, etc. Thanks, Jeff On Sun, 10 Mar 2002, Glenn Gombert wrote: I have the UMA patch installed on two systems here, a 500Mhz K7 system and dual PIII SMP box, both of which have WITNESS and INVARIANTS configured in the kernel. I will run them for the next few days, and report anything that looks unusual in operation :) GG. I'd like people to test with WITNESS and INVARIANTS, although with these options on it is somewhat slower than the original kernel. With these disabled it is on par. If you have a SMP machine you will get witness warnings if you run low on memory. There is no real problem except that witness doesn't understand that the condition is safe. If you do test this patch, please send me an email so I know how many people are using this. If you get a lock order violation other than acquring duplicate lock of same type please let me know. If you get a panic, please give me a stack trace (tr in ddb) and the output of call uma_print_stats in the debugger if that is possible. This has been debugged and tested over several months so it is quite stable for me. Hopefully it will be stable for you too. :-) The patch and new files are available at: http://www.chesapeake.net/~jroberson/uma.tar Untar into src/sys and apply the patch. After you rerun config you should be ready to compile. Thanks, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Glenn Gombert [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Call for UMA (allocator) testers.
On Mon, Mar 11, 2002 at 06:24:08PM -0500, Jeff Roberson wrote: I have received a few reports of panics when loading modules. If you're going to run it you may want to staticly compile in pseudofs/procfs, etc. Jeff, There were problems with loading modules, but I haven't seen any panics. The loading problems were fixed yesterday in revisions 1.77 and 1.78 of kern_linker.c. I suspect people, who imay have had panics, need to update to the latest version of kern_linker.c. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Call for UMA (allocator) testers.
There were problems with loading modules, but I haven't seen any panics. The loading problems were fixed yesterday in revisions 1.77 and 1.78 of kern_linker.c. I suspect people, who imay have had panics, need to update to the latest version of kern_linker.c. -- Steve Good news for me. Thanks, I haven't caught up on my commit mail yet. I'll make sure this fixes the panic for me as soon as I get home. For those of you that saw the panic, can you update this file and try again? Thanks, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Call for UMA (allocator) testers.
On Mon, Mar 11, 2002 at 06:36:53PM -0500, Jeff Roberson wrote: There were problems with loading modules, but I haven't seen any panics. The loading problems were fixed yesterday in revisions 1.77 and 1.78 of kern_linker.c. I suspect people, who imay have had panics, need to update to the latest version of kern_linker.c. Good news for me. Thanks, I haven't caught up on my commit mail yet. I'll make sure this fixes the panic for me as soon as I get home. For those of you that saw the panic, can you update this file and try again? Whoops, revisions 1.78 and 1.79. Damn off-by-one errors :-) -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Warnings in my bootup (dmesg.boot)
Hiten Pandya wrote:
On Mon, Mar 11, 2002 at 11:55:34AM -0800, Terry Lambert wrote:
This means that it's trying to register a driver with a
subsystem that has not yet been initialized. You probably
need to split it off, and initialize it seperately ysing a
SYSINIT in the SI_SUB_DRIVERS, SI_ORDER_ANY. If you have
trouble doing this, let me know, and I can take a look at
it for you (it's going to be a bit of a pain if it's allowed
to be loaded later; if so, the easiest thing to do is to
simply load it later, e.g. in /etc/rc.local).
Hmm. AFAIK, All I did was to add the PERFMON driver to the kernel
configuration file, and when I compiled and installed the kernel, and
booted ofcourse, it came up with the error.
Yes.
The perfmon_init() in /sys/i386/i386/perfmon.c makes a call to
make_dev(). With devfs, you can't call this until the device
subsystem has been initialized.
The perfmon_init() is called from /sys/i386/i386/machdep.c in
cpu_startup(), which is called as a result of:
SYSINIT(cpu, SI_SUB_CPU, SI_ORDER_FIRST, cpu_startup, NULL)
which happens before SI_SUB_DRIVERS.
So to fix it, you would split the perfmon_init into a
perfmon_init() and a perfmon_init_dev(). The perfmon_init_dev()
code (in perfmon.c) would look like:
static void perfmon_init_dev __P((void *));
SYSINIT(cpu, SI_SUB_DRIVERS, SI_ORDER_ANY, perfmon_init_dev, NULL)
/* ARGSUSED */
static void
perfmon_init_dev(dummy)
void *dummy;
{
make_dev(perfmon_cdevsw, 32, UID_ROOT, GID_KMEM,
0640, perfmon);
}
The SI_ORDER_ANY makes it the lowest priority to happen at
SI_SUB_DRIVERS, which guaranteees that it's called *after*,
which avoids the problem.
In other words, it's a pretty rivial hack.
If someone wants to commit the code, the code I've listed
above is pretty much exactly what you'd need.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Serial break into debugger broken from 'cu' on -CURRENT?
Wilko Bulte wrote: This is bug for bug compatible with the V7 cu except for the unusably slow speed of 9600. For perfect brokenness, the default speed should be 300. *ROTFL* Duh... goes hunting for the ASR33 to verify this. Strange that it isn't 110baud :-P The default is the default for the first open for the device. It's actually a compile-time tunable, and not a result of an explicit set of the baud rate. System V has always had a strange relationship with its ttys. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: gcc -O broken in CURRENT
Hi all, Here are my test news. The -O bug doesn't happen with gcc295 from ports ! Previously I had stated before, the gcc295 from ports did not work too. but it seems that that was a user error :-) /usr/ports/devel/stlport (and the tests test/eh) can be succesfully be made. My staroffice build has survived the segfaulting part now in saxparser. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panics with CardBus
John Baldwin also cornered me about these panics. I'll be looking at them tonight. I think he gave me a good way to recreate them. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Request for testers of ATA RAID support
In [EMAIL PROTECTED] Soren Schmidt [EMAIL PROTECTED] wrote: SS As some might have noticed I've done some significant work on SS the ATA RAID support (for Promise Highpoint controllers) SS all thanks to Advanis which has made this possible. SS The code as it is now in -current allows for RAID1's (mirrors) SS to be properly handled when a disk dies, that means the SS system continues on the good disk and logs the loss of mirror SS to the console. After this commit, I'm not sure, current kernel cannot detect ata buses on my HighPoint HPT370 ATA100 controller. Any hint is appreciated. With new kernel on Thu Feb 28 14:07:18 JST 2002, I got following boot message. And yesterday's kernel also has same problem, that is, atapci0 cannot be detected properly and ar disk is not available. Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #3: Thu Feb 28 14:07:18 JST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NAKAJI Preloaded elf kernel /boot/kernel/kernel at 0xc0469000. Preloaded userconfig_script /boot/kernel.conf at 0xc04690a8. Preloaded elf module /boot/kernel/linux.ko at 0xc04690f8. Preloaded elf module /boot/kernel/agp.ko at 0xc04691a4. Preloaded elf module /boot/kernel/acpi.ko at 0xc046924c. Timecounter i8254 frequency 1193182 Hz CPU: Pentium 4 (1399.85-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf0a Stepping = 10 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 671023104 (655296K bytes) avail memory = 647380992 (632208K bytes) Using $PIR table, 10 entries at 0xc00fdec0 ACPI-0161: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82845 host to AGP 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) pcib2: PCI-PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x9000-0x907f mem 0xe900-0xe97f irq 9 at device 1.0 on pci2 xl0: Ethernet address: 00:01:02:c2:15:af miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: Adaptec 2940 Ultra2 SCSI adapter (OEM) port 0x9400-0x94ff mem 0xe9001000-0xe9001fff irq 11 at device 2.0 on pci2 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs atapci0: HighPoint HPT370 ATA100 controller port 0xa800-0xa8ff,0xa400-0xa403,0xa000-0xa007,0x9c00-0x9c03,0x9800-0x9807 irq 5 at device 5.0 on pci2 pcib2: device atapci0 requested unsupported I/O range 0x0-0x9c00 (decoding 0x9000-0xafff) pcib2: device atapci0 requested unsupported I/O range 0x0-0xa400 (decoding 0x9000-0xafff) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci1: Intel ICH2 ATA100 controller port 0xf000-0xf00f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 pci0: serial bus, USB at device 31.2 (no driver attached) pci0: serial bus, SMBus at device 31.3 (no driver attached) pci0: serial bus, USB at device 31.4 (no driver attached) pcm0: Intel 82801BA (ICH2) port 0xc000-0xc03f,0xbc00-0xbcff irq 11 at device 31.5 on pci0 orm0: Option ROMs at iomem 0xd-0xd57ff,0xc-0xc on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: failed to get data. psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/ECP/ECP_RLE Probing for PnP devices on ppbus0: ppbus0: EPSON LP-8400PS3 PRINTER POSTSCRIPT plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ppc1: cannot reserve I/O port range sc0: System console 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 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ad0: 2441MB WDC AC32500H [4960/16/63] at ata0-master
Adding realloc()
Hi,
I've had the need for a realloc() in the kernel several times
before and am having it once again. Finally figured it's time to
do something about it.
Does anyone have problems with the attached patch? This patch adds
realloc() and also fixes the semantics of free() to be consistent
with userland, in that free(NULL) is legal and does nothing. This
will make it possible to simplify some netgraph code and probably
other stuff too. Reviews appreciated as well.
Thanks,
-Archie
__
Archie Cobbs * Packet Design * http://www.packetdesign.com
Index: kern/kern_malloc.c
===
RCS file: /home/ncvs/src/sys/kern/kern_malloc.c,v
retrieving revision 1.93
diff -u -r1.93 kern_malloc.c
--- kern_malloc.c 12 Sep 2001 08:37:44 - 1.93
+++ kern_malloc.c 12 Mar 2002 00:06:03 -
-57,6 +57,16
#include machine/cpu.h
#endif
+/*
+ * When realloc() is called, if the new size is sufficiently smaller than
+ * the old size, realloc() will allocate a new, smaller block to avoid
+ * wasting memory. 'Sufficiently smaller' is defined as: newsize =
+ * oldsize / 2^n, where REALLOC_FRACTION defines the value of 'n'.
+ */
+#ifndef REALLOC_FRACTION
+#define REALLOC_FRACTION 1 /* new block if = half the size */
+#endif
+
MALLOC_DEFINE(M_CACHE, cache, Various Dynamically allocated caches);
MALLOC_DEFINE(M_DEVBUF, devbuf, device driver memory);
MALLOC_DEFINE(M_TEMP, temp, misc temporary data buffers);
-294,6 +304,10
#endif
register struct malloc_type *ksp = type;
+ /* free(NULL, ...) does nothing */
+ if (addr == NULL)
+ return;
+
KASSERT(kmembase = (char *)addr (char *)addr kmemlimit,
(free: address %p out of range, (void *)addr));
kup = btokup(addr);
-397,6 +411,49
#endif
splx(s);
mtx_unlock(malloc_mtx);
+}
+
+/*
+ * realloc: change the size of a memory block
+ */
+void *
+realloc(addr, size, type, flags)
+ void *addr;
+ unsigned long size;
+ struct malloc_type *type;
+ int flags;
+{
+ struct kmemusage *kup;
+ unsigned long alloc;
+ void *newaddr;
+
+ /* realloc(NULL, ...) is equivalent to malloc(...) */
+ if (addr == NULL)
+ return (malloc(size, type, flags));
+
+ /* Sanity check */
+ KASSERT(kmembase = (char *)addr (char *)addr kmemlimit,
+ (realloc: address %p out of range, (void *)addr));
+
+ /* Get the size of the original block */
+ kup = btokup(addr);
+ alloc = 1 kup-ku_indx;
+ if (alloc MAXALLOCSAVE)
+ alloc = kup-ku_pagecnt PAGE_SHIFT;
+
+ /* Reuse the original block if appropriate */
+ if (size = alloc
+ (size (alloc REALLOC_FRACTION) || alloc == MINALLOCSIZE))
+ return (addr);
+
+ /* Allocate a new, bigger (or smaller) block */
+ if ((newaddr = malloc(size, type, flags)) == NULL)
+ return (NULL);
+
+ /* Copy over original contents */
+ bcopy(addr, newaddr, min(size, alloc));
+ free(addr, type);
+ return (newaddr);
}
/*
Index: sys/malloc.h
===
RCS file: /home/ncvs/src/sys/sys/malloc.h,v
retrieving revision 1.54
diff -u -r1.54 malloc.h
--- malloc.h 10 Aug 2001 06:37:04 - 1.54
+++ malloc.h 12 Mar 2002 00:06:12 -
-173,6 +173,8
void *malloc __P((unsigned long size, struct malloc_type *type, int flags));
void malloc_init __P((void *));
void malloc_uninit __P((void *));
+void *realloc __P((void *addr, unsigned long size,
+ struct malloc_type *type, int flags));
#endif /* _KERNEL */
#endif /* !_SYS_MALLOC_H_ */
Re: GEOM code ready for testing
In message [EMAIL PROTECTED], Carl Makin writes: Hi, On Mon, 2002-03-11 at 06:34, Poul-Henning Kamp wrote: The GEOM code is now ready for early testing: Would GEOM support accessing a device via multiple paths? (ie could we write a method that would do that?) Yes, that would be possible. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
