On Tue, 30 Sep 2014 10:44:11 -0400, Mike. wrote
> On 9/29/2014 at 11:04 PM JosÃ© PÃ©rez Arauzo wrote:
> |This encoded message has been converted to an attachment.
> |Hi Mike,
> |On Mon, 29 Sep 2014 16:03:44 -0400, Mike. wrote
> |So that should put a time bracket on the issue,
> |roughly the first half of 2014.
> |can you boot 271146? Just buildkernel and installkernel. Thank
> There doesn't seem to be much, if any, interest on the part of the
> FreeBSD developers in fixing this recently-introduced issue with
> booting up FreeBSD.
The glass is half full. Always.
Did you get it to boot with 271146 as I suggested? This would really
help and see if we are hitting the same issue or not.
> Since I experience the problem only on the one notebook of mine, I'll
> just re-purpose that notebook for OpenBSD and try to find another old
> notebook that works with FreeBSD. Seems like the path of least
> resistance for me....
C'mon, don't give up now. Try the 271146, I'm trying to find out where
it exactly loops. I've done some testing and might be it'AHCI actually.
Warner Losh (the maintainer) sent at least 3 messages about this, he's
very cooperative I think.
I'll try the no-SMP thing now just to see how it works.
José Pérez Arauzo
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"