From: Xiangfu Liu <xiangfu@qi-hardware.com>
To: vinit dhatrak <vinit.dhatrak@gmail.com>
Cc: loody <miloody@gmail.com>, linux-mips <linux-mips@linux-mips.org>,
Kernel Newbies <kernelnewbies@nl.linux.org>
Subject: Re: kernel panic about kernel unaligned access
Date: Wed, 28 Oct 2009 04:05:23 +0800 [thread overview]
Message-ID: <4AE75283.4040404@qi-hardware.com> (raw)
In-Reply-To: <edf0f34e0910271003k66440e9did790c07a0a79919b@mail.gmail.com>
vinit dhatrak wrote:
>> my questions are:
>> 1. what does "Not tainted" mean?
>> 2. I grep the kernel and I find the above message comes from do_ade in
>> unaligned.c, If I guess correctly.
>> but from the call trace I cannot find out who call it.
>> who and how kernel pass the information to do_ade?
>> 3. as far as i know, inode is the data structure we used to record file.
>> From what information in the inode I can find out the file name the
>> writeback_inodes try to write?
>> appreciate your help,
>> miloody
>>
>
> I can answer your first question. Loading a proprietary or
> non-GPL-compatible module will 'taint' the running kernel—meaning that
> any problems or bugs experienced will be less likely to be
> investigated by the maintainers. See this "Tainted Kernel" document
> from Novell.
> http://www.novell.com/support/viewContent.do?externalId=3582750&sliceId=1
>
> In your case, it seems that your kernel is not tainted by any external code.
> Also, what you see as call trace is actually just stack dump, not
> exactly a backtrace.
Hi I also got similar panic in my board (ben nanonote). the process is "Process ksoftirqd/0"
Q: how to get the backtrace?
next prev parent reply other threads:[~2009-10-27 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 13:27 kernel panic about kernel unaligned access loody
2009-10-27 13:27 ` loody
[not found] ` <edf0f34e0910271003k66440e9did790c07a0a79919b@mail.gmail.com>
2009-10-27 20:05 ` Xiangfu Liu [this message]
2009-10-28 3:56 ` Mulyadi Santosa
2009-10-28 4:03 ` loody
2009-10-28 15:40 ` David Daney
2009-10-29 3:48 ` loody
2009-10-29 5:51 ` Anupam Kapoor
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=4AE75283.4040404@qi-hardware.com \
--to=xiangfu@qi-hardware.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mips@linux-mips.org \
--cc=miloody@gmail.com \
--cc=vinit.dhatrak@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).