BUG: unable to handle kernel NULL pointer dereference EIP:asus_sysfs_is_visible

[elhoir]

hello,
i have been hitting this since 4.4.0 linux kernel.
It boots fine so it doesnt make system unbootable.

I think this has something to do with the asus_laptop module (my laptop is ASUS), but im not sure.

I attach the complete dmesg output. BUG is at line 830.
---
ApportVersion: 2.19.4-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: toni 1708 F...m pulseaudio
 /dev/snd/controlC0: toni 1708 F.... pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=963bfe58-9faa-4c89-a33e-31ac1d2cee76
InstallationDate: Installed on 2015-05-28 (263 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: ASUSTeK Computer INC. K50AF
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic root=UUID=73345602-0907-43e9-91e1-883f6066e57a ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-4-generic N/A
 linux-backports-modules-4.4.0-4-generic N/A
 linux-firmware 1.155
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-4-generic i686
UpgradeStatus: Upgraded to xenial on 2015-12-13 (64 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/21/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 213
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: K50AF
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr213:bd07/21/2010:svnASUSTeKComputerINC.:pnK50AF:pvr1.0:rvnASUSTeKComputerINC.:rnK50AF:rvr1.00:cvnASUSTekComputerINC.:ct10:cvr1.0:
dmi.product.name: K50AF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer INC.

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[elhoir (jfarroyo82)]

apport information

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc4-wily/

[elhoir (jfarroyo82)]

Hello,

Yes, bug seems to have been fixed in 4.5-rc4

i dont see the BUG line in there.

[elhoir (jfarroyo82)]

mmm... how do i add tags? xD

[elhoir (jfarroyo82)]

ah ok done

[elhoir (jfarroyo82)]

and, bug is already in Confirmed status :)

[penalvch (penalvch)]

elhoir, the next step is to fully reverse commit bisect from kernel 4.4 to 4.5-rc4 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[elhoir (jfarroyo82)]

hello, sorry to say its quite hard for me to do all this procedure. I can test every single kernel release, but not every single commit....

I am very sorry about this

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]