From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: "Reserved instruction in kernel code" on ath9k insertion
Date: Mon, 26 Oct 2009 14:27:56 +0100 [thread overview]
Message-ID: <4AE5A3DC.1090804@wpkg.org> (raw)
In-Reply-To: <43e72e890910260617n6efbd260gcafbf5d1d2c84e23@mail.gmail.com>
Luis R. Rodriguez wrote:
> On Sat, Oct 24, 2009 at 12:50 PM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>> When I do "modprobe ath9k" on ASUS-WL-500gP (MIPS) with _ath5k_ card (so, no
>> ath9k hardware), it says "Reserved instruction in kernel code" - is it
>> expected?
>
> No.
>
>> The kernel is 2.6.31.1.
>>
>>
>> # modprobe ath9k
>> [ 165.440000] Reserved instruction in kernel code[#1]:
>> [ 165.440000] Cpu 0
>> [ 165.440000] $ 0 : 00000000 1000dc00 00000000 00000000
>> [ 165.440000] $ 4 : c1135b20 00000001 c044e69c ffffffff
>> [ 165.440000] $ 8 : 0000000a 8101f6d8 ffffffe0 0000002b
>> [ 165.440000] $12 : 00000e44 00000006 80333ae8 5f657361
>> [ 165.440000] $16 : 00000001 c1135ca4 80370000 81418000
>> [ 165.440000] $20 : 00000000 00000000 00000000 004fe008
>> [ 165.440000] $24 : 00000010 c1115118
>> [ 165.440000] $28 : 81da6000 81da7ea8 7febead8 81418014
>> [ 165.440000] Hi : 00000000
>> [ 165.440000] Lo : 00000000
>> [ 165.440000] epc : c044e694 0xc044e694
>> [ 165.440000] Not tainted
>
> This says not tainted.
(...)
>> [ 165.440000] Disabling lock debugging due to kernel taint
>
> But this says kernel taint.
Yep, I saw this as well.
About every oops or panic on this hardware says "Disabling lock
debugging due to kernel taint", no idea why.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-10-26 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 19:50 "Reserved instruction in kernel code" on ath9k insertion Tomasz Chmielewski
2009-10-24 20:50 ` Larry Finger
2009-10-24 20:58 ` Tomasz Chmielewski
2009-10-26 13:17 ` Luis R. Rodriguez
2009-10-26 13:27 ` Tomasz Chmielewski [this message]
2009-10-26 13:31 ` Johannes Berg
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=4AE5A3DC.1090804@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).