sdhci error report in syslog
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | linux (Ubuntu) |
Undecided
|
Unassigned | ||
| | linux-source-2.6.20 (Ubuntu) |
Medium
|
Unassigned | ||
Bug Description
Binary package hint: linux-source-2.6.20
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] mmc0: Got command interrupt even though no command operation was in progress.
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] mmc0: Please report this to <email address hidden>.
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: ============== REGISTER DUMP ==============
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Sys addr: 0xffffffff | Version: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Blk size: 0x0000ffff | Blk cnt: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Present: 0xffffffff | Host ctl: 0x000000ff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Power: 0x000000ff | Blk gap: 0x000000ff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Wake-up: 0x000000ff | Clock: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Timeout: 0x000000ff | Int stat: 0xffffffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Caps: 0xffffffff | Max curr: 0xffffffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: =======
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] mmc0: Card is consuming too much power!
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] mmc0: Unexpected interrupt 0x00800000. Please report this to <email address hidden>.
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: ============== REGISTER DUMP ==============
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Sys addr: 0xffffffff | Version: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Blk size: 0x0000ffff | Blk cnt: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Present: 0xffffffff | Host ctl: 0x000000ff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Power: 0x000000ff | Blk gap: 0x000000ff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Wake-up: 0x000000ff | Clock: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Timeout: 0x000000ff | Int stat: 0xffffffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: Caps: 0xffffffff | Max curr: 0xffffffff
Jan 22 03:28:41 lifelesslap kernel: [ 5873.120000] sdhci: =======
| Robert Collins (lifeless) wrote : | #1 |
| Cristian Aravena Romero (caravena) wrote : | #2 |
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available here: <http://
| Robert Collins (lifeless) wrote : | #3 |
Uhm, you already have all the relevant dmesg data there: I showed this to the Ubuntu kernel developers in person.
Kernel build is:
2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux
| Ben Collins (ben-collins) wrote : | #4 |
I'm wondering if this has anything to do with shared interrupts. Can you attach "cat /proc/interrupts"?
| Changed in linux-source-2.6.20: | |
| assignee: | nobody → ubuntu-kernel-team |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
On Thu, 2007-02-22 at 21:34 +0000, Ben Collins wrote:
> I'm wondering if this has anything to do with shared interrupts. Can you
> attach "cat /proc/interrupts"?
I'm on .8 now, if that changes anything.
~$ cat /proc/interrupts
CPU0
0: 21752125 IO-APIC-edge timer
1: 192364 IO-APIC-edge i8042
8: 5 IO-APIC-edge rtc
9: 47 IO-APIC-fasteoi acpi
12: 1234728 IO-APIC-edge i8042
14: 1292794 IO-APIC-edge ide0
16: 15501018 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5, Intel
ICH6, i915@pci:
17: 0 IO-APIC-fasteoi uhci_hcd:usb4, yenta
18: 8976829 IO-APIC-fasteoi uhci_hcd:usb2, sdhci:slot0, ipw2200
19: 2 IO-APIC-fasteoi uhci_hcd:usb3, ohci1394
NMI: 0
LOC: 21752069
ERR: 0
MIS: 0
--
GPG key available at: <http://
Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://
| Leann Ogasawara (leannogasawara) wrote : | #7 |
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:
1) If you are comfortable installing packages on your own, the linux-image-
--or--
2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://
Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.
Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https:/
| Ike Panhc (ikepanhc) wrote : | #9 |
This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Won't Fix |


From the sdhci list...
PCI config space issue. Try to find someone of the suspend guys to have
a look at it.
Rgds
--
-- Pierre Ossman