Date: Tue, 5 Dec 2000 01:39:55 +0100 From: Andrea Campi <andrea@webcom.it> To: John Baldwin <jhb@FreeBSD.org> Cc: Andrea Campi <a.campi@inet.it>, freebsd-current@FreeBSD.org Subject: Re: [jhb@FreeBSD.org: RE: Panic in -current] Message-ID: <20001205013955.A2351@webcom.it> In-Reply-To: <XFMail.001129115020.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Wed, Nov 29, 2000 at 11:50:20AM -0800 References: <20001129200041.M92759@inet.it> <XFMail.001129115020.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> >
> > db> x/i,10 0xc025ad3c
> > scrn_timer: pushl %ebp
> > [...]
> >
> > nm just confirmed this, so it definitely looks like scrn_timer is to blame
> > here. Any other instructions? ;-) For the time being, vidcontrol -t off
> > (seems to) keep the machine up.
> >
> > Bye,
> > Andrea
>
> Weird, I don't see anything offhand that syscons is doing that would cause it
> to leak Giant. Hmm. Can you add a the same code before the mtx_enter() of
Having gone through yet another series of cvsup - make kernel - panics, I can
now confirm this happens if and only if I have VESA defined. A
vidcontrol -t off
stops the panics. Now I will try to understand what's up, but I should warn you
that I'm not really confident with this part of the kernel yet.
More details: this is an IBM Thinkpad laptop with APM enabled and in the kernel.
As usual, any hint is more than welcome. This used to work...
Bye,
Andrea
--
The three Rs of Microsoft support: Retry, Reboot, Reinstall.
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?20001205013955.A2351>