-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: workqueue leaked lock or atomic: kworker/0:2/0xffffffff/4586 #944
Comments
@marc40000 has your issue been resolved? If yes, then please close this issue. |
No. I still have issues with wifi rpis crashing every few days. |
@marc40000 what does |
pi@gardeneast ~ $ vcgencmd version pi@gardeneast ~ $ uname -a I have several rpis running and they all work without issues. Only the 2 |
Also, I don't know if it helps, but it feels like it always happens if there is a lot of wifi udp traffic going on. |
The kernel for jessie is using 4.4 tree. |
Ok I'll upgrade On 15.08.2016 13:20, popcornmix wrote:
|
Ok I upgraded. And I still have this issue. Random crashes. twice a weak on average. |
What wireless devices are you using? |
A new unit test for the device-dax 1GB enabling currently fails with this warning before hanging the test thread: WARNING: CPU: 0 PID: 21 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0x1e3/0x1f0 percpu ref (dax_pmem_percpu_release [dax_pmem]) <= 0 (0) after switching to atomic [..] CPU: 0 PID: 21 Comm: rcuos/1 Tainted: G O 4.10.0-rc7-next-20170207+ raspberrypi#944 [..] Call Trace: dump_stack+0x86/0xc3 __warn+0xcb/0xf0 warn_slowpath_fmt+0x5f/0x80 ? rcu_nocb_kthread+0x27a/0x510 ? dax_pmem_percpu_exit+0x50/0x50 [dax_pmem] percpu_ref_switch_to_atomic_rcu+0x1e3/0x1f0 ? percpu_ref_exit+0x60/0x60 rcu_nocb_kthread+0x339/0x510 ? rcu_nocb_kthread+0x27a/0x510 kthread+0x101/0x140 The get_user_pages() path needs to arrange for references to be taken against the dev_pagemap instance backing the pud mapping. Refactor the existing __gup_device_huge_pmd() to also account for the pud case. Link: http://lkml.kernel.org/r/148653181153.38226.9605457830505509385.stgit@dwillia2-desk3.amr.corp.intel.com Signed-off-by: Dan Williams <dan.j.williams@intel.com> Cc: Dave Jiang <dave.jiang@intel.com> Cc: Matthew Wilcox <mawilcox@microsoft.com> Cc: Ross Zwisler <ross.zwisler@linux.intel.com> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Cc: Nilesh Choudhury <nilesh.choudhury@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
@marc40000 There have been some fixes for wireless and USB drivers in the latest kernel (4.9). Can you try those and see if the issue is fixed? |
Closing due to lack of activity. Reopen if you feel this issue is still relevant. |
Hi !
I get a crash every one or two days on one of my rpis. Everything works fine but at some point, I get repeating entries multiple times in /var/log/syslog and /var/log/Messages multiple times per second:
This continues for a few minutes and afterwards it crashes:
It's a rpi b+ with kernel 3.18.7 #755. I use the raspbian Image. There is a EDIMAX EW-7811UN that connects the rpi to the lan and Internet.
What causes this? Is it really a kernel bug? Can I do something about it?
The text was updated successfully, but these errors were encountered: