C
> #define BCOM_DEVICEID_BCM5751 0x1677
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
On Dec 24, 2007, at 8:19 AM, Kostik Belousov wrote:
Mark, could you, please, retest the patch below in your setup ?
I want to put a change or some edition of it into the 7.0 release, and
we need to move fast to do this.
It's building now. The testing will run overnight.
Your pat
0:04.62
[softdepflush]
Building a new kernel with KTR and FULL_PREEMPTION now.
--
mark
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Wed, Dec 26, 2007 at 06:15:16PM +0100, Henrik Gulbrandsen wrote:
> Fixing and merging are good, but it seems to me (as an occasional patch
> contributor without commit privileges) that the bottleneck for USB is
> still in the handling of incoming patches [...] if a one-line fix
> such as that in
On Wed, Dec 26, 2007 at 12:43:06PM -0800, Richard Neese wrote:
> Point and Fax I have emaile Sobomax about fixing and updating the asterisk
> ports. and have sent patches but never got a reply in 9 months.
For situations like this you need to email [EMAIL PROTECTED] We already have
defined para
On Sun, Dec 30, 2007 at 01:01:19AM +0100, Alexander Leidinger wrote:
> Quoting Mark Linimon <[EMAIL PROTECTED]> (from Wed, 26 Dec 2007
> 12:04:15 -0600):
>
> > - The creation of a weekly posting "bugs the bugmeister team thinks are
> > ready for commit".
I've just posted a message with that title to sparc64@ with crosspost
to [EMAIL PROTECTED] If you're interested in deciding on where we're going with
sparc64, I invite you to join that thread. (Please don't reply to
this message; 2 lists is probably one too many).
mcl
___
On Tue, Jan 15, 2008 at 09:51:13PM +0200, George Kontostanos wrote:
> So may I guess that we have a release ?
This question happens every time we get near a release.
There will be a release when, and only when, a signed email is sent from
the Release Engineering team to the various mailing lists.
On Thu, Jan 17, 2008 at 01:59:01PM -0800, Josef Grosch wrote:
> I have a mirror at work (Juniper Networks) and we have had all the
> bits since Tuesday.
You can't have; the final sparc64-6 packages were just finished
yesterday, at the last second.
mcl
_
On Fri, Jan 18, 2008 at 03:51:43PM -0500, Ken Smith wrote:
> Due to resource limitations (both human and computer) there won't
> be an ia64 6.3-RELEASE but there will be an ia64 7.0-RELEASE.
Unless something changes rapidly, ia64-7 will not have any packages
shipped with it: the last I tried, it w
e
that faults in gcc with this turned on. You can try adding
vm.pmap.pg_ps_enabled="0"
to /boot/loader.conf, rebooting and see if that fixes the problem. If so,
you might provide the list with your hardware configuration.
For reference:
http://thread.gmane.org/gmane.os.freebs
disk corruption can cause this.
If you can complete a buildworld, a fresh buildworld and installworld with
make delete-old might solve your compilation problems.If qt depends on
the gcc in ports, you may have to rebuild that one as well afterwards.
--
Mark Atkinson
atkin...@yahoo.com
channel simple_log {
> file "/var/log/named/named.log" versions 5 size 20m;
> severity warning;
> print-time yes;
> print-category yes;
> print-severity yes;
>};
>...
>
>
> -
On Sun, Mar 22, 2009 at 09:18:03AM +1100, Aristedes Maniatis wrote:
> Is there any way to automatically create such a page from the bug
> tracker?
Not that fills in the dates, no. We are working on a prototype to
track particular PRs.
mcl
___
freebsd
http://www.mail-archive.com/freebsd-questi...@freebsd.org/msg197899.html
Other than that, I'd suggest checking the disk(s) with smartmontools to
try to rule out hardware problems.
regards
Mark
___
freebsd-stable@freebsd.org mailing
** Error code 1Stop in /usr/src.*** Error
code 1Stop in /usr/src.*** Error code 1Stop in /usr/src.Any ideas on how to
resolve this?Thank you,Mark--***
* Mark Skurzynski * Lomag Internet Services,
LLC m...@lomag.net * http://www.lomag.net E
rror code 1Stop in /usr/src.*** Error
code 1Stop in /usr/src.*** Error code 1Stop in /usr/src.Any ideas on how to
resolve this?Thank you,Mark--***
* Mark Skurzynski * Lomag Internet Services,
LLC m...@lomag.net * http://www.lomag.net Edison
We have a Dell R710 with its first ethernet port connected to a Dell
5524 ethernet switch. Just installed 7.2-RELEASE on it and get no
connectivity over the ethernet. tcpdump shows no frames at all.
Installing your patches eliminated the PHY write timeout errors, but
still have no connectivity.
___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
"#!" is used to define the interpretor when the
d like it better if the four discs would spin up simultaneously.
Thus my question: "Is it possible to \"group\" discs to be spun up
together, or to issue a custom command upon upspinning of a disc such as
to spin up other disks?"
Thanks!
Greetz,
Mark
signature.asc
Description: OpenPGP digital signature
Ivan Voras wrote:
> 2009/7/21 Mark Stapper :
>
>> Ivan Voras wrote:
>>
>>> Mark Stapper wrote:
>>>
>>>> Good day,
>>>>
>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other
>>>
Arnaud Houdelette wrote:
> Mark Stapper a écrit :
>> Ivan Voras wrote:
>>
>>> 2009/7/21 Mark Stapper :
>>>
>>>> Ivan Voras wrote:
>>>>
>>>>> Mark Stapper wrote:
>>>>>
&
Arnaud Houdelette wrote:
> Mark Stapper wrote:
>> Arnaud Houdelette wrote:
>>
>>> Mark Stapper a écrit :
>>>
>>>> Ivan Voras wrote:
>>>>
>>>>
>>>>> 2009/7/21 Mark Stapper :
>>>
planation and probably not entirely correct, but I hope it suffices.
> Only hope: Make sure that not all disk space is used.
>
> Christian
>
Indeed, if by some coincident (like a growing logfile) every single byte
is used, even the copy action might fail...
To prevent this you coul
Arnaud Houdelette wrote:
> Mark Stapper wrote:
>> Arnaud Houdelette wrote:
>>
>>> Mark Stapper a écrit :
>>>
>>>> Ivan Voras wrote:
>>>>
>>>>
>>>>> 2009/7/21 Mark Stapper :
>>>
rom. Takes a little more efford, but
is more uniform.
Updating zfs will be a pain though. You would have to boot from another
filesystem to be able to update your root filesystem.
If you'll be reinstalling your system, you might want to check out
FreeBSD 8 because zfs boot support is better.
Hope it helps.
Greetz,
Mark
signature.asc
Description: OpenPGP digital signature
Emil Mikulic wrote:
> On Wed, Sep 02, 2009 at 09:20:21AM +0200, Mark Stapper wrote:
>
>> updating a zfs filesystem which you are running from is next to
>> impossible.
>>
>
> [citation needed] :)
>
Well, to update your zfs filesystem version, the fi
Thomas Backman wrote:
> On Sep 2, 2009, at 10:27 AM, Mark Stapper wrote:
>
>>
> Nothing a LiveCD or something to that regard can't handle. Obviously
> this doesn't work for everyone, but it should for many.
Actually it won't because updating zfs comes with updati
t; address instead of the old fe80 as suggested.
>
> BIND's now happily running in its jail and responding to public
> queries.
>
>
> Perhaps a small addition to the jails entry in the Handbook to
> advise people about the use of IP6 addresses on loopback interfaces
&g
> Considering your name, I understand why you need the accent marks.
>
> Have you looked at the instructions in chapter 23 of the handbook?
>
> http://www.freebsd.org/doc/hu/books/handbook/l10n.html
>
> Minden jót kivánok
>
> -jeff
>
Just off topic.. but.. Magyar?
Egészségedre!
Mark
signature.asc
Description: OpenPGP digital signature
1 and libc++" list in that last paragraph
given the "upgrade easily" context intended.
(If there is an easy powerpc64 upgrade then I'd like to see notes about it:
Other contexts might be able to use similar techniques. I started my
explorations with 10.)
===
Mark Millard
m
tation fault.
I'm still not sure that the stable/9 to stable/10 update would be reliably
clean for powerpc64, despite -mlongcall not being used at that stage.
===
Mark Millard
markmi at dsl-only.net
On 2015-Oct-11, at 8:05 PM, Mark Millard wrote:
> On 2014-Oct-11 Dimitry Andric wrote:
fine there!
I haven't tried yet to build it with debugging, or capture
a core dump.
Puzzling...
Mark
2015-10-30 12:34, je David Wolfskill napisal
On Fri, Oct 30, 2015 at 09:42:07AM +0100, Dag-Erling Smørgrav wrote:
David Wolfskill writes:
> ...
> bound to 172.17.1.245 --
Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd crashes
(apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm).
Thanks!!!
Mark
On 2015-11-01 10:31, Andre Albsmeier wrote:
On Fri, 30-Oct-2015 at 19:47:59 +0100, Mark Martinec wrote:
Not sure if it's the same
Please submit this via bugzilla so that it will not get lost in all
the mailing list traffic. Thank you.
mcl
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-
, a simple
workaround is to run shell from a command line instead of as a
shebang, i.e.:
# /bin/sh /usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr
instead of:
# /usr/src/contrib/netbsd-tests/lib/libc/net/gen_ether_subr
Mark
___
f
So, is this a new state of affairs that /usr/src file system
needs to be mounted exec in order for buildworld to succeed,
or is this an unintended change and I should file a bug report?
Mark
On 2015-11-26 19:44, Miroslav Lachman wrote:
Mark Martinec wrote on 11/26/2015 19:31:
Up to about a
://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2871
I checked in svn and there are no recent changes to sys/dev/random .
Does anyone have any insight into this ?
--
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mail
On Tue, Jan 5, 2016 at 8:45 AM, Adam Vande More
wrote:
> On Mon, Jan 4, 2016 at 3:44 PM, Mark Saad wrote:
>
>> All
>> At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
>> starting at or about r292122 and still up till r292855.
>>
>&
On Tue, Jan 5, 2016 at 2:00 PM, Peter Jeremy wrote:
> On 2016-Jan-04 16:44:49 -0500, Mark Saad wrote:
> >On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
> >
> >random device not loaded; using insecure entropy
>
> When I first noticed this, I
n 10.3 - or at least it should be clearly documented in release notes.
Mark
On 2015-12-07 16:35, Mark Martinec wrote:
So, is this a new state of affairs that /usr/src file system
needs to be mounted exec in order for buildworld to succeed,
or is this an unintended change and I should file a bu
out the WITH_TESTS="yes" from
/etc/make.conf avoids the problem - although this was not necessary
in 10.2-RELEASE, as far as I can tell.
Mark
On 1/14/2016 7:42 AM, Mark Martinec wrote:
Prompted by recent security advisories I did a 'make buildworld'
on a fresh svn checko
an instant.
Several others have the same problem. See here on the freebsd forums:
http://tinyurl.com/z9oldkc
(URL shortened cos I'm only allowed 80chars per line)
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/ma
Kurt Jaeger opsec.eu> writes:
>
> Hi!
>
> > I have a new Asus H170-Plus-D3 motherboard that will be used for a DOM0 Xen
> > Server. It uses an Intel i5-6300 processor and a Samsung 840 EVO SSD. I
> > would like to use ZFS on this new installation. The Xen Kernel does not
have
> > UEFI sup
Konstantin Belousov gmail.com> writes:
>
> On Fri, Feb 12, 2016 at 09:15:49PM +0000, Mark Dixon wrote:
> > > Can you put a dmesg.boot from the server ? An pciconf -lvb ?
> > >
> >
> > I have the exact same issue on the forum, so I can:
> As a blind s
Konstantin Belousov gmail.com> writes:
> On Sat, Feb 13, 2016 at 03:46:16PM +, Mark Dixon wrote:
> Might be, try the following (mostly debugging) change.
>
Tried it, the only thing I saw different is after the menu I got:
rd eef611d6
Hope that
5cNGG+SxupZajtIuaCBTeUv0QwjnDH5
> Pnu44Xe4MCvpDSt9odICdzytxO6yzwL7mLj70o2SsPs2ijN1w/fOlNqS46bekmJ/
> MtvVwObCRnoDg3aMRUL0
> =In6V
> -END PGP SIGNATURE-
> ___
> freebsd...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail
x27;m remembering correctly, a volume with more than 2 drives creates a
> passN device for all but one of the drives.
>
>Terry Kennedy http://www.glaver.org New York, NY USA
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
---
Mark Saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
or messages from
> the probes.
>
> Let me know if you need any additional info.
>
> Terry Kennedy http://www.glaver.org New York, NY USA
>
Can you build 10-STABLE and merge back the mpt driver prior to r285840 . It
looks like a change was merged in about 7
Pavel Timofeev gmail.com> writes:
>
> Hi!
> Has anybody tried net-im/skype4 under FreeBSD 10.3(-BETA[0-9])??
> Seems like net-im/skype4 missing some dependencies and if it's
> satisfied net-im/skype4 hangs after start.
> linprocfs mounting doesn't help.
> I installed them all from the ports tree
Will Green sundivenetworks.com> writes:
>
> I am happy to test patches and/or current on this server if that helps. If
you want more details on the
> motherboard/system I have started a post on it at
http://buildwithbsd.org/hw/skylake_xeon_server.html
>
I've made the UEFI switch which worked f
On Thu, Mar 31, 2016 at 10:32:45AM +1100, Jason Tubnor wrote:
> 10.3-RELEASE has been available for a few days now
No, it hasn't.
The bits for what _may be_ 10.3-RELEASE, barring the finding of any
last-minute problems, are what is there.
In at least one previous release cycle, last-minute probl
On Wed, Mar 30, 2016 at 11:04:30PM -0700, Ronald F. Guilmette wrote:
> I would however like to ask if there is an ETA for 10.3-RELEASE
> actually being official and final.
>From the front page of www.freebsd.org, click on the link
"Upcoming: 10.3" which will take you to
https://www.freebsd.org/rel
gt; and proceeded usual rebuilding procedure.
>
> Fortunately, there was only 3 commits between r298836 and r298920,
> and I got right one in first attempt.
>
> But unfortunately, fixing portupgrade[-devel] or file/libmagic beyonds
> my hand. :-<
I have taken Tomoaki'
On Fri, May 13, 2016 at 04:14:34PM -0400, Kurt Lidl wrote:
> I updated one of my sparc64 machines (a V240, dual processor, 8GB
> of memory) and now it panics.
>
> Before (working without issue):
> FreeBSD spork.pix.net 10.3-STABLE FreeBSD 10.3-STABLE #18 r299561: Thu
> May 12 16:28:16 EDT 2016
>
On Wed, Jun 08, 2016 at 05:02:09PM -0400, Mikhail T. wrote:
> In my absence my desktop managed to run out of memory and had to kill a
> number of processes:
>
> pid 47493 (firefox), uid 105, was killed: out of swap space
> pid 1665 (thunderbird), uid 105, was killed: out of swap space
>
e
> performance of LSI MegaRAID 9260-8i and had the following bad result:
>
> 1. Test environment:
>(1) OS: FreeBSD 10.0 release
10.0-RELEASE is no longer supported. Can you reproduce this on
10.3-RELEASE?
--
Mark Felder
f...@feld.me
the write penalty on
each read access.
We need more data :-)
--
Mark Felder
ports-secteam member
f...@freebsd.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
e device, and bsnmp went back to normal.
"Interesting". So far I didn't notice memory issues.
Mark
--
Nice testing in little China...
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
On Tue, Jul 05, 2016 at 10:38:23AM +0200, Mark Huizer wrote:
> On Mon, May 02, 2016 at 12:01:07AM +0200, Wolfgang Zenker wrote:
> > Hi,
> >
> > after updating some 10-STABLE systems a few days ago, I noticed that on
> > two of those systems bsnmpd started to use up
; WITH_CLANG_FULL=
> WITH_CLANG_EXTRAS=
> WITH_LLDB=
> #
> WITH_BOOT=
> WITHOUT_LIB32=
> WITHOUT_LIBSOFT=
> #
> WITHOUT_ELFTOOLCHAIN_BOOTSTRAP=
> WITHOUT_GCC_BOOTSTRAP=
> WITHOUT_GCC=
> WITHOUT_GCC_IS_CC=
> WITHOUT_GNUCXX=
> #
> NO_WERROR=
> #WERROR=
> MALLOC_PRODUCTION=
> #
> WITH_DEBUG_FILES=
> #
> XCFLAGS+= -march=armv7-a -mcpu=cortex-a7
> XCXXFLAGS+= -march=armv7-a -mcpu=cortex-a7
make.conf was empty.
The earlier -r302331 cross build had WITH_LIBSOFT= in use. -r302412 is my first
testing of WITHOUT_LIBSOFT= after rebuilding all ports to avoid libsoft.
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
of a different issue when
WITH_META_MODE was attempted.
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
= "arm" does not appear to achieve the original test's intent
and will mishandle things list armv6 as far as I can tell. (It certainly does
avoid the malformed conditional problem that stops the build.)
===
Mark Millard
markmi at dsl-only.net
___
27;:
> /usr/src/sys/modules/ahci/../../dev/ahci/ahci.c:288:22: error: unknown
> conversion type character 'b' in format [-Werror=format=]
>device_printf(dev, "quirks=0x%b\n", ctlr->quirks,
> ^
> /usr/src/sys/modules/ahci/../../dev/ahci/ahci.
[Top post of probable "already fixed" status.]
It looks like -r320441 on stable/11 reverted a kern.mk change controlling what
formats are (un)available for some compilers.
I'm rebuilding things based on -r302457 instead of -r302412 and will close the
defect if things work.
=
On 2016-Jul-9, at 8:53 PM, Ngie Cooper wrote:
>> On Jul 9, 2016, at 18:52, bugzilla-nore...@freebsd.org wrote:
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210953
>>
>> Mark Millard changed:
>
> I accidentally committed this regression to ker
On 2016-Jul-8, at 12:23 AM, Mark Millard wrote --but with
a few []'d notes added:
> [Before the below cross build/update attempt I updated my amd64 from -r302331
> -> -r302412.]
>
> Summary: It appears that WITHOUT_META_MODE= still needs to be forced for
> cross comp
ile SRCS
being ppc64_elf_freebsd.c).
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
est
> build with the -CFLAGS+= -Wa,-mppc64bridge line removed?
> -Nathan
>
> On 07/11/16 03:55, Mark Millard wrote:
>> Is the following something that should be updated something like is
>> indicated below for 11.0-BETA1? Is kboot powerpc64 specific?
>>
>> #
On 2016-Jul-11, at 11:04 AM, Mark Millard wrote:
> On 2016-Jul-11, at 6:49 AM, Nathan Whitehorn wrote:
>>
>> It is not 64-bit only; like the normal loader, it can load both 32-bit and
>> 64-bit kernels. Those two flags are probably obsolete at this point and were
>
On 2016-Jul-11, at 11:30 AM, Mark Millard wrote:
> On 2016-Jul-11, at 11:04 AM, Mark Millard wrote:
>
>> On 2016-Jul-11, at 6:49 AM, Nathan Whitehorn wrote:
>>>
>>> It is not 64-bit only; like the normal loader, it can load both 32-bit and
>>> 64-bi
kboot in.
I'll enter a report showing the sys/boot/powerpc/kboot/Makefile change that I
tried.
===
Mark Millard
markmi at dsl-only.net
On 2016-Jul-11, at 11:43 AM, Mark Millard wrote:
> On 2016-Jul-11, at 11:30 AM, Mark Millard wrote:
>
>> On 2016-Jul-11, at 11:04 AM, Ma
On 2016-Jul-11, at 1:51 PM, Mark Millard wrote:
> Quick top-post just to indicate that I just did gcc 4.2.1 based cross-builds
> for TARGET_ARCH=powerpc and TARGET_ARCH=powerpc64 and they completed. They
> had analogous warnings to what clang (powerpc) and powerpc64-gcc (powerpc64)
&
ck with Bruce Evans. He has good coverage of the various
standards to be covered (that may not all agree and how/what FreeBSD then
picks).
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[The below does note that TARGET=powerpc has a mix of signed wchar_t and
unsigned char types and most architectures have both being signed types.]
On 2016-Jul-11, at 8:57 PM, Andrey Chernov wrote:
> On 12.07.2016 5:44, Mark Millard wrote:
>> My understanding of the criteria for __WCHA
On 2016-Jul-13, at 6:00 PM, Andrey Chernov wrote:
> On 13.07.2016 11:53, Mark Millard wrote:
>> [The below does note that TARGET=powerpc has a mix of signed wchar_t and
>> unsigned char types and most architectures have both being signed types.]
>
> POSIX says nothing a
ariants (32-bit vs. 64-bit), causing
lots of false-positive compiler notices. gcc had followed the ABI involved
(long int) until the correction.
===
Mark Millard
markmi at dsl-only.net
On 2016-Jul-13, at 11:46 PM, Mark Millard wrote:
> On 2016-Jul-13, at 6:00 PM, Andrey Chernov wrote:
>
&
ebus.c
> >head/sys/dev/gpio/ofw_gpiobus.c
> >head/sys/dev/iicbus/ofw_iicbus.c
> >head/sys/dev/ofw/ofw_bus_subr.c
> >head/sys/dev/ofw/ofw_bus_subr.h
> >head/sys/dev/ofw/ofwbus.c
> >head/sys/dev/pci/pci_host_generic.c
> > head/sys/dev/vn
dling. There are
other problems as well, such as exception handling. To actually use the
buildworld result I'd use a kernel modified to have a so-called "red-zone" for
signal delivery. clang can not yet build the kernel so that part would be gcc
4.2.1 based. This does not deal wit
(autoselect)
> status: no carrier
> nd6 options=29
> add host 127.0.0.1: gateway lo0 fib 0: route already in table
> add host ::1: gateway lo0 fib 0: route already in table
> add net fe80::: gateway ::1
> add net ff02::: gateway ::1
> add net :::0.0.0.0:
WWW: http://wiki.qemu.org/Main_Page
> Comment: QEMU CPU Emulator - development version
> Options:
> CDROM_DMA : on
> CURL : on
> DOCS : on
> GNS3 : on
> GNUTLS : on
> GTK2 : on
> JPEG : on
> OPENGL : on
> PCAP : on
> PNG: on
> SAMBA : off
> SASL : on
> STATIC_LINK: off
> USBREDIR : off
> X11: on
> X86_TARGETS: off
. . .
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Mon, Aug 08, 2016 at 10:02:00AM +0200, Harry Schmalzbauer wrote:
> Bezüglich Rick Macklem's Nachricht vom 07.08.2016 23:34 (localtime):
> > Harry Schmalzbauer wrote:
> >> Hello,
> >>
> >> I had another crash which I'm quite sure was triggered by mount_unionfs:
> > Just in case you are not alread
TRINGS
.endif
#
#
# From based on clang (via system). . .
#
.if ${.MAKE.LEVEL} == 0
CC=/usr/bin/clang
CXX=/usr/bin/clang++
CPP=/usr/bin/clang-cpp
.export CC
.export CXX
.export CPP
.endif
# more ~/src.configs/make.conf
CFLAGS.gcc+= -v
===
Mark Millard
markmi at dsl-only.net
___
[i:]"
Revision: 304029
Last Changed Rev: 304029
# uname -apKU
FreeBSD rpi2 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #4 r304029M: Sat Aug 13
01:10:34 PDT 2016
markmi@FreeBSDx64:/usr/obj/clang/arm.armv6/usr/src/sys/RPI2-NODBG arm armv6
1100500 1100500
# svnlite info /usr/ports | grep &
On Mon, Aug 15, 2016, at 05:27, Bob Bishop wrote:
>
> Why is this hiding out on questions@ ?
>
I wanted to reach a broader audience.
--
Mark Felder
ports-secteam member
f...@freebsd.org
___
freebsd-stable@freebsd.org mailing l
-PRERELEASE #4 r304029M: Sat Aug 13
> 01:10:34 PDT 2016
> markmi@FreeBSDx64:/usr/obj/clang/arm.armv6/usr/src/sys/RPI2-N
> ODBG arm armv6 1100500 1100500
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Mon, Aug 22, 2016 at 09:57:24AM +1000, Dewayne Geraghty wrote:
> unless knowledgable people respond publicly and/or in the phoronix
> forums [...] this interpretation of reality will be fixed in decision-
> makers' minds and consequently the uptake (and support) of FreeBSD.
IIRC this has been d
make.conf
> WANT_QT_VERBOSE_CONFIGURE=1
> #
> DEFAULT_VERSIONS+=perl5=5.22
> WRKDIRPREFIX=/usr/obj/portswork
> WITH_DEBUG=
> WITH_DEBUG_FILES=
> MALLOC_PRODUCTION=
If I remember right the above are accurate for the rpi2 as well.
I'll note that arm-none-eabi-binutils
Quick top post: retrying "portmaster -DKa" after rebooting did not repeat the
panic.
OPTIONS_FILE_SET+=RELRO likely has nothing to do with the unusual panic.
===
Mark Millard
markmi at dsl-only.net
On 2016-Aug-27, at 3:35 AM, Mark Millard wrote:
[I've no solid evidence of wh
I'll demur just a bit on your points.
On Mon, Aug 29, 2016 at 08:51:02PM -0700, K. Macy wrote:
> "we need a compiler to build the system" (a prebuilt package does that
> just fine),
Well, yes, for a tier-1 machine; and one that is connected to the network.
> I can't speak for the whole universe
in
expecting that /var/run may be ephemeral and is such a setup
(as is common in Linux) unsupported?
Mark
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "fr
uilding
> on one system and installing on another will fail due
> to not finding cc in the OBJDIR.
>
> An actual fix will be made on head separately.
>
> PR: 212877
> Relnotes: yes
> Sponsored by: Dell EMC
note that, while there are no official builds for the Pine64 family
(A64 based) that are under the Allwinner arm activity, the SOC's involved are
Cortex-A53 64-bit arm based. They likely do not fit in the "standard
conventions" or arm64/aarch64 would be where they would hav
andard
conventions" or arm64/aarch64 would be where they would have been supported.
Some rewording might be appropriate for the above quote as well.]
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebs
e SOC's involved are
Cortex-A53 64-bit arm based. They likely do not fit in the "standard
conventions" or arm64/aarch64 would be where they would have been supported.
Some rewording might be appropriate for the above quote as well.]
===
Mark Millard
markmi at dsl-only.net
On 2016-Sep-24, at 2:11 PM, Warner Losh wrote:
> On Fri, Sep 23, 2016 at 8:29 PM, Mark Millard wrote:
>> [A resend since I forget to list free-arm in the To: the first time.]
>>
>> From https://www.freebsd.org/platforms/arm.html :
>>
>>> 32-bit ARM is offi
64. I've not put much effort into figuring such out given
the more basic problems above. (The environment the attempt was done from is
dhcp based.)
===
Mark Millard
markmi at dsl-only.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
more /etc/make.conf
> WANT_QT_VERBOSE_CONFIGURE=1
> #
> DEFAULT_VERSIONS+=perl5=5.22
> WRKDIRPREFIX=/usr/obj/portswork
> WITH_DEBUG=
> WITH_DEBUG_FILES=
> MALLOC_PRODUCTION=
> # svnlite status /usr/src
> M /usr/src/contrib/llvm/lib/CodeGen/SelectionDAG/Selection
Quick top post on avoiding the problem:
Reverting devel/powerpc64-gcc from -r421598 to -r413189 appears to have avoided
this problem.
While buildworld is still building: the build is well past the failure point
reported below.
===
Mark Millard
markmi at dsl-only.net
On 2016-Sep-26, at 4:48
Hi Andriy,
I tried your patch on an Asus Z170-Deluxe on 11-RELEASEt and aibs did
not seem to pick up anything before or after. Not 100% what sensors
this board has.
Regards,
Mark
signature.asc
Description: This is a digitally signed message part
501 - 600 of 1357 matches
Mail list logo
