Re: start-up failure at SVN r314889
It works, thank you! On Thu, Mar 9, 2017 at 5:58 AM, Michael Butler wrote: > Per Hans .. this should fix it: > > r314953 | hselasky | 2017-03-09 04:17:43 -0500 (Thu, 09 Mar 2017) | 9 lines > Changed paths: >M /head/sys/compat/linuxkpi/common/src/linux_work.c > > Don't create any threads before SI_SUB_INIT_IF in the LinuxKPI. Else > kthread_add() will assert it is called too soon. This fixes a startup > issue when COMPAT_LINUXKPI is in enabled the kernel configuration > file. > > imb > > > > On 3/8/17 6:02 PM, Michael Butler wrote: >> >> The difference between a kernel that boots and another that won't is .. >> >> imb@toshi:/home/imb> diff -cw /sys/amd64/conf/TOSHI~ /sys/amd64/conf/TOSHI >> *** /sys/amd64/conf/TOSHI~ Wed Mar 8 10:05:09 2017 >> --- /sys/amd64/conf/TOSHI Wed Mar 8 17:33:25 2017 >> *** >> *** 373,379 >># Enable Linux ABI emulation >>#options COMPAT_LINUX32 >># Enable Linux KPI >> ! #options COMPAT_LINUXKPI >> >># Enable the linux-like proc filesystem support (requires COMPAT_LINUX >># and PSEUDOFS) >> --- 373,379 >># Enable Linux ABI emulation >>#options COMPAT_LINUX32 >># Enable Linux KPI >> ! options COMPAT_LINUXKPI >> >> # Enable the linux-like proc filesystem support (requires COMPAT_LINUX >># and PSEUDOFS) >> >> Seems to point at something in SVN r314843 :-( >> >> imb >> >> >> On 03/08/17 17:10, Eric Camachat wrote: >>> >>> I have the same issue on Dell Precision M4800. >>> >>> On Wed, Mar 8, 2017 at 6:26 AM, David Wolfskill >>> wrote: >>>> >>>> On Wed, Mar 08, 2017 at 07:55:44AM -0500, Michael Butler wrote: >>>>> >>>>> My laptop usually starts like this .. >>>>> >>>>> FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar 6 19:34:51 EST 2017 >>>>> i...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI >>>>> amd64 >>>>> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >>>>> 4.0.0) >>>>> ... >>>>> >>>>> This morning, I get this :-( >>>>> >>>>> FreeBSD 12.0-CURRENT #27 r314889M: Tue Mar 7 19:55:25 EST 2017 >>>>> i...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI >>>>> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >>>>> 4.0.0) >>>>> VT(vga): resolution 640x480 >>>>> panic: kthread_add called too soon >>>>> [ .. ] >>>>> >>>>> Any thoughts? >>>>> >>>> >>>> "uname -vp" output from my last several (successful) build/smoke-tests >>>> for head: >>>> >>>> FreeBSD 12.0-CURRENT #274 r314653M/314653:1200023: Sat Mar 4 06:46:18 >>>> PST 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY >>>> amd64 >>>> >>>> FreeBSD 12.0-CURRENT #275 r314700M/314700:1200023: Sun Mar 5 07:45:20 >>>> PST 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY >>>> amd64 >>>> >>>> FreeBSD 12.0-CURRENT #276 r314770M/314770:1200023: Mon Mar 6 05:45:44 >>>> PST 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY >>>> amd64 >>>> >>>> FreeBSD 12.0-CURRENT #277 r314842M/314842:1200023: Tue Mar 7 05:55:58 >>>> PST 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY >>>> amd64 >>>> >>>> FreeBSD 12.0-CURRENT #278 r314906M/314906:1200024: Wed Mar 8 06:05:49 >>>> PST 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY >>>> amd64 >>>> >>>> Sorry it's not more help. >>>> >>>> Peace, >>>> david >>>> -- >>>> David H. Wolfskill da...@catwhisker.org >>>> How could one possibly "respect" a misogynist, racist, bullying >>>> con-man??!? >>>> >>>> See http://www.catwhisker.org/~david/publickey.gpg for my public key. >>> >>> >>> >> ___ >> 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" -- ☀Eric ___ 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: start-up failure at SVN r314889
I have the same issue on Dell Precision M4800. On Wed, Mar 8, 2017 at 6:26 AM, David Wolfskill wrote: > On Wed, Mar 08, 2017 at 07:55:44AM -0500, Michael Butler wrote: >> My laptop usually starts like this .. >> >> FreeBSD 12.0-CURRENT #21 r314812M: Mon Mar 6 19:34:51 EST 2017 >> i...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI amd64 >> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >> 4.0.0) >> ... >> >> This morning, I get this :-( >> >> FreeBSD 12.0-CURRENT #27 r314889M: Tue Mar 7 19:55:25 EST 2017 >> i...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/sys/TOSHI >> FreeBSD clang version 4.0.0 (branches/release_40 296509) (based on LLVM >> 4.0.0) >> VT(vga): resolution 640x480 >> panic: kthread_add called too soon >> [ .. ] >> >> Any thoughts? >> > > "uname -vp" output from my last several (successful) build/smoke-tests > for head: > > FreeBSD 12.0-CURRENT #274 r314653M/314653:1200023: Sat Mar 4 06:46:18 PST > 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > FreeBSD 12.0-CURRENT #275 r314700M/314700:1200023: Sun Mar 5 07:45:20 PST > 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > FreeBSD 12.0-CURRENT #276 r314770M/314770:1200023: Mon Mar 6 05:45:44 PST > 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > FreeBSD 12.0-CURRENT #277 r314842M/314842:1200023: Tue Mar 7 05:55:58 PST > 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > FreeBSD 12.0-CURRENT #278 r314906M/314906:1200024: Wed Mar 8 06:05:49 PST > 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > Sorry it's not more help. > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > How could one possibly "respect" a misogynist, racist, bullying con-man??!? > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. -- ☀Eric ___ 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"
failed to compile base, buldworld, with -Os CFLAGS
I tried to buildworld with -Os CFLAGS, but it failed. Here is the compiling log: --- getcap.So --- cc -m32 -DCOMPAT_32BIT -march=haswell -isystem /usr/obj/usr/src/lib32/usr/include/ -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32 -fpic -DPIC -g -Os -pipe -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -DNLS -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -I/usr/src/lib/libc/../../contrib/libc-vis -DINET6 -I/usr/obj/usr/src/world32/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libmd -I/usr/src/lib/libc/../../contrib/jemalloc/include -I/usr/src/lib/libc/../../contrib/tzcode/stdtime -I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -MD -MF.depend.getcap.So -MTgetcap.So -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Qunused-arguments -I/usr/src/lib/libutil -I/usr/src/lib/msun/i387 -I/usr/src/lib/msun/x86 -I/usr/src/lib/msun/src -c /usr/src/lib/libc/gen/getcap.c -o getcap.So --- getcwd.So --- --- fnmatch.So --- cc: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: cc: note: diagnostic msg: /tmp/fnmatch-87dc57.c (http://slexy.org/view/s2ddVhTTyQ) cc: note: diagnostic msg: /tmp/fnmatch-87dc57.sh (http://slexy.org/view/s21zeFmDPU) cc: note: diagnostic msg: *** [fnmatch.So] Error code 254 make[4]: stopped in /usr/src/lib/libc -- 🌞Eric ___ 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"
sd card on hp laptop doesn't work anymore on 11-current
My SD card slot was working before, but it no longer works. looks like the mmc driver for hp laptop is gone. $ dmesg|grep -iE 'sdhc|mmc' sdhci_pci0: mem 0xd4603000-0xd46030ff irq 18 at device 0.2 on pci35 sdhci_pci0: 1 slot(s) allocated sdhci_pci0: mem 0xd4603000-0xd46030ff irq 18 at device 0.2 on pci35 sdhci_pci0: 1 slot(s) allocated sdhci_pci0: mem 0xd4603000-0xd46030ff irq 18 at device 0.2 on pci35 sdhci_pci0: 1 slot(s) allocated it was a mmc* there. $ pciconf -lv ... none1@pci0:35:0:0: class=0x0c0010 card=0x161c103c chip=0x2380197b rev=0x30 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'IEEE 1394 Host Controller' class = serial bus subclass = FireWire none2@pci0:35:0:1: class=0x088000 card=0x161c103c chip=0x2392197b rev=0x30 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'SD/MMC Host Controller' class = base peripheral sdhci_pci0@pci0:35:0:2: class=0x080501 card=0x161c103c chip=0x2391197b rev=0x30 hdr=0x00 vendor = 'JMicron Technology Corp.' device = 'Standard SD Host Controller' class = base peripheral subclass = SD host controller ... no driver attached to mmc Thanks, Eric ___ 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: Fatal trap 12: page fault while in kernel mode (FUSE related?)
FYI, works fine after changed to pkg0.isc.FreeBSD.org. # pkg update Updating repository catalogue digests.txz 100% 960KB 240.0KB/s 80.0KB/s 00:04 packagesite.txz 100% 5258KB 309.3KB/s 498.5KB/s 00:17 Incremental update completed, 0 packages processed: 0 packages updated, 0 removed and 21724 added. On Thu, Oct 31, 2013 at 9:59 AM, Kevin Oberman wrote: > On Tue, Oct 29, 2013 at 3:24 AM, Alexey Dokuchaev wrote: > > > Hi again, > > > > I was running out of space on my UFS partition and decided to use big > NTFS > > one I also have on the drive. I've mounted it with ntfs-3g and our > native > > fuse.ko. I needed the scratch space to built Open/LibreOffice on it > *LOL*. > > Well, it failed with a panic (see the excerpt from text core at the end > of > > this email; full debug info is available upon request). > > > > This is on fresh 11-CURRENT, i386. > > > > ./danfe > > > > I get a very similar panic when I attempt an rsync from a remote system > to > my NTFS drive. Very easy to reproduce. Something in fuse goes off the > rails under active R/W activity, it seems. > -- > R. Kevin Oberman, Network Engineer > E-mail: rkober...@gmail.com > ___ > 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" > ___ 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: Official FreeBSD Binary Packages now available for pkgng
browsing www.freebsd.org worked fine. tried pkg.freebsd.org it got below. Our DNS server can resolve proxy server only. Only proxy server can resolve internet sites, this is how our company force all traffic went through proxy server. Eric Network Error (dns_server_failure) Your request could not be processed because an error occurred contacting the DNS server. The DNS server may be temporarily unavailable, or there could be a network problem. If problem persists, please open a ticket with Motorola help desk; and copy and paste this page in ticket. Date/Time: 2013-10-3122:11:37 Request: GET http://pkg.freebsd.org/ Error: (dns_server_failure) Proxy Name:proxy Proxy IP: xxx.xxx.xxx.xxx Client IP: zzz.zzz.zzz.zzz Referer URL: On Thu, Oct 31, 2013 at 2:51 PM, Bryan Drewery wrote: > On 10/31/2013 3:47 PM, Eric Camachat wrote: > > It doesn't work with our (microsoft) proxy server, see below. > > > > root@basay:/usr/local/etc/pkg/repos # pkg update -f > > Updating repository catalogue > > pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz: > Service > > Unavailable > > pkg: No digest falling back on legacy catalog format > > pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/repo.txz: Service > > Unavailable > > root@basay:/usr/local/etc/pkg/repos # > > I somewhat doubt this is a DNS or SRV issue. The pkg(8) client will do > the DNS lookup and then contact the real server directly. It's more > likely your proxy is just blocking the requests. Perhaps ask your > administrator to add an exception for *.freebsd.org:80 :) > > -- > Regards, > Bryan Drewery > > ___ 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: Official FreeBSD Binary Packages now available for pkgng
Same result, neither pkg+http:// nor http+pkg:// worked with proxy server.
Eric
On Thu, Oct 31, 2013 at 2:09 PM, Bryan Drewery wrote:
> On 10/31/2013 4:06 PM, Adrian Chadd wrote:
> > ... I still think the SRV record stuff is a bad idea.
> >
> > Well, I think it's a great idea - because I plan on supporting it in
> > the next HTTP thing I write - but not having an A record is going to
> > continue to bite things.
>
> I don't like it either, it's not up to portmgr.
>
> >
> > Also, http+pkg:// isn't a defined protocol either and some strict
> > proxies may actually reject it. You should go back to the http://
> > protocol.
>
> It's not real. It's a client-side thing only. The "pkg+" is stripped
> away before the fetch. It's only intended to make people realize they
> can't just drop it into firefox and hit enter.
>
> 1.2 adds support for it which is coming soon, but it doesn't really
> change much.
>
> >
> >
> > -adrian
> >
> > (with his HTTP hat on..)
> >
> >
> > On 31 October 2013 14:04, Allan Jude wrote:
> >>
> > On 2013-10-31 16:47, Eric Camachat wrote:
> >>>> It doesn't work with our (microsoft) proxy server, see below.
> >>>>
> >>>> root@basay:/usr/local/etc/pkg/repos # pkg update -f
> >>>> Updating repository catalogue
> >>>> pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz:
> Service
> >>>> Unavailable
> >>>> pkg: No digest falling back on legacy catalog format
> >>>> pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/repo.txz:
> Service
> >>>> Unavailable
> >>>> root@basay:/usr/local/etc/pkg/repos #
> >>>>
> >>>> Eric
> >>>>
> >>>>
> >>>> On Wed, Oct 30, 2013 at 7:10 PM, Bryan Drewery
> > wrote:
> >>>>
> >>>>> We are pleased to announce that official binary packages are now
> >>>>> available for pkg, the next generation package management tool for
> > FreeBSD.
> >>>>>
> >>>>> Pkg allows you to either use ports with portmaster/portupgrade or to
> >>>>> have binary remote packages without ports.
> >>>>>
> >>>>> We have binary packages available for i386 and amd64 on
> >>>>> 8.3,8.4,9.1,9.2,10.0 and 11 (head).
> >>>>>
> >>>>> Pkg will be the default starting in FreeBSD 10.
> >>>>>
> >>>>> The pkg_install suite of tools pkg_create(1), pkg_add(1), and
> >>>>> pkg_info(1) (which ports also use), are deprecated and will be
> >>>>> discontinued in roughly 6 months. A communication regarding the
> >>>>> deprecation of the pkg_install suite of tools will be sent
> separately in
> >>>>> the future.
> >>>>>
> >>>>> If you are currently not using pkg and wish to, run the following as
> >>>>> root. Be sure not to add WITH_PKGNG=yes to your make.conf until after
> >>>>> pkg is installed.
> >>>>>
> >>>>> # cd /usr/ports/ports-mgmt/pkg && make install clean
> >>>>> # echo WITH_PKGNG=yes >> /etc/make.conf
> >>>>> # pkg2ng
> >>>>>
> >>>>> You can now either continue to use ports with
> portmaster/portupgrade, as
> >>>>> before or switch to using binary packages only.
> >>>>>
> >>>>>
> >>>>> To use binary packages:
> >>>>>
> >>>>> 1. Ensure your pkg(8) is up-to-date. 'pkg -v' should say at least
> >>>>>1.1.4_8. If it does not, first upgrade from ports.
> >>>>> 2. Remove any repository-specific configuration from
> >>>>>/usr/local/etc/pkg.conf, such as PACKAGESITE, MIRROR_TYPE, PUBKEY.
> >>>>>If this leaves your pkg.conf empty, just remove it.
> >>>>> 3. mkdir -p /usr/local/etc/pkg/repos
> >>>>> 4. Create the file /usr/local/etc/pkg/repos/FreeBSD.conf with:
> >>>>> FreeBSD: {
> >>>>> url: "http://pkg.FreeBSD.org/${ABI}/latest";,
> >>>>> mirror_type: "srv",
> >>>>> enabled: "yes"
> >>>>> }
> >>>>>
> >>>>> * Note that pkg.FreeBSD.org does not have a brows
Re: Official FreeBSD Binary Packages now available for pkgng
It doesn't work with our (microsoft) proxy server, see below.
root@basay:/usr/local/etc/pkg/repos # pkg update -f
Updating repository catalogue
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz: Service
Unavailable
pkg: No digest falling back on legacy catalog format
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/repo.txz: Service
Unavailable
root@basay:/usr/local/etc/pkg/repos #
Eric
On Wed, Oct 30, 2013 at 7:10 PM, Bryan Drewery wrote:
> We are pleased to announce that official binary packages are now
> available for pkg, the next generation package management tool for FreeBSD.
>
> Pkg allows you to either use ports with portmaster/portupgrade or to
> have binary remote packages without ports.
>
> We have binary packages available for i386 and amd64 on
> 8.3,8.4,9.1,9.2,10.0 and 11 (head).
>
> Pkg will be the default starting in FreeBSD 10.
>
> The pkg_install suite of tools pkg_create(1), pkg_add(1), and
> pkg_info(1) (which ports also use), are deprecated and will be
> discontinued in roughly 6 months. A communication regarding the
> deprecation of the pkg_install suite of tools will be sent separately in
> the future.
>
> If you are currently not using pkg and wish to, run the following as
> root. Be sure not to add WITH_PKGNG=yes to your make.conf until after
> pkg is installed.
>
> # cd /usr/ports/ports-mgmt/pkg && make install clean
> # echo WITH_PKGNG=yes >> /etc/make.conf
> # pkg2ng
>
> You can now either continue to use ports with portmaster/portupgrade, as
> before or switch to using binary packages only.
>
>
> To use binary packages:
>
> 1. Ensure your pkg(8) is up-to-date. 'pkg -v' should say at least
>1.1.4_8. If it does not, first upgrade from ports.
> 2. Remove any repository-specific configuration from
>/usr/local/etc/pkg.conf, such as PACKAGESITE, MIRROR_TYPE, PUBKEY.
>If this leaves your pkg.conf empty, just remove it.
> 3. mkdir -p /usr/local/etc/pkg/repos
> 4. Create the file /usr/local/etc/pkg/repos/FreeBSD.conf with:
> FreeBSD: {
> url: "http://pkg.FreeBSD.org/${ABI}/latest";,
> mirror_type: "srv",
> enabled: "yes"
> }
>
> * Note that pkg.FreeBSD.org does not have a browsable web page on it and
> does not have a DNS A record. This is intended as it is an SRV host.
> pkg(8) knows how to properly use it. You can use 'pkg search' to browse
> the available packages in the repository.
>
> Mirrors you may use instead of the global pkg.FreeBSD.org:
>
> pkg.eu.FreeBSD.org
> pkg.us-east.FreeBSD.org
> pkg.us-west.FreeBSD.org
>
> Your system is now ready to use packages!
>
> Refer to the handbook section on pkgng for usage at
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html
> .
> Also see 'man pkg' for examples or 'pkg help'.
>
>
> Packages are built weekly from a snapshot of the Ports Collection every
> Wednesday morning 01:00 UTC. They typically will be available in the
> repository after a few days.
>
> Pkg 1.2 will be released in the coming month which will bring many
> improvements including officially signed packages. FreeBSD 10's pkg
> bootstrap now also supports signed pkg(8) installation.
>
>
> Regards,
> Bryan Drewery
> on behalf of portmgr@
>
>
> ___
> 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"
>
___
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: Virtualbox "Settings" don't show any window (FreeBSD-10 current)
I run it on my 10-ALPHA1 without problem. There were many fix for clang/libc++ in ports recently. Try to update ports and rebuild all dependencies. Eric On Mon, Sep 16, 2013 at 7:14 AM, Mike C. wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Perhaps this is best placed in "current" list! > > - Original Message > Subject: Virtualbox "Settings" don't show any window (FreeBSD-10 current) > Date: Sun, 15 Sep 2013 18:35:02 + > From: Mike C. > To: freebsd-emulat...@freebsd.org > > > I've successfully installed virtualbox in my Latptop running Freebsd-10 > current... > > Everything seems fine except for when I click the "Settings button" it > doesn't show any window and the current windows stays "locked" (I can't > click anything)... > > Running VirtualBox from the command-line I don't see any error... > > Has anyone tried VirtualBox in FreeBSD-10? > > Thanks! > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.21 (FreeBSD) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBAgAGBQJSNxItAAoJEGKyFhaKt9g3utAP/34rlyrLGntXCIDa9LHv3Qly > nmRRcIWgkT//MEDFG2OZMdWo+50DQ12k9L0qAAoUkezhDqfZXTo+U5DOn2mr0MEf > 2KOXT5yMkqNBtab54a/nCDxp0bCAiaMSJjsKqXjF6mq6fqoj6aVEFJY6rgzG+Qb1 > cAjHlBfbOBcOFtWd4xt0+w1m5VodnJ8dsd5CTVfkazTRRfk32qlLMraRUmQT1x+C > STi2Dt4xDJzbx6MThDcwjOfudPQeQiQ1SnFn65aNRCxSj//pNcZW0DeU3efKq730 > 1RA2yPjpoqzrPklkkW4wF0Kv/50rGGytS1WYcA01uwBq8noBdVmW9J7GfeqmVuF8 > vATRX8eDYNVtkJLZmBqgUgXPT0BocHpoW7qPpTmRHG2OJ8TQTIytGT+nx08rG/T3 > EEWssgY/kOKDfYgB9DYcgLyGIPcLt0JuwCWL/sm5wzX1bogNyVhrn5hmJTTiFAng > O4cbyXDPaEHdZhQ9SibqiJ2H1FfUa4keD0d2JW2ZhR5cSFD3oW1s8WprNf/ujBWn > Bc7Z78qy4z0feqrYUabFKMxhmJJtwVfW7Y7Kmuzuvk08CHYjsAikQjumkKNm4Onz > iYFFDfYXbEF73KJslr7tY+kWIY1iRuFc4xnjjaucEIbG/Bp7SvgMhTsNgQ7d//z5 > ZVwvJTV0HsyqF+VPz1Ei > =kQa4 > -END PGP SIGNATURE- > ___ > 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" > ___ 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: ipv6_activate_all_interfaces doesn't work on wireless interface.
OK, I will try add accept_rtadv to ifconfig_wlan0_ipv6. Thanks, Eric On Fri, Aug 16, 2013 at 6:19 AM, Kimmo Paasiala wrote: > On Fri, Aug 16, 2013 at 8:47 AM, Eric L Camachat > wrote: > > Here is my /etc/rc.conf > > ipv6_enable="YES" > > #ip6addrctl_enable="YES" > > #ip6addrctl_policy="ipv6_prefer" > > #ipv6_activate_all_interfaces="YES" > > wlans_iwn0="wlan0" > > ifconfig_wlan0="WPA DHCP" > > > > rc.d system said ipv6_enable is obsoleted by > > ipv6_activate_all_interfaces. > > So, I tried to replaced ipv6_enable with ipv6_activate_all_interfaces > > and ip6addrctl_*, interface wlan0 will not get ipv6 address from router. > > > > After investigated, that's because of wlan0 didn't add 'accept_rtadv' > > ipv6 option. > > > > -- > > Eric > > > > As far as I know, not enabling accept_rtadv is a reasonable default > and it has been like that always. Just like DHCP is not a default > configuration method for IPv4 addresses. > > -Kimmo > ___ 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: Kernel crash during heavy disk access
On Mon, 2013-07-08 at 23:05 -0700, Adrian Chadd wrote: > Hi, > > Try doing a full, non-journal fsck. > > -adrian Thank you, it fixed the problem! Does it mean journal didn't work? -- Eric Camachat signature.asc Description: This is a digitally signed message part
Kernel crash during heavy disk access
I experienced kernel crashes while make world or ports. For example: # cd /usr/port/lang/mono # make Will cause the crash, from /var/crash/core.txt: eb8460p dumped core - see /var/crash/vmcore.5 Mon Jul 8 21:22:58 PDT 2013 FreeBSD eb8460p 10.0-CURRENT FreeBSD 10.0-CURRENT #5 r253048: Mon Jul 8 19:07:18 PDT 2013 root@eb8460p:/u sr/obj/usr/src/sys/EB8460p amd64 panic: ffs_valloc: dup alloc GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: mode = 0100600, inum = 52969060, fs = / panic: ffs_valloc: dup alloc cpuid = 0 KDB: stack backtrace: #0 0x805fd6d0 at kdb_backtrace+0x60 #1 0x805c5b65 at panic+0x155 #2 0x807dda6a at ffs_valloc+0x88a #3 0x8081a34c at ufs_makeinode+0x7c #4 0x808d2872 at VOP_CREATE_APV+0x92 #5 0x80670c49 at vn_open_cred+0x2c9 #6 0x8066a22f at kern_openat+0x1ef #7 0x8085db47 at amd64_syscall+0x357 #8 0x808475db at Xfast_syscall+0xfb Uptime: 6m57s Dumping 599 out of 3972 MB:..3%..11%..22%..33%..41%..51%..62%..73%..81%..91% Reading symbols from /boot/modules/cuse4bsd.ko...done. Loaded symbols for /boot/modules/cuse4bsd.ko Reading symbols from /boot/kernel/fdescfs.ko.symbols...done. Loaded symbols for /boot/kernel/fdescfs.ko.symbols Reading symbols from /boot/kernel/ng_ubt.ko.symbols...done. Loaded symbols for /boot/kernel/ng_ubt.ko.symbols Reading symbols from /boot/kernel/netgraph.ko.symbols...done. Loaded symbols for /boot/kernel/netgraph.ko.symbols Reading symbols from /boot/kernel/ng_hci.ko.symbols...done. Loaded symbols for /boot/kernel/ng_hci.ko.symbols Reading symbols from /boot/kernel/ng_bluetooth.ko.symbols...done. Loaded symbols for /boot/kernel/ng_bluetooth.ko.symbols Reading symbols from /boot/kernel/ums.ko.symbols...done. Loaded symbols for /boot/kernel/ums.ko.symbols Reading symbols from /boot/kernel/ng_l2cap.ko.symbols...done. Loaded symbols for /boot/kernel/ng_l2cap.ko.symbols Reading symbols from /boot/kernel/ng_btsocket.ko.symbols...done. Loaded symbols for /boot/kernel/ng_btsocket.ko.symbols Reading symbols from /boot/kernel/ng_socket.ko.symbols...done. Loaded symbols for /boot/kernel/ng_socket.ko.symbols #0 doadump (textdump=) at pcpu.h:236 236 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:236 #1 0x805c57e0 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:447 #2 0x805c5ba4 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:754 #3 0x807dda6a in ffs_valloc (pvp=, mode=, cred=, vpp=) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1022 #4 0x8081a34c in ufs_makeinode (mode=, dvp=0xfe011bf44ce8, vpp=0xff811ba058d8, cnp=0xff811ba05900) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2620 #5 0x808d2872 in VOP_CREATE_APV (vop=, a=) at vnode_if.c:265 #6 0x80670c49 in vn_open_cred (ndp=0xff811ba05880, flagp=0xff811ba0595c, cmode=420, vn_open_flags=, cred=0xfe0011fcee00, fp=0xfe00110925a0) at vnode_if.h:109 #7 0x8066a22f in kern_openat (td=0xfe011960f920, fd=, path=0x801dbd580 , pathseg=UIO_USERSPACE, flags=1538, mode=) at /usr/src/sys/kern/vfs_syscalls.c:1093 #8 0x8085db47 in amd64_syscall (td=0xfe011960f920, traced=0) at subr_syscall.c:134 #9 0x808475db in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:391 #10 0x0008013a5f2a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal (kgdb) -- Eric Camachat signature.asc Description: This is a digitally signed message part
