Re: -CURRENT boot problems: loader, kernel

So I'm not the only one having problems. . . FreeBSD/i386 bootstrap loader, Revision 1.0 ([EMAIL PROTECTED], Fri Nov 9 01:58:33 PST 2001) name not found Assert failed: (false), function ficlCompileSoftcore, file softcore.c, line 291 I got the system running by: booting up with a set of 'fixi

sys/dev/usb/uhci.c needs patch to compile

I've been having to apply the following patch to get a kernel compile to go through. The problem sees to be that when you have options UHCI_DEBUG AND options DIAGNOSTIC some conditional code gets added that trys to call uhci_dump_ii which isn't defined anywhere. Also on line

Re: HEADS UP: -CURRENT switched from pam.conf to pam.d

The convert script seems to have an error. su-2.05# perl -w /usr/src/etc/pam.d/convert.pl /etc/pam.conf /(\$FreeBSD: src/: unmatched () in regexp at /usr/src/etc/pam.d/convert.pl line 63. su-2.05# --On Saturday, January 12, 2002 3:09 PM +0100 Dag-Erling Smorgrav <[EMAIL PROTECTED]> wrote:

Re: size of /usr/src

My current /usr/src is 524M. That include 83M of kernel object files in /usr/src/sys/i386/compile from a couple of different kernel builds. /usr/obj which holds the object files from a buildworld is 460M. If you're going to do a full cvs repository then /home/ncvs on my system is 1391M. --On

miniperl not found error?

okI give up! I've been getting this error for ages when doing a 'make depend' on the current tree and up to now I've just done a 'make -k' to get it to work. Whats the final solution so I don't have to do this? What stupid thing have I missed somewhere along the line. ===> gnu/usr.bin/per

Re: 5.0-RC2 won't install (zf_read & vm_fault) while 4.7 will

--On Friday, January 10, 2003 5:36 PM -0800 "Gary W. Swearingen" <[EMAIL PROTECTED]> wrote: I got an old P100 I'm preparing for NAT duty at a Linux meeting and I tried to install 5.0-RC2 on it. Near end of mfsroot.flp loading I get: zf_read: unexpected EOF but it continues booting. Just

Re: 5.0 Freezes under high load with SMP.

--On Tuesday, January 14, 2003 8:15 PM +0100 Wilko Bulte <[EMAIL PROTECTED]> wrote: On Tue, Jan 14, 2003 at 11:12:30AM -0800, Nate Lawson wrote: On Tue, 14 Jan 2003, wade wrote: > Although GENERIC functions perfectly, when I enable SMP in > GENERIC, the box freezes during big build jobs ( i.e. b

bad ACPL asl's on motherboards

I gather that there are quite a few Motherboards with bad ACPI asl's on them. I know that my Abit BP6 sure has problems. As a result I can't run ACPI. What are those of us with these motherboards supposed to to? I realize that we can use acpidump to get the asl, correct it, and then recompile

make release errors

I've been trying to do a 'make release' the last couple of weeks and keep getting the following error. Is this something on my end? I assume other aren't having problems with it being this close to release date. Any suggestions on the fix? To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: make release errors

--On Thursday, January 16, 2003 6:12 AM -0800 "Joel M. Baldwin" <[EMAIL PROTECTED]> wrote: I've been trying to do a 'make release' the last couple of weeks and keep getting the following error. geeze time for a coffee. sorry people. here is the er

Re: Server locking hard -- A LOT!!!

Check your RAM. Check your BIOS settings. Try running the system with the failsafe settings if your BIOS has that. If all else fails put the debug options into the kernel, add a serial console, and see if you can break into ddb. --On Tuesday, February 04, 2003 10

requesting vinum help

Could a vinum guru please contact me via email? I've lost 2 vinum volumes as a result of the latest fiasco and naturally am eager to figure out what's going on and recover the data. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/list

Re: requesting vinum help

Geeze! Not only aren't there any emails, but I've started a full blown thread! --On Tuesday, November 25, 2003 8:39 AM -0800 "Joel M. Baldwin" <[EMAIL PROTECTED]> wrote: Could a vinum guru please contact me via email? I've lost 2 vinum volumes as a result of the

natd core dumping with bus error

Something has messed up natd. If I don't have the punch_fw option in the /etc/natd.conf file it eventuially core dumps with a bus error. I think this started JUST BEFORE the KSE commit. /etc/natd.conf: ( note that this works. comment out the punch_fw option and it c

Re: natd core dumping with bus error

in ?? () ># 7 0x08048131 in ?? () > (gdb) > > > If you need something else to diagnose this let me know and I'll > do whatever I can to help. --On Monday, July 08, 2002 2:26 AM -0700 Luigi Rizzo <[EMAIL PROTECTED]> wrote: > Could you clarify the problem ? > I

Re: natd core dumping with bus error

I'll have to ditto that. no ppp, just natd, and sysctl stuff is set as listed below. Without the punch-fw directive in /etc/natd.conf, natd will core dump. I just verified that without the directive it core dumps. The problem still exits. It isn't an instant dump, it runs for a while. --On M

Re: Do we still need portmap(8)?

Shouldn't ALL of the files in /bin, /usr/bin, /usr/include, /usr/lib etc be replaced during an installworld? I've always looked for files older than the last installworld and moved them aside thinking that they're obsolete. ( aside, not delete, just in case ) --On Monday, October 07, 2002 8:51

Why is my -current system Hard Locking?

I'm getting quite frustrated with -current. I've been running it for years and had relatively few problems. However for quite some time now I've had a problem with Hard Locks. By Hard Lock I mean that the system doesn't respond to ether traffic, the keyboard doesn't respond, the capslock, numlo

Re: Why is my -current system Hard Locking?

--On Tuesday, November 05, 2002 9:55 AM -0500 Andrew Gallatin <[EMAIL PROTECTED]> wrote: Joel M. Baldwin writes: <...> > don't think this is related to the X FP problem ( although I am > running X11 ). There have been many times when I'd walk in the

Re: Why is my -current system Hard Locking?

There isn't any indication of a panic. The system just locks up and is non responsive. --On Tuesday, November 05, 2002 9:25 PM -0800 Steve Kargl <[EMAIL PROTECTED]> wrote: This sounds good, but isn't it. X doesn't have control of the graphics and kbd on my system. Only xdm and clients are r

Re: Why is my -current system Hard Locking?

No change, the system is still Hard Locking. It did it 4 times yesterday. The next steps for me are: 1.) Get a serial console working. Maybe I'll get some indication of what's happening that way. 2.) When the serial console is working, see if I can break into ddb after a Hard Lock. Is there

