Adding sapoliakaran to CC list.

For the record:

$ grep 'DMI:' journalctl-2.log 
Jan 11 06:24:40 kernel: DMI: ASUSTeK COMPUTER INC. GL502VMK/GL502VMK, BIOS GL502VMK.305 07/03/2017

ROG GL502VM | ROG - Republic Of Gamers | ASUS USA
https://www.asus.com/us/ROG-Republic-Of-Gamers/ROG-GL502VM/

(In reply to sapoliakaran from Bug 1663613, comment #43)
> Replying to Bug 1663613, comment #41
> ➜  ~ find /sys/devices/platform/asus-nb-wmi/ -name '*hwmon*' -o -name '*fan*'
> /sys/devices/platform/asus-nb-wmi/hwmon
> /sys/devices/platform/asus-nb-wmi/hwmon/hwmon2
> 
> Yes, it has two fans. One for the CPU and the other for the GPU.

What do you show for:

$ ls -l /sys/devices/platform/asus-nb-wmi/hwmon/hwmon2

(On my ASUS laptop, there is an "hwmon1" directory, but no "hwmon2" directory.)

Replying to comment #3
➜  ~ ls -l /sys/devices/platform/asus-nb-wmi/hwmon/hwmon2
total 0
lrwxrwxrwx. 1 root root    0 Jan 15 01:12 device -> ../../../asus-nb-wmi
-r--r--r--. 1 root root 4096 Jan 15 01:09 name
drwxr-xr-x. 2 root root    0 Jan 15 01:12 power
lrwxrwxrwx. 1 root root    0 Jan 15 01:09 subsystem -> ../../../../../class/hwmon
-rw-r--r--. 1 root root 4096 Jan 15 01:08 uevent

Replying to comment #3

➜  / ls sys/class/hwmon       
hwmon0  hwmon1  hwmon2  hwmon3  hwmon4

I see these 5 sub-drectories on mine. And their contents:

➜  / ls sys/class/hwmon/hwmon0
device  name  power  subsystem  temp1_crit  temp1_input  uevent
➜  / ls sys/class/hwmon/hwmon1
device  name  power  subsystem  temp1_input  uevent
➜  / ls sys/class/hwmon/hwmon2
device  name  power  subsystem  uevent
➜  / ls sys/class/hwmon/hwmon3
device      temp1_crit_alarm  temp2_crit_alarm  temp3_crit_alarm  temp4_crit_alarm  temp5_crit_alarm
name        temp1_input       temp2_input       temp3_input       temp4_input       temp5_input
power       temp1_label       temp2_label       temp3_label       temp4_label       temp5_label
subsystem   temp1_max         temp2_max         temp3_max         temp4_max         temp5_max
temp1_crit  temp2_crit        temp3_crit        temp4_crit        temp5_crit        uevent
➜  / ls sys/class/hwmon/hwmon4
device  name  power  subsystem  temp1_input  uevent

(In reply to sapoliakaran from comment #4)
> Replying to comment #3
> ➜  ~ ls -l /sys/devices/platform/asus-nb-wmi/hwmon/hwmon2
> total 0
> lrwxrwxrwx. 1 root root    0 Jan 15 01:12 device -> ../../../asus-nb-wmi
> -r--r--r--. 1 root root 4096 Jan 15 01:09 name
> drwxr-xr-x. 2 root root    0 Jan 15 01:12 power
> lrwxrwxrwx. 1 root root    0 Jan 15 01:09 subsystem ->
> ../../../../../class/hwmon
> -rw-r--r--. 1 root root 4096 Jan 15 01:08 uevent

Thanks. For comparison, here is what my ASUS laptop has:

$ find /sys/devices/platform/asus-nb-wmi/ -name '*hwmon*' -o -name '*fan*'
/sys/devices/platform/asus-nb-wmi/hwmon
/sys/devices/platform/asus-nb-wmi/hwmon/hwmon1
/sys/devices/platform/asus-nb-wmi/hwmon/hwmon1/fan1_label
/sys/devices/platform/asus-nb-wmi/hwmon/hwmon1/fan1_input

$ ls -l /sys/devices/platform/asus-nb-wmi/hwmon/hwmon1/
total 0
lrwxrwxrwx. 1 root root    0 Jan 14 12:01 device -> ../../../asus-nb-wmi
-r--r--r--. 1 root root 4096 Jan 14 12:01 fan1_input
-r--r--r--. 1 root root 4096 Jan 14 12:01 fan1_label
-r--r--r--. 1 root root 4096 Jan 14 12:01 name
drwxr-xr-x. 2 root root    0 Jan 14 12:01 power
-rw-r--r--. 1 root root 4096 Jan 14 12:01 pwm1
-rw-r--r--. 1 root root 4096 Jan 14 12:01 pwm1_enable
lrwxrwxrwx. 1 root root    0 Jan 14 12:01 subsystem -> ../../../../../class/hwmon
-r--r--r--. 1 root root 4096 Jan 14 12:01 temp1_input
-rw-r--r--. 1 root root 4096 Jan 14 12:01 uevent

$ uname -r
4.19.14-300.fc29.x86_64

(In reply to sapoliakaran from comment #5)
> Replying to comment #3
> 
> ➜  / ls sys/class/hwmon       
> hwmon0  hwmon1  hwmon2  hwmon3  hwmon4
...

Thanks for posting the additional directories. Those are links. What do you show for this?

$ ls -l /sys/class/hwmon

Replying to comment #7

➜  ~ ls -l /sys/class/hwmon
total 0
lrwxrwxrwx. 1 root root 0 Jan 15  2019 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
lrwxrwxrwx. 1 root root 0 Jan 15 04:03 hwmon1 -> ../../devices/virtual/thermal/thermal_zone1/hwmon1
lrwxrwxrwx. 1 root root 0 Jan 15 04:03 hwmon2 -> ../../devices/platform/asus-nb-wmi/hwmon/hwmon2
lrwxrwxrwx. 1 root root 0 Jan 15 04:03 hwmon3 -> ../../devices/platform/coretemp.0/hwmon/hwmon3
lrwxrwxrwx. 1 root root 0 Jan 15 04:03 hwmon4 -> ../../devices/virtual/thermal/thermal_zone5/hwmon4

This appears to be the same bug:

Bug 1663927 - I installed Fedora 29 to Asus X542U. Now fan is working always and I can not control it.

A quick note: I shifted from GNOME to i3, which also changed the display server from Wayland to XOrg. My Fedora laptop is dead quiet now, and the battery also lasts almost an hour and a half more. Don't know how this happened. But the continuous running fans in GNOME have stopped now. I run the same applications now as I did on GNOME then, but the difference is stark. Don't know how this helps or what the reason could be.

(In reply to sapoliakaran from comment #10)
> A quick note: I shifted from GNOME to i3, which also changed the display
> server from Wayland to XOrg. My Fedora laptop is dead quiet now, and the
> battery also lasts almost an hour and a half more. Don't know how this
> happened. But the continuous running fans in GNOME have stopped now. I run
> the same applications now as I did on GNOME then, but the difference is
> stark. Don't know how this helps or what the reason could be.

Thanks for reporting that. If you still have Gnome3 installed, could you try running it with Xorg? There is a gear icon on the GDM login screen that lets you select "GNOME on Xorg". See the screenshot here:

How to debug Wayland problems
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems

(In reply to sapoliakaran from comment #10)
> ... My Fedora laptop is dead quiet now, and the
> battery also lasts almost an hour and a half more. Don't know how this
> happened. But the continuous running fans in GNOME have stopped now.
...

The CPU or the GPU could be heavily loaded. The "top" command will show processes that are loading the CPU.

For the GPU, it might be possible to monitor its temperature with a suitable application. The "lm_sensors" package has commands to detect sensor chips and to read temperatures from them. Here is a summary:

# dnf install lm_sensors
# sensors-detect
$ sensors

The package includes documentation:

$ rpm -qd lm_sensors
...
/usr/share/man/man1/sensors.1.gz
/usr/share/man/man5/sensors.conf.5.gz
/usr/share/man/man5/sensors3.conf.5.gz
/usr/share/man/man8/fancontrol.8.gz
/usr/share/man/man8/isadump.8.gz
/usr/share/man/man8/isaset.8.gz
/usr/share/man/man8/pwmconfig.8.gz
/usr/share/man/man8/sensors-conf-convert.8.gz
/usr/share/man/man8/sensors-detect.8.gz

NB: sensors-detect may configure kernel modules to be loaded:
$ cat /etc/sysconfig/lm_sensors

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 4.20.5-200.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.