From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: 2.6.26-rc0: pcmcia disk changed place, does not work after s2ram
Date: Thu, 1 May 2008 21:25:11 +0200 [thread overview]
Message-ID: <20080501192432.GA1618@elf.ucw.cz> (raw)
Hi!
On thinkpad x60, pcmcia flashcard (CF in pcmcia slot) moved from hda
to hdc. Moreover, it stops working after s2ram/resume.
As a bonus, I now have this in the log after s2ram, but I believe
that's known already.
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
PM: Writing back config space on device 0000:15:00.2 at offset 4 (was
0, writing e4301800)
PM: Writing back config space on device 0000:15:00.2 at offset 3 (was
800000, writing 804000)
PM: Writing back config space on device 0000:15:00.2 at offset 1 (was
2100000, writing 2100006)
sleepy: scsi_bus_resume start
sleepy: scsi_bus_resume done
mmc0: new SD card at address e624
mmc mmc0:e624: parent mmc0 is sleeping
------------[ cut here ]------------
WARNING: at /data/l/linux/drivers/base/power/main.c:77
device_pm_add+0x60/0xd0()
Modules linked in:
Pid: 293, comm: kmmcd Not tainted 2.6.25 #287
[<c022a2af>] warn_on_slowpath+0x5f/0x90
[<c0751dba>] _spin_lock_irqsave+0x3a/0x50
[<c0241701>] up+0x11/0x40
[<c022ac2e>] release_console_sem+0x19e/0x1d0
[<c02bd705>] sysfs_addrm_finish+0x15/0x1e0
[<c02bd110>] sysfs_ilookup_test+0x0/0x10
[<c02bd3f1>] sysfs_find_dirent+0x21/0x30
[<c07507cd>] mutex_lock_nested+0x12d/0x1e0
[<c0428133>] device_pm_add+0x13/0xd0
[<c022b23b>] printk+0x1b/0x20
[<c0428180>] device_pm_add+0x60/0xd0
[<c04233d8>] device_add+0x388/0x500
[<c0595171>] mmc_add_card+0xa1/0x120
[<c0596ce4>] mmc_attach_sd+0x1e4/0x840
[<c0594db0>] mmc_rescan+0x0/0x180
[<c0594ed4>] mmc_rescan+0x124/0x180
[<c023a141>] run_workqueue+0x121/0x1d0
[<c023a0ed>] run_workqueue+0xcd/0x1d0
[<c023ab10>] worker_thread+0x0/0xf0
[<c023abac>] worker_thread+0x9c/0xf0
[<c023d820>] autoremove_wake_function+0x0/0x50
[<c023ab10>] worker_thread+0x0/0xf0
[<c023d522>] kthread+0x42/0x70
[<c023d4e0>] kthread+0x0/0x70
[<c02047cb>] kernel_thread_helper+0x7/0x1c
=======================
---[ end trace 93797a55e35ccd7c ]---
mmcblk0: mmc0:e624 SU128 123008KiB
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
reply other threads:[~2008-05-01 19:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080501192432.GA1618@elf.ucw.cz \
--to=pavel@ucw.cz \
--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
all inboxes | Powered by JetHome®