[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#412915: marked as done (linux-image-2.6.18-4-686: mmc/sdhci problems after resume from ram)

Your message dated Thu, 3 Jul 2008 19:30:46 +0200
with message-id <20080703173046.GF20796@stro.at>
and subject line Re: linux-image-2.6.18-4-686: mmc/sdhci problems after resume from ram
has caused the Debian Bug report #412915,
regarding linux-image-2.6.18-4-686: mmc/sdhci problems after resume from ram
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
412915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412915
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-11
Severity: normal

Hi,

after resuming from suspend-to-ram (suspended with s2ram from
uswsusp/unstable) mmc_core and sdhci spit out tons of errors and make the
system very unresponsive. Eventually the system freezes (or
unresponsiveness >>> my patience), a quick shutdown after resume usually helps.

a few lines from syslog:

Feb 27 04:15:18 lembas kernel: mmc0: Controller never released inhibit bit(s). Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x2 never completed. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x4 never completed. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:18 lembas kernel: mmc0: Controller never released inhibit bit(s). Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x2 never completed. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x4 never completed. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:18 lembas kernel: mmc0: Reset 0x1 never completed. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:33 lembas kernel: mmc0: Got command interrupt even though no command operation was in progress.
Feb 27 04:15:33 lembas kernel: mmc0: Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:33 lembas kernel: mmc0: Card is consuming too much power!
Feb 27 04:15:33 lembas kernel: mmc0: Unexpected interrupt 0x00800000. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:33 lembas kernel: mmc0: Got command interrupt even though no command operation was in progress.
Feb 27 04:15:33 lembas kernel: mmc0: Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:33 lembas kernel: mmc0: Card is consuming too much power!
Feb 27 04:15:33 lembas kernel: mmc0: Unexpected interrupt 0x00800000. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:35 lembas kernel: mmc0: Controller never released inhibit bit(s). Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:35 lembas kernel: mmc0: Reset 0x2 never completed. Please report this to <sdhci-devel@list.drzeus.cx>.
Feb 27 04:15:35 lembas kernel: mmc0: Reset 0x4 never completed. Please report this to <sdhci-devel@list.drzeus.cx>.

The mmc messages are repeated in differing amounts of the single messages
again and again, each message is followed (or preceded?) by the following sdhci messages:

Feb 27 04:15:18 lembas kernel: sdhci: ============== REGISTER DUMP ==============
Feb 27 04:15:18 lembas kernel: sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
Feb 27 04:15:18 lembas kernel: sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
Feb 27 04:15:18 lembas kernel: sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
Feb 27 04:15:18 lembas kernel: sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
Feb 27 04:15:18 lembas kernel: sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
Feb 27 04:15:18 lembas kernel: sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
Feb 27 04:15:18 lembas kernel: sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
Feb 27 04:15:18 lembas kernel: sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
Feb 27 04:15:18 lembas kernel: sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
Feb 27 04:15:18 lembas kernel: sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
Feb 27 04:15:18 lembas kernel: sdhci: ===========================================

Suspend-to-Ram (and resume) with the two modules mmc_core and sdhci unloaded
just works fine. Since I don't need the card reader (not sure if it even
works) I'll probably just blacklist these modules ...

Andreas


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (600, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

--- End Message ---
--- Begin Message --- 
Version: 2.6.25-1

fixed in newer linux images.

thanks for report.

-- 
maks

--- End Message ---
Reply to: