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

2019-10-13 Thread Tom Jones
On Mon, Sep 16, 2019 at 01:24:12PM +0200, Niclas Zeising wrote:
> 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 wowking with core i7-4500U on r352239 (1300047).
> > 
> 
> Hi!
> Which version of drm-current are you using?  Have you recompiled it 
> after updating the kernel?  What happens if you change to 
> kld_list="/boot/modules/i915kms.ko"?
> 
> There is a patch here: 
> https://github.com/FreeBSDDesktop/kms-drm/pull/175/commits/7b8fab2461262b22f64425146b60608bb0e0240d
>  
> that might solve the issue, can you apply that and recompile 
> drm-current-kmod and see if it works?

Hi Niclas,

I can report that the above patch fixes lock ups when loading i915kms on
my x270

- [tj]
___
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: hang up with r352239 and r352386 with i5-7500

2019-09-18 Thread Masachika ISHIZUKA
 Can you please use absolute paths to i915kms.ko anyway, just to test?
>>
  [snip]
>>
>>Now, drm-current-kmod is working fine on r352467 by your patch.
>> 
> 
> Hi!
> I just updated the port with the fix I suggested earlier, hopefully 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.g20190918 in port tree.
  Thank you very much.
-- 
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: hang up with r352239 and r352386 with i5-7500

2019-09-18 Thread Niclas Zeising

On 2019-09-18 10:15, 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.

   kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko"
will hang as well.

/boot/modules/{drm,i915kms}.ko is patched modules.

# /boot/kernel.r352239/{drm,i915kms}.ko is not patched.


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 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.
   The reason why it didn't work was because the patch was applied
to the wrong file.

   Now, drm-current-kmod is working fine on r352467 by your patch.



Hi!
I just updated the port with the fix I suggested earlier, hopefully 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.

Regards
--
Niclas Zeising
___
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: hang up with r352239 and r352386 with i5-7500

2019-09-18 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.
>>> >> 
>>> > 
>>> > Even after applying the patch I suggested?
>>> 
>>>   Yes.
>>> 
>>>   kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko"
>>> will hang as well.
>>> 
>>> /boot/modules/{drm,i915kms}.ko is patched modules.
>>> 
>>> # /boot/kernel.r352239/{drm,i915kms}.ko is not patched.
>> 
>> 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 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.
  The reason why it didn't work was because the patch was applied
to the wrong file.

  Now, drm-current-kmod is working fine on r352467 by your patch.
-- 
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: hang up with r352239 and r352386 with i5-7500

2019-09-17 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.
>> >> 
>> > 
>> > Even after applying the patch I suggested?
>> 
>>   Yes.
>> 
>>   kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko"
>> will hang as well.
>> 
>> /boot/modules/{drm,i915kms}.ko is patched modules.
>> 
>> # /boot/kernel.r352239/{drm,i915kms}.ko is not patched.
> 
> 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 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.
-- 
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: hang up with r352239 and r352386 with i5-7500

2019-09-17 Thread Mark Johnston
On Tue, Sep 17, 2019 at 07:20:41AM +0900, Masachika ISHIZUKA wrote:
> > 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.
> 
>   kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko"
> will hang as well.
> 
> /boot/modules/{drm,i915kms}.ko is patched modules.
> 
> # /boot/kernel.r352239/{drm,i915kms}.ko is not patched.

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 failure; having the
vmcore would help us debug.
___
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: 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.

  kld_list="/boot/modules/drm.ko /boot/modules/i915kms.ko"
will hang as well.

/boot/modules/{drm,i915kms}.ko is patched modules.

# /boot/kernel.r352239/{drm,i915kms}.ko is not patched.
-- 
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: 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
___
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: 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://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


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.
What happens if you add drm2.ko and/or switch to absolute paths?

This is what I had to put in my /etc/rc.conf for a Dell Latitude
E5530 to get rid of the message of drm2 being deprecated:

kld_list="/boot/modules/drm2.ko /boot/modules/i915kms.ko"


   Hi.

   Thank you for mail.
   I'm using 13-current and it has no longer drm2.ko.
   This machine was working good on r351728 as follows.
   
r351728% kldstat

Id Refs AddressSize Name
  1   90 0x8020  2336bb0 kernel
  21 0x82537000 7278 ums.ko
  31 0x82ef9000 aa70 tmpfs.ko
  41 0x82f04000 4fb8 linprocfs.ko
  54 0x82f09000 3d70 linux_common.ko
  61 0x82f0d000 24fe linsysfs.ko
  71 0x82f1   12eb90 i915kms.ko
  81 0x8303f00077e90 drm.ko
  94 0x830b7000125f0 linuxkpi.ko
