Re: How to supress prompt on bc 5.3.1,Re: How to supress prompt on bc 5.3.1

2022-06-15 Thread Masachika ISHIZUKA
. Thank you for commit. 'bc' 5.3.3 works fine on master-n256152-ce00b11940a. -- Masachika ISHIZUKA

Re: dmesg: ACPI Warning: Firmware issue warning spaming

2022-06-13 Thread Masachika ISHIZUKA
872cad521 >>> I am not sure what happened after that. >> I found the author actually filed a pull request to revert the commit. >> https://github.com/acpica/acpica/pull/780 > > FYI, I removed the message. > > https://cgit.freebsd.org/src/commit/?id=c7f14adfda21dfacab1895015b4c78bf7c2febb6 Thank you very much. -- Masachika ISHIZUKA

How to supress prompt on bc 5.3.1

2022-06-13 Thread Masachika ISHIZUKA
I updated to master-n256084-5dd1f6f1441 (1400061) and this leads to bc to 5.3.1. Previosly, 'BC-ENV-APRG=-P' or 'bc -P' were working but it doesn't work on 5.3.1. Is there any way to supress prompt ? -- Masachika ISHIZUKA

Re: dmesg: ACPI Warning: Firmware issue warning spaming

2022-06-13 Thread Masachika ISHIZUKA
ime (0x0010 >> ms > >> > 10 ms) in ACPI Control Method (20220331/exsystem-347) >> > --- >> > Is there a way to silence it? I think this spam message is from linux. So, I think we should discuss on linux forum but I don't familier to linux. -- Masachika ISHIZUKA

Re: dmesg: ACPI Warning: Firmware issue warning spaming

2022-06-12 Thread Masachika ISHIZUKA
{ ACPI_WARNING ((AE_INFO, -"Firmware issue: Excessive sleep time (0x%8.8X%8.8X ms > 10 ms)" +"Firmware issue: Excessive sleep time (0x%8.8X%8.8X ms > 20 ms)" " in ACPI Control Method", ACPI_FORMAT_UINT64 (HowLongMs))); } -- Masachika ISHIZUKA

How can I suppress ACPI Warning messages ?

2022-04-23 Thread Masachika ISHIZUKA
ess this ACPI warning messages ? -- Masachika ISHIZUKA

Re: make buildworls over NFS

2021-06-22 Thread Masachika ISHIZUKA
] _COPY_HOST_TOOL=cp -pf [new] _COPY_HOST_TOOL=ln -sfn (2) edit /usr/src/Makefile.inc1 [old] cp -pf ${.CURDIR}/sys ${WORLDTMP} [new] ln -sfn ${.CURDIR}/sys ${WORLDTMP} -- Masachika ISHIZUKA

make buildworls over NFS

2021-06-22 Thread Masachika ISHIZUKA
can 'make buildworld' after clear uarch flags on all files in /bin, /sbin, /usr/bin and /usr/sbin. Is there any way to 'make buildworld' easier ? -- Masachika ISHIZUKA

Re: system freeze on 14.0-CURRENT

2021-04-02 Thread Masachika ISHIZUKA
>> main-8223717ce is working fine on vostro 3267, but isn't >> working on XPS 12. > > main-4d221f59b is freezed on vostro 3267. Although main-8223717ce wasn't frozen on vostro 3267 yesterday, main-8223717ce is frozen on vostro 3267 today. --

Re: system freeze on 14.0-CURRENT

2021-04-02 Thread Masachika ISHIZUKA
> main-8223717ce is working fine on vostro 3267, but isn't > working on XPS 12. main-4d221f59b is freezed on vostro 3267. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-c

Re: system freeze on 14.0-CURRENT,Re: system freeze on 14.0-CURRENT

2021-03-31 Thread Masachika ISHIZUKA
me level. > > I tried to disable hwpstate_intel via loader.conf and it helps: > > % grep hint /boot/loader.conf > hint.hwpstate_intel.0.disabled="1" Unfortunately, hint.hwpstate_intel.0.disabled="1" doesn't solve XPS12 freeze problem. -- Masachika ISHIZUKA

Re: system freeze on 14.0-CURRENT

2021-03-30 Thread Masachika ISHIZUKA
main-8223717ce is working fine on vostro 3267, but isn't working on XPS 12. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-cu

Re: system freeze on 14.0-CURRENT

2021-03-29 Thread Masachika ISHIZUKA
CURRENT 146 main-6a762cfae. [vostro 3568] CPU: Celeron 3865U RAM: 4GB graphics: intel HD610 (i915kms) P.S. As I installed kernel and userland from NFS server, I think all machines binaries are the same. -- Masachika ISHIZUKA ___ freebsd-current@

Re: system freeze on 14.0-CURRENT

2021-03-28 Thread Masachika ISHIZUKA
memory: 8GB graphics: intel HD4400(i915kms) [vostro 3267] cpu: Core i5-7500 memory: 12GB graphics: intel HD630(i915kms) And I also use dell studio 1558 laptop. This machine is working fine, not freezed. [studio 1558] cpu: core i7-Q840 memor

Re: system freeze on 14.0-CURRENT

2021-03-28 Thread Masachika ISHIZUKA
Unfortunely, machine was frozen and all ssh connections were frozen too. -- Masachika ISHIZUKA ___ 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"

system freeze on 14.0-CURRENT

2021-03-27 Thread Masachika ISHIZUKA
v87.0 is working well. # I want to update to the newest 14.0-CURRENT because of ssl security problems. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: pkg for 14-current

2021-01-27 Thread Masachika ISHIZUKA
t now.) Thank you very much. I'm happy to be able to pkg upgrade on 14-current. -- Masachika ISHIZUKA ___ 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"

pkg for 14-current

2021-01-24 Thread Masachika ISHIZUKA
/meta.txz: Not Found > repository FreeBSD has no meta file, using default settings > pkg: http://pkgmir.geo.freebsd.org/FreeBSD:14:amd64/latest/packagesite.txz: > Not Found > Unable to update repository FreeBSD > Error updating repositories

Re: r359627 is panicked with 'softdep_setup_blkfree: not free'

2020-04-09 Thread Masachika ISHIZUKA
I applied the above patch to r359627M and occured panic. This was r359668 was not applied. I made buildkernel on r359766M and this looks work fine. Thank you very much for your effort. # The panic was occured to open/close tabs on firefox. -- Masachika ISHIZUKA __

Re: r359627 is panicked with 'softdep_setup_blkfree: not free'

2020-04-09 Thread Masachika ISHIZUKA
ournaltrunc == 0 && DOINGSOFTDEP(vp) && length == 0) > softdeptrunc = !softdep_slowdown(vp); > extblocks = 0; Thank you for reply, and sorry to late reply. Unfortunately, this patch did not prevent panic. -- Masachika ISHIZUKA

Re: r359627 is panicked with 'softdep_setup_blkfree: not free'

2020-04-07 Thread Masachika ISHIZUKA
l version and userland version, it's good working. I'll use this old kernel for a while. -- Masachika ISHIZUKA ___ 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: r359627 is panicked with 'softdep_setup_blkfree: not free'

2020-04-06 Thread Masachika ISHIZUKA
ne. The panic was occured again. Crash dump was the same. To reinstall drm-current-kmod was not fixed this issue. -- Masachika ISHIZUKA ___ 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: r359627 is panicked with 'softdep_setup_blkfree: not free'

2020-04-06 Thread Masachika ISHIZUKA
Annotations: FreeBSD_version: 1300084 <--- old [snip] old# pkg install -f drm-current-kmod new% pkg info drm-current-kmod [snip] Annotations: FreeBSD_version: 1300088 [snip] This works fine. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.o

r359627 is panicked with 'softdep_setup_blkfree: not free'

2020-04-06 Thread Masachika ISHIZUKA
ery large(128MB) -- Masachika ISHIZUKA ___ 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: Build failed compiling ittnotify_static.pico

2020-03-14 Thread Masachika ISHIZUKA
ico] Error code 1 >> >> 'make cleanworld' solved it, build without error. >> I used to always delete obj for years, but I've not done that for a >> couple of years without any problems I've noticed. > > Thank you for information. > I'

Re: Build failed compiling ittnotify_static.pico

2020-03-13 Thread Masachika ISHIZUKA
gt; > 'make cleanworld' solved it, build without error. > I used to always delete obj for years, but I've not done that for a > couple of years without any problems I've noticed. Thank you for information. I'll try it. -- Masachika ISHIZUKA __

Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

2020-01-24 Thread Masachika ISHIZUKA
gt;>>> You could just plug it with a one liner that adds IFF_NEEDSEPOCH >>>> in ieee80211_vap_attach(). >>>> >>>> Or fix ath, which I'm going to do in next five minutes. >>> >>> Now, I'm doing buildworld/buildkernel on r357093 with D23

Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

