Re: ghostscript-gnu build broken

2002-01-14 Thread Andreas Klemm
On Mon, Jan 14, 2002 at 08:17:39AM +0200, John Hay wrote: Do you think its possible to put that logic into the port ? I looked into it a bit. I think it is better if automake don't have to be run. What about removeing files/patch-hpijs-1.0:configure.in and patch the port Makefile with the

Re: panic during fdisk'ing a md(4) device

2002-01-14 Thread Michael Reifenberger
Hi, more food: The kernel startup is: ... vga: ... makedev(116,65538) make_dev(maj=116,min=65538,name=ad0) ad0: ... makedev(116,65546) make_dev(maj=116,min=65546,name=ad1) ad1: ... acd0: ... Mounting root from ufs:/dev/ad0s3a makedev(116,65538) (?!?!? Why, where)

Re: panic during fdisk'ing a md(4) device

2002-01-14 Thread Bruce Evans
On Mon, 14 Jan 2002, Michael Reifenberger wrote: Hi, more food: The kernel startup is: ... vga: ... makedev(116,65538) make_dev(maj=116,min=65538,name=ad0) ad0: ... makedev(116,65546) make_dev(maj=116,min=65546,name=ad1) ad1: ... acd0: ... Mounting root from ufs:/dev/ad0s3a

Re: panic during fdisk'ing a md(4) device

2002-01-14 Thread Michael Reifenberger
On Tue, 15 Jan 2002, Bruce Evans wrote: ... Yes, it is a bit confusing. sys/types.h gives the userland version. Only as confusing as the rest of the dk* code :-) Try this version. Only disklabel.h has many changes. The code for avoiding creation of bogus 'c' partitions didn't work at

Re: cvs commit: src/sbin/ping ping.c

2002-01-14 Thread Ruslan Ermilov
On Mon, Jan 14, 2002 at 06:33:35AM -0800, Ruslan Ermilov wrote: ru 2002/01/14 06:33:35 PST Modified files: sbin/pingping.c Log: Fixed two bugs with the -l preload option: - first ping after a preload was sent undelayed - we could send more than -c

ACPI messages.

