Re: midi causes panic on boot? + entropy gatherer works fine
On Mon, Mar 12, 2001 at 04:38:50PM +0100, Szilveszter Adam wrote: I wonder if this is known? If not, I can certainly provide more information. The offending sound hw is a Creative SB 64 AWE ISAPnP card. It works fine otherwise. (as it always has) Yup I'm seeing this too. SMP kernel, AWE64 PnP. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
random reboots...
I haven't been able to track this down since the kernel won't panic.. but with more recent kernels I've noticed: * options NCP prevents the kernel from linking * midi panics the system right after bootup But the biggest problem seems to be the spontaneous rebooting. At first I thought it might have been related to the recently re-installed HPT366, no such luck there. Then I thought something in make world was causing problems, nope. It seems mainly to happen when I suspend a program.. I'll just hit Ctrl-Z and the screen blanks, and I see the video card copyright info, etc, etc. The kernel that seems to work was built on Feb 18th, and the ones that aren't are from as recently as March 13th. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal to mergemaster
Hmm, just some thoughts here: I modified mergemaster so he add's to every file he touches or installs this md5 checksum. When mergemaster reads a file and compares it, it extracts the md5 checksum form the file (if it exists) and looks if the file has been changed or not. If a new file get's installed, the md5 checksum of that file is written. For the first time you update you have the same way to go as usual. but the second time, you will be only asked for the files which have been modified. Even if 90% of the config files have new $ID's and are a lot different. If it is possible to add these checksums also in sysinstall when extracting the first time you install, nothing has to be done with commit scripts and also the first time you run mergemaster, you can run it a lot more faster than now. Martin Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 On Tue, 13 Mar 2001, Jordan Hubbard wrote: Hmmm, this is nice! I've wanted this option for a long time. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: midi causes panic on boot? + entropy gatherer works fine
On Wed, 14 Mar 2001 00:49:53 -0800, Alex Zepeda [EMAIL PROTECTED] said: Alex On Mon, Mar 12, 2001 at 04:38:50PM +0100, Szilveszter Adam wrote: I wonder if this is known? If not, I can certainly provide more information. The offending sound hw is a Creative SB 64 AWE ISAPnP card. It works fine otherwise. (as it always has) Alex Yup I'm seeing this too. SMP kernel, AWE64 PnP. If the kernel attempts to probe mpu to die, my last commit should fix that. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: random reboots...
On Wed, Mar 14, 2001 at 12:49:01AM -0800, Alex Zepeda wrote: The kernel that seems to work was built on Feb 18th, and the ones that aren't are from as recently as March 13th. D'oh. Forgot the kernel config file and dmesg output. The config file hasn't changed, but the dmesg output is (obviously) from the older kernel. - alex Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Sun Feb 18 19:07:27 PST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/ZIPPY_SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (451.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) avail memory = 125919232 (122968K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc048b000. WARNING: size of kinfo_proc (648) should be 644!!! seq0-15: Midi sequencers. Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdcf0 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: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard IOAPIC #0 intpin 19 - irq 2 IOAPIC #0 intpin 17 - irq 9 IOAPIC #0 intpin 18 - irq 10 pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 IOAPIC #0 intpin 16 - irq 11 pci1: PCI bus on pcib1 pci1: display, VGA at 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 Warning, ithread (19, irq14: ata0) is an entropy source. ata1: at 0x170 irq 15 on atapci0 Warning, ithread (20, irq15: ata1) is an entropy source. uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 2 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: Intel 82371AB Power management controller port 0x5000-0x500f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped 4000 pci0: display, VGA at 9.0 (no driver attached) fxp0: Intel InBusiness 10/100 Ethernet port 0xe400-0xe43f mem 0xdb00-0xdb0f,0xdb10-0xdb100fff irq 10 at device 10.0 on pci0 fxp0: Ethernet address 00:90:27:d1:83:6a isa0: unexpected small tag 14 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 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 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sbc0: Creative SB AWE64 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: SB16 DSP 4.16 on sbc0 midi0: SB Midi Interface on sbc0 midi1: SB OPL FM Synthesizer on sbc0 joy0: Generic PnP Joystick at port 0x200-0x207 on isa0 midi2: CTL0022 WaveTable Synthesizer at port 0x620-0x623,0xa20-0xa23,0xe20-0xe23 on isa0 emu2: DRAM size = 512KB unknown: PNP0303 can't assign resources unknown: PNP0f13 can't assign resources sio0: 16550A-compatible COM port at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A unknown: PNP0700 can't assign resources ppc0: ECP parallel printer port at port 0x378-0x37f,0x778-0x77a irq 7 drq 3 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio1: 16550A-compatible COM port at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IPsec: Initialized Security Association Processing. ncp_load: [210-213] ad0: 29314MB IBM-DTLA-307030 [59560/16/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s3a WARNING: / was not properly dismounted SMP: AP CPU #1 Launched! lock order reversal 1st vnode interlock last acquired @ ../../ufs/ffs/ffs_vfsops.c:396 2nd 0xc03ff0a0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:457 3rd 0xc815bc8c vnode interlock @
Re: Proposal to mergemaster
From: Martin Blapp [EMAIL PROTECTED] Subject: Re: Proposal to mergemaster Date: Wed, 14 Mar 2001 09:51:28 +0100 (CET) If it is possible to add these checksums also in sysinstall when extracting the first time you install, nothing has to be done with commit scripts and also the first time you run mergemaster, you can run it a lot more faster than now. Can you be more specific? Some diffs would certainly be easier to grasp the meaning of. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal to mergemaster
Hi Jordan, If it is possible to add these checksums also in sysinstall when extracting the first time you install, nothing has to be done with commit scripts and also the first time you run mergemaster, you can run it a lot more faster than now. Can you be more specific? Some diffs would certainly be easier to grasp the meaning of. :) Yes, I mean when we extract and install all /etc files, is it possible to add then then md5 checksum to all installed config files into the cvs header ? (With grep -v "$FreeBSD:" of course). Martin Martin Blapp, [EMAIL PROTECTED] Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal to mergemaster
Yes, I mean when we extract and install all /etc files, is it possible to add then then md5 checksum to all installed config files into the cvs header ? (With grep -v "$FreeBSD:" of course). Oh. No, not easily. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: random reboots...
On Wed, 14 Mar 2001, Alex Zepeda wrote: I haven't been able to track this down since the kernel won't panic.. but with more recent kernels I've noticed: * options NCP prevents the kernel from linking You need options LIBMCHAIN as well. We don't have mechanism for specifying dependancies between options as of yet. (sorry, should put a note in the NOTES). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: random reboots...
Alex Zepeda wrote: I haven't been able to track this down since the kernel won't panic.. but with more recent kernels I've noticed: * options NCP prevents the kernel from linking * midi panics the system right after bootup Me too Saw the NCP problem today at ctm-cvs-cur 7214. Saw the midi problem earlier but haven't put midi and seq in my kernels since then. /Me too To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal to mergemaster
Brian Somers wrote: 3. Have a cvs-aware option. If the installed and new version numbers differ, mergemaster does a cvs diff -u -rINSTALLEDVERSION newversion | patch INSTALLEDFILE. If this works, everyone's happy. If not, it forces you to modify the new file 'till there are no bits in it. Yes yes yes. Many people using mergemaster have the Repo on hand at $CVSROOT so this should be an option if not the default (when $CVSROOT is defined). For those who dont I suppose a directory could keep the unmodified versions of the currently installed files that mergemaster updates. Or maybe the versions could be fetched from the web (from cvsweb ?) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM(?) breaks r* and ftpd
Dmitry Valdov wrote: Hi! Try to make an .rhosts file and rlogin to fresh RELENG_4 or -CURRENT branch. rlogin -l dv xxx.xxx.xxx.xxx I saw the rlogin problem but somehow fixed it later my pam.conf was OK so I uncommented the ipv6 versions of the services in /etc/inetd.conf and that seemed to fix it. As I did this at work, I cant reproduce this now. This is on -CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed - pthread altsigstack problem
On Mon, 12 Mar 2001 18:46:16 -0500 James FitzGibbon [EMAIL PROTECTED] wrote: Both of the patches below fix the problem mentioned in PR bin/25110. The first one fixes it inside of kern_fork.c and would appear to apply the corrective behaviour regardless of whether the process uses libc_r or not. The first patch that I sent to you makes the SS_DISABLE flag setting be inherited to the child process (especially when the parent have cleared the flag), as I had mentioned in the mail to -current: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=332928+0+archive/2001/freebsd-current/20010304.freebsd-current I'm not sure that the SS_DISABLE flag setting should be inherited to the child process, but at least I can say the behavior of 5-CURRENT (and 4-STABLE) is different from that of Solaris 7, NetBSD 1.5 and FreeBSD 3.5-STABLE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal to mergemaster
At Tue, 13 Mar 2001 16:53:46 +0100, Martin Blapp wrote:
Hi,
I have made something like this and submitted a PR
http://www.freebsd.org/cgi/query-pr.cgi?pr=25771
Yep, something like this I'd like to do, but with md5 checksums,
so we do not have to say 'yes' to each file we update.
I remember some discussion about something similar.
The proposal back then was to use a text-file with each
file to just install on one line in the file.
And also to have a text-file for file which should never be
updated.
However, I belive this was turned down since this
if [ -r "${MM_PRE_COMPARE_SCRIPT}" ]; then
. "${MM_PRE_COMPARE_SCRIPT}"
fi
hook in mergemaster can be used to do that.
Using this hook the admin will have to know what he is doing :-)
/Johan K
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
On Tue, Mar 13, 2001 at 07:52:49AM -0500, Christos Zoulas wrote: Thanks so much! I wonder how come this bug remained unnoticed for such a long time! AFAIK, this isn't a bug. It's what csh has always done. (It's what IBM and Sun's csh do anyway...) To echo a newline in csh you do 'echo ""'. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
On Wed, Mar 14, 2001 at 12:41:09 +, David Malone wrote: On Tue, Mar 13, 2001 at 07:52:49AM -0500, Christos Zoulas wrote: Thanks so much! I wonder how come this bug remained unnoticed for such a long time! AFAIK, this isn't a bug. It's what csh has always done. (It's what IBM and Sun's csh do anyway...) To echo a newline in csh you do 'echo ""'. If this bug is rotten in csh as designed, it not means that it isn't the bug. Lets look from other side: "echo" is internal csh command which replace /bin/echo for speed reasons. /bin/echo;/bin/echo;/bin/echo produce 3 \n, so internal command must do the same in any case. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
On Wed, Mar 14, 2001 at 15:46:39 +0300, Andrey A. Chernov wrote: On Wed, Mar 14, 2001 at 12:41:09 +, David Malone wrote: On Tue, Mar 13, 2001 at 07:52:49AM -0500, Christos Zoulas wrote: Thanks so much! I wonder how come this bug remained unnoticed for such a long time! AFAIK, this isn't a bug. It's what csh has always done. (It's what IBM and Sun's csh do anyway...) To echo a newline in csh you do 'echo ""'. If this bug is rotten in csh as designed, it not means that it isn't the bug. Lets look from other side: "echo" is internal csh command which replace /bin/echo for speed reasons. /bin/echo;/bin/echo;/bin/echo produce 3 \n, so internal command must do the same in any case. Thinking about compatibility: Since internal 'echo' does nothing, it _not_ used in any old csh scripts, while 'echo ""' does the same thing in both old and new variants, so old scripts will works in the same way. Since old csh is not maintained anymore, we don't need to preserve exact void compatibility with unsupported and not maintained other platforms software with no practical reason. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
Since internal 'echo' does nothing, it _not_ used in any old csh scripts, while 'echo ""' does the same thing in both old and new variants, so old scripts will works in the same way. Will it change what happens if you do: set null="" echo $null (this produces nothing in "traditional" tcsh and csh)? Since old csh is not maintained anymore, we don't need to preserve exact void compatibility with unsupported and not maintained other platforms software with no practical reason. I guess we should leave it up to the tcsh folks. There are other internal csh commands which behave differently to external commands (nice and time come to mind). I think it is known that 'echo ""' is a relatively portable way of printing a blank line. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
On Wed, Mar 14, 2001 at 14:10:06 +, David Malone wrote: Will it change what happens if you do: set null="" echo $null (this produces nothing in "traditional" tcsh and csh)? It will change. I guess we should leave it up to the tcsh folks. There are other internal csh commands which behave differently to external commands (nice and time come to mind). I think it is known that 'echo ""' is a relatively portable way of printing a blank line. echo is more like as external command, even in its internal form it tends to be compatible even with SysV-isms. What non-BSD grown (i.e. SysV) csh echo prints? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
On Mar 14, 2:41pm, [EMAIL PROTECTED] (David Malone) wrote: -- Subject: Re: tcsh 6.10.00 echo;echo;echo; bug with fix | echo is more like as external command, even in its internal form it | tends to be compatible even with SysV-isms. What non-BSD grown (i.e. SysV) | csh echo prints? | | Solaris, AIX and HPUX all print nothing. I guess all csh versions | are likely to be BSD dervied, so there is likely to be a consistant | response. | | Maybe something could be done with the echo_style variable to | control what is done? Yeah, that is a good idea. I think that I'll add an echo_style "bsdbug", and leave the default alone. christos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
I agree with Andrey -- although this has the possibility of breaking old scripts that expect no output from echoing an empty variable. Since the DEC/OSF system update script only works with their ancient /bin/sh (and not with the XPG4 sh) I wouldn't be surprised to find such scripts out there... :-) + Kim | From:"Andrey A. Chernov" [EMAIL PROTECTED] | Date:Wed, 14 Mar 2001 15:46:39 +0300 | | On Wed, Mar 14, 2001 at 12:41:09 +, David Malone wrote: | On Tue, Mar 13, 2001 at 07:52:49AM -0500, Christos Zoulas wrote: | | Thanks so much! I wonder how come this bug remained unnoticed for such | a long time! | | AFAIK, this isn't a bug. It's what csh has always done. (It's what | IBM and Sun's csh do anyway...) To echo a newline in csh you do | 'echo ""'. | | If this bug is rotten in csh as designed, it not means that it isn't | the bug. | | Lets look from other side: "echo" is internal csh command which replace | /bin/echo for speed reasons. /bin/echo;/bin/echo;/bin/echo produce 3 \n, | so internal command must do the same in any case. | | -- | Andrey A. Chernov | http://ache.pp.ru/ | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: random reboots...
On Wed, 14 Mar 2001 15:48:03 +0600 (ALMT), Boris Popov [EMAIL PROTECTED] said: You need options LIBMCHAIN as well. We don't have mechanism for specifying dependancies between options as of yet. (sorry, should put a note in the NOTES). Actually, yes we do, although it's not often used. If the relevant sources are listed twice in `files', conditional on each option, then `config' will do the right thing. For example: dev/pccard/card_if.moptional card dev/pccard/card_if.moptional pccard -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
On Wed, Mar 14, 2001 at 09:54:32 -0500, Christos Zoulas wrote: Yeah, that is a good idea. I think that I'll add an echo_style "bsdbug", and leave the default alone. Even if we left old default in place (which I personally not like), old code have signal handler bug, we can't just "return" from xecho(), because signal mask not set again after "if (sigintr) sigrelse(SIGINT);", we need to jump somewhere near "done:" label to get signal mask properly set again. If someone tells me that it is intentional old csh behaviour too, I will be speechless... -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
building perl 5.6.0 with `-DPERL_POLLUTE'
I've noticed that lots of the perl ports are now broken since the move to perl 5.6.0. Some examples: http://bento.freebsd.org/errorlogs/5-full/p5-Crypt-IDEA-1.01.log http://bento.freebsd.org/errorlogs/5-full/p5-Devel-Peek-0.96.log With these two in particular, the problem can be fixed by compiling perl with `-DPERL_POLLUTE' to get back the missing preprocessor definitions. Would it be worth it to compile the default 5.x perl in this manner? $ man perldelta [...] C Source Incompatibilities `PERL_POLLUTE' Release 5.005 grandfathered old global symbol names by providing preprocessor macros for extension source compatibility. As of release 5.6.0, these preprocessor definitions are not available by default. You need to explicitly compile perl with `-DPERL_POLLUTE' to get these definitions. For extensions still using the old symbols, this option can be specified via MakeMaker: perl Makefile.PL POLLUTE=1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building perl 5.6.0 with `-DPERL_POLLUTE'
* Jason R. Mastaler [EMAIL PROTECTED] [010314 12:43] wrote: I've noticed that lots of the perl ports are now broken since the move to perl 5.6.0. Some examples: http://bento.freebsd.org/errorlogs/5-full/p5-Crypt-IDEA-1.01.log http://bento.freebsd.org/errorlogs/5-full/p5-Devel-Peek-0.96.log With these two in particular, the problem can be fixed by compiling perl with `-DPERL_POLLUTE' to get back the missing preprocessor definitions. Would it be worth it to compile the default 5.x perl in this manner? No. I'd rather not keep other people's cruft in our system. It will eventually go away, and the longer we keep it as a crutch, the more people are going to be hurt by it when/if it disappears completely. Those people need to fix thier modules. :) -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tcsh 6.10.00 echo;echo;echo; bug with fix
On Mar 14, 11:24pm, [EMAIL PROTECTED] ("Andrey A. Chernov") wrote:
-- Subject: Re: tcsh 6.10.00 echo;echo;echo; bug with fix
With the new information about solaris having fixed this, I've decided
against keeping compatibility and just applying the fix you proposed.
christos
| On Wed, Mar 14, 2001 at 09:54:32 -0500, Christos Zoulas wrote:
|
| Yeah, that is a good idea. I think that I'll add an echo_style "bsdbug",
| and leave the default alone.
|
| Even if we left old default in place (which I personally not like), old
| code have signal handler bug, we can't just "return" from xecho(), because
| signal mask not set again after "if (sigintr) sigrelse(SIGINT);", we need
| to jump somewhere near "done:" label to get signal mask properly set
| again. If someone tells me that it is intentional old csh behaviour too, I
| will be speechless...
|
| --
| Andrey A. Chernov
| http://ache.pp.ru/
-- End of excerpt from "Andrey A. Chernov"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: building perl 5.6.0 with `-DPERL_POLLUTE'
On Wed, Mar 14, 2001 at 08:43:11PM -, Jason R. Mastaler wrote: I've noticed that lots of the perl ports are now broken since the move to perl 5.6.0. Some examples: http://bento.freebsd.org/errorlogs/5-full/p5-Crypt-IDEA-1.01.log http://bento.freebsd.org/errorlogs/5-full/p5-Devel-Peek-0.96.log With these two in particular, the problem can be fixed by compiling perl with `-DPERL_POLLUTE' to get back the missing preprocessor definitions. Would it be worth it to compile the default 5.x perl in this manner? No. It is not necessary to compile *Perl* with -DPERL_POLLUTE, it's enough to compile the module in question with -DPERL_POLLUTE. Thus, this is easily fixable for individual ports. For extensions still using the old symbols, this option can be specified via MakeMaker: perl Makefile.PL POLLUTE=1 What it says... Cheers, -Anton. -- May the tuna salad be with you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic and filesystem corruption
:I was cvsupping the GNATS database (the *entire* GNATS database, that :is - I didn't already have a copy) when I got this panic: How old a kernel are you running? Kirk and I have been attempting to locate the filesystem bitmap corruption for months. We've fixed a number of bugs but have yet to find a smoking gun. It is possible that it *has* been fixed but people's filesystems still contain some corruption from previous breakage. The corruption appears to be related to heavy directory activity and may or may not be related to softupdates. We just can't tell. We can't reproduce it. We thought we had found someone who could reproduce the problem at will but it turned out to be his RAID controller screwing up (where even newfs followed by an fsck would generate errors). Yahoo's test machines still occassionally show the problem, but so far it's too infrequent to get a good handle on. fsck all of your filesystems from single-user to remove the possibility of 'old' corruption (as in 'fsck', not 'fsck -p'). -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Tracking down problem with booting large kernels (bug in locore.s)
Richard Todd wrote: In message [EMAIL PROTECTED], Peter Wemm writes: Richard Todd wrote: No crashes as of here pushl $begin /* jump to high virtualized add ress */ ret /* now running relocated at KERNBASE where the system is linked to run */ begin: crashes before it gets here!!! /* set up bootstrap stack */ movlproc0paddr,%eax /* location of in-kernel pages */ I have some suspicions.. Can you do a nm on your kernel? peter@daintree[8:41pm]~-102 nm /boot/kernel/kernel |grep begin c0123689 t begin Sure. A working kernel (the one I'm booted off of now) shows: 55 ichotolot ~[11:49PM] Z% nm /boot/kernel.good5/kernel | grep begin c0128c79 t begin c0368b3f t mp_begin and one that crashes shows: 56 ichotolot ~[11:50PM] Z% nm /boot/kernel.old/kernel | grep begin c01290a9 t begin c038d49f t mp_begin Now I am confused. I can't see any logical reason why the jump to "begin" should fail like that... It is only ~168K into the text section... Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic and filesystem corruption
On Wed, Mar 14, 2001 at 04:39:53PM -0800, Matt Dillon wrote: fsck all of your filesystems from single-user to remove the possibility of 'old' corruption (as in 'fsck', not 'fsck -p'). So if an fsck -f doesn't bomb out, the filesystem should be in an okay state? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic and filesystem corruption
: :On Wed, Mar 14, 2001 at 04:39:53PM -0800, Matt Dillon wrote: : : fsck all of your filesystems from single-user to remove the possibility : of 'old' corruption (as in 'fsck', not 'fsck -p'). : :So if an fsck -f doesn't bomb out, the filesystem should be in an okay :state? : :- alex Right. Or even fsck -n from multiuser mode if all your filesystems are completely idle and synced up. I do that from cron once a week just to be sure that everything is A.O.K. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Tracking down problem with booting large kernels (bug in locore.s)
Peter Wemm wrote:
Richard Todd wrote:
In message [EMAIL PROTECTED], Peter Wemm write
s:
Richard Todd wrote:
No crashes as of here
pushl $begin /* jump to high virtualized add
ress */
ret
/* now running relocated at KERNBASE where the system is linked to run *
/
begin:
crashes before it gets here!!!
/* set up bootstrap stack */
movlproc0paddr,%eax /* location of in-kernel pages
*/
I have some suspicions.. Can you do a nm on your kernel?
peter@daintree[8:41pm]~-102 nm /boot/kernel/kernel |grep begin
c0123689 t begin
Sure. A working kernel (the one I'm booted off of now) shows:
55 ichotolot ~[11:49PM] Z% nm /boot/kernel.good5/kernel | grep begin
c0128c79 t begin
c0368b3f t mp_begin
and one that crashes shows:
56 ichotolot ~[11:50PM] Z% nm /boot/kernel.old/kernel | grep begin
c01290a9 t begin
c038d49f t mp_begin
Now I am confused. I can't see any logical reason why the jump to "begin"
should fail like that... It is only ~168K into the text section...
Actually, now I understand it completely. The problem was the location
of the stack. If text was too large, the stack (in the data segment) got
pushed beyond the limit of the temporary 4MB P==V mapping during boot.
This is (fortunately) an easy fix. SMP suffers the same problem during AP
bootstrap and needs fixing there. I've known about the SMP one for a while.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: random reboots...
On Wed, 14 Mar 2001, Garrett Wollman wrote: You need options LIBMCHAIN as well. We don't have mechanism for specifying dependancies between options as of yet. (sorry, should put a note in the NOTES). Actually, yes we do, although it's not often used. If the relevant sources are listed twice in `files', conditional on each option, then `config' will do the right thing. For example: dev/pccard/card_if.moptional card dev/pccard/card_if.moptional pccard Yes, thats why I don't like this method :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
status of KSE?
I wonder status of KSE, I am dreaming rewrite our application server using kqueue+pthread(KSE), current, we use poll()+pthread because pthread does not work with kqueue at present. -- Best regards, David Xu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CURRENT instability
Hi, With a CURRENT build/installworld from yesterday ... i get a VERY unstable system that page faults under the slightest CPU load (e.g. playing MP3's) i fortunately have a (very outdated) backup-kernel that will hopefully at least let me do new buildworld's ... I have to be off for work right now ... so i haven't got to writing a copy of one of those pagefaults. The problem is that it TRIES to sync disks (and hopefully write a crashdump) but the system is completely locked by then ... have to press the reset button. Does anyone have an idea of what might be causing these problems, or how i might be able to get some more detailed information that might be able to help you further ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl begin LOVE-LETTER-FOR-YOU.TXT.vbs I'm a signature virus. Please copy me and help me spread. end To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
