Compiling with high optimization?
Has anyone tried building world/kernel with high optimizations (-O2, -O3) recently? What breaks? (Booby prize to whoever says common sense ;) I last tried it quite a few months ago and the resolver died on me, don't know what else. I'm not really thinking of running like that, but I am curious about others' experiences. -- Ray Kohler [EMAIL PROTECTED] When you're not looking at it, this fortune is written in FORTRAN. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Request for info from SiS chipset owners
agp0@pci0:0:0: class=0x06 card=0x chip=0x07301039 rev=0x02 hdr=0x00 atapci0@pci0:0:1: class=0x010180 card=0x0a011019 chip=0x55131039 rev=0xd0 hdr=0x00 isab0@pci0:1:0: class=0x060100 card=0x chip=0x00081039 rev=0x00 hdr=0x00 ohci0@pci0:1:2: class=0x0c0310 card=0x70011039 chip=0x70011039 rev=0x07 hdr=0x00 ohci1@pci0:1:3: class=0x0c0310 card=0x70001039 chip=0x70011039 rev=0x07 hdr=0x00 none0@pci0:1:4: class=0x040100 card=0x0a011019 chip=0x70181039 rev=0x02 hdr=0x00 pcib1@pci0:2:0: class=0x060400 card=0x chip=0x00011039 rev=0x00 hdr=0x01 rl0@pci0:13:0: class=0x02 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 drm0@pci1:0:0: class=0x03 card=0x013a1002 chip=0x51571002 rev=0x00 hdr=0x00 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: first snag with 5.0 - XFree86 4 (fwd)
On Tue, Jan 21, 2003 at 08:41:27PM +0200, fingers wrote: hi it's been suggested that i send this to current@. Please let me know what info you'd like to carry on debugging this. Regards --Rob -- Forwarded message -- Date: Tue, 21 Jan 2003 16:05:34 +0200 (SAST) From: fingers [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: first snag with 5.0 - XFree86 4 howdie built X 4 from source or using package I'm getting: snip XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 5.0-RC i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Jan 21 11:15:10 2003 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 Fatal server error: xf86EnableIO: Failed to open /dev/io for extended I/O What are the permissions on /dev/io? What's your securelevel set to (sysctl kern.securelevel)? -- Ray Kohler [EMAIL PROTECTED] Chism's Law of Completion: The amount of time required to complete a government project is precisely equal to the length of time already spent on it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: How to build -current and install to empty slice?
On Sun, Jan 19, 2003 at 05:05:37PM -0800, Darren Pilgrim wrote: How do tell make to use /5/usr/obj instead of /usr/obj? Will MAKEOBJDIRPREFIX=/5/usr/obj do this? I have more questons: Can I force make to ignore /etc/make.conf and /etc/defaults/make.conf and read another set of config files? Would it be safe to use /5/usr/src/etc/defaults/make.conf? Will DESTDIR=/5 cause the new build tools to install under /5 as well, or do I need to set something else to avoid having my 4.7p3 build tools clobbered? So far I have this set of commands: # cd /5/usr/src MAKEOBJDIRPREFIX=/5/usr/obj DESTDIR=/5 make buildworld # MAKEOBJDIRPREFIX=/5/usr/obj DESTDIR=/5 make kernel # MAKEOBJDIRPREFIX=/5/usr/obj DESTDIR=/5 make installworld # cd /5/usr/src/etc DESTDIR=/5 make distribution MAKEOBJDIRPREFIX is probably redundant here, but I don't know. # cd /5/usr/src/release/sysinstall make clean make all install sysinstall now lives in usr/sbin, so it'll be taken care of by the regular build/installworld. # install -o root -g wheel -m 0555 /5/usr/src/etc/MAKEDEV /5/dev/MAKEDEV # cd /5/dev ./MAKEDEV all ad4 ad4s2h ad4s3h ad4s4h ums1 vn1 vty16 Don't do these two, MAKEDEV isn't needed in 5.0, even though it still exists, and when DEVFS is mounted on /dev, this stuff will get lost anyway (and take up disk space). # disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 /dev/ad4s3 Don't you mean # disklabel -B -b /5/boot/boot1 -s /5/boot/boot2 /dev/ad4s3 ? -- Ray Kohler [EMAIL PROTECTED] After living in New York, you trust nobody, but you believe everything. Just in case. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-RC3 working great, but NOTES incomplete?
On Sat, Jan 18, 2003 at 09:32:09PM -0800, Craig R wrote: I got 5.0-RC3 working great on my box today, but when I went to make a custom kernel and read NOTES I noticed that it makes no mention of IPFIREWALL and friends. Is this intentional? craig@boss:~$ grep IPFIREWALL /sys/i386/conf/NOTES craig@boss:~$ Nothing shows up. What's the scoop? It's been moved to the machine-independent NOTES file, /sys/conf/NOTES. -- Ray Kohler [EMAIL PROTECTED] I'm a creationist; I refuse to believe that I could have evolved from man. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: aicasm broke?
On Sun, Jan 19, 2003 at 12:57:17AM -0500, Jeff Utter wrote: I'm using 5.0 -current (as of about 5 minutes ago) but it's been doing this for DAYS.. kernel build dies on this: /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:50:16: db.h: No such file or directory which is then followed by a ton of other errors, obviously caused by the lack of db.h. anyone know what's up? Looks like your copy of /usr/include/db.h got lost. I'd suggest copying it from /usr/src/include or maybe doing a 'make includes' if you think any other includes might be goofed up. -- Ray Kohler [EMAIL PROTECTED] I am not an Economist. I am an honest man! -- Paul McCracken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: How to update UFS1 to UFS2?
On Tue, Dec 17, 2002 at 11:29:05AM +0200, Vitaly Markitantov wrote: Have an existing partition with UFS1 on it. How can i update/convert it to UFS2? It is safe make it that way: dump -0 -f /store/arch.usr /usr shutdown now umount -a /usr mount / mount /store newfs -O2 /dev/ad0s2e restore -f /store/arch.usr About right, but I'd do it just a little differently: shutdown now umount /usr dump 0af /store/arch.usr /dev/ad0s2e newfs -O 2 -U /dev/ad0s2e mount /usr cd /usr restore rf /store/arch.usr -- Ray Kohler [EMAIL PROTECTED] As Zeus said to Narcissus, Watch yourself. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: How to update UFS1 to UFS2?
On Tue, Dec 17, 2002 at 11:47:23AM -0500, Steven Ames wrote: On a related topic... how do you tell which of your filesystems are mounted UFS1 -vs- UFS2? 'mount -v' just says ufs. dumpfs filesystem | grep UFS -- Ray Kohler [EMAIL PROTECTED] See - the thing is - I'm an absolutist. I mean, kind of ... in a way ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
writing to mbr under GEOM
What's the status of the issue where devices with open partitions can't have their boot sectors written to? I know phk@ was working on it a while back but it's something I'd like to see fixed soon, maybe before release? ~ 9:14PM % sudo fdisk -B ad0 fdisk: can't open device /dev/ad0 fdisk: cannot open disk /dev/ad0: Operation not permitted zsh: 13660 exit 1 sudo fdisk -B ad0 ~ 9:25PM % sudo fdisk -i ad0 fdisk: can't open device /dev/ad0 fdisk: cannot open disk /dev/ad0: Operation not permitted zsh: 13661 exit 1 sudo fdisk -i ad0 -- Ray Kohler [EMAIL PROTECTED] When you have an efficient government, you have a dictatorship. -- Harry Truman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: TTL
On Fri, Dec 13, 2002 at 09:14:06PM -0800, Jimi Thompson wrote: This is an issue that we recently ran into at work and I wanted to mention this since 5.0 isn't released yet. I don't know if FreeBSD has addressed this or not but thought it should be mentioned just in case. We've discovered that in many *nix OS's the TCP stack sets the default TTL for packets to 30. Apparently, IBM (AIX) had not and our research showed that most of the other *nix OS's hadn't either. With the increasing complexity of the internet, this is often a problem for those who have large internal networks and/or live in Australia. 30 hops often isn't enough to make to the core DNS. It probably ought to be extended to something more realistic. The other numbers that I've seen used 64, 128, and 256. I'm not completely sure but I believe the default TTL on 5.0 is 64. I've briefly tested this by pinging myself and watching the output, but if there are any special cases for that then I could very well be wrong. -- Ray Kohler [EMAIL PROTECTED] Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
stuck in DDB
Just tonight I pushed Ctl+Alt+Esc and dropped into DDB, only to find I couldn't do anything there. Either the machine hard locked or my keyboard didn't work, I can't think of any way to tell the difference there. I really have pitifully little to go on; I didn't even have DDB compiled in until today for a very long time, so I don't know if it used to work before. I have a USB keyboard, with support for it enabled in the BIOS, if anyone cares. I don't expect anybody can solve this with so little to go on, but maybe somebody else has at least experienced it? (I can't try a non-USB keyboard; this box has a busted PS/2 port.) -- Ray Kohler [EMAIL PROTECTED] Egotist, n.: A person of low taste, more interested in himself than me. -- Ambrose Bierce, The Devil's Dictionary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld failure
On Thu, Dec 05, 2002 at 10:55:48AM +0800, JY wrote: On Wed, Dec 04, 2002 at 10:55:24AM -0800, David O'Brien wrote: On Thu, Dec 05, 2002 at 02:08:42AM +0800, JY wrote: /usr/src/contrib/gcc/cp/except.c:790:18: cfns.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. Please cvsup again, and reply back if you still have any build problems. buildworld ok now. But cvsup kept coming up with this -- Running /usr/local/bin/cvsup -- Connected to cvsup2.FreeBSD.org Updating collection src-all/cvs Delete src/contrib/gcc/INSTALL Cannot delete /usr/src/contrib/gcc/INSTALL: Directory not empty rm -rf /usr/src rm -rf /usr/sup and re-cvsupping does not help. I removed just the problematic directory and re-cvsupped. It downloaded the directory again but after that it didn't complain again. This looks like some kind of repo damage. -- Ray Kohler [EMAIL PROTECTED] You are only young once, but you can stay immature indefinitely. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/sound/pcm buffer.c channel.c feeder.c feeder_fmt.c feeder_rate.c sndstat.c sound.c sound.h vchan.c
On Tue, Nov 26, 2002 at 06:19:41AM +, cameron grant wrote: I have no idea why, but this commit broke kernel building: cc -c -O -pipe -mcpu=athlon -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/sound/isa/ad1816.c cc1: warnings being treated as errors /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_lock': /usr/src/sys/dev/sound/isa/ad1816.c:81: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:81: request for member `mtx_lock' in something not a structure or union /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_unlock': /usr/src/sys/dev/sound/isa/ad1816.c:87: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:87: request for member `mtx_lock' in something not a structure or union *** Error code 1 And the same result for other consumers of snd_mtx* . i'm unable to reproduce this. have you tried a clean build? It was a clean build, done by make buildkernel immediately after make buildworld. SOP. FWIW, I can't even figure out why this doesn't compile, everything looks fine to me and the errors make no sense at all. The only thing I can think to do is blow away /usr/src and get a new one, see if anything changes. -- Ray Kohler [EMAIL PROTECTED] It has been said that man is a rational animal. All my life I have been searching for evidence which could support this. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel broken
On Tue, Nov 26, 2002 at 12:53:39PM +0100, Jan Stocker wrote: CVSuped (2 mins ago) -current kernel is broken: cc1: warnings being treated as errors /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_lock': /usr/src/sys/dev/sound/isa/ad1816.c:81: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:81: request for member `mtx_lock' in something not a structure or union /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_unlock': /usr/src/sys/dev/sound/isa/ad1816.c:87: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:87: request for member `mtx_lock' in something not a structure or union This turns out to be semi-reproduceable. I have this problem but the committer who made the change can't reproduce it. -- Ray Kohler [EMAIL PROTECTED] Math is like love -- a simple idea but it can get complicated. -- R. Drabek To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/sound/isa ad1816.c mss.c sbc.c src/sys/dev/sound/pci aureal.c cmi.c ds1.c emu10k1.c maestro.c t4dwave.c src/sys/dev/sound/pcm ac97.c channel.h mixer.c sound.c
On Tue, Nov 26, 2002 at 10:16:28AM -0800, Cameron Grant wrote: cg 2002/11/26 10:16:28 PST Modified files: sys/dev/sound/isaad1816.c mss.c sbc.c sys/dev/sound/pciaureal.c cmi.c ds1.c emu10k1.c maestro.c t4dwave.c sys/dev/sound/pcmac97.c channel.h mixer.c sound.c Log: (hopefully) fix build breakage some people are seeing This fixed it, thanks! -- Ray Kohler [EMAIL PROTECTED] Jesus Saves, Moses Invests, But only Buddha pays Dividends. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel broken
On Wed, Nov 27, 2002 at 02:02:12AM +0200, Giorgos Keramidas wrote:
On 2002-11-26 16:33, Gary Jennejohn [EMAIL PROTECTED] wrote:
Ray Kohler [EMAIL PROTECTED] wrote:
On Tue, Nov 26, 2002 at 12:53:39PM +0100, Jan Stocker wrote:
CVSuped (2 mins ago) -current kernel is broken:
cc1: warnings being treated as errors
/usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_lock':
/usr/src/sys/dev/sound/isa/ad1816.c:81: warning: dereferencing `void *' pointer
/usr/src/sys/dev/sound/isa/ad1816.c:81: request for member `mtx_lock' in
something not a structure or union
/usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_unlock':
/usr/src/sys/dev/sound/isa/ad1816.c:87: warning: dereferencing `void *' pointer
/usr/src/sys/dev/sound/isa/ad1816.c:87: request for member `mtx_lock' in
something not a structure or union
This turns out to be semi-reproduceable. I have this problem but the
committer who made the change can't reproduce it.
I have the same problem, [...]
The culprit seems to be a change in /sys/dev/sound/pcm/sound.h,
where snd_mtx{un}lock() were changed from routines to macros which
simply use mtx_{un}lock(). The routines required a ``void *'', but
the macros require a ``struct mtx *''.
The following drivers still declare the lock to be a ``void *'',
which is totally bogus after the above mentioned change:
/sys/dev/sound/isa/ad1816.c
/sys/dev/sound/isa/mss.c
/sys/dev/sound/isa/sbc.c
/sys/dev/sound/pci/cmi.c
/sys/dev/sound/pci/ds1.c
/sys/dev/sound/pci/emu10k1.c
/sys/dev/sound/pci/t4dwave.c
/sys/dev/sound/pcm/ac97.c
/sys/dev/sound/pcm/mixer.c
/sys/dev/sound/pcm/sound.c
I successfuly rebuilt a kernel with the following revisions of these
files.
keramida@gothmog[02:01]/home/keramida uname -v
FreeBSD 5.0-CURRENT #1: Tue Nov 26 22:30:31 EET 2002 ...
Can you check that you have the right revisions checked out:
$FreeBSD: src/sys/dev/sound/isa/ad1816.c,v 1.24 2002/06/09 14:20:17 hm Exp $
$FreeBSD: src/sys/dev/sound/isa/mss.c,v 1.78 2002/04/04 20:56:45 jhb Exp $
$FreeBSD: src/sys/dev/sound/isa/sbc.c,v 1.35 2002/04/04 20:56:45 jhb Exp $
$FreeBSD: src/sys/dev/sound/pci/cmi.c,v 1.17 2002/08/23 20:54:32 orion Exp $
$FreeBSD: src/sys/dev/sound/pci/ds1.c,v 1.27 2002/04/04 20:56:46 jhb Exp $
$FreeBSD: src/sys/dev/sound/pci/emu10k1.c,v 1.27 2002/11/25 17:07:33 cg Exp $
$FreeBSD: src/sys/dev/sound/pci/t4dwave.c,v 1.34 2002/10/17 03:45:34 marcel Exp
$
$FreeBSD: src/sys/dev/sound/pcm/ac97.c,v 1.27 2002/08/23 06:19:28 orion Exp $
$FreeBSD: src/sys/dev/sound/pcm/mixer.c,v 1.27 2002/07/25 04:49:45 green Exp $
$FreeBSD: src/sys/dev/sound/pcm/sound.c,v 1.79 2002/11/25 17:17:42 cg Exp $
cg's latest commit (Tuesday) makes the above change and fixes these
errors. I still can't figure out what would make it work only for some
people, especially if we're all doing proper builds.
--
Ray Kohler [EMAIL PROTECTED]
This novel is not to be tossed lightly aside, but to be hurled with
great force.
-- Dorothy Parker
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/dev/sound/pcm buffer.c channel.c feeder.c feeder_fmt.c feeder_rate.c sndstat.c sound.c sound.h vchan.c
cg 2002/11/25 09:17:43 PST Modified files: sys/dev/sound/pcmbuffer.c channel.c feeder.c feeder_fmt.c feeder_rate.c sndstat.c sound.c sound.h vchan.c Log: various fixes to eliminate locking warnings Approved by: re Reviewed by: orion I have no idea why, but this commit broke kernel building: cc -c -O -pipe -mcpu=athlon -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/sound/isa/ad1816.c cc1: warnings being treated as errors /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_lock': /usr/src/sys/dev/sound/isa/ad1816.c:81: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:81: request for member `mtx_lock' in something not a structure or union /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_unlock': /usr/src/sys/dev/sound/isa/ad1816.c:87: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:87: request for member `mtx_lock' in something not a structure or union *** Error code 1 And the same result for other consumers of snd_mtx* . -- Ray Kohler [EMAIL PROTECTED] What color is a chameleon on a mirror? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cyclic dependancies?
Patrick Stinson wrote: seems I've backed myself into a corner. I've got 4.4-Release installed, and have cvsup'ed src-all into a /usr prefix. make buildworld completed successfully, but now I cannot continue without libc.so.5. Unfortuantely, I can't build libc 5 without the current kernel, and vise-versa. I get a core dump (assuming that's because of my kernel version) from make in the /usr/src directory when logged in as root. config bails after asking for libc.so.5. make kernel worked at one point, but the kernel didn't seem to actually install on /. suggesstions? Current kernels install to /boot/kernel/kernel. Either interrupt the loader during boot and point it there or install the new loader before you reboot. This is documented in src/UPDATING (and there are a few more issues there, I'd suggest checking it out before you run into more trouble.) - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
From [EMAIL PROTECTED] Fri Nov 8 02:45:04 2002 Date: Fri, 08 Nov 2002 00:39:35 -0700 (MST) To: [EMAIL PROTECTED] Subject: Re: [PATCH] note the __sF change in src/UPDATING From: M. Warner Losh [EMAIL PROTECTED] In message: [EMAIL PROTECTED] Ray Kohler [EMAIL PROTECTED] writes: : Hear hear, I agree. There's no need to expose what ought to be : private data to the world, especially when we can get the additional : benefit here of letting us play with the implementation. -current already does this. The problem is that we're trying to shoot the bad access in the head, and that is what is screwing people. So the problem isn't that we're trying to export private data to the world. Quite the contrary, we're trying to eliminate it and having growing pains. Exactly. That's why I'm arguing against putting __sF back (or adopting equally crapulent measures). Growing pains are a necessary evil. (I also agree that we probably ought to staticize any other things of this nature while we're at it and get the pain over with.) - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl5.6.1 wrapper
From [EMAIL PROTECTED] Fri Nov 8 04:15:04 2002 To: Kris Kennaway [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: perl5.6.1 wrapper Date: Fri, 08 Nov 2002 08:58:44 + From: Mark Murray [EMAIL PROTECTED] IMVHO, the perl wrapper should be removed altogether, and the perl port's use.port symlink-creating feature should be used instead. M Can someone explain why the perl wrapper needs to be hardlinked to perl5.6.1? The problem I am seeing is this: USE_PERL5=yes in a port adds the following BUILD_DEPENDS: enigma# make -V BUILD_DEPENDS perl5.6.1:/usr/ports/lang/perl5 However 5.0 has perl5.6.1 in the base system still, so this dependency is always satisfied, the perl port is never added and the port build that relies on it will fail. Then we're back to the problem of there being a complete stale perl in the base system after a 4.X-5.X upgrade, but then, I've always thought that clean out the cruft ought to be a mandatory step in upgrading. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
From [EMAIL PROTECTED] Fri Nov 8 11:30:05 2002 Date: Fri, 08 Nov 2002 09:27:32 -0700 (MST) To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [PATCH] note the __sF change in src/UPDATING From: M. Warner Losh [EMAIL PROTECTED] In message: [EMAIL PROTECTED] Ray Kohler [EMAIL PROTECTED] writes: : From [EMAIL PROTECTED] Fri Nov 8 02:45:04 2002 : Date: Fri, 08 Nov 2002 00:39:35 -0700 (MST) : To: [EMAIL PROTECTED] : Subject: Re: [PATCH] note the __sF change in src/UPDATING : From: M. Warner Losh [EMAIL PROTECTED] : : In message: [EMAIL PROTECTED] : Ray Kohler [EMAIL PROTECTED] writes: : : Hear hear, I agree. There's no need to expose what ought to be : : private data to the world, especially when we can get the additional : : benefit here of letting us play with the implementation. : : -current already does this. The problem is that we're trying to shoot : the bad access in the head, and that is what is screwing people. So : the problem isn't that we're trying to export private data to the : world. Quite the contrary, we're trying to eliminate it and having : growing pains. : : Exactly. That's why I'm arguing against putting __sF back (or : adopting equally crapulent measures). Growing pains are a necessary evil. : (I also agree that we probably ought to staticize any other things of : this nature while we're at it and get the pain over with.) Yes, but this is too painful. If we were going to do this, the time for the pain was 6-9 months ago, not just before the release. Yeah, that's true. I think unfortunately we ought to wait and do it next cycle, but when we do, do it completely and as quickly as possible. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
phoenix works on -current!
I've sent mail to phoenix@ , but I thought I'd let this list know as well. Native phoenix works fine on -current for me, in spite of the Makefile claims. Install the perl5 port on a recent -current and phoenix will build and run perfectly. (And if it doesn't, I'm sure phoenix@ would like to know about it anyway.) - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl5.6.1 wrapper
From [EMAIL PROTECTED] Fri Nov 8 16:15:05 2002 Date: Fri, 8 Nov 2002 13:02:58 -0800 From: Kris Kennaway [EMAIL PROTECTED] To: Ray Kohler [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: perl5.6.1 wrapper On Fri, Nov 08, 2002 at 06:54:37AM -0500, Ray Kohler wrote: Then we're back to the problem of there being a complete stale perl in the base system after a 4.X-5.X upgrade, but then, I've always thought that clean out the cruft ought to be a mandatory step in upgrading. Yes, it's already a mandatory step (remove old includes, or you can't build C++ programs). I mean *all* the cruft -- old modules and config files, deprecated binaries and man pages, even old shlibs if it's safe. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
From [EMAIL PROTECTED] Thu Nov 7 18:00:10 2002 Date: Thu, 07 Nov 2002 14:47:03 -0800 From: Joel M. Baldwin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. So the questions now are. 1.) What is dnet doing that is Hard Locking the system? 2.) Is the dnet problem the same as what has been causing my Hard Locks all along? Just a guess, but maybe your system locks up every time the CPU usage gets very high under SMP? That's one thing dnetc is guaranteed to do. Do other CPU-intensive operations do it? (Maybe you said earlier, but I haven't been following this thread.) - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
From [EMAIL PROTECTED] Thu Nov 7 18:30:04 2002 Date: Thu, 07 Nov 2002 15:26:57 -0800 From: Terry Lambert [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [PATCH] note the __sF change in src/UPDATING Specifically, I do not buy the idea that there is a necessity for the existance of data interfaces, as opposed to procedural interfaces. And procedural interfaces are fixable with weak symbols. The thing that's screwing us with __sF is that it is a data block that's directly referenced without the use of an accessor function, and thefore there are global data references, rather than accessor or mutator function references. As a result, when the underlying data changes, the code that has already been compiled to reference it, must also change. This problem has already been fixed with errno. It has already been fixed with strerror() (though unfortunately, the sys_errlist[] and sys_nerr references remain unwrapped). It has been fixed in many other places (e.g. the curses library used to export row and column count integers, and doesn't any more). It's very obvious to me that defining a *non-inline* function to return the correct __sF entry by entry ID will erase this problem for a future version of FreeBSD, while leaving the __sF invisible for a revision cycle, so that new applications will get the function reference, and old applications will get the __sF reference they expect, and continue to compile and link correctly. Hear hear, I agree. There's no need to expose what ought to be private data to the world, especially when we can get the additional benefit here of letting us play with the implementation. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
From [EMAIL PROTECTED] Thu Nov 7 19:30:04 2002 Date: Thu, 07 Nov 2002 16:19:57 -0800 From: Terry Lambert [EMAIL PROTECTED] To: Horen [EMAIL PROTECTED] Cc: Eric Anholt [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: XFree Horen wrote: Tried all combinations. Disabled every chip related feature, that isn't required to bring X up. Screensaver is disabled. No way to get any readable display back without reboot. Installed a fresh XFree86 built from the ports tree, hour before updated. No luck :-( You stated Typing blind starts X again. Can you tell us what you mean by this? o It restarts X, as if you typed startx o It restarts X, as if you typed xinit o It restarts X, as in it comes back from video signal blanking o It doesn't really restart X, you were lying... (8-)) o Turning my monitor off, and back on works the same way o ...something else happens I think he meant Typing commands blind works, up to and including running `startx' to start X again. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Followup: questions about the performance of current
Ok, so based on the promising response I got to my original 3 questions, I went ahead and upgraded. It went _very_ smoothly, with the help of UPDATING and some experience with this sort of thing. No make errors at any point. The only issues I hit were my fault, like forgetting to run mergemaster and then having pam lock me out, and forgetting to install perl and having half of my port rebuilds fail. D'oh. Every port I have built cleanly with the exception of games/xkobo (very minor, and I can file a PR if desired). (Also, the WITHOUT_COMPOSER hack to mozilla-devel seems to be broken, but that's a separate issue.) I am working on a write-up of my upgrade path, a sort of Informal Guide to doing 4.X-current, which I will post to -doc when the network on the (non-FreeBSD) machine starts working again. So, to sum it up, my upgrading experience was excellent. Great work. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
burncd hangs after 'blank'
Sorry if this is old news, but I've just discovered a problem in burncd.
If I do a 'blank' the operation completes but burncd then hangs. I have
a gdb session that shows the situation quite nicely: when burncd does
CDRIOCGETPROGRESS to get the number for the progress bar, it always
reports 0, and with no error, so burncd gets stuck in an infinite loop.
This really looks like an ioctl() issue more than a burncd one: either
CDRIOCGETPROGRESS shouldn't be allowed on 'blank' or it should return
valid information. Gdb session follows (sorry about the horrible
line-wrapping).
/usr/src/usr.sbin/burncd 10:23PM % sudo cc -O -pipe -g -march=athlon
-Wall -Wno-format-y2k -Wno-uninitialized -o burncd burncd.c
/usr/src/usr.sbin/burncd 10:26PM % sudo gdb burncd
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-undermydesk-freebsd...
(gdb) r -s 4 -f /dev/acd0c blank
Starting program: /usr/src/usr.sbin/burncd/burncd -s 4 -f /dev/acd0c blank
^Zanking CD, please wait..
Program received signal SIGTSTP, Stopped (user).
0x280b0823 in nanosleep () from /usr/lib/libc.so.5
(gdb) bt
#0 0x280b0823 in nanosleep () from /usr/lib/libc.so.5
#1 0x280a594f in sleep () from /usr/lib/libc.so.5
#2 0x08049069 in main (argc=1, argv=0x2812247c) at burncd.c:194
#3 0x08048a80 in _start ()
(gdb) up 2
#2 0x08049069 in main (argc=1, argv=0x2812247c) at burncd.c:194
194 sleep(1);
(gdb) l
189 blank == CDR_B_ALL ?
eras : blank);
190
191 if (ioctl(fd, CDRIOCBLANK, blank) 0)
192 err(EX_IOERR, ioctl(CDRIOCBLANK));
193 while (1) {
194 sleep(1);
195 error = ioctl(fd,
CDRIOCGETPROGRESS, percent);
196 if (percent 0 !quiet)
197 fprintf(stderr,
198 %sing CD - %d
%% done \r,
(gdb)
199 blank ==
CDR_B_ALL ?
200 eras :
blank, percent);
201 if (error || percent == 100 ||
202 (percent == 0 last ==
99))
203 break;
204 last = percent;
205 }
206 if (!quiet)
207 printf(\n);
208 continue;
(gdb) p error
$1 = 0
(gdb) p percent
$2 = 0
(gdb) p last
$3 = 0
(gdb) set last=99
(gdb) p last
$4 = 99
(gdb) c
Continuing.
Program exited normally.
(gdb) q
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
just moved to current, mouse is jerky
I just upgraded to current today on my goof-off box, and the mouse moves in big jerks instead of smoothly. It does this either in X or in console, and also in X without moused running (reading /dev/psm0 directly). I've also tried setting high resolution on this device (flags 0x004). Nothing has made any difference. Should I really be using the devfs devices and not the old static ones (in general, not just in this case)? Is this a known issue? What should I try next? (Am I just being an idiot bothering people about this? I realize that expecting current to work perfectly is unreasonable, but this sure puts a crimp in my messing around on it.) Thanks for helping out a not-very-important current user with a dumb problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
strange messages at bootup
I just came over from 4.0 yesterday, and now I get some odd messages that weren't there before. unknown0: PNP0c01 at iomem 0-0x9fbff,0x9fc00-0x9,0xe-0xf,0x10-0x4fe,0x4ff-0x4ff7fff,0x4ff8000-0x4ff,0xfffc-0x on isa0 unknown: PNP can't assign resources unknown1: PNP0200 at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown3: PNP0b00 at port 0x70-0x73 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown4: PNP0800 at port 0x61 on isa0 npxisa0: Legacy ISA coprocessor support at port 0xf0-0xff irq 13 on isa0 unknown: PNP0c02 can't assign resources unknown5: PNP0c02 at port 0xff00-0xff3f,0xff40-0xff4f on isa0 unknown6: PNP0f13 on isa0 unknown7: PNP0a03 at port 0xcf8-0xcff on isa0 unknown8: PNP0501 at port 0x3f8-0x3ff irq 4 on isa0 unknown9: PNP0c02 on isa0 unknown: PNP0400 can't assign resources unknown: PNP0700 can't assign resources What are these? Are they possibly related to my mouse no longer working (it's not the "out of sync" problem)? How can I get rid of them? I think they are from the ppbus driver checking for attached devices, I'll put the entire dmesg here for context. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #4: Sat Jun 10 16:09:51 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/RJK191 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 167046041 Hz CPU: Pentium/P55C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 83820544 (81856K bytes) avail memory = 78753792 (76908K bytes) Preloaded elf kernel "kernel" at 0xc02c. Intel Pentium detected, installing workaround for F00F bug npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: Intel 82439TX System controller (MTXC) at 0.0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller at 7.2 irq 10 pci0: Intel 82371AB Power management controller at 7.3 pci0: ATI Mach64-GU graphics accelerator at 10.0 irq 11 pcm0: AudioPCI ES1370 port 0xee80-0xeebf irq 10 at device 11.0 on pci0 pci0: unknown card (vendor=0x109e, dev=0x0350) at 18.0 irq 10 xl0: 3Com 3c900-TPO Etherlink XL port 0xef00-0xef3f irq 11 at device 19.0 on pci0 xl0: Ethernet address: 00:60:97:6d:9c:d8 xl0: selecting 10baseT transceiver, half duplex fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: Parallel port at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: HEWLETT-PACKARD DESKJET 710C SCP,VLINK lpt0: Printer on ppbus0 lpt0: Interrupt-driven port unknown0: PNP0c01 at iomem 0-0x9fbff,0x9fc00-0x9,0xe-0xf,0x10-0x4fe,0x4ff-0x4ff7fff,0x4ff8000-0x4ff,0xfffc-0x on isa0 unknown: PNP can't assign resources unknown1: PNP0200 at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown3: PNP0b00 at port 0x70-0x73 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown4: PNP0800 at port 0x61 on isa0 npxisa0: Legacy ISA coprocessor support at port 0xf0-0xff irq 13 on isa0 unknown: PNP0c02 can't assign resources unknown5: PNP0c02 at port 0xff00-0xff3f,0xff40-0xff4f on isa0 unknown6: PNP0f13 on isa0 unknown7: PNP0a03 at port 0xcf8-0xcff on isa0 unknown8: PNP0501 at port 0x3f8-0x3ff irq 4 on isa0 unknown9: PNP0c02 on isa0 unknown: PNP0400 can't assign resources unknown: PNP0700 can't assign resources ad0: 6204MB ST36540A [13446/15/63] at ata0-master using UDMA33 acd0: CDROM TOSHIBA CD-ROM XM-6002B at ata1-master using PIO3 Mounting root from ufs:/dev/ad0s2a lpt0: switched to polled standard mode -- Ray Kohler [EMAIL PROTECTED] FreeBSD -- The Power to Serve The lion and the calf shall lie down together but the calf won't get much sleep. -- Woody Allen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange messages at bootup
On Sat, Jun 10, 2000 at 11:19:01PM -0400, Brian Reichert wrote: On Sat, Jun 10, 2000 at 09:24:28PM -0400, Ray Kohler wrote: I just came over from 4.0 yesterday, and now I get some odd messages that weren't there before. unknown0: PNP0c01 at iomem 0-0x9fbff,0x9fc00-0x9,0xe-0xf,0x10-0x4fe,0x4ff-0x4ff7fff,0x4ff8000-0x4ff,0xfffc-0x on isa0 I would hazard the guess that you now have the PNPBIOS directive in your kernel config file... Actually, I don't have PnP in my config file. That's why I think this is so weird... -- Ray Kohler [EMAIL PROTECTED] FreeBSD -- The Power to Serve Speak softly and carry a +6 two-handed sword. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: strange messages at bootup
On Sat, Jun 10, 2000 at 09:33:51PM -0700, Chris Piazza wrote: On Sun, Jun 11, 2000 at 12:30:45AM -0400, Ray Kohler wrote: On Sat, Jun 10, 2000 at 11:19:01PM -0400, Brian Reichert wrote: I would hazard the guess that you now have the PNPBIOS directive in your kernel config file... Actually, I don't have PnP in my config file. That's why I think this is so weird... It's on by default now. Can I turn it off somehow? Or otherwise fix it? -- Ray Kohler [EMAIL PROTECTED] FreeBSD -- The Power to Serve Pure drivel tends to drive ordinary drivel off the TV screen. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ps2 mouse troubles
vice ID 3-00, 3 buttons psm0: config:, flags:, packet size:4 psm0: syncmask:08, syncbits:08 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) ppc0: parallel port found at 0x378 ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: EPP SPP ppc0: Parallel port at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/ECP/NIBBLE_ID/ECP_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: HEWLETT-PACKARD DESKJET 710C SCP,VLINK lpt0: Printer on ppbus0 lpt0: Interrupt-driven port mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) isa_probe_children: probing PnP devices unknown0: PNP0c01 at iomem 0-0x9fbff,0x9fc00-0x9,0xe-0xf,0x10-0x4fe,0x4ff-0x4ff7fff,0x4ff8000-0x4ff,0xfffc-0x on isa0 unknown: PNP can't assign resources unknown1: PNP0200 at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown2: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown3: PNP0b00 at port 0x70-0x73 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown4: PNP0800 at port 0x61 on isa0 npxisa0: Legacy ISA coprocessor support at port 0xf0-0xff irq 13 on isa0 unknown: PNP0c02 can't assign resources unknown5: PNP0c02 at port 0xff00-0xff3f,0xff40-0xff4f on isa0 unknown6: PNP0f13 on isa0 unknown7: PNP0a03 at port 0xcf8-0xcff on isa0 unknown8: PNP0501 at port 0x3f8-0x3ff irq 4 on isa0 unknown9: PNP0c02 on isa0 unknown: PNP0400 can't assign resources unknown: PNP0700 can't assign resources BIOS Geometries: 0:0314fe3f 0..788=789 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ST36540A/1.00 ATA-4 disk at ata0 as master ad0: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 ata1-master: success setting up PIO3 mode on generic chip acd0: TOSHIBA CD-ROM XM-6002B/0527 CDROM drive at ata1 as master acd0: read 2755KB/s (2755KB/s), 256KB buffer, PIO3 acd0: Reads: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xb, start 63, end = 6329609, size 6329547 : OK ad0s2: type 0xa5, start 6329610, end = 12691349, size 6361740 : OK start_init: trying /sbin/init lpt0: switched to polled standard mode -- Ray Kohler [EMAIL PROTECTED] FreeBSD -- The Power to Serve HOW YOU CAN TELL THAT IT'S GOING TO BE A ROTTEN DAY: #32: You call your answering service and they've never heard of you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NOUUCP knob and /etc/uucp
I was just noticing that the files in /etc/uucp are installed anyway if you set NOUUCP, whereas those in /etc/ssh and /etc/ssl are affected by their respective knobs. Could /etc/uucp be wrapped around the NOUUCP knob? -- Ray Kohler [EMAIL PROTECTED] Commitment, n.: Commitment can be illustrated by a breakfast of ham and eggs. The chicken was involved, the pig was committed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
psm.c broken
After a cvsup today, building a kernel finishes with this: linking kernel.debug psm.o: In function `psmprobe': /sys/compile/RJK191/../../isa/psm.c(.text+0x9fe): undefined reference to `atkbdc _open' *** Error code 1 I know psm.c was changed today, I'd suppose one reference here was missed in the process. Just figured I'd be the first to say so. -- Ray Kohler [EMAIL PROTECTED] The bogosity meter just pegged. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Several odd problems
Over the past two days I've acquired a few weird problems; I'm sending this to current as opposed to questions because these seem to be current-related... 1)top and ps stopped working. $ top kvm_open: proc size mismatch (34452 total, 1040 chunks) top: Out of memory. $ ps ps: proc size mismatch (8352 total, 1040 chunks) This looks like classic mismatch between kernel and these two programs, but all three are in sync with each other. 2)ldconfig from linux emulation dumps core. $ /usr/compat/linux/sbin/ldconfig Segmentation fault - core dumped Not sure why this happens, but I know there was a commit in the linux emulation code today. Obviously, this means no linux apps will run now - they all coredump. 3)installing perl fails. 101 # pwd /usr/src/gnu/usr.bin/perl 102 # make install ... vm/vnode_pager.h - vm/vnode_pager.ph *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/utils. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. This one seems by far the most mysterious of all, since I can find no reason whatsoever for it. It happens whether I install it separately or as part of an installworld. It chugs along quite happily and then fails there with no more information than that. 4)can't install the linux_base port. It passes all checksum tests, but gets a segv while trying to install the ldconfig RPM. I found this one while trying to investigate problem #2 above. Not sure whether it's even relevant, but I thought I'd mention it while I'm at it. -- Ray Kohler [EMAIL PROTECTED] Travel important today; Internal Revenue men arrive tomorrow. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Is openssl/openssh working right yet for others?
I know that openssl and openssh were under heavy construction (yesterday?), but since the commits have stopped (for now), I was wondering is anyone else is able to build it. Going to /usr/src/secure and running make produces a problem due to a missing buildinf.h, which should be automatically generated (in crypto/openssl/crypto), and doing make -k produces loads of syntax errors and such. Since I hadn't seen any complaints about this here (not even from random people who don't know what's going on), I just wondered whether it was just my problem, or if it's not compilable yet. Will produce make (-k) output on request. -- Ray Kohler [EMAIL PROTECTED] A closed mouth gathers no foot. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/sys/i386/machdep.c breaks kernel build
The latest commit of /sys/i386/i386/machdep.c breaks the kernel build:
cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include
opt_global.h -elf -mpreferred-stack-boundary=2
../../i386/i386/machdep.c
{standard input}: Assembler messages:
{standard input}:2772: Error: operands given don't match any known
386 instruction
*** Error code 1
Stop in /usr/src/sys/compile/RJK191.
--
Ray Kohler [EMAIL PROTECTED]
"No, `Eureka' is Greek for `This bath is too hot.'"
-- Dr. Who
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: /sys/i386/machdep.c breaks kernel build
On Mon, Feb 21, 2000 at 02:00:42PM +0900, Seigo Tanimura wrote:
On Sun, 20 Feb 2000 23:48:01 -0500,
Ray Kohler [EMAIL PROTECTED] said:
Ray cc -c -march=pentium -O3 -pipe -fno-builtin -Wall -Wredundant-decls
Ray -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
Ray -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
Ray -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include
Ray opt_global.h -elf -mpreferred-stack-boundary=2
Ray ../../i386/i386/machdep.c
Ray {standard input}: Assembler messages:
Ray {standard input}:2772: Error: operands given don't match any known
Ray 386 instruction
Ray *** Error code 1
Could you try the following patch(sent to bsd personally)? It prevents
movl between a debug register and memory.
This patch fixed it. Compiles fine, runs fine. Thanks!
--
Ray Kohler [EMAIL PROTECTED]
May the Fleas of a Thousand Camels infest one of your Erogenous Zones.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ata (CDROM mount) and PCCARD problems (xe driver) with 4.0
On Wed, Feb 02, 2000 at 09:54:04PM +0100, Andreas Klemm wrote: b) Can't mount cdrom mount /cdrom Device busy But I'm not under /cdrom and doesn't have a CD mounted I always get "Device busy" if I try to mount a CD without one in the drive, but it works if I actually put a disk in ;) Seems like something about the atapi-cd driver... -- Ray Kohler [EMAIL PROTECTED] I must have slipped a disk -- my pack hurts To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
