Hi
For a while I have had occasional random reboots. Today I managed to get 2
core dumps, both with the same backtrace.
It might be the case that this only happens after the system has been
resumed from S3 but I'm not sure. The second time the reboot was 30 minutes
after resume. I
Hi all,
Last night I cvsup-ed to -CURRENT and built world and kernel. Today this
machine rebooted alot by itself, with absolutely no load on it whatsoever. I
dont know how to determine what is causing the reboots, so if anyone can
give me a hint, it would be greatly appreciated. This machine acts
On Wed, Mar 14, 2001 at 03:48:03PM +0600, Boris Popov wrote:
> You need options LIBMCHAIN as well. We don't have mechanism for
> specifying dependancies between options as of yet. (sorry, should put a
> note in the NOTES).
OOps, okay. Thanks :)
OTOH, it seems that suspending a program (hi
On Wed, 14 Mar 2001, Garrett Wollman wrote:
> > You need options LIBMCHAIN as well. We don't have mechanism for
> > specifying dependancies between options as of yet. (sorry, should put a
> > note in the NOTES).
>
> Actually, yes we do, although it's not often used. If the relevant
> source
< said:
> You need options LIBMCHAIN as well. We don't have mechanism for
> specifying dependancies between options as of yet. (sorry, should put a
> note in the NOTES).
Actually, yes we do, although it's not often used. If the relevant
sources are listed twice in `files', conditional on
Alex Zepeda wrote:
>
> I haven't been able to track this down since the kernel won't panic.. but
> with more recent kernels I've noticed:
>
> * options NCP prevents the kernel from linking
> * midi panics the system right after bootup
>
Saw the NCP problem today at ctm-cvs-cur 7214.
Saw the mi
On Wed, 14 Mar 2001, Alex Zepeda wrote:
> I haven't been able to track this down since the kernel won't panic.. but
> with more recent kernels I've noticed:
>
> * options NCP prevents the kernel from linking
You need options LIBMCHAIN as well. We don't have mechanism for
specifying dep
On Wed, Mar 14, 2001 at 12:49:01AM -0800, Alex Zepeda wrote:
> The kernel that seems to work was built on Feb 18th, and the ones that
> aren't are from as recently as March 13th.
D'oh. Forgot the kernel config file and dmesg output.
The config file hasn't changed, but the dmesg output is (obvi
I haven't been able to track this down since the kernel won't panic.. but
with more recent kernels I've noticed:
* options NCP prevents the kernel from linking
* midi panics the system right after bootup
But the biggest problem seems to be the spontaneous rebooting. At first I
thought it might