[Kernel-packages] [Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
OMG! Has anyone besides the OP reproduced the issue on these drives? I'm not even sure that his FS corruption, in this particular instance, is because of the hardware layer: The Original Poster (Ritesh), states in post #31 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/comments/31) that he is using an encryption layer below EXT4 for the root partition. It is totally NOT recommended to use TRIM or DISCARD together with a software encryption level solution, and it might be causing the problems that the OP encountered. The ext4 errors problems are easy to explain (fs corruption due to messing with "empty space" on which the encryption solution relied). The read error problems, could also be easily explained: a corrupted filesystem which has corrupted pointers to invalid regions of the disk, will provoke ata read errors. All this is because the encryption layer might store internal info on more blocks than the EXT4 fs reports. Fstrim/discard only looks at used blocks from the EXT4 filesystem's perspective. The result is that one could end up trimming a block used by LUKS (dm-crypt), and corrupt a little or a lot of data, depending on luck. (unless luks/dm-crypt guarantees that all used blocks are also mapped by EXT4). Cheers, Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Triaged Bug description: fs goes into read-only mode while building LibreOffice. WORKAROUND: Disable discard option - /dev/mapper/volumegroup-root/ ext4discard,noatime,nodiratime,errors=remount-ro01 disabling ncq has no effect. $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.0
[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
Breaking News! A fix in the form of a kernel patch has now been posted to the linux- acpi and linux-kernel mailing list: "[PATCH v2] ACPI / EC: Clear stale EC events on Samsung systems" http://marc.info/?l=linux-acpi&m=139359680828880&w=2 That kernel patch was made by Kieran Clancy and tested by me and others. -- Juan Manuel Cabo http://zenstep.com.ar/samsung-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. OR: 1) echo disable > /sys/firmware/acpi/interrupts/gpe17 2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) 3) echo enable > /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. WORKAROUND (kernel patch 1): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 BETTER WORKAROUND (kernel patch 2): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1283589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 971061] Re: acpi reports battery state incorrectly
Breaking News! A fix in the form of a kernel patch has now been posted to the linux- acpi and linux-kernel mailing list: "[PATCH v2] ACPI / EC: Clear stale EC events on Samsung systems" http://marc.info/?l=linux-acpi&m=139359680828880&w=2 That kernel patch was made by Kieran Clancy and tested by me and others. -- Juan Manuel Cabo http://zenstep.com.ar/samsung-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly Status in “linux” package in Ubuntu: Won't Fix Bug description: I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. Here is output from "acpitool -a -b" in various situations: When booted with charger connected and charger is still connected: Battery #1 : charging, 47.00%, 01:00:43 AC adapter : on-line When booted with charger connected and charger is now disconnected: Battery #1 : charging, 47.00%, 01:36:59 AC adapter : off-line [The battery couldn't possibly be charging when the AC adapter is offline!] When booted with charger disconnected and charger is still disconnected: Battery #1 : discharging, 47.00%, 01:39:44 AC adapter : off-line When booted with charger disconnected and charger is now connected: Battery #1 : discharging, 47.00%, 00:53:43 AC adapter : on-line [The battery is actually charging as the AC adapter is online] The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. So the state is the only thing that is incorrect. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. "lshal -m" doesn't report anything when I plug the charger in or out. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 22:50:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
Joseph: The best kernel patch so far was made by Kieran Clancy (see post #18 here). His patch is attached to a kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=44161 in comment 149. I'm just the author of the userspace workaround (post #3, #4, #14) that started it all (see the other issue here https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061 comments 102 onwards) . It is a standalone program that unstucks the EC. On the other hand, Kieran's kernel patch now does the same in a cleaner way from inside the kernel. In my humble opinion, Kieran Clancy's patch can be included in the kernel. I don't know whether Kieran will submit it. Cheers! -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore Status in “linux” package in Ubuntu: Triaged Bug description: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. OR: 1) echo disable > /sys/firmware/acpi/interrupts/gpe17 2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) 3) echo enable > /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. WORKAROUND (kernel patch 1): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 BETTER WORKAROUND (kernel patch 2): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- Mailing list: https://launchpad.net/~kern
[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
> Many thanks juanmanuel for identifying the cause for this long running issue and for working diligently to find the fix. You're welcome, it fills me with joy reading all this good feedback!! -- Juan Manuel Cabo http://zenstep.com.ar/samsung-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore Status in “linux” package in Ubuntu: Confirmed Bug description: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. OR: 1) echo disable > /sys/firmware/acpi/interrupts/gpe17 2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) 3) echo enable > /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. WORKAROUND (kernel patch 1): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 BETTER WORKAROUND (kernel patch 2): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
This is a NEW and BETTER patch created by Kieran Clancy on the kernel bugzilla to do the same that my workaround did, but in a more proper way, and from the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 I also tested it this weekend, and it works (I forced the issue to happen again, and then saw it being resolved automatically by a kernel compiled with this patch). The most salient advantage over the previous patch is that it also unstucks the EC when the computer starts (in addition to sleep resume). This is more fool proof and suits more use cases. It also checks the laptop model. Lets hope more people test this patch so that it can be included some day in the kernel. ** Patch added: "BETTER_ec_kernel_patch.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3994501/+files/BETTER_ec_kernel_patch.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore Status in “linux” package in Ubuntu: Confirmed Bug description: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. OR: 1) echo disable > /sys/firmware/acpi/interrupts/gpe17 2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) 3) echo enable > /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. WORKAROUND (kernel patch 1): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 BETTER WORKAROUND (kernel patch 2): https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSU
[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
** Description changed: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. - 4) echo disable > /sys/firmware/acpi/interrupts/gpe17 - plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) - echo enable > /sys/firmware/acpi/interrupts/gpe17 + + OR: + 1) echo disable > /sys/firmware/acpi/interrupts/gpe17 + 2) plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) + 3) echo enable > /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. - WORKAROUND: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 . + WORKAROUND (kernel patch 1): + https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 + + BETTER WORKAROUND (kernel patch 2): + https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore Status in “linux” package in Ubuntu: Confirmed Bug description: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accum
[Kernel-packages] [Bug 971061] Re: acpi reports battery state incorrectly
UPDATED v2: Safer because it obtains the EC ports automatically from /proc/ioports, and it micro-pauses between queries, so that the EC returns each event only once. This replaces the little program in #3. This is the program I made, that "unstucks" the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. ** Attachment added: "samsung_fix_ec_events_v2.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+attachment/3993277/+files/samsung_fix_ec_events_v2.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly Status in “linux” package in Ubuntu: Won't Fix Bug description: I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. Here is output from "acpitool -a -b" in various situations: When booted with charger connected and charger is still connected: Battery #1 : charging, 47.00%, 01:00:43 AC adapter : on-line When booted with charger connected and charger is now disconnected: Battery #1 : charging, 47.00%, 01:36:59 AC adapter : off-line [The battery couldn't possibly be charging when the AC adapter is offline!] When booted with charger disconnected and charger is still disconnected: Battery #1 : discharging, 47.00%, 01:39:44 AC adapter : off-line When booted with charger disconnected and charger is now connected: Battery #1 : discharging, 47.00%, 00:53:43 AC adapter : on-line [The battery is actually charging as the AC adapter is online] The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. So the state is the only thing that is incorrect. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. "lshal -m" doesn't report anything when I plug the charger in or out. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 22:50:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
UPDATED v2: Safer because it obtains the EC ports automatically from /proc/ioports, and it micro-pauses between queries, so that the EC returns each event only once. This replaces the little program in #3. This is the program I made, that "unstucks" the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. ** Attachment added: "samsung_fix_ec_events_v2.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3993249/+files/samsung_fix_ec_events_v2.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore Status in “linux” package in Ubuntu: Confirmed Bug description: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. 4) echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. WORKAROUND: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : http
[Kernel-packages] [Bug 1283589] Re: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore
Christopher: you changed my description of the bug, and in doing so, confused the two different ways to force the issue to show up. You listed the second way as a fourth item of the first way, when it is a different way. Take a look at the original description. -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: [Samsung NP530U3C-A01] LID close, AC, and battery status events not produced anymore Status in “linux” package in Ubuntu: Confirmed Bug description: On my Samsung Series 5 NP530U3C-A01 the LID close, AC, and battery status events not produced anymore. The situation is the same (tested with trusty-desktop-amd64.iso 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. The issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. 4) echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 WORKAROUND: Turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. WORKAROUND: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 971061] Re: acpi reports battery state incorrectly
I also wanted to put all the info in one place, so I made this blog here: http://www.zenstep.com.ar/samsung-linux Cheers -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly Status in “linux” package in Ubuntu: Won't Fix Bug description: I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. Here is output from "acpitool -a -b" in various situations: When booted with charger connected and charger is still connected: Battery #1 : charging, 47.00%, 01:00:43 AC adapter : on-line When booted with charger connected and charger is now disconnected: Battery #1 : charging, 47.00%, 01:36:59 AC adapter : off-line [The battery couldn't possibly be charging when the AC adapter is offline!] When booted with charger disconnected and charger is still disconnected: Battery #1 : discharging, 47.00%, 01:39:44 AC adapter : off-line When booted with charger disconnected and charger is now connected: Battery #1 : discharging, 47.00%, 00:53:43 AC adapter : on-line [The battery is actually charging as the AC adapter is online] The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. So the state is the only thing that is incorrect. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. "lshal -m" doesn't report anything when I plug the charger in or out. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 22:50:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
More description about this issue found I posted in blog format here: http://www.zenstep.com.ar/samsung-laptop -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. Status in “linux” package in Ubuntu: Confirmed Bug description: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session da
[Kernel-packages] [Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
(sorry, the link is: http://www.zenstep.com.ar/samsung-linux ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. Status in “linux” package in Ubuntu: Confirmed Bug description: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-gene
[Kernel-packages] [Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
This is a patch created by Lan Tianyu on the kernel bugzilla to do the same that my workaround did, but in a more proper way, and from the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 I tested it: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 and it works. Lets hope more people test this patch so that it can be included some day in the kernel. ** Bug watch added: Linux Kernel Bug Tracker #44161 http://bugzilla.kernel.org/show_bug.cgi?id=44161 ** Patch added: "ec_kernel_patch.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992108/+files/ec_kernel_patch.patch ** Description changed: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061 + + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom
[Kernel-packages] [Bug 971061] Re: acpi reports battery state incorrectly
Christopher: I created the new issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589 -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly Status in “linux” package in Ubuntu: Won't Fix Bug description: I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. Here is output from "acpitool -a -b" in various situations: When booted with charger connected and charger is still connected: Battery #1 : charging, 47.00%, 01:00:43 AC adapter : on-line When booted with charger connected and charger is now disconnected: Battery #1 : charging, 47.00%, 01:36:59 AC adapter : off-line [The battery couldn't possibly be charging when the AC adapter is offline!] When booted with charger disconnected and charger is still disconnected: Battery #1 : discharging, 47.00%, 01:39:44 AC adapter : off-line When booted with charger disconnected and charger is now connected: Battery #1 : discharging, 47.00%, 00:53:43 AC adapter : on-line [The battery is actually charging as the AC adapter is online] The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. So the state is the only thing that is incorrect. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. "lshal -m" doesn't report anything when I plug the charger in or out. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 22:50:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
This is the program I made, that "unstucks" the computer so that it can send LID and AC and Battery events again. (it queries the embedded controller queued events, thus unblocking the EC so that it can start sending them again). Ideally run after resume from sleep, or at any other time. ** Attachment added: "samsung_fix_ec_events.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992106/+files/samsung_fix_ec_events.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. Status in “linux” package in Ubuntu: Confirmed Bug description: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: i
[Kernel-packages] [Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
Script that calls the program found in the other attachment after resume from sleep. ** Attachment added: "99samsung_fix_ec_events" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992107/+files/99samsung_fix_ec_events -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. Status in “linux” package in Ubuntu: Confirmed Bug description: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio
[Kernel-packages] [Bug 1283589] Re: LID close and AC and battery status events not produced anymore on samsung ultrabook.
Attached DSDT of a Samsung Series 5 NP530U3C ultrabook with the same problem. Bios version is latest: P14AAJ ** Attachment added: "DSDT_SamsungSeries5-NP530U3c-AB1_WithBios_P14AAJ.dsl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589/+attachment/3992105/+files/DSDT_SamsungSeries5-NP530U3c-AB1_WithBios_P14AAJ.dsl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1283589 Title: LID close and AC and battery status events not produced anymore on samsung ultrabook. Status in “linux” package in Ubuntu: Confirmed Bug description: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi Pu
[Kernel-packages] [Bug 1283589] [NEW] LID close and AC and battery status events not produced anymore on samsung ultrabook.
Public bug reported: LID close and AC and battery status events not produced anymore on samsung ultrabook. I have a Samsung Series 5 NP530U3C-A01 ultrabook. This is an old issue with a new workaround fix. I just posted here to give information for my computer, and to confirm that I've tested with the latest ubuntu and the situation is the same (tested with trusty- desktop-amd64.iso from http://cdimage.ubuntu.com/daily-live/current/ the ISO is dated 2014-02-22). I created a blog post where I can put all the information related to this bug here: http://zenstep.com.ar/samsung-linux/ In summary, after a suspend sleep with many events (8 plug/unplug, or battery dropping or increasing about 16%, maybe less), the Embedded Controller accumulates those events and stops producing GPE 0x17. Neither Windows nor Linux query those accumulated events, because the EC doesn't produce GPE 0x17 anymore. CHICKEN AND EGG SITUATION :-) THe issue persists between restarts and shutdowns, and even after re-suspending/re-resuming. Hitting the reset button through the hole in the back fixes the problem temporarily. That is, until the next unlucky suspend. IMPORTANT: if the laptop is never ever suspended, the issue never comes back. I diagnosed the issue and made a workaround fix, posted first to this launchpad issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 Also see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/100 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c129 To force the issue to happen, you can either: 1) Sleep the computer in linux (by closing the lid or any other means). 2) Unplug from the wall, plug, unplug, plug, unplug, plug, unplug, plug (8 actions or more). 3) Resume from sleep. You'll note that the battery icon is fixed, and unplugging or plugging doesn't update battery status anymore. Also note that the ability to suspend by closing the LID is lost. or: echo disable > /sys/firmware/acpi/interrupts/gpe17 plug, unplug, plug, unplug, plug, unplug, plug, unplug (8 actions) echo enable > /sys/firmware/acpi/interrupts/gpe17 To bring back the normal behaviour, I can: turn off the computer, unplug it, hit the reset button in the back of the laptop, and then plug it again. Another way to bring back the normal behavior, is to force query the accumulated events in the Embedded Controller. That is what my little C program does, and I offered it as a workaround here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/102 >From the feedback I gathered, the following samsung models are affected and can be fixed by querying the EC: Samsung Series 5 (models NP530U3C, NP535U3C, NP530U3B, NP550P5C) Samsung Series 9 (models NP900X3F, NP900X4B, NP900X4C, NP900X4D, NP900X3C) which are roughly series 5 and series 9 from 2011 and 2012. This issue has been frustrating us users for years. A kernel patch has been made here, based on my research, by Lan Tianyu: https://bugzilla.kernel.org/show_bug.cgi?id=44161#c133 https://bugzilla.kernel.org/show_bug.cgi?id=44161#c135 The patch properly queries the EC properly after resume from sleep, instead of my original quick and dirty approach. I tested it myself and it works. I hope it gets included some day in the kernel, so that non-tech saavy people can benefit too. -- Juan Manuel Cabo ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-11-generic 3.13.0-11.31 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2546 F pulseaudio CasperVersion: 1.337 Date: Sat Feb 22 22:57:34 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-11-generic N/A linux-backports-modules-3.13.0-11-generic N/A linux-firmware 1.125 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias:
[Kernel-packages] [Bug 971061] Re: acpi reports battery state incorrectly
> If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . I downloaded trusty-desktop-amd64.isofrom that link, and tested with my Series 5 NP530U3C, and the issue still persist in the latest ubuntu. So, latest ubuntu is the same. Here is what I did: 1) Downloaded ISO image 2) Put it in a 2GB pendrive using 'unetbootin' to transfer it there. 3) Booted up, selected "Try ubuntu without installing". 4) Started acpi_listen, I see that plugging and unplugging are recognized as events. 5) Suspended the laptop by closing the lid. 6) Unplugged, plugged, unplugged. (8 actions or more) while suspended. 7) Resumed from sleep. 8) > Now events are NOT produced anymore and the laptop got into "problem state". < Closing the lid doesn't suspend the laptop. The battery icon says charging even though the ultrabook is unplugged from the wall. No surprise there. Still UNFIXED in latest ubuntu (the ISO file has a date of 2014-02-22 in that download site). Another way to get the laptop into "problem state" would be to let it discharge or charge by 16% while suspended in S3 sleep. Christopher: Should I file a new bug report? -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly Status in “linux” package in Ubuntu: Won't Fix Bug description: I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. Here is output from "acpitool -a -b" in various situations: When booted with charger connected and charger is still connected: Battery #1 : charging, 47.00%, 01:00:43 AC adapter : on-line When booted with charger connected and charger is now disconnected: Battery #1 : charging, 47.00%, 01:36:59 AC adapter : off-line [The battery couldn't possibly be charging when the AC adapter is offline!] When booted with charger disconnected and charger is still disconnected: Battery #1 : discharging, 47.00%, 01:39:44 AC adapter : off-line When booted with charger disconnected and charger is now connected: Battery #1 : discharging, 47.00%, 00:53:43 AC adapter : on-line [The battery is actually charging as the AC adapter is online] The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. So the state is the only thing that is incorrect. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. "lshal -m" doesn't report anything when I plug the charger in or out. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 22:50:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 971061] Re: acpi reports battery state incorrectly
I'm sorry, yes, its not a bug in the userspace acpi program, rather a problem that can be fixed by the kernel ACPI or a userspace workaround (post #103). Cheers -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly Status in Linux ACPI client: Incomplete Status in “linux” package in Ubuntu: Confirmed Bug description: I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. Here is output from "acpitool -a -b" in various situations: When booted with charger connected and charger is still connected: Battery #1 : charging, 47.00%, 01:00:43 AC adapter : on-line When booted with charger connected and charger is now disconnected: Battery #1 : charging, 47.00%, 01:36:59 AC adapter : off-line [The battery couldn't possibly be charging when the AC adapter is offline!] When booted with charger disconnected and charger is still disconnected: Battery #1 : discharging, 47.00%, 01:39:44 AC adapter : off-line When booted with charger disconnected and charger is now connected: Battery #1 : discharging, 47.00%, 00:53:43 AC adapter : on-line [The battery is actually charging as the AC adapter is online] The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. So the state is the only thing that is incorrect. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. "lshal -m" doesn't report anything when I plug the charger in or out. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 22:50:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 971061] Re: acpi reports battery state incorrectly
> This is not a bug in acpi (Ubuntu) as this is just a software package that > displays > information. Instead, this would be a bug in the linux kernel (ex. > samsung-laptop.c) > for not handling the laptop lid logic correctly. No, you are confounding two issues. This is a buggy behaviour in samsung's EC embedded controller when going to sleep and resuming, that can only be fixed in linux kernel ACPI handling of it ( /drivers/acpi/ec.c ). There is a patch ready in the kernel bugzilla, that adds a few lines to "acpi/ec.c", that I personally tested and confirmed that does the same as my userspace workaround (unstuck the samsung ACPI embedded controller): https://bugzilla.kernel.org/show_bug.cgi?id=44161 (comments 133 and 135) samsung-laptop.c has nothing to do with ACPI or the LID detection or this bug. samsung-laptop.c uses a SABI interface. The reason samsung-laptop.c came up, was because that file disables keyboard backlight under certain conditions, and some people said that now that the LID and AC status works with my fix, that now keyboard backlight was the only thing missing for linux compatibility. I just brought up samsung-laptop.c to point to how to fix that last, separate, independant remaining problem of keyboard backlight. LID detection and AC status detection, is handled by standard ACPI drivers in these laptops. So, this _is_ a bug that is fixed by patching ACPI's drivers/acpi/ec.c. (or by my userspace program that pokes two EC ports, post #103). Cheers -- Juan Manuel Cabo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/971061 Title: acpi reports battery state incorrectly Status in Linux ACPI client: Incomplete Status in “linux” package in Ubuntu: Confirmed Bug description: I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. Here is output from "acpitool -a -b" in various situations: When booted with charger connected and charger is still connected: Battery #1 : charging, 47.00%, 01:00:43 AC adapter : on-line When booted with charger connected and charger is now disconnected: Battery #1 : charging, 47.00%, 01:36:59 AC adapter : off-line [The battery couldn't possibly be charging when the AC adapter is offline!] When booted with charger disconnected and charger is still disconnected: Battery #1 : discharging, 47.00%, 01:39:44 AC adapter : off-line When booted with charger disconnected and charger is now connected: Battery #1 : discharging, 47.00%, 00:53:43 AC adapter : on-line [The battery is actually charging as the AC adapter is online] The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. So the state is the only thing that is incorrect. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. "lshal -m" doesn't report anything when I plug the charger in or out. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 22:50:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: acpi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/acpi/+bug/971061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1027368] Re: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close
For those of you with a Samsung laptop showing this problem, please see this issue: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061 in particular my last two posts. I think a kernel patch can be made to flush the events (LID, AC plug/unplug, etc) from the Embedded Controller, at resume, in the same way that I do it with my C program that I attached to that issue for Samsung laptops (and maybe others with the problem). TL;DR: If the events don't get flushed (queried), the GPE of the EC is never triggered again (chicken and egg situation), my little program queries the events and "unstucks" the EC immediatly. After that, LID and AC plugged events are reported normally. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1027368 Title: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: I've installed Ubuntu 12.04 on my wife's laptop, (a Samsung NP530U3B), all goes well except when I close the lid it does not suspend. I've checked the settings and it is set to suspend on lid close, though does not. Things I've noticed are: 1 - Clicking suspend in the power menu works fine. 2 - When I cat /proc/acpi/button/lid/LID0/state it always returns open, even when closed, (I ran a script that looped the cat then closed the lid) 3 - Running the latest Ubuntu 12.10 alpha 2 does not work either. 4 - The latest mainstream kernel 'linux-image-3.5.0-999-generic_3.5.0-999.201207190406_i386' does not work either. 5 - One odd thing was that after installing the latest bios on the laptop using Windows 7, then restarting into Ubuntu worked once, then it never worked again. I tried booting in to Windows then rebooting back in to Ubuntu to see if that is what changed something but it did not work that time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-26-generic-pae 3.2.0-26.41 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lou2512 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' Controls : 24 Simple ctrls : 11 Date: Sat Jul 21 09:37:25 2012 HibernationDevice: RESUME=UUID=3c27803e-5c58-4d5f-b649-d7357db99120 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic-pae root=UUID=36b0eced-301e-4fa8-a3e4-2c1466de4955 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-26-generic-pae N/A linux-backports-modules-3.2.0-26-generic-pae N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 08XK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 530U3BI/530U4BI/530U4BH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08XK:bd07/11/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3BI/530U4BI/530U4BH dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1027368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 89860] Re: /proc/acpi/button/lid/*/state always says "open"
For those of you with a Samsung laptop showing this problem, please see this issue: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/971061 in particular my last two posts. I think a kernel patch can be made to flush the events from the embedded controller, at resume, in the same way that I do it with my C program that I attached to that issue for Samsung laptops (and maybe others with the problem). TL;DR: If the events don't get flushed (queried), the GPE of the EC is never triggered again (chicken and egg situation), my little program queries the events and "unstucks" the EC immediatly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/89860 Title: /proc/acpi/button/lid/*/state always says "open" Status in “linux” package in Ubuntu: Won't Fix Status in “linux-source-2.6.20” package in Ubuntu: Won't Fix Status in “linux-source-2.6.22” package in Ubuntu: Won't Fix Bug description: My laptop is an HP Pavilion dv4000. I'm running up-to-date Feisty. Regardless of whether my laptop lid is open or closed, I always get this: root@peace:/etc/acpi# cat /proc/acpi/button/lid/*/state state: open This would explain why I can suspend the laptop using Gnome's power management menu, but why it doesn't do it when I close the lid. (I have specified under power management preferences that it's to suspend when I close the lid.) I know that at some level the lid switch works because when I press it the screen backlight turns off (although I can still faintly see that the display is still live). There was one hint of the issue in this email: http://lists.opensuse.org/opensuse-mobile/2007-02/msg00016.html Here's a Ubuntu bug that seems similar, but got rejected: https://launchpad.net/ubuntu/+source/kernel-package/+bug/16662 My bug is different than this one: https://launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/34389 because my laptop state is *always* reported as open. I've attached the output of dmesg and dmidecode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/89860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp