I got this a few days ago. Apparently there was some form of problem
with the vm subsystem (I'm speculating here). What I did to fix it was
to re-cvsup the source tree (after killing non-essential processes) and
rebuilding only the kernel. After compiling and installing the new
kernel, I reboot
On Monday, 5 July 1999 at 15:42:13 -0700, Tom Pavel wrote:
>
>> On Sat, 3 Jul 1999, Peter Wemm <[EMAIL PROTECTED]> writes:
>
>> A few key suggestions for people still along for the ride:
>>
>> 1: When you've got a good running kernel that you're happy with, do yourself
>> a big favour and cop
> On Sat, 3 Jul 1999, Peter Wemm <[EMAIL PROTECTED]> writes:
> A few key suggestions for people still along for the ride:
>
> 1: When you've got a good running kernel that you're happy with, do yourself
> a big favour and copy it from /kernel to /kernel.ok or something like that.
> So, when
In article <[EMAIL PROTECTED]>, Matthew
Dillon <[EMAIL PROTECTED]> wrote:
> Hey, I just had a thought... and a question. When we are using
> cvsup to keep a local CVS reposity in sync, can we tag our local
> CVS resposity without cvsup deleting the tags?
Yes, you can do it if you're
Try booting kernel.old . It's supposed to be the previous kernel. If
that does not work, I can send you one that does work, so you can at
least compile a new kernel.
Nick
On Fri, 2 Jul 1999, Alexander Langer wrote:
> Thus spake Nick Hibma ([EMAIL PROTECTED]):
>
> Hello again!
>
> > If you ar
What makes you think that?
> interesting. i thought this was a netscape issue.
>
> In reply:
> > If you are still running current, please cvsup the newest sources. This
> > problem has been solved in the past few days. It showed up on saturday
> > evening after a commit on McKusick and most of
Matthew Dillon wrote:
> :This doesn't mean it's OK for committers to screw things up for fun, but
> :we're only human. We do try and keep it in fairly good condition
> :(remember, the developers depend on it working for development), but
> :mistakes happen..
> :
> :Cheers,
> :-Peter
>
> Hey,
:This doesn't mean it's OK for committers to screw things up for fun, but
:we're only human. We do try and keep it in fairly good condition
:(remember, the developers depend on it working for development), but
:mistakes happen..
:
:Cheers,
:-Peter
Hey, I just had a thought... and a question.
> There might still be one or two remaining, but these should be very
> infrequent.
The panice happened during make world with two setiathome clients.
Is this a new one or one known to be fixed?
Thanks
PS: June 30 kernel does not have this problem so far.
Tammy
Stack trace and dmesg follows:
Mike Smith wrote:
> >
> > The kernel that made the problem is 2 days old. (From Wednesday).
> > Actually, I even can´t compile a new kernel/world, cause it reboots and
> > hangs all the time.
>
> Welcome to -current. Time to learn about keeping a working kernel
> around at all times.
I'll re
>
> The kernel that made the problem is 2 days old. (From Wednesday).
> Actually, I even can´t compile a new kernel/world, cause it reboots and
> hangs all the time.
Welcome to -current. Time to learn about keeping a working kernel
around at all times.
--
\\ The mind's the standard \
On 02-Jul-99 Alexander Langer wrote:
> Thus spake Nick Hibma ([EMAIL PROTECTED]):
>
> Hello again!
>
>> If you are still running current, please cvsup the newest sources. This
>> problem has been solved in the past few days. It showed up on saturday
>> evening after a commit on McKusick and mos
Thus spake Nick Hibma ([EMAIL PROTECTED]):
Hello again!
> If you are still running current, please cvsup the newest sources. This
> problem has been solved in the past few days. It showed up on saturday
> evening after a commit on McKusick and most of the problem area's have
> been identified an
interesting. i thought this was a netscape issue.
In reply:
> If you are still running current, please cvsup the newest sources. This
> problem has been solved in the past few days. It showed up on saturday
> evening after a commit on McKusick and most of the problem area's have
> been identifie
If you are still running current, please cvsup the newest sources. This
problem has been solved in the past few days. It showed up on saturday
evening after a commit on McKusick and most of the problem area's have
been identified and tracked down.
There might still be one or two remaining, but t
On 12-Aug-99 Alexander Langer wrote:
> Thus spake Matthew Jacob ([EMAIL PROTECTED]):
>
>> panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
>
> I got this very often the last days, too.
>
> Actually I try do downgrade to 3.2, because my machines reboots 3
> times a day because
Thus spake Matthew Jacob ([EMAIL PROTECTED]):
> panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
I got this very often the last days, too.
Actually I try do downgrade to 3.2, because my machines reboots 3
times a day because of either this error or other things. -CURRENT
actua
>
> >
> > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
> >
Sorry- -current as of today, alpha. rebooting. Likely an NFS lock.
>
> It might be if you supplied some additional information, like what
> sources your kernel was built from, as a minimum. UP or SMP? What
>
> panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
I had the similar panic last night during make world. I have a
dump at home but I didn't have time to take a look this morning.
My system is dual PPro SMP, 128MB RAM, 3 SCSI UW disks with CCD,
about two day old -current. Sinc
On Thu, 1 Jul 1999, Matthew Jacob wrote:
>
> panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
>
It might be if you supplied some additional information, like what
sources your kernel was built from, as a minimum. UP or SMP? What
was the box doing when it paniced? If you
panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
21 matches
Mail list logo
