From: sgr.m.pdy@gmail.com (Sagar Padhye)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Should I do anything about this warning?
Date: Wed, 8 Oct 2014 12:43:58 +0530 [thread overview]
Message-ID: <20141008071356.GA20385@gmail.com> (raw)
Hi,
I am new at kernel programming. I have written a driver for a custom device, running on arm board. It works well (for last few months).
I happen to look at kernel logs and I seen,
[231250.894334] ------------[ cut here ]------------
[231250.899146] WARNING: at kernel/workqueue.c:1953 process_one_work+0x398/0x52c()
[231250.906491] Modules linked in: bcmdhd cfg80211 <XYZ>
[231250.911885] [<c0016450>] (unwind_backtrace+0x0/0x144) from [<c05c04f0>] (dump_stack+0x20/0x24)
[231250.920672] [<c05c04f0>] (dump_stack+0x20/0x24) from [<c006c330>] (warn_slowpath_common+0x5c/0x74)
[231250.929757] [<c006c330>] (warn_slowpath_common+0x5c/0x74) from [<c006c374>] (warn_slowpath_null+0x2c/0x34)
[231250.939581] [<c006c374>] (warn_slowpath_null+0x2c/0x34) from [<c0088f08>] (process_one_work+0x398/0x52c)
[231250.949232] [<c0088f08>] (process_one_work+0x398/0x52c) from [<c00895c8>] (rescuer_thread+0x184/0x230)
[231250.958708] [<c00895c8>] (rescuer_thread+0x184/0x230) from [<c008dd60>] (kthread+0xac/0xb4)
[231250.967236] [<c008dd60>] (kthread+0xac/0xb4) from [<c000fd4c>] (kernel_thread_exit+0x0/0x8)
[231250.975755] ---[ end trace 9f9c2187c0bee21b ]---
The device is still working after this. No issues in operation. I am just sceptical about analyzing this issue? Do I need to check more? If yes how? with this trace?
Thanks,
Sagar
next reply other threads:[~2014-10-08 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 7:13 Sagar Padhye [this message]
2014-10-08 9:33 ` Should I do anything about this warning? Kristof Provost
2014-10-08 11:55 ` Sagar Padhye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141008071356.GA20385@gmail.com \
--to=sgr.m.pdy@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.