OK, so my results were kind of expected ;-) Anyway I'm sending my dmesg.log with mmc-debug enabled as per Pierre demand. The missing event should have been at the end of the file. As you can see, there's no evidence at all that tifm notices the card insertion after resuming. Regards, Fabio On 11/3/06, Alex Dubov <[email protected]> wrote:
I was looking into this stuff lately, and it's appears to be something complex. I couldn't get it to crush on git-head, but I've got write corruptions every now and then. And suspend is totally untested at the moment. I'm currently trying to fix this. ____________________________________________________________________________________ We have the perfect Group for you. Check out the handy changes to Yahoo! Groups (http://groups.yahoo.com)
Attachment:
dmesg.log
Description: Binary data
- References:
- Re: 2.6.19-rc4 - tifm_7xx1 does not work after suspend-to-disk
- From: Pierre Ossman <[email protected]>
- Re: 2.6.19-rc4 - tifm_7xx1 does not work after suspend-to-disk
- From: Alex Dubov <[email protected]>
- Re: 2.6.19-rc4 - tifm_7xx1 does not work after suspend-to-disk
- Prev by Date: Re: [2.6.18] Suspend to ram and SATA
- Next by Date: Re: 2.6.18 is problematic in VMware
- Previous by thread: Re: 2.6.19-rc4 - tifm_7xx1 does not work after suspend-to-disk
- Next by thread: [RFC] [PATCH 2.6.19-rc4] kdump panics early in boot when reserving MP Tables located in high memory
- Index(es):
 |