Re: Why is my -current system Hard Locking?

--On Wednesday, November 06, 2002 9:23 PM -0600 Sean Kelly <[EMAIL PROTECTED]> wrote: . . . snip . . . I just came across this problem for the first time on my -CURRENT from Wed Oct 30. I was in the middle of reading a message in mutt (my MUA) on the console and the system just froze. I was al

duplicate lock

FreeBSD outel.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Nov 7 05:13:19 PST 2002 [EMAIL PROTECTED]:/disk2/usr.src/sys/i386/compile/testGeneric.nonsmp i386 acquiring duplicate lock of same type: "inp" 1st inp @ ../../../netinet/udp_usrreq.c:290 2nd inp @ ../../../netinet/udp_usrreq.c:290 thi

dnet causes Hard Lock on SMP kernel? ( was 'Why is my -currentsystem Hard Locking?' )

I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG t

Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my-current system Hard Locking?' )

--On Thursday, November 07, 2002 6:07 PM -0500 Ray Kohler <[EMAIL PROTECTED]> wrote: 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

Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my-current system Hard Locking?' )

--On Friday, November 08, 2002 8:45 AM +0900 Jun Kuriyama <[EMAIL PROTECTED]> wrote: At Thu, 7 Nov 2002 22:55:56 + (UTC), Joel M. Baldwin <[EMAIL PROTECTED]> wrote: I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. N

Panics instead of Hard Locks

Since going from a SMP to nonSMP kernel the Hard Locks don't seem to be happening. However I'm getting panics. I've gotten 4 'sleeping thread owns a mutex' panics and one each of 'Assertion i != 0 failed at ../../../kern/subr_witness.c:669' and 'Duplicate free of item 0xc3895cc0 from zone 0xc0ea

Re: Panics instead of Hard Locks

If there's a race why hasn't it been fixed in the main tree? A swap issue makes sense. If I've been down long enough I get swamped with email when I come back up. A bug in the latest procmail yields 130M processes that fill up swap and make the system be swap bound. The solution is the followi

dnet causes panic ( was Hard Lock )

Well I'm not getting Hard Locks when I try running dnet on a SMP kernel. Instead I've gotten the following panics. It turns out I can run a single non threaded dnet process when I invoke it thus: 'dnet -cpunum 0' - lock order rev

more info from panic from running dnet on SMP kernel ( lockorder reversal, recursed on non-recursive lock )

running dnet on a SMP kernel causes the kernel to panic. lock order reversal 1st 0xc2c803e8 process lock (process lock) @ ../../../kern/kern_fork.c:571 2nd 0xc03cfce0 proctree (proctree) @ ../../../kern/kern_fork.c:596 recursed on non-recursive lock (sleep mutex) process lock @ ../../../kern/k

Re: SMP stability ? [was Re: more info from panic from runningdnet on SMP kernel]

--On Sunday, November 17, 2002 11:36 AM +0100 Thierry Herbelot <[EMAIL PROTECTED]> wrote: Le Sunday 17 November 2002 10:50, Joel M. Baldwin a écrit : running dnet on a SMP kernel causes the kernel to panic. [Hijacking another thread ?] No problem, lets compare notes. I haven'