2020-01-24 Thread Masachika ISHIZUKA
AL media: IEEE 802.11 Wireless Ethernet DS/1Mbps mode 11ng status: associated nd6 options=29 lagg0: flags=8843 metric 0 mtu 1500 ether XX:XX:XX:XX:XX:XX inet XXX.XXX.XXX.XXX netmask 0xff00 broadcast XXX.XXX.XXX.XXX inet6 fe80::5%

Re: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

2020-01-24 Thread Masachika ISHIZUKA
Or fix ath, which I'm going to do in next five minutes. > > Now, I'm doing buildworld/buildkernel on r357093 with D23347 and D23348. Hi. t357093 with D23347 and D23348 was panicked. Screenshot is https://www.ish.org/files/panic-r357093+D23347+D23348.jpeg -- Masachika ISHIZUKA ___ 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: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

2020-01-24 Thread Masachika ISHIZUKA
48 are not fixed my problem. Now, I'm doing buildworld/buildkernel on r357093 with D23347 and D23348. As I'm busy to care of my old father, I'm sorry to late reply mail. -- Masachika ISHIZUKA ___ 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: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

2020-01-24 Thread Masachika ISHIZUKA
I can not capture screen. Screenshot was uploaded to https://www.ish.org/files/panic-r357061.jpeg -- Masachika ISHIZUKA ___ 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: panic: Assertion in_epoch(net_epoch_preempt) failed at ... src/sys/net/if.c:3694

2020-01-23 Thread Masachika ISHIZUKA
> 21.01.2020, 20:10, "Nick Hibma" : >> That (with the return added, thanks Cy) worked like a charm. > Got committed in r357038. > Thank you for the report! Hi. My machine was panicked on r357061 with in_epoch in netisr.c. I can not capture scree

Re: DRM-current-kmod is still a problem at r353339

2019-10-18 Thread Masachika ISHIZUKA
s are required. (2) DELL Vostro 3568 notebook (Celeron 3865U) Both patches are required. (3) DELL XPS 12 9Q33 notebook (core i7-4500U) At least mjg@'s pmap-fict-invl patch is required. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing

Re: DRM-current-kmod is still a problem at r353339

2019-10-18 Thread Masachika ISHIZUKA
0xfe0060c4eab0 kernel: --- trap 0, rip = 0, rsp = 0, rbp = 0 --- kernel: Uptime: 11h21m3s kernel: Dumping 874 out of 8058 MB:..2%..11%..21%..32%..41%..52%..61%..72%..81%..92% -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list htt

Re: hang up with r352239 and r352386 with i5-7500

2019-09-18 Thread Masachika ISHIZUKA
fully it > works. It will take some time before it shows up as packages, but > there is no problems building drm-current-kmod from ports even if > packages are used for the rest of the system. It is good working drm-current-kmod-4.16.g20

Re: hang up with r352239 and r352386 with i5-7500

2019-09-18 Thread Masachika ISHIZUKA
unning an >> INVARIANTS kernel you might be hitting an assertion failure; having the >> vmcore would help us debug. > > Thank you for mail. > > As I'm busy now, I'll try to get kernel dump about 1 day after. I'm very sorry. The patch you suggested is work fine.

Re: hang up with r352239 and r352386 with i5-7500

2019-09-17 Thread Masachika ISHIZUKA
hed. > > Are you able to collect a kernel dump? If so, remove the kld_list > setting and set debug.debugger_on_panic=0 and dev.drm.skip_ddb=1. Then > manually kldload /boot/modules/i915kms.ko. If you are running an > INVARIANTS kernel you might be hitting an assertion fail

Re: panic: sleeping thread on r352386

2019-09-17 Thread Masachika ISHIZUKA
1728(kernel)/r352432(user land). After that, 'make -j4 buildworld && make -j4 buildkernel' on r352432M(patched kernel)/ r352432(user land) with the nfs file system was done successfully. -- Masachika ISHIZUKA ___ 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: panic: sleeping thread on r352386

2019-09-17 Thread Masachika ISHIZUKA
As the result, 'make buildworld' stopped with a panic that "sleeping thread (...) owns a non-sleepable lock". -- Masachika ISHIZUKA ___ 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: panic: sleeping thread on r352386

2019-09-16 Thread Masachika ISHIZUKA
to be written at offset 0xe925000 for process ld.lld Sep 17 14:01:53 okra kernel: pid 50292 (ld.lld), jid 0, uid 16220: exited on signal 11 (core dumped) I can 'make buildworld' successfully on r351728(1300044). -- Masachika ISHIZUKA ___ freebsd-c

Re: hang up with r352239 and r352386 with i5-7500

2019-09-16 Thread Masachika ISHIZUKA
> On 2019-09-16 16:06, Masachika ISHIZUKA wrote: >>> Can you please use absolute paths to i915kms.ko anyway, just to test? >>The same hang up occure with kld_list="/boot/modules/i915kms.ko" >> in /etc/rc.conf. >> > > Even after applying the

Re: hang up with r352239 and r352386 with i5-7500

2019-09-16 Thread Masachika ISHIZUKA
> Can you please use absolute paths to i915kms.ko anyway, just to test? The same hang up occure with kld_list="/boot/modules/i915kms.ko" in /etc/rc.conf. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://list

Re: hang up with r352239 and r352386 with i5-7500

2019-09-16 Thread Masachika ISHIZUKA
d560 ng_l2cap.ko 221 0x8312600019900 ng_btsocket.ko 231 0x8314 2100 ng_socket.ko 241 0x83143000263b0 ipfw.ko 251 0x8316a0003c960 linux.ko 261 0x831a700034b70 linux64.ko 271 0x831dc000 45a0

Re: hang up with r352239 and r352386 with i5-7500

2019-09-16 Thread Masachika ISHIZUKA
u apply that and recompile > drm-current-kmod and see if it works? Thank you. I did the following. # portsnap fetch # portsnap update # cd /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux # vi pagevec.h (comment out line 49) # cd /usr/ports/graphics/drm-current-kmod

panic: sleeping thread on r352386

2019-09-16 Thread Masachika ISHIZUKA
cpuid = 3 time = 1568633100 KBD: stack backtrace: db_trace_self_wrapper() at (snip) vpanic() at (snip) (snip) --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter : panic [ thread pid 2108 tid 100236 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> -- Masachika ISHIZ

hang up with r352239 and r352386 with i5-7500

2019-09-16 Thread Masachika ISHIZUKA
9 (1300047). -- Masachika ISHIZUKA ___ 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: Can't buildworld at r350321

2019-07-25 Thread Masachika ISHIZUKA
>>I want to update 13-current from r349989 to r350321 as follows. > > This should have been fixed, or at least worked around, in r350322, as > I understand it. > Regards Thank you, Niclas. I'm very happy because I can make buildworld in r350322. --

Can't buildworld at r350321

2019-07-25 Thread Masachika ISHIZUKA
cal/freebsd-current/src/lib/libsysdecode (snip) make: stopped in /usr/altlocal/freebsd-current/src 20974.852u 3569.891s 2:17:32.86 297.4% 60110+3554k 183950+308232io 225686pf+0w I can buildworld at r349989 without errors. -- Masachika ISHIZUKA ___ free

Re: libunwind: decodeEHHdr

2019-02-20 Thread Masachika ISHIZUKA
hine and reinstall kernel/userland to the broken machines. Now they are working well. P.S. Althougth I was applied patches of https://reviews.llvm.org/D57081, no libunwind: decodeEHHdr messages are displayed. I think D57081 is not cause of this. -- Masachika ISHIZUKA ___

Re: libunwind: decodeEHHdr

2019-02-19 Thread Masachika ISHIZUKA
.eh_frame_hdr version > Redirecting call to abort() to mozalloc_abort 'https://reviews.llvm.org/D57081' was found, but I have not tried this patch yet. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/

libunwind: decodeEHHdr

2019-02-19 Thread Masachika ISHIZUKA
/GENERIC amd64 Is this error only me ? -- Masachika ISHIZUKA ___ 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: How to run drm-next-kmod on r334511

2018-06-02 Thread Masachika ISHIZUKA
This should be fixed as of ports r471368. > https://svnweb.freebsd.org/ports?view=revision=471368 Thank you, Niclas. Now, drm-next-kmod works again on r334511. -- Masachika ISHIZUKA ___ 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: How to run drm-next-kmod on r334511

2018-06-02 Thread Masachika ISHIZUKA
We are working on a fix now. > Sorry for any trouble caused. Thank you for reply, Johannes Since it works well in 11.2-RC1, it is not in a hurry, but I am looking forward to being fixed. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing

How to run drm-next-kmod on r334511

2018-06-01 Thread Masachika ISHIZUKA
Hi. When I updated to r334511, drm-next-kmod is not working with the message '[drm:fw_domain_wait_ack] render: timed out waiting for forcewake ack request.'. drm-next-kmod was working fine on r333704. My CPU is pentium G4560(kaby lake). -- Masachika ISHIZUKA

Re: /usr/obj is 11GB huge on FreeBSD 12-current

2017-12-15 Thread Masachika ISHIZUKA
nd removed no-longer-used subdirectories under /usr/obj/usr/src/. Now, I have enought space to 'make -j4 buildworld && make -j4 kernel'. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/

Re: panic r326359

2017-11-30 Thread Masachika ISHIZUKA
in /boot/loader.conf >>Thank you for reply, HPS. >>It seems good working by 'set kern.smp.disabled=1' on loader prompt. > > Issue should be fixed by: > https://svnweb.freebsd.org/changeset/base/326376 Thank you, HPS. I updated r326384 and it is good working. -- M

Re: panic r326359

2017-11-29 Thread Masachika ISHIZUKA
et/2007/07/01/ufs_dirbad-panic-with-mangled-entries-in-ufs/ # and now work well. -- Masachika ISHIZUKA ___ 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"

panic r326359

2017-11-29 Thread Masachika ISHIZUKA
not read locked @ /usr/src/sys/net/if_lagg.c:1655 Dump Parity: 971727379 Bounds: 6 Dump Status: good I put vmcore.6.bz2(157mb) in the following. https://www.ish.org/files/vmcore.6.bz2 -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list

Re: Xorg error 'alphasort'

2017-05-31 Thread Masachika ISHIZUKA
Hi. I was using 12-current r318249 and did 'pkg upgrade', and could not start xorg with alphasort error. After updating r319315, xorg works again. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org

Re: r316677:EFI boot failure: Can't load kernel

2017-04-11 Thread Masachika ISHIZUKA
\ <--- hang up = I can only reboot (ctrl-alt-del) for this hang up. -- Masachika ISHIZUKA ___ 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: r316677:EFI boot failure: Can't load kernel

2017-04-11 Thread Masachika ISHIZUKA
s are > booting again. > > Conclusion: UEFI loader is broken! Hi. I'm using dell xps12 9q33 (core i7-4500U) with an internal SSD. As reporting Bug 218473, I cannot boot /boot/loader.efi after r316585. Replacing only loader.efi before r316584, I can boot

How to automount an internal ntfs partition ?

2017-03-17 Thread Masachika ISHIZUKA
ernal ntfs partition. It is working well for ufs partitions and fat partitions. # I want to automatic unmount partitions that are not accessed for a long time because it prevent from damage if some panic occurred. # 11.0-RELEASE-p8 is the same result. -- Masachik

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-18 Thread Masachika ISHIZUKA
sd-bug 217161 is working again. As this patch was applied by r313912, the head branch is working again. (I'm tested at r313915). -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-curr

Re: 'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-12 Thread Masachika ISHIZUKA
ght information for Shockwave Flash 24.0 r0 was displayed. -- Masachika ISHIZUKA ___ 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: 'Protocol not supported' on linux socket call ( r313313 amd64 )

2017-02-09 Thread Masachika ISHIZUKA
Hi. linux-flashplayer (with opera or firefox) is not working with r313440. After reverting r313285 and r313284, it is working again. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

Re: 5.1-beta2 failed upgrade install

2003-06-04 Thread Masachika ISHIZUKA
Are there anybody who can upgrade to 5.1-RC1 successfully with Xeon or Pentium4 ? I can newly install 5.1-RC1, but I can not upgrade from 5.1-BETA or 5.1-RC1 to 5.1-RC1 with Xeon or Pentium4 without panics. -- [EMAIL PROTECTED] ___ [EMAIL PROTECTED]

Re: 5.1-beta2 failed upgrade install

2003-06-04 Thread Masachika ISHIZUKA
Are there anybody who can upgrade to 5.1-RC1 successfully with Xeon or Pentium4 ? I can newly install 5.1-RC1, but I can not upgrade from 5.1-BETA or 5.1-RC1 to 5.1-RC1 with Xeon or Pentium4 without panics. Here, here. I was doing installworld and got a double fault. After rebooting with

Re: 5.1-beta2 failed upgrade install

2003-05-30 Thread Masachika ISHIZUKA
I want to upgrade from 5.1-BETA-20030522-JPSNAP to 5.1-BETA2 with CD-ROM (5.1-BETA2-i386-disc1.iso). I upgraded from 5.1-BETA2 to 5.1-BETA2 for testing. The following message is displayed. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code