Maverick fails to wake up on Samsung N150

Bug #640100 reported by Benjamin Nave
384
This bug affects 70 people
Affects Status Importance Assigned to Milestone
Linux
Expired
Medium
Release Notes for Ubuntu
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Medium
Seth Forshee
Maverick
Won't Fix
Medium
Unassigned
Natty
Won't Fix
Medium
Seth Forshee
Oneiric
Won't Fix
Medium
Unassigned

Bug Description

== Release Notes ==
See Comment #155

Recently upgraded from 10.04LTS to 10.10 Beta on a Samsung N150 NetBook. Since update, my netbook does not resume from suspend state after lid is opened. Power, disk, and wireless activity lights turn on, but screen does not wake up. I cannot ssh into the netbook from a remote host so I do not think that the network is resuming even though the wireless light indicates that the card is on. I have to power off/on the netbook once it is hung in this state.

I've examined /var/log/messages after power cycling but I don't see any relevant errors. I would be happy to submit applicable logs or provide more information if someone could point me in the right direction.

Thanks!

== Regression details ==
Last known good version: mainline 2.6.34.7-maverick
Confirmed broken since: 2.6.35-22.34

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 Cannot stat file /proc/13903/fd/11: Stale NFS file handle
                      USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3659 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0400000 irq 47'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,144dc072,00100004'
   Controls : 11
   Simple ctrls : 7DistroRelease: Ubuntu 10.10LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150/N210/N220
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname-netbook.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4Regression: Yes
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: noTags: maverick ubuntu-une kernel-power suspend resume regression-release needs-upstream-testing
Uname: Linux 2.6.35-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/25/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 08JI.M073.20100325.JIP
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150/N210/N220
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08JI.M073.20100325.JIP:bd03/25/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150/N210/N220:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150/N210/N220:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150/N210/N220
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Philip Muškovac (yofel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.

Please run the following command which will attach necessary information:

apport-collect 640100

Bear in mind that when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you cannot use apport please at least add the following information (pay attention to lspci's additional options):
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

As you are experiencing a suspend issue, please also follow
https://wiki.ubuntu.com/DebuggingKernelSuspend

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

tags: added: maverick
affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote :

i second the problem. apport coming.

tags: added: apport-collected
Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: merlin 1450 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0400000 irq 47'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,144dc072,00100004'
   Controls : 11
   Simple ctrls : 7
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=0fbfe3f3-3a37-49ea-9767-e2a37fca2364
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150/N210/N220
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=4a510bbe-d7e2-4c8e-b426-2063d995f601 ro quiet splash usbcore.autosuspend=1 acpi_osi=Linux
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.34~ppa1~loms~maverick-generic 2.6.35.4
Regression: Yes
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
Tags: ubuntu-une maverick kernel-power suspend resume regression-potential needs-upstream-testing
Uname: Linux 2.6.35-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/25/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 08JI.M073.20100325.JIP
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150/N210/N220
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08JI.M073.20100325.JIP:bd03/25/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150/N210/N220:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150/N210/N220:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150/N210/N220
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : AcpiTables.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : AlsaDevices.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : BootDmesg.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : IwConfig.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : Lspci.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : Lsusb.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : PciMultimedia.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : ProcModules.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : RfKill.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : UdevDb.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : UdevLog.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : WifiSyslog.txt

apport information

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote :

sorry i used the samsung-tools kernel. its a patched kernel. using the default kernel the problem persists. shall i do another apport?

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote :

Same problem with my Samsung N148 Plus.

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote :

I've tested suspend to ram in Lucid. Works fine.

Revision history for this message
Philip Muškovac (yofel) wrote :

ig-88, Alexander: can you please file your own bugs about this issue? This is Alexanders bug report and he's the one that has to submit his information.

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : apport information

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mm 1533 F.... pulseaudio
CRDA: Error: [Errno 2] Нет такого файла или каталога
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0400000 irq 47'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,144dc072,00100004'
   Controls : 11
   Simple ctrls : 7
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=d48e6900-4905-4b83-a647-d3fe64bce63f
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.2)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N148P/N208P/N218P/NB28P
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=2637efc1-4986-4ace-9641-2fdb51e6b87f ro quiet splash
ProcEnviron:
 LANG=ru_UA.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.34~ppa1~loms~maverick-generic 2.6.35.4
Regression: Yes
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
Tags: maverick ubuntu-une kernel-power suspend resume regression-potential needs-upstream-testing
Uname: Linux 2.6.35-22-generic i686
UserGroups: adm admin audio cdrom dialout dip disk fax fuse lpadmin netdev nopasswdlogin plugdev sambashare tape video
dmi.bios.date: 05/03/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 00MG.M009.20100503.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N148P/N208P/N218P/NB28P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr00MG.M009.20100503.RHU:bd05/03/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN148P/N208P/N218P/NB28P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN148P/N208P/N218P/NB28P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N148P/N208P/N218P/NB28P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : AcpiTables.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : AlsaDevices.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : BootDmesg.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : IwConfig.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : Lspci.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : Lsusb.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : PciMultimedia.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : ProcModules.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : RfKill.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : UdevDb.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : UdevLog.txt

apport information

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : WifiSyslog.txt

apport information

Revision history for this message
Olof Mogren (olof-mogren) wrote :

I have the same problem. Tried the instructions at https://wiki.ubuntu.com/DebuggingKernelSuspend but does not seem to have had any luck. No hash matches.

[ 0.700379] Magic number: 14:497:297
[ 0.700568] rtc_cmos 00:04: setting system clock to 2010-10-07 21:16:44 UTC (1286486204)
[ 0.700578] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 0.700584] EDD information not available.

BR, Olof

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote : Re: [Bug 640100] Re: Maverick fails to wake up on Samsung N150
  • dmesg.txt Edit (53.2 KiB, text/plain; charset=US-ASCII; name="dmesg.txt")

My dmesg has no any hash too.

[ 0.787311] Magic number: 14:513:794
[ 0.787456] rtc_cmos 00:04: setting system clock to 2010-10-06
17:45:50 UTC (1286387150)
[ 0.787467] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 0.787472] EDD information not available.

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote :

[ 0.791493] Magic number: 14:170:963
[ 0.791637] rtc_cmos 00:04: setting system clock to 2010-10-08 01:58:42 UTC (1286503122)
[ 0.791647] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 0.791652] EDD information not available.

Revision history for this message
Benjamin Nave (bnave) wrote : AcpiTables.txt

apport information

description: updated
Revision history for this message
Benjamin Nave (bnave) wrote : AlsaDevices.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : BootDmesg.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : IwConfig.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : Lspci.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : Lsusb.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : PciMultimedia.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : ProcModules.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : UdevDb.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : UdevLog.txt

apport information

Revision history for this message
Benjamin Nave (bnave) wrote : WifiSyslog.txt

apport information

Philip Muškovac (yofel)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
ercoppa (ercoppa) wrote :

Same problem on my Samsung N150 HAZ1IT

Revision history for this message
dodo (dodvan) wrote :

Same problem here on a Samsung NB30. Should I post the apport information?

Revision history for this message
dodo (dodvan) wrote :

Following the procedure detailed at https://wiki.ubuntu.com/DebuggingKernelSuspend I found that at dmesg:

[ 0.695528] Magic number: 14:89:936
[ 0.695563] pci_express 0000:00:1c.3:pcie04: hash matches

(No more "matches" line below that one...) lspci says:

00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 02)

Which module should I disable to test if it is the "likely culprit"? Regards.

Revision history for this message
dodo (dodvan) wrote :

Ooops. This is weird. I did it once more time, and now dmesg says:

[ 0.701999] registered taskstats version 1
[ 0.702635] Magic number: 14:574:331
[ 0.702678] tty tty52: hash matches
[ 0.702778] rtc_cmos 00:04: setting system clock to 2010-10-12 13:20:53 UTC (1286889653)

?

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote :

According to some posts in the Voria (http://www.voria.org/forum/viewforum.php?f=3) it happens also on the n220.

Revision history for this message
Raúl Núñez de Arenas Coronado (dervishd) wrote :

Confirmed in a fresh 10.10 install (i386). I'm going to test with the Voria kernel but I'm afraid it won't work, either.

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote : Re: [Bug 640100] Re: Maverick fails to wake up on Samsung N150
Download full text (3.7 KiB)

Vorias kernel disables suspend.
Am 13.10.2010 11:46 schrieb "DervishD" <email address hidden>:
> Confirmed in a fresh 10.10 install (i386). I'm going to test with the
> Voria kernel but I'm afraid it won't work, either.
>
> --
> Maverick fails to wake up on Samsung N150
> https://bugs.launchpad.net/bugs/640100
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
>
> Bug description:
> Recently upgraded from 10.04LTS to 10.10 Beta on a Samsung N150 NetBook.
Since update, my netbook does not resume from suspend state after lid is
opened. Power, disk, and wireless activity lights turn on, but screen does
not wake up. I cannot ssh into the netbook from a remote host so I do not
think that the network is resuming even though the wireless light indicates
that the card is on. I have to power off/on the netbook once it is hung in
this state.
>
> I've examined /var/log/messages after power cycling but I don't see any
relevant errors. I would be happy to submit applicable logs or provide more
information if someone could point me in the right direction.
>
> Thanks!
> ---
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> AplayDevices:
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> Architecture: i386
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> Cannot stat file /proc/13903/fd/11: Stale NFS file handle
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu 3659 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf0400000 irq 47'
> Mixer name : 'Realtek ALC269'
> Components : 'HDA:10ec0269,144dc072,00100004'
> Controls : 11
> Simple ctrls : 7
> DistroRelease: Ubuntu 10.10
> LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386
(20101007)
> MachineType: SAMSUNG ELECTRONICS CO., LTD. N150/N210/N220
> Package: linux (not installed)
> ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true
persistent file=/cdrom/preseed/hostname-netbook.seed boot=casper
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Regression: Yes
> RelatedPackageVersions: linux-firmware 1.38
> Reproducible: Yes
> RfKill:
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> Tags: maverick ubuntu-une kernel-power suspend resume regression-release
needs-upstream-testing
> Uname: Linux 2.6.35-22-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> dmi.bios.date: 03/25/2010
> dmi.bios.vendor: Phoenix Technologies Ltd.
> dmi.bios.version: 08JI.M073.20100325.JIP
> dmi.board.asset.tag: SAMSUNG
> dmi.board.name: N150/N210/N220
> dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
> dmi.board.version: Not Applicable
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type:...

Read more...

Revision history for this message
Olof Mogren (olof-mogren) wrote :

The only way to use suspend/resume on my laptop was to install a Lucid kernel.

Revision history for this message
Gergan Penkov (gergan) wrote :

Yes I'm the one with N220, the lucid kernel still works, that's why it purely kernel problem. I have asked if there are some pristine kernels on ubuntu to try, as it is a hard lockup and I don't think much information could be gathered from the lock up.

Revision history for this message
ercoppa (ercoppa) wrote :

How easily can I install a lucid kernel on maverick?

Revision history for this message
Olof Mogren (olof-mogren) wrote :

Installing a Lucid kernel:

1. Download the packages for your architechture (i386 or amd64, the second header is arch independent) below.

http://packages.ubuntu.com/lucid/linux-image-2.6.32-22-generic
http://packages.ubuntu.com/lucid/linux-headers-2.6.32-22-generic
http://packages.ubuntu.com/lucid/linux-headers-2.6.32-22

2. Install them with dpkg -i or graphically (i guess double-clicking on the files would do).

Revision history for this message
Adam Kent (akent) wrote :

I am having this problem as well with my N150. Confirmed that lucid kernel 2.6.32-24-generic suspends and resumes fine.

I compiled and tested the current vanilla kernel from git.kernel.org (commit ae42d8d44195a614c78a636683fe65ed31744cbd -- 2.6.36-rc7) and the problem still occurs with this upstream version.

tags: added: kj-triage
Revision history for this message
Andrew Ferrier (andrew-ferrier) wrote :

I have a similar problem with my Samsung N210. I had to switch to voria's PPA to get screen brightness control working in 10.10, but this broke the suspend/resume in exactly the way described in this bug. This is a regression from 10.04.

Reverting to the 2.6.32 kernel from Lucid "fixed" the problem.

Revision history for this message
Wilson K (lachkater) wrote :

You can also use kernel 2.6.34 ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34.7-maverick/ )
which has longer battery life than the lucid kernel.

Revision history for this message
Andrew Ferrier (andrew-ferrier) wrote :

Thanks. Wilfried, certainly works for me - brightness control and suspend/resume are fine. Not sure if it's giving me more battery life yet - would have to test a bit more. Thanks for the heads-up, though.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Benjamin Nave (bnave) wrote :

Kernel v2.6.34-7 does not resolve the issue for me.

:-(

Revision history for this message
Benjamin Nave (bnave) wrote :

Disregard comment #77. I realized that although I had installed kernel 2.6.34-7, my system is still booting the 2.6.35 kernel. How do I switch it?

Revision history for this message
Andrew Ferrier (andrew-ferrier) wrote :

@Benjamin, "Esc" just as your machine begins to boot (post-BIOS) should bring up the Grub menu and allow you to temporarily switch kernels for one boot, to test.

To switch permanently, I just uninstalled the 2.6.35 kernel. I'm sure you can permanently change the Grub boot order though. This is probably a good place to start: https://help.ubuntu.com/community/Grub2.

Revision history for this message
Andrew Ferrier (andrew-ferrier) wrote :

Correction: it may be the "Shift" key. Double-check the Grub docs.

Revision history for this message
turbolad (turbolad995) wrote :

How do I get that version of the kernel onto the netbook to try it out?

Revision history for this message
dodo (dodvan) wrote :

Check #72.

Revision history for this message
turbolad (turbolad995) wrote :

Yes that has worked. Installing the older kernel version, as per post #72, has fixed this problem. It looks like we have a regression.

Revision history for this message
Юрий Чудновский (fqc) wrote :

I notified what suspend is successful then netbook in on line power when suspending. It comes to sleep fast and clean, and come back good both on line power and battery.
But on battery power it suspend much-much slower, video signal is lost before powering off backlight and monitor displaying color lines (its like "no signal" on external monitors), and after suspend there is no way to come back alive both on battery and line power.
On 10.04 both cases of suspend was on same behaviour.

Revision history for this message
Benjamin Nave (bnave) wrote :

@Andrew: Thanks for the info and link to Docs.

The 2.6.34-7 kernel does resolve the issue for me.

Revision history for this message
Юрий Чудновский (fqc) wrote :

On 2.6.34-02063407-generic I get hang-up resuming from suspend entered on battery, diff vs 2.6.35 is video is coming on: I see boot messages, but no more.

Revision history for this message
ignasi (igp-oenus) wrote :

This is clearly a regression. I've been using both Lucid's kernel modified by voria.org as well as the official from the Ubuntu repo since Maverick rc without a problem. As of today, the 2.6.35 still has this problem.

Revision history for this message
Юрий Чудновский (fqc) wrote :

Hey, I just discovered, my Ethernet card did not work if power adapter not connected! Its look like working, even speed negotiated and ethtool tells "link is up and running", but no any packets going thru eth0!
Is it the same kind of trouble like "bad sleep on battery" discussed here?

Revision history for this message
Rand Aijala (raijala) wrote :

I built the upstream 2.6.36 kernel yesterday and this solved the suspend issues on my Samsung N150 and introduced no new problems as far as I can tell.

Revision history for this message
Rand Aijala (raijala) wrote :

I have attached a tarball with the i386 kernel image and header debs and the config I used. The only change from the default Maverick config was setting the cpu type to Intel Atom.

Revision history for this message
Юрий Чудновский (fqc) wrote :

Confirmed successful wakeup from suspend entered from battery on 2.6.36 kernel! Yeah, entering to sleep on battery power is not fast but its working :)

Revision history for this message
Bazon (bazonbloch) wrote :

Yes, I also can confirm suspend and wakeup works with that 2.6.36-custom kernel.
But on the other hand with that kernel, brightness control for the display doesn't work anymore.

