Re: fstab weirdness / UPDATING *solved!*

Hello guys, [Cc-ing the list just for the sake of the archives, so that people could see what the resolution of the case was.] Thanks for trying to help me while I was busy sleeping... here I am again. As suggested, I looked at my fstab, although I do not remember fiddling with it in a long tim

perl broken?

Different ports, similar problem: /usr/bin/perl5 -I/usr/libdata/perl/5.6.0/mach -I/usr/libdata/perl/BSDPANIMAP.xs > IMAP.xsc && mv IMAP.xsc IMAP.c /* * Copyright (c) 1998-2000 Carnegie Mellon University. All rights reserved. * * Redistribution and use in source and binar/: ?+*{} follows

panic: spin lock sched lock ...

just panic'd, couldn't even get to the ddb prompt this time ... panic: spin lock sched lock held by 0xcb34b840 for > 5 seconds cpuid = 1; lapic.id = 0100 Debugger("panic") CPU1 stopping CPUs ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Admini

syscons panic in userconfig mode (with patch)

[ cc'd to -stable since that's affected, too ] Attempting to switch VTYs in userconfig mode will lead to a null dereference in syscons. I saw some messages about this on -current, -stable, or -bugs recently, but I can't find them now. This is pretty easy to reproduce: simply boot the kernel wit

Re: fstab weirdness / UPDATING

In message <[EMAIL PROTECTED]>, Szilveszter Adam writ es: >Hello, > >On Sat, Apr 07, 2001 at 12:04:07PM -0700, David Wolfskill wrote: >> I suggest "fsck -d -p" -- the debugging output could prove useful. > >Here we go: Is this with or without the patch I committed earlier today ? -- Poul-Henning

Re: fstab weirdness / UPDATING

Hello, On Sat, Apr 07, 2001 at 12:04:07PM -0700, David Wolfskill wrote: > I suggest "fsck -d -p" -- the debugging output could prove useful. Here we go: pass1 pass1, name /dev/ad0s1a pass2 pass2, name /dev/ad0s1f pass2, name /dev/ad0s1g pass2, name /dev/ad0s1h pass2, name /dev/ad0s1d pass2, nam

Re: panic: lockmgr: draining against myself

problem appears to be fsck related ... fsck -p was only doing two out of 6 of my file systems .. manually ran fsck on each, and right now am doing a buildworld for last nights upgrade and we'll see what happens ... On Sat, 7 Apr 2001, The Hermit Hacker wrote: > > > just as a heads up, was just

Re: panic: lockmgr: draining against myself

just as a heads up, was just able to recreate it with a simple 'make install' ... didn't need the -j16 to do it ... On Sat, 7 Apr 2001, The Hermit Hacker wrote: > > doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd > with: > > panic: lockmgr: draining against myself > cpui

panic: lockmgr: draining against myself

doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd with: panic: lockmgr: draining against myself cpuid = 1; lapic.id = 0100 Debugging("panic") CPU1 stopping CPUs: 0x0001... stopped. Stopped at DEbuger+0x46: pushl %ebx trace shows: Debugger panic lockmgr vo

Re: fstab weirdness / UPDATING

Hello everybody, I am sorry to report that the fix committed to preen.c by phk recently did not fix the problem for me entirely. I have: ad0 with partitions within s1 a through h (ad0s1a->ad0s1h) and ad1s1a. Upon rebooting (after a clean shutdown) with an up-to-date kernel and userland, all th

Re: fstab weirdness / UPDATING

>Date: Sat, 07 Apr 2001 09:08:41 +0200 >From: Poul-Henning Kamp <[EMAIL PROTECTED]> >Yup, seems like i goofed that patch. Can you try this for me ? OK; it works much better with the patch: it seems to work correctly, from what I've tested so far. [Below is a sketch of what I did, so folks wil