Re: more info from panic from running dnet on SMP kernel ( lockorder reversal, recursed on non-recursive lock )

tes Laboratories On Sun, 17 Nov 2002, Joel M. Baldwin wrote: running dnet on a SMP kernel causes the kernel to panic. lock order reversal 1st 0xc2c803e8 process lock (process lock) @ . . . snip . . . To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: SMP stability ? [was Re: more info from panic from runningdnet on SMP kernel]

ack, I keep forgetting there are TWO conf dirs now. I didn't even see those options. I'll try this also. --On Sunday, November 17, 2002 8:55 PM +0100 Thierry Herbelot <[EMAIL PROTECTED]> wrote: Le Sunday 17 November 2002 20:46, Robert Watson a écrit : I've seen several reports that using a

panic: sleeping thread owns a mutex - with debug traceback

Under heavy system load and heavy swapping I had the following panic occur. - Panic message from the serial console: panic: sleeping thread owns a mutex cpuid = 1; lapic.id = 0100 Debugger("panic") Stopped at Debugger+0x55: x

Re: SMP stability ? [was Re: more info from panic from running

I haven't had any Hard Locks since I upgraded the BIOS on my BP6 from LP to RU and cvsup/buildworld/installworld again. At the moment I'm thinking that my system is stable again, but won't feel comfortable with that until I do some more stress testing. I've gotten a panic, but I think its unrela

Re: panic: sleeping thread owns a mutex - with debug traceback

--On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson <[EMAIL PROTECTED]> wrote: On Wed, 20 Nov 2002, Robert Watson wrote: Hmm. Another thread has decided to sleep while holding an inpcb mutex. Any chance this can be reproduced while running WITNESS? If so, you should get a panic ea

Re: panic: sleeping thread owns a mutex - with debug traceback

--On Wednesday, November 20, 2002 2:27 PM -0500 John Baldwin <[EMAIL PROTECTED]> wrote: On 20-Nov-2002 Joel M. Baldwin wrote: --On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson <[EMAIL PROTECTED]> wrote: On Wed, 20 Nov 2002, Robert Watson wrote: Hmm. Anothe

more info - Re: panic: sleeping thread owns a mutex - withdebug traceback

--On Wednesday, November 20, 2002 2:27 PM -0500 John Baldwin <[EMAIL PROTECTED]> wrote: On 20-Nov-2002 Joel M. Baldwin wrote: --On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson <[EMAIL PROTECTED]> wrote: On Wed, 20 Nov 2002, Robert Watson wrote: Hmm. Another thread

Re: more info - Re: panic: sleeping thread owns a mutex - withdebug traceback

yes, LONG before I posted the first time. I've even swaped the memory from another system. The problem ISN'T the memory. --On Wednesday, November 20, 2002 9:47 PM -0800 Nate Lawson <[EMAIL PROTECTED]> wrote: Wow, I haven't seen so many panics from one person before. Tried memtest86.com yet?

Re: more info - Re: panic: sleeping thread owns a mutex - withdebug traceback

--On Wednesday, November 20, 2002 10:12 PM -0800 Steve Kargl <[EMAIL PROTECTED]> wrote: On Wed, Nov 20, 2002 at 09:59:32PM -0800, Joel M. Baldwin wrote: --On Wednesday, November 20, 2002 9:47 PM -0800 Nate Lawson <[EMAIL PROTECTED]> wrote: > Wow, I haven't seen so many pa

Hard Lock info

I came home last night and found the system Hard Locked. ^ Stopped at siointr1+0xf4: movl$0,brk_state1.0 db> db> show locks db> ps pid proc addruid ppid pgrp flag stat wmesgwchan cmd 71987 c3557000 d364b000 1006 71985 71985 0004000 norm[LOCK Giant c03d01a0] for

Re: Hard Lock info

.) Does anything look out of place in the trace or ps? 2.) What additional commands should I do next time this happens? This is on a SMP kernel less than a couple of days old. The dmesg of the system is attached. --On Saturday, November 23, 2002 12:07 PM -0800 "Joel M. Baldwin" <[EM

dev/usb/uhci.c is messed up again

/usr/src/sys/dev/usb/uhci.c is messed up again for those of us that have the kernel compiled with UHCI_DEBUG. The following patch appears to get it to at least compile. problem summary: 1.) uhci_dump_ii is defined twice, starting at lines 805 and 920. 2.) a missing ; at the e

can't make release - don't know how to make maninstall inusr.bin/strip

I've been trying to do a 'make release' for a week or two and I keep getting the following error. I've cvsuped, make buildworld, make installworld, reboot, a number times hoping for it to work, but no go. Am I doing something wrong, or is there something that is yet to be fixed? su-2.05# m