Hi there,
I'm playing around with the latest snapshots on my IGEPv2 and I'm seeing a recurring message posted to the console while using it:
[ 1561.340942] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1561.350860] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1681.356597] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1681.367187] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
root@linaro:~# uname -a Linux linaro 2.6.38-1002-linaro-omap #3-Ubuntu SMP Fri Apr 15 14:00:54 UTC 2011 armv7l armv7l armv7l GNU/Linux
I'd like to find out what that task is meant to be doing and why it is getting blocked. I haven't been able to notice anything negative in my use of the system (downloading and installing packages, editing files, running cpuburn and stress).
Thanks,
Dnia 2011-05-23, pon o godzinie 10:10 -0300, Christian Robottom Reis pisze:
Hi there,
I'm playing around with the latest snapshots on my IGEPv2 and I'mseeing a recurring message posted to the console while using it:
[ 1561.340942] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1561.350860] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1681.356597] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1681.367187] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@linaro:~# uname -a Linux linaro 2.6.38-1002-linaro-omap #3-Ubuntu SMP Fri Apr 15 14:00:54 UTC 2011 armv7l armv7l armv7l GNU/LinuxI'd like to find out what that task is meant to be doing and why it is getting blocked. I haven't been able to notice anything negative in my use of the system (downloading and installing packages, editing files, running cpuburn and stress).
Same happens from time to time on PandaBoard.
I've also seen it on my beagle Xm from time to time. Agree, be nice to figure out who is blocked and why.
On Mon, May 23, 2011 at 8:10 AM, Christian Robottom Reis kiko@async.com.br wrote:
Hi there,
I'm playing around with the latest snapshots on my IGEPv2 and I'm seeing a recurring message posted to the console while using it:
[ 1561.340942] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1561.350860] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1681.356597] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1681.367187] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
root@linaro:~# uname -a Linux linaro 2.6.38-1002-linaro-omap #3-Ubuntu SMP Fri Apr 15 14:00:54 UTC 2011 armv7l armv7l armv7l GNU/Linux
I'd like to find out what that task is meant to be doing and why it is getting blocked. I haven't been able to notice anything negative in my use of the system (downloading and installing packages, editing files, running cpuburn and stress).
Thanks,
Christian Robottom Reis | [+55 16] 3376 0125 | http://launchpad.net/~kiko Canonical Ltd. | [+55 16] 9112 6430 | http://async.com.br/~kiko
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Mon, May 23, 2011 at 9:50 AM, Tom Gall tom.gall@linaro.org wrote:
I've also seen it on my beagle Xm from time to time. Agree, be nice to figure out who is blocked and why.
ok, its not the wireless driver mishaving then
Hi John,
echo blacklist wl12xx_sdio > /etc/modprobe.d/blacklist-wireless.conf reboot
Doesn't change the behavior on my Xm.
Anything else you want me to try just hollar.
Regards, Tom
On Mon, May 23, 2011 at 10:52 AM, John Rigby john.rigby@linaro.org wrote:
On Mon, May 23, 2011 at 9:50 AM, Tom Gall tom.gall@linaro.org wrote:
I've also seen it on my beagle Xm from time to time. Agree, be nice to figure out who is blocked and why.
ok, its not the wireless driver mishaving then
I have only seen this with the wireless problem already noted. Can you see if blacklisting the wireless driver fixes the problem?
echo blacklist wl12xx_sdio > /etc/modeprobe.d/blacklist-wireless.conf reboot
On Mon, May 23, 2011 at 7:10 AM, Christian Robottom Reis kiko@async.com.br wrote:
Hi there,
I'm playing around with the latest snapshots on my IGEPv2 and I'm seeing a recurring message posted to the console while using it:
[ 1561.340942] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1561.350860] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1681.356597] INFO: task kworker/0:0:1030 blocked for more than 120 seconds. [ 1681.367187] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
root@linaro:~# uname -a Linux linaro 2.6.38-1002-linaro-omap #3-Ubuntu SMP Fri Apr 15 14:00:54 UTC 2011 armv7l armv7l armv7l GNU/Linux
I'd like to find out what that task is meant to be doing and why it is getting blocked. I haven't been able to notice anything negative in my use of the system (downloading and installing packages, editing files, running cpuburn and stress).
Thanks,
Christian Robottom Reis | [+55 16] 3376 0125 | http://launchpad.net/~kiko Canonical Ltd. | [+55 16] 9112 6430 | http://async.com.br/~kiko
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Mon, May 23, 2011 at 09:51:04AM -0600, John Rigby wrote:
I have only seen this with the wireless problem already noted. Can you see if blacklisting the wireless driver fixes the problem?
Hmmm. What wireless problem?
echo blacklist wl12xx_sdio > /etc/modeprobe.d/blacklist-wireless.conf reboot
The IGEPv2 doesn't use wl12xx; it uses the libertas (it's got a Marvell 88w8686 onboard).
Just to be clear, wifi works fine on this device, out of the box.
Isn't there a way to trigger a backtrace or dump of the hung kworker task?
PS: I just boot-tested the latest 1003 kernel and it's working fine; in fact, I now get a flashing green light when the box is on, whereas before I used to get a dead led. The U-Boot issues I pointed out earlier are still there, though.
On Tue, May 24, 2011 at 10:03 PM, Christian Robottom Reis kiko@linaro.org wrote:
On Mon, May 23, 2011 at 09:51:04AM -0600, John Rigby wrote:
I have only seen this with the wireless problem already noted. Can you see if blacklisting the wireless driver fixes the problem?
Hmmm. What wireless problem?
echo blacklist wl12xx_sdio > /etc/modeprobe.d/blacklist-wireless.conf reboot
The IGEPv2 doesn't use wl12xx; it uses the libertas (it's got a Marvell 88w8686 onboard).
Just to be clear, wifi works fine on this device, out of the box.
Isn't there a way to trigger a backtrace or dump of the hung kworker task?
PS: I just boot-tested the latest 1003 kernel and it's working fine; in fact, I now get a flashing green light when the box is on, whereas before I used to get a dead led. The U-Boot issues I pointed out earlier are still there, though.
It seems that this issue was fixed with 1003 as soon as we disabled cpu_freq for both Omap 3 and Omap 4. Didn't confirm, but that would be the main change regarding Omap 3.
For Omap 4 the wlan driver was also causing similar issues.
Cheers,
-
Christian Robottom Reis -
Christian Robottom Reis -
John Rigby -
Marcin Juszkiewicz -
Ricardo Salveti -
Tom Gall