Re: Lock-up with modprobe sdhci after suspending to ram

Hi Jani,

On 4/24/06, Jani-Matti Hätinen <[email protected]> wrote:
>   I've tested this with 2.6.15-gentoo-r1 with the sdhci-0.11 patches
> and vanilla 2.6.17-rc2. Sadly nothing gets as far as to the log when
> the lock-up occurs.

If this is a regression from an earlier version, you could try git
bisect to isolate the broken changeset. See the following URL for more
details:

  http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt.

                                              Pekka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Lock-up with modprobe sdhci after suspending to ram
    • From: Jani-Matti Hätinen <[email protected]>

• References:
  • Lock-up with modprobe sdhci after suspending to ram
    • From: "Jani-Matti Hätinen" <[email protected]>

• Prev by Date: Re: [RFC][PATCH] swsusp: support creating bigger images
• Next by Date: Re: [(take 2)patch 0/7] Notify page fault call chain
• Previous by thread: Re: Lock-up with modprobe sdhci after suspending to ram
• Next by thread: Re: Lock-up with modprobe sdhci after suspending to ram
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]