2002-01-14 Thread Magnus B{ckstr|m
I put CURRENT on a new Dell Inspiron 4100 laptop this weekend. Works fine, but I keep getting these messages: ACPI-0294: *** Error: Method execution failed, AE_AML_OPERAND_TYPE The messages are logged once every few seconds, and every time I e g remove or insert a battery. I'm not sure

panic mutex filedesc structure not owned at /usr/src/sys/kern/kern_mutex.c:223

2002-01-14 Thread David Wolfskill
CVSup done just before 4 AM (US/Pacific) form cvsup14. Got this during attempted multi-user boot: Routing daemons:. Additional daemons: syslogdJan 14 08:47:51 freebeast syslogd: kernel boot file is /boot/kernel/kernel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe

Panic mutex filedesc structure not owned at /usr/src/sys/kern/kern_mutex.c:223

2002-01-14 Thread David Wolfskill
Once more, with feeling (sorry, gang... :-(). CVSupped this morning (just before 4 AM, US/Pacific (8 hrs. west of GMT) from cvsup14. Booting yielded: Routing daemons:. Additional daemons: syslogdJan 14 08:47:51 freebeast syslogd: kernel boot file is /boot/kernel/kernel . Doing additional

Re: Panic mutex filedesc structure not owned at /usr/src/sys/kern/kern_mutex.c:223

2002-01-14 Thread Alfred Perlstein
* David Wolfskill [EMAIL PROTECTED] [020114 08:57] wrote: Once more, with feeling (sorry, gang... :-(). CVSupped this morning (just before 4 AM, US/Pacific (8 hrs. west of GMT) from cvsup14. Booting yielded: Seigo Tanimura has a patch for this, just remove the extranious FILEDESC_UNLOCK

Where to put errors for ports only in current?

2002-01-14 Thread Jan Stocker
Hi, where i've to post a error regarding an installed software from ports, which only occurs on current? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: Where to put errors for ports only in current?

2002-01-14 Thread Christopher Schulte
-ports and -current would be appropriate, I'd think. At 08:01 PM 1/14/2002 +0100, Jan Stocker wrote: Hi, where i've to post a error regarding an installed software from ports, which only occurs on current? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in

Re: Where to put errors for ports only in current?

2002-01-14 Thread Sheldon Hearn
On Mon, 14 Jan 2002 13:06:52 CST, Christopher Schulte wrote: -ports and -current would be appropriate, I'd think. No! Cross-posting should not be encouraged. Either -ports or -current, depending on what the problem is. If you're not sure, try -current, since the fact that it works in

new panic under -current

2002-01-14 Thread Michael Reifenberger
Hi, a new panic while surfing under X: GNU gdb 4.18 Copyright 1998 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.

Re: Where to put errors for ports only in current?

2002-01-14 Thread Marc Recht
where i've to post a error regarding an installed software from ports, which only occurs on current? How about writing the port maintainer ? Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: Panic mutex filedesc structure not owned at /usr/src/sys/ke

2002-01-14 Thread John Baldwin
On 14-Jan-02 Alfred Perlstein wrote: * David Wolfskill [EMAIL PROTECTED] [020114 08:57] wrote: Once more, with feeling (sorry, gang... :-(). CVSupped this morning (just before 4 AM, US/Pacific (8 hrs. west of GMT) from cvsup14. Booting yielded: Seigo Tanimura has a patch for this, just

RE: sudo busted after recent upgrade to -current

2002-01-14 Thread John Baldwin
On 14-Jan-02 M. Warner Losh wrote: OK. I did a make buildworld/installworld. I did a mergemaster and made sure that /etc/pam.d was there. I also rebuilt sudo 1.6.4 via the ports system (I changed the version number there from the old one to this). However, now when I type sudo it says,

Re: new panic under -current

2002-01-14 Thread Sheldon Hearn
On Mon, 14 Jan 2002 20:43:11 +0100, Michael Reifenberger wrote: syncing disks... panic: bwrite: buffer is not busy??? Uptime: 4h47m36s I can get these pretty easily by using modules that are out of sync with the kernel. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: sudo busted after recent upgrade to -current

2002-01-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED] John Baldwin [EMAIL PROTECTED] writes: : : On 14-Jan-02 M. Warner Losh wrote: : OK. I did a make buildworld/installworld. I did a mergemaster and : made sure that /etc/pam.d was there. I also rebuilt sudo 1.6.4 via : the ports system (I changed the

Re: new panic under -current

2002-01-14 Thread John Baldwin
On 14-Jan-02 Sheldon Hearn wrote: On Mon, 14 Jan 2002 20:43:11 +0100, Michael Reifenberger wrote: syncing disks... panic: bwrite: buffer is not busy??? Uptime: 4h47m36s I can get these pretty easily by using modules that are out of sync with the kernel. That wasn't his real panic.

Re: sudo busted after recent upgrade to -current

2002-01-14 Thread John Baldwin
On 14-Jan-02 M. Warner Losh wrote: In message: [EMAIL PROTECTED] John Baldwin [EMAIL PROTECTED] writes: : : On 14-Jan-02 M. Warner Losh wrote: : OK. I did a make buildworld/installworld. I did a mergemaster and : made sure that /etc/pam.d was there. I also rebuilt sudo 1.6.4

Re: Panic mutex filedesc structure not owned at /usr/src/sys/ke

2002-01-14 Thread David Wolfskill
Date: Mon, 14 Jan 2002 12:01:12 -0800 (PST) From: John Baldwin [EMAIL PROTECTED] Seigo Tanimura has a patch for this, just remove the extranious FILEDESC_UNLOCK from the bottom of the unp_externalize function. You could commit it then if it fixes a bug. :) That fix seems to do the trick for

Re: new panic under -current

2002-01-14 Thread Sheldon Hearn
On Mon, 14 Jan 2002 12:37:16 PST, John Baldwin wrote: I can get these pretty easily by using modules that are out of sync with the kernel. That wasn't his real panic. If you read teh whole log, a vrele() called from fdrop_locked() did a vput(0x0), i.e. vput(NULL) which resulted in a

Re: new panic under -current

2002-01-14 Thread Alfred Perlstein
* Michael Reifenberger [EMAIL PROTECTED] [020114 11:47] wrote: Hi, a new panic while surfing under X: Can you cvsup and try to reproduce this? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

rpcbind panic

2002-01-14 Thread Michael McGoldrick
Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT from cvsup.freebsd.org. The panic message is hand copied. Please send me a mail if other details (eg dme sg) are required. Kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault

RE: rpcbind panic

2002-01-14 Thread John Baldwin
On 14-Jan-02 Michael McGoldrick wrote: Kernel and world built with sources cvsupped as of Mon Jan 14 18:44:04 GMT from cvsup.freebsd.org. The panic message is hand copied. Please send me a mail if other details (eg dme sg) are required. A traceback would be most useful. Type 't' in ddb.

Re: new panic under -current

2002-01-14 Thread Michael Reifenberger
On Mon, 14 Jan 2002, Alfred Perlstein wrote: ... Can you cvsup and try to reproduce this? Do you have some new -current patches in mind which could affect the problem? My -current is as of today (with some local patches from bde regarding slice-handling which shouldn't be related here). I've

Re: sudo busted after recent upgrade to -current

2002-01-14 Thread Michael Reifenberger
On Mon, 14 Jan 2002, John Baldwin wrote: ... Sheesh, ok. :) I had a problem with sudo a while back due to pam not falling back to other in pam.conf properly when the pam.d dir existed. Have you tried copying /etc/pam.d/other to /etc/pam.d/sudo? I see this too when I do `su - pgsql`. I have

Trace for rpcbind panic

2002-01-14 Thread Michael McGoldrick
The trace was short, so I wrote the whole thing down. _mtx_unlock_sleep(c232c834,0,0,0) at _mtx_unlock_sleep+0x9f unp_externalize(c0b6ab00,c0b6ac00,cb5d3ccc,cb5d3c8c,cb5d3ccc) at unp_externalize +0x38e soreceive(ca29d420,cb5d3c18,cb5d3c44,0,cb5d3c1c) at soreceive+0x376

RE: Trace for rpcbind panic

2002-01-14 Thread John Baldwin
On 14-Jan-02 Michael McGoldrick wrote: The trace was short, so I wrote the whole thing down. That one is fixed already, re-cvsup. Also, you should probably be running with INVARIANTS turned on in -current as that would give more useful error messages. _mtx_unlock_sleep(c232c834,0,0,0) at

Re: sudo busted after recent upgrade to -current

2002-01-14 Thread M. Warner Losh
In message: [EMAIL PROTECTED] John Baldwin [EMAIL PROTECTED] writes: : Sheesh, ok. :) I had a problem with sudo a while back due to pam not falling : back to other in pam.conf properly when the pam.d dir existed. Have you tried : copying /etc/pam.d/other to /etc/pam.d/sudo? No. I

Re: ACPI messages.

2002-01-14 Thread Takanori Watanabe
In message [EMAIL PROTECTED], M agnus B{ckstr|m wrote: I put CURRENT on a new Dell Inspiron 4100 laptop this weekend. Works fine, but I keep getting these messages: ACPI-0294: *** Error: Method execution failed, AE_AML_OPERAND_TYPE The messages are logged once every few seconds, and every

sudo redu

2002-01-14 Thread M. Warner Losh
OK. This looks like a problem in 1.6.4p1 of sudo. It isn't a problem with 1.6.3p7_2. 1.6.4 works on -stable, but not -current. It apparently added a call to pam_setcred: 453) Now call pam_setcreds() to setup creds for the target user when PAM is in use. On Linux this often sets