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: Tue, 25 Apr 2006 10:42:14 +0200 [thread overview]
Message-ID: <444DE0E6.8090801@drzeus.cx> (raw)
In-Reply-To: <200604251108.52515.jani-matti.hatinen@iki.fi>
Jani-Matti Hätinen wrote:
>
> Looks like some kind of routing problem. Even pings don't seem to get through
> to mmc.drzeus.cx, or list.drzeus.cx. With http I get a timeout from
> mmc.drzeus.cx. This is from IP 80.221.18.58
>
Most of the domain is down right now (changing ISP). But the mail server
is up at hermes.drzeus.cx:
drzeus.cx. 86393 IN MX 10 mail.drzeus.cx.
list.drzeus.cx. 86400 IN MX 10 mail.drzeus.cx.
mail.drzeus.cx. 84586 IN A 193.12.253.7
hermes.drzeus.cx. 83892 IN A 193.12.253.7
> Unfortunately even text mode is completely speechless about it. The modprobe
> goes through cleanly and I get the regular prompt (with a blinking cursor
> even), but the machine's completely locked up.
>
>
Have you tried pinging it? For some reason the keyboard tends to bail
out when there are outstanding MMC requests. I've only seen this with a
card in the slot though.
You could increase the log level sent to console and enable MMC_DEBUG.
If you can find more closely where it hangs I have a better chance of
finding it.
Rgds
Pierre
next prev parent reply other threads:[~2006-04-25 8:42 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 [this message]
2006-04-25 13:45 ` Jani-Matti Hätinen
2006-04-29 15:25 ` Pierre Ossman
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=444DE0E6.8090801@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.