Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Panic in quirk_usb_early_handoff
Date: Sat, 4 Mar 2017 17:57:59 +0100	[thread overview]
Message-ID: <4a07dbec-dcde-9ec0-514f-3b896e2b0b19@free.fr> (raw)
In-Reply-To: <CAKv+Gu_M6aMMfeCy7ZUM46Ptei1suvX+F_KtWG2_QFp_6jbCWw@mail.gmail.com>

On 04/03/2017 09:07, Ard Biesheuvel wrote:
> On 4 March 2017 at 00:24, Mason wrote:
>> On 03/03/2017 20:02, Robin Murphy wrote:
>>
>>> On 03/03/17 17:15, Mason wrote:
>>>
>>>> [    1.261813] Unable to handle kernel paging request at virtual address d08611e4
>>>> [    1.269167] pgd = c0004000
>>>> [    1.271979] [d08611e4] *pgd=8f804811, *pte=00000000, *ppte=00000000
>>>> [    1.278394] Internal error: Oops: 7 [#1] PREEMPT SMP ARM
>>>> [    1.283815] Modules linked in:
>>>> [    1.286970] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.7-1-rc2 #157
>>>> [    1.293614] Hardware name: Sigma Tango DT
>>>> [    1.297726] task: cf82c9c0 task.stack: cf838000
>>>> [    1.302364] PC is at quirk_usb_early_handoff+0x3e8/0x790
>>>> [    1.307790] LR is at ioremap_page_range+0xf8/0x1a8
>>>> [    1.312688] pc : [<c039fe44>]    lr : [<c02d0a10>]    psr: 000e0013
>>>> [    1.312688] sp : cf839d78  ip : 00000000  fp : cf839e38
>>>> [    1.324399] r10: c10248a0  r9 : 00000000  r8 : d08611e4
>>>> [    1.329733] r7 : d084e000  r6 : 00002000  r5 : 000c0300  r4 : cfb4e800
>>>> [    1.336377] r3 : 000131e4  r2 : 00000000  r1 : 91001e13  r0 : d084e000
>>>
>>> ...and again. And always at the same PC, too.
>>
>> By the way, isn't LR supposed to point to the caller of the
>> current function? ("LR is at ioremap_page_range")
>>
>> If so, why does it not appear in the back trace?
> 
> lr is supposed to point to the return address at function entry. After
> that, all bets are off, really, since ARM usually pops the return
> address from the stack straight into the pc register. So in this case,
> it looks like it still contains the address that the most recent leaf
> function returned to (or another function that actually restores the
> return address into lr before branching to it). But it could easily
> contain garbage as well.

If there is only a tiny chance that LR contains genuinely useful
information, then what is the rationale for providing the info
at all in the panic message?

I would argue that no info is better than info that is wrong
most of the time.

Regards.

  parent reply	other threads:[~2017-03-04 16:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 16:18 Panic in quirk_usb_early_handoff Mason
2017-03-03 17:10 ` Mason
2017-03-03 17:15   ` Mason
2017-03-03 19:02     ` Robin Murphy
2017-03-03 22:09       ` Mason
2017-03-04  0:24       ` Mason
2017-03-04  8:07         ` Ard Biesheuvel
2017-03-04 15:51           ` Alan Stern
2017-03-04 16:57           ` Mason [this message]
2017-03-04 17:16             ` Ard Biesheuvel
2017-03-04 17:29               ` Mason
2017-03-04 18:27                 ` Ard Biesheuvel
2017-03-06 12:42       ` Mason
2017-03-06 13:49         ` Mason
2017-03-06 15:27           ` David Laight
2017-03-06 15:45             ` Mason
2017-03-06 15:58               ` David Laight
2017-03-06 14:30         ` Robin Murphy
2017-03-06 14:56           ` Mason

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=4a07dbec-dcde-9ec0-514f-3b896e2b0b19@free.fr \
    --to=slash.tmp@free.fr \
    --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