[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 <jnelson-suse@jamponi.net> --- Note: do not hit enter too early, the new bugzilla treats this as 'submit'. What I was going to write: closing the lid in KDE (at least - not sure if it's desktop dependant) does not always result in a suspend. I tried this a bunch of times yesterday. Probably 80% success rate, but at the end of the evening I closed the lid and walked away only to find that in the morning the laptop did not suspend. Nothing in /var/log/messages about trying to do so, either -- network remained connected throughout the evening, etc... -- 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 <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|lid |closing lid of laptop does | |not always result in | |suspend -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |jnelson-suse@jamponi.net, | |kstreitova@novell.com Flags| |needinfo?(jnelson-suse@jamp | |oni.net) --- Comment #2 from Bernhard Wiedemann <bwiedemann@suse.com> --- could be dependent on hardware, because ACPI / EFI can matter. Can you please attach output of dmidecode and hwinfo --all -- 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 #3 from Jon Nelson <jnelson-suse@jamponi.net> --- Created attachment 609637 --> http://bugzilla.opensuse.org/attachment.cgi?id=609637&action=edit dmidecode.txt -- 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 <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jnelson-suse@jamp | |oni.net) | --- Comment #4 from Jon Nelson <jnelson-suse@jamponi.net> --- Created attachment 609638 --> http://bugzilla.opensuse.org/attachment.cgi?id=609638&action=edit hwinfo --all Please note: this laptop (a Lenovo B570) has run multiple older versions of openSUSE without exhibiting the same issue, so this is also a regression. -- 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 #5 from Jon Nelson <jnelson-suse@jamponi.net> --- Now running 3.16.4-1.g7a8842b-desktop and it seems /better/ (not sure if fixed yet). I did notice a *LOT* of ACPI errors with the prior kernel. I had even fixed many of them, but (apparently?) kernels still don't allow overriding the DSDT. If that could be fixed, it would be super. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-maintainers@forge.pr | |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273 Kristyna Streitova <kstreitova@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- 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 <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #12 from Jon Nelson <jnelson-suse@jamponi.net> --- The doesn't-always-suspend issue has returned. I am on 3.16.2, all up-to-date. As you can see... it never really went to sleep: 2014-11-19T23:12:35.928625-06:00 linux kernel: [ 7156.713777] PM: Syncing filesystems ... done. 2014-11-19T23:12:35.928642-06:00 linux kernel: [ 7157.720509] PM: Preparing system for mem sleep 2014-11-19T23:13:29.374861-06:00 linux su: pam_unix(su-l:auth): authentication failure; logname=jon uid=1000 euid=0 tty=pts/1 ruser=jon rhost= user=root 2014-11-19T23:13:32.649301-06:00 linux su: (to root) jon on pts/1 2014-11-19T23:13:32.650291-06:00 linux su: pam_unix(su-l:session): session opened for user root by jon(uid=1000) Perhaps this is it? (from /var/log/warn, not /var/log/messages): 2014-11-19T22:53:31.523314-06:00 linux kernel: [ 6009.183512] Freezing user space processes ... (elapsed 0.001 seconds) done. 2014-11-19T22:53:31.523315-06:00 linux kernel: [ 6009.185197] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 2014-11-19T22:53:31.523316-06:00 linux kernel: [ 6009.186352] Suspending console(s) (use no_console_suspend to debug) 2014-11-19T22:53:31.523348-06:00 linux kernel: [ 6012.868216] Restarting tasks ... 2014-11-19T22:53:31.523349-06:00 linux kernel: [ 6012.868325] bcma-pci-bridge 0000:02:00.0: no hotplug settings from platform 2014-11-19T22:53:31.523350-06:00 linux kernel: [ 6012.868367] r8169 0000:03:00.0: no hotplug settings from platform 2014-11-19T22:53:31.526399-06:00 linux kernel: [ 6012.870944] done. -- 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 #13 from Takashi Iwai <tiwai@suse.com> --- This might be a regression in r8169 driver about WoL. Try to turn off WoL for each network device, such as ethtool -s $NETDEV wol d Also, give the content of /proc/acpi/wakeup, too. -- 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 <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jnelson-suse@jamp | |oni.net) | --- Comment #14 from Jon Nelson <jnelson-suse@jamponi.net> --- Before: jon@linux:~> cat wu Device S-state Status Sysfs node P0P1 S4 *disabled GLAN S4 *disabled EHC1 S3 *enabled pci:0000:00:1d.0 EHC2 S3 *enabled pci:0000:00:1a.0 HDEF S4 *disabled pci:0000:00:1b.0 RP01 S4 *disabled pci:0000:00:1c.0 PXSX S4 *disabled RP02 S4 *disabled pci:0000:00:1c.1 PXSX S4 *disabled pci:0000:02:00.0 RP03 S4 *disabled PXSX S4 *disabled RP04 S4 *disabled pci:0000:00:1c.3 PXSX S4 *enabled pci:0000:03:00.0 RP05 S4 *disabled PXSX S4 *disabled RP06 S4 *disabled PXSX S4 *disabled RP07 S4 *disabled PXSX S4 *disabled RP08 S4 *disabled PXSX S4 *disabled PEG0 S4 *disabled PEGP S4 *disabled PEG1 S4 *disabled PEG2 S4 *disabled PEG3 S4 *disabled LID0 S3 *enabled platform:PNP0C0D:00 SLPB S3 *enabled platform:PNP0C0E:00 jon@linux:~> After "sudo ethtool -s eth0 wol d": jon@linux:~> cat wu2 Device S-state Status Sysfs node P0P1 S4 *disabled GLAN S4 *disabled EHC1 S3 *enabled pci:0000:00:1d.0 EHC2 S3 *enabled pci:0000:00:1a.0 HDEF S4 *disabled pci:0000:00:1b.0 RP01 S4 *disabled pci:0000:00:1c.0 PXSX S4 *disabled RP02 S4 *disabled pci:0000:00:1c.1 PXSX S4 *disabled pci:0000:02:00.0 RP03 S4 *disabled PXSX S4 *disabled RP04 S4 *disabled pci:0000:00:1c.3 PXSX S4 *disabled pci:0000:03:00.0 RP05 S4 *disabled PXSX S4 *disabled RP06 S4 *disabled PXSX S4 *disabled RP07 S4 *disabled PXSX S4 *disabled RP08 S4 *disabled PXSX S4 *disabled PEG0 S4 *disabled PEGP S4 *disabled PEG1 S4 *disabled PEG2 S4 *disabled PEG3 S4 *disabled LID0 S3 *enabled platform:PNP0C0D:00 SLPB S3 *enabled platform:PNP0C0E:00 jon@linux:~> diff: jon@linux:~> diff wu wu2 14c14 < PXSX S4 *enabled pci:0000:03:00.0 ---
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 <tiwai@suse.com> --- See bug 905988. At best, we may fix a driver regression, but you can work around it by disabling wol in some ways, too. -- 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 #16 from Jon Nelson <jnelson-suse@jamponi.net> --- Disabling wake-on-lan works... for a while. Then suspend doesn't work *at all*. I even strace'd: echo mem > /sys/power/state and it ended up stuck in the write system call. 2014-11-24T18:40:14.289985-06:00 linux kernel: [86179.636073] PM: Syncing filesystems ... done. 2014-11-24T18:40:14.290001-06:00 linux kernel: [86180.709563] PM: Preparing system for mem sleep 2014-11-24T18:40:14.290038-06:00 linux kernel: [86180.709821] Freezing user space processes ... (elapsed 0.001 seconds) done. 2014-11-24T18:40:14.290039-06:00 linux kernel: [86180.711568] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 2014-11-24T18:40:14.290040-06:00 linux kernel: [86180.712775] PM: Entering mem sleep 2014-11-24T18:40:14.290041-06:00 linux kernel: [86180.712819] Suspending console(s) (use no_console_suspend to debug) 2014-11-24T18:40:14.290041-06:00 linux kernel: [86180.713293] sd 0:0:0:0: [sda] Synchronizing SCSI cache 2014-11-24T18:40:14.290042-06:00 linux kernel: [86180.713596] sd 0:0:0:0: [sda] Stopping disk 2014-11-24T18:40:14.290043-06:00 linux kernel: [86181.343664] PM: suspend of devices complete after 630.362 msecs 2014-11-24T18:40:14.290044-06:00 linux kernel: [86181.354677] PM: late suspend of devices complete after 11.002 msecs 2014-11-24T18:40:14.291747-06:00 linux kernel: [86181.355484] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI 2014-11-24T18:40:14.291761-06:00 linux kernel: [86181.355566] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI 2014-11-24T18:40:14.291762-06:00 linux kernel: [86181.366532] PM: noirq suspend of devices complete after 11.843 msecs 2014-11-24T18:40:14.291763-06:00 linux kernel: [86181.366986] ACPI: Preparing to enter system sleep state S3 2014-11-24T18:40:14.291763-06:00 linux kernel: [86181.368501] PM: Saving platform NVS memory 2014-11-24T18:40:14.291764-06:00 linux kernel: [86181.369253] Disabling non-boot CPUs ... 2014-11-24T18:40:14.291765-06:00 linux kernel: [86181.369300] intel_pstate CPU 1 exiting 2014-11-24T18:40:14.291765-06:00 linux kernel: [86181.370546] smpboot: CPU 1 is now offline 2014-11-24T18:40:14.291766-06:00 linux kernel: [86181.371837] ACPI: Low-level resume complete 2014-11-24T18:40:14.291767-06:00 linux kernel: [86181.371887] PM: Restoring platform NVS memory 2014-11-24T18:40:14.291767-06:00 linux kernel: [86181.372636] Enabling non-boot CPUs ... 2014-11-24T18:40:14.291768-06:00 linux kernel: [86181.372735] x86: Booting SMP configuration: 2014-11-24T18:40:14.291769-06:00 linux kernel: [86181.372736] smpboot: Booting Node 0 Processor 1 APIC 0x2 2014-11-24T18:40:14.291769-06:00 linux kernel: [86181.383700] CPU1 microcode updated early to revision 0x29, date = 2013-06-12 2014-11-24T18:40:14.291770-06:00 linux kernel: [86181.383880] Disabled fast string operations 2014-11-24T18:40:14.291771-06:00 linux kernel: [86181.386162] Intel pstate controlling: cpu 1 2014-11-24T18:40:14.291771-06:00 linux kernel: [86181.386218] CPU1 is up 2014-11-24T18:40:14.291772-06:00 linux kernel: [86181.387533] ACPI: Waking up from system sleep state S3 2014-11-24T18:40:14.291773-06:00 linux kernel: [86181.427323] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI 2014-11-24T18:40:14.291773-06:00 linux kernel: [86181.427348] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI 2014-11-24T18:40:14.291774-06:00 linux kernel: [86181.428062] PM: noirq resume of devices complete after 11.507 msecs 2014-11-24T18:40:14.291775-06:00 linux kernel: [86181.428290] PM: early resume of devices complete after 0.203 msecs 2014-11-24T18:40:14.291775-06:00 linux kernel: [86181.429181] mei_me 0000:00:16.0: irq 42 for MSI/MSI-X 2014-11-24T18:40:14.291776-06:00 linux kernel: [86181.429400] snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X 2014-11-24T18:40:14.291777-06:00 linux kernel: [86181.440211] sd 0:0:0:0: [sda] Starting disk 2014-11-24T18:40:14.291777-06:00 linux kernel: [86181.441211] [drm] Wrong MCH_SSKPD value: 0x16040307 2014-11-24T18:40:14.291778-06:00 linux kernel: [86181.441212] [drm] This can cause pipe underruns and display issues. 2014-11-24T18:40:14.291779-06:00 linux kernel: [86181.441212] [drm] Please upgrade your BIOS to fix this. 2014-11-24T18:40:14.291779-06:00 linux kernel: [86181.565504] r8169 0000:03:00.0 eth0: link down 2014-11-24T18:40:14.291780-06:00 linux kernel: [86181.639393] usb 1-1.5: reset high-speed USB device number 3 using ehci-pci 2014-11-24T18:40:14.291781-06:00 linux kernel: [86181.639434] usb 2-1.3: reset full-speed USB device number 4 using ehci-pci 2014-11-24T18:40:14.291782-06:00 linux kernel: [86181.747311] ata4: SATA link down (SStatus 0 SControl 300) 2014-11-24T18:40:14.291782-06:00 linux kernel: [86181.749357] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 2014-11-24T18:40:14.291783-06:00 linux kernel: [86181.751321] ata6: SATA link down (SStatus 0 SControl 300) 2014-11-24T18:40:14.291783-06:00 linux kernel: [86181.753088] ata5.00: configured for UDMA/100 2014-11-24T18:40:14.291784-06:00 linux kernel: [86181.797480] usb 2-1.6: reset high-speed USB device number 5 using ehci-pci 2014-11-24T18:40:14.291785-06:00 linux kernel: [86183.411410] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off 2014-11-24T18:40:14.291785-06:00 linux kernel: [86184.251818] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) 2014-11-24T18:40:14.291786-06:00 linux kernel: [86184.479212] ata1.00: configured for UDMA/133 2014-11-24T18:40:14.291787-06:00 linux kernel: [86184.487963] PM: resume of devices complete after 3057.943 msecs 2014-11-24T18:40:14.291787-06:00 linux kernel: [86184.488148] PM: Finishing wakeup. 2014-11-24T18:40:14.291788-06:00 linux kernel: [86184.488149] Restarting tasks ... 2014-11-24T18:40:14.291789-06:00 linux kernel: [86184.488262] bcma-pci-bridge 0000:02:00.0: no hotplug settings from platform 2014-11-24T18:40:14.291789-06:00 linux kernel: [86184.488318] r8169 0000:03:00.0: no hotplug settings from platform 2014-11-24T18:40:14.296617-06:00 linux kernel: [86184.493936] done. ... and after this, it wouldn't suspend again. In fact, I tried shutting it off and it just sat there, partially shut down, with no indication as to what it was doing (or not doing) for several minutes. I finally had to hold down the power button to get it to shut off. -- 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 #17 from Takashi Iwai <tiwai@suse.com> --- So something else still woke up, and it confused either kernel or systemd state that blocks the further suspend or shutdown. You can try disabling others by writing /proc/acpi/wakeup to see if it really matters. Other than that, I have no more clue. This is a really sensitive issue purely depending on the machine, and it's hard to debug remotely. The best would be to bisect the regression by yourself if you can... -- 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 #18 from Jon Nelson <jnelson-suse@jamponi.net> --- The only enabled items are: EHC1 S3 *enabled pci:0000:00:1d.0 EHC2 S3 *enabled pci:0000:00:1a.0 which are: 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI]) and 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI]) and LID0 S3 *enabled platform:PNP0C0D:00 SLPB S3 *enabled platform:PNP0C0E:00 which, according to - http://www.thinkwiki.org/wiki/Talk:How_to_make_ACPI_work - is the LID (obvious) and SLPB (the function key??) I'll keep poking around. -- 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 #19 from Jon Nelson <jnelson-suse@jamponi.net> --- Did a lot of research and rebooted a *lot*. This page: https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt was especially useful. It seemed to point to a device problem. I started blacklisting modules and found rtsx_usb (and the associated rtsx_usb_ms, rtsx_usb_sdmmc) *seemed* to be the problem. A bit of research has indicated that this used to be the rts5139, which I had previously either blacklist or used special options with. It has *always* been problematic. This page: http://unix.stackexchange.com/questions/155637/rts5139-rtsx-usb-borked-in-3-... seems to indicate I'm not alone with problems with this hardware. I'm going to leave it blacklisted, and if the system continues to be stable (although the WOL rtl1869 stuff would be a nice fix), what - if anything - can be done to fix this for others (and of course for myself in the future)? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |oneukum@suse.com Flags| |needinfo?(oneukum@suse.com) --- Comment #20 from Takashi Iwai <tiwai@suse.com> --- Thanks for tracking down! So, it comes from USB, but a specific device. Oliver, any idea? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273 Oliver Neukum <oneukum@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(oneukum@suse.com) |needinfo?(jnelson-suse@jamp | |oni.net) --- Comment #21 from Oliver Neukum <oneukum@suse.com> --- (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? -- 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 <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jnelson-suse@jamp | |oni.net) | --- Comment #22 from Jon Nelson <jnelson-suse@jamponi.net> --- 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:~ # -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=900273 Oliver Neukum <oneukum@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jnelson-suse@jamp | |oni.net) --- Comment #23 from Oliver Neukum <oneukum@suse.com> --- (In reply to Jon Nelson from comment #22)
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 <maxtram95@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxtram95@gmail.com --- Comment #24 from Maxim Mikityanskiy <maxtram95@gmail.com> --- (In reply to Oliver Neukum from comment #21)
(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 <oneukum@suse.com> --- 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? -- 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 <maxtram95@gmail.com> --- (In reply to Oliver Neukum from comment #25)
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