Discussion:
r330538 broken CURRENT on MacBookPro
(too old to reply)
huanghwh
2018-03-16 01:55:02 UTC
Permalink
Hi,
I got this panic:
Loading Image...


r330538 broken CURRENT found by svn bisect


any idea?


Huang Wen Hui
huanghwh
2018-03-16 02:27:02 UTC
Permalink
Sorry, It is r330539, not r330538.
Post by huanghwh
Hi,
http://sw.gddsn.org.cn/freebsd/panic.jpg
r330538 broken CURRENT found by svn bisect
any idea?
Huang Wen Hui
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current
Warner Losh
2018-03-16 02:56:23 UTC
Permalink
Post by huanghwh
Hi,
http://sw.gddsn.org.cn/freebsd/panic.jpg
r330538 broken CURRENT found by svn bisect
any idea?
'trace' at the db> prompt would let us know better what's going on.

Warner
Konstantin Belousov
2018-03-16 09:57:23 UTC
Permalink
Post by Warner Losh
Post by huanghwh
Hi,
http://sw.gddsn.org.cn/freebsd/panic.jpg
r330538 broken CURRENT found by svn bisect
any idea?
'trace' at the db> prompt would let us know better what's going on.
See the other thread on current@, 'amd64: panic on -CURRENT @r330539 for
certain UEFI hosts'.

Continue reading on narkive:
Search results for 'r330538 broken CURRENT on MacBookPro' (Questions and Answers)
10
replies
*-MACBOOK/PRO QUESTION-* what one is better?
started 2009-01-30 20:13:24 UTC
laptops & notebooks
Loading...