[Bug 900273] New: lid
http://bugzilla.opensuse.org/show_bug.cgi?id=900273 Bug ID: 900273 Summary: lid Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jnelson-suse@jamponi.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Closing lid -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #1 from Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #3 from Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #5 from Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Kristyna Streitova
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #13 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Jon Nelson
PXSX S4 *disabled pci:0000:03:00.0 jon@linux:~>
I will see if this helps. If it does, how soon might a generic fix be made available? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #15 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #16 from Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #17 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #18 from Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #19 from Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Oliver Neukum
Thanks for tracking down!
So, it comes from USB, but a specific device. Oliver, any idea?
We might be hitting a race with the poll for medium change. Can you try with the attribute "events_poll_msecs" for the device in sysfs set to -1? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Jon Nelson
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Oliver Neukum
Doesn't seem to be available:
linux:~ # lsmod | grep rtsx rtsx_usb_sdmmc 27787 0 mmc_core 133468 1 rtsx_usb_sdmmc rtsx_usb_ms 18697 0 memstick 16966 1 rtsx_usb_ms rtsx_usb 20987 2 rtsx_usb_sdmmc,rtsx_usb_ms mfd_core 13435 2 lpc_ich,rtsx_usb linux:~ # find /sys | grep rtsx | grep events linux:~ #
These tests are no good. This line:
mmc_core 133468 1 rtsx_usb_sdmmc
tells you that the rtsx driver uses the generic mmc layer. So there will be a generic mmc device in /sys/block. Please look again. (You might need a medium present in the device for this to work) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
Maxim Mikityanskiy
(In reply to Takashi Iwai from comment #20)
Thanks for tracking down!
So, it comes from USB, but a specific device. Oliver, any idea?
We might be hitting a race with the poll for medium change. Can you try with the attribute "events_poll_msecs" for the device in sysfs set to -1?
I experience the same problem on Lenovo Ideapad Z570, Gentoo, kernel 3.17.4. I also use KDE and systemd. Sometimes laptop does not go to suspend, further writes to /sys/power/state result in "Device or resourse busy", and I can't rmmod rtsx_usb_sdmmc and bbswitch, rmmod just hangs in D state. I inserted SD card, but events_poll_msecs does not appear: max@ideapad ~ % ls -l /sys/block/mmcblk0/ total 0 -r--r--r-- 1 root root 4096 Dec 7 12:31 alignment_offset lrwxrwxrwx 1 root root 0 Dec 7 12:31 bdi -> ../../../../../../../../../../../../virtual/bdi/179:0 -r--r--r-- 1 root root 4096 Dec 7 12:31 capability -r--r--r-- 1 root root 4096 Dec 7 12:31 dev lrwxrwxrwx 1 root root 0 Dec 7 12:31 device -> ../../../mmc0:0002 -r--r--r-- 1 root root 4096 Dec 7 12:31 discard_alignment -r--r--r-- 1 root root 4096 Dec 7 12:31 ext_range -rw-r--r-- 1 root root 4096 Dec 7 12:31 force_ro drwxr-xr-x 2 root root 0 Dec 7 12:31 holders -r--r--r-- 1 root root 4096 Dec 7 12:31 inflight drwxr-xr-x 2 root root 0 Dec 7 12:31 power drwxr-xr-x 3 root root 0 Dec 7 12:31 queue -r--r--r-- 1 root root 4096 Dec 7 12:31 range -r--r--r-- 1 root root 4096 Dec 7 12:31 removable -r--r--r-- 1 root root 4096 Dec 7 12:31 ro -r--r--r-- 1 root root 4096 Dec 7 12:31 size drwxr-xr-x 2 root root 0 Dec 7 12:31 slaves -r--r--r-- 1 root root 4096 Dec 7 12:31 stat lrwxrwxrwx 1 root root 0 Dec 7 12:30 subsystem -> ../../../../../../../../../../../../../class/block -rw-r--r-- 1 root root 4096 Dec 7 12:31 uevent Instead, /sys/block/sda/events_poll_msecs exists, but it is hard drive, not the card reader. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #25 from Oliver Neukum
Instead, /sys/block/sda/events_poll_msecs exists, but it is hard drive, not the card reader.
Sorry, I overlooked that they don't use the generic mechanism. Does this happen with and without media in the reader? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273
--- Comment #26 from Maxim Mikityanskiy
OK, (In reply to Maxim Mikityanskiy from comment #24)
Instead, /sys/block/sda/events_poll_msecs exists, but it is hard drive, not the card reader.
Sorry, I overlooked that they don't use the generic mechanism. Does this happen with and without media in the reader?
I'm not sure, but it seems that the problem appears when I have microSD-to-SD adapter (without microSD card) inserted in the reader. And it seems that there is no problem when plastic stub is inserted in the reader. I haven't tested with media. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com