From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mmc@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, pfactum@gmail.com,
Maxim Levitsky <maximlevitsky@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [Bugme-new] [Bug 16627] New: sdhci shows backtrace while resuming after s2disk
Date: Thu, 19 Aug 2010 15:45:39 -0700 [thread overview]
Message-ID: <20100819154539.31c4e6b9.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-16627-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Thu, 19 Aug 2010 10:01:14 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=16627
>
> Summary: sdhci shows backtrace while resuming after s2disk
> Product: Drivers
> Version: 2.5
> Kernel Version: 2.6.35.2
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: MMC/SD
> AssignedTo: drivers_mmc-sd@kernel-bugs.osdl.org
> ReportedBy: pfactum@gmail.com
> Regression: No
>
>
> Created an attachment (id=27506)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=27506)
> config, lspci and dmesg
>
> The following strings appear in dmesg after resuming:
>
> ===
> [ 199.151739] Call Trace:
> [ 199.151749] [<c1073734>] ? __report_bad_irq+0x24/0x90
> [ 199.151753] [<c10738f0>] ? note_interrupt+0x150/0x190
> [ 199.151757] [<c10751f1>] ? move_native_irq+0x11/0x50
> [ 199.151762] [<c107413b>] ? handle_fasteoi_irq+0xab/0xd0
> [ 199.151765] [<c1074090>] ? handle_fasteoi_irq+0x0/0xd0
> [ 199.151768] <IRQ> [<c1004657>] ? do_IRQ+0x47/0xc0
> [ 199.151775] [<c10030e9>] ? common_interrupt+0x29/0x30
> [ 199.151780] [<c103007b>] ? __sched_setscheduler+0x26b/0x400
> [ 199.151786] [<c122f581>] ? acpi_idle_enter_c1+0x9d/0xb2
> [ 199.151792] [<c135e586>] ? cpuidle_idle_call+0x76/0xe0
> [ 199.151795] [<c1001bef>] ? cpu_idle+0x3f/0x90
> [ 199.151800] [<c15ee8d7>] ? start_kernel+0x2e9/0x2ee
> [ 199.151804] [<c15ee42c>] ? unknown_bootoption+0x0/0x190
> [ 199.151806] handlers:
> [ 199.151808] [<f8bfac50>] (r852_irq+0x0/0x250 [r852])
> [ 199.151820] [<c136a080>] (sdhci_irq+0x0/0x570)
Both r852_irq() and sdhci_irq() are on that IRQ so the interrupt could
have been for either one.
> ===
> ...
> ===
> [ 208.256014] mmc0: Timeout waiting for hardware interrupt.
> [ 208.256019] sdhci: ============== REGISTER DUMP ==============
> [ 208.256025] sdhci: Sys addr: 0x00000000 | Version: 0x00000400
> [ 208.256030] sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
> [ 208.256035] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
> [ 208.256040] sdhci: Present: 0x01f70000 | Host ctl: 0x00000001
> [ 208.256044] sdhci: Power: 0x0000000f | Blk gap: 0x00000000
> [ 208.256049] sdhci: Wake-up: 0x00000000 | Clock: 0x00004007
> [ 208.256054] sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
> [ 208.256058] sdhci: Int enab: 0x00ff00c3 | Sig enab: 0x00ff00c3
> [ 208.256063] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001
> [ 208.256068] sdhci: Caps: 0x00c02120 | Max curr: 0x00000040
> [ 208.256070] sdhci: ===========================================
> ===
Although it does look more MMCish. It may be a platform issue too, in
which case we'd need to talk with the ACPI guys.
> lspci, dmesg and config are enclosed as attach.
Thanks.
next parent reply other threads:[~2010-08-19 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16627-10286@https.bugzilla.kernel.org/>
2010-08-19 22:45 ` Andrew Morton [this message]
2010-08-20 7:27 ` [Bugme-new] [Bug 16627] New: sdhci shows backtrace while resuming after s2disk Maxim Levitsky
2010-08-20 9:16 ` Oleksandr Natalenko
2010-08-20 10:38 ` Oleksandr Natalenko
2010-08-20 12:18 ` Oleksandr Natalenko
2010-08-20 12:18 ` Oleksandr Natalenko
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=20100819154539.31c4e6b9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=pfactum@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