You are not logged in.

#1 2016-01-16 16:37:57

abraxas88
Member
From: Cosenza, Italy
Registered: 2009-12-12
Posts: 87

[Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

Hello guys, I updated a few moments ago from testing and rebooted the system to try the new kernel. At some point during the boot I get this error:

[    0.897305] Hardware name: ASUSTeK Computer Inc. G53JW/G53JW, BIOS G53JW.211 01/28/2011
[    0.897306]  0000000000000000 000000001678f531 ffff8802361bbd48 ffffffff812c8a99
[    0.897308]  ffff8802361bbd90 ffff8802361bbd80 ffffffff810771c2 ffff8802361bbe90
[    0.897310]  8000000000000163 0000000000000004 0000000000000000 0000000000000000
[    0.897312] Call Trace:
[    0.897316]  [<ffffffff812c8a99>] dump_stack+0x4b/0x72
[    0.897321]  [<ffffffff810771c2>] warn_slowpath_common+0x82/0xc0
[    0.897322]  [<ffffffff8107725c>] warn_slowpath_fmt+0x5c/0x80
[    0.897324]  [<ffffffff8106c4c1>] note_page+0x5e1/0x780
[    0.897325]  [<ffffffff8106c967>] ptdump_walk_pgd_level_core+0x307/0x450
[    0.897327]  [<ffffffff8106cae7>] ptdump_walk_pgd_level_checkwx+0x17/0x20
[    0.897329]  [<ffffffff8106278f>] mark_rodata_ro+0xef/0x100
[    0.897331]  [<ffffffff81586350>] ? rest_init+0x90/0x90
[    0.897333]  [<ffffffff8158636d>] kernel_init+0x1d/0xe0
[    0.897335]  [<ffffffff8159290f>] ret_from_fork+0x3f/0x70
[    0.897336]  [<ffffffff81586350>] ? rest_init+0x90/0x90
[    0.897337] ---[ end trace bd9ab46da7771193 ]---

and then down further in dmesg:

[    4.993006] BUG: unable to handle kernel NULL pointer dereference at 0000000000000e20
[    4.993183] IP: [<ffffffffa03d0623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    4.993355] PGD 0 
[    4.993406] Oops: 0000 [#1] PREEMPT SMP 
[    4.993503] Modules linked in: asus_laptop(+) kvm irqbypass crc32c_intel evdev joydev input_leds mousedev sparse_keymap mac_hid psmouse rtsx_pci_ms led_class serio_raw drm r8169 snd_timer pcspkr rfkill i7core_edac snd memstick edac_core input_polldev mii soundcore fjes shpchp lpc_ich thermal video button mei_me mei acpi_cpufreq tpm_tis tpm processor ac battery sch_fq_codel ip_tables x_tables ext4 crc16 mbcache jbd2 hid_generic usbhid hid sr_mod sd_mod cdrom rtsx_pci_sdmmc mmc_core atkbd libps2 ahci libahci libata scsi_mod xhci_pci ehci_pci xhci_hcd ehci_hcd rtsx_pci usbcore usb_common i8042 serio
[    4.994923] CPU: 6 PID: 253 Comm: systemd-udevd Tainted: G        W       4.4.0-3-ARCH #1
[    4.995099] Hardware name: ASUSTeK Computer Inc. G53JW/G53JW, BIOS G53JW.211 01/28/2011
[    4.995274] task: ffff880235328000 ti: ffff880235324000 task.ti: ffff880235324000
[    4.995438] RIP: 0010:[<ffffffffa03d0623>]  [<ffffffffa03d0623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    4.995662] RSP: 0018:ffff880235327a70  EFLAGS: 00010282
[    4.995778] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[    4.995934] RDX: 0000000000000000 RSI: ffffffffa03d33c0 RDI: ffff88023488dc20
[    4.996089] RBP: ffff880235327a80 R08: 0000000000000000 R09: 0000000000000124
[    4.996245] R10: ffffea0002ec6880 R11: ffff8800bb194f78 R12: ffffffffa03d1940
[    4.996401] R13: 0000000000000000 R14: ffff8800bb1947f8 R15: ffffffffa03d3220
[    4.996557] FS:  00007efda34717c0(0000) GS:ffff88023fd80000(0000) knlGS:0000000000000000
[    4.996734] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.996861] CR2: 0000000000000e20 CR3: 000000023531a000 CR4: 00000000000006e0
[    4.997014] Stack:
[    4.997058]  0000000000000000 ffffffffa03d1940 ffff880235327ac8 ffffffff8125b7bb
[    4.997238]  0000000000000000 ffff88023488dc20 ffff880235c93000 0000000000000000
[    4.997414]  0000000000000000 ffff880234e73b78 0000000000000001 ffff880235327ad8
[    4.997591] Call Trace:
[    4.997645]  [<ffffffff8125b7bb>] internal_create_group+0xbb/0x310
[    4.997777]  [<ffffffff8125ba23>] sysfs_create_group+0x13/0x20
[    4.997904]  [<ffffffffa03cfb0a>] asus_acpi_add+0x3ca/0xed0 [asus_laptop]
[    4.998053]  [<ffffffff8134c214>] acpi_device_probe+0x4f/0xf5
[    4.998178]  [<ffffffff813ec1b2>] driver_probe_device+0x222/0x4a0
[    4.998310]  [<ffffffff813ec4b4>] __driver_attach+0x84/0x90
[    4.998432]  [<ffffffff813ec430>] ? driver_probe_device+0x4a0/0x4a0
[    4.998570]  [<ffffffff813e9dec>] bus_for_each_dev+0x6c/0xc0
[    4.998692]  [<ffffffff813eb96e>] driver_attach+0x1e/0x20
[    4.998809]  [<ffffffff813eb4bb>] bus_add_driver+0x1eb/0x280
[    4.998933]  [<ffffffffa03b4000>] ? 0xffffffffa03b4000
[    4.999045]  [<ffffffff813ecdc0>] driver_register+0x60/0xe0
[    4.999167]  [<ffffffff8134c0e3>] acpi_bus_register_driver+0x3b/0x43
[    4.999306]  [<ffffffffa03b402a>] asus_laptop_init+0x2a/0x1000 [asus_laptop]
[    4.999460]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
[    4.999584]  [<ffffffff81162537>] do_init_module+0x5f/0x1e8
[    4.999706]  [<ffffffff810fcb8f>] load_module+0x219f/0x27e0
[    4.999826]  [<ffffffff810f9a80>] ? symbol_put_addr+0x50/0x50
[    4.999954]  [<ffffffff810fd31e>] SyS_init_module+0x14e/0x190
[    5.005498]  [<ffffffff815925ae>] entry_SYSCALL_64_fastpath+0x12/0x71
[    5.011032] Code: 48 18 3d a0 e8 e1 1c d9 e0 eb e5 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 54 53 48 8b 87 90 00 00 00 <4c> 8b a0 20 0e 00 00 0f b6 80 95 0d 00 00 84 c0 74 1a 48 81 fe 
[    5.022557] RIP  [<ffffffffa03d0623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    5.028199]  RSP <ffff880235327a70>
[    5.033828] CR2: 0000000000000e20
[    5.039357] ---[ end trace bd9ab46da7771194 ]---

It boots just fine, and it seems to be working well, except it won't let me shut down or restart the system properly. The system is the one in the signature. Thank you smile

Last edited by abraxas88 (2016-01-26 16:20:11)


Asus G53Jw-IX160V Intel Core i7 740M 1.73 GHz, 8 GB RAM DDR3 1333 MHz, nVidia GTX 460M 1.5 GB GDDR5. Arch Linux 64 bit, of course. wink

Offline

#2 2016-01-16 20:38:27

SysGhost
Member
From: Stockholm
Registered: 2012-11-09
Posts: 53

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

Today, On my Asus G1s, I got this during boot:

[    2.776484] asus_laptop: Asus Laptop Support version 0.42
[    2.777170] asus_laptop:   G1S model detected
[    2.777400] BUG: unable to handle kernel NULL pointer dereference at 0000000000000e20
[    2.778166] IP: [<ffffffffa0d8b623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    2.778880] PGD 0 
[    2.779078] Oops: 0000 [#1] PREEMPT SMP 
[    2.779479] Modules linked in: asus_laptop(+) pcc_cpufreq(-) sparse_keymap acpi_cpufreq led_class tpm_tis rfkill input_polldev tpm processor fjes video battery ac button sch_fq_codel pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) nfs lockd grace sunrpc fscache ip_tables x_tables ext4 crc16 mbcache jbd2 sd_mod atkbd libps2 nvidia(PO) ata_piix ahci libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common i8042 serio drm                                                                                                                                                                                                                   
[    2.780219] CPU: 1 PID: 255 Comm: systemd-udevd Tainted: P           O    4.4.0-3-ARCH #1
[    2.780219] Hardware name: ASUSTeK Computer Inc.         G1S                 /G1S       , BIOS 300     12/25/2007
[    2.780219] task: ffff8800ba38a580 ti: ffff88013a7e4000 task.ti: ffff88013a7e4000
[    2.780219] RIP: 0010:[<ffffffffa0d8b623>]  [<ffffffffa0d8b623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    2.780219] RSP: 0018:ffff88013a7e7a70  EFLAGS: 00010282
[    2.780219] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[    2.780219] RDX: 0000000000000000 RSI: ffffffffa0d8e3c0 RDI: ffff88013a7ea020
[    2.780219] RBP: ffff88013a7e7a80 R08: 0000000000000000 R09: 0000000000000124
[    2.780219] R10: ffffea0002eb3cc0 R11: 0000000000000011 R12: ffffffffa0d8c940
[    2.780219] R13: 0000000000000000 R14: ffff8800bade2f00 R15: ffffffffa0d8e220
[    2.780219] FS:  00007f27577967c0(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000
[    2.780219] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.780219] CR2: 0000000000000e20 CR3: 0000000139b32000 CR4: 00000000000006e0
[    2.780219] Stack:
[    2.780219]  0000000000000000 ffffffffa0d8c940 ffff88013a7e7ac8 ffffffff8125b7bb
[    2.780219]  0000000000000000 ffff88013a7ea020 ffff8800bac7c000 0000000000000000
[    2.780219]  0000000000000000 ffff8800bb2341b8 0000000000000001 ffff88013a7e7ad8
[    2.780219] Call Trace:
[    2.780219]  [<ffffffff8125b7bb>] internal_create_group+0xbb/0x310
[    2.780219]  [<ffffffff8125ba23>] sysfs_create_group+0x13/0x20
[    2.780219]  [<ffffffffa0d8ab0a>] asus_acpi_add+0x3ca/0xed0 [asus_laptop]
[    2.780219]  [<ffffffff8134c214>] acpi_device_probe+0x4f/0xf5
[    2.780219]  [<ffffffff813ec1b2>] driver_probe_device+0x222/0x4a0
[    2.780219]  [<ffffffff813ec4b4>] __driver_attach+0x84/0x90
[    2.780219]  [<ffffffff813ec430>] ? driver_probe_device+0x4a0/0x4a0
[    2.780219]  [<ffffffff813e9dec>] bus_for_each_dev+0x6c/0xc0
[    2.780219]  [<ffffffff813eb96e>] driver_attach+0x1e/0x20
[    2.780219]  [<ffffffff813eb4bb>] bus_add_driver+0x1eb/0x280
[    2.780219]  [<ffffffffa0d91000>] ? 0xffffffffa0d91000
[    2.780219]  [<ffffffff813ecdc0>] driver_register+0x60/0xe0
[    2.780219]  [<ffffffff8134c0e3>] acpi_bus_register_driver+0x3b/0x43
[    2.780219]  [<ffffffffa0d9102a>] asus_laptop_init+0x2a/0x1000 [asus_laptop]
[    2.780219]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
[    2.780219]  [<ffffffff81162537>] do_init_module+0x5f/0x1e8
[    2.780219]  [<ffffffff810fcb8f>] load_module+0x219f/0x27e0
[    2.780219]  [<ffffffff810f9a80>] ? symbol_put_addr+0x50/0x50
[    2.780219]  [<ffffffff810fd31e>] SyS_init_module+0x14e/0x190
[    2.780219]  [<ffffffff815925ae>] entry_SYSCALL_64_fastpath+0x12/0x71
[    2.780219] Code: 48 c8 d8 a0 e8 e1 6c 3d e0 eb e5 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 54 53 48 8b 87 90 00 00 00 <4c> 8b a0 20 0e 00 00 0f b6 80 95 0d 00 00 84 c0 74 1a 48 81 fe 
[    2.780219] RIP  [<ffffffffa0d8b623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    2.780219]  RSP <ffff88013a7e7a70>
[    2.780219] CR2: 0000000000000e20
[    2.810195] ---[ end trace 4defc51f15c1b03b ]---
[    2.847162] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    2.854247] thermal LNXTHERM:00: registered as thermal_zone0
[    2.854864] ACPI: Thermal Zone [THRM] (47 C)
[    2.873309] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
*snip*

...

Pretty much the same problems. System refuse to shutdown and suspend.multimedia keys also stopped working (Keys depends on asus_laptop module). Aslo have some problems with the wifi and bluetooth, but I suspect that isn't related to this, so I'll leave that out for now.
I downgraded kernel to 4.3.x to get it working again.


-"If the primates that we came from had known that someday politicians would come out of the gene pool, they'd have stayed up in the trees and written evolution off as a bad idea!"

Offline

#3 2016-01-16 21:39:59

blablo
Member
Registered: 2011-06-02
Posts: 18

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

Confirm, bug on 'asus_laptop:   M70Vm model'

dmesg log:

[    9.671361] asus_laptop: Asus Laptop Support version 0.42
[    9.671472] asus_laptop:   M70Vm model detected
[    9.680272] BUG: unable to handle kernel NULL pointer dereference at 0000000000000e20
[    9.680780] IP: [<ffffffffa0311623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    9.681121] PGD 0
[    9.681448] Oops: 0000 [#1] PREEMPT SMP
[    9.682113] Modules linked in: asus_laptop(+) snd_hwdep ip6table_filter rc_core ip6_tables snd_pcm snd_timer snd ac sparse_keymap nf_conntrack_netbios_ns soundcore rfkill nf_conntrack_broadcast input_p
olldev nf_nat_ftp nf_nat battery intel_agp video button tpm_infineon shpchp intel_gtt nf_conntrack_ftp nf_conntrack acpi_cpufreq tpm_tis tpm processor iptable_filter sch_fq_codel ip_tables x_tables sd_mod
 sr_mod cdrom atkbd libps2 ahci libahci firewire_ohci libata sdhci_pci sdhci led_class scsi_mod mmc_core firewire_core crc_itu_t i8042 serio ehci_pci uhci_hcd ehci_hcd usbcore usb_common ext4 crc16 mbcach
e jbd2
[    9.683527] CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 4.4.0-3-ARCH #1
[    9.683527] Hardware name: ASUSTeK Computer Inc.         M70Vm               /M70Vm     , BIOS 210     04/22/2009
[    9.683527] task: ffff8800bacc5780 ti: ffff8800bb3d8000 task.ti: ffff8800bb3d8000
[    9.683527] RIP: 0010:[<ffffffffa0311623>]  [<ffffffffa0311623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]
[    9.683527] RSP: 0018:ffff8800bb3dba70  EFLAGS: 00010282
[    9.683527] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[    9.683527] RDX: 0000000000000000 RSI: ffffffffa03143c0 RDI: ffff88013a74fc20
[    9.683527] RBP: ffff8800bb3dba80 R08: 0000000000000000 R09: 0000000000000124
[    9.683527] R10: ffffea0002eccc80 R11: 0000000000000011 R12: ffffffffa0312940
[    9.683527] R13: 0000000000000000 R14: ffff8800bb3322d0 R15: ffffffffa0314220
[    9.683527] FS:  00007f24ae6d77c0(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000
[    9.683527] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    9.683527] CR2: 0000000000000e20 CR3: 00000000bb5e1000 CR4: 00000000000006e0
[    9.683527] Stack:
[    9.683527]  0000000000000000 ffffffffa0312940 ffff8800bb3dbac8 ffffffff8125b7bb
[    9.683527]  0000000000000000 ffff88013a74fc20 ffff88013a248000 0000000000000000
[    9.683527]  0000000000000000 ffff8800baa2c2f8 0000000000000001 ffff8800bb3dbad8
[    9.683527] Call Trace:
[    9.683527]  [<ffffffff8125b7bb>] internal_create_group+0xbb/0x310
[    9.683527]  [<ffffffff8125ba23>] sysfs_create_group+0x13/0x20
[    9.683527]  [<ffffffffa0310b0a>] asus_acpi_add+0x3ca/0xed0 [asus_laptop]
[    9.683527]  [<ffffffff8134c214>] acpi_device_probe+0x4f/0xf5
[    9.683527]  [<ffffffff813ec1b2>] driver_probe_device+0x222/0x4a0
[    9.683527]  [<ffffffff813ec4b4>] __driver_attach+0x84/0x90
[    9.683527]  [<ffffffff813ec430>] ? driver_probe_device+0x4a0/0x4a0
[    9.683527]  [<ffffffff813e9dec>] bus_for_each_dev+0x6c/0xc0
[    9.683527]  [<ffffffff813eb96e>] driver_attach+0x1e/0x20
[    9.683527]  [<ffffffff813eb4bb>] bus_add_driver+0x1eb/0x280
[    9.683527]  [<ffffffffa0317000>] ? 0xffffffffa0317000
[    9.683527]  [<ffffffff813ecdc0>] driver_register+0x60/0xe0
[    9.683527]  [<ffffffff8134c0e3>] acpi_bus_register_driver+0x3b/0x43
[    9.683527]  [<ffffffffa031702a>] asus_laptop_init+0x2a/0x1000 [asus_laptop]
[    9.683527]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
[    9.683527]  [<ffffffff81162537>] do_init_module+0x5f/0x1e8
[    9.683527]  [<ffffffff810fcb8f>] load_module+0x219f/0x27e0
[    9.683527]  [<ffffffff810f9a80>] ? symbol_put_addr+0x50/0x50
[    9.683527]  [<ffffffff810fd31e>] SyS_init_module+0x14e/0x190
[    9.683527]  [<ffffffff815925ae>] entry_SYSCALL_64_fastpath+0x12/0x71
[    9.683527] Code: 48 28 31 a0 e8 e1 0c e5 e0 eb e5 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 54 53 48 8b 87 90 00 00 00 <4c> 8b a0 20 0e 00 00 0f b6 80 95 0d 00 00 84 c0 74 1
a 48 81 fe
[    9.683527] RIP  [<ffffffffa0311623>] asus_sysfs_is_visible+0x13/0x1d0 [asus_laptop]

Last edited by blablo (2016-01-16 22:27:16)

Offline

#4 2016-01-16 22:46:14

Namarrgon
Member
Registered: 2010-03-17
Posts: 8

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=110751

The second comment links to a patch that mitigates the NULL dereference.

Offline

#5 2016-01-17 01:17:28

blablo
Member
Registered: 2011-06-02
Posts: 18

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

@Namarrgon  Thanks for the link

Tested : boot, reboot,  shutdown, keys
https://patchwork.ozlabs.org/patch/552082/ - fixes the issue for me

dmesg:

[    9.857650] asus_laptop: Asus Laptop Support version 0.42
[    9.857748] asus_laptop:   M70Vm model detected
[    9.867526] input: Asus Laptop extra buttons as /devices/platform/asus_laptop/input/input15
[    9.930051] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000084F (\PMIO) (20150930/utaddress-254)
[    9.930058] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.930062] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20150930/utaddress-254)
[    9.930066] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.930068] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20150930/utaddress-254)
[    9.930072] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.930073] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   10.118115] Intel(R) Wireless WiFi driver for Linux
[   10.118120] Copyright(c) 2003- 2015 Intel Corporation
[   10.118280] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[   10.613075] r592: driver successfully loaded
[   10.761074] media: Linux media interface: v0.10
[   10.771304] r852: driver loaded successfully
[   10.777587] Linux video capture interface: v2.00

Last edited by blablo (2016-01-17 10:37:38)

Offline

#6 2016-01-17 12:18:25

abraxas88
Member
From: Cosenza, Italy
Registered: 2009-12-12
Posts: 87

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

Agreed. It seems to be working. Should I mark it as solved, though?


Asus G53Jw-IX160V Intel Core i7 740M 1.73 GHz, 8 GB RAM DDR3 1333 MHz, nVidia GTX 460M 1.5 GB GDDR5. Arch Linux 64 bit, of course. wink

Offline

#7 2016-01-17 15:28:22

SysGhost
Member
From: Stockholm
Registered: 2012-11-09
Posts: 53

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

abraxas88 wrote:

Agreed. It seems to be working. Should I mark it as solved, though?

In my opinion, this problem isn't solved until the patch has been accepted and integrated with official sources... but that's me though.

EDIT:
I've also took the opportunity to report the bug:
https://bugs.archlinux.org/index.php?do … k_id=47805

Last edited by SysGhost (2016-01-17 17:50:43)


-"If the primates that we came from had known that someday politicians would come out of the gene pool, they'd have stayed up in the trees and written evolution off as a bad idea!"

Offline

#8 2016-01-18 10:35:37

abraxas88
Member
From: Cosenza, Italy
Registered: 2009-12-12
Posts: 87

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

SysGhost wrote:

In my opinion, this problem isn't solved until the patch has been accepted and integrated with official sources... but that's me though.

EDIT:
I've also took the opportunity to report the bug:
https://bugs.archlinux.org/index.php?do … k_id=47805

I agree with you, I shall follow your advice smile


Asus G53Jw-IX160V Intel Core i7 740M 1.73 GHz, 8 GB RAM DDR3 1333 MHz, nVidia GTX 460M 1.5 GB GDDR5. Arch Linux 64 bit, of course. wink

Offline

#9 2016-01-19 23:50:41

blablo
Member
Registered: 2011-06-02
Posts: 18

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

Offline

#10 2016-01-26 16:20:52

abraxas88
Member
From: Cosenza, Italy
Registered: 2009-12-12
Posts: 87

Re: [Solved] Kernel panic on Linux 4.4.0 prevents from shutdown

Solved with the latest 4.4.0-4 kernel update.


Asus G53Jw-IX160V Intel Core i7 740M 1.73 GHz, 8 GB RAM DDR3 1333 MHz, nVidia GTX 460M 1.5 GB GDDR5. Arch Linux 64 bit, of course. wink

Offline

Board footer

Powered by FluxBB