(With 2.6.32, it works with the samsung-tools and samsung backlight packages as proposed there: https://bugs.launchpad.net/ubuntu/+bug/574250/comments/4 )

Revision history for this message
Rand Aijala (raijala) wrote :

Backlight keys aren't working here either. The script found here still works though: http://wiki.archlinux.org/index.php/Samsung_N150#Backlight

Revision history for this message
Amman Sood (amman-sood) wrote :

Also affects my Samsung X460-44G.

Confirmed 2.6.34 Lucid kernel works.

Revision history for this message
Юрий Чудновский (fqc) wrote :

It's look like problem still exists with 2.6.36 kernel but have less hang-up chance. I can't figure out the exact case for hang-up. Maybe it is related to sound activity.

Revision history for this message
Susanne Schlensog (sschlensog) wrote :

I had no luck with 2.6.36. And I don't think it's related to sound activity. It even freezes with sound all muted. I'm sort of getting tired with this regression. From what I've read in the past days, a lot of people with very different hardware suffer from resume bugs. No idea if and how they are related but this is a really bad thing. Users with laptops/netbooks rely on suspend/hibernate.

I'm now running a 2.6.34 kernel from maverick, and it's working as expected - even with samsung-tools and samsung backlight. But not getting security and bug fixes via update makes me feel a little insecure.

Revision history for this message
turbolad (turbolad995) wrote :

It looks like this kernel regression in Maverick affects Samsung netbooks rather than other brands of netbooks.

Obviously a change to the way power management works in the newer kernel is causing this.

Revision history for this message
Юрий Чудновский (fqc) wrote :

On 2.6.34-02063407-generic kernel Ethernet on battery is broken too, so, regression seems to be "introduced" in 2.6.33 or 2.6.34 branch.

Revision history for this message
turbolad (turbolad995) wrote :

It's obvious a newer kernel has caused regressions with Samsung netbooks.

"Who" can fix this so we can download the updates and have the issues resolved?

How can we avoid a repeat of this?

I'm willing to try new updates which have not been 100% tested and give you feedback.

Cheers.

Revision history for this message
Юрий Чудновский (fqc) wrote :

Hmm... I'v got Ethernet not working on 2.6.36-custom kernel...Still don't know if it the same regression...

Revision history for this message
Юрий Чудновский (fqc) wrote :

BTW, I've tested Meego 1.1 (it is used 2.6.25 kernel) - same problem with suspend mode. So, it is a definitely Linux kernel related problem.

Revision history for this message
turbolad (turbolad995) wrote :

@Юрий Чудновский

Thank you for confirming this is a kernel bug and regression.

If the kernel developers are made aware of this bug (which now has 102 comments), users of all distributions of Linux, including Ubuntu, will benefit from the fixes made.

Revision history for this message
Benjamin Nave (bnave) wrote :
Revision history for this message
Mark Lord (launchpad-rtr) wrote :

Same issues on N210 netbook with stock 2.6.36 kernel as well as with Maverick kernel,
on top of Ubuntu 10.04 Desktop edition.

-ml

Revision history for this message
Geordi LaForge (develop-ipv7) wrote :

Same issue for me, Samsung N150 Plus, with Kubuntu 10.10.
With kernel proposed in #75, works well and the backlight works.

Revision history for this message
Юрий Чудновский (fqc) wrote :

Installed 2.6.33 kernel - can't hang-up any more ;)
So, bug (regression) is in 2.6.34 kernel branch.
Attaching my kernel build (as previous, just CPU model set to Atom, nothing more).
39.1 MB archive
Can anyone confirm it's works?

Philip Muškovac (yofel)
tags: added: regression-release resume suspend
description: updated
Revision history for this message
Geordi LaForge (develop-ipv7) wrote :

Someone can take a look on this old bug? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/594885
The story is the same, and there is a solution, disable the CONFIG_PM_DISABLE_CONSOLE in kernel configuration and rebuild it.
I try to search in the config file for this parameter but there isn't...
As i read, the problem is the same...is it possibile that in the kernel code, someone activated this option?

Revision history for this message
Юрий Чудновский (fqc) wrote :

No, that is not the same problem. This is totally different bug.

Revision history for this message
Юрий Чудновский (fqc) wrote :

Dismissing my comment #86. I re-tested 2.6.34 kernel and its seems to work good for now. So, confirming regression start at 2.6.35 branch.
And, since my Ethernet not working on battery power even with 2.6.33, it is is another bug, not common for this one.

Revision history for this message
Adam Griffiths (adam-lw-griffiths) wrote :

This also affects the Samsung N145.
Just FYI as there doesn't seem to be a single N145 user on here =/.
I've written up my experience on here in-case its some help to someone else: http://twistedpairdevelopment.wordpress.com/2010/11/16/installing-ubuntu-on-a-samsung-n145-and-possibly-others/

Revision history for this message
Adam Griffiths (adam-lw-griffiths) wrote :

Also can confirm that using the Lucid kernels in comment #72 fix this issue.

Brad Figg (brad-figg)
tags: added: acpi-namespace-lookup
tags: added: acpi-parse-exec-fail
Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

I do have the same problem with a Thinkpad T400.

Revision history for this message
Susanne Schlensog (sschlensog) wrote :

Btw. it's the same with the Natty kernel...

Revision history for this message
Darrell Kavanagh (darrell) wrote :

Same here with a Samsung NP-N210 Plus, BIOS version 01KY. Kernel 2.6.34 (as advised in #75 above) fixes this.

Revision history for this message
Daniel Schindler (daniel-vcard24) wrote :

I had the same problem with the NC10 Plus, appening intel_idle.max_cstate=0 to grub fixes the wakeup thing for me.

Revision history for this message
Darrell Kavanagh (darrell) wrote :

Confirmed workaround: adding intel_idle.max_cstate=0 to kernel boot parameters works for me (N210 Plus) with latest Maverick Kernel (2.6.35-24-generic).

Thanks, Daniel.

Revision history for this message
Mystic-Mirage (mystic-mirage) wrote :

Fix in #115 works for my N148 Plus!
Thanks!

Revision history for this message
Chris (chris-blower) wrote :

#115 also works me with my NB30. Thank you :D

Revision history for this message
turbolad (turbolad995) wrote :

I now have Ubuntu 10.04 on my Samsung NB30, having previously used Ubuntu 10.10 and found it to be slow.

When I put the lid down, the NB30 never wakes up. I tried the solution on post #115, but it didn't work.

Please help!

Revision history for this message
Susanne Schlensog (sschlensog) wrote :

The solution in #115 doesn't work for me on Samsung N150

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote :

#115 works fine for me on a Samsung N150 using the voria kernel.

Revision history for this message
turbolad (turbolad995) wrote :

@Merlin Schumacher
Sorry, but the voria kernel causes Flash player to constantly crash. Without the voria kernel, Flash player behaves in Chromium.

I don't use the wireless on the Samsung NB30, so I don't need the "Samsung wireless" package.

The only thing I can't get working at the moment is resuming from standby after opening the lid. This bug needs fixing.

Revision history for this message
Merlin Schumacher (merlin-schumacher) wrote :

@turbolad: flash works fine for me in firefox. i didn't try chromium. nb30 may be too different to my n150 for comparision.

Revision history for this message
Patrick Biernat (pat91950) wrote :

Comment #115's solution works for me, under the latest 10.10 kernel. Here's my uname -a.

"Linux SMNG-N150 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 01:41:57 UTC 2010 i686 GNU/Linux".

NOTE: The solution appears to work. Before trying this, my Samsung N150 PLUS would sometimes come out of a suspend, and sometimes stay in a coma, where it was impossible to revive it save for a hard reboot. I recreated the same conditions (Firefox, on youtube + Empathy signed into Facebook/IRC + Standard run-off-the-mill Ubuntu 10.10 Netbook Remix install) and tried it twice. Once with closing the lid, once with calling the suspend from a key-combination.

Both resumed quickly and without error (~3-~5 seconds from power switch to login window asking for my password).

If something changes (IE, the error occurs again, I'll be re-commenting, but for now, it looks good) :)

Revision history for this message
Patrick Biernat (pat91950) wrote :

Alright, it seems to have passed a fairly good test. I had it go into suspend mode last night around 12AM, it's now 7:12AM and the laptop successfully, and just as quickly came out of suspend as it should. (Before, long suspend times seemed to almost guarantee a failure in awakening.)

Revision history for this message
turbolad (turbolad995) wrote :

Does anyone know a workaround to get this problem fixed in Ubuntu 10.04? I tried Maverick (Ubuntu 10.10), but it doesn't work well on the NB30.

Revision history for this message
shadyabhi (abhijeet-1989) wrote :

Appending intel_idle.max_cstate=0 to the kernel boot parameters solves the issue on my samsung n210 with 2.6.36.2 kernel.

Revision history for this message
Johannes Postler (josi) wrote :

I confirm #115 is resolving the issue for Samsung N220 plus

Revision history for this message
David P Kleinschmidt (david-kleinschmidt) wrote :

It seems that I can set intel_idle.max_cstate as high as 3 to fix the bug on my Samsung N150+, and it isn't until intel_idle.max_cstate=4 that I start to run into problems.

Linux tinytronix 2.6.35-24-generic #43~ppa1~loms~maverick-Ubuntu SMP Fri Dec 24 18:15:40 UTC 2010 i686 GNU/Linux

BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=66817f18-a5c7-4d9e-8a29-3220974cb618 ro intel_idle.max_cstate=3 quiet splash

- dpk

Revision history for this message
turbolad (turbolad995) wrote :

On the affected Samsung netbooks (I'm using the NB30), what's the difference between:

intel_idle.max_cstate=0
intel_idle.max_cstate=1
intel_idle.max_cstate=2
intel_idle.max_cstate=3
intel_idle.max_cstate=4

Is it worth trying them all?
Ubuntu 10.04 is also affected by this bug.

Revision history for this message
David P Kleinschmidt (david-kleinschmidt) wrote :

I am not a hardware person, but this is what I have gleaned: cstates are reduced-power modes of the CPU, with 0 representing the standard full-power operating state and higher numbers meaning greater power reduction through underclocking and voltage reduction. So in a theoretical sense, max_cstate=3 would almost certainly be better for battery life than max_cstate=0, but how much better and in what cases, I couldn't tell ya.

However, intel_idle.max_cstate=0 is a flag to the intel_idle kernel module to turn itself off completely, leaving power management to the acpi_idle module. It's possible that a fully-functional acpi_idle module might be better for your battery than a throttled-back intel_idle module, I don't know.

- dpk

Revision history for this message
turbolad (turbolad995) wrote :

Thanks for the info @David P Kleinschmidt

I'm running Ubuntu 10.04 (I was previously using Ubuntu 10.10).

What are the precise steps for adding: intel_idle.max_cstate=0

Maybe I've been doing it wrong?

Revision history for this message
Timo Voigt (timovoigt) wrote :

Yeah a step by step instruction would be great for linux newbies like me...

Revision history for this message
Daniel Schindler (daniel-vcard24) wrote :

Hi

Step by step editing:

1.) Edit the grub config file
#sudo nano /etc/default/grub

2.) Append intel_idle.max_cstate=0 to the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
-> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=0"

3.) Save grub config file
Press Ctrl + X

4.) run update-grub
#sudo update-grub

5.) Reboot
#sudo reboot

Revision history for this message
Timo Voigt (timovoigt) wrote :

thank u very much i can`t believe it actually works on my samsung n150 plus.

Revision history for this message
Daniel Schindler (daniel-vcard24) wrote :

btw, it works also (at least for me) with just adding nolapic_timer to grub boot paramters instead of intel_idle.max_cstate=0

Revision history for this message
turbolad (turbolad995) wrote :

Neither intel_idle.max_cstate=0 or nolapic_timer offer permanent fixes. Having tried both workarounds, sometimes the Samsung NB30 resumes from power saving, but other times it will not resume. Then the networking gets disabled and requires manual fixing:
http://www.ubuntugeek.com/how-to-fix-network-manager-disabled-problem-in-ubuntu-10-04-lucid.html

Will someone PLEASE fix this power saving bug and offer the fix to every Ubuntu user via the Update Manager! There's now over 136 comments regarding this bug and there's no fix yet.

Revision history for this message
Stuart (sjh777) wrote :
Download full text (4.5 KiB)

Daniel,

Thanks very much for the step-by-step guide. I haven't tried the
nolapic_timer method yet but the intel_idle.max_cstate=0 certainly
fixed the issue on my Samsung N220 Plus.

Thanks again!

On 5 January 2011 20:40, turbolad <email address hidden> wrote:
> Neither intel_idle.max_cstate=0 or nolapic_timer offer permanent fixes.  Having tried both workarounds, sometimes the Samsung NB30 resumes from power saving, but other times it will not resume.  Then the networking gets disabled and requires manual fixing:
> http://www.ubuntugeek.com/how-to-fix-network-manager-disabled-problem-in-ubuntu-10-04-lucid.html
>
> Will someone PLEASE fix this power saving bug and offer the fix to every
> Ubuntu user via the Update Manager!  There's now over 136 comments
> regarding this bug and there's no fix yet.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/640100
>
> Title:
>  Maverick fails to wake up on Samsung N150
>
> Status in “linux” package in Ubuntu:
>  Confirmed
>
> Bug description:
>  Recently upgraded from 10.04LTS to 10.10 Beta on a Samsung N150 NetBook.  Since update, my netbook does not resume from suspend state after lid is opened.  Power, disk, and wireless activity lights turn on, but screen does not wake up.  I cannot ssh into the netbook from a remote host so I do not think that the network is resuming even though the wireless light indicates that the card is on.  I have to power off/on the netbook once it is hung in this state.
>
> I've examined /var/log/messages after power cycling but I don't see any relevant errors.  I would be happy to submit applicable logs or provide more information if someone could point me in the right direction.
>
> Thanks!
>
> == Regression details ==
> Last known good version: mainline 2.6.34.7-maverick
> Confirmed broken since: 2.6.35-22.34
>
> ---
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> AplayDevices:
>  **** List of PLAYBACK Hardware Devices ****
>  card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
>    Subdevices: 1/1
>    Subdevice #0: subdevice #0
> Architecture: i386
> ArecordDevices:
>  **** List of CAPTURE Hardware Devices ****
>  card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
>    Subdevices: 1/1
>    Subdevice #0: subdevice #0
> AudioDevicesInUse:
>  Cannot stat file /proc/13903/fd/11: Stale NFS file handle
>                       USER        PID ACCESS COMMAND
>  /dev/snd/controlC0:  ubuntu     3659 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
>  Card hw:0 'Intel'/'HDA Intel at 0xf0400000 irq 47'
>    Mixer name   : 'Realtek ALC269'
>    Components   : 'HDA:10ec0269,144dc072,00100004'
>    Controls      : 11
>    Simple ctrls  : 7DistroRelease: Ubuntu 10.10LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
> MachineType: SAMSUNG ELECTRONICS CO., LTD. N150/N210/N220
> Package: linux (not installed)
> ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname-netbook.seed boot=casper initrd=/casper/initrd.lz qu...

Read more...

Revision history for this message
montini (montini) wrote :

After applying the workaround "intel_idle.max_cstate=0" I have come into some issue when after resuming from suspend (that part seems to be working fine now) the backlighting of my n220 is jumping up and down for some time (with the respective indicator applet visualizations, and no chance to stop it by using keyboard Fn-Up/Fn-Down). This occurs kind of randomly, and goes away after some time - sometimes it can be solved by closing the lid and opening again - i.e. by additional suspend/resume cycle. Is anyone else having this also?

Revision history for this message
TenaciousC (chris-kool4katz) wrote :

With the the 2.6.35-24 kernel I could not control backlight brightness using the samsung tools (Fn-Up/Fn-Down) at all. I had to add a further kernel parameter : acpi_backlight=vendor . With that the control works again, but when the backlight level is changed by the system (for power saving) the brightness indicator applet goes into a loop until interrupted by clicking an item on the main menu bar (Applications for example).

However I removed intel_idle.max_cstate=0 from the kernel boot parameters and the problem stills occurs, so I'm not sure the brightness phenomenon is related to these parameters.

C

Revision history for this message
montini (montini) wrote :
Download full text (4.5 KiB)

In my case I am using samsung tools

On Thu, Jan 6, 2011 at 9:40 AM, TenaciousC <email address hidden> wrote:

> With the the 2.6.35-24 kernel I could not control backlight brightness
> using the samsung tools (Fn-Up/Fn-Down) at all. I had to add a further
> kernel parameter : acpi_backlight=vendor . With that the control works
> again, but when the backlight level is changed by the system (for power
> saving) the brightness indicator applet goes into a loop until
> interrupted by clicking an item on the main menu bar (Applications for
> example).
>
> However I removed intel_idle.max_cstate=0 from the kernel boot
> parameters and the problem stills occurs, so I'm not sure the
> brightness phenomenon is related to these parameters.
>
> C
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/640100
>
> Title:
> Maverick fails to wake up on Samsung N150
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> Recently upgraded from 10.04LTS to 10.10 Beta on a Samsung N150 NetBook.
> Since update, my netbook does not resume from suspend state after lid is
> opened. Power, disk, and wireless activity lights turn on, but screen does
> not wake up. I cannot ssh into the netbook from a remote host so I do not
> think that the network is resuming even though the wireless light indicates
> that the card is on. I have to power off/on the netbook once it is hung in
> this state.
>
> I've examined /var/log/messages after power cycling but I don't see any
> relevant errors. I would be happy to submit applicable logs or provide more
> information if someone could point me in the right direction.
>
> Thanks!
>
> == Regression details ==
> Last known good version: mainline 2.6.34.7-maverick
> Confirmed broken since: 2.6.35-22.34
>
> ---
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
> AplayDevices:
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> Architecture: i386
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> Cannot stat file /proc/13903/fd/11: Stale NFS file handle
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu 3659 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf0400000 irq 47'
> Mixer name : 'Realtek ALC269'
> Components : 'HDA:10ec0269,144dc072,00100004'
> Controls : 11
> Simple ctrls : 7DistroRelease: Ubuntu 10.10LiveMediaBuild:
> Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
> MachineType: SAMSUNG ELECTRONICS CO., LTD. N150/N210/N220
> Package: linux (not installed)
> ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true
> persistent file=/cdrom/preseed/hostname-netbook.seed boot=casper
> initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
> ProcEnviron:
> ...

Read more...

Revision history for this message
Юрий Чудновский (fqc) wrote :

Confirm "acpi_backlight=vendor" lead backlight go crazy. Simplest way to stop flicking is to switch on virtual console (for example Ctrl+Alt+F1) and back.

Revision history for this message
David D (noiseball) wrote :

Both of Daniel's solutions (#115 and #136) solve the suspend issues on my N150Plus, but caused me to lose the ability to control the screen brightness. (well, #115 seemed to cause it, #136 certainly didn't bring it back)

Revision history for this message
Susanne Schlensog (sschlensog) wrote :

I've filed a bug for Natty, where my N150 suffers from the same symptoms. You can find it here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/705044
Please subscribe and add a "me too". Thanks!

Revision history for this message
Philip Muškovac (yofel) wrote :

Please DON'T add a "me too" - for kernel bugs everyone should have his/her own bug unless you're using the exact same hardware, kernel, firmware version, etc... So please file seperate bugs instead of adding metoos!
(Also: we have the "affects me" link at the top of the page for actually counted me-toos)

Revision history for this message
Susanne Schlensog (sschlensog) wrote :

Uh, I meant that everybody affected should add him- or herself as "affects me". Sorry!

Revision history for this message
dks (mydks) wrote :

#134 works on my n148 netbook. Thx.

Seth Forshee (sforshee)
Changed in linux (Ubuntu):
assignee: nobody → Seth Forshee (sforshee)
status: Confirmed → In Progress
Revision history for this message
Anton (anton-bugs) wrote :

this is might be the upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=20172

Revision history for this message
Seth Forshee (sforshee) wrote :

@Anton:

Thanks for the pointer, but that looks like a different bug. I've linked up this issue with the appropriate issue in the kernel bugzilla.

Changed in linux:
importance: Unknown → Medium
status: Unknown → Incomplete
Revision history for this message
turbolad (turbolad995) wrote :

I installed Lubuntu (yes Lubuntu) on my Samsung NB30 - the latest alpha version with kernel 2.6.38-4-generic SMP. Waking up from standby now works when I open the lid. Wireless now works, but when I open the lid to resume from standby, the wireless stops working.

Revision history for this message
Seth Forshee (sforshee) wrote :

@turbolad:

How many times have you tried it? For me on an N150 it's inconsistent -- sometimes it resumes, sometimes it doesn't. So much so that I'm using a script to do repeated suspend/resume cycles until it hangs. It frequently takes 20+ cycles, and I've even seen 100+ cycles before it finally hung on a couple of occasions.

Revision history for this message
turbolad (turbolad995) wrote :

If it fails to resume from standby, I'll post again.

The only problem I'm now having is the wireless stops working after power saving.

Revision history for this message
Tom Rowland (b-rizlaz) wrote :

The "intel_idle.max_cstate=0" appears to work on my N145 with 2.6.35-25 and, except for using lucid 2.6.32-22 kernel, the steps collated by Adam Griffiths (see #110).
I have only tested it two or three times though (keys, lid, lid).
Also note the backlight issue, but have seen this happen without sleep/resume, so agree with others on that being a 'something else'.

Revision history for this message
turbolad (turbolad995) wrote :

Using Lubuntu with kernel 2.6.38-7-generic on my Samsung NB30 netbook and the power management still works EXCEPT for the wireless not working after coming out of standby - it says "device not ready".

Revision history for this message
Seth Forshee (sforshee) wrote :

Adding a release notes task since it doesn't look likely there will be a fix for this in time for Natty. Proposed text:

Samsung N150 hangs indefinitely after suspend. Workaround: specify "intel_idle.max_cstate=3" as kernel parameter at boot.

Revision history for this message
waffelball (johannes-temme) wrote :

I have a Samsung N220 Plus netbook and encountered the following: After a clean new install of Natty (Beta 1) suspend to ram works out of the box but unfortunately adapting backlight did not work.
Hence I installed the package samsung-backlight from the ppa of voria (for maverick, since natty packages are not yet available) which resolved this problem. As a matter of fact from there on suspend to ram did not work for me anymore and i encountered the same problems as described in this bug report.
Unloading the samsung-backlight module before suspend made suspend to ram working again. More explicitly I followed the steps proposed here http://www.voria.org/forum/viewtopic.php?f=3&t=625&hilit=N220&start=60

0) install samsung-backlight from the ppa of voria
1) modifiy in /etc/default/grub following line from
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash'
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
2) sudo update-grub; sudo update-initramfs -u
3) add the following text to the end of /etc/modprobe.d/blacklist.conf: blacklist samsung-backlight
4) edit /etc/rc.local and paste before the "exit 0" statement: modprobe samsung-backlight
5) create a file called /etc/pm/config.d/unload_modules containing: SUSPEND_MODULES="samsung-backlight"

I emphasize I did not have to append "intel_idle.max_cstate=0 " to grub to make suspend to ram working!
So everyone encountering the problems described in this bug report should check whether samsung-backlight is installed and whether unloading its module before suspend resolves the problem!

Revision history for this message
Seth Forshee (sforshee) wrote :

@waffelball: Thanks for the suggestion, but I don't have samsung-backlight installed on the N150 and it still hangs coming out of resume.

Revision history for this message
Tom Rowland (b-rizlaz) wrote :

@waffelball: I do have samsung-backlight installed on my N145+ with Maverick and kernel 2.6.35-27, and tried your suggestion.
I'm pretty sure I followed the steps correctly, but it did not work.

Changed in linux (Ubuntu Natty):
importance: Undecided → Medium
Changed in linux (Ubuntu Oneiric):
importance: Undecided → Medium
Changed in linux (Ubuntu Maverick):
importance: Undecided → Medium
Revision history for this message
Юрий Чудновский (fqc) wrote :

I've getting hangups every day or two and can't figure out a reason. It can be the same bug. Today I get hanged one CPU core and sustem was able to log down incident.
It begins by "BUG: unable to handle kernel NULL pointer dereference at (null)" and continued by spam of "BUG: soft lockup - CPU#1 stuck for 61s!" messages. Bakause of relatively big log volume piece, I'm pasted it to http://pastebin.com/cCqjw0vy

Revision history for this message
Seth Forshee (sforshee) wrote :

@Юрий Чудновский:

That looks like something different. Please open a new bug report for your issue.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Set Natty task Won't Fix. We will review potential fixes and SRU where applicable.

Thanks!

~JFo

Changed in linux (Ubuntu Natty):
status: In Progress → Won't Fix
description: updated
Seth Forshee (sforshee)
Changed in ubuntu-release-notes:
status: New → Fix Released
Revision history for this message
Seth Forshee (sforshee) wrote :

Marking kernel tasks as Won't Fix since a good workaround exists.

Changed in linux (Ubuntu):
status: In Progress → Won't Fix
Changed in linux (Ubuntu Maverick):
status: New → Won't Fix
Changed in linux (Ubuntu Oneiric):
status: New → Won't Fix
Revision history for this message
Jaap Versteegh (j-r-versteegh) wrote :

I have this issue on my N210 on Maverick (2.6.35). Screen stays black after resume. I've installed a Lucid kernel (2.6.32). This kernel does resume from suspend properly and seems to work ok with Maverick otherwise too.

Revision history for this message
Tom Rowland (b-rizlaz) wrote :

Confirm instructions by @waffelball in post #156 work with clean install of Natty (11.04) on N145Plus with samsung-tools + samsung-backlight. Did not try suspend when out-of-box.

Revision history for this message
Susanne Schlensog (sschlensog) wrote :

Instructions on #156 do NOT work with an up-to-date Natty install on a Samsung N150 with samsung-tools and samsung-backlight. Performing the steps in #156 leads to a non-adjustable backlight - else suspend isn't working, neither with instructions or without. I can say, it was partly working before the release of Natty.

Revision history for this message
turbolad (turbolad995) wrote :

This bug affects a lot of people, including me, when I use my Samsung netbook - which is an NB30 and not the N150.

If it comes out of power saving mode when I open the lid, the wireless stops working.

Revision history for this message
Susanne Schlensog (sschlensog) wrote :

I configured gnome-power-manager to go into suspend after 30 minutes of idle state. Most of the time, it doesn't work at all and the N150 runs until the battery is drained. The other times, it goes into suspend but fails to wake up again. I don't know how many times I had to hard reset. This is very bad!

Revision history for this message
Seth Forshee (sforshee) wrote :

Backlight issues really aren't relevant to this bug. If no bug exists for this issue please create a new one.

@turbolad, from looking back over you comments I think there's a good chance that the problem with your machine is different from the one affecting the N150. It would probably make sense to reopen your original bug report, and to open a new one for the wireless failing after resume if no other bug matches your symptoms.

@Susanne, the failure to suspend after 30 minutes are separate issues from this one, and you should file a new bug if no existing bug matches your symptoms. There is not a fix available for the failure to resume from suspend, but you can perform the following steps to work around the problem:

1. Open /etc/default/grub as root and modify the line beginning with GRUB_CMDLINE_LINUX to read:

  GRUB_CMDLINE_LINUX="intel_idle.max_cstate=3"

2. In a terminal, run "sudo update-grub2"

3. Reboot

After this resuming from suspend should function correctly.

Revision history for this message
Arnon Klein (arnon-klein) wrote :

It looks like it is a wireless device module issue. I'm using 11.04 with out-of-the-box kernel 2.6.38-8-generic .

Patching up /usr/lib/pm-utils/sleep.d/55NetworkManager
with :

case "$1" in
 hibernate|suspend)
  suspend_nm
                modprobe -r ath9k
  ;;
 thaw|resume)
  modprobe ath9k
  resume_nm
  ;;
 *) exit $NA
  ;;
esac

solved this, and my N150 is now returning from suspend.

Revision history for this message
Tom Rowland (b-rizlaz) wrote :

Can confirm that Arnon's patch works on my N145P (also using 2.6.38-8 generic).
Some update broke Waffelball's #156 suggestion, which had previously worked.

Revision history for this message
Seth Forshee (sforshee) wrote :

On Fri, Jul 08, 2011 at 03:16:20PM -0000, Arnon Klein wrote:
> It looks like it is a wireless device module issue. I'm using 11.04 with
> out-of-the-box kernel 2.6.38-8-generic .
>
> Patching up /usr/lib/pm-utils/sleep.d/55NetworkManager
> with :
>
> case "$1" in
> hibernate|suspend)
> suspend_nm
> modprobe -r ath9k
> ;;
> thaw|resume)
> modprobe ath9k
> resume_nm
> ;;
> *) exit $NA
> ;;
> esac
>
> solved this, and my N150 is now returning from suspend.

That's interesting. When I investigated I saw that the hang was most
definitely happening prior to resuming devices, so I'm not sure what the
relationship is. A lot of things seemed to make the problem harder to
trigger without completely eliminating it though; the hang appears to be
very timing sensitive. If you're interested you could try running an
automated S3 test to see whether you can trigger a hang. The following
would do 100 S3 iterations (you'll probably need to run 'sudo apt-get
install fwts' first):

  fwts s3 --s3-multiple=100

I'm no longer in posession of one of these machines to try it myself.

Revision history for this message
dan (mybodya) wrote :

Hey guys, it's ridiculous that this bug is not planned to be fixed neither in this version of Ubuntu nor in the next. There are 300 000 Lenovo s10-3 and Samsung N230 netbooks manufactured each year and if their users install Ubuntu, they have to loose their data if the netbook suspends. I can be a tester for this project, please send me instructions whatto do but please do not freeze work on this bug

The solutions posted here didn't work for me

I've found some spacial solution described here
http://ubuntuforums.org/showthread.php?t=1799930&highlight=lenovo

Revision history for this message
Seth Forshee (sforshee) wrote :

On Fri, Jul 08, 2011 at 09:31:42PM -0000, dan wrote:
> Hey guys, it's ridiculous that this bug is not planned to be fixed
> neither in this version of Ubuntu nor in the next. There are 300 000
> Lenovo s10-3 and Samsung N230 netbooks manufactured each year and if

What reason do you have to believe that the issue with the Lenovo is the
same as the issue with the Samsung netbooks?

Failure to resume tends to be very hardware-specific, particular to a
particular piece of hardware or model of computer. If you have a Lenovo
s10-3 or Samsung N230 that fails to resume and can't find any bugs
addressing your model specifically, I suggest that you open a new bug.
We are keen to fix as many of these problems as possible.

Revision history for this message
Gergan Penkov (gergan) wrote :

I haven't commented till now, but I must say that this bug shows for me the trends in Ubuntu. In the past three years I have installed 3 Computers with Ubuntu (mostly friends with old laptops, who had problems to keep on with windows and the viruses :) ) and won some users for ubuntu and linux.
Now not to sound as a jerk I am thankful for what canonical and Ubuntu have done for Linux, but from 10.10 on this is one unusable Distro. Now all these laptops are Arch.
My own nettop is Samsung N220 and had this same problem after the 10.10 update. Now strangely enough with Arch the problem does not occur.
What I want to say is that I am a long time gentoo user and my work and home desktops are running gentoo and although there is a misconception that gentoo developers are harsh and unhelpful, I have never seen such unprofessional bug treatment in gentoo-bugzilla as the one here, with such comments and with resolutions won't fix.
The second bug I followed was about the extremely slow unity. This specific nettop was also unusable with unity. This second bug is still open and here to be found https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/657976
Now if for three releases two extremely big problems in totally open sourced hardware could not be fixed, i am not sure if it is worth it to try and install ubuntu again.

PS: Gnome 3 on Arch on this very laptop is extremely fluid - so this is a distro regression.

Changed in linux:
status: Incomplete → Fix Released
Changed in linux:
status: Fix Released → Confirmed
Revision history for this message
Laurent Genoud (lg-u) wrote :

For the Samsung N150 running Ubuntu 11.10

I can confirm the only solution worked for me is the post 156 (Thanks to Waffelball)

All other proposed solutions leads to suspend and backlight not working together.
(tried solutions of almost all posts except 169)

Thanks to Ubuntu and folks here, don't need to buy a new laptop for my girlfriend ;-)

Changed in linux:
status: Confirmed → In Progress
Revision history for this message
Sebastian Thürrschmidt (thuerrschmidt) wrote :

After upgrading my Samsung N150 to Raring (amd64), suspend/resume now works out of the box. Previously, with Quantal, it needed the intel_idle.max_cstate=3 kernel parameter. Looks like this bug has been fixed, intentionally or not.

Changed in linux:
status: In Progress → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.