Bug#625804: marked as done (linux-2.6: lockups in rtc on armhf)
Your message dated Wed, 25 May 2011 17:27:45 +0200
with message-id <874o4ipzpq.fsf@lebrac.rtp-net.org>
and subject line Re: Bug#625804: rtc/mc13xxx: don't call rtc_device_register with the lock held
has caused the Debian Bug report #625804,
regarding linux-2.6: lockups in rtc on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
625804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625804
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.39~rc5-1~experimental.1
Severity: normal
i was experiencing lockups on an armhf kernel built from the experimental branch:
[ 2.644589] usb 2-1.1: SerialNumber: 1.0
[ 240.664217] INFO: task swapper:1 blocked for more than 120 seconds.
[ 240.670509] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.678374] swapper D c0285240 0 1 0 0x00000000
[ 240.684824] [<c0285240>] (schedule+0x4bc/0x510) from [<c0285ca0>] (__mutex_lock_slowpath+0x7c/0xa0)
[ 240.693914] [<c0285ca0>] (__mutex_lock_slowpath+0x7c/0xa0) from [<c01e2bb8>] (mc13xxx_rtc_read_time+0x18/0xe4)
[ 240.703967] [<c01e2bb8>] (mc13xxx_rtc_read_time+0x18/0xe4) from [<c01e0974>] (__rtc_read_time+0x4c/0x50)
the following patch by Arnaud Patard seemed to resolve the problem:
http://patchwork.ozlabs.org/patch/89644/
Index: imx-test/drivers/rtc/rtc-mc13xxx.c
===================================================================
--- imx-test.orig/drivers/rtc/rtc-mc13xxx.c
+++ imx-test/drivers/rtc/rtc-mc13xxx.c
@@ -349,8 +349,13 @@ static int __devinit mc13xxx_rtc_probe(s
if (ret)
goto err_alarm_irq_request;
+ mc13xxx_unlock(mc13xxx);
+
priv->rtc = rtc_device_register(pdev->name,
&pdev->dev, &mc13xxx_rtc_ops, THIS_MODULE);
+
+ mc13xxx_lock(mc13xxx);
+
if (IS_ERR(priv->rtc)) {
ret = PTR_ERR(priv->rtc);
live well,
vagrant
--- End Message ---
--- Begin Message ---
Vagrant Cascadian <vagrant@debian.org> writes:
Version: 2.6.39-1
Hi,
>
> http://patchwork.ozlabs.org/patch/94354/
>
> thanks! i just tested and confirmed that this patch also resolves the issue.
This patch is in 2.6.39 which has landed into unstable so closing the
bug
Arnaud
--- End Message ---
Reply to: