From: stillcompiling@gmail.com (Joshua Clayton)
To: linux-arm-kernel@lists.infradead.org
Subject: Debug kernel oops
Date: Tue, 14 Feb 2017 04:31:24 -0800 [thread overview]
Message-ID: <1757589.1i8MyMhxGJ@diplodocus> (raw)
In-Reply-To: <CAA2oCO=48kuhqZC1pK4NhgWS=FFexRwoak4ks9aRaHoYNmESTw@mail.gmail.com>
On Monday, February 13, 2017 11:35:43 PM PST Madhu K wrote:
> Hi All,
>
> How to debug the kernel oops for arm boards?
>
> Below is my board and setup details.
>
> 1) I am using Beaglebone black board which is running with 4.9.2 kernel
> version.
> 2) I wrote some i2c driver on host machine, it is cross compiled for arm
> and loaded on beaglebone black.
> 3) Insmod is proper, but while unloading the module I am seeing some kernel
> oops.
> 4) How to debug that oops? which tools we have to use?
>
dmesg is your first tool.
And the oops itself is your second debugging tool.
There are plenty of resources on how to decode an oops, such as
... (goes and types "kernel oops example" into a web browser search),
http://opensourceforu.com/2011/01/understanding-a-kernel-oops/
Then add some extra print statements (temporary, for debugging)
to enable you to understand what you are doing wrong.
Good luck.
> Thanks in advance
> Madhu
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2017-02-14 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 7:35 Debug kernel oops Madhu K
2017-02-14 12:31 ` Joshua Clayton [this message]
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=1757589.1i8MyMhxGJ@diplodocus \
--to=stillcompiling@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox