From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG (maybe) with find_get_entry()
Date: Wed, 8 Oct 2014 20:13:04 +0200 [thread overview]
Message-ID: <20141008181304.GA3109@debian> (raw)
In-Reply-To: <20141008165714.GG22688@saruman>
On Wed, Oct 08, 2014 at 11:57:14AM -0500, Felipe Balbi wrote:
> Hi,
>
> With today's linus/master and with greg/usb-next I keep getting random
> kernel oops from find_get_entry() (see below):
>
> [ 47.700065] Unable to handle kernel paging request at virtual address ffffffff
> [ 47.707667] pgd = c0004000
> [ 47.710506] [ffffffff] *pgd=ae7f6821, *pte=00000000, *ppte=00000000
> [ 47.717135] Internal error: Oops: 17 [#1] SMP ARM
> [ 47.722047] Modules linked in: g_mass_storage usb_f_mass_storage libcomposite configfs xhci_plat_hcd xhci_hcd snd_soc_davinci_mcasp snd_soc_edma snd_soc_omap snd_soc_evm snd_soc_tlv320aic3x dwc3 snd_soc_core snd_compress omapdrm snd_pcm_dmaengine snd_pcm snd_timer snd fb_sys_fops lis3lv02d_i2c panel_dpi matrix_keypad lis3lv02d dwc3_omap input_polldev soundcore
> [ 47.755668] CPU: 0 PID: 1440 Comm: file-storage Not tainted 3.17.0-02899-ga7d2165 #229
> [ 47.763958] task: ed1b22c0 ti: ed20e000 task.ti: ed20e000
> [ 47.769609] PC is at find_get_entry+0x64/0x100
> [ 47.774281] LR is at 0xfffffffa
What GCC version are you using?
4.8.1 and 4.8.2 are known to miscompile the ARM kernel and these
find_get_entry() crashes with 0xffffffff involved smell a lot like the
earlier reports from kernels build with those compilers:
https://lkml.org/lkml/2014/6/25/456
https://lkml.org/lkml/2014/6/30/375
https://lkml.org/lkml/2014/6/30/660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854
https://lkml.org/lkml/2014/5/9/330
prev parent reply other threads:[~2014-10-08 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 16:57 BUG (maybe) with find_get_entry() Felipe Balbi
2014-10-08 18:13 ` Rabin Vincent [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=20141008181304.GA3109@debian \
--to=rabin@rab.in \
--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;
as well as URLs for NNTP newsgroup(s).