public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "Jani-Matti Hätinen" <jani-matti.hatinen@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lock-up with modprobe sdhci after suspending to ram
Date: Sat, 29 Apr 2006 17:25:53 +0200	[thread overview]
Message-ID: <44538581.50608@drzeus.cx> (raw)
In-Reply-To: <200604251645.58421.jani-matti.hatinen@iki.fi>

Jani-Matti Hätinen wrote:
>
> Ok, this is what I get on Loglevel 9.
>   If I try to suspend with the module loaded and with a card in the reader I 
> get:
> Stopping tasks: ================================|
> ipw2200: Failed to send CARD_DISABLE: Command timed out
> ACPI: PCI interrupt for device 0000:01:05.0 disabled
> sdhci [sdhci_suspend()]: Suspending...
> MMC: starting cmd 07 arg 00000000 flags 00000000
> sdhci [sdhci_send_command()]: Sending cmd (7)
>
> And if I modprobe sdhci after suspend&resume I get the following:
>   First from the modprobe (not all of it is visible):
> sdhci: Sys addr: 0xffffffff | Version:  0x0000ffff
> sdhci: Blk size: 0x0000ffff | Blk cnt:  0x0000ffff
> sdhci: Argument: 0xffffffff | Trn mode: 0x0000ffff
> sdhci: Present:  0xffffffff | Host ctl: 0x000000ff
> sdhci: Power:    0x000000ff | Blk gap:  0x000000ff
> sdhci: Wake-up:  0x000000ff | Clock:    0x0000ffff
> sdhci: Timeout:  0x000000ff | Int stat: 0xffffffff
> sdhci: Int enab: 0xffffffff | Sig enab: 0xffffffff
> sdhci: AC12 err: 0x0000ffff | Slot int: 0x0000ffff
> sdhci: Caps:     0xffffffff | Max curr: 0xffffffff
> sdhci: ===========================================
>   

Now this is horribly broken and would explain why things go south. I
guess the chip needs a reset early in the detection sequence to function
properly. Try putting:

    sdhci_reset(host, SDHCI_RESET_ALL);

just before the driver does a readl() on the capabilities register (in
sdhci_probe_slot()).

>   Also I just noticed that if the machine has been through at least one 
> suspend&resume cycle, rebooting no longer works. All processes exit cleanly, 
> but the system just hangs when it should shut down.
>   

That's just probably a broken ACPI. Laptops tend to be buggy as hell.
File a report with the ACPI guys.

Rgds
Pierre


  reply	other threads:[~2006-04-29 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24  7:33 Lock-up with modprobe sdhci after suspending to ram Jani-Matti Hätinen
2006-04-24 12:29 ` Pierre Ossman
2006-04-25  8:08   ` Jani-Matti Hätinen
2006-04-25  8:42     ` Pierre Ossman
2006-04-25 13:45       ` Jani-Matti Hätinen
2006-04-29 15:25         ` Pierre Ossman [this message]
2006-05-04  6:57           ` Jani-Matti Hätinen
2006-05-05 20:40             ` Pierre Ossman
2006-04-25 10:12 ` Pekka Enberg
2006-04-25 19:11   ` Jani-Matti Hätinen

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=44538581.50608@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=jani-matti.hatinen@iki.fi \
    --cc=linux-kernel@vger.kernel.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