okay because
we properly set memory attribute. It's a long standing bug and there's
PR254381.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254381
Jung-uk Kim
LENOVO_L5INTEL_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x380f) ?
I guess. :-)
JK
Jung-uk Kim mailto:j...@freebsd.org>> escreveu no dia
quinta, 25/08/2022 à(s) 20:15:
On
On 22. 6. 13., Jung-uk Kim wrote:
On 22. 6. 13., Jung-uk Kim wrote:
On 22. 6. 13., Jung-uk Kim wrote:
On 22. 6. 13., Masachika ISHIZUKA wrote:
What do you think opening a review about this fix/tweak to stop this
spamming that blinds dmesg?
I'm running CURRENT 8d95f500521 and I'm
On 22. 6. 13., Jung-uk Kim wrote:
On 22. 6. 13., Jung-uk Kim wrote:
On 22. 6. 13., Masachika ISHIZUKA wrote:
What do you think opening a review about this fix/tweak to stop this
spamming that blinds dmesg?
I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg
warnings:
On 22. 6. 13., Jung-uk Kim wrote:
On 22. 6. 13., Masachika ISHIZUKA wrote:
What do you think opening a review about this fix/tweak to stop this
spamming that blinds dmesg?
I'm running CURRENT 8d95f500521 and I'm receiving loads of dmesg
warnings:
---
ACPI Warning: Firmware issue:
https://acpica.org
This message was added by this commit:
https://github.com/acpica/acpica/commit/2a0d1d475e7ea1c815bee1e0692d81db9a7c909c
You can file your complaints here if it is really bothering you.
https://github.com/acpica/acpica/issues
Jung-uk Kim
ommit.
https://cgit.freebsd.org/src/commit/?id=428a32edba4c3bf3cfc0e4cf240c1b29397ecdbb
Jung-uk Kim
164..096a84721670, I
> note a couple of promising-looking candidates:
>
> share/mk/bsd.opts.mk| 1 +
> share/mk/src.opts.mk| 1 -
>
> Reviewing the commit log for share/mk/bsd.opts.mk, I see that the most
> recent entry is:
>
> | co
etooth-related kernel modules as both
> systems are rack-mounted servers with no bluetooth hardware in them to my
> knowledge.
>
> I've looked in /usr/src/UPDATING for any recent note related to this but
> can't find anything. My last update (ci
Could someone point me to snapshot of 13-CURRENT
> that'd include the commit I need?
http://docs.freebsd.org/cgi/mid.cgi?20191121172230.GA28849
Jung-uk Kim
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
mod for "AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx" (aka.
Vega 8).
Jung-uk Kim
> On 10/10/19, Thomas Laus wrote:
>> On 2019-10-10 12:21, Mateusz Guzik wrote:
>>> Try this:
>>>
>>> http://dpaste.com/0P2MXF6
>>>
>>> if it s
Level Stripe State Cache Name
mfid0 ( 36T) RAID-6 64K OPTIMAL Disabled
FYI, it's been working fine for 7 years.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
you want it to use LLVM_DEFAULT at your own risk.
> MESA_LLVM_VER=${LLVM_DEFAULT}
> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239682#c0>
> DEFAULT_VERSIONS+=llvm=90
I believe r351055 was the culprit.
https://svnweb.freebsd.org/changeset/base/351055
Note r351067 reverted it.
https://svnweb.freebsd.org/changeset/base/351067
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
> What happened here? Does anyone do have a hint or might know the cause?
I had the same problem and reverting r349154 fixed the problem for me.
https://svnweb.freebsd.org/changeset/base/349154
FYI...
Jung-uk Kim
___
freebsd-current@freebsd.org mai
>> freebeast(13.0-C)[3] ssh albert hostname
>> Could not open /dev/crypto: No such file or directory
>> albert.catwhisker.org
>> freebeast(13.0-C)[4] echo $?
>> 0
>> freebeast(13.0-C)[5]
>
> It's r342009, and I followed up on that
On 18. 12. 11., Alexandre C. Guimarães wrote:
> Hi.
>
> This is just informative.
>
> Apparently Linux is considering deprecate x32 support:
>
> https://lkml.org/lkml/2018/12/10/1151
x32 != i386
https://en.wikipedia.org/wiki/X32_ABI
FYI, FreeBSD never supported
AE_NOT_EXIST (20181031/psparse-677)
>
> As a result, I am now unable to query battery information at the very
> least. r340490 is my last built revision with this working.
I am pretty sure r340644 caused the regression.
https://svnweb.freebsd
0 74 00 61 00 54 00
>> 00c0: 72 00 61 00 76 00 65 00 6c 00 65 00 72 00 20 00
>> 00d0: 32 00 2e 00 30 00 31 00 2e 00 30 00 30 00 00 00
>> 00e0: 7f ff 04 00 00 00 42 4f
>> gryphon#
>>
>
> Perfect. I'll decode this and see if I can figure out where we'
On 18. 10. 12., Harry Schmalzbauer wrote:
> Am 12.10.2018 um 07:41 schrieb Dag-Erling Smørgrav:
>> Jung-uk Kim writes:
>>> I forgot to patch one more file, i.e., Makefile.inc1. Please try the
>>> attached patch instead.
>> Thanks, I missed that too.
>>
On 18. 10. 12., Jung-uk Kim wrote:
> On 18. 10. 11., Glen Barber wrote:
>> On Thu, Oct 11, 2018 at 10:55:46PM +, Glen Barber wrote:
>>> On Thu, Oct 11, 2018 at 10:32:34PM +, Glen Barber wrote:
>>>> I still see a failure with this applied.
>>>&g
On 18. 10. 12., Jung-uk Kim wrote:
> On 18. 10. 11., Glen Barber wrote:
>> On Thu, Oct 11, 2018 at 10:55:46PM +, Glen Barber wrote:
>>> On Thu, Oct 11, 2018 at 10:32:34PM +, Glen Barber wrote:
>>>> I still see a failure with this applied.
>>>&g
nt 2
>> of 'lh_ERR_STRING_DATA_insert' discards qualifiers from pointer target type
>> /usr/obj/usr/src/powerpc.powerpc/tmp/usr/bin/ld: cannot find -lpthread
>> *** Error code 1
>>
>> Stop.
>> make[4]: stopped in /usr/src/secure/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18. 10. 11., Jung-uk Kim wrote:
> On 18. 10. 11., Justin Hibbits wrote:
>> On Thu, 11 Oct 2018 19:07:45 + Glen Barber
>> wrote:
>>
>>> On Thu, Oct 11, 2018 at 09:05:52AM +0200, Raúl wrote:
>>>&g
ot
>> the final merge from the projects/openssl111 branch.
>>
>> Glen
>>
>
> Seems r339303 is the cuplrit. Reverting this gets my build completing.
It seems ldns now requires libssl.so to support DANE-TA. Please try the
attached patch.
Jung-uk Kim
Index: lib/libld
: 4f 00 53 00 00 00 04 01 2a 00 02 00 00 00 00 68
0020: 09 00 00 00 00 00 00 18 03 00 00 00 00 00 d9 29
0030: 2b 57 b4 37 24 48 b0 a1 0a d8 23 6b 38 db 02 02
0040: 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00
0050: 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00
0060: 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00
0070: 7f ff 04 00 aa 55 00 00
Good variable added by efibootmgr:
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0003
: 01 00 00 00 5e 00 55 00 45 00 46 00 49 00 20 00
0010: 4f 00 53 00 00 00 04 01 2a 00 02 00 00 00 00 68
0020: 09 00 00 00 00 00 00 18 03 00 00 00 00 00 d9 29
0030: 2b 57 b4 37 24 48 b0 a1 0a d8 23 6b 38 db 02 02
0040: 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00
0050: 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00
0060: 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00
0070: 7f ff 04 00
Actually, "efibootmgr -v" hangs or crashes depending on current boot
order. My guess is device path printing is not robust enough to ignore
the bogus data.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/03/2018 15:23, Jung-uk Kim wrote:
> On 07/03/2018 15:02, John Baldwin wrote:
>> On 7/3/18 11:28 AM, Niclas Zeising wrote:
>>> On 07/03/18 17:02, O. Hartmann wrote:
>>>> -BEGIN PGP SIGNED MESSAGE- Hash: S
=
> --- atomic.h (revision 335896)
> +++ atomic.h (working copy)
> @@ -446,10 +446,10 @@ ATOMIC_ASM(clear,int, "andl %1,%0", "ir", ~
> ATOMIC_ASM(add, int, "addl %1,%0", "ir", v);
> ATOMIC_ASM(subtract, int, "subl %1,%0", "ir", v);
>
> -ATOMIC_ASM(set, long, "orq %1,%0", "ir", v);
> -ATOMIC_ASM(clear,long, "andq %1,%0", "ir", ~v);
> -ATOMIC_ASM(add, long, "addq %1,%0", "ir", v);
> -ATOMIC_ASM(subtract, long, "subq %1,%0", "ir", v);
> +ATOMIC_ASM(set, long, "orq %1,%0", "er", v);
> +ATOMIC_ASM(clear,long, "andq %1,%0", "er", ~v);
> +ATOMIC_ASM(add, long, "addq %1,%0", "er", v);
> +ATOMIC_ASM(subtract, long, "subq %1,%0", "er", v);
>
> #define ATOMIC_LOADSTORE(TYPE) \
> ATOMIC_LOAD(TYPE); \
Isn't "Z" better than "e" in this case?
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
On 06/27/2018 13:05, Rodney W. Grimes wrote:
> There are several white papers, including one from VMWare about what
> they have done to help with the time keeping problems.
https://www.vmware.com/files/pdf/techpaper/Timekeeping-In-VirtualMachines.pdf
Jung-uk Kim
signature.asc
Descr
r nor interrupts are not running yet.
>
> Although, come to think of it, I seem to recall something about SMI
> interrupts mucking this up long in the past, for exactly the same
> reason.
I think it was legacy USB device emulation for certain Intel
chipset-based motherboards.
Jung-uk K
On 06/27/2018 12:47, Alan Somers wrote:
> On Wed, Jun 27, 2018 at 10:36 AM, Jung-uk Kim <mailto:j...@freebsd.org>> wrote:
>
> On 06/27/2018 03:14, Andriy Gapon wrote:
> >
> > It seems that TSC calibration in virtual machines sometimes can do more
>
different
> timecounter:
> https://lists.freebsd.org/pipermail/freebsd-cloud/2017-January/80.html
We already do that for VMware hosts since r221214.
https://svnweb.freebsd.org/changeset/base/221214
We should do the same for each hypervisor.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
rror: Method parse/execution failed
> \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677)
>
> with svn 329142 on a Lenovo ThinkCentre M83
> ACPI APIC Table:
>
> Claude Buisson
This problem should be fixed now (r80). Sorry for the delay.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
rror: Method parse/execution failed
> \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677)
>
> with svn 329142 on a Lenovo ThinkCentre M83
> ACPI APIC Table:
>
> Claude Buisson
I believe you can silence the errors with the attached patch. Please
try it and let me know
ssl/openssl/blob/master/tools/c_rehash.in
I guess they just forgot to add "functionally" in front of "equivalent". ;-)
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
On 02/08/2018 18:51, Ian Lepore wrote:
> On Thu, 2018-02-08 at 17:47 -0500, Jung-uk Kim wrote:
>> On 02/08/2018 17:31, Chris H wrote:
>>>
>>> [...]
>>> Couldn't this be in $base? I'd like to vote yes. :-)
>> From OpenSSL 1.1.0, openssl(1) added
On 02/08/2018 17:31, Chris H wrote:
> On Thu, 08 Feb 2018 13:25:13 -0700 "Ian Lepore" said
>> On Thu, 2018-02-08 at 21:15 +0100, Ulrich Spörlein wrote:
>> > 2018-02-08 21:00 GMT+01:00 Jung-uk Kim :
>> > > > > > On 02/08/2018 08:52, Jan Bramkam
On 02/08/2018 15:15, Ulrich Spörlein wrote:
>
> 2018-02-08 21:00 GMT+01:00 Jung-uk Kim <mailto:j...@freebsd.org>>:
>
> On 02/08/2018 08:52, Jan Bramkamp wrote:
> > On 08.02.18 14:24, Ulrich Spörlein wrote:
> >> Hey,
> >>
> &
>> history with git pickaxe right).
>
> The LibreSSL port lacks a c_rehash script as well. Putting c_rehash back
> into base wouldn't solve the problem because it requires Perl 5.
Correct. I just removed the manual page to not confuse users.
https://svnweb.freebsd.org/changeset/base/329024
Thanks for letting me know!
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 256(256) NS
link x4(x4) speed 2.5(2.5) ASPM disabled(L0s)
ecap 0001[100] = AER 1 0 fatal 1 non-fatal 0 corrected
ecap 0003[140] = Serial 1 00151751bcba
> I'm assuming you do *not* have any iflib or em(4) tuning options set either.
Nope.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
e vtnet interface.
Can you please try r322323 or later? Basically, r322076 was incomplete
and r322323 corrected the stupid mistake.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
t;^#"
>> ifconfig_re0="DHCP"
>>
>> "service netif restart" doesn't help either. Only manual dhclient
>> starting.
>
> Same issues here with today CURRENT, r315896.
FYI, r315901 fixed the issue for me.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
reebsd/src/sys/cam/scsi/scsi_all.c:59:
/export/freebsd/src/sys/cam/cam_xpt.h:36:10: fatal error: 'opt_printf.h' file
not found
#include "opt_printf.h"
I committed a fix already (r312852).
Jung-uk Kim
___
freebsd-current@
ec0: evaluation of query method _Q50 failed: AE_AML_OPERAND_TYPE
>
> over the holidays, so I assume that means the previous version of ACPI,
> 20161117 which the 20161222 version is supposed to fix.
I was AFK for two weeks. I will merge ACPICA 20161222 to FreeBSD head
this week when I find some free time.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
;> FWIW, I will commit the following change shortly. Since third-party
>>> modules break the invariant, either due to bugs (ndis wrappers) or
>>> possibly due to KBI breakage, it is worth to have the detection enabled
>>> for production kernels.
>>
>> Interesting ... I tried running virtualbox on recent 10.3-STABLE with a
>> GENERIC kernel and the guest seemed to operate properly. Then I enabled
>> INVARIANTS and got the panic. I suspect that is why nobody has stumbled
>> across this before.
>>
> This is yet another reason to promote KASSERT to the full panic.
> I expect that the vbox source lacks fpu_kern_enter() calls around the
> FPU state restoration.
Unfortunately, the code is in MI source as it is unnecessary for
supported OSes (read: FreeBSD is not supported) and it's not easy to
inject fpu_kern_enter()/fpu_kern_leave() calls there. :-(
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
On 07/25/16 03:27 PM, Jung-uk Kim wrote:
> On 07/25/16 03:13 PM, Randy Westlund wrote:
>> I'm running 12-CURRENT r303286 and virtualbox-ose-kmod-5.0.26. I just
>> rebuilt the module, so I know they're in sync. When I boot with
>> vboxdrv_load="YES" in
b: movq$0,kdb_why
>
> I'm not sure whether this is a problem with the base system or the port,
> but this happens every time I boot with the module enabled.
emulators/virtualbox-ose-kmod is causing the trouble and this problem is
well known. To work around it, remove WITNESS option from kernel
configuration for now.
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
(r302984) and I think someone
> else reported a similiar issue earlier.
FYI, this bug was introduced in r302324, which is between ALPHA6 and
BETA1. It should be fixed in r302916 (head) and r303112 (stable/11).
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
On 07/18/16 08:12 AM, Mathieu Arnold wrote:
> Hi,
>
> +--On 11 juillet 2016 22:56:00 +0300 Slawa Olhovchenkov
> wrote:
> | On Mon, Jul 11, 2016 at 03:00:39PM -0400, Jung-uk Kim wrote:
> |> > .if ( ${PORT_OPTIONS:MGOST} || ${PORT_OPTIONS:MGOST_ASN1} ) &&
>
On 07/11/16 02:41 PM, Slawa Olhovchenkov wrote:
> On Mon, Jul 11, 2016 at 02:28:45PM -0400, Jung-uk Kim wrote:
>
>> On 07/10/16 10:10 AM, Andrey Chernov wrote:
>>> On 10.07.2016 16:30, Slawa Olhovchenkov wrote:
>>>> I am surprised lack of support GOST in opens
enSSL 1.1.0 branch.
[OpenSSL-maintainer-for-the-base hat off]
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
containing the
# X.509v3 extensions to use:
Please see the README file for more info:
https://svnweb.freebsd.org/base/head/crypto/openssl/engines/ccgost/README.gost?revision=238405&view=co
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
69 and the ports
>> were built before the -r298793 buildworld/buildkernel was done. And both
>> -r297769 and -r298793 11.0's are running under the same vintage of Virtual
>> Box (5.0.20 r106931).
>>
>> So what is different is just the FreeBSD vintage.
>>
>> 11.0's -r297769 virtual machine does contain the buildworld/buildkernel
>> /usr/obj material for -r298793, it is just not installed.
>
> This was already covered in an earlier thread. r298838 has the fix /
> workaround.
FYI, the upstream was notified and a patch is available from here:
https://github.com/acpica/acpica/pull/138
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
On 04/29/16 05:46 PM, Jung-uk Kim wrote:
> On 04/29/16 05:17 PM, John Baldwin wrote:
>> You'll have to talk to the Intel guy who broke this to find out how he'd
>> like to fix it (not hardcode 32, or fix the AccessWidth).
>
> I notified Intel guys and they will ta
fix ASAP.
Thanks for analysing the issue quickly!
Jung-uk Kim
signature.asc
Description: OpenPGP digital signature
ser look at the following commits:
https://github.com/acpica/acpica/commit/6cb97888
https://github.com/acpica/acpica/commit/3d8583a0
https://github.com/acpica/acpica/commit/48eea5e7
https://github.com/acpica/acpica/commit/41f6aefa
https://github.com/acpica/acpica/commit/c23034a3
https:/
6975
> Last Changed Date: 2016-03-16 20:15:16 -0500 (Wed, 16 Mar 2016)
It seems r296967 is the culprit:
https://svnweb.freebsd.org/changeset/base/296967
The attached patch fixed the build issues for me.
Jung-uk Kim
Index: lib/libxo/tests/Makefile
===
type
> Mar 1 16:54:36 toshi kernel: KLD vboxnetadp.ko: depends on
> vboxnetflt - not available or version mismatch Mar 1 16:54:36
> toshi kernel: linker_load_file: Unsupported file type
It should be fixed now (r409965).
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/19/16 06:49 PM, Jung-uk Kim wrote:
> On 01/19/16 06:05 PM, Dimitry Andric wrote:
>> On 19 Jan 2016, at 23:32, Thomas Mueller
>> wrote:
>>>
>>> Has there recently been a version bump in the shared
>>&
rtmaster and pkg which I rebuilt after getting the
>> errors?
>
> It is easiest to use pkg-static to reinstall your ports, e.g.:
>
> pkg-static update pkg-static upgrade
>
> Alternatively, rebuild all ports depending on OpenSSL.
A crude way to find almost all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL on head has been updated to 1.0.2d. Please make sure to
recompile all binaries depending on libcrypto.so.7 or libssl.so.7.
Cheers!
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJWM9nDAAoJEHyflib82/FGuV8H
ative to the point at
which the system must supply the maximum cooling for the processor's
specified maximum case temperature and maximum thermal power dissipation”
according to BIOS and Kernel Developer's Guide (BKDG) for AMD Processors,
http://developer.amd.com/documentation/guid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/03/2015 18:30, David Wolfskill wrote:
> [Much trimming, both of older content and recipient addresses --
> dhw]
>
> On Thu, Sep 03, 2015 at 06:18:52PM -0400, Jung-uk Kim wrote:
>> ... AFAICT, the whole suspend/resume code lo
sys/dev/usb/controller/ohci_pci.c looks like a good use of
> pci_set_powerstate. sys/dev/ixgbe/if_ix.c looks like an incorrect /
> redundant use of the functions.
AFAICT, the whole suspend/resume code looks incomplete and very messy.
In fact, I'll be very surprised if it ever worked. :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/02/2015 21:26, Cy Schubert wrote:
> In message <551da257.6060...@freebsd.org>, Jung-uk Kim writes:
>> This is a multi-part message in MIME format.
>> --090800070300040107060309 Content-Type: text/plain;
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/02/2015 16:11, Jung-uk Kim wrote:
> On 04/01/2015 11:32, Manfred Antar wrote:
>> Apr 1 08:29:19 pozo ntpd[49825]: setsockopt IPV6_MULTICAST_IF 0
>> for fe80::1%2 fails: Can't assign requested address
>
> A sepa
x
> error
ntp_crypto.c was not properly merged. Basically, the fix for
SA-14:31.ntp was applied twice. Please try the attached patch.
> Apr 1 08:29:19 pozo ntpd[49825]: setsockopt IPV6_MULTICAST_IF 0
> for fe80::1%2 fails: Can't assign requested address
A separate issue, I think.
compiler.y maximum
> table size exceeded *** [aslcompilerparse.c] Error code 2 make[5]:
> stopped in /usr/src/usr.sbin/acpi/iasl 1 error
>
>
> Does your fix address the problem in HEAD or just STABLE?
Just stable.
http://docs.freebsd.org/cgi/mid.cgi?54EE05EA.3030509
Jung-uk Kim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/25/2015 14:59, Arseny Nasokin wrote:
> On 25 February 2015 at 22:14, Jung-uk Kim <mailto:j...@freebsd.org>> wrote:
>
> On 02/25/2015 14:05, Glen Barber wrote:
>> On Wed, Feb 25, 2015 at 10:51:31PM +0400, Arseny
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/25/2015 14:05, Glen Barber wrote:
> On Wed, Feb 25, 2015 at 10:51:31PM +0400, Arseny Nasokin wrote:
>> On 25 February 2015 at 20:27, Jung-uk Kim
>> wrote:
>>> Your installed yacc(1) is too old, i.e., your world was bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/25/2015 13:55, Garrett Cooper wrote:
> On Feb 25, 2015, at 10:51, Arseny Nasokin
> wrote:
>
>> On 25 February 2015 at 20:27, Jung-uk Kim
>> wrote:
>>
> On 02/25/2015 11:22, Ivan Klymenko wrote:
>>>&g
for
building from stable:
https://svnweb.freebsd.org/changeset/base/278975
For building from old head (pre-r274460), you have to manually
bootstrap yacc first, e.g., something like this:
cd /usr/src/usr.bin/yacc
make clean cleandepend
make all &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/05/2015 12:33, Jung-uk Kim wrote:
> On 01/05/2015 12:27, Lev Serebryakov wrote:
>> On 05.01.2015 20:11, Jung-uk Kim wrote:
>
>>> Someone with copious free time and enough knowledge should be
>>> able to por
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/05/2015 12:27, Lev Serebryakov wrote:
> On 05.01.2015 20:11, Jung-uk Kim wrote:
>
>> Someone with copious free time and enough knowledge should be
>> able to port Linux KMS/DRM2 driver for us.
>
>> https://www.
runk/src/VBox/Additions/linux
It shouldn't be too hard. ;-)
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJUqsXNAAoJEHyflib82/FGni4H/RJrYLCNoYKdny70LJ0O6+o0
Mh5sf/fdfUkmfynrbyDAgCFfXdzD2/3p2NIX4WGgysUxOTgtWGFTLW67VNnQupwK
pBSwz7Ute4LrSmXg
A file seems missing. I worked around it like this:
sed -e 's/@ENABLE_DNSTAP@/0/' \
/usr/src/contrib/unbound/dnstap/dnstap_config.h.in > \
/usr/src/contrib/unbound/dnstap/dnstap_config.h
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBCAAGBQJUp6FaAAoJEHyflib82/F
The next
> highest on the list is java/openjdk6, for which ports r374780 [4]
> was very recently committed.
Unfortunately, r374780 was not enough. Instead, I just turned off
"-Werror" for now (r374824).
https://svnweb.freebsd.org/changeset/ports/374824
Jung-uk Kim
-BEGIN PGP SIGN
panic: make_dev_credv:
> bad si_name (error=17, si_name=full)
...
FYI, lindev(4) was removed in r265212.
http://svnweb.freebsd.org/changeset/base/265212
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)
iQEcBAEBAgAGBQJTY9GXAAoJEHyflib82/FGKPsH/3mpNaAgbC8kQuJif
On 2014-04-19 02:14:58 -0400, Thomas Hoffmann wrote:
> On Sat, Apr 19, 2014 at 1:05 AM, Jung-uk Kim <mailto:j...@freebsd.org>> wrote:
>
> On 2014-04-18 23:46:46 -0400, Thomas Hoffmann wrote:
> > After building at -CURRENT amd64 r264673, I got the following
>
On 2014-04-18 23:46:46 -0400, Thomas Hoffmann wrote:
> After building at -CURRENT amd64 r264673, I got the following
> errors running 'make delete-old' and 'make delete-old-libs':
...
This should be fixed in r264674.
Jung-uk Kim
_
past then?
>>>>>
>>>>
>>>> .. and I've submitted it as a PR:
>>>>
>>>> kern/187152
>>>
>>> Complete stab in the dark (not compile tested) here:
>>>
>>> http://www.FreeBSD.org/~jhb/patches/i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-09-18 13:20:27 -0400, Jung-uk Kim wrote:
2013년 9월 18일 13:20, Jung-uk Kim 쓴 글:> On 2013-09-18 12:39:46
- -0400, David Chisnall wrote:
>> On 18 Sep 2013, at 16:26, Tijl Coosemans
>> wrote:
>
>>> On Tue, 17 Sep 2013
it broke OpenOffice.org. 8-)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38732
http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=143170
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.21 (FreeBSD)
iQEcBAEBAgAGBQJSOgkeAAoJECXpabHZMqHOlcwIALxc3r7H3Ocj7TPOG41itms6
+pmquUmLC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-09-18 12:39:46 -0400, David Chisnall wrote:
> On 18 Sep 2013, at 16:26, Tijl Coosemans wrote:
>
>> On Tue, 17 Sep 2013 21:04:14 -0400 Jung-uk Kim wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-09-17 13:24:41 -0400, Jung-uk Kim wrote:
> I am still working on libc++ issues but it is much more
> complicated. :-(
I fixed almost everything except for exception handling issues.
Unfortunately, libc++/libcxxrt's exception hand
stantiation of function template specialization
>> 'mdds::multi_type_matrix::set> *>' requested here maMat.set(nR, nC, pArray, pArray + nLen); ^
>> /wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-4.0.5.2/sc/source/core/tool/scmatrix.cxx:92:65:
>>
>>
branded CPU which did
> not implemented cmpxchg8b. Some late 486 did provided cpuid, but I
> am almost certain that they did not have cmpxchg8b (cannot check
> anyway).
It is actually little complicated.
http://www.geoffchappell.com/studies/win
urther. Any ideas?
I had a similar problem a week ago. Basically, that Clang version
mis-compiles xorg-server. You may want to try the latest Clang on
- -CURRENT or build it with "make USE_GCC=any".
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.20 (FreeBSD)
iQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-05-22 12:24:45 -0400, Sergey Kandaurov wrote:
> On 22 May 2013 00:03, Jung-uk Kim wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> Please note flex/lex was updated to 2.5.37 from
>> flex.sourceforge.ne
version. OTOH, this version is far more popular and third-party
sources often require this version. Most importantly, NetBSD,
DragonFly BSD, and Mac OS X already adopted it for the same reason.
Cheers!
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.20 (FreeBSD
0x000803869eb9 in ?? () #16 0x in ??
>>> () (gdb)
>>>
>>> That backtrace would probably be clearer if you got it from a
>>> debug build of OpenJDK. Also you could find the exact commit
>>> that broke it by doing a bisection-search in SVN
5/ rebuild regcomp.o, regcomp.So
>> with -O2 to confirm
>
> I have been able to reproduce this on amd64, with -O3, but not on
> i386. It seems regcomp() is either miscompiled at -O3, or it
> contains some bug triggered only by the vectorizer. I am still
> investigating.
.
already lives in src/contrib and src/sys/contrib,
> would the change in License from Darren Reed's own not so BSD
> friendly IPF license to GPLv2 be of concern. I recall there was a
> lot of concern over IPF's license change at the time. (FreeBSD
> moved it to contrib while OpenBS
uot;safe mode" in the boot
>> loader menu seems to work around the problem on my system. Now I
>> will not reboot until I see a fix for this in head :-)
>
> "safe mode" toggles a few different things IIRC, can you narrow it
> dow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-26 11:58:16 -0500, Pawel Jakub Dawidek wrote:
> On Fri, Jan 25, 2013 at 04:19:44PM -0500, Jung-uk Kim wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 2013-01-25 04:26:02 -0500, Pawel Jakub Dawidek wrot
irely closed).
>
> Closing lid doesn't trigger suspend or anything like that. It just
> turns off the display.
Please try the attached patch (with my previous patch). Also,
available from here:
http://people.freebsd.org/~jkim/acpi_exit.diff
Thanks,
Jung-uk Kim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-01-24 04:41:08 -0500, Andriy Gapon wrote:
> on 24/01/2013 02:54 Jung-uk Kim said the following:
>>
>> Can you please try the attached patch? It is also available from
>> here:
>>
>> http://people.freebsd.or
may not fix the problem but I think I
found an ancient bug. :-(
Thanks,
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
iQEcBAEBAgAGBQJRAIZhAAoJECXpabHZMqHOWl8H/3pUGshUkzCNbEOQHoZOYXMW
TtLaUqdV3/zYGEYDYl5Tbxv2JUz4tWDU5KlWhnZk+MjNnR1+g0fgzQu3mK056NU+
rpZu
exit code 1 TB --- 2013-01-21 20:22:58 - ERROR: failed to
> build LINT kernel TB --- 2013-01-21 20:22:58 - 5462.62 user 1225.88
> system 7131.85 real
>
>
> http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-ia64-ia64.full
It
>
should be
ken when jkim imported the latest ACPICA code
> base:
> https://svnweb.freebsd.org/base?view=revision&revision=245582
>
> I've forward the tinderbox failure to him, so hopefully he'll fix
> it shortly...
It should be fixed now (r245636). Sorry for the breakage.
Jun
clang and would like to know, since the default is now clang
> on -CURRENT.
#ifdef __clang__
/* clang-specific stuff */
#else
/* Something else */
#endif
Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla -
1 - 100 of 197 matches
Mail list logo
