Blaz Zupan <[EMAIL PROTECTED]> wrote:
} > } > start adding/removing things one-by-one from GENERIC until it looks
} > } > like the kernel that fails. This should make it obvious what is
} > } > causing it to do this and that would be very helpful info indeed!
} >
} > I have started this process, but I have only gotten through one iteration
} > because I got too tired to work on it last night. ;)
}
} Let me help you: try adding back "device apm". It helped me with a simmilar
} problem on some different hardware.
That fixed it. Thanks, Blaz!
So now I have to wonder why this fixed the problem? Is this a sign of
some other problem, or is it just something that is an issue with
non-Intel i386 hardware?
-Patrick
Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