102 0x830ca00013f30 linuxkpi_gplv2.ko
112 0x830de000  8e0 lindebugfs.ko
121 0x830df000 240d i915_kbl_dmc_ver1_04_bin.ko
131 0x830e2000 a218 if_lagg.ko
141 0x830ed000 3f00 ng_ubt.ko
156 0x830f1000 a998 netgraph.ko
162 0x830fc000 9378 ng_hci.ko
173 0x83106000  9c0 ng_bluetooth.ko
181 0x83107000 c890 snd_uaudio.ko
191 0x83114000 1840 uhid.ko
201 0x83116000 1b00 wmt.ko
211 0x83118000 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 autofs.ko
281 0x831e1000  acf mac_ntpd.ko




Hi!
Can you please use absolute paths to i915kms.ko anyway, just to test?
Thanks!
Regards
--
Niclas Zeising
___
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: 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 and/or switch to absolute paths?
> 
> This is what I had to put in my /etc/rc.conf for a Dell Latitude 
> E5530 to get rid of the message of drm2 being deprecated:
> 
> kld_list="/boot/modules/drm2.ko /boot/modules/i915kms.ko"

  Hi.

  Thank you for mail.
  I'm using 13-current and it has no longer drm2.ko.
  This machine was working good on r351728 as follows.
  
r351728% kldstat
Id Refs AddressSize Name
 1   90 0x8020  2336bb0 kernel
 21 0x82537000 7278 ums.ko
 31 0x82ef9000 aa70 tmpfs.ko
 41 0x82f04000 4fb8 linprocfs.ko
 54 0x82f09000 3d70 linux_common.ko
 61 0x82f0d000 24fe linsysfs.ko
 71 0x82f1   12eb90 i915kms.ko
 81 0x8303f00077e90 drm.ko
 94 0x830b7000125f0 linuxkpi.ko
102 0x830ca00013f30 linuxkpi_gplv2.ko
112 0x830de000  8e0 lindebugfs.ko
121 0x830df000 240d i915_kbl_dmc_ver1_04_bin.ko
131 0x830e2000 a218 if_lagg.ko
141 0x830ed000 3f00 ng_ubt.ko
156 0x830f1000 a998 netgraph.ko
162 0x830fc000 9378 ng_hci.ko
173 0x83106000  9c0 ng_bluetooth.ko
181 0x83107000 c890 snd_uaudio.ko
191 0x83114000 1840 uhid.ko
201 0x83116000 1b00 wmt.ko
211 0x83118000 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 autofs.ko
281 0x831e1000  acf mac_ntpd.ko
-- 
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: 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 the intrusion.
What happens if you add drm2.ko and/or switch to absolute paths?

This is what I had to put in my /etc/rc.conf for a Dell Latitude 
E5530 to get rid of the message of drm2 being deprecated:

kld_list="/boot/modules/drm2.ko /boot/modules/i915kms.ko"

-- 
Trond.
___
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: 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 (1300047).
>> 
> 
> Hi!
> Which version of drm-current are you using?

 Thank you for reply.

% pkg info drm-current-kmod
drm-current-kmod-4.16.g20190828
Name   : drm-current-kmod
Version: 4.16.g20190828
Installed on   : Mon Sep  2 14:42:56 2019 JST
Origin : graphics/drm-current-kmod
Architecture   : FreeBSD:13:amd64
Prefix : /usr/local
Categories : graphics kld
Licenses   : BSD2CLAUSE, MIT, GPLv2
Maintainer : x...@freebsd.org
WWW: https://github.com/FreeBSDDesktop/kms-drm
Comment: DRM modules for the linuxkpi-based KMS components
Options:
DEBUG  : off
SOURCE : on
Annotations:
FreeBSD_version: 1300042
repo_type  : binary
repository : FreeBSD
Flat size  : 122MiB
Description:
amdgpu, i915, and radeon DRM modules for the linuxkpi-based KMS components.
Currently corresponding to Linux 4.16 DRM.
This version is for FreeBSD CURRENT.
amdgpu and radeonkms are known to fail with EFI boot.

WWW: https://github.com/FreeBSDDesktop/kms-drm

> Have you recompiled it after updating the kernel?

  No.
  
> What happens if you change to kld_list="/boot/modules/i915kms.ko"?

  The same hangup has occured.

> There is a patch here:
> https://github.com/FreeBSDDesktop/kms-drm/pull/175/commits/7b8fab2461262b22f64425146b60608bb0e0240d
> that might solve the issue, can you 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
# make
# make deinstall
# make install
# reboot

But, it hangs 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: 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 wowking with core i7-4500U on r352239 (1300047).



Hi!
Which version of drm-current are you using?  Have you recompiled it 
after updating the kernel?  What happens if you change to 
kld_list="/boot/modules/i915kms.ko"?


There is a patch here: 
https://github.com/FreeBSDDesktop/kms-drm/pull/175/commits/7b8fab2461262b22f64425146b60608bb0e0240d 
that might solve the issue, can you apply that and recompile 
drm-current-kmod and see if it works?


Thanks!
Regards
--
Niclas Zeising
___
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"


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).
-- 
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"