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

2019-09-16 Thread Niclas Zeising
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 patch I suggested? Regards -- Niclas Zeising

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

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

2019-09-16 Thread Niclas Zeising
On 2019-09-16 15:13, Masachika ISHIZUKA wrote: My machine (with core i5-7500) is hangup when loading i915kms.ko on r352239 and r352386 (1300047). This machine was working good with r351728 (1300044). /etc/rc.conf has the following line. kld_list="i915kms.ko" Pardon the intrusion.

Re: panic: sleeping thread on r352386

2019-09-16 Thread Alastair Hogge
On Monday, 16 September 2019 7:55:32 PM AWST Masachika ISHIZUKA wrote: > Hi. > > This panic happens on 1300047 (both r352239 and r352386) with core > i5-7500 as follows. This panic dose not happen on r351728 (1300044). > (The following lines were typed by hand so they might have some miss >

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 patch I suggested? Yes.

r352368 can't boot

2019-09-16 Thread KIRIYAMA Kazuhiko
Hi,all Yesterday I've updated latest head (r352368) and rebuild 13.0-CURRENT. All went fine, but when I boot, it's stopped at boot stage. Then I typed `boot', booted normally and put login prompt and login go ahead. But `shutdown -r now', stopped at loader prompt same as login case. What

Re: panic: sleeping thread on r352386

2019-09-16 Thread Masachika ISHIZUKA
>> This panic happens on 1300047 (both r352239 and r352386) with core >> i5-7500 as follows. This panic dose not happen on r351728 (1300044). >> (The following lines were typed by hand so they might have some miss >> typed letters.) >> >> == >> Sleeping thread (tid 100177, pid 1814) owns a

Re: r352368 can't boot

2019-09-16 Thread Toomas Soome
> On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko wrote: > > Hi,all > > Yesterday I've updated latest head (r352368) and rebuild > 13.0-CURRENT. All went fine, but when I boot, it's stopped > at boot stage. Then I typed `boot', booted normally and put > login prompt and login go ahead. But

"Sleeping with non-sleepable lock" in NFS on recent -current

2019-09-16 Thread Peter Jeremy
I'm consistently seeing panics in the NFS code on recent -current on aarm64. The panics are one of the following two: Sleeping on "vmopar" with the following non-sleepable locks held: exclusive sleep mutex NEWNFSnode lock (NEWNFSnode lock) r = 0 (0xfd0078b346f0) locked @

error message during "mergemaster"

2019-09-16 Thread M - Krasznai András
In FreeBSD 13.0 when I update the kernel and world I receive the following error message during mergemaster: ka-freebsd:/usr/src# mergemaster *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure

Re: "Sleeping with non-sleepable lock" in NFS on recent -current

2019-09-16 Thread Konstantin Belousov
On Mon, Sep 16, 2019 at 04:12:05PM +1000, Peter Jeremy wrote: > I'm consistently seeing panics in the NFS code on recent -current on aarm64. > The panics are one of the following two: > Sleeping on "vmopar" with the following non-sleepable locks held: > exclusive sleep mutex NEWNFSnode lock

Re: "Sleeping with non-sleepable lock" in NFS on recent -current

2019-09-16 Thread Peter Jeremy
On 2019-Sep-16 09:32:52 +0300, Konstantin Belousov wrote: >On Mon, Sep 16, 2019 at 04:12:05PM +1000, Peter Jeremy wrote: >> I'm consistently seeing panics in the NFS code on recent -current on aarm64. >> The panics are one of the following two: >> Sleeping on "vmopar" with the following

Re: "Sleeping with non-sleepable lock" in NFS on recent -current

2019-09-16 Thread Konstantin Belousov
On Mon, Sep 16, 2019 at 05:44:28PM +1000, Peter Jeremy wrote: > On 2019-Sep-16 09:32:52 +0300, Konstantin Belousov > wrote: > >On Mon, Sep 16, 2019 at 04:12:05PM +1000, Peter Jeremy wrote: > >> I'm consistently seeing panics in the NFS code on recent -current on > >> aarm64. > >> The panics are

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

2019-09-16 Thread Masachika ISHIZUKA
>>My machine (with core i5-7500) is hangup when loading i915kms.ko >> on r352239 and r352386 (1300047). >>This machine was working good with r351728 (1300044). >>/etc/rc.conf has the following line. >> kld_list="i915kms.ko" >>It is good wowking with core i7-4500U on r352239

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

2019-09-16 Thread Trond Endrestøl
On Mon, 16 Sep 2019 20:09+0900, Masachika ISHIZUKA wrote: > My machine (with core i5-7500) is hangup when loading i915kms.ko > on r352239 and r352386 (1300047). > This machine was working good with r351728 (1300044). > > /etc/rc.conf has the following line. > kld_list="i915kms.ko" Pardon

hang up with r352239 and r352386 with i5-7500

2019-09-16 Thread Masachika ISHIZUKA
Hi. My machine (with core i5-7500) is hangup when loading i915kms.ko on r352239 and r352386 (1300047). This machine was working good with r351728 (1300044). /etc/rc.conf has the following line. kld_list="i915kms.ko" It is good wowking with core i7-4500U on r352239 (1300047). --

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

2019-09-16 Thread Niclas Zeising
On 2019-09-16 13:09, Masachika ISHIZUKA wrote: Hi. My machine (with core i5-7500) is hangup when loading i915kms.ko on r352239 and r352386 (1300047). This machine was working good with r351728 (1300044). /etc/rc.conf has the following line. kld_list="i915kms.ko" It is good

panic: sleeping thread on r352386

2019-09-16 Thread Masachika ISHIZUKA
Hi. This panic happens on 1300047 (both r352239 and r352386) with core i5-7500 as follows. This panic dose not happen on r351728 (1300044). (The following lines were typed by hand so they might have some miss typed letters.) == Sleeping thread (tid 100177, pid 1814) owns a non-sleepable lock

Re: "Sleeping with non-sleepable lock" in NFS on recent -current

2019-09-16 Thread Peter Jeremy
On 2019-Sep-16 11:19:02 +0300, Konstantin Belousov wrote: >diff --git a/sys/fs/nfsclient/nfs_clport.c b/sys/fs/nfsclient/nfs_clport.c >index 471e029a8b5..63ea4736707 100644 ... Thanks, that patch seems much more stable. -- Peter Jeremy signature.asc Description: PGP signature

Re: svn commit: r351858 - in head: bin/uuidgen ...

2019-09-16 Thread Emmanuel Vadot
On Sat, 14 Sep 2019 19:41:06 +0200 mj-mailingl...@gmx.de wrote: > Building a jail from pkgbase packages after base r351858 shows this cap_mkdb > message: > > to create the jail this command is used: > > pkg --rootdir /jails/test01 -o 'ASSUME_ALWAYS_YES=true' -o > 'ABI=FreeBSD:13:amd64'

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

2019-09-16 Thread Masachika ISHIZUKA
>> My machine (with core i5-7500) is hangup when loading i915kms.ko >> on r352239 and r352386 (1300047). >> This machine was working good with r351728 (1300044). >> >> /etc/rc.conf has the following line. >> kld_list="i915kms.ko" > > Pardon the intrusion. > What happens if you add drm2.ko