From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Kernel BUG due to kernel page fault
Date: Fri, 27 Jan 2012 17:42:21 +0100 [thread overview]
Message-ID: <20120127164219.GE19323@redhat.com> (raw)
In-Reply-To: <4F21D57F.7090103@lwfinger.net>
On Thu, Jan 26, 2012 at 04:36:47PM -0600, Larry Finger wrote:
> Modules linked in: fuse autofs4 snd_pcm_oss snd_mixer_oss snd_seq
> snd_seq_device edd nfs nfsd lockd auth_rpcgss nfs_acl sunrpc
> exportfs ipv6 vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> RIP: 0010:[<ffffffff811e3ecb>] [<ffffffff811e3ecb>] strnlen+0xb/0x30
[snip]
> Call Trace:
> [<ffffffff811e58ae>] string.isra.4+0x3e/0xd0
> [<ffffffff811e6889>] vsnprintf+0x219/0x600
> [<ffffffff81153093>] seq_printf+0x53/0x80
> [<ffffffff811e21db>] ? radix_tree_lookup+0xb/0x10
> [<ffffffff810ba5ab>] show_interrupts+0x24b/0x300
> [<ffffffff81153474>] seq_read+0x2b4/0x3f0
> [<ffffffff811531c0>] ? seq_lseek+0x100/0x100
> [<ffffffff8118b651>] proc_reg_read+0x81/0xc0
> [<ffffffff8112f967>] vfs_read+0xa7/0x160
> [<ffffffff8112fa65>] sys_read+0x45/0x90
> [<ffffffff813a33a2>] system_call_fastpath+0x16/0x1b
This is call trace from cat /proc/interrupts, seems something pass
malformed string to request_irq(). I do not think this is rtlwifi,
rather that vbox thing.
Stanislaw
next prev parent reply other threads:[~2012-01-27 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 22:36 Kernel BUG due to kernel page fault Larry Finger
2012-01-27 16:42 ` Stanislaw Gruszka [this message]
2012-01-27 18:07 ` Larry Finger
2012-01-28 4:30 ` Johannes Berg
2012-01-28 23:02 ` Larry Finger
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=20120127164219.GE19323@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--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.