From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: "Reserved instruction in kernel code" on ath9k insertion
Date: Sat, 24 Oct 2009 22:58:49 +0200 [thread overview]
Message-ID: <4AE36A89.8070105@wpkg.org> (raw)
In-Reply-To: <4AE36884.6060806@lwfinger.net>
Larry Finger schrieb:
>> # modprobe ath9k
>> [ 165.440000] Reserved instruction in kernel code[#1]:
(...)
>> [ 165.440000] Code: 00000000 00000000 00000000 <00003009> 005196a8
>> 005196a8 00000002 00000000 005166b0
>> [ 165.440000] Disabling lock debugging due to kernel taint
>> Segmentation fault
>> #
>
> Is that the start of the error dump?
Yes - as I do "modprobe", it starts to print the dump.
Then, modprobe segfaults.
> A BUG() statement places an
> illegal instruction in the code. Is that the case here?
I have no idea.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-10-24 20:59 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 [this message]
2009-10-26 13:17 ` Luis R. Rodriguez
2009-10-26 13:27 ` Tomasz Chmielewski
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=4AE36A89.8070105@wpkg.org \
--to=mangoo@wpkg.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.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.