Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Apr 2000 15:49:28 +0200
From:      Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
To:        Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: panic in the morning
Message-ID:  <20000419154928.A8169@gil.physik.rwth-aachen.de>
In-Reply-To: <20000419152405.A7940@gil.physik.rwth-aachen.de>; from kuku@gilberto.physik.RWTH-Aachen.DE on Wed, Apr 19, 2000 at 03:24:05PM %2B0200
References:  <200004191044.MAA07122@gil.physik.rwth-aachen.de> <20000419152405.A7940@gil.physik.rwth-aachen.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 19, 2000 at 03:24:05PM +0200, Christoph Kukulies wrote:
> On Wed, Apr 19, 2000 at 12:44:22PM +0200, Christoph Kukulies wrote:
> > 
> > With a kernel built Apr 18th (and also today, Apr 19th) I'm getting
> > panics when starting up in multiuser mode but also strange things
> > happen when trying to boot /kernel -s
> > 
> > In the latter case I was dropped into ddb after being prompted with
> > something like mountroot>
> >  
> > I'm running i4b (isdnd) and the old PCI shims (ncr), FWIW.
> >  
> > Also I don't know if it is now a bug or a feature: I compiled DDB into
> > the kernel this morning after getting the panics (which were in strcmp()
> > or strcpy() in the kernel, process was 'sh' in the panic log. After booting
> > this DDB kernel first time the kernel didn't panic apparently but it
> > was 'shutdown' smoothly (bufdaemon was stopped and kernel was halted).
> >  
> > (looked like a feature but I couldn't see any benefit since I don't know
> > whether it really panick'ed and if, where it did).
> >  
> > All in all strange things are happening at the moment. Also ftpd
> > tells me some module could not be loaded (auth_pam).
> > 
> > I was hardly able to get up . Only with heavily hitting ^C through the daemon
> > starup phase I got the kernel running. Maybe some daemon is the
> > culprit (Mysqld, squid, sshd)?

The panic is gone. I disabled the loading of the linuxulator in /etc/rc.local
and re-brandelf'ed it. Unfortunately I have no longer any proof that
it really *was* the linux emulator (should have made a copy). So what.


-- 
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000419154928.A8169>