Re: r330538 broken CURRENT on MacBookPro
On Thu, Mar 15, 2018 at 08:56:23PM -0600, Warner Losh wrote: > On Thu, Mar 15, 2018 at 7:55 PM, huanghwh <huang...@163.com> wrote: > > > Hi, > > I got this panic: > > 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'. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r330538 broken CURRENT on MacBookPro
On Thu, Mar 15, 2018 at 7:55 PM, huanghwh <huang...@163.com> wrote: > Hi, > I got this panic: > 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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re:r330539 broken CURRENT on MacBookPro
Sorry, It is r330539, not r330538. At 2018-03-16 09:55:02, "huanghwh" <huang...@163.com> wrote: >Hi, >I got this panic: >http://sw.gddsn.org.cn/freebsd/panic.jpg > > >r330538 broken CURRENT found by svn bisect > > >any idea? > > >Huang Wen Hui >___ >freebsd-current@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r330538 broken CURRENT on MacBookPro
Hi, I got this panic: http://sw.gddsn.org.cn/freebsd/panic.jpg r330538 broken CURRENT found by svn bisect any idea? Huang Wen Hui ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
console screen saver broken? -current
Up until a few months ago the following added to /etc/rc.conf would blank the screen: # /etc/rc.conf saver=green allscreens_flags=-t 60 Now that no longer works. Can someone explain how to restore the power saving screen saver please? It doesn't seem obvious from the docs or anything else. Are the current green_saver.ko and other screen saver modules still able to blank the screen? Do splash screen work? -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: console screen saver broken? -current
On Thu, Dec 11, 2014 at 8:42 PM, Alfred Perlstein alf...@freebsd.org wrote: Up until a few months ago the following added to /etc/rc.conf would blank the screen: # /etc/rc.conf saver=green allscreens_flags=-t 60 Now that no longer works. Can someone explain how to restore the power saving screen saver please? It doesn't seem obvious from the docs or anything else. Are the current green_saver.ko and other screen saver modules still able to blank the screen? Do splash screen work? -Alfred See https://wiki.freebsd.org/Newcons?highlight=%28syscons%29 screensaver No ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: console screen saver broken? -current
On Thu, Dec 11, 2014 at 9:42 AM, Alfred Perlstein alf...@freebsd.org wrote: Up until a few months ago the following added to /etc/rc.conf would blank the screen: # /etc/rc.conf saver=green allscreens_flags=-t 60 Now that no longer works. Can someone explain how to restore the power saving screen saver please? - Put this in /boot/loader.conf to use the older syscons(4) console driver by default and reboot: kern.vty=sc This lists the missing functionality in the new vt(4) driver such as screensaver: https://wiki.freebsd.org/Newcons#Feature_Comparison_with_syscons.284.29 -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
broken current
hi, 44 camlib.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libdisk;make beforeinstall cd /usr/src/lib/libdisk sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libdisk.h /usr/obj/usr/src/i386/usr/include cd /usr/src/lib/libedit;make beforeinstall cd /usr/src/lib/libedit sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 histedit.h /usr/obj/usr/src/i386/usr/include install: histedit.h: No such file or directory Getting this like 3d time as of today. Any ideas? Yevgeniy Raytsin| ITSP Extreme Telecom | phone: +380-44-2391429 | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: broken current
On Mon, Oct 01, 2001 at 10:49:16PM +0300, Gene Raytsin wrote: hi, Hi. /usr/obj/usr/src/i386/usr/include install: histedit.h: No such file or directory Getting this like 3d time as of today. Any ideas? Yeah, do what ever you do to retrieve this mailing list; then read any new messages before sending out a current is broken email. If you had done that you would have known I was working on this issue. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
oops [was: Re: broken current]
On Mon, 01 Oct 2001 at 14:37:14 -0700, David O'Brien wrote: On Mon, Oct 01, 2001 at 10:49:16PM +0300, Gene Raytsin wrote: hi, Hi. /usr/obj/usr/src/i386/usr/include install: histedit.h: No such file or directory Getting this like 3d time as of today. Any ideas? Yeah, do what ever you do to retrieve this mailing list; then read any new messages before sending out a current is broken email. If you had done that you would have known I was working on this issue. sorry man, my falt :( didn't mean to piss you off. and I am sorry for offtopic, ofcourse regards To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: oops [was: Re: broken current]
On Tue, Oct 02, 2001 at 12:43:50AM +0300, Gene Raytsin wrote: and I am sorry for offtopic, ofcourse It wasn't off topic. Users of -current just have responsibilities (such as reading the freebsd-current list) before posting about a problem. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Broken CURRENT
Looks like installworld is broken in CURRENT. The /usr/share/examples/isdn/i4runppp directory was not added to etc/mtree/BSD.usr.dist. Who's got the pointy hat? -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Broken CURRENT
From the keyboard of Crist J. Clark: Looks like installworld is broken in CURRENT. The /usr/share/examples/isdn/i4runppp directory was not added to etc/mtree/BSD.usr.dist. Who's got the pointy hat? Me. Fix just committed ... Sorry, hellmuth -- Hellmuth MichaelisTel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
