Author |
Message |
timrichardson
|
|
Post subject: one task refusing to freeze
Posted: 29.10.2010, 20:11
|
|

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
|
|
In the past couple of weeks, my laptop often won't suspend or hibernate. It goes through most of the process, but then returns to a resume state (ie locked screensaver). The computer is stable, and I can repeat the process and get the same result. Sometimes I see a console message "one task refusing to freeze". How can I find out which task this is?
The hardware a Dell Vostro. I am still using and have been using
2.6.35-7.slh.5-aptosid-686
for some time; I don't the problem is related to a change in kernel.
I use kde from sid. |
|
|
|
|
 |
ikeinthai
|
|
Post subject: try latest kernel.
Posted: 01.11.2010, 06:56
|
|

Joined: 2010-09-22
Posts: 119
Location: bigannastybkk
Status: Offline
|
|
try dist-upgrading. my hp mini was doing the same thing for a while but now it stopped. suspend resume is fine. i try to dist-upgrade as often as possible (we're on the .36 kernel now).
all the best, ike.
ps the installs on the harddisk and sd card often behave differently when it comes to suspend/resume. the harddisk install is much more likely to do it properly. the sd card installs often cannot. |
_________________ aptosid: magic in action, the point of the spear. bleedin pearls before swine? lets hope not. freesoftware/freedomsoftware=a chance at freedom. participants, engage your vehicle. . . avatar by zenren
|
|
|
|
 |
hy
|
|
Post subject: RE: try latest kernel.
Posted: 01.11.2010, 07:26
|
|

Joined: 2010-09-14
Posts: 194
Location: Costa Teguise
Status: Offline
|
|
I am having the same problem [sleep or hibernate won't work from time to time] - fully dist-upgraded. |
|
|
|
|
 |
timrichardson
|
|
Post subject: RE: try latest kernel.
Posted: 03.11.2010, 09:15
|
|

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
|
|
I have a guess the problem for me is the non-free Jungledisk client (wxpython) but it's just a guess. I haven't seen anything in log files to help |
_________________ There are some who call me Tim
|
|
|
|
 |
hy
|
|
Post subject: RE: try latest kernel.
Posted: 03.11.2010, 10:34
|
|

Joined: 2010-09-14
Posts: 194
Location: Costa Teguise
Status: Offline
|
|
@timrichardson: I don't have wxpython or Jungledisk installed - but the problem is the same here. |
|
|
|
|
 |
timrichardson
|
|
Post subject: RE: try latest kernel.
Posted: 03.11.2010, 10:54
|
|

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
|
|
I wish there was a way to see which processes are not freezing |
_________________ There are some who call me Tim
|
|
|
|
 |
timrichardson
|
|
Post subject: RE: try latest kernel.
Posted: 03.11.2010, 11:23
|
|

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
|
|
In case this helps, I changed /etc/uswsusp.conf by adding this line at the end
Code:
suspend loglevel = 1
which may be generating more talkative logs in /var/log/pm-suspend
although of course since doing that I can not reproduce the problem. |
_________________ There are some who call me Tim
|
|
|
|
 |
timrichardson
|
|
Post subject: RE: try latest kernel.
Posted: 04.11.2010, 11:52
|
|

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
|
|
I got 31 processes refusing to freeze just now, as the computer on battery power attempted to automatically suspend to ram. Relevant logfile is syslog. The failing to freeze message is from the kernel.
I will try the latest kernel. |
_________________ There are some who call me Tim
|
|
|
|
 |
timrichardson
|
|
Post subject: RE: try latest kernel.
Posted: 04.11.2010, 19:57
|
|

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
|
|
With the latest kernel, problem persists. Here is syslog output from just now.
Code:
Nov 5 06:55:45 siduxbox kernel: [28517.734513] PM: Syncing filesystems ... done.
Nov 5 06:56:05 siduxbox kernel: [28517.892467] Freezing user space processes ...
Nov 5 06:56:05 siduxbox kernel: [28537.902106] Freezing of tasks failed after 20.00 seconds (1 tasks refusing to freeze, wq_busy=0):
Nov 5 06:56:05 siduxbox kernel: [28537.902235] nepomukservic D c5e3be60 0 3149 3073 0x00800084
Nov 5 06:56:05 siduxbox kernel: [28537.902241] f4b97240 00200086 c48f7e60 c5e3be60 00000001 00000000 c012bd57 00000000
Nov 5 06:56:05 siduxbox kernel: [28537.902248] c6575434 c057e3c0 c057e3c0 f69c76c0 000019ef c057e3c0 f4b973fc f4b973f8
Nov 5 06:56:05 siduxbox kernel: [28537.902255] c057e3c0 f4b97240 c057e3c0 d6dd0a48 000019ef c4323cbc c0151b2d c4323c20
Nov 5 06:56:05 siduxbox kernel: [28537.902262] Call Trace:
Nov 5 06:56:05 siduxbox kernel: [28537.902271] [<c012bd57>] ? __wake_up_common+0x47/0x70
Nov 5 06:56:05 siduxbox kernel: [28537.902276] [<c0151b2d>] ? prepare_to_wait+0x1d/0x70
Nov 5 06:56:05 siduxbox kernel: [28537.902289] [<fa3f6f3d>] ? fuse_request_send+0xcd/0x2a0 [fuse]
Nov 5 06:56:05 siduxbox kernel: [28537.902292] [<c01518e0>] ? autoremove_wake_function+0x0/0x40
Nov 5 06:56:05 siduxbox kernel: [28537.902295] [<c01df3e0>] ? filldir+0x0/0xd0
Nov 5 06:56:05 siduxbox kernel: [28537.902298] [<fa3f9a27>] ? fuse_readdir+0xc7/0x220 [fuse]
Nov 5 06:56:05 siduxbox kernel: [28537.902301] [<c01df3e0>] ? filldir+0x0/0xd0
Nov 5 06:56:05 siduxbox kernel: [28537.902303] [<c01df3e0>] ? filldir+0x0/0xd0
Nov 5 06:56:05 siduxbox kernel: [28537.902305] [<c01df62d>] ? vfs_readdir+0x9d/0xc0
Nov 5 06:56:05 siduxbox kernel: [28537.902307] [<c01df78e>] ? sys_getdents+0x6e/0xc0
Nov 5 06:56:05 siduxbox kernel: [28537.902310] [<c0103718>] ? sysenter_do_call+0x12/0x28
Nov 5 06:56:05 siduxbox kernel: [28537.902323]
Nov 5 06:56:05 siduxbox kernel: [28537.902324] Restarting tasks ... done.
|
_________________ There are some who call me Tim
|
|
|
|
 |
DeepDayze
|
|
Post subject: Re: RE: try latest kernel.
Posted: 05.11.2010, 00:03
|
|

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
|
|
timrichardson wrote:
With the latest kernel, problem persists. Here is syslog output from just now.
Code:
Nov 5 06:55:45 siduxbox kernel: [28517.734513] PM: Syncing filesystems ... done.
Nov 5 06:56:05 siduxbox kernel: [28517.892467] Freezing user space processes ...
Nov 5 06:56:05 siduxbox kernel: [28537.902106] Freezing of tasks failed after 20.00 seconds (1 tasks refusing to freeze, wq_busy=0):
Nov 5 06:56:05 siduxbox kernel: [28537.902235] nepomukservic D c5e3be60 0 3149 3073 0x00800084
Nov 5 06:56:05 siduxbox kernel: [28537.902241] f4b97240 00200086 c48f7e60 c5e3be60 00000001 00000000 c012bd57 00000000
Nov 5 06:56:05 siduxbox kernel: [28537.902248] c6575434 c057e3c0 c057e3c0 f69c76c0 000019ef c057e3c0 f4b973fc f4b973f8
Nov 5 06:56:05 siduxbox kernel: [28537.902255] c057e3c0 f4b97240 c057e3c0 d6dd0a48 000019ef c4323cbc c0151b2d c4323c20
Nov 5 06:56:05 siduxbox kernel: [28537.902262] Call Trace:
Nov 5 06:56:05 siduxbox kernel: [28537.902271] [<c012bd57>] ? __wake_up_common+0x47/0x70
Nov 5 06:56:05 siduxbox kernel: [28537.902276] [<c0151b2d>] ? prepare_to_wait+0x1d/0x70
Nov 5 06:56:05 siduxbox kernel: [28537.902289] [<fa3f6f3d>] ? fuse_request_send+0xcd/0x2a0 [fuse]
Nov 5 06:56:05 siduxbox kernel: [28537.902292] [<c01518e0>] ? autoremove_wake_function+0x0/0x40
Nov 5 06:56:05 siduxbox kernel: [28537.902295] [<c01df3e0>] ? filldir+0x0/0xd0
Nov 5 06:56:05 siduxbox kernel: [28537.902298] [<fa3f9a27>] ? fuse_readdir+0xc7/0x220 [fuse]
Nov 5 06:56:05 siduxbox kernel: [28537.902301] [<c01df3e0>] ? filldir+0x0/0xd0
Nov 5 06:56:05 siduxbox kernel: [28537.902303] [<c01df3e0>] ? filldir+0x0/0xd0
Nov 5 06:56:05 siduxbox kernel: [28537.902305] [<c01df62d>] ? vfs_readdir+0x9d/0xc0
Nov 5 06:56:05 siduxbox kernel: [28537.902307] [<c01df78e>] ? sys_getdents+0x6e/0xc0
Nov 5 06:56:05 siduxbox kernel: [28537.902310] [<c0103718>] ? sysenter_do_call+0x12/0x28
Nov 5 06:56:05 siduxbox kernel: [28537.902323]
Nov 5 06:56:05 siduxbox kernel: [28537.902324] Restarting tasks ... done.
Looks like nepomukservice oopsed there, not sure if that's the culprit |
|
|
|
|
 |
timrichardson
|
|
Post subject:
Posted: 07.11.2010, 01:07
|
|

Joined: 2010-09-12
Posts: 66
Location: Melbourne
Status: Offline
|
|
I'm pretty sure it was the culprit. I disabled it a few days ago and I've been watching how the system goes. It has suspended flawlessly since I turned off Nepomuk. I normally don't use Nepomuk but activated it a few weeks ago to see how useful it was, so this may or may not be a new bug in Nepomuk. |
|
|
|
|
 |
DeepDayze
|
|
Post subject:
Posted: 07.11.2010, 16:16
|
|

Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
|
|
timrichardson wrote:
I'm pretty sure it was the culprit. I disabled it a few days ago and I've been watching how the system goes. It has suspended flawlessly since I turned off Nepomuk. I normally don't use Nepomuk but activated it a few weeks ago to see how useful it was, so this may or may not be a new bug in Nepomuk.
Why not open a bug using reportbug if this hasn't been reported already? Sounds like an issue that needs correction, particularly for notebooks...for people who use nepomuk. I'd think nepomuk should freeze/unfreeze itself gracefully |
|
|
|
|
